Retations not shown in output, depends on reference node?

[maganap]

Hello!

I'm trying to recurse up and down from a node, like this:

( node(21289794); <; >; ); out meta;

This node, 21289794, belongs to a way and then to a relation: highway=motorway A-7 in Spain.

When using query-overpass, I don't get the 3 expected relations that I do get from other tools:

• If I make this request from http://overpass-turbo.eu/ , I receive 31204 nodes, 3169 ways, and 3 relations.

• If I make the same request directly to OSM interpreter, I get 31189 nodes, 3166 ways, and 3 relations.

  curl --location --globoff -o a7.osm “http://api.openstreetmap.fr/oapi/interpreter?data=[out:json];(node(21289794);%3C;%3E;);out;”

• If I make the request using query-overpass, then, I get 1024 nodes (which is fine), 3169 ways, but I get none of the 3 relations.

  echo '[out:json];(node(21289794);<;>;);out meta;' | query-overpass > a-7.json

If I make the same procedure using a different node (506902452), which belongs to relation: highway=motorway A-20 in Spain, I do get 1 relation using each of the 3 previous methods.

Shouldn't I get the expected relations using the 3 methods?
Thanks in advance!

[perliedman]

@tyrasd it feels like you're probably a lot more qualified than I to answer this - I've never worked with relations through the Overpass API. Any clues as to these differences?

The only difference I can see is that Overpass Turbo uses XML for this request, while query-overpass currently only supports JSON.

[perliedman]

I implemented XML support in query-overpass (released as version 1.5.0), and I can see that there is a difference between the GeoJSON exported from Overpass with JSON output compared to Overpass with XML output, but still none of them look like what's exported via Overpass Turbo...

I'm experiencing similar issue - empty relation arrays even though my output from Overpass turbo contains several. Upon inspecting osmtogeojson library code it seems the enhanced output flag is responsible for generating relations.

https://github.com/tyrasd/osmtogeojson/blob/bd508f1ceb079e1edacf21747551cf722b2f5fdb/osmtogeojson#L141

Strangely enough I now get correct result after explicitly specifying {flatProperties: false} option

        osmQuery(query,  resultHandler, {flatProperties: false});        

[tyrasd]

@tyrasd Any clues as to these differences?

Hm. Yes, the overpass API returns OSM relations, but query-overpass (as well as overpass-turbo) pass the raw OSM data through osmtogeojson to get GeoJSON (which one can display on a map for example). But osmtogeojson (v2.*) doesn't know about route relations (that's a feature that will come with v3), so you don't get GeoJSON features for these relations. That's to be expected.

I can see that there is a difference between the GeoJSON exported from Overpass with JSON output compared to Overpass with XML output

Really? That shouldn't be the case. Can you give a concrete example where this happens?

but still none of them look like what's exported via Overpass Turbo...

yeah, overpass-turbo has (for historic reasons) it's own dialect of the GeoJSON properties it outputs (it's kind of a mix between what you get in osmtogeojson with flatProperties set to true and and it set to false). It's confusing and I'll probably eventually change this into something that matches what osmtogeojson does.

I'm experiencing similar issue

@vietnugent oddly, I can't reproduce your issue. osmQuery(query, resultHandler, {flatProperties: false}); produces exactly the same results as osmQuery(query, resultHandler); for me, which both have the relations fields in the output.

[te0d]

@maganap I experienced a similar issue where I was not getting relations in the output from query-overpass while overpass-turbo did work. Eventually I noticed that installing query-overpass installs osmtogeojson [2.2.12] while overpass-turbo uses osmtogeojson [3.0.0-beta.3]. As tyrasd said, it's expected behavior up until osmtogeojson v3.

To get around this, I modified my package-lock.json to cause query-overpass to use [3.0.0-beta.3]. Query results then matched the output of overpass-turbo.

@perliedman Updating dependencies should resolve the issue.

[maganap]

@te0d Great to know! I'm not working on that project anymore, but as soon as I have the opportunity I'll try that. Thanks a lot

[perliedman]

@te0d happy to update dependencies once it's no longer a beta!