Route planner freezing - App crashing without being able to save

Gabriele Tampucci shared this problem 21 days ago
In Progress

Hello everyone.

As the title states I'm currently unable to plan my upcoming trek because the second part of it goes over what, for the Italian institutions, is a closed Via Ferrata. To be able and trace all the route correctly I have to manually trace over the previous Via Ferrata route (that is still on the map, i just cannot tell the app to use it with Walking/Hiking calculation) but when i do that i get over 100 shaping points and the app starts to go laggy, after a while it freezes and crashes.

I also tried to trace the route manually via Web-App but as a result I get that all the shaping points placed via web-app are at 0 altitude and invalidates my planning.

If it could be possible, in some way, to let the map calculate the route without need to manually tracing it?


If it can be useful, i leave here some useful insight regards the actual route.

I'm trying to connect the spring at N 44° 06.751', E 010° 12.036' to the "K2" bivouac at N 44° 07.256', E 010° 12.201' passing through "Ferrata del Monte Contrario".


My route is https://link.locusmap.app/t/dwvvdb

Replies (1)

photo
1

Hi Gabriele,

I didn't simulate any crash when adding manual shaping points in the app, so I drew the route along the ferrata for you:

This comment is in trash! Restore
photo
1

Hi Michael! thank you for the response, later I'm gonna try and import that route that you drew.

I also want to try and record my screen while the route planner makes the app crash, would that be useful?

Also, if u could answer a question: It is currently not possible to make the app calculate the route between the spring at N 44° 06.751', E 010° 12.036' and the "K2" bivouac at N 44° 07.256', E 010° 12.201' passing through "Ferrata del Monte Contrario" with hiking profile?

Thank you again and in advance :)

This comment is in trash! Restore
photo
1

Sorry if I make another reply, do you think that the web-app shaping points with 0 altitude is a matter that requires opening a separate ticket?

I've seen you didn't touch that in the reply...

This comment is in trash! Restore
photo
1

Screen recording won't help much; better to send your user ID and /or system bug report created after the crash (more at https://docs.locusmap.app/doku.php?id=manual:faq:issue_reporting).

As for the missing elevation data on the web, that is a known issue - so far, we haven't solved the elevation data source and updating, which is why only calculated routes contain elevation data which are taken from the router.

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!