Talk:Tag:highway=motorway junction
Discuss Tag:highway=motorway_junction here:
Contents |
Similar tag for trunk road junctions?
Could we add a tag "highway=trunk_junction" for trunk roads or are these not common? In germany, the exits of trunk-roads mostly have a name (usually the name of the town/city to where the exit leads via primaries or such) but have no numbers. How is the situation in other countries? --Jannis 17:24, 22 January 2008 (UTC)
- It's the same thing in France. And these exits can have numbers. Wagner51 10:56, 8 February 2008 (UTC)
- Other than the name, is there any particular reason why this tag is not appropriate for these exits? Chriscf 10:40, 18 September 2008 (UTC)
- The only one that I can see is that it's then hard to tell what category of road the junction is for - should it be a blue number, green number etc. Gravitystorm 10:12, 23 September 2008 (UTC)
- Perhaps, but we can deal with that when it becomes a real problem. As things stand, you can establish what type of road it's for by the road it's attached to. That is, once we've got rid of the sited-for-the-renderer nodes. Chriscf 10:53, 23 September 2008 (UTC)
- The only one that I can see is that it's then hard to tell what category of road the junction is for - should it be a blue number, green number etc. Gravitystorm 10:12, 23 September 2008 (UTC)
- Other than the name, is there any particular reason why this tag is not appropriate for these exits? Chriscf 10:40, 18 September 2008 (UTC)
Names and destinations
Some mappers seem to be adding the exit destinations as the name. I don't think this is the right thing to do, as IMO, the name tag should be the name of the junction itself (e.g. "Lofthouse Interchange", or "Spaghetti Junction" - though the latter is a common name for "Gravelly Hill Interchange, but that's a different kettle of worms). Do we need an exit_to tag?--Tms13 12:12, 3 June 2009 (UTC)
- Don't know if it's used, but there's Relations/Proposed/Destination_Signs. Alv 12:34, 3 June 2009 (UTC)
I agree. In fact I've just swapped a 'name' to an 'exit_to' key on this junction node http://www.openstreetmap.org/browse/node/205491/history Having 'Gatwick Airport' in a name tag was causing incorrect matches on this geocoding query. Now CloudMade could adjust their algorithms to filter this out (and may have to for reliability), but it is bad tagging in my opinion. There's plenty of scope for systems (anything automatically examining name tags) to get confused if we start putting signed destination names in name=*. So I agree we should not do that. -- Harry Wood 14:31, 11 June 2009 (UTC)
How about junction=exit instead?
Why is this a highway=*? Wouldn't it be cleaner with junction=*? And whats with the motorway bias? 'exit' would work (and not be confusing) in any highway level. --Gorm 19:31, 3 July 2010 (UTC)
- I think it's highway=motorway_junction because motorway junctions are grade-separated… and highway=grade-separated_junction just looks stupid. Kevin Steinhardt 00:08, 9 August 2010 (BST)
- So you are saying that only motorways are grade separated? I think not: http://www.openstreetmap.org/?lat=59.46305&lon=5.47472&zoom=17&layers=O. --Gorm 01:23, 17 August 2010 (BST)
- I personally wouldn't be against doing it this way, but I think highway=exit would be better if it was changed. --Rickmastfan67 05:20, 17 August 2010 (BST)
- So you are saying that only motorways are grade separated? I think not: http://www.openstreetmap.org/?lat=59.46305&lon=5.47472&zoom=17&layers=O. --Gorm 01:23, 17 August 2010 (BST)
Street name
Should a street name on an exit sign be included as name, exit_to, or not at all? If the exit sign just has a street name, does that count as the name of the junction itself? The thing is that the road where the exit ramp ends does not always match the road on the sign. Evil saltine 05:14, 11 March 2011 (UTC)
- The text on the sign would be exit_to. The street it leads directly to is already in the database as the way that intersects the chain of motorway_links that begins at the motorway_junction node. A junction name is a separate thing that often doesn't exist. --NE2 06:44, 11 March 2011 (UTC)
- Thanks. Evil saltine 14:23, 23 March 2011 (UTC)
Multiple exits - Collector roads
In Virginia there are approximately 47 "exits" which lead to collector roads which then have the actual exists. In some areas these have been tagged by separating the actual exit numbers with semicolons, e.g. ref=123A;123B;123C. However you then have additional nodes on the collector road which are the actual exits, ref=123A, etc. How is this to be handled? For the Virginia Department of Transportation (VDOT) database, they indicate this initial "exit" with the X suffix, e.g. 123X. I doubt this is the way to go, at least not without sufficient warning to the routing developers out there, not to mention there might actually be an X suffix used somewhere in the world. -- Joshdoe 02:28, 2 April 2011 (BST)
- There's a 2X in Kansas City: http://www.okroads.com/080904/i35moappi70_14mi.JPG and a 15X in New Jersey. What I've done is find a sign that lists all the exits together and use whatever it uses. That might be 123, 123A-B-C, 123ABC, or 123A-C. If there's no such sign, I guess you'd use whatever is normally used in that area of the state. --NE2 17:28, 2 April 2011 (BST)
- I agree with matching the sign - I've seen it two ways that I can find: 123 or 123A-C MikeN 00:54, 3 April 2011 (BST)
- Ha, thanks for that picture, good to know! So we'd all agree to create multiple exits then, and to use whatever is on the sign or whatever is common convention in that area? Then later if necessary we could add a tag like motorway_junction=collector_road or something to indicate that it's not an actual exit from the interstate (assuming you consider the collector road to be part of the interstate). -- Joshdoe 02:08, 3 April 2011 (BST)
Where to split the junction
The text states that the splitting point should be located at the place where junction "spplits" from mailine, but this is not very clear what exactly is meant by this. Also for routing SW it would be nice if we can distinguish at least two (if not more) places - point where the splitting line emerges and the point where it separate from the continuing lanes (point where the two lanes stop to be separated only by a full line and diverge). Apart from this there are also other interesting points, for example the point where the full line starts - i.e. the last point where I can choose whether I take the exit or not. Also there is a fourth place - the point where link and mainline stop to be connected by surface and separate. All these points can be several hundreds meters apart from each other. Also some of these splitting points are not only of academic interest, but they can be very useful for navigation SW which provide navigation in lanes.
Jakub
- We don't mark the point at which lines become solid on approaching an at-grade intersection. (Also, depending on where you are, it may be legal to cross a single solid line.) --NE2 16:10, 18 August 2011 (BST)