Exposure of route coordinates in the API.

Hi there
The navigation features of my Fenix 3 HR are not very good - the autozoom is too zoomed out to be usable - disabling it means if I go off track there is no indication on the map to the direction of the the course. The course to follow is green which on a low contrast display in poor light conditions is hard to see ( we don't all live in California ). I would like to write an app that handled navigation better ( emulate my Suunto Ambit3 Peak which does it well ). I am interested in the persisted content but the returned course class does not seem to expose the underlying co-ordinates of the course. Am I getting the wrong end of the stick or are the course coordinates not exposed in the API? It does not seem possible to save a route on the simulator and interrogate the data that is supplied with a route intent ( to see if the coords are hidden in there ). Grateful for either advice on how to go about this or a definitive statement that it can't be done.
Cheers
Dreuw
:D

Former Member over 8 years ago

I have noticed in some Connect IQ apps that their developers are creating their own set of waypoints rather than using the persisted ones already saved by the standard Garmin apps. Does this mean that waypoint coordinates cannot be obtained by the API, in a similar way to you have found with course coordinates? This would be a shame as it so easy to store points as 'saved locations' which could then be used by other apps.

jim_m_58 over 8 years ago

I'm the author of one of the apps that maintains it's own waypoints (Hike2), and did it some time before PersistedContent existed, but had looked at PresistedLocations (now depreciated) which only allowed locations to be saved (not read), and only on a few devices. Unfortunately, the information in PersistedContent can't be accessed from a CIQ app (It was the first thing I looked at when it was available). In my case I not only wanted to read the info on waypoints, but also allow for setting new ones, but neither can be done.

Doing my own saved WPs in the app really wasn't that hard to do.

dududu13 over 8 years ago

entrada road

Hi jim_m_58
I've made my app with built-in waypoints, cause I have a F3, and persisted content doesn't work with this model.
I'm using 60 alphanumeric properties and settings (for 60 waypoints), and this is not very useful. And I have to decode each string in a tab[60] when I want to read one waypoint.

Did you find an other way to do ?

I would be very interessed, cause I'm to the limit, with my app, of the memory for my F3
See the app in my signature

Thanks

jim_m_58 over 8 years ago

The app adds the WPs itself when a user marks one, and loads the list when it's run the next time. Everything is saved in the Object Store (not the same as app settings, with properties, etc), as between 0 and 50 lat/lon pairs (going up to 99 would be no issue, but going to 3 digits might take changes to some screens where I display the WP number - I use numbers and not names to ID them.)

I have some smarts in the app, so It can display "reasonable" ones that are loaded - ones that are within a certain distance of the current location, or had been "found" in the current recording, so you could have WPs from different hikes in different areas, and this way, it's not WP's from both locations all the time, just the ones that pertain...

dududu13 over 8 years ago

Ah OK, thanks but this will not OK for my app
Thanks again