[OSM-talk] routing - US interstate type junction -Wichita, KS
There is a junction on the north end of Wichita KS, that does not route correctly in the southbound direction. http://www.openstreetmap.org/?lat=37.7627lon=-97.3218zoom=14layers=B000FTF I downloaded the openstreetmap for Garmin from na1400.info and noticed it there so I tried the same navigation from http://www.yournavigation.org/ and it did the same thing. I added bridges to this intersections map a few days ago - but the na1400.info data doesn't have my changes yet. I have looked at the tags on the sections of the road and don't see anything unusual. cloudmade.com seems to have an older version of the data and on there the routing works. I would like to fix this and if I messed it up I apologize and want to learn from this so it doesn't happen again. If someone has time to find the problem - please let me know what it is. Thanks ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] routing - US interstate type junction -Wichita, KS
One thing I see at that intersection is that where the roads split with the connector to 254, the southeastern link appears to be tagged wrong. If you start from the north, working south: A way named as carrying US 81, State 15 and State 96. Also relation named 135 south. Split with a connection to 254 - Problem US 81, etc also continues south. The problem connector is also named US81...etc, as well as containing the routing relation 135 South. I believe that is what disrupted the routing. -- From: Tim Litwiller t...@litwiller.net Sent: Tuesday, September 22, 2009 5:04 PM To: talk@openstreetmap.org Subject: [OSM-talk] routing - US interstate type junction -Wichita, KS There is a junction on the north end of Wichita KS, that does not route correctly in the southbound direction. http://www.openstreetmap.org/?lat=37.7627lon=-97.3218zoom=14layers=B000FTF ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] routing - US interstate type junction -Wichita, KS
The problem connector is also named US81...etc, as well as containing the routing relation 135 South. I believe that is what disrupted the routing. A further clarification - the connection from 81 to 254 would be a secondary_link , since the road to which it connects is secondary.If it connected with another motorway, the connecting road would be a motorway_link. A *_link way usually does not have a name except for unusual cases. As an option (not required for routing), if the connection to 254 is marked as an exit, you would place a motorway_junction and enter the name(s) as shown on the sign, separated by semicolons, and the exit number. Another option is to add a 'ref' tag to the secondary_link with just the exit number. Eventually turn-by-turn instructions could make use of that information. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] routing - US interstate type junction -Wichita, KS
On Tue, Sep 22, 2009 at 5:04 PM, Tim Litwiller t...@litwiller.net wrote: There is a junction on the north end of Wichita KS, that does not route correctly in the southbound direction. http://www.openstreetmap.org/?lat=37.7627lon=-97.3218zoom=14layers=B000FTF I downloaded the openstreetmap for Garmin from na1400.info and noticed it there so I tried the same navigation from http://www.yournavigation.org/ and it did the same thing. I added bridges to this intersections map a few days ago - but the na1400.info data doesn't have my changes yet. I have looked at the tags on the sections of the road and don't see anything unusual. cloudmade.com seems to have an older version of the data and on there the routing works. I would like to fix this and if I messed it up I apologize and want to learn from this so it doesn't happen again. If someone has time to find the problem - please let me know what it is. where 254 W ramp merges into 81 S, there was an errant node that required a 178 degree turn left, then 178 degree turn right after a few yards. This was bad for my neck at 70 MPH, so I removed it. ;-) http://www.openstreetmap.org/browse/node/505128415/history That sort of thing happens to me when I edit with potlatch and fumble the mouse. Not an analogy. If you are fixing TIGER stuff, remove the tiger:reviewed=no tags, or change them to yes. I consider layer=0 redundant and leave it out. Others don't. ;-) Interstates, US Routes, State Routes, anything with a highway shield sign, should have a ref=number, so I-254 is ref=254 TIGER had nodes that joined each overpass to each road passing below. Detach those nodes, then delete them. If they add important shape, move them enough that they don't overlap. None of this should break routing.though. There are a couple of typos lay=0 Do you ever change from a layer to a layer more than +/-1? I wonder if that will break routing? Have fun! ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] routing - US interstate type junction -Wichita, KS
On Tue, Sep 22, 2009 at 16:55, Mike N. nice...@att.net wrote: The problem connector is also named US81...etc, as well as containing the routing relation 135 South. I believe that is what disrupted the routing. A further clarification - the connection from 81 to 254 would be a secondary_link , since the road to which it connects is secondary. If it connected with another motorway, the connecting road would be a motorway_link. Actually, I'd say that the most common method (and what it sounds like the map features page on the wiki says) is to tag the higher of the two road classes for *_link, rather than the class of the road being connected to. So the correct tag would be motorway_link when leaving or joining a motorway regardless of the class of the other road, trunk_link if one road is a trunk and the other is anything other than motorway, and so on. It also looks like, from what I can see on aerial photos, the highway=motorway designation could apply further east for another couple miles, but I'll let someone with local knowledge make the decision there. -- David J. Lynch djly...@gmail.com ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
