[Openstreetmap] Extending GPX to include track type information?

[Matt Amos]

On Monday 21 March 2005 20:26, Nick Whitelegg wrote:
> Combining yours and Lars's responses, I think the best thing to do
> is to have a separate <trkseg> for each segment, then have the
> table just store segment types in the same order as the <trkseg>s
> (no need for start and end tags in that case). e.g.
>
> <segdefs>
> <seg>
> <foot>yes</foot>
> <horse>yes</horse>
> </seg> <!-- segment 1-->
>
> ... etc.... (like the readable form of the tags? ;-) )

is it better to use the <extensions> part of the trksegType? e.g:

...
<trkseg>
 <trkpt>...</trkpt>
 <trkpt>...</trkpt>
 <trkpt>...</trkpt>
 <extensions>
  <navigability foot="1" horse="1" car="0" boat="0">
  <signpostmarking>Bridleway</signpostmarking>
 </extensions>
</trkseg>
...

> Re Lars's point.... I'm a bit worried about each path being a
> separate <trk>. For example, if you were editing a track, and
> wanted to divide it up into segments of different types, if each
> newly-created segment was separated out into a separate <trk> you
> would lose the information on the parent track of each segment, the
> original GPS-surveyed track. This could be a problem if you made a
> mistake and you wished to delete a segment. I do feel that there
> needs to be a way to associate track *segments* with types.

this is why we need (and have) inherent versioning in the database. 
you can upload your raw GPX tracks, then edit them afterwards, safe 
in the knowledge that if anyone makes a mistake you can roll back the 
database.

cya,

matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20050324/408a3d31/attachment.pgp>