Sunday 9 November 2014
Thursday 6 November 2014
GPX 1.1 and track routes
The first version Trackprofiler worked with only one kind of GPS files -- GPX. Not even all versions of GPX, only 1.0. That wasn't a big problem since 1.1 wasn't used very much at the time. With time I added more formats, but as for GPX handling -- Trackprofiler remained for years with 1.0.
Part of this latest rewrite is the ability to handle GPX 1.1.
Related to GPX handling comes another feature. Track files can contain three different kinds of entities:
Related to GPX handling comes another feature. Track files can contain three different kinds of entities:
- Tracks (with segments)
- Routes
- Waypoints
Tracks are a series of geo-locations recorded with a real GPS. Routes are "planning stages" for tracks, they usually contain fewer points (per unit of distance) and are created by the user on the computer without the need of a GPS unit. Routes are usually uploaded to the GPS (not downloaded from like tracks) and are used to help people navigate outdoor.
Trackprofiler is a GPS track editor, but tracks and routes are basically similar, and that's why you can convert track to route on-the-fly when downloading. But there was one thing missing, you couldn't upload a track consisting of only routes.
Now you can, on the upload page there is a checkbox "Convert routes". If checked routes will be converted to tracks and then you can edit them as with any other track on Trackprofiler.
Trackprofiler is a GPS track editor, but tracks and routes are basically similar, and that's why you can convert track to route on-the-fly when downloading. But there was one thing missing, you couldn't upload a track consisting of only routes.
Now you can, on the upload page there is a checkbox "Convert routes". If checked routes will be converted to tracks and then you can edit them as with any other track on Trackprofiler.
Wednesday 5 November 2014
Track snapshots and multistep undo
...so, let us start with the changes introduced with yesterday upgrade. The first I want to highlight is the "Undo" link when you are editing the track:
From now on, every change you make on a track is stored in a temporary memory with "snapshots" of the track. Snapshots are stored for 10-15 minutes from the moment you made the edit. When you are not happy with the changes you made -- you can reset the track to any of the snapshots (or, of course, reset it to original any time).
From now on, every change you make on a track is stored in a temporary memory with "snapshots" of the track. Snapshots are stored for 10-15 minutes from the moment you made the edit. When you are not happy with the changes you made -- you can reset the track to any of the snapshots (or, of course, reset it to original any time).
Tuesday 4 November 2014
Faster Trackprofiler
After 4 weeks in beta testing the new version of Trackprofiler is deployed on the main site. This version brings many new features. I'll mention only one here (and leave the rest for another blogpost)...
In the last 3 months the entire code for GPX/track manipulation is rewritten from Python to Go(lang). The result is that all the track operations, graph and thumbnail reloading and map refresh time is now much faster than before.
More about this update soon...
In the last 3 months the entire code for GPX/track manipulation is rewritten from Python to Go(lang). The result is that all the track operations, graph and thumbnail reloading and map refresh time is now much faster than before.
More about this update soon...
Subscribe to:
Posts (Atom)
