Hubrisware

This is a minor release which improves export to Google Maps and fixes two bugs.

Thanks to a diligent user I was able to find and fix a small bug in the KML export logic which was causing the tracks to not be drawn when imported into Google Maps, even though they worked correctly in Google Earth.  In correcting this and playing with Google Maps a bit, I found that Maps has known limitations with large KML files.  When the number of vertices reaches a certain point, it will automatically paginate the display of the KML into multiple pages.  For a long ride with all the GPS points loaded in the KML, this makes it impossible to view anything but a short ride in Google Maps without loading different map pages.  To deal with this situation I added a new Filtered KML export option.  What filtering does is try to remove extraneous GPS points from the KML.  The algorithm to remove the extra points is based on distance and bearing and greatly reduces the size of the KML file.  In my example, a 3+ hour ride with unfiltered data was 192K and was broken into 3 pages on Google Maps.  With filtered output it was 64K and displayed on a single page.

There are some downsides to filtering.  There is a loss of data so the result is less accurate than when unfiltered.  In my experiment I tried a lot of different distance/bearing settings before settling on the one now in place.  For the examples I have tested against, the display difference between filtered and unfiltered is small, but I cant guarantee that will be true for all cases.  Future versions of RideTrac will likely do more with filtering (attempt to filter noise, improved algorithms, provide user settable parameters, etc).  If you have problems with this version of filtering let me know and I’ll try to make improvements.

The other bug fixed is a crash that would happen if you selected a track drawing mode other than OFF or SOLID before loading a track.  This has been corrected in this version.

dave RideTrac