Weird behaviour in Overpass Turbo queries

Help and support
1

Hello,

in the following Overpass QL query I can either comment out line #3 or not. When leaving it, I get the result of a search focused on one relation number. When commenting it out, I get the result of the same search, based on an area rather than a relation number.

area[name=France]->.france;
rel[network=rwn][route=hiking][type~route](area.france)->.rwn;
rel[network=rwn][route=hiking][type~route](19907325)->.rwn;
.rwn;
out;

What I don’t understand is why the ~1000-long list of relations returned by the area-based query does not include the one relation. The other query proves that the relation matches the criteria, and that it is located in the area. So why is it not included in the list?

Any idea where the problem lies?

1 Like
2

This relation has no members except relations.

KISS principle:

area[name="France"]->.france;
rel[network=rwn][route=hiking][type=route](area.france);
out geom;

returns 80 MB.

3

Are you implying that Overpass filters do not support super-relations?

2 Likes
4

Geospatial filters, it works with attribute-based filters.

2 Likes
5

This help forum post is old but I believe still relevant (public transport “route master” relations are usually similar in that they only contain other relations):

1 Like
6

Thanks for this. It feels a little clunky, but hey that’s life.