Route Calculation Error and Ferries

Hi I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads. I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc) If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn" This ferry works: https://www.openstreetmap.org/way/3533551 These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415 Any thoughts Ticker

Using GPSMapEdit to look at the coordinates of the first point in the ferry way, the one that worked has the points in the direction of travel, and the one that didn't has them the other way around (but neither is marked one-way) Ticker On Mon, 2018-03-12 at 15:31 +0000, Ticker Berkin wrote:
Hi
I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads.
I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc)
If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn"
This ferry works: https://www.openstreetmap.org/way/3533551
These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415
Any thoughts
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Ticker, the direction should not matter. What vehicle do you use for routing? The one that works has no toll=yes tag. Maybe your style does something special with toll=*? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 16:46:02 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries Using GPSMapEdit to look at the coordinates of the first point in the ferry way, the one that worked has the points in the direction of travel, and the one that didn't has them the other way around (but neither is marked one-way) Ticker On Mon, 2018-03-12 at 15:31 +0000, Ticker Berkin wrote:
Hi
I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads.
I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc)
If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn"
This ferry works: https://www.openstreetmap.org/way/3533551
These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415
Any thoughts
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd I've tried navigating as both Pedestrian and as Car/Motorcycle. The Island (Isle of Wight) I'm trying to route to has 3 car ferries and 1 foot ferry. All the ferries I'm trying have are set as toll (my style sets this for ferries unless they explicitly have tag toll=no). GPSMapEdit shows toll, along with no-one-way. I allow "toll" in the device routing options. I only mentioned the order of points because the device requests a u -turn at the via point. I don't think point order is the problem because creating a device-route back along the same ferry doesn't work either. The one ferry I've found that does work leaves from the same jetty as a failing one, but doesn't go to the island - ie it's destination can be navigated to via the road/trail network without a ferry journey. Ticker On Mon, 2018-03-12 at 16:42 +0000, Gerd Petermann wrote:
Hi Ticker,
the direction should not matter. What vehicle do you use for routing? The one that works has no toll=yes tag. Maybe your style does something special with toll=*?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 16:46:02 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries
Using GPSMapEdit to look at the coordinates of the first point in the ferry way, the one that worked has the points in the direction of travel, and the one that didn't has them the other way around (but neither is marked one-way)
Ticker
On Mon, 2018-03-12 at 15:31 +0000, Ticker Berkin wrote:
Hi
I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads.
I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc)
If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn"
This ferry works: https://www.openstreetmap.org/way/3533551
These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415
Any thoughts
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Ticker, do you see the same problems in Mapsource or Basecamp? If yes, I can try to find a reason. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 18:30:31 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries Hi Gerd I've tried navigating as both Pedestrian and as Car/Motorcycle. The Island (Isle of Wight) I'm trying to route to has 3 car ferries and 1 foot ferry. All the ferries I'm trying have are set as toll (my style sets this for ferries unless they explicitly have tag toll=no). GPSMapEdit shows toll, along with no-one-way. I allow "toll" in the device routing options. I only mentioned the order of points because the device requests a u -turn at the via point. I don't think point order is the problem because creating a device-route back along the same ferry doesn't work either. The one ferry I've found that does work leaves from the same jetty as a failing one, but doesn't go to the island - ie it's destination can be navigated to via the road/trail network without a ferry journey. Ticker On Mon, 2018-03-12 at 16:42 +0000, Gerd Petermann wrote:
Hi Ticker,
the direction should not matter. What vehicle do you use for routing? The one that works has no toll=yes tag. Maybe your style does something special with toll=*?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 16:46:02 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries
Using GPSMapEdit to look at the coordinates of the first point in the ferry way, the one that worked has the points in the direction of travel, and the one that didn't has them the other way around (but neither is marked one-way)
Ticker
On Mon, 2018-03-12 at 15:31 +0000, Ticker Berkin wrote:
Hi
I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads.
I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc)
If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn"
This ferry works: https://www.openstreetmap.org/way/3533551
These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415
Any thoughts
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd I don't have either of these installed anywhere at the moment - I'll download Basecamp and see how it behaves. Ticker On Mon, 2018-03-12 at 17:40 +0000, Gerd Petermann wrote:
Hi Ticker,
do you see the same problems in Mapsource or Basecamp? If yes, I can try to find a reason.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 18:30:31 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries
Hi Gerd
I've tried navigating as both Pedestrian and as Car/Motorcycle. The Island (Isle of Wight) I'm trying to route to has 3 car ferries and 1 foot ferry.
All the ferries I'm trying have are set as toll (my style sets this for ferries unless they explicitly have tag toll=no). GPSMapEdit shows toll, along with no-one-way. I allow "toll" in the device routing options.
I only mentioned the order of points because the device requests a u -turn at the via point. I don't think point order is the problem because creating a device-route back along the same ferry doesn't work either.
The one ferry I've found that does work leaves from the same jetty as a failing one, but doesn't go to the island - ie it's destination can be navigated to via the road/trail network without a ferry journey.
Ticker
On Mon, 2018-03-12 at 16:42 +0000, Gerd Petermann wrote:
Hi Ticker,
the direction should not matter. What vehicle do you use for routing? The one that works has no toll=yes tag. Maybe your style does something special with toll=*?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 12. März 2018 16:46:02 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries
Using GPSMapEdit to look at the coordinates of the first point in the ferry way, the one that worked has the points in the direction of travel, and the one that didn't has them the other way around (but neither is marked one-way)
Ticker
On Mon, 2018-03-12 at 15:31 +0000, Ticker Berkin wrote:
Hi
I almost always get "Route Calculation Error" on my Garmin when a ferry crossing is required. GPSMapEdit "Tools > Test Routing Graph" does find the routes and it shows reasonable properties for the ferries, walkways and relevant roads.
I'm testing it with a mix of foot and car ferries. In the routing options, all "Avoids" are turned off (ie allow tolls, unpaved, etc)
If I create a "Route" on the device, with a "Via Point" on the ferry line, and then navigate this route, it works, except immediately after the "via point" it gives the instruction is "Make a U-turn"
This ferry works: https://www.openstreetmap.org/way/3533551
These don't: https://www.openstreetmap.org/way/614416 https://www.openstreetmap.org/way/614415
Any thoughts
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Ticker, all these ferries are used for routes in BaseCamp. 2 of them only for pedestrian routes. -- Best regards, Andrzej

