tabsep layout information

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

tabsep layout information

Ted Timmons
Is there any documentation behind the tabsep data form? I'm importing
from mapsource and GDB data formats, and I'm wondering where a lot of my
data went- track name, elevation, speed, even the time of day.


5107    RPT4334 RPT4334         ""                      47.916396
-124.606802     1745531788      1102206032      47.916396N
124.606802W     N47.916396      W124.606802     N       W
24.104589F      7.347168M       38535.113044    1120272167      0.0
0.0     Unknown Unknown 13.412120       21.584715               20050702


-ted


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Gpsbabel-misc mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: tabsep layout information

Robert Lipe

> Is there any documentation behind the tabsep data form?

Tabsep is kind of an odd duck.  It really is just kind of a dump of
everything (?) we think we know about a waypoint.   The best way to see
exactly what's in it - and it does change over time - is to look:

http://cvs.sourceforge.net/viewcvs.py/gpsbabel/gpsbabel/style/tabsep.style?rev=1.6&view=markup

The fields themselves are defined in 'README.style' in our source tree
and binary distributions.

> I'm importing
> from mapsource and GDB data formats, and I'm wondering where a lot of my
> data went- track name, elevation, speed, even the time of day.

A reality is that 'tabsep' really is a waypoint format.  (See discussion
earlier this week on waypoints and tracks not really being totally
interchangeable.)  So things like 'track name' aren't representable in
this format for now.

> 5107    RPT4334 RPT4334         ""                      47.916396
> -124.606802     1745531788      1102206032      47.916396N
> 124.606802W     N47.916396      W124.606802     N       W
> 24.104589F      7.347168M       38535.113044    1120272167      0.0
> 0.0     Unknown Unknown 13.412120       21.584715               20050702

Your altitude is 24.1045 Feet which is 7.347Meters.
Speed isn't stored.   Applications that display this compute it themselves.
Your timestamp is 1102206032 seconds since the epoch which appears to be
about Saturday December 4, 2004 around 6:20pm.  (That may be local time
instead of GMT - adjust to taste.)

RJL


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Gpsbabel-misc mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: tabsep layout information

Ted Timmons
Robert Lipe wrote:
>>I'm importing
>>from mapsource and GDB data formats, and I'm wondering where a lot of my
>>data went- track name, elevation, speed, even the time of day.
>
> A reality is that 'tabsep' really is a waypoint format.  (See discussion
> earlier this week on waypoints and tracks not really being totally
> interchangeable.)  So things like 'track name' aren't representable in
> this format for now.

Is there some other format tracks should be output to, so I can see
_all_ the data gpsbabel knows how to extract? Hmm, maybe I should use GPX.

>>5107    RPT4334 RPT4334         ""                      47.916396
>>-124.606802     1745531788      1102206032      47.916396N
>>124.606802W     N47.916396      W124.606802     N       W
>>24.104589F      7.347168M       38535.113044    1120272167      0.0
>>0.0     Unknown Unknown 13.412120       21.584715               20050702
>
>
> Your altitude is 24.1045 Feet which is 7.347Meters.

Aha.

> Speed isn't stored.   Applications that display this compute it themselves.

Makes sense.

> Your timestamp is 1102206032 seconds since the epoch which appears to be
> about Saturday December 4, 2004 around 6:20pm.  (That may be local time
> instead of GMT - adjust to taste.)

Hrm. That's my point- that date isn't right. It should be around 7/1/05,
give or take a couple of days.

After a bit of checking, the problem seems to be with tabsep- if I
output as GPX, things look better.. so maybe I'll switch to that.

FWIW, I verified with GDB v1 and v2, mapsource, and GPX to tabsep.
Obviously, the latter is significantly easier to prove.

-ted



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Gpsbabel-misc mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: tabsep layout information

Robert Lipe
> Is there some other format tracks should be output to, so I can see
> _all_ the data gpsbabel knows how to extract? Hmm, maybe I should use GPX.

GPX is probably the most expressive format that's easy to parse.

> >Your timestamp is 1102206032 seconds since the epoch which appears to be
> Hrm. That's my point- that date isn't right. It should be around 7/1/05,

You said you were "wondering where it went".  I didn't follow the jump
to you knowing where it was and thinking it's wrong.

> After a bit of checking, the problem seems to be with tabsep- if I
> output as GPX, things look better.. so maybe I'll switch to that.

If you can produce a clear test case (data file and precise command
issued) we'll look at it.

It's not apparent to me yet if you're seeing a problem in the GDB reader
or in one of the writers.


--
Support GPSBabel by helping to improve it or fund those that that have
done so.  Visit:

        http://sourceforge.net/donate/index.php?group_id=58972


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Gpsbabel-misc mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc