I don't mean to be terse, but you did not ask any question. You simply made a feature request, which does not necessitate an answer. I assume by "locations database" you're referring to stored waypoints, tracks, and routes on the device. Is that correct?
We have longer term plans to include more navigation and mapping support in Connect IQ, so this kind of feature will be available in a future release. In the meantime, there are a few examples of ways people have found creative solutions to use Connect IQ to manage this kind of information:
I don't mean to be terse, but you did not ask any question. You simply made a feature request, which does not necessitate an answer. I assume by "locations database" you're referring to stored waypoints, tracks, and routes on the device. Is that correct?
We have longer term plans to include more navigation and mapping support in Connect IQ, so this kind of feature will be available in a future release. In the meantime, there are a few examples of ways people have found creative solutions to use Connect IQ to manage this kind of information:
Yes, I think about true, original waypoints stored in device (in any ciq applications, including watchface), syncing with basecamp etc. Not like this "creative solutions" who need battery drain in internet connection, and store ways and points in cloud.
And about _shared waypoints_ between oryginal applications in firmware and ciq - dwmap and hike don't can this.
Yes, I think about true, original waypoints stored in device (in any ciq applications, including watchface), syncing with basecamp etc. Not like this "creative solutions" who need battery drain in internet connection, and store ways and points in cloud.
And about _shared waypoints_ between oryginal applications in firmware and ciq - dwmap and hike don't can this.
Ok, long term, yes, undestund, I ask in 2017.
Actually, "hike" stores everything locally, and needs no internet connection at all. The .fit has lap marks where waypoints are marked, and a user found a way to take the data and import it to basecamp. Battery wise, it's similar to the standard running app.
I build waypoints as you go, vs loading something existing through. But there's no reason I couldn't store waypoints in the object store and use them again when the app is run the next time.
On fenix/epix You can store POI (I save waypoints in poiget app), but we can't get this in ciq :(
I think about datafield with three closer POI (distance/direction) but I can write this without database. Yes, I'm "creative" and can write this using external/self poi database - but this is prothesis not solution.
I want write watchface with closer POI (compared to last know position) - no way.
Long term plan is in Fenix 8 ;) I don't have wait 5 years for silmple, low energy and safe solution like get poi from local inwatch database.
I think you're being a little hyperbolic in your outlook. :P This isn't something that you'll have to wait five years for, but I can't speak to exact dates yet. I can assure you that it's all being planned. I wish I could share more!
