<html>
At 2011-03-28 12:40, Ian Dees wrote:<br>
<blockquote type=cite class=cite cite>On Mon, Mar 28, 2011 at 2:35 PM,
Mike N <<a href="mailto:niceman@att.net">niceman@att.net</a>>
wrote:
<dl>
<dd>On 3/28/2011 3:19 PM, Ian Dees wrote:
<dd>In this picture:
<dd><a href="http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg">http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg</a><br><br>
<dd><<a href="http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg" eudora="autourl">http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg</a>>What
<dd>is the proposed tag for the highway=motorway_junction node?
<dd>Are we tagging the node with exactly what is on the sign or are we
<dd>looking down the road and coming up with text on our own?<br><br>
</dl><br>
Where possible, this will duplicate the sign. The thinking is
that sign contents are carefully chosen for maximum clarity to drivers,
and to distinguish them from nearby exits. That will not
necessarily be the nearest main road the exit leads to. The Wiki would
have the exit node as<br><br>
ref=20A<br>
name=<br>
exit_to=HI 63 North; Likelike Hwy<br><br>
(Exit Only optional also, I suppose)<br><br>
Ok, that makes sense. I am thinking of the case where a GPS provider or
directions provider uses our data and wants to have "Take exit 20A
towards HI 63 North Likelike Hwy" on the screen or spoken via
TTS.<br><br>
With that in mind I think it's important that the exit_to tag only
include verbage on the sign (and not stuff we make
up).</blockquote><br>
IMO, not all the verbage on the sign. I've been tagging name as the name
of the exit according to the relevant authority (e.g. CalTrans in CA). I
accept that people now want to change this to use exit_to instead of
name. However, some exit signs also have destination information, like
the name of the city or local tourist attraction. This secondary
information I've been putting in a towards tag. I would also like to
separate the name into a root and a directional component. e.g.<br><br>
Signed:<br>
Exit 19<br>
[SR2 shield] South<br>
Los Angeles<br><br>
Tagged:<br>
ref=19<br>
exit_to=CA-2<br>
exit_to_dir=South<br>
towards=Los Angeles<br><br>
<br>
Signed:<br>
Exit 54<br>
Mountain Avenue<br>
Mount Baldy<br><br>
Tagged:<br>
ref=54<br>
exit_to=Mountain Avenue<br>
towards=Mount Baldy<br><br>
<br>
NE2 seems to have already jumped ahead with
<a href="http://www.openstreetmap.org/browse/changeset/7787398" eudora="autourl">http://www.openstreetmap.org/browse/changeset/7787398</a>
- "change name to exit_to and speed limits to mph". Perhaps he can comment on exactly what he did so I know what I have left to do in SoCal, where I've been the primary tagger of on/offramps.<br><br>
How do we ask the renderers to recognize the new schema?<br><br>
Also, JOSM should have the ability to concatenate ref, exit_to, exit_to_dir, and towards (currently, you can just pick one via mappaint.nameOrder).<br>
<x-sigsep><p></x-sigsep>
--<br>
Alan Mintz <Alan_Mintz+OSM@Earthlink.net><br>
</html>