New Topic

Locus Map - help desk Topic Idea Locus Map (Android)

Category Locus Map (Android)

Comments 8

Subscribers 6

Votes 8

Simplify track editing - show all points when track selected

Andrew Heard shared this idea ago

Gathering feedback

It is tedious to edit an existing track. In my test track below I added a single start and end point, with BRouter computing the track and intermediate points. Now if I want to alter the track I have to

A) tap the track

B) tap ">" button on label

C) tap "Edit on map"

D) tap left/ right arrows buttons to select point to move

E) tap Tool button

F) tap "Edit location"

G1) drag one of three green points to new location (see screen cap below)

G2) or long tap on a green point then tap Delete

e5b758304874eb63c505fc3a7c5c1715

Would it be possible to simply display ALL points on the track as soon as selected? This would include displaying all computed points. This would eliminate many taps.

At present this idea has limited use if a point is moved far away until the Rubberbanding feature is also implemented. I note that topic has 37 votes.

I like this idea 0

Replies (2)

Ingo Rau ●

This also bothers me, especially as I can't be a technical problem: When creating a new route, it's obviously possible to have all points editable at once (including the in-between red dots that can be moved to create new points).

And I wouldn't say this has "limited use" - when editing recorded tracks, you don't need any rubberbanding, but this would make life a lot easier still...

Reply URL

Andrew Heard ●

>you don't need any rubberbanding

@Ingo - useful if modifying recorded track for use as a new track if the changes are anything more than trivial

If I modify any track at present, add a point that is "far away", the new parts of the track are only straight lines "point to point" rather than following an existing road i.e. the Compute Source is not used. Why does the Compute Source get used during initial track creation, but not during subsequent track editing? Forcing an existing track through a different town (for example) is useless at present because of this limitation. OsmAnd 2.x mentions it is possible to add waypoints into an existing track and have the track properly recalculated, but I haven't figured out how. It also suggests a track waypoint can be dragged to another location with recalculation but again I haven't figured out how. It can also optimize the itinerary (track waypoints) (traveling salesman algorithm), and this does actually work well.

URL

Ingo Rau ●

Sorry, I didn't mean to deny the usefulness of rubberbanding. After all, I fully support your idea ;)

Just for recorded tracks, I see less use, I mainly correct GPS outliers there. Rarely useful to "snap" the track to existing roads. After all, I recorded where I went, not where there are roads ;) *

But anyway, we want the same thing, I just wanted to point out that your sentence "At present this idea has limited use" was wrong and it may look to others that this idea is not so important right now.

* Also, I often hike in the mountains (Switzerland). A lot of the trails there are on the SwissTopo maps, but not in OSM. So I can correct my tracks manually, but recalculation is useless.

URL

Ingo Rau ●

Would like to bump this up again.

Menion, could you please comment on this? More precisely: What is the reason that in "creation" mode I can move any point at the same time, while in "edit" mode only ever three? This makes editing so tedious, whereas creating is a breeze. And it doesn't seem to be a technical issue, because the "edit all" functionality exists. So I wonder why it's not possible?

Reply URL

Menion ●

Hello, main reason why I limited this to three points only was to a) prevent some incorrect calculations for interpolated points, b) performance issues because this editing is quite slow mainly when saving results.

Anyway agree that we may at least try to extend it from nearest three points, to wider range. I'll try to enable it to next Beta version to more points around ..

URL

Ingo Rau ●

I can imagine that for really big tracks it may be a performance problem - so I appreciate some compromise like that! Thx!

URL

Andrew Heard ●

Clearly much interest with the original Rubberbanding feature (5 years ago) 45 votes & subsequent still open topic (3 years ago) 36 votes - in the "top 10" topics.

URL

Ingo Rau ●

Just realized, editing more points at once is already "live" in current version. Thx Menion, that's a big improvement. I still think the option to have everything editable at once would be nice, but I understand the technical side and can perfectly fine live with this compromise.

URL