Hi Using Basecamp 4.6.2 and the gmapsupp.img from my Garmin Etrex, after turning off the relevant "Avoid"s from profiles: It will generate "Walking" routes using various ferries to the I.O.W: https://www.openstreetmap.org/way/614416 Sotn.-W Cowes foot https://www.openstreetmap.org/way/614415 Sotn.-E Cowes vehicle https://www.openstreetmap.org/way/368066 Yarmouth-Lymington vehicle https://www.openstreetmap.org/way/1886910 Fishbourne-Portsmouth vehicle and a couple of others to from Portsmouth/Southsea to Ryde, IOW and (not IOW): https://www.openstreetmap.org/way/353355 Sotn.-Hythe foot The Etrex itself gives "Route Calculation Error" when asked to route as a pedestrian to the IOW from the mainland. Basecamp will generate a "Driving" route using: https://www.openstreetmap.org/way/614415 Sotn.-E Cowes vehicle as long as the start and/or end points are only a few streets away from the ferry termini (but outside the ferry port, on public streets). I haven't yet determined the point at which it fails. It won't generate a route (ie. just gives a straight line) using: https://www.openstreetmap.org/way/368066 Yarmouth-Lymington vehicle https://www.openstreetmap.org/way/1886910 Fishbourne-Portsmouth vehicle if starting/ending just outside the ferry ports, but looking at these on OSM, some of the required service roads are marked as access=destination, which triggers mkgmap:throughroute=no So, Basecamp demonstrates some problems I get in the Etrex, and it seems to be related to vehicle routing and distances between the end of the ferry and the start/destination. It doesn't demonstrate the Etrex problems with Pedestrian routing, but the examples I have that work on the Etrex are all short ferry crossings on the same linked road network. Ticker On Mon, 2018-03-12 at 21:10 +0100, Andrzej Popowski wrote:
Hi Ticker,
all these ferries are used for routes in BaseCamp. 2 of them only for pedestrian routes.

Hi Ticker,
as long as the start and/or end points are only a few streets away from the ferry termini
This could be because of service roads leading to a ferry. That kind of roads are the last resort for a route and usually at the endpoint only. They are probably ignored, when calculating longer route for a car. -- Best regards, Andrzej

Hi Andrzej No - I checked all of this. A couple of ferries wouldn't route to/from the public highway network because of this (access=destination), but one didn't have this tagging on its service roads and Basecamp would route using the ferry as long as the start and end points (on public roads) were close to the ferry terminals, but trying to start/end further away, still on connected public roads, it wouldn't route. Ticker On Tue, 2018-03-13 at 14:11 +0100, Andrzej Popowski wrote:
Hi Ticker,
as long as the start and/or end points are only a few streets away from the ferry termini
This could be because of service roads leading to a ferry. That kind of roads are the last resort for a route and usually at the endpoint only. They are probably ignored, when calculating longer route for a car.

Hi Ticker, I think what Andrzej wants to point out is that Garmins routing algo is quite special. When looking for a possible route it tries to reach a road with a high class. Once this is found it will ignore roads with lower class if this is the only connection to the ferry (which also should be a high class, default style uses 3). I think this search is done from start and target. So, if a class=3 road takes you close to the ferry terminal but not onto the ferry you might see these problems when your route includes the class=3 road. I wonder if this also happens for pedestrian routing, but for cars I've often seen that. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <ticker@jagIT.co.uk> Gesendet: Dienstag, 13. März 2018 15:09:50 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries Hi Andrzej No - I checked all of this. A couple of ferries wouldn't route to/from the public highway network because of this (access=destination), but one didn't have this tagging on its service roads and Basecamp would route using the ferry as long as the start and end points (on public roads) were close to the ferry terminals, but trying to start/end further away, still on connected public roads, it wouldn't route. Ticker On Tue, 2018-03-13 at 14:11 +0100, Andrzej Popowski wrote:
Hi Ticker,
as long as the start and/or end points are only a few streets away from the ferry termini
This could be because of service roads leading to a ferry. That kind of roads are the last resort for a route and usually at the endpoint only. They are probably ignored, when calculating longer route for a car.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd, Andrzej I've done a bit more experimenting with Basecamp. Starting from a fixed point on a main roundabout on the mainland, I've been creating routes to a Primary road on the Island, working along this road until it fails to use the ferry and resorts to a straight line. Using GPSMapEdit to look at the road segments, positions of routing nodes and other properties, it appears to work on one side of a routing node but not the other on a single line segment. Ticker On Tue, 2018-03-13 at 14:46 +0000, Gerd Petermann wrote:
Hi Ticker,
I think what Andrzej wants to point out is that Garmins routing algo is quite special. When looking for a possible route it tries to reach a road with a high class. Once this is found it will ignore roads with lower class if this is the only connection to the ferry (which also should be a high class, default style uses 3). I think this search is done from start and target. So, if a class=3 road takes you close to the ferry terminal but not onto the ferry you might see these problems when your route includes the class=3 road. I wonder if this also happens for pedestrian routing, but for cars I've often seen that.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <ticker@jagIT.co.uk> Gesendet: Dienstag, 13. März 2018 15:09:50 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Route Calculation Error and Ferries
Hi Andrzej
No - I checked all of this. A couple of ferries wouldn't route to/from the public highway network because of this (access=destination), but one didn't have this tagging on its service roads and Basecamp would route using the ferry as long as the start and end points (on public roads) were close to the ferry terminals, but trying to start/end further away, still on connected public roads, it wouldn't route.
Ticker
On Tue, 2018-03-13 at 14:11 +0100, Andrzej Popowski wrote:
Hi Ticker,
as long as the start and/or end points are only a few streets away from the ferry termini
This could be because of service roads leading to a ferry. That kind of roads are the last resort for a route and usually at the endpoint only. They are probably ignored, when calculating longer route for a car.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Andrzej Popowski
-
Gerd Petermann
-
Ticker Berkin
-
Ticker Berkin