There have been lots of little updates to GPSLog Labs since my last post and a couple of big new features that I'll preview here but will explain in full detail in future posts.

• Translations: GPSLog Labs is now available in different languages.

  By default only day and month names will be translated, but there is a more comprehensive Polish translation thanks to Lukasz. If you want to help out translating GPSLog Labs into your language, contact me at tom@gpsloglabs.com.

  
• Upload via email: On the detail page for your device you will be provided with an email address that you can email logs to (as attachments) and they will be processed. When they're ready you'll receive a reply with the links to your activity.
  
  This is particularly useful if you want to upload a track recorded on your iPhone using MotionX GPS app, for example.
• Sharing: By default all your activity on GPSLog Labs is private and visible only to you, but Logs now have a Share button that lets you generate a publicly accessible detail page, such as this one.

  You can then share the URL on Twitter, Facebook, email, IM or wherever you like.

  

  You can also get a snippet of HTML to embed the map or graphs into your own website like this:

The day and week calendar views of your activity on GPSLog Labs now have a new Itinerary tab. This isn't the best name, as it shows what you did, not what you plan to do, but you get the idea.

In this view, all activity (and sessions) are displayed one under another with their own maps and altitude profile graphs.

Having their own maps means that short activity isn't invisible at the scale required to show longer activity.

This post outlines a few of the recent updates to GPSLog Labs:

• Sorting/filtering the Uploaded Log Files page:
  

  The Uploaded Log Files page can be sorted either by the date the files were uploaded or the date of the activity in the file.

  It can also be restricted to show only "new" uploads, that is log files which haven't had any edits yet. This can be handy to find the logs you've uploaded but not yet edited.

  These logs will have their file names coloured yellow in the list, and when you make a change they will go blue.

  
• Mark as done
  

  A checkbox will now appear next to logs on the Uploaded Log Files page if they don't need to be edited. This will mark them as edited and turn the filename from yellow to blue and stop them from showing up on the "new uploads only" view.

• Go back to Uploads button
  

  The Go back to Uploads button on the log editing page will now go back to the uploaded log files page at the same place you left it from, which should make it a bit easier to keep track of the logs you're editing. It will also have a "mark as done" checkbox if you haven't made any changes to the activity segments but want the log to no longer show on the "new uploads only" view.

• Device format detection
  

  The device format detection page has had an overhaul to make it clearer that you have to do this step before you can see all the log file details.

  This page shows the details of the newly uploaded file, and tests it against all the file formats that GPSLog Labs supports.

  Any formats that have valid data will be displayed and you can choose the best one before continuing on with the main processing and editing of your log file.

I've changed the GPSLog Labs upload form a little, partly to make it nicer looking and less cluttered, but mostly to make the purpose of Devices a little clearer.

Previously, the choice of device to upload to wasn't shown on the form if you had only one device, and now it will always be given.

To process the log files you upload, the system needs to know what the format of the file is. When you first upload a file, there is a page that automatically detects this format, but that isn't practical to do for every file that is uploaded, so the setting is stored in a "device". This means that each device can handle one format only, and therefore, if you want to upload files with a different format you'll need to create another device to do so.

The other purpose of devices is to track battery life. If you upload all logs you record, then GPSLog Labs knows how long your logger has been switched on so can predict how much time you have before you need to recharge/replace your batteries and therefore prevent you getting a flat battery in the middle of an activity, which can be rather frustrating!

When the logged usage goes over 75% you'll get a warning:

Marking the point where you recharged or replaced your batteries is easy too:

The new GPS track filters in GPSLog Labs are powerful, but if you had to configure them by hand for every log that you uploaded, they wouldn't be much use.

Thankfully, the real power of the filters is that they can be attached to tags, and then when that tag is assigned to a log the filters will be copied across automatically.

This means you can configure a set of filters for all your logs tagged with Run, and you can have a different set of filters for Bike Ride. For example, you may want to tweak the sample window size on the Median filter as the average speed will vary less when running than when bike riding so the filter can be a bit more aggressive.

The process for adding filters to a tag is the same as for a log, the difference is that you can't see what is being matched by the filter, so I suggest you get the filter working on a log then copy the details across to the tag so it is automatically applied to other logs.

Note that the filters are only automatically copied across to the log when the tag is assigned to the log and you have not modified the log filters. You can click the Reset button on the log filters page to restore it to the defaults for the tag.

As always, let me know if you have any difficulties or suggestions, and I hope you enjoy this new functionality.

In addition to the automatic discard filters, GPSLog Labs has 2 "manual" filters you can use to clean bad data out of GPS tracks that the automatic filters can't handle.

Manual Filter

This filter lets you discard logged data between two times. E.g. if you spent some time inside a building and got spurious signals as a result, you can "zero out" the data between when you entered the building and when you left.

Select the time range by highlighting the portion of the log on the graph, or adjusting the slider, or keying the times into the text boxes:

The data between those two times will be discarded and GPSLog Labs will interpolate the log between the remaining points:

You can use as many manual discard filters as necessary to clean up your log.

Position Filter

This filter lets you discard logged data in a specified area. E.g. if you have travelled between buildings or through an underpass where you get bad signals you can zero all points within that area.

Select the area to remove by moving the marker on the map and adjusting the radius:

The data between within the selected area will be discarded and GPSLog Labs will interpolate the log along a straight line between the remaining points. This won't be perfect, but will be better than the original noisy data. Like Places, the discard filter is "sticky" so that if the track leaves the radius briefly (less than 60 seconds) it will discard everything between the first point inside the radius and the last. This should mean you don't have to make the radius too large and will still be able to capture all the bad points.

You can use as many radius discard filters as necessary to clean up your log.

GPSLog Labs currently has 2 "discard" filters that run automatically to clean bad data out of GPS tracks.

Speed Filter

This filter is the easiest to understand: It will discard any points where the speed is above a certain threshold.

It has two parameters, the cutoff speed (e.g. 20 km/h for running) and the number of points to discard either side of the "bad" point.

After the points have been discarded, the log will be interpolated between the remaining points, hopefully giving you a more accurate trace of your activity.

Static Navigation

The static navigation filter will only be useful if you have a GPS logger with a chipset that includes this "feature" and you can't disable it (e.g. a logger using the SiRF Star III chipset such as the AMOD AGL 3080.) More details on static navigation can be found by reading http://www.etenblog.com/2007/11/20/static-navigation-explained/ and http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=25575.

Basically, in this mode (which is optimized for driving, not walking or running), when your speed is below 5km/h the logger will "clamp" your position on the assumption it's getting some kind of signal "drift". When it decides you really have moved the logged position will "jump" giving you a log that looks something like the following:

Applying a simple median filter to this data doesn't really help (see the detail below) as there are still lots of samples at the same location:

The static navigation filter will detect these points and remove not just the point, but as many of the "clamped" points as it can, giving a much better result:

(Note that this still needs a median filter to get the best results.)

The next post will describe the "manual" discard filters.

GPSLog Labs now has a powerful and customizable filtering feature to clean up errors in your logs caused by bad GPS signals.

There is a new menu option on the log detail page that will let you edit the filters applied to that log:

The following graph comes from a log recorded while running and shows the kind of noisy data that is often present. The incorrect speeds mess up the maximum speed, average speed and distance stats and often correspond to a bad trace on the map too.

Discard filters

The first filters you can choose from will discard invalid points from your log and then interpolate the speed and course between the remaining points.

After applying those filters, the speed vs time graph looks a lot better (discarded points are colour-coded to match up with the chosen filters):

Post filters

The second filtering stage applies an average function to the newly cleaned up data. Smoothing the speed graph will give you a more reliable average and maximum speed statistic and also improve the distance and time split data, but won't clean up the trace on the map or affect the total distance.

The original speeds are shown on the graph below as a light blue line, and after applying a median filter, the thick blue line has been smoothed (no discard filters were applied for this graph).

This graph shows the final results when both discard and post filters are applied:

Existing logs

The new filters will only take affect for new uploads, existing logs will retain the data from the old filter that GPSLog Labs used to apply until they are reprocessed.

Also, the discarded points from the old filter will no longer be shown on the Speed vs Time graph on the log detail other graphs tab. This information is only available now for logs using the new filter system from the Filters menu item.

Try it out

I suggest using a simple Speed Median filter initially, as that will clean out a lot of noise, setting the window time parameter to a larger value will smooth the speed more. I'll be describing the other filters in future posts.

As always, let me know if you have any difficulties or suggestions, and I hope this new feature helps you get more out of the site and your GPS logger!

I've just updated the select route dialog when editing the processed activity for an uploaded log to make it nice and graphical, instead of an unclear dropdown list:

This will show the thumbnails for each route to help identify them, and also highlight in green the routes that are closest in length to the logged activity.

If you've assigned tags to the activity, the possible routes will be filtered. You can click the Show all routes link if you need to see other routes.

GPSLog Labs has always made some basic attempts to automatically assign a route for a log segment if it can:

• If there is a single route between the start and end places of the log it will be assigned automatically.
• If there are no routes between the start and end places, one will be automatically created and assigned.

And now I've just added an experimental feature that will try to guess the route after you assign a tag. This is useful in those cases where you have 2 (or more) routes between places, say one by car and one by bike. The above automatic assignment won't work in these cases, but if you tell it whether it was by bike or car by tagging the route, it will look again for routes using only the assigned tags.

This works in reverse too, if you assign a route that always has a particular tag associated with it, then the tag will be automatically filled in too.

So, it'll vary depending on your setup, but you should be able to select the route in many cases and have the tags automatically assigned and select the tag in other cases to have the route automatically assigned.

Let me know if you come across any issues with this change, and hopefully it makes things a little easier.