This issue reminds me of something I saw a lot of recently on OSMin Fort Collins, Colorado. I get the impression that the mapper whodid this editing did it as a way to avoid the problem(s) mentionedregarding routing. When I first saw this "peculiar" way of mappingtraffic signals, I didn't speak up. I'm glad this finally got me to do so. Instead of placing the traffic_signals key at the intersection nodes ofa dual carriageway (divided highway) intersection with signals, thismapper created "redundant" nodes on the ways (one-ways) prior tothe intersections (and prior to pedestrian crossings, of course) atthe point where vehicles (by law) must stop for a red signal. Here is just one example of many in Fort Collins: http://www.openstreetmap.org/#map=19/40.55255/-105.07708 David From: "[email protected]" <[email protected]> To: [email protected] Sent: Monday, July 27, 2015 11:10 AM Subject: Talk-us Digest, Vol 92, Issue 19 Send Talk-us mailing list submissions to [email protected]
To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstreetmap.org/listinfo/talk-us or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Talk-us digest..." Today's Topics: 1. Am I mapping this wrong, or should the router be fixed for this? (James Mast) 2. Re: Am I mapping this wrong, or should the router be fixed for this? (Tod Fitch) 3. Re: Am I mapping this wrong, or should the router be fixed for this? (Mike Thompson) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Jul 2015 11:58:04 -0400 From: James Mast <[email protected]> To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: [Talk-us] Am I mapping this wrong, or should the router be fixed for this? Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" I've been normally mapping slip lanes as '_link' highways at intersections since the beginning. However, as most fellow US mappers know, they almost never have 'speed limits' posted for them, and that seems to help cause problems in some routing programs when they give those slip lanes a speed limit higher than the main highway. Anyways, I've been using OSMAnd recently for occasional offline routing on my tablet and have come across weird routing (I'd like to call them 'bugs') at some intersections that have 3+ traffic lights nodes at them because of the roads being divided. Here, OSMAnd routes me onto a slip lane, makes a U-Turn on the side road, and then continues the across the main road to accomplish what a simple 'left turn' could have done [1], all to avoid '1' traffic light node. So, I go report the 'bug' on the OSMAnd Google group [2], and then somebody forwards it to the GitHub site [3]. In the response I get back on GitHub, one of the maintainers of OSMAnd says it's a 'map data' issue and closes it. Claims that in the 'maneuver', since it avoids an extra traffic light node, it's the shortest route, even though it does that funky U-Turn. Say what?! I mean, honestly, if both MapQuest Open & OSMR can do that left turn 'normally' without needing to make a funky U-Turn, something has to be wrong in OSMAnd, right?? Sure, there isn't a 'NO U-Turn' sign posted for this maneuver, but still, the routing engine shouldn't be suggesting it since there isn't a 'NO Left Turn' relation there preventing the left turn from McKnight SB to Siebert EB. So, that leads me to my question. Does anybody think I've tagged the intersection incorrectly? This is how I've been tagging intersections like this from since the start, and I know most other US mappers have been doing the same. Or should I start adding 'false' U-Turn restrictions to prevent the routing bugs and then be called out as 'tagging for the router', or even maybe start putting traffic light nodes at the stop lines for intersections that have both roads divided (and just leave simple one-node intersections as-is)? I'm very curious to see what others have to say about this to see how I'll move forward when I map in the future. Also, don't hesitate to respond at the Google Group post or the GitHub one too as I get the e-mail notifications from them as well. -James [1] - (MapQuest routing, OSMAnd suggestion in [2] link) - https://www.openstreetmap.org/directions?engine=mapquest_car&route=40.53204%2C-80.01073%3B40.53002%2C-80.00614 [2] - https://groups.google.com/forum/#!topic/osmand/XJ-HVOHhKEM [3] - https://github.com/osmandapp/Osmand/issues/1501 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20150727/8a715b2f/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 27 Jul 2015 09:29:08 -0700 From: Tod Fitch <[email protected]> To: James Mast <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [Talk-us] Am I mapping this wrong, or should the router be fixed for this? Message-ID: <[email protected]> Content-Type: text/plain; charset="windows-1252" > On Jul 27, 2015, at 8:58 AM, James Mast <[email protected]> wrote: > > I've been normally mapping slip lanes as '_link' highways at intersections > since the beginning. However, as most fellow US mappers know, they almost > never have 'speed limits' posted for them, and that seems to help cause > problems in some routing programs when they give those slip lanes a speed > limit higher than the main highway. > > Anyways, I've been using OSMAnd recently for occasional offline routing on my > tablet and have come across weird routing (I'd like to call them 'bugs') at > some intersections that have 3+ traffic lights nodes at them because of the > roads being divided. Here, OSMAnd routes me onto a slip lane, makes a U-Turn > on the side road, and then continues the across the main road to accomplish > what a simple 'left turn' could have done [1], all to avoid '1' traffic light > node. So, I go report the 'bug' on the OSMAnd Google group [2], and then > somebody forwards it to the GitHub site [3]. > > In the response I get back on GitHub, one of the maintainers of OSMAnd says > it's a 'map data' issue and closes it. Claims that in the 'maneuver', since > it avoids an extra traffic light node, it's the shortest route, even though > it does that funky U-Turn. Say what?! I mean, honestly, if both MapQuest > Open & OSMR can do that left turn 'normally' without needing to make a funky > U-Turn, something has to be wrong in OSMAnd, right?? Sure, there isn't a 'NO > U-Turn' sign posted for this maneuver, but still, the routing engine > shouldn't be suggesting it since there isn't a 'NO Left Turn' relation there > preventing the left turn from McKnight SB to Siebert EB. > > So, that leads me to my question. Does anybody think I've tagged the > intersection incorrectly? This is how I've been tagging intersections like > this from since the start, and I know most other US mappers have been doing > the same. Or should I start adding 'false' U-Turn restrictions to prevent > the routing bugs and then be called out as 'tagging for the router', or even > maybe start putting traffic light nodes at the stop lines for intersections > that have both roads divided (and just leave simple one-node intersections > as-is)? > > I'm very curious to see what others have to say about this to see how I'll > move forward when I map in the future. Also, don't hesitate to respond at > the Google Group post or the GitHub one too as I get the e-mail notifications > from them as well. > > -James I use OSMand for a couple of reasons, but I am really beginning to think that the developers are confused with their routing logic and assumptions. I’ve largely fixed the routing via _link ways by changing routing.xml for my personal use. My changes delete all their odd penalty logic when changing from one class of highway to another and simply set a reasonable default assumed speed for ways without maxspeed tagging. Basically, I set the maxspeed assumptions to be that for my state and then set the _link speeds to 1/2 that of the associated highway class. That fix has been mentioned by several posters on the OSMand discussion area and has been routinely ignored over several OSMand releases. So my opinion is that you are mapping correctly (as evidenced by other routing engines giving reasonable results) and that the OSMand team is getting confused about how to actually fix the routing issues that are routinely being posted on their Google Group area. Cheers, Tod -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20150727/f7211569/attachment-0001.html> ------------------------------ Message: 3 Date: Mon, 27 Jul 2015 11:10:40 -0600 From: Mike Thompson <[email protected]> To: James Mast <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [Talk-us] Am I mapping this wrong, or should the router be fixed for this? Message-ID: <CALJoUku+EzwSchK=xs3t3ulrubsgj3q2owvycd9n+bb0+kj...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" In reality there is only one set of stop lights there, correct? In other words, if one were headed south on McKnight Road turning east on Seibert, one would not have to stop (assuming red lights) three different times. 1) A routing engine should have some heuristics to interpret the three (in this case) nodes tagged "highway=traffic_signals" as one. 2) There should be some cost in a routing engine for making a u-turn so as to discourage such routes even if there was an extra set of signals. Making a u-turn does take time (one can not go from the posted speed limit in one direction to the posted speed limit in the other direction instantly). The presence of other traffic in the opposing directly would add further to the time needed to make a u-turn as one would have to wait for an opening. Mike On Mon, Jul 27, 2015 at 9:58 AM, James Mast <[email protected]> wrote: > I've been normally mapping slip lanes as '_link' highways at intersections > since the beginning. However, as most fellow US mappers know, they almost > never have 'speed limits' posted for them, and that seems to help cause > problems in some routing programs when they give those slip lanes a speed > limit higher than the main highway. > > Anyways, I've been using OSMAnd recently for occasional offline routing on > my tablet and have come across weird routing (I'd like to call them 'bugs') > at some intersections that have 3+ traffic lights nodes at them because of > the roads being divided. Here, OSMAnd routes me onto a slip lane, makes a > U-Turn on the side road, and then continues the across the main road to > accomplish what a simple 'left turn' could have done [1], all to avoid '1' > traffic light node. So, I go report the 'bug' on the OSMAnd Google group > [2], and then somebody forwards it to the GitHub site [3]. > > In the response I get back on GitHub, one of the maintainers of OSMAnd > says it's a 'map data' issue and closes it. Claims that in the 'maneuver', > since it avoids an extra traffic light node, it's the shortest route, even > though it does that funky U-Turn. Say what?! I mean, honestly, if both > MapQuest Open & OSMR can do that left turn 'normally' without needing to > make a funky U-Turn, something has to be wrong in OSMAnd, right?? Sure, > there isn't a 'NO U-Turn' sign posted for this maneuver, but still, the > routing engine shouldn't be suggesting it since there isn't a 'NO Left > Turn' relation there preventing the left turn from McKnight SB to Siebert > EB. > > So, that leads me to my question. Does anybody think I've tagged the > intersection incorrectly? This is how I've been tagging intersections like > this from since the start, and I know most other US mappers have been doing > the same. Or should I start adding 'false' U-Turn restrictions to prevent > the routing bugs and then be called out as 'tagging for the router', or > even maybe start putting traffic light nodes at the stop lines for > intersections that have both roads divided (and just leave simple one-node > intersections as-is)? > > I'm very curious to see what others have to say about this to see how I'll > move forward when I map in the future. Also, don't hesitate to respond at > the Google Group post or the GitHub one too as I get the e-mail > notifications from them as well. > > -James > > > > [1] - (MapQuest routing, OSMAnd suggestion in [2] link) - > <https://www.openstreetmap.org/directions?engine=mapquest_car&route=40.53204%2C-80.01073%3B40.53002%2C-80.00614> > https://www.openstreetmap.org/directions?engine=mapquest_car&route=40.53204%2C-80.01073%3B40.53002%2C-80.00614 > [2] - https://groups.google.com/forum/#!topic/osmand/XJ-HVOHhKEM > [3] - https://github.com/osmandapp/Osmand/issues/1501 > > _______________________________________________ > Talk-us mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-us > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20150727/a04958ec/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us ------------------------------ End of Talk-us Digest, Vol 92, Issue 19 ***************************************
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
