In map_features.xml atm there appears to be a pretty big distinction
drawn between "poi" features (notably shops, amenities of various
kinds) and, for want of a better term, "area" features. They're
defined in separate parts of the file, they have different kinds of
icons, different categories (there isn't even a "shopping" category
for way features)...I first thought you were talking about mkgmap and converting area features to nodes for garmin search, and the osm->garmin style rules. Obviously I was confused, but my reaction is: It seems reasonable to say that anything that can be a node that's sort of like a POI can also be an area, which means either a closed way or a closed way with building=yes or area=yes, with the same tags as the node would have had. it would be cool if all renderers agreed that this was all equivalent maybe closed ways that are proxies for things that are originally nodes should have a node=yes tag, and that turns on "treat these tags semantically as if they were on a node". Then we can remove the way feature duplicate tagging rules and simplify. because in the garmin world we need to map areas to nodes because area POIs don't show up in searching, and because it's good to have a node being the entrance for large POIS (front door of 3 hectare store), it would be really nice to have a clean way to tie a node which is the "if you need a point, here it is" location to the polygon, so that all users that need a point for an area can get one, and autoconvert the centroid if such is not tagged. I wonder how different front door node of store polygon and town center node of town boundary really are.
pgpFIrAx1ObhK.pgp
Description: PGP signature
_______________________________________________ Potlatch-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/potlatch-dev
