Accessing stored locations

Former Member over 8 years ago

Hi,

I would like to create a geocaching app for fenix 3. Therefore i would like to send the caches(*.gpx) via basecamp to the watch. Then i would like to load the cache as location in my application.
Basicly navigate the user to the cache, but i would like to display it in another way, as the default "navigation" function does.

There is a module called persistedLocation, but it only has an methode to store, but not to load the location...
Is there a way to acces the filesystem of the watch? I could manually parse the gpx file ?!?

Thanks for your support!

Best regards, Christian

Brandon.ConnectIQ over 8 years ago

There is currently not a way to download GPX files (or other file types) directly to the file system of the device. Keep an eye out for a future release, however--this is something that's been discussed, and we have several navigation-related features on the road map.

Former Member over 8 years ago

There is currently not a way to download GPX files (or other file types) directly to the file system of the device. Keep an eye out for a future release, however--this is something that's been discussed, and we have several navigation-related features on the road map.

Awesome! Any hope to get access to the navigation info form 1.3 on the fenix 3 in the future? Or to turn off the pre turn alerts for that matter ;)

Brandon.ConnectIQ over 8 years ago

It's unclear right now where these features will fall with respect to 1.3 v. 2.1, so I don't want to set the wrong expectation.

For example, had you asked me six months ago whether we'd have some of the features we have in 1.3, I would have leaned toward "no", but we were able to get a lot more back-ported than I was anticipating. :) On the other hand, I know that it took a lot of work to get 1.3 squeezed in because of hardware limitations (especially on fenix 3), so I'm hesitant to suggest we'll add a bunch of new navigational features in a future 1.x release.

Mapping and navigational features are something we're talking a lot about, however. It's the core of many of our products, after all, but something like a mapping API isn't exactly a trivial thing to do. If it's any encouragement, we're already on the Oregon 7xx and Rino 7xx devices, and a product like that (bigger screen, much faster hardware, more hardware resources, etc.) is just begging for more navigational features.

Former Member over 8 years ago

It's unclear right now where these features will fall with respect to 1.3 v. 2.1, so I don't want to set the wrong expectation.

For example, had you asked me six months ago whether we'd have some of the features we have in 1.3, I would have leaned toward "no", but we were able to get a lot more back-ported than I was anticipating. :) On the other hand, I know that it took a lot of work to get 1.3 squeezed in because of hardware limitations (especially on fenix 3), so I'm hesitant to suggest we'll add a bunch of new navigational features in a future 1.x release.

Mapping and navigational features are something we're talking a lot about, however. It's the core of many of our products, after all, but something like a mapping API isn't exactly a trivial thing to do. If it's any encouragement, we're already on the Oregon 7xx and Rino 7xx devices, and a product like that (bigger screen, much faster hardware, more hardware resources, etc.) is just begging for more navigational features.

I'm trying to mix race planning (power targets at specific lat long points) with the navigation so need access to power data as well. But I think the edge devices are planning on implementing some of this data. So that will be a good starting point.