Comments force "Export > Raw data from overpass api" to output xml not json #47
Labels
Comments
|
Looks very much like a bug with how the Overpass-API handles Overpass-XML queries. Maybe you can open an issue there, or @drolbr can take a look at it here… |
|
Yes, I can confirm the issue. It is a problem of Overpass API, not of Overpass Turbo. What in fact happens is that the parser encloses the whole query in an extra "osm-script" because the first element is not an "osm-script" element (it is a comment instead). This is an unwanted side-effect of the permissive XML interpretation. I'll fix this with the next version. The suggested workaround is to use proper XML, i.e. to start with the XML declaration: <?xml version="1.0" encoding="UTF-8"?> |
|
closing here in favour of drolbr/Overpass-API#73 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a bit odd. I made a simple query from a Turbo template, and the template was designed to output JSON (
output="json"). When I went through "Export > Raw data from overpass api", then copied the link and ran it using wget:It did not return JSON but returned XML. This is wrong.
Then I modified the query in the Turbo text panel, simply removing the XML "<!--" comment from the top. When I ran this one:
...it worked as intended, i.e. returning JSON content (and with a MIME type
application/json).It seems that for some reason, the comment breaks the format request.
(Please let me know if I need to redirect this to overpass issues rather than turbo issues!)
The text was updated successfully, but these errors were encountered: