Showing posts with label gps. Show all posts
Showing posts with label gps. Show all posts

2009-07-25

Garmin, Get Your Act Together

I went for my 80 mile loop ride today; it's posted at http://connect.garmin.com/activity/9719415. I need to start training with PowerCranks again and getting back into a routine; my power data clearly indicates that I'm getting fat, slow, and lazy.

Garmin Connect is a neat service; in fact, it integrates many of the features that I would have liked to see in some other programs, like WKO and SportTracks. Of course, there is no single program that does everything I'd like, so I'll probably end up writing my own in the next few years. In short, I want a program that has all of the advanced power analysis features of WKO, with the mapping features of SportTracks and Connect, that allows you to seamlessly store information both in a standalone app (because I don't always have Internet at races) and online in the cloud (because I like to share my data).

The single biggest complaint I have, at present, is that Connect doesn't work in Opera or Chrome. (I haven't tried Safari.) Come on guys, really? I haven't taken a look at Garmin's Javascripts at all, but I'm guessing it's a simple fix. For all that they've done to embrace Web standards - the .TCX format is, after all, just an XML standard that works with the usual XML processing tools very nicely - it's a real pity that Garmin locks browsers this way. It's like the browser wars all over again. Party like it's 1997.

The best thing about standards, is that there are so many to choose from!

2008-03-05

So Many Incompatible File Formats

There is a very simple reason that people haven't started doing all sorts of interesting things with GPS systems on their bicycles: they're expensive, and they're complicated. You shouldn't need a degree in computer science to figure this stuff out.

I'm racing in the Philly Phlyer this weekend. I've never been on this course before, so I did my homework and found - voila! - a representation of the course as a Google Map, through a service using the Google Maps API. Better yet, this service (using a script that broke Opera but worked in IE) allowed me to save the route as a Google Earth .kml file.


What did the .kml do for me? I could see the route in Google Earth, but that's about it. I wanted to be able to see a profile in DeLorme Topo USA, or export the route for tracking to my Edge 305 GPS, or save it in what ought to be the industry-standard .gpx format. What's a man to do?

After some massaging, I was able to use GPS Babel to convert the .kml file to a DeLorme .gpl data log, which appeared as a bunch of dots in Topo USA. I was then able to trace the route, get my profile, and realize that the course has a nasty downhill going into a sharp right turn. Sigh.





The next step was to get the file onto my Edge 305 GPS. The Edge 305 is such a convoluted device, that one has to use a special file format with special padding using their special software to get something that almost works. Thank you, Garmin. Thank you. I was able to use gpx2crs to convert the racecourse to a Garmin Training Center .crs file. I had to disable automatic turn generation, and add a point every 30 meters. I eventually got something that the Edge 305 would display on its screen.

As a computer scientist friend of mine noted, everyone is indeed using one standard file format: XML. Great. That's almost like saying all computers execute binary instructions of some sort. Having the data is half the battle, using it is the other half.

Why is this so hard? This is absurd. I have a real interest in having incredibly precise maps, as they offer a competitive edge. Lots of smart people are working on this. Guys, make it easier! I'll do my part.