Suggested Developer Reading

**thekl0wn** · 07-02-2009, 12:25 PM

This project interests me, as a developer and mobile computer enthusiast!

Upon a quick search, I've found a few resources which seem to be giving me a better grasp of what all this project(s) is going to encompass.

Starters
To start off with, the general direction and information is located in this thread.

Open Source Mapping
OSM Wiki Beginner's Guide to Mapping

NMEA Data -- National Marine Electronics Association.
http://www.mp3car.com/vbulletin/show...itle=NMEA+Data
http://www.nmea.org/content/nmea_sta..._standards.asp
http://en.wikipedia.org/wiki/NMEA
http://www.gpsinformation.org/dale/nmea.htm
http://aprs.gids.nl/nmea/
http://www.codeproject.com/KB/mobile...ications1.aspx

Mods, feel free to add/remove/alter anything to this post if need be, and I don't get to it first.

**ecog** · 07-02-2009, 05:09 PM

The OSM wiki has some good info too:
-OSM Wiki Beginner's Guide to Mapping

**chunkyks** · 07-02-2009, 06:39 PM

I realise this is more of a negative read than a positive one, but I find it interesting:
http://esr.ibiblio.org/?p=801

For what it's worth, I use gpsd for all my gps needs. If nothing else, it's really /really/ easy to use. The entire code that obdgpslogger needs to get lat,lon,alt is here: http://svn.icculus.org/obdgpslogger/....c?view=markup

For an idea of the things that gpsd can return, start at struct gps_data_t near the bottom of the header for using gpsd's libgps: http://svn.berlios.de/viewvc/gpsd/tr...93&view=markup
The really interesting bit for most people is gps_fix_t which is the first struct in that file.

Have fun,
Gary (-;

**malcom2073** · 07-02-2009, 08:29 PM

That's all good and well, but it's kinda worthless coming from a heavily anti-windows guy (the gpsd lead) for two reasons. First, for this project to succeed I think we need to focus on the windows market as the majority of carputers we're dealing with here run windows. Anyone who argues that is a fool. Secondly of the primary things to watch out for when doing massive data collection and algorithm generation is data consistency. Unless that guy or someone else (you?) is planning on porting GPSD to windows it's worthless to us. You don't want to collect data two different ways depending on the platform, that's a great way to start running into issues real fast.

**chunkyks** · 07-04-2009, 12:40 AM

I fully recognise that gpsd is 'nix only and anti-windows.

I'm just suggesting that for want of a list of things that are easily accessible via a gps device, there's a big list right there.

Gary (-;

**Fiberoptic** · 07-06-2009, 09:55 AM

Originally Posted by malcom2073

First, for this project to succeed I think we need to focus on the windows market as the majority of carputers we're dealing with here run windows.

In order for the solutions and algorithms I talk about here to work, we need millions of active probes or data from hundreds of thousands of probes collected over a long time. The long term plan should include the ability to collect data from gps or skyhook mobile devices (phones) to increase the chance of success.

Consumers are going to get grumpy with paying 9.99 a month for their nav apps and I hope we can leverage that to collect more data.

**thekl0wn** · 07-06-2009, 10:58 AM

IMO, shouldn't the focus/plan be aimed at the data, its integrity, and the availability to add/receive that info... Not the end-program(s) platform?

**Fiberoptic** · 07-06-2009, 02:35 PM

Originally Posted by thekl0wn

IMO, shouldn't the focus/plan be aimed at the data, its integrity, and the availability to add/receive that info... Not the end-program(s) platform?

yes, the focus should be on data collection.

I think we were talking about probe and data collection platforms not navigation/routing/ user interface platforms or the server which will collect this data.