Remove tracks and waypoints from the resulting GPX, keeping only the route.Remove as many waypoints as possible, creating maximum error of 500 meters.Gpsbabel -i kml -o gpx -f Routetest.kml -x transform,rte=trk -x nuketypes,waypoints,tracks -x simplify,error=0.5k -F Routetest.gpx
So if you want to skip the labour-intensive step of creating placemarks for all your route waypoints, you can use the track instead. Now, the funny thing is, that this can also be applied to tracks from Google Maps’ KML files. If this is still acceptable, you can profit from the greater accuracy of your route. For example, using ‘error=0.05k’ (50 m), gives me 109 route waypoints. It speaks for itself, that a higher value for ‘error’ will give you less waypoints, and a lower value will give you more. My guess is, that most routing engines will calculate identical routes, regardless of your routing parameters, like shortest/quickest route. I think that this gives us a route, that has enough waypoints not to leave much room for interpretation by the routing engine of a GPS device. In orange is the original track in green is the resulting route, with dots on the route waypoints. Gpsbabel -i gpx -o gpx -f track.gpx -x transform,rte=trk -x nuketypes,waypoints,tracks -x simplify,error=0.1k -F route.gpxīy specifying a maximum error of 0.1k (0.1 km, or 100 m), our original track file, containing a track of 62.84 km in 2641 trackpoints, is converted in to a route file, containing 73 route waypoints. That means that the nuber of waypoints can be higher on more complex pieces of our route, and lower on the long stretches. It allows us (and again, I quote) to specify the maximum allowable error that may be introduced by removing a single point.
Simplify will let you specify a maximum number of waypoints in a route, but we will use another feature: maximum error. The Simplify filter is used to simplify routes and tracks for use with formats that limit the number of points they can contain or just to reduce the complexity of a route.Īnd that is exactly what we need. The invocation is similar to the one in my previous post, but instead of using waypoints, we convert a track into a route, and we add a filter: simplify. We will use GPSBabel to do the conversion. So, now I have a GPX, containing the exact track that I want turned into a route. Maybe later I will post something on using Viking, but that’s besides the scope of this post. Stuff like that is easily corrected with Viking, a nice GPS/track/waypoint editor, that runs on Linux (POSIX) and Windows, and is available under the GPL v2 license. I don’t know about you, but in my case, a track always contains some stuff that I don’t want to show up in the end result: mistakes that I made during my ride, like entering dead-end streets, or those extra meters that you make, looking for a place to park for a coffee break. Now, I would like to create a route out of this track, that I can share with others. For example, a drive of about 60 km that I took a few weeks back, gave me a track consisting of over 2600 trackpoints. Typically, such a track contains many trackpoints. Suppose you have a GPX file, containing a track.
GPSBABEL FROM NV2 TO GPX HOW TO
This post is about something else, namely how to convert a GPS track (that you created by driving, downloaded somewhere, etc.) into a route, with the same criteria as last time.
The main problem that I was trying to solve, is how to create a “real” route that my Zümo will understand, built out of a minimal amount of route waypoints (that show up as such on the Zümo when navigating), rather than possibly thousands of trackpoints, that are hard to process for the device and don’t give you as much navigation flexibility. Last week, I blogged about creating routes for a Garmin Zümo, using Google Maps and GPSBabel. Categories: GPS and mapping, Motor, Nerd Stuff
0 kommentar(er)
