Blat Maps. Help!

[mikecocker]

In order to do The Paul Marriott Memorial Blat last Saturday, I had to learn to use the MyRouteapp.

I thought I was doing ok until part way through the run when it all went wrong with blue lines in every direction. I had to follow other people and even at the finish it was telling me to do a u turn.

Next day I tried to understand what went wrong, and realised that the route on Blat Maps when transferred to the Navigator app on my Android wasn't the same, eg wp 13 and wp 16-17.

I then downloaded the Tomtom app and that transferred correctly. 

Any ideas if I'm doing something wrong?

Today I had a check of my mobile data usage and that one trip used 816 Mb. Could it use a lot of data continually trying to correct the route all day?

[AdrianC]

I am afraid I dont know about Android Navigator.

My Route-App Navigation works seamlessly with MRA. When you create a route on MRA it appears straight away on MRA Navigation. You can download maps so little data use.

You do have to purchase separately the Navigation app.

https://navigation.myrouteapp.com/en

[mikecocker]

Adrian,

That is the app I'm using on my Android phone.

If I go to Route Planning it changes wp 13 to a left turn instead of right. When I go to Navigation and Tracking it also changes wp 16-17 into a loop.

Maybe someone could try and see if they get the same result.

[mikecocker]

For reference here's the route in MRA

[AdrianC]

Has the route been uploaded to L7C Blatmaps?

Had a look and couldnt see it.

If I can get the route I can have a look at it as I have both MRA and MRA Navigation

[mikecocker]

This is it

https://www.myrouteapp.com/route/open/1298714?origin=library&partner=534&embed=true

 

[AdrianC]

Ok so I have had a look at the route, remembering that if you plan a route in MRA basic you are using Open Street Maps as the mapping algorithm. This will differ in some instances from a TomTom map alogorithim. If you purchase the Gold version you can plan routes in TomTom maps (or Garmin Here equivalent) which will always be faithfully replicated on a TT device or any software using TT maps. There is also a useful function to be able to compare the routes created on one map type with another so you can easily see the differences in the algorithms the mapping software uses.

It is important not to place waypoints near to junctions. In the case of WP 13 this in my view is far to close to the T junction and the actual GPS might easily think its a left turn here and hence you are taken to the west of Silverstone and not through the town.

This also applies to WP 17 which I can see again is right on a junction. When you arrive at WP 17 you need to turn right but in fact the nav device can easily see this as a left turn. So you are told to turn left and go through the WP and instead of then requiring a "U" turn takes you on a loop back towards 16. As you have now been through 17 the routing then looks for WP 18 and determines the fastest route to it, hence why you are directed though Charwelton and not Woodford Halse.

I dont think there is anything wrong with the software.What any nav device relies on is the accuracy of its actual GPS location and comparing it with the GPS co-ordinates of the next WP. To avoid these sorts of discrepancies keep WP's away from junctions, roundabouts and the like and allow the device a chance to navigate to the next WP.

Hopefully this explains the problems you encountered.