Is there a "standard" file structure for in-car nav systems?
 16 years
|
I just bought my first car with an in-dash navigation system (Nissan Murano). It is possible to import destinations into the system, but the file structure is not anything like what I've seen in gpx, csv or ov2 files we use with our standalone GPS units. (The manual has ZERO technical info on importing data.)
File extensions are hlc for the "Home" location, and slc for "stored locations." I exported the few locations in my system, and changed the file extensions to *.csv so I could read what's there. There are 30 or so fields in the *.slc file, and they are separated by commas. I can figure out what only two of the fields are: longitude and latitude. There was nothing that indicated where the display name, street address, city, state etc. are stored. And many of the fields have 0's, 1's and -1's in them, signifying that they may be flags of some kind. The home location file has few fields, but I don't know what the data signifies.
Is there a "standard" file structure for in-car nav systems? And if so, where would I find out how the records are structured?
Many thanks in advance.
don't think so
I just bought my first car with an in-dash navigation system (Nissan Murano). It is possible to import destinations into the system, but the file structure is not anything like what I've seen in gpx, csv or ov2 files we use with our standalone GPS units. (The manual has ZERO technical info on importing data.)
File extensions are hlc for the "Home" location, and slc for "stored locations." I exported the few locations in my system, and changed the file extensions to *.csv so I could read what's there. There are 30 or so fields in the *.slc file, and they are separated by commas. I can figure out what only two of the fields are: longitude and latitude. There was nothing that indicated where the display name, street address, city, state etc. are stored. And many of the fields have 0's, 1's and -1's in them, signifying that they may be flags of some kind. The home location file has few fields, but I don't know what the data signifies.
Is there a "standard" file structure for in-car nav systems? And if so, where would I find out how the records are structured?
Many thanks in advance.
As each system is proprietary in their interface to the integrated entertainment system it would stand to reason there would be no standardization. Look to Garmin and Tom-Tom, the files each uses are different. Not only is the input structure different, you can't run an OV2 in a Garmin just as a Tom-Tom won't run a GPI or GPX.
Illiterate? Write for free help.
Is there a "standard" file structure for in-car nav systems?
Just to follow up, with new info...
After learning that Nissan has a Navigation help desk, I spoke to them about this. Bottom line, the nav system was not designed to allow users to import destination data into it. The export/import function is designed only for backing up the destinations one has programmed into its Address Book. Eg, let's say you buy a new Nissan: you can export the destination data from your old car and import it into the new car's nav system.
The only way to add new destinations to the nav system's Address Book is to input them manually, via the head unit. Bummer.
Garmin DriveSmart 55 & Traffic | Garmin nüvi 250W | Garmin eTrex "yellow"