Martin,
I have now added a type=building relation to group the Pantheon's Simple
3D features in a logical way. It is this relation:
http://www.openstreetmap.org/relation/6325840.
I added the "outline" role to the multipolygon representing the
building's footprint, and added the "part" role to all building:part
features in the relation. This is how a properly formed Simple 3D
building should be tagged.
As you can see now on the OpenStreetMap website, whatever part you
click, you can now navigate "upwards" to the parent type=building
relation, to see which features are all parts of the building, and then
move "downwards" to the feature with the "outline" role to get to the
actual building tags. I hope you agree that navigating the buildings
individual parts, and finding the actual feature that carries the
buildings tags (which should always be the closed way or multipolygon
with the outline role), is now fare easier.
I still wish though that the main OpenStreetMap website's interface
would stop showing the senseless individual nodes or ways links first
when you select a feature, and put relation links on top instead. This
would make it even more obvious that there is a parent building relation
present. Now, you sometimes need to scroll down considerably, to get to
the relation links. In my opinion, the hierarchy of nodes/ways/relations
should be reversed in the display on the website. I have never
understood the choice for the current display / order, it is just not
logical for navigation.
Marco
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk
