-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No "What can be left here for recycling?" for recycling containers mapped as way #5735
Comments
Are you sure that it is not asked for recycling areas? Looking at the code, it certainly should. See #4907 |
Agree with the premise that it should be asked on a ways too, and it seems to me that it is asked on other ways, as cursory look at the code would suggest it should do: Lines 18 to 25 in 8636a3b
however I can confirm (in 58.1) that that it is not being asked on that specific way 1276097081 for some reason. |
playing in SCEE, Quest is also not shown on way 1276097081, but if I edit that way to add any unrelated tag (like Lines 38 to 45 in 8636a3b
small_Screen_Recording_20240710_220709_SCEE.mp4 |
Oh, I see the mistake. It's in line 36. |
Thanks for the quick fix @westnordost! ❤️ |
An
amenity=recycling
withrecycling_type=container
may be mapped as a single node or as an area. While nodes are way more common (373 388) than ways/areas (10 977), there is definitely a good reason to map larger recycling container areas as an area, for example this one, which consists of 23 individual containers:The corresponding OSM way is: https://www.openstreetmap.org/way/1276097081
Of course, also areas should be enriched with the
recycling:*
tags to specify what can be recycled there.How to Reproduce
Go to an recycling container area (any overlay is fine), no quest arises.
Expected Behavior
Quest "What can be left here for recycling?" should arise.
Versions affected
v58.2
Note: If I understand PR #4936 correctly, this already works for the glass recycling quest. The fix for all recycling containers could be similar.
The text was updated successfully, but these errors were encountered: