-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Vollmert wrote: | On Jul 25, 2008, at 13:13, David Earl wrote: |> I've thought about not tagging for the rendering (and name finder is a |> kind of renderer), but there isn't a simple algorithmic solution.
I always thought that "Not tagging for rendering" means "Don't tag a wide river as a motorway to make it a large blue line on the map", or, as someone did recently "Don't tag roads under construction as tunnels to make them dashed lines on the map" IMHO, it doesn't mean "Don't invent a tag that is useful for renderers". That's OK (although it's much better to use existing tags and/or try to ensure new tags are useful in other situations in future). Having said all that, in this case: | An alternative to search=yes that might be more generally useful is to | group parts of a street into a relation (see http://wiki.openstreetmap.org/index.php?title=Relation:street) | . That would be an object you could point to. It would also be | possible to mark spurs with role=spur if that would help. That is a much better idea - if a way is part of a relationship that supplies a name, use the relationship's name, not the way's. Personally, if I search for M25, I probably want to see this: http://www.openstreetmap.org/?lat=51.486&lon=-0.087&zoom=10 (the whole M25) Rather than 100 results that look like these: http://www.openstreetmap.org/?lat=51.53392&lon=0.27965&zoom=17 http://www.openstreetmap.org/?lat=51.34412&lon=0.15669&zoom=17 http://www.openstreetmap.org/?lat=51.68061&lon=0.00565&zoom=16 which is the kind of thing you get now. Robert (Jamie) Munro -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiJ7jgACgkQz+aYVHdncI2DLACg5iO43wdK1x5XgCjwnu6askrv p9EAoMyYJQJIhdMWHCETgzPU/gYi+IyS =6Y29 -----END PGP SIGNATURE----- _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
