I'm not sure what a TTN6 is - TomTom? Usually they have some kind of stickiness algorithm for when you go under bridges or into tunnels - it assumes you stick to the nearest road until you are about 10 meters out at least (My navman GPS/router does something like this - it was fun on a section where I was ON the PA Turnpike and it insisted I was on a side road). The nav software tends not to trust the GPS, or at least isn't good enough to distinguish Dilution of Precision, or even number of satellites, or DGPS via WAAS or EGNOS. The point displayed on the map even at high zoom (like my Zmapper for the zaurus, now working on the nokia) is often right on the line (well within 3 meters). But another problem might be the maps aren't always accurate. US14 has a new section (Janesville to Waseca MN) that still isn't on many online maps. So the problem might be an attempt to compensate if the map is off (or traffic is on the shoulder or across as in an construction zone).

On the topic of mounts, since I have an n810, its AMPS mount, and a DockNRock (amp+dual speaker handlebar clamp) on my motorcycle, I plan on mounting it there. I already checked it would fit. Now if the ice would just go away . I'm using an AMPS panavise mount I mentioned in accessories in my car.

However my GPS and my EVDO system might go elsewhere. The above image was from a KR1 router in a drybox I have attached to my sissy bar. The velocity data is live (series of KMLs), but the above was post-processed. I embed the datastream (not OBD2, but I've decoded enough of the traffic to know where the RPM, gear, etc is) within XML comments within the KMLs, so you have a GPS location every 200 mS, followed by records with system milliseconds and the j1850 traffic in hex which you can see if you examine the above telemetry file. (I used to carry an iPod, but won't need that with the Nokia).

Note that KR1 is a mips machine with far less power than the n810. It was just convenient since it ran linux, had two serial ports (hidden), and I could hack the firmware to add GPS.

Make no mistake, USD5000 is no 'small prize pot'. I hope this tempts developers into the fold. A complete list of requirements in a nice specification would help a potential developer, hell for that money I'd do it if I could justify the time! Without a more precise spec its hard to guesstimate how long and thus how worthwhile the bounty is so you really need a comprehensive list of "must have's".

I'm interested as I'm sure many others are.

In fact looking at the initial post again which is, I suppose, a 'mini-spec', the 'first version' would be well within a short development time-frame. Some of the more advanced features could be expanded on later. Shoot me a PM as I'm interested in learning a little more about the project. Check out my home page (and linked in profile if need be) to see more about me.

I am always game I am comfortable in programming with python maemo , c++, gtk .

I bought a Wii controller for 39$ and a nunchuck for 19$. http://www.wiili.org/index.php/Wiimote#Motion_Sensor . Wiimote uses bluetooth and uses ADXL330 for the motion sensor which has a range of +/-3g. One can also connect multiple Bluetooth devices at a time. I tried with the Wiimote and a BT GPS together and it worked fine.

Frankly, I never expected to be able to pull this off for free. Ideally, it would be great to find a developer who is open to a revenue share, otherwise I would just commission someone to get this done for a fee and take it commercial/donationware/shareware. I'm also open to a hybrid model where the developer gets paid a token sum, and takes a small revenue share for every licence sold. Many ways to cut the pie, and I'm open to options.

I'll be working on a detailed requirements specification this weekend, and will have something to share with interested developers (e.g. vabgeo) next week.

The 10Hz GPS with J1850 saved to KML is working now. I'm slowly turning my n810 into an instrument cluster for my Harley. Now if only the weather would cooperate.

I'll probably be doing an alpha release of my minigpsd shortly (which does all these things). I've released a "developer" version - no deb, just tarball with source, binaries, and readme.