-
Notifications
You must be signed in to change notification settings - Fork 923
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
Query Feature says Bad Request #1843
Comments
Unfortunately that service is outside our control - all we can do is send it queries and hope. |
So I assumed you meant a general failure of the overpass service but actually it's only one of the queries that is failing, and it is actually reporting an error if you dig a bit deeper in the inspector:
I have no idea what it means though... I assume that the initial segment is the "union" but I have no idea which item is the "print" it is complaining about. |
Ah I think it wants a semicolon after the second entry in the union. |
Yes, the semicolon was missing. Roland deployed version 0.7.55 on one of the two production servers earlier today, and this version has a slightly more restrictive syntax check with regards to the union statement. The other server currently still runs on 0.7.54, so there's like a 50% chance you would hit this issue today. Edit: May 1st: both production servers are on 0.7.55 now. I applied pretty much the same change to a number of examples on the Overpass by Example page in the wiki. |
Err yeah, my bad, I wasn't clear. I had seen the more detailed error messages but I had forgotten to write about them. |
Hmm, if 0.7.55 introduces changes that make previously-working queries fail, shouldn't it be named 0.8.0 then? |
Overpass uses a different versioning schema: this is really a change from 0.7.54.13 to 0.7.55 (.0). |
I'm sorry. If was of course not intended to break things. However, the omission of the semicolon never was intended as valid syntax. And I never checked that that worked and that anybody used that. I'm sorry for the inconvenience. Thank you, M1dgard for reporting the thing and thank you, Tom, for fixing it. |
Since some days now, the Query Feature feature consistently fails with
Error contacting https://overpass-api.de/api/interpreter: Bad Request
.The query it appears to be sending is (split on multiple lines and indented):
The text was updated successfully, but these errors were encountered: