-
-
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
Crash on downloading MarkCompletedHighwayConstruction quest #1041
Comments
I will look into it, hopefully today. I can reproduce it, apparently overpass changed accepted syntax without backward compatibility. So every single query in this quest will show "crash happened". I am not sure what is your policy in that cases - but hotfix that simply disables that quest may be a good idea. I am currently traveling and I will have access to a laptop in about 5 hours. Unfortunately I am also preparing for the next trip - so I will maybe make PR with fix from 5 to 20 hours from now and then I will be inactive until at least 4th May.-M |
Note - building construction quest is also likely to be affected, but it has lower priority so it will not appear often. |
I aim to release an update tomorrow, with a fix for it (and the other reported bugs). If you are not able to finish it until then, you can post your findings or other info here and I will look into it.
Am 30. April 2018 14:01:38 MESZ schrieb Mateusz Konieczny <[email protected]>:
…I will look into it, hopefully today.
I can reproduce it, apparently overpass changed accepted syntax without
backward compatibility.
So every single query in this quest will show "crash happened".
I am not sure what is your policy in that cases - but hotfix that
simply disables that worst may be a good idea.
I am currently traveling and I will have access to a laptop in about 5
hours. Unfortunately I am also preparing for the next trip - so I will
maybe make PR with fix from 5 to 20 hours from now and then I will be
inactive until at least 4th May.
|
https://wiki.openstreetmap.org/wiki/Overpass_API/versions#Overpass_API_v0.7.54 has history of versions. To my surprise it is not indicating recent updates. |
I only see the error with the building quest enabled, but that may be because there are no construction roads in my area. |
The query feature on osm.org was not working, too Ah, there is an fixed item: openstreetmap/openstreetmap-website#1843 |
So, shall I take a look? |
The issue is probably in this line: It needs to be changed to:
(two semicolons added) I don't know how the full query really looks like, I can just try to derive it from the Java source code. So watch out for those semicolons! BTW: This syntax was always documented this way on the wiki (https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Difference), but those semicolons weren't really enforced in the past. |
That was it, thank you @mmd-osm ! It works now with this fix. By the way, for your information, the full query looks like this
I also checked for the other quests if they may have the same problem, but all others are fine. |
So after the 5.1 update, I dont see any quests that actually show up for these, despite there being a half dozen buildings under construction tagged as such. Example |
@gappleto97 Please, link using rather https://www.openstreetmap.org/#map=19/46.55960/-87.41665 (it is easier to enable data layer and at least map on OsmAnd website is broken) |
Or even better - can you link a specific object like https://www.openstreetmap.org/way/525479646#map=19/46.55961/-87.41652 ? I looked quickly and nothing was building=construction. |
But this one is: |
I just tested, this quest appears for me Are you sure that you have building construction quest enabled and that you never selected "hide this quest" for this building? Can you try moving building construction quest to top in quest priority in settings and scan for more quests? |
Gah. I moved it to the top priority and it showed up, even though there were no quests around it which should have hidden it. I am confused, but it works. |
cc @matkoniecz
The text was updated successfully, but these errors were encountered: