Re: [Talk-us] Interstate exit junction tagging
On 10/26/2010 06:42 AM, Phil! Gold wrote:
* Mike N. nice...@att.net [2010-10-25 21:44 -0400]:
Since I believe the name={signInfo] is a US-only convention and there
are no other strong opinions, we should look at changing this.
I like the idea of putting the immediately-connected road in the exit_to=
tag and leaving the rest of the sign's text to destination sign relations.
I fully agree that some people's current practice (including mine in the
past) makes for a very clittered map and needs improvement.
Seems like the result you're looking for could be solved automatically
by the renderers if they just displayed the exit numbers unless absent,
then show the name...
signature.asc
Description: OpenPGP digital signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
On 10/26/2010 07:33 AM, Mike N. wrote: I like the idea of putting the immediately-connected road in the exit_to= tag and leaving the rest of the sign's text to destination sign relations. I fully agree that some people's current practice (including mine in the past) makes for a very clittered map and needs improvement. Interstate exit signs are carefully chosen for clarity - using only the immediately-connected road in exit_to can result in a situation such Tulsa, OK where Skelly Drive parallels I44, and there would be many exits with an immediate link to Skelly Drive: http://www.openstreetmap.org/?lat=36.0895lon=-95.95508zoom=16layers=M - totally confusing someone who uses that information. I can't think of any of those exits offhand that are actually posted as Skelly Drive. If I recall correctly (given that I'm trying to avoid taking I44 as much as work lets me thanks to ODOT detouring I-44 to Skelly Drive), none of the exits are called Skelly Drive, but instead the next cross street after the ramp. Sign relations are less ambiguous, but there is no editor assistance. In many cases, a destination city on a sign will be hundreds of KM distant, which again complicates trying to locate the object to add to the sign relation. Such as taking US-64 eastbound in South Tulsa. At Creek Turnpike, the guide sign says West / Oklahoma City. A more extreme example is in The Dalles, Oregon, where you have signs pointing out Boise. signature.asc Description: OpenPGP digital signature ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
Seems like the result you're looking for could be solved automatically by the renderers if they just displayed the exit numbers unless absent, then show the name... For named exits such as http://www.aaroads.com/northeast/pennsylvania075/i-076_wb_exit_312_01.jpg , it would be proper to tag all 3 elements: name, ref, and destination. Dropping the name rendering for locations having a ref= tag might not be desirable for many locations. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
On 10/27/2010 10:45 AM, Peter Budny wrote:
Paul Johnson ba...@ursamundi.org writes:
On 10/26/2010 06:42 AM, Phil! Gold wrote:
* Mike N. nice...@att.net [2010-10-25 21:44 -0400]:
Since I believe the name={signInfo] is a US-only convention and there
are no other strong opinions, we should look at changing this.
I like the idea of putting the immediately-connected road in the exit_to=
tag and leaving the rest of the sign's text to destination sign relations.
I fully agree that some people's current practice (including mine in the
past) makes for a very clittered map and needs improvement.
Seems like the result you're looking for could be solved automatically
by the renderers if they just displayed the exit numbers unless absent,
then show the name...
I believe this is already what they do (at least Mapnik anyway).
Mapnik renders name and ref for motorway_junctions, whenever available;
this means if both are available, both are rendered. If only one is
available, only that one is rendered.
It's /very/ useful for routing, though. I would love for my satnav to
tell me take the exit for 10th Street and then shut up, because it
knows I can just follow the signs.
I really like how the Garmin Oregon handles that...it chimes when you're
approaching a turn, then beeps twice when you're at it. This is more
desirable to me than smarmy Silicon Sally, particularly when fed bad data.
signature.asc
Description: OpenPGP digital signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
* Mike N. nice...@att.net [2010-10-25 21:44 -0400]:
Since I believe the name={signInfo] is a US-only convention and there
are no other strong opinions, we should look at changing this.
I like the idea of putting the immediately-connected road in the exit_to=
tag and leaving the rest of the sign's text to destination sign relations.
I fully agree that some people's current practice (including mine in the
past) makes for a very clittered map and needs improvement.
--
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2
--- --
Facts do not cease to exist because they are ignored.
-- Aldous Huxley
--- --
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
I like the idea of putting the immediately-connected road in the exit_to= tag and leaving the rest of the sign's text to destination sign relations. I fully agree that some people's current practice (including mine in the past) makes for a very clittered map and needs improvement. Interstate exit signs are carefully chosen for clarity - using only the immediately-connected road in exit_to can result in a situation such Tulsa, OK where Skelly Drive parallels I44, and there would be many exits with an immediate link to Skelly Drive: http://www.openstreetmap.org/?lat=36.0895lon=-95.95508zoom=16layers=M - totally confusing someone who uses that information. Sign relations are less ambiguous, but there is no editor assistance. In many cases, a destination city on a sign will be hundreds of KM distant, which again complicates trying to locate the object to add to the sign relation. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
On 10/25/10 9:44 PM, Mike N. wrote:
The official current Wiki convention for interstate tagging
http://wiki.openstreetmap.org/wiki/Interstate_Highways has the exit
sign information being placed in the name= tag. The
motorway_junction tag
http://wiki.openstreetmap.org/wiki/Tag:highway%3Dmotorway_junction
introduces a new exit_to= tag to record exit sign destinations.
There was no response to a question on the tagging list as to whether
the name= should contain all exit destinations from the sign.
http://lists.openstreetmap.org/pipermail/tagging/2010-October/005207.html
Some have commented that placing exit sign information in the name
results in a cluttered map because the name renders instead of the
ref. I agree with this.Since I believe the name={signInfo] is a
US-only convention and there are no other strong opinions, we should
look at changing this. If there are no other comments, I'll outline
the steps we'll need to go through to change this.
i think you're right. this has been bothering me for some time.
richard
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
On Mon, Oct 25, 2010 at 8:44 PM, Mike N. nice...@att.net wrote: Some have commented that placing exit sign information in the name results in a cluttered map because the name renders instead of the ref. I agree with this. I am not opposed to changing however just to be clear, both mapnik and osmarender do render both name AND ref on motorway_junction nodes. In fact, mapnik renders ref one zoom level earlier than it renders name. In the few places out here where things actually do become cluttered it seems to drop name before it drops ref. For example: http://www.openstreetmap.org/?lat=39.0943lon=-96.0354zoom=12layers=M Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Interstate exit junction tagging
I also support the change; name=* should be for simple names, for instance those that a toll road authority might assign (Pennsylvania Turnpike exit 312 Downingtown). This also means that 'floating street names' on urban highways without exit numbers will no longer be rendered. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
