|
I hope there is a way of setting it up to record a single non-fragmented trace. It's time wasting to have to find and join the bits for upload. The traces are usually of up to seven hours or 20 km hikes with the device set up to record a point every second. At the moment the traces seem to get stopped and restarted after 500 seconds or points. Maybe I'll try distance instead of time. With Units set on miles the shortest distance is 0.01 miles (17.6 yards) which is no good for most mapping, but on yards I can set it to 1 yard or less (0.9 of a meter) which should be ideal, but with units set to metric the smallest distance is 0.01 KM (also not good) there is not a meter option. I have not checked out what the record rate is if it set to 1 yard and I then switch to metric units, although it does indicate the log distance is 0.00 KM which doesn't make sense. I just have to do some test traces to see what gets recorded and if the trace gets split. I like the Oregon but this seems inferior the my old VistaHCX which just recorded once every second and stored it as a continuous trace on the micro SD although the devices inbuilt memory would start to over write the oldest data. |
|
tl;dr:
Old Garmin devices with micro sd slots were designed to write one gpx logfile per day. This file contained the segments which resulted from switching the device off and on or (iirc) when the device wrote it's buffer of 9.999 waypoints to disk. The newer devices as of ~2010(afaik) and later save the gpx log to their internal memory. The device can set to "automatically save" it "daily", "weekly" or "when full" but I see no sense in this setting since it only names the files after day or week and creates a lot of them. Additionally the created files also contain several way segments. I manage the gpx files this way: Reasoning to split the files in even smaller chunks: A gpx file named 2013-12-20 12.54.09.gpx is named after the date it got saved. It can contain way segments from other days or even weeks depending on how often the device is used. The splitter script gives each way segment an name like 2013-10-20T14:31:48Z.gpx GPX data I want to upload to OSM I mostly can define by the date, so I just run Another way to have just one gpx file is to append the gpx files you want using gpsbabel. I wrote a small script for this, too. |
|
The best trace setting for mapping is to record once a second. I have found that the free version of GPSTrackMaker and easyGPS http://www.easygps.com/ which when opened I can use to find the oregon/garmin/gpx folder and control click on all the days track sections and down load them all at once. (I couldn't find another to do this) This group of files are then saved as one named as the "date" or the "place" of the walk as a GPX. The next step is to open this GPX with my usual program that I use to trim off the birds nests, the ends and join the sections together, this is then saved as ready for upload to OSM. This will do until Garmin write an update that works as well as the old Vista HCX which creates a single trace for the day. edit The calculator isn't scientific but the Oregon is very very good. It gets a cold fix in 30 seconds,even when moving. I have about 6 vector maps to switch about and loads of custom maps, The 2100mAh batteries I use last 8 hours ok and the battery gauge shows when getting low. I recommend Oregon 450. Thanks for this Andy. I have just bought an etrex30 and am also trying to get the gpx sorted. It is more trouble than expected and the ability to save very long 1 sec traces directly to the sd drive would be ideal.
(23 Dec '13, 00:50)
nevw
I cannot find a setting on my Garmin Oregon 450 to save traces straight to SD, maybe your new etrex 20 can and hopefully as one complete trace each day.
(23 Dec '13, 19:26)
andy mackey
The Micro SD will often be used for expensive purchased maps. Probably why Garmin don't use this for GPX storage.
(23 Mar '18, 07:19)
andy mackey
|
|
I have been experiencing and looking at fragmented/sectionalized problem again. I have had the Oregon set to auto archive and this and a full current file caused the device to save to archive when full, On one walk every 50 minutes. The main cause of autosave kicking in, is my failure save GPXes to my PC then delete them from the Oregon's memory. The mapping software i usually use only has the facility to choose only a single file at a time, which is tedious. GPS Prune allowed me to control click all of the sections, with the same date, then load them as one file. Prune, as the name suggests as pruning facilities to trim off rouge points and it also displays the up-to-date OSM map so you can see if you new trace is new to OSM and worth uploading to the traces list.
|
Today I found that auto record only yielded 600 points in 145 minutes too crude for mapping. But found I should choose from menu, track manager, current track, save and name,then clear. Hopefully this will give me the specified 10000 track points for a hike, which equals 2.666 hours at one a second. The oregon will then auto save then which is probabley why I get the sectioned trace. If I do the save, name and clear bit, 3 traces called say part a ,b and c should be ok and will be easier to pick for editing, joining and uploading.
I didn't remember to keep doing this, but you may, you could set an alarm on the oregon to remind you.... too complicated.
Would it be perhaps be possible to upload somewhere an example of a "fragmented" trace? Maybe then someone could have a go at using something to glue the bits together automatically.
http://www.openstreetmap.org/user/andy%20mackey/traces/1624036 http://www.openstreetmap.org/user/andy%20mackey/traces/1628215 http://www.openstreetmap.org/user/andy%20mackey/traces/1628217 the top trace was the whole days hike the last two are some of the 8 that i joined to make one.