[OSM-dev] Thoughts on an enhanced GPX api

[Martin Koppenhoefer]

2009/7/29 David Earl <david at frankieandshadow.com>:
> 2009/7/29 Sebastian Spaeth <Sebastian at sspaeth.de>:
>> And no, I don't think the solution is to dropping those traces, but eg
>> being able to connect traces along a path rather than having a big cloud
>> of independent points would make them much more useful to me already.
>
> Isn't the point of the GPX traces not mainly to be able to make them
> available to other people to make sense of, but to
> (a) provide evidence of data source for possible copyright infringement
> accusations, and
> (b) provide the trace for your own editing in Potlatch.

I think they're quite useful to have them underlying. Here the aerials
are often offset by several meters and with enough tracks you can see
this offset and move the underlying aerial. It is IMHO crucial to have
more than one track though.

(b) potlatch? You can't move the aerial-layer (AFAIK), you can't zoom
in closely and it takes ages to load just the mapdata, not to talk
about gpx-traces from the server, so I really wouldn't recommend it to
trace tracks. It is nice to perform tasks as reclassification of
existing streets though.

cheers,
Martin