After navigation recalculation appears BRouter trying to use car profile by mistake

Andrew Heard shared this problem ago

Closed

I was testing the new Recalculate feature in 3.10.3 using a track created with BRouter and fastbike profile. After I tap Recalculate observe the messagebox below suggests BRouter is trying to use a car profile instead of fastbike profile because it mentions CD5 file version mismatch. Sure - these files are very likely not up to date, so I expect if I create a track with a car profile I may get a similar error, but I have never seen this error because I only use cycling profiles. Recalculate should use same profile as defined for the track. Track V1.1 GPX is attached if that helps.

eb67e85c7a988124c66e50bf398076f6

Otherwise the new 3.10 via point feature seems to be working well, at least with simulated GPS.

Files:

The same problem 0

Replies (1)

Menion ●

Hmm, how exactly was track created and exported? Created by BRouter, then you have used navigation and then you exported this track? Because in GPX file is no information about "type" used for compute. So I need to simulate your steps to get track without this information after export. Thanks!

URL

Andrew Heard ●

That was a quick response, thanks. The track was created with "Add new track", with BRouter, fastbike profile, no Compute Instructions, manual conversion of selected navpoints.

>Because in GPX file is no information about "type" used for compute

hmm, unusual based on what I just told you?

Just looking at another GPX backup, I guess you refer to locus:rteComputeType (example):

<trk>
<name>Channel Loop</name>
<extensions>
<gpx_style:line>
<gpx_style:color>#00FFD5</gpx_style:color>
<gpx_style:width>20.0</gpx_style:width>
</gpx_style:line>
<locus:rteComputeType>4</locus:rteComputeType>
</extensions>

But the original GPX I attached doesn't have this tag - I can't explain that either, sorry. And I guess when this tag is not found the default profile will be a car, and hence the error.

I have just created a similar track with same steps - attached. This time the tag is valid. However the bad news is that after I performed a test Recalculate every minor bend is again part of the navigation commands.

Files:

URL

Menion ●

"But the original GPX I attached doesn't have this tag - I can't explain that either, sorry. And I guess when this tag is not found the default profile will be a car, and hence the error." - exactly. If this parameter is missing, "car" is used. So what I need is a steps that leads to exported track with missing "rteComputetype" parameter, hmm.

"However the bad news is that after I performed a test Recalculate every minor bend is again part of the navigation commands." - this is anyway already know different story: http://help.locusmap.eu/topic/reduce-battery-power-during-navigation-recalculation

URL