This object is in archive! 

Allow routing service during track edit

Bucky Kid shared this idea 8 years ago
Declined

Hello, I find it more powerful if routing (navigating) service could be (optionally) in effect also during track edit, especially when adding new points inside track. The reason is that sometimes a more extensive part of track has to be changed, in this case user must delineate whole part point by point. Because Locus always knows context of added points, it wouldn't be hard to apply routing to new (and possibly edited) waypoints so track segments always lead through registered paths.

Replies (8)

photo
1

This sounds very similar to RubberBand route planning?

photo
1

You are right, the idea seems be same, but the name was a bit misleading for me (not everybody could imagine the principe of rubberband feature ;) )

photo
1

And you are right, your topic name is a far better description of the proposed idea. I observe the routing service works during recalculation, the proposals would appear to be a generalization of that existing function.

photo
1

Hello guys,


may you give me some more information about this idea? Please read before my last answer here http://help.locusmap.eu/topic/rubberband_route_planning#comment-18459 and say me if my answer cover also this topic (so it may be closed) or if I miss something here and some extra work needs to be done. Thanks

photo
1

Hello menion, the idea in http://help.locusmap.eu/topic/edit-a-route-after-saving-or-importing-it is supportive for this feature but doesn't cover the feature of routing service between 2 changed waypoints on saved track, so I think it's not the same, though the function of saving only manually added waypoints would be highly useful when editing saved track. But I agree, basically it's the same idea as rubberband, ie. recompute route between two changed or added points on saved track.

Together with "leave computed waypoints out from saved track" there's however one drawback, the track must be always recomputed when rendered/used which brings more CPU load and also if online routing provider is chosen to route the track the track usability will depend on online data, including complications with later track changes when routing provider is changed in global navi preferences. This problem may be solved by implementing of Quick routing profiles saved together with user-only wpts tracks, but I'm going too far :D

Since delete part of track is available, just adding routing on waypoints change I consider as sufficient and will ensure the track won't vary in future in dependence on routing service changes.

photo
1

Partially understand, thanks.


Anyway I still think it is quite similar, nearly same. At least from developer point of view. Both features require, that Locus pick a few existing waypoints, create from them "core" points (same as green dots during "Add new route") and allow to move with them and recompute route just between these waypoints, right?


If you don't mind, I'll close this topic and forward all people to mentioned topic, so votes won't be spread into two, very "similar" topics, possible?

photo
1

Yes I agree the idea is same as rubberband. I would suggest as best solution for future recomputing track between two changed points, save all waypoints including computed to track while flagging user defined waypoints with special attribute. When entering edit mode later, show only pass-through waypoints added by user, on two neighbour waypoints change recompute the track segment using current routing service while discarding previously computed waypoints between them. On changed track save store again all waypoints to ensure same track shape.

photo
1

Agree. In new beta version is already implemented new feature "via points", which has quite close to what you wants.


So topic closed. All who find it, please vote for already existing topic here: http://help.locusmap.eu/topic/edit-a-route-after-saving-or-importing-it , thank you for understanding.

Replies have been locked on this page!