Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue? Brian
On 16/11/2014 02:49, Brian Egge wrote:
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue?
When creating a map for the car, I _do_ remove stuff I don't want it to think about navigating over (footways, paths, tracks without appropriate access) from the .osm file that gets fed to mkgmap. The idea is not just to fix the problem that you're seeing, but also to just reduce data to speed up route creation. Cheers, Andy
Remove the footways tagged with footway=sidewalk. ( http://wiki.openstreetmap.org/wiki/Tag:footway%3Dsidewalk) Furthermore it might be beneficial for data quality when creators of these footways always use footway=sidewalk when applicable 2014-11-16 3:49 GMT+01:00 Brian Egge <brianegge@gmail.com>:
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue?
Brian
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
You don't have to remove your sidewalks , just make them non routable, ie give them an extended type number -- View this message in context: http://gis.19327.n5.nabble.com/Driving-on-Trail-tp5824491p5824532.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Brian, I never saw this text on my Oregon. If I got you right, you have two routable lines for the same OSM way, the device routes you over the way for the car, but it displays the info for the sidewalk. Could this be the reason? Gerd Brian Egge wrote
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue?
Brian
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Driving-on-Trail-tp5824491p5824534.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
GerdP wrote
Hi Brian,
I never saw this text on my Oregon. If I got you right, you have two routable lines for the same OSM way, the device routes you over the way for the car, but it displays the info for the sidewalk. Could this be the reason?
Gerd
Hi Gerd, i can second this behavior on my etrex Vista. The unit definitely routes on the sideway/bicycle-way and on the next crossing it tries to route onto the main road. I don't get it, how it "thinks", i am on the sideway, when there *is* a road and it is in car mode. :? I will try to filter "unwanted" data out of the dataset with osmfilter. Declaring the sideways not routeable would render the "route for pedestrians"-mode useless, i think? Uli -- View this message in context: http://gis.19327.n5.nabble.com/Driving-on-Trail-tp5824491p5824566.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Uli, I would understand this when the style adds two routable ways for the same OSM way. Garmin maps don't use this trick, so I would not be surprised to see that they can't handle it properly. We already noticed that with the cycleways added by the --make-opposite-cycleways option. Gerd
Date: Mon, 17 Nov 2014 01:28:23 -0700 From: ulibaer@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Driving on Trail
GerdP wrote
Hi Brian,
I never saw this text on my Oregon. If I got you right, you have two routable lines for the same OSM way, the device routes you over the way for the car, but it displays the info for the sidewalk. Could this be the reason?
Gerd
Hi Gerd,
i can second this behavior on my etrex Vista. The unit definitely routes on the sideway/bicycle-way and on the next crossing it tries to route onto the main road. I don't get it, how it "thinks", i am on the sideway, when there *is* a road and it is in car mode. :?
I will try to filter "unwanted" data out of the dataset with osmfilter.
Declaring the sideways not routeable would render the "route for pedestrians"-mode useless, i think?
Uli
-- View this message in context: http://gis.19327.n5.nabble.com/Driving-on-Trail-tp5824491p5824566.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, Here's an example area: http://www.openstreetmap.org/way/305805056#map=19/41.27951/-73.49803 The sidewalks are generally parallel to the road, but are sometimes set back quite a way, as is the case on Main Street. The planned route won't send me onto a sidewalk, but if I'm driving without a route set, it will try to place me onto the nearest street. I thought the following rule would disallow this when not in pedestrian mode: highway=footway|highway=path|highway=steps [0x16 road_class=0 road_speed=0 resolution 23] I haven't tried putting the nuvi into pedestrian mode, but I'm assuming it would try to route you on these types of roads. Brian On Sun Nov 16 2014 at 2:59:56 PM GerdP <gpetermann_muenchen@hotmail.com> wrote:
Hi Brian,
I never saw this text on my Oregon. If I got you right, you have two routable lines for the same OSM way, the device routes you over the way for the car, but it displays the info for the sidewalk. Could this be the reason?
Gerd
Brian Egge wrote
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue?
Brian
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble. com/Driving-on-Trail-tp5824491p5824534.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 16.11.2014 03:49, schrieb Brian Egge:
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mode, which it is. I can't figure out anyway to have it ignore pedestrian routes, short of removing them from the map. Any suggestions on how to fix this issue?
Hi, this is because of how the Garmin Routing algorithm works. Depending on the current GPS position (which is not always exact) the next routable line is taken. Even if this is blocked for motorcar. You can fix this by making sideways non routable. But then it's no longer working for pedestrian routing. Chris
In your letter dated Mon, 17 Nov 2014 12:48:54 +0100 you wrote:
Depending on the current GPS position (which is not always exact) the next routable line is taken. Even if this is blocked for motorcar.
You can fix this by making sideways non routable. But then it's no longer working for pedestrian routing.
I started doing the same thing after I got really stuck in the country side when my 62s tried to have me drive over a narrow trail. (Didn't get physically stuck, just had no clue how to get where I wanted to be) I'm already generating separate maps for driving and cycling, but I'll have to add walking as well :-(
participants (9)
-
Brian Egge -
chris66 -
Gerd Petermann -
GerdP
-
Johan C -
nwillink -
Philip Homburg -
SomeoneElse -
UliBaer