As a mobile and open device the OpenMoko platform is ideal to run an OSM client. But since you don't have that much time while driving and postprocessing consumes quite some time the client should do lots of things automatically for you.
Here are some suggestions to make the interface suck less.
Features
- Auto record mode: If your speed is faster than running (say 20 km/h) and you are on an unchartered road, record the road automatically. If you are on already marked road, but with "questionable" status (missing street name, etc), notify user about missing data, and allow user to add the missing data.
When entering a new road you get to choose what type it is (eg. residential, motorway, primary, ...) (It may be entered as [http://www.linuxtogo.org/gowiki/OpenMoko/ideas/VoiceText VoiceText]). Option to make a photo (of street name sign) and relate it to GPS point would be nice.
While you're on the street (and if you have enough time) either enter the name or record the name of the street for later (It may be entered as [http://www.linuxtogo.org/gowiki/OpenMoko/ideas/VoiceText VoiceText])
- Maybe a button "This is the speed limit" which calculates your current speed from GPS and rounds it to the nearest 10 km/h
- Optional display an underlying map of the current existing OSM data
- Cache a set of tiles for an area and for the area along a route so using GPRS is not needed while traveling
- This is more hardware feature, but nonetheless: Make an add-on keyboard (BT or wired) with big touch buttons so they can be pressed without looking at the Neo1973. Useful buttons would be: "Take voice note", "One way street", "Two way street".
- 'Default' setting (or factory reset) for good data capture: 1 Hz, drop points with low-DOP (precision)?
Developer Notes
Look at MaemoMapper for tiling and map display
OpenMokoIdeas OpenMokoIdeasWithGPS