I now realized that the unexpected osm ID way I see being returned, lies even
outside the extent of the Geofabrik "Liechtenstein" extract that I used as
input for osm2pgsql and testing of the import.
It is not even in the planet_osm_line table. It **is** a way member of the
Rhein relation, which is the second waterway relation next to the Alpine Rhine
one that is in the Liechtenstein extract.
This likely explains the discrepancy, I now realize: the Liechtenstein pbf
extract contains all the information of the members of the relation, but not
the actual geometries of all members.
Maybe we need an **object.members_with_geometry** iterator, that only returns a
table for complete members including full geometry, those that are being
included in the output of **object.as_geometrycollection()**?
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2204#discussioncomment-18271712
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
