Messages

Is there any trick to setting OM behaviour for timestamps on waypoints imported from gpx? I can see that OM is attempting to show them in local time, but for me it always adds 11 hrs to the UTC in the gpx file; even though my timezone (correctly set in android) is UTC + 10 hours. Altering UTC settings in OM Global Settings > Units has no effect on the time displayed in waypoint properties. Strangely, waypoints imported with no timestamp show as 1970-01-01 10:00, which I am guessing is a default time of 1970-01-01 0:00 + 10 hours. If so OM uses +10 hours there, but +11 hours when there is an incoming timestamp. Am I missing something??

Great App. I have studied the manual (and searched online), but I am still learning and can't find any answers to:



1. Is there any way to get a list of the Oruxmaps built-in waypoint types (faster than using many screen shots)? This would help a lot beacuse users do not need to recreate them as custom types, and it may be possible to efficiently assign Oruxmaps types to imported waypoints by editing a gpx file in a spreadsheet (after converting to csv using something like ExtraPOI editor).



2. The former option to show waypoints on screen was useful for those of us who think of waypoints as POIs rather than points necessarily attached to a track or route. But this option seems not to exist in v7.0.12. To see them on the map, I have to use in the Manage Wpts screen > Select (icon near top) then > Load into Active Route (icon near bottom left) > No Navigation. Is that the intended (quickest) method?



3. I guess using the above method, all those POIs will disappear from the map screen when I choose to navigate a saved route. I understand this is the current Oruxmaps model of "waypoints as points along a track or route", but it there any way to serve those who use a model of waypoints as POIs (points for display on the map even if we are not currently navigating to them)?



4. Although the terms waypoint and POI both appear in the Oruxmap manual, there seems to be no distinction between the concepts in the current App?



5. When a Track type is selected, does this do anything other than adding a tag? e.g. does it alter the way a track is displayed?