> > > I'm in danger of spending more time flaming than fixing the map, but > have always been interested in the database schema aspect of OSM. > Evolving tags is messier than a designed scheme, but I see the > wisdom of > how it avoids the wrong design persisting. Still, I think it may make > sense to try to design each microfeature. >
good catch. total chaos yet still very useful data and fun work > The US highways in California are really (I think) regular US > highways, > but CA uses a different kind of sign. So tagging then us_us_ca seems > again like tagging for the renderer. This is sort of OK, perhaps, but > it bothers me perhaps because it's doing so in a denormalized way. > Database users that care if something is a US highway will then have > to > have a list of tags and check against that set. > many states had(have?) different signs. wikimedia has lots of examples. > An alternative would be to have a shield hint tag, like > > shield_flavor=us_ca > posted earlier. if someone is willing to write the rules for a renderer perfect. but shortterm it's easier to add a symbol ref like proposed here http://wiki.openstreetmap.org/wiki/United_States_roads_tagging > added, leaving network=us_i. Then users that don't care about sign > variants jus see us highways, and renderers get their hints. Or > perhaps > renderers know that a highway is in CA. Or maybe the shield_flavor is > needed because we're trying to match each road's actual signs, and > they > aren't consistent. Or maybe it's shield_flavour. > > For Route 66, I'm not clear on whether it is a historic route and the > current legal route is elsewhere. If so, the the historic > designation is > part of the actual designation, not a rendering hint. > > _______________________________________________ > Talk-us mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/talk-us _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
