1. An UBER 5700 mAH battery (Approx doubles it's weight, and thickness, though it might stay on for 6 months without quibbling)
2. The "Expansion Pack" which add's two ports, an RGB port and a USB port.
Turns out the best the RGB port could do was give you a flaccid 640x480 split screen, even though the linux version was supposed to run 800x600 (as it's native res is only 320x240, it's only understandable). Here's hoping the linux aims for these older devices aren't completely washed away!
So I stuck it all together, found an open source NMEA logger, and went to town... literally.
With enough sattelites in clear view, your 2D machinations become 3D, tracking your altitude, as well as your latitude and longitude.. Now that's a lot of tude's .. dude... *facepalm*
Ok.. so, the wonderful site at www.gpsvisualizer.com can take any nmea GPS log and make something fantastic out of it... all the above charts were made using my dinky little PDA and GPS puck setup. As long as you can get the file to the website you can make all kinds of comparison charts, and even google earth traces.
The whole point of all this gps nonsense is to attempt to glean lots of very cool data out of my daily commute. Which way might be faster? If I looked at the top down of my commute, is there a shorter path? Am I going up a bunch of hills that I could be avoiding? Could there be a more fuel efficient route to be taken on my return trip?
The main problem with all of this is that my current vehicle gets 75 MPG without trying all that hard, so my incentive to push that even farther really isn't that heavy, not to mention my total two way commute per day ranges from only 20 to 60 mins. Most of my co-workers have to deal with 75 mins one way.