Snap to Route is still behaving terriblyFORUMS HOME SEARCH FORUMS

- There is the OsmAnd map web route planner. No experience with it.

- There is a  nice Cruiser desktop version. I share the gpx (nav)tracks designs between desktop and android via dropbox. Of course, as with any new app, you have to get used to using it optimally. The discrete gpx navigation track mode is an evolution of the Plotaroute gpx track + directions (in gpx waypoints) Locus map compatible export.

Hi Willy,

I hadn't heard of Cruiser_Brouter either, but after a quick search I realise you've spent a lot of time working on exactly this topic! And those instructions on a sensible route are what I was hoping for, and used to get, and hope to soon reliably get again, through Plotaroute.

I think you're right that in the first example I posted the one-way section is causing it some headaches, but it still makes no sense to add in 60 loops. It also has problems without one-way sections, as you can see in: https://www.plotaroute.com/route/2937761?units=km and https://www.plotaroute.com/route/2937762?units=km, where for some reason it triples the distance with an out-and-back detour. Essentially for the race I'm doing next week I broke the route down into 100km sections and tried snapping the first four - all four of them had significant errors. At that point I gave up, with still quite a few sections to go!

I might have a better look at OsmAnd and Cruiser/Cruiser Brouter to see if they can at least get me out of trouble for my coming race. Do you know if either are available as desktop apps?

Thanks,

Rowan

I'm just using the free plotaroute version. I suspect that one-way section is causing trouble. 

OsmAnd offers snap to street but I do not use the app. The results are not always flawless.

Inclusive turn instructions this delicate task is even more difficult.

Redesigning for such short distances is usually faster.

Through the Cruiser_Brouter (offline) gps app I tested this.

Convert this track with the max number of shaping points. 

Adjust where the result differs with the import overlay.

Especially check the locations where U-turns occur.

If desired, than remove the many shaping helper points.

Produce so a plug and play gpx navtrack inclusive TBT.

Import this file into Cruiser gps app press navigate and go.

Example demo file is temporarily available here.

https://send.tresorit.com/a#OKU1KxLj_Xf6nuXSZqJpYw

Hi Willy, 

Thank you for the information on OsmAnd, which I had not heard of. It looks like it has snapped the route as I would have hoped, so that is a good start. I would like to avoid having to do a lot of processing on all of my routes though. 

The premium membership of Plotaroute absolutely does offer a snap to nearest road tool - it is called "SNAP ROUTE TO MAP", and the way it used to work was that it snapped the route to the nearest road (within some configurable parameters) and generated directions as it did so. It worked quite well and the purpose is quite unambiguous. Unfortuntunately it has recently started performing very badly, as you can see from my linked examples.

I am very much hoping that Julien and the development team will be able to restore it to its former level of performance, perhaps even with an option to "unsnap" selected sections.

Plotaroute is a route planner which so follows the routing rules.

Plotaroute does not offer a simple snap to nearest road tool.

By the OsmAnd app snap to road feature you can enforce this anyway.

OsmAnd exports a gpx (trk) track plus gpx (rte) route (start- finish).

But OsmAnd also adds a rather complex OsmAnd gpx extension. 

By removing the excess obtain a simple “snapped to road” track.

Download test result here.

https://send.tresorit.com/a#vppL-CnH3dmKhFInFPyw2w

Hi,

I've answered via email this morning, but I also want to post here, so that others can follow this topic and know that we're looking into it:

This has been raised with the devs and I'll keep you updated on any development of the snap route to map feature that could prevent such crazy outcomes (such as snapping or unsapping only a section).

Best regards,

Julien

Just as some further information - the section where it is having problems is normally a one-way road (but not for the event I'll be doing). So I am happy if it finds an alternate route around that section (I can always fix it manually by hand). But 60 loops is just ridiculous. For those who don't have premium membership and can't see the outputs, here is the same route after using the Snap Route to Map feature: https://www.plotaroute.com/route/2935553?units=km

I raised this before but it seems to have disappeared from this list, so adding it back in. Snap to Route, a premium feature that I just paid more money to retain access to, continues to behave absolutely terribly. 

As an example, see this linked route: https://www.plotaroute.com/route/2935535?units=km

https://www.plotaroute.com/route/2935535?units=km

The original route is 26.199km with 538m of climbing - a reasonably straight section from one location to another. When I use the Snap to Route feature, the resulting snapped route is 155.961km long, and includes 3,028m of climbing, most of which happens during the approximately 60 times it loops around 6 or 7 different loops.

This really isn't good enough for a premium feature. I raised the issue several months ago now, by now you should have either fixed the snapping so it doesn't produce these crazy results, or at least given us an easy way to say "return only this portion to its unsnapped version".