mboeringa left a comment (osm2pgsql-dev/osm2pgsql#2333)
> A locator can then be queried using `all_intersecting()` returning a list of
> names of all regions that intersect the specified OSM object geometry.
This raises one more question: I can imagine it being very useful to have the
'all_intersecting()' function return geometries in a specific sorted order,
e.g. from largest in terms of area to smallest, to be able to use that in
subsequent processing in Lua. Think of a locator build on all OpenStreetMap
boundary relations of all levels, where you would like to see the
largest-to-smallest set of intersecting boundary relations for a specific OSM
object.
Does the current implementation implement any type of sort, or is the returned
set's order completely arbitrary?
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/pull/2333#issuecomment-2922916762
You are receiving this because you are subscribed to this thread.
Message ID: <osm2pgsql-dev/osm2pgsql/pull/2333/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
