Why is OSM not listing this administrative boundary as an enclosing feature when querying features within it?

If I query features within this administrative boundary, it lists the following:


None of these are the aforementioned boundary. If I query features on the actual boundary, it shows up under “Nearby Features”:

Is this expected behavior?

Shows up fine when I checked just then, it might just be delays in waiting for whatever service is being used for that functionality (likely an Overpass server) to get the latest data.

1 Like

Yup, this one is working for me as expected now. Took a decent amount of time, though.

The Overpass server behind that query is fairly quick with updates from OSM. “Nearby Features” are usually visible around 2min after upload. Area computation takes a bit longer, though. “Enclosing Features” will only show up around 3 hours later.

5 Likes