I`d love to see a "rubber band" route planning same way than google maps has,
just grab the route from any point and move it, release it and vóila, it has been moved to a different road.
possibly in combination with...
Yeah, I like that functionality in Google Maps. Very convenient.
may I ask you what is missing in Locus about this feature? Because when you use "add new route" feature, this is already implemented there.
At the time I voted for the idea, Locus had no nice grab & drag function or I was not aware of it. What's missing in current implementation?
Hello GeorgD, thanks for your feedback.
I think anyway, that it's not precise.
Add new route & measure feature has nice button no.5 ( check manual http://docs.locusmap.eu/doku.php?id=manual:functions:add_new_route_measure ), which allows to enable compute of navigation during moving a track. It also recompute track in (I hope) very nice when even when you move some middle points.
Suggestions for possible! UX improvements are always welcome, so if you have anything that may helps you, it's welcome.
I would like to change a navigation route to navigate an alternative route without traffic jam. The handling should be not too complicated, because of using it in stop and go traffic. A new calculation via a rubberband feature to a street beside the jam would be great.
Rubber banding is a great idea if (a) the new route picks up navigation instructions and (b) it can be usable on a cell phone with its relatively small screen.
I tried to use the rubber banding feature of the website ridewithgps while cycling and could not manage. It was impossible for me to click with my finger on the route in order to drag it. I constantly either moved the map sideways on the screen instead of the route or I added a new point to the existing route where I pointed. Very frustrating.
@1: Exactly that was what I meant, rubber band is made for track creation, i.e. it is not offered for modification of a route while already navigating (started menu > more > navigate to). As a standard user, would you start navigation via "navigate to" or via "add new route & measure"? ;-) As I told, nothing relevant for me.
@2: UX enhancements. Difficult to tell & explain, what is hard, what shall be changed in which way. The only I can really explain and causes a lot of stumbling is the context menu handling.
For red points, we could disable context menu completely so the red points have exactly one function, to add a new point. I believe "delete" is not really required for a nonexisting point ;-) Another story with "edit". Usually, I do not need to place a point to "map center" or "coordinates" the like, so in the seldom cae I do have to, I could use red points to create a new point at arbitrary position, then tap the new green point and call edit on it.
BTW, that's a general problem of nearly all android apps: You simply don't see and can't look up which taps, gestures etc will cause what action. And every app has it's own interaction patters. IMHO, on request, a platform function shall visualize all currently registered event handlers (or however they're called) so it works identical across all apps.
Oh, and: If you've 5 green points, move the cross over one of the middle ones and press minus icon. Not the "selected" one (=hovered above) is deleted but the end one. But: For plus icon, the cross is used - so interaction patterns appear a little inconsistent despite they're perfectly logical.
I have read thru this & the linked topic & can't figure out how to move an existing green point within a track. It shouldn't be that hard. It's easy & intuitive using Google Maps or RideWithGps (for example) to move a track point.
Hi Georg - thanks for the suggestion. Unfortunately for me when I tap & hold on any green point I get a small pop up window saying "loading" then a little while later another window with information found in the database around the point found. I've tried many times to be accurate to tap exactly on the green point, but always the same behavior.
In fact it's the same behavior as if there is no route/ track & I just tap anywhere on the map, that is not on a green route point. I get the "loading" window, then details found at that point.
From reading through this topic, I think the current requirement is implemented, but it is a little unintuitive as you can't edit tracks once you hit save. After saving, clicking on any point on a track just brings up information about this point.
This is covered by a different idea:
Alan - this topic issue isn't yet implemented - moving an existing track point to another location simply results in two straight lines between three existing points. This is not the behavior of Google maps or other online track planning websites. I think that was suopo's main idea?
BTW there is an alternative method of creating a track you may find of interest here which I think works better over longer distances, similar to your comments in the other topic. A couple of other related topics here and here.
Sorry for my misunderstanding. I'd interpreted "rubber banding" to be what Google refers to as "draggable directions" as implemented in the "Add new route and measure" UI on Locus. This style of grabbing an existing route point (or one of the intermediate points) and moving it causes Locus to recalculate directions between the various points (and therefore not produce straight lines). The behaviour I thought this topic was referring to is shown in this (rather poor quality, sorry) video:
I guess my understanding of the topic is wrong, so I apologise. What was the behaviour that is being looked for here?
You're understanding may be entirely correct, and mine wrong. I shouldn't have sounded so sure of what the original writer had in mind. He wrote it 3 years ago and a huge amount has improved in that time. But the topic is still flagged as "collecting votes". Certainly track creation as shown in your video supports rubberbanding, but any subsequent track editing (and what I had in mind without being explicit) only supports straight lines between points i.e. the Compute Source is not invoked to "fill in" the intermediate track points. See this other new topic on improving track editing.
Yes: this was the reason for my comment. My understanding of this topic was that it was about dragging routes around (which is implemented); the other topic that I linked is about being able to do it after you've saved the route (which isn't). The other new topic you mentioned is also more relevant (although arguably rather similar to the one about editing after saving).
Still, it's nice to know that lots of people want this! Let's just hope the votes don't get spread across too many issues so that one of them gets implemented!
Hello guys, thank you for a nice discussion.
"Nice" mainly because I have quite similar thought as Alan here http://help.locusmap.eu/topic/rubberband_route_planning#comment-18396
So I have to ask: isn't this idea already implemented?
I'm aware there are alternative topis, but main idea was ability to allow "Google like" planning of tracks. Do not know what Google do, but expect similar system to "Add new route" function in Locus.
It is almost "Google like", but in Google you can click the little cog icon, click "Share or embed map" and that effectively saves it as e.g. https://goo.gl/maps/BFPDS. You can then go back and edit it after saving it.
I'm fairly sure this specific topic is implemented, but my concern would be that all those 41 votes were from people who thought it was also referring to editing routes after saving and didn't think it was worth voting again for one of the other issues!
Based on previous discussion,
Thanks for understanding and enjoy finally coming summer ;).
Comments have been locked on this page!