The final product still has a few glitches which are mainly due to me being a bit slow to switch on data roaming or because Latitude failed (I believe there are a few days in 2012 where this was the case for my account). $GPSBABEL -i gpx -f $1 -x transform,wpt=trk,del -x transform,trk=wpt,del -x simplify,count=7500 -o gpx -F simple.gpx $GPSBABEL -i gpx -f $1 -x transform,wpt=trk,del -x transform,trk=wpt,del -x simplify,count=7500 -x transform,trk=wpt,del -o kml,lines=1,points=1,line_width=4,trackdirection=1,labels=1 -F simple.kml It is a good idea to reduce the number of points a little bit which is easily achieved with gpsbabel. I could finally look at the result in Google Earth. Gpsbabel -t -i gpx -f $file -i gpx -f join.gpx -x track,merge,title='2012' -o gpx -F join-tmp.gpx # first gpx file and then deleted all track points. # actually this needs to be file that has valid GPX but no points $GPSBABEL -i gpx -f $file -x transform,wpt=trk,del -x radius,distance=0.2K,lat=$LAT,lon=$LON,nosort,exclude -x radius,distance=0.2K,lat=$LAT0,lon=$LON0,nosort,exclude -x transform,trk=wpt,del -o gpx -F tmp.gpxĪ few days (or weeks) later I had cleaned the entire data set and glued the traces back together with gpsbabel. So, another was used to scrub out those points. I soon noticed that Latitude keeps reporting the same wrong data. split/$begindate.gpxįinally, I could go through every day and delete points that were wrong. latitude-ordered.gpx -x transform,trk=wpt,del -x track,split,start=$begindate,stop=$enddate -o gpx -F. I used gpsbabel to break down the data into days.īegindate=`date -d '$FirstDay +$(( $ +1 ))days' +%Y%m%d`00Įcho '$day $begindate $enddate' Now, the problem was that the entire annual data was a bit large. Again, it took a while to find the right program that I liked, eventually I found gpsprune. So, the next step was to find a program that allows to edit a gpx trace. Unfortunately, Latitude includes quite a bit of erroneous data. At last I could see my track in Google Earth. The first disappointment was that the takeout data was in json format and looking at it was not easy … After searching around for a while I found this script that converted json to kml. So, I downloaded my data and thought I would quickly make a little map. This however looked like it would make the whole project much simpler. I had previously wondered how I could display my annual travel and had dabbled with the possibility to download parts of my entire in kml format form within Latitude. Just before Christmas 2012 a friend pointed me to Google Takeout that allows to download all data Goggle has stored about you including the Latitude data, if you have signed up for it. This worked slightly better with more advanced phones, but until I got my hands on a Nexus S in Autumn 2010 this always stayed very patchy. Soon after Google Latitude started I signed up for it and sporadically updated my location. There are probably any number of bugs.I wrote this a a few years ago for my website that I have now migrated to wordpress. Ideally, gpxsplitter should be part of gpsbabel or something… but yeah, I’ll save the XML parsing in C for a very, very rainy day. Its necessary to include the -t option to force simplify to operate on tracks: gpsbabel -t -i gdb -f ContDiv.gdb -x simplify,count475 -o gpx -F ContDiv3.gpx Note that your coordinates should be in EPSG:4326, and the track should be a single segment. I thought about turning this into a web service, where users can upload their GPX files and have them split, but I’d like to know the demand for such a service before writing it. You can get it from the gpxsplitter repository on gitorious, and the GpxSplitter wiki page is the one-stop place that will collect information about it. It’s a quick little script written in Python 2.x, with dependencies on mxDateTime and lxml. I have converted a track in GPX with GPS Babel but I cannot transfer it to the Geosat through the Geosat Suite. It’s meant to be run first-thing after downloading data from your unit via gpsbabel or mtkbabel. Separating tracks and their associated waypoints was a headache until gpxsplitter came along. GPX files containing multiple tracks and waypoints jumbled together are produced on export by many GPS units, particularly MTK chipset-based devices such as the Qstarz Q1000 and Transystem i-Blue 474. Gpxsplitter splits multi-track GPX files, containing waypoints, into individual one-track GPX files with their respective waypoints.
0 Comments
Leave a Reply. |