Configurable Default Waypoint Icon?
I am a new user migrating from Orux for bike navigation. Orux has a default waypoint icon that is easily visible at all map zoom levels for imported GPX track files. With bike navigation these need to be easily visible at a glance... Just like the GPS in your cars.
Locus also has a default icon for imported tracks. Unfortunately, it is a nearly invisible microscopic black dot - barely visible at the highest map zoom levels. This may be fine while hiking or walking out of traffic but is worthless for bike navigation!
Please consider adding a user configurable default waypoint icon that is easily visible at all map zoom levels. Locus has a large number of user choices for track styles. How hard can it be to do this for waypoints?
Thanks,
Steve
I like this idea 
Hello Steve,
may you please attach small GPX sample so I may check icon we talk about on own device? I'm not 100% sure from where may come small dot and sample GPX may help me here, thanks.
Menion
Hello Steve,
may you please attach small GPX sample so I may check icon we talk about on own device? I'm not 100% sure from where may come small dot and sample GPX may help me here, thanks.
Menion
Hello Steve, c. s. g.
in next version will be improved icon for merged track waypoints as described here.
I would rather stay with perfectly working default icon without need to set manually. So please if in the next version, you find some icon really "wrong", share the same sample data or screenshot and we may discuss here replacement of this icon directly in the app. Thanks.
Hello Steve, c. s. g.
in next version will be improved icon for merged track waypoints as described here.
I would rather stay with perfectly working default icon without need to set manually. So please if in the next version, you find some icon really "wrong", share the same sample data or screenshot and we may discuss here replacement of this icon directly in the app. Thanks.
Steve is out now for a cycling tour. Internet ?
It is not about rtept's. What is the problem ?
Rwgps gpx output uses the unsupported and unknown sym "dot" for each waypoint (wpt), so it is only about wpt's !
Locus automatically generates the "mini dot" Icon for any unsupported sym ( "dot"). For Steve this default Locus Icon is too small and hardly visible at a track overview while cycling. (Not using navigate).
Request was: Let the user choose free "default" Icon. Ex a Flag of any other larger Icon from the available Icon range list. Roger ?
(mobile edit sorry for typo's)
Steve is out now for a cycling tour. Internet ?
It is not about rtept's. What is the problem ?
Rwgps gpx output uses the unsupported and unknown sym "dot" for each waypoint (wpt), so it is only about wpt's !
Locus automatically generates the "mini dot" Icon for any unsupported sym ( "dot"). For Steve this default Locus Icon is too small and hardly visible at a track overview while cycling. (Not using navigate).
Request was: Let the user choose free "default" Icon. Ex a Flag of any other larger Icon from the available Icon range list. Roger ?
(mobile edit sorry for typo's)
Thanks Willy.
I'm anyway a little bit confused now. Second topic where Steve and others discuss the probably similar issue is too long to read. So I'll rather wait till Steve returns from his trip and upload me here one trip that display mentioned small icons. So I'll be able to simply test it and offer some other icons in these cases.
Which I really really prefer. Option to choose default icon is doable anyway there won't be clear when this default icon will be used. You also know that it will be used only in cases when GPX contains an unknown (invalid) "sym" parameter. Which usually should not happen (at least not too often).
Thanks Willy.
I'm anyway a little bit confused now. Second topic where Steve and others discuss the probably similar issue is too long to read. So I'll rather wait till Steve returns from his trip and upload me here one trip that display mentioned small icons. So I'll be able to simply test it and offer some other icons in these cases.
Which I really really prefer. Option to choose default icon is doable anyway there won't be clear when this default icon will be used. You also know that it will be used only in cases when GPX contains an unknown (invalid) "sym" parameter. Which usually should not happen (at least not too often).
I just spent (NOW WASTED) an hour and a half to post a response. Hit comment and it DISAPPEARED!
I just spent (NOW WASTED) an hour and a half to post a response. Hit comment and it DISAPPEARED!
Let's start over... and this time in a separate text editor!
In this part of the world, at least, RWGPS is the 800 pound gorilla in the bike navigation room. Local clubs and state and national organizations generally use RWGPS to provide electronic POI/navigation to participants in their events.
Therefore it is highly desirable for other devices and apps (like Locus) to be able to effectively use this data. Note that the riders/participants have little control over how the data is generated other than the export options in RWGPS.
With Orux I could export a GPX file from RWGPS and view it in Orux. Although Orux wouldn't navigate it directly it would show your location on the map and the rest stops and POIs on the route. The default POI icon was big enough to see at any zoom level and tapping it would bring up details of a particular POI.
This is, at least, the functionality that I am trying to get from Locus. Actual turn-by-turn navigation would be nice as well as long as it doesn't use up battery life too fast.
Based on may hours of trial and error testing it would appear that the small "dot" icon is only part of the issue. As I mentioned previously the small dot icon can be made more visible by changing the default color of the track.
Here is the RWGPS route that I have been studying:
https://ridewithgps.com/routes/28040734
NOTE: zoom in the map to see more POIs that are on top of each other.
FIT -
Appears to be NAV info only; NO POIs shown on imported map. Does anyone know if the FIT file format supports POIs?
TCX -
Also Appears to be NAV info only; NO POIs shown on imported map. Looking at the XML file I don't see any of the POIs included. Does anyone know if the TCX file format supports POIs?
GPX Include POIs as Waypoints -
POIs show as the small black dot but at least they are there! XML file shows a single "dot" icon for ALL POIs. RWGPS specific icons don't appear to be output. Does anyone know if the GPX file format will support different POI icons?
Issues:
1. Pink navigation track COMPLETELY covers POI icons.
2. Pink navigation track obscures streets in urban areas unless zoomed WAY in. Can this navigation track width/style be changed?
3. Can Locus really turn-by-turn navigate without directional waypoints at each turn? No warning was given when I hit "navigate".
GPX Include POIs & Cues as Waypoints -
POIs show as the small black dot but at least they are there! XML file shows a single "dot" icon for ALL POIs. RWGPS specific icons don't appear to be output. Does anyone know if the GPX file format will support different POI icons?
Issues:
1. Pink navigation track COMPLETELY covers POI icons.
2. Pink navigation track obscures streets in urban areas unless zoomed WAY in. Can this navigation track width/style be changed?
3. Again, will Locus turn-by-turn navigate this time with waypoints at the turns? The XML has the NAV waypoints as directionals and Locus displays this on the map as well.
So this issue is complicated. It looks like RWGPS either doesn't support POI icons in some file format exports or the file type itself doesn't.
On the Locus side imported POIs only show as a small dot and are completly covered by the pink navigation track. However, if Locus can't navigate a GPX track then this is moot. It may be that navigation (must use FIT or TCX file) are mutually exclusive to displaying POIs (GPX files).
One thing that I did notice when looking at the TCX from my recent tour was that the rest stops and other POIs were encoded as a directionals. While they showed on the map they were completely lost in all of the "uninteresting" directional waypoints.
Does anyone have any other thoughts / suggestions?
Let's start over... and this time in a separate text editor!
In this part of the world, at least, RWGPS is the 800 pound gorilla in the bike navigation room. Local clubs and state and national organizations generally use RWGPS to provide electronic POI/navigation to participants in their events.
Therefore it is highly desirable for other devices and apps (like Locus) to be able to effectively use this data. Note that the riders/participants have little control over how the data is generated other than the export options in RWGPS.
With Orux I could export a GPX file from RWGPS and view it in Orux. Although Orux wouldn't navigate it directly it would show your location on the map and the rest stops and POIs on the route. The default POI icon was big enough to see at any zoom level and tapping it would bring up details of a particular POI.
This is, at least, the functionality that I am trying to get from Locus. Actual turn-by-turn navigation would be nice as well as long as it doesn't use up battery life too fast.
Based on may hours of trial and error testing it would appear that the small "dot" icon is only part of the issue. As I mentioned previously the small dot icon can be made more visible by changing the default color of the track.
Here is the RWGPS route that I have been studying:
https://ridewithgps.com/routes/28040734
NOTE: zoom in the map to see more POIs that are on top of each other.
FIT -
Appears to be NAV info only; NO POIs shown on imported map. Does anyone know if the FIT file format supports POIs?
TCX -
Also Appears to be NAV info only; NO POIs shown on imported map. Looking at the XML file I don't see any of the POIs included. Does anyone know if the TCX file format supports POIs?
GPX Include POIs as Waypoints -
POIs show as the small black dot but at least they are there! XML file shows a single "dot" icon for ALL POIs. RWGPS specific icons don't appear to be output. Does anyone know if the GPX file format will support different POI icons?
Issues:
1. Pink navigation track COMPLETELY covers POI icons.
2. Pink navigation track obscures streets in urban areas unless zoomed WAY in. Can this navigation track width/style be changed?
3. Can Locus really turn-by-turn navigate without directional waypoints at each turn? No warning was given when I hit "navigate".
GPX Include POIs & Cues as Waypoints -
POIs show as the small black dot but at least they are there! XML file shows a single "dot" icon for ALL POIs. RWGPS specific icons don't appear to be output. Does anyone know if the GPX file format will support different POI icons?
Issues:
1. Pink navigation track COMPLETELY covers POI icons.
2. Pink navigation track obscures streets in urban areas unless zoomed WAY in. Can this navigation track width/style be changed?
3. Again, will Locus turn-by-turn navigate this time with waypoints at the turns? The XML has the NAV waypoints as directionals and Locus displays this on the map as well.
So this issue is complicated. It looks like RWGPS either doesn't support POI icons in some file format exports or the file type itself doesn't.
On the Locus side imported POIs only show as a small dot and are completly covered by the pink navigation track. However, if Locus can't navigate a GPX track then this is moot. It may be that navigation (must use FIT or TCX file) are mutually exclusive to displaying POIs (GPX files).
One thing that I did notice when looking at the TCX from my recent tour was that the rest stops and other POIs were encoded as a directionals. While they showed on the map they were completely lost in all of the "uninteresting" directional waypoints.
Does anyone have any other thoughts / suggestions?
Thanks, Steve! This is a much needed enhancement for use with current RWGPS output to make waypoints, like rest stops, visible.
Thanks, Steve! This is a much needed enhancement for use with current RWGPS output to make waypoints, like rest stops, visible.
Hi guys, Steve,
not sure about the exact state and need of this idea. It's been half of the year. The initial idea was also mainly about the icon for points that comes into the app over import.
Anyway, because it may be useful, I've added an option to choose point default icon into expert settings. So it will be available in the next version 3.45.
Hi guys, Steve,
not sure about the exact state and need of this idea. It's been half of the year. The initial idea was also mainly about the icon for points that comes into the app over import.
Anyway, because it may be useful, I've added an option to choose point default icon into expert settings. So it will be available in the next version 3.45.
Menion,
I believe that the configurable default icon should apply to points that are IMPORTED with and merged with a specific TRACK.
It is unclear (to me) if and how this relates to your expert setting above. Don't non-track related points already have a default icon selection by folder?
Thanks,
Steve
Menion,
I believe that the configurable default icon should apply to points that are IMPORTED with and merged with a specific TRACK.
It is unclear (to me) if and how this relates to your expert setting above. Don't non-track related points already have a default icon selection by folder?
Thanks,
Steve
Replies have been locked on this page!