Format of gpspoint location output is probably wrong.

[GoogleCodeExporter]

The only other programs that I know of that use gpspoint format are:

http://beej.us/gps/
+
http://sourceforge.net/projects/viking/

These both use the string 'latitude' to indicate the value not 'latdata'.
Similarly should be 'longitude' not 'londata' in templates.rb.

Disclaimer: I'm current the maintainer for Viking, but I know of no references 
of any kind to describe the gpspoint format.

Original issue reported on code.google.com by rwa.nor...@gmail.com on 20 Mar 2013 at 11:12

[GoogleCodeExporter]

Obviously the user base for the gpspoint format is, um, quite narrow...
Thanks for pointing out the discrepancy which seems to be real indeed:

http://mpickering.homeip.net/content/conversion-tools suggests to use gpsbabel

  gpsbabel -i gpx -f input_file.gpx -o xcsv,style=gpspoint_track.style -F output_file.gpspoint

with the style file containing the comment (matching the rules)

  #type="waypoint"  name="HOME"  altitude="886.9"  latitude="32.24827"  longitude="-82.20285"  symbol="house"  display_option="symbol+name"

A quick workaround (until a patch is ready) to fix the gpd file would be to run 
a text replacement command like "sed":

  sed -i -e 's~latdata=~latitude=~g' -e 's~londata=~longitude=~g' output.gpd

I'd like to see some feedback from non-Viking gpspoint users (are there any) or 
a pointer to a format description. What for example about the pre/post lines 
"waypointlist" and "waypointlistend"?

Original comment by Steve8x8 on 21 Mar 2013 at 12:00

• Changed state: InfoNeeded

[GoogleCodeExporter]

Found another place which looks rather canonical:

  http://mirror.rosalab.ru/rosa/rosa2012.1/repository/SRPMS/contrib/release/gpspoint-2.030521-7.src.rpm

although the sources in the packages are from 2003...
It's clear now that the field names are "name", "longitude", "latitude", 
"altitude" (we don't have that, should there be a dummy value?), "comment", 
"symbol", "display_option", and "rtpoint" (the latter probably marking a route 
point).
The decimal digit counts are 1 for altitude, and 5 for longitude and 
latitude... I don't think 6 digits would do any harm but I'll reset that to 5 
for consistency.

There will be a patch within the next day(s)...

Original comment by Steve8x8 on 21 Mar 2013 at 12:48

• Changed state: Started

[GoogleCodeExporter]

First patch fixes the original "gpspoint" template.
Second one (apply after first one) adds a new template "gpspoint2" which uses 
gpsbabel to convert a gpx file into gpspoint format, additional waypoints are 
also output (I think this is what most people want?).
Please test...
(Both patches have applied to SVN trunk, resulting in rev 1299.)

Original comment by Steve8x8 on 21 Mar 2013 at 3:00

[GoogleCodeExporter]

Um, forgot to append the patches... trying again...

Original comment by Steve8x8 on 21 Mar 2013 at 3:02

Attachments:

• 263a-gpspoint.diff
• 263b-gpspoint.diff

[GoogleCodeExporter]

Any feedback about this issue, before it's time for the next release?

Original comment by Steve8x8 on 18 Apr 2013 at 1:15

[GoogleCodeExporter]

Supposed to be fixed by 3.16.6 (if not, will re-open)

Original comment by Steve8x8 on 26 Apr 2013 at 7:15

• Changed state: Fixed