Messages

OK, thx, I'll check at BRouter. On OSM I've checked some random tunnels and bridges and most of them did have correct info, but of course not all of them. But there, as OSM users, we can help to enrich the data where we find it is incomplete...

Is the OSM 'maxheight' information also included in the LoMaps?

Hi,

I've been trying to start making a custom routing profile but I can't get it to work. Followed the online instruction but I'm not sure if that is still valid after the changes in directory access by Android/Google. I created /Locus/router/profile2, but .brf files (copies from BRouter repository) are not detected.

Is there an up to date step-by-step instruction for making custom routing profiles?

Thx,
Mike

Hi, I've been searching for the option to take vehicle height, width and weight in consideration in the route planning. So far I've only seen this in two other apps (CoPilot and MyRouteApp). I've not found if this is an option in Locusmap.
Would this be possible?
Mike

[Thanks LocusMap developers, this is really cool!]

Hi, when I have a route calculated on the Locusmap planner website, selecting the car-eco profile the total travel time is about 16hrs, when I calculate the same route in the android app, the travel time is about 33hrs, although the used profile and given distance is the same. What am I doing wrong? I'm using an up-to-date android version of LocusMap and updated Brouter data.

Oops, this might as wel be a duplication of https://forum.locusmap.eu/index.php?topic=8924.0. Excuse...

Oops 2: it seems that in LocusMap 4.24.2 the bug seems to be solved, toghether with a lot of improvements to the routing options (like custom routing profiles).
Thanks LocusMap developers, this is really cool!

Hi, when I have a route calculated on the Locusmap planner website, selecting the car-eco profile the total travel time is about 16hrs, when I calculate the same route in the android app, the travel time is about 33hrs, although the used profile and given distance is the same. What am I doing wrong? I'm using an up-to-date android version of LocusMap and updated Brouter data.

Oops, this might as wel be a duplication of https://forum.locusmap.eu/index.php?topic=8924.0. Excuse...

Hi, when I have a route calculated on the Locusmap planner website, selecting the car-eco profile the total travel time is about 16hrs, when I calculate the same route in the android app, the travel time is about 33hrs, although the used profile and given distance is the same. What am I doing wrong? I'm using an up-to-date android version of LocusMap and updated Brouter data.

Yep the most ideal situation would be if the entire track would be recorded with state of the art equipment.

However in this case a part of the track was not recorded at all and was added manually after the track was completed. I also realize that modifying elevation by hand can be an enormous job, especially if the recording trackpoints is dense. For now I'll go for the option to split the track, correct the part which is not correct (using update elevation) and join the tracks together again after the correction. Hopefully at the joining points the difference between the actually measured heights and the heights from the Locus Height map is acceptable.

Thanks for all your help.

"Edit on map" -> "Remove gap".

Thanks, did not know that this was meant to remove such a gap, as the track still appears as a single track. It works perfectly!

@ insomniux: You could try to split the original track, so that the section you want to change is a separate short track. Then make the changes for that one and update the elevation information. Then merge the track parts again (in the correct order:-). The unchanged track parts should then keep the GPS elevation info.

That's a good suggestion @Graf Geo, I'll give it a try. I'm however still a bit concerned about the points where the different parts of the track connect after correcting the height data. There may be some jumps which may need manual correction. I've still not figured out how that can be done.

I think you have incorrect offline altitude data.
The best are the lidars from Sony.

The altitude data before 3KM and after 4KM is correct. Between those two points the altitude is calculated by the LocusMap app, as those points are manually added (in the app). So my question does not concern the registration of altitude by any device but if there is a possibility (in the app or on the website) to manually correct the altitude of certain points (in this case the calculated points).

Excuse, the example may not be fully clear but does show the approximation which is applied by the Refresh Elevation tool. Here is another graph where I had to change part of the track. Here is the height information lost after editing. Between 3 and 4km there is a straight line, whereas in reality there should have been a peak up to 560m.

You cannot view this attachment.

While manually modifying track points, especially while adding points, the height information of the point seems to be calculated (or ignored). After updating the height information (using the 'Tools/Refresh Elevation'), a good approximation of the elevation is applied to the entire track, but a lot of detail, collected by the GPS, is lost.
Would there be a way to apply the 'Refresh Elevation' tool to just a part of the track, or is there a way to adjust the elevation information of selected point of the track?

Raw data from GPS:
You cannot view this attachment.

After applying the Refresh Elevation tool:
You cannot view this attachment.

The trackline which is shown on the map, at certain points, show a gap (interruption of the line). I cannot get rid of this gap by editing (remove the points at the location of the gap). Is there a way to let the lines join?

You cannot view this attachment.