Recording Where You've Ridden All Day On Garmin 595lm?

Discussion in 'Clothing, Gadgets & Equipment' started by dubcat, Jun 6, 2019.

  1. Does anyone know if it's possible to set a Garmin Zumo 595LM up to record where you have been riding throughout the day so you can plot it on google maps afterwards?
     
  2. There is a 'track' mode, not sure if it resets on PF. But I think there is a setting on one to save as a favourite journey. If so, you can then get into basecamp and I'm sure get in to google maps with a converter.
     
  3. Does it email the data to your local plod too, to check speed compliance?
     
    • Agree Agree x 1
  4. All Garmins record a tracklog of where you've been, time and speed. Look in the GPX folder on the device, not the SD card, for a file called current.gpx, this has your current tracklog (as well as routes and POI that you've imported). When that gets a bit unweildy the tracklog data is saved to /GPX/Archive in incremental files and the tracklog in current.gpx cleared before it starts recording new track data. So, unless you've had a purge and deleted it, there will be details of your travels from the first time you rode with your Garmin switched on to the current day.

    Using appropriate software you can read and display this data. For Google Maps it would need to have the number of recorded points seriously reduced to work.

    This data could easily be accessed by law enforcement in the course of an accident investigation, that's if they know it's there in the first place...
     
    • Like Like x 1
  5. You can convert tracks to routes on the 595, and also join them together (usually join all for the same date together to start with).

    if you use basecamp, plug the 595 in and upload all the data from the device. I suggest you create a new 'list' folder in your collection area and import into that, otherwise everything just goes into the 'unlisted data' area.

    There will be a bunch of tracks for each session the device was turned on. You can browse each of these on basecamp, and delete the ones you don't want (i.e. while you had it turned on in a hotel, or having lunch for example)
    you can join these together to make a complete track, and also convert a track to a route.
    You can also put sensibly named waypoints on it if you wish.

    Once you have what you want (either as track or route), export it as a gpx file, and then load that into google maps.

    I regularly use track logs. When my mates who have tomtom devices share gpx files with me, the first thing I do is load them into basecamp, as they generally come in as tracks if they were created on Tyre or its replacement. I load these onto my 590 and set them to be displayed so I can see where my calculated version differs from their original.
     
  6. Basecamp's convert to route feature is a bit clunky and, from my experience, just arbitrarily reduces the number of nodes in a route. I find it preferable to 'trace' over the route with the routing tool. That way you can drop nodes on the far sides of towns, for example, the GPS will then 'pull' you through by the best/most efficient, in its mind anyway, route.

    On older devices such as the 660 Zumo this helps with the announced points too.
     
    • Like Like x 1
  7. Thats odd bumpkin, I never find it removes node points. It certainly doesn't if you combine them on the device itself, the file still contains all the track points.

    I do agree with your routing method though.
    The problem with converting from a trip log to a route is you don't get a liberal sprinkling of waypoints, so makes it tricky if you want to recalculate, or start mid way along a route.
    This is a bit off topic, but always interesting to hear how others plan their routes. I use a combination of announced (way point) and unannounced (shaping point). I put sensible names on the announced ones, which are generally every 20 miles or so, depending on the complexity of the route. If you have cause to recalculate it only does it to the next waypoint.

    I should declare I have worked with gps devices in my day job, and created / processed the various types of gpx files. Its interesting to see (to me anyway :yum) just how the likes of tyre change the content of the file depending on what device type it was intended for, and how this still differs from the actual garmin generated format. This is why the likes of the 390 gets upset by tyre generated routes when sharing them, and despite tomtom and garmin both complying to the gpx standards, they create and process the content in a different way. Plus they impose arbitrary limits on the number of waypoints (purely for what we assume is memory processing reasons).
    No, I don't work for either Garmin or TomTom :)
     
  8. I also find basecamp clunky, and slow (running on mac so probably why!) but it works ok: just need to allocate a lot of time to do it.

    I just find google doesn't like whatever you try and upload.
     
  9. Ah i have a 590lm! not a 595. So, they do all record tracks automatically. I wonder how many miles/hours of tracks they can hold though.
     
  10. From the day you first used it... It should all be there in the /gpx/achive folder.
     
  11. Presumably it ultimately runs out of space and then starts over writing the oldest data. I’d like to know how long/far that takes to happen.
     
  12. Just for something a bit different, there’s an App called ‘Relive’. Maps out the route you’ve taken, you can add photos from points you’ve stopped at and does a video type rerun of your route that you can save to your device as a video file
     
  13. Will check it out but my bikes USB connection is not providing any power for some reason so I'm a bit worried about running out of juice on the phone. Friend told me to try a similar app called 'rever'.
     
  14. Get yourself a powercase for the phone. Absolute godsend!
     
    • Like Like x 1
Do Not Sell My Personal Information