So I’ve noticed that the in-map query feature (for a specific location) isn’t showing enclosing boundaries. For example, if I query anywhere on this view, the query results will show no enclosing features. However, if you zoom out, you can see that there are actually two boundaries that enclose this area: the country boundary UL22f and the city/municipal boundary Viskestads Kommun.
From trying this out, it seems like this feature hasn’t updated: areas that were in the country boundary before I edited the border here still will get the country returned on the query. However, newly added areas aren’t showing it (it’s been a couple of days since I edited these borders) even though they are inside the relation.
Any suggestions or help?
Comment from Luciano on 15 December 2021 at 14:12
That’s true. The “query features” tool is based on overpass, and “enclosing features” is based on a special run creating an enclosing areas table in the overpass database.
I will note that your boundary isn’t updated properly in the ogf-topo layer either, for low zooms.
Both of these represent failures of the replication update process from the source data (rails port AKA apidb) to the render database or overpass database.
I confess I don’t fully understand the contexts and causes of these failures. They are unpredictable and inconsistent. I am aware of the problem but for now, it’s something I have to continue troubleshooting because I don’t know the solution. For the renders, I can periodically “restart” the render (reload it from zero) and that fixes the problems. I’m not sure I have that option with overpass. I will continue working on it.
Comment from Anonymous21 on 15 December 2021 at 16:31
Okay, thank you so much!