Re: [cruiser-users] App Destination Name Error

[Emux]

Thanks for the detailed report.

To clarify how the waypoint names work:

> GPS on, press+hold Favorite to "Set End".

A waypoint (end) is created from the favorite with the favorite name.

> press+hold same location and "Set as Via Point".

Do you mean press+hold the favorite again?
Then a via point is created with the favorite name.

> Then select a more distant Favorite as "End".

Here the end waypoint should probably get the favorite name.

Or we had decided in the K forum to not change automatically the waypoint names (if they already have names).

Nevertheless users expect the waypoints from favorites to get the favorite names.

--
Emux

[Emux]

Names from favorites, search results, etc. will have priority in the next Cruiser update
for the actions that waypoints are (re)created from them.

> I would have expected the new end point *NOT* to inherit a previously selected name - especially if it's not the actual place/road/area.

Actually it is not a *new* point, also the app cannot know if a name is road or not.

When the start and end waypoints already exist (with custom names or weights),
when we set them elsewhere via "Set start / end", it is like *moving* them there (via drag).

Waypoint names and weights are expected to be maintained when moving them.

Except the case like this report, where we (re)create them explicitly from existing favorites,
so the favorite name should have priority.

--
Emux

[Emux]

Do you mean that would like when placing a new waypoint on the map,
that it automatically gets the name of the nearest road or map element?

This is reverse geocoding and it is not performed by the routing engines.
It can be done by the selected search engine (with snap of coordinates).

To test it, use the "Show address" in Cruiser (long press or right click).

You will see that depending on the selected search engine,
the result will be a blue icon *not* at the pressed point, but *near*,
(where the engine finds a result).

Note that this needs internet and causes load on the search engines.

--
Emux

[Willy]

Correct routing and tight navigation with clear simple and good arrangements.

The Shaping(Via) routepoints are nicely and precisely snapped to an osm road.
Thus the street name is then known and just like turnpoints to be put in gpx cmt.
The Shaping(via) points remain nameless this until you give the "child" a name.
Simple.

Example by RouteYou web.

https://www.routeyou.com/r/12000229
See the gpx file contents by Notepad ++

Op vrijdag 6 januari 2023 om 17:06:11 UTC+1 schreef Emux:

[Emux]

Indeed few can merge map + routing together, usually in proprietary formats.
Most use maps + routing from multiple sources and with many combinations.


The POI files are at an early stage.
The Search is expected to improve dramatically in the future Cruiser versions.

We can also use the POI in navigation, i.e. show (with distance) the next fuel stations on the route:
https://github.com/devemux86/cruiser/discussions/9

--
Emux

[Willy]

Understood MotoRiderUK, ok now is very clear what you expect.
OsmAnd maps might even not be possible given the licence either.
I'm not an expert so I  don't read this through that completely.
https://github.com/osmandapp/Osmand/blob/master/LICENSE

Op vrijdag 6 januari 2023 om 18:50:53 UTC+1 schreef Emux: