Differences in QuickOSM and overpass-turbo.eu (parsing issue?) about quickosm HOT 4 CLOSED

The difference is that QuickOSM is using a different OSM data interpreter/converter than overpass turbo. While the latter is using osmtogeojson, I presume that QuickOSM is using QGIS' internal routines for handling OSM data (via OGR, I guess).

This explains why QuickOSM can't handle the geometry="center" output in the second part of this issue, because this is a very new Overpass-API feature that is still to be implemented on many Overpass-data-consuming programs.

The small differences in the first part of this ticket likely result from slight differences in how certain corner cases in OSM data are interpreted by the different converter libraries. For example node/2377791618 (a member of a tourism=zoo site relation) is a delta between the two programs (I don't see any difference in lines, but I can't test it directly in the QuickOSM plugin atm because of #26). This node is probably ignored by QGIS because it doesn't have any tags. osmtogeojson preserves it, however, because it is a member of a relation.

from quickosm.

I see. I think there is another explanation because of the somehow idiosyncratic concept of the Overpass API: I assume, that it's a two step process where XML-attribute output (<"osm-script output="json"...) defines the result (XML or JSON) and the the XML-tag "print" (<print mode="... ) defines how the result is being processed in the client.

Regarding to this issue, I guess, QuickOSM ignores the print statement completely (so it's not really because of OGR parsing the result document).

If this is correct that the print statement is ignored, this should be communicated to end users in the help pages of QuickOSM.

from quickosm.

In OGR, the osmconf defines which tags are unsignificant if there are alone :
https://github.com/3liz/QgisQuickOSMPlugin/blob/master/CoreQuickOSM/Parser/QuickOSMconf.ini#L22
This might be the reason for the first query.

For the second query, the "center" won't be fix in OGR : http://trac.osgeo.org/gdal/ticket/5523

QuickOSM doesn't change anything about the print statement. You can try body, skeleton, meta. You should get different results.
However, QuickOSM needs XML (because OGR don't know this kind of json), so the output is re-written before sending the query to the server.

from quickosm.

Thanks!

from quickosm.