CIQ app, for watch or non wearable, has very limited access to files. Storage and Settings for reading/writing, <name>.txt log files for logging. and .fit files for recording. A few reasons are speed (the file system is slow), and also for the watch to protect itself. No large files the FW doesn't know what they are, etc. Also a security piece. How to make sure only your app can read/write the file.
What you could do is pull down the data when you have network access and store in in your App's Storage for later use.
CIQ app, for watch or non wearable, has very limited access to files. Storage and Settings for reading/writing, <name>.txt log files for logging. and .fit files for recording. A few reasons are speed (the file system is slow), and also for the watch to protect itself. No large files the FW doesn't know what they are, etc. Also a security piece. How to make sure only your app can read/write the file.
I knew about this. The speed thing is a BS issue (since IQ already lets apps use "persisted storage").
The size thing too is kind of BS (since there's that issue with web data). So is the "don't know what they are" (make the files JSON just like is already done for web data).
The security is, also, might not that hard to deal with. (Maybe, that other apps can read the file is just a noted risk.)
There really aren't very good reasons why IQ can provide controlled access to reading a file (it does it already).
Other than the "security" issue, IQ already does what it needs to do with files with what it does for the web data.
What you could do is pull down the data when you have network access and store in in your App's Storage for later use.
That's what I do.
What I do is read the course files to get data they contain (like the start point and the distance).
It's kind of silly to already reading the mounted drive but being forced to update the information on the network. It's also an extra, confusing step for the user.
In fact I`d like to filter osm for amenity=drinking_water for a certain area only and copy the result on the device to get the information on long runs where the next possibility for drinking water is. A data field for that is easy to create. Statically binding means a lot of data for runs which are not close to your home. Changing the data is not difficult: Everybody has access to all the data on the device via USB-cable.
Unfurtinately garmin did not think about exporting the water-data from osm to their img-file. You get results for restaurants, flower shops, ... but not for basics during an excercise!
