That doesn't work because
a) there isn't one geometry for a member, there are lots of possible geometries
you can create from a member (if the member is a closed way for instance, a
linestring or a polygon)
b) for a property we'd need to create the geometry even if it isn't used which
creates a lot of overhead
We'll figure something out eventually, but for the moment: this is harder than
it looks which is partly due to the OSM data model but partly also due to the
way osm2pgsql handles these things internally.
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2204#discussioncomment-18282429
You are receiving this because you are subscribed to this thread.
Message ID:
<osm2pgsql-dev/osm2pgsql/repo-discussions/2204/comments/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving