cgeo
[Nightly] Long distance routing behaves erratic
Describe your problem!
When routing over a long distance (in my case >400 km), it takes way longer (than since the routing data got cached) to calculate the route (which may be the reason why half of the times I just got a straight line (timeout?)). But the mayor problem is that you sometimes can not get rid of the long route again ... and that it does not get recalculated resp. updated anymore (seems as if the cache is too persistent).
How to reproduce?
- Route to a target in a distance of about 400+ km
- Wait until the route will be shown on the map
- Follow the route for a while ...
Actual result after these steps?
- ... the route start will remain at the initial start point, i. e. although you proceeded on the route, the route line will not change anymore
- now try to change the routing target (i. e. select any cache on the map and route to it by using the icon in the bottom sheet)
- a recalculation will not happen (although the new target is shown in the header, neither routing line nor routing distance will change)
- try to clear the routing target (via click on the route button)
- the route line will disappear for a few seconds, but then it shows up again, either constant or flickering
- once this happens, there's no way to get rid of the (long) route anymore, other than killing c:geo
Expected result after these steps?
Routing should follow user's input
Reproducible
Yes
c:geo Version
2025.10.30
Additional Information
Video will follow (as soon as github allows the upload)
github seems to have an issue ... Unable to upload .mp4 However, then I'll try to send it zipped ...
In the video you see the already deactivated resp removed long route (see the bottom sheet, where's not possibility anymore to remove route target), then I tried to switch route target to a nearby cache (Das Schneckenhaus), but to no avail.
As currently internal routing is completely useless for long distance routing (>200 km), due to ...
- taking ages until a route is calculated, especially if you start routing while moving
- once a route is calculated/displayed, it constantly switches from routing line to bee line
- start point of the route is usually several hundred meters behind the current position
- sometimes c:geo manages to show a route, but after a while following it, c:geo crashes with OOME
... I switched back to external routing (via BRouter) - which is working perfectly fine.
And I would say, all this happens since routing data gets cached ...
And I would say, all this happens since routing data gets cached ...
In case you were referring to this entry in the changelog:
New: Route optimization caches calculated data
This is relevant for the "route optimization" function of individual routes only, it is not related to regular route calculation.
Route calculation routines have not changed throughout the last versions (AFAIK), therefore I'm wondering where this change in behavior comes from which you are observing.
