Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - zhaelon

#1
Quote from: menion on October 05, 2017, 22:09:15
Hello, thanks for a feedback.
I have to ask, why you would like to create via-points by moving shaping points closer to existing points? Why not to directly tap on existing point and add it to plan?

Google Places fix: thanks for testing and confirmation!

Hmm using both versions at once is really not recommended. It may lead to unexpected problems like these you wrote about. No simple solution on this, sorry.

Hope you had a nice time!

The reason is probably the way I plan motorcycle tours: I first construct the rough plan (start, POI, end) and then search for things to enhance the tour (interesting roads, landmarks,...) and modify the route accordingly. Then I search for specific POI along this route, for example a resting area, picnic places, restaurants, gas stations, etc and modify the route again.

And here I would like to just move a shaping point to an existing point,for example by moving the red dot (middle of a segment) to the via point. With the add option of the point, I would need to specify where to insert the point, which is not necessarily the beginning or end (or second last) point.

For the other problem: I just wanted to let you know that while both free and pro can be installed side by side, having a track recording active and accidentally opening the other version leads to both trying to record. I noticed only while beta testing and was surprised, that was all :-)

The motorcycle vacation was awesome and for me, Locus plays a huge part in it (planning, recording, etc). So I would like to thank you again for your efforts and hope that you still enjoy working on it!
#2
I noticed that when you add a point from the database, say Restaurant A to the track with the + button, it becomes a via point and uses the name as description. When you move the point, it is converted back to a shaping point. This is a good feature, as it makes planning and shaping easier.

Maybe I missed it, but I was looking for the remaining option: moving a shaping point on top of / near a point from the database could offer the conversion to a via point. That way, I could plan a route, search for a place along the route, then add a shaping point near the POI and move it to the search result and directly have a via point with the additional information :-)

The fix for the Google Places works like a charm. I haven't seen any wrong entries starting with the previous beta. Thanks a lot!

I noticed one more thing during my tests: I planned the routes using the beta version, stored them and then use the pro version as usual (because I added the widget, etc) for track recording. This leads to the following behavior: If you start recording on the pro version  and open the beta, suddenly both are recording. And both use different pause / recording state at least they indicate this.. Is there a way to lock recording to only one of the two instances? ;-)

Sadly my motorcycle vacation is almost over, so I won't be able to do a lot more testing.
#3
Hey everyone,

Please excuse me if I did miss already discussed points. I tried to read the threads but may have skipped over some parts.

I would like to comment on the new route planner, as I make heavy use on the old one (about 30k miles planned with it) and just tested it during the last 2 days for our motorcycle vacation (still almost 1 week left).

First off, I really like the new design and it adds a lot of flexibility.

Please add me to those hoping that the meta data about the current routing profile is stored on a per point basis and that a recompute function is added using this information. I also have to switch profiles a lot and just by dragging a point (for example on a small byroad) the current profile is applied, which is usually the wrong one messing up a previously good route ;-)

What I am currently unable to do (maybe I missed it, as I only tried it a few times):


  • Search for Google Places from within the planner (I can search for addresses, though this seems not intuitive) - I use this a lot to search for Hotels / Restaurants / etc while planning
  • Add a search result (address /Google Places)  to the database
  • Show currently hidden points from the database (access track/POI menu)
  • Switch maps from within the planner (access map menu)
  • Switch vector map theme from within the planner
  • Display the direct line between the points in addition to the routed path (was removed in some version between 2015 and now) - which was really useful as an overview for long distance planning
  • Read out the distance from route begin to a definition/whatever point (tool tip shows distance from GPS, which is meaningless for my plans)

That said, the route planner makes planning our motorcycle trips easier (allowing to better insert points in between) but makes it a lot more difficult by preventing access to several (for us) critical options (poi/track, map, themes). Also I do hope that the distance value will be changed / enhanced to display the distance from start and distance to end instead of distance to GPS.

Another thing which I would love to see (though I could not say if it is included or not): I know that the Locus Maps have a POI database. As I never downloaded anything from the Locus Store, I do not have them and use the free vector maps without them.
Nevertheless, it would be great for motorcycle trip planning if there was an option to show POI of a certain group (for example gas stations) *along the route* (say +- n km/mi, optional value). That should not be a dynamic option but a 'display GROUP (select) along the current route' button, which helps identify a POI (or multiple) to add as via point (or mark as 'visible') and then hide everything else again.

Currently I use Navigon Cruiser or Here we go (both work on Here maps and its POI database) to find the nearest gas station offline and add them manually to the route :-)

Best wishes,
zhaelon