[OSM-talk] Gpx: non-public traces in JOSM/Potlatch and milliseconds in timestamps with JOSM

[Richard Fairhurst]

Tom Hughes wrote:

> Jukka Rahkonen <jukka.rahkonen at mmmtike.fi> wrote:
>> While Potlatch shows the uploaded track fine with a neat blue line,  
>>  the "Convert
>> to data layer" function in JOSM does not order trackpoints correctly by
>> milliseconds.  Is it supposed to do so or is it just better to make running
>> seconds instead of milliseconds?
>
> The server only stores points to 1s resolution I believe, so Potlatch
> has no choice in the case where it is displaying all points in the
> area. When displaying a single trace it has the original XML file
> available so could use greater resolution if it wished.

If we're just talking "ordering", Potlatch, as you say, just orders by  
timestamp per track ("ORDER BY fileid DESC, timestamp").

However I'm willing to believe that MySQL might, within this  
constraint, return them in the order of insertion. That would mean  
that Potlatch would get the order right anyway.

cheers
Richard