Regularly update cookie jar; update map paths; include gpx scripts

1 files changed, 46 insertions, 0 deletions

diff --git a/tracks/README b/tracks/README
new file mode 100644
index 0000000..31cf41c
--- /dev/null
+++ b/tracks/README
@@ -0,0 +1,46 @@
+Firmware
+========
+ - Firmware will be updated automatically if device is connected to WiFi network. This doesn't work on the power cable
+ and batteries should be present in the system. Once firmware downloaded (on WiFi availability, no message), the update
+ will be performed during next restart.
+
+Sync
+====
+  - There is multiple sources of tracks, routes, and waypoints.
+    * Garmin/GPX folder (in earlier firmwares this was limited to tracks in GPX/Archive in the main memory
+    The data will be not loaded from SD and waypoints/routes were not supported. This is not fixed by using MapSource
+    or old version of BaseCamp. But this seems fixed in the current firmware).
+    * EDM database which updated when routes/waypoints are stored on device or synchronized using explore.garming.com
+
+  - Easiest way to synchronize.
+    * Generate a list of .gpx files using basecamp: separate file for each track and route, but one for waypoints.
+    Names are non-informative and will be as bad in the device if copied as is. Rename script will fix it and organize
+    structure.
+    * Basically puts all tracks to 'GPX/Archive' folder which will ensure they are not using active memory. Waypoints
+    and routes go to directly under 'GPX'. Waypoints/routes goes to SD. Tracks for now should be stored in main memory
+    as on SD they are not archived but active even if put under 'GPX/Archive'. In the internal memory, it OK.
+    * Routes will still not preserve the actual path and will be recalculated on the device (but there is no way around
+    with other synchronization options)
+
+  - osmand
+    * Single GPX is reasonably imported (and can be easily removed). However, routes are imported as small tracks (consisting 
+    of waypoints only). There is no way to pass the routing either. So, basically best to exclude routes.
+
+
+  - Problems
+    * If archived, there would be no way to sort/filter tracks (they are even not alphabetically sorted). So, it is 
+    quite inconvinient for overview. Might be better solution is to use osmand for planning and Garmin on the trail and
+    for routes.
+
+
+Garmin Explore
+==============
+  - Routes need to be loaded one by one or the naming will be lost if a single GPX with multiple routes is used. Using
+    kml input doesn't help either. 
+    * Routes also include waypoints and importing routes and waypoints sequentially will result in dublicates (also on
+    the device). 
+  - Tracks are not possible import at all. Web site just says 'Invalid media type'. Even if a single track is imported.
+    KML import results in the same error.
+  - Tracks/routes from 'GPX/' on the device are synchronized (but not tracks in the 'GPX/Archived'). So, thats probably
+    the only way to import stuff in the system.
+  - The web site is also anyway pretty limited in the sense of route analysis (no routing!), etc.