[Openstreetmap] Re: How to be more efficient inserting tracks?

[Immanuel Scholz]

Hi,

> the new REST interface for "Uploaded Points" seems to return only the
> raw lat/lon information
> Shouldn't we change this? maybe something like
>   <trkpt lon='-0.20506667' lat='51.495342' id='1234'/>
> with an request that returns the full information
> (or for privacy reasons only track-id and order)
> for a list of trpkpt id's

Well, this is not legal gpx.

We could do this by something like:
<trkpt lon="..." lat="..."><extensions>...</extensions></trkpt>
or use an own transport format (as already suggested somewhere in Wiki ;).

However, doing single requests for every track point one after another
will surely blow up the server. So better transfer the correct order in
the first place.

GPX does not restrict the order the points are transfered. So

1. Order them in the way they were uploaded inside one page.
2. do not transfer a static amount of 5000 points per page but one upload
track file per page.

could do the trick as well..

However all this feels like stretching the gpx-format to its legal limit,
bypassing the spirit of gpx... I'd always try to use things for what they
are made for. So using gpx's own structures for passing tracks would be
best, IMHO. Why using some additional interpration when all things we need
already there?

<!-- first uploaded raw gps data file -->
<trk>
  <trkseg>
    <trkpt lat="..." lon="..." />
    <trkpt lat="..." lon="..." />
    <trkpt lat="..." lon="..." />
    <trkpt lat="..." lon="..." />
  </trkseg>
</trk>

<!-- next uploaded raw gps data file -->
<trk>
  <trkseg>
    <trkpt lat="..." lon="..." />
    <trkpt lat="..." lon="..." />
    <trkpt lat="..." lon="..." />
  </trkseg>
</trk>
...

This would enable users to show the gpx on a normal, gpx viewer not made
for OSM.


Uhm, shouldn't we switch to osm-dev for the boring technical details? :)


Ciao, Imi.