-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Hughes wrote: | In message <[EMAIL PROTECTED]> | David Earl <[EMAIL PROTECTED]> wrote: | |> On 28/03/2008 16:50, Raphael Mack wrote: |>> Am Freitag, 28. März 2008 schrieb Steve Hill: |>>> On Fri, 28 Mar 2008, Steve Hill wrote: |>>>>> Are you saying every single arrow points the wrong way? Because that |>>>>> would be an easy fix to make ;-) |>>>> Yes, seems to be the case :) |>>> To complicate things more, the direction arrows on data imported from a |>>> local GPX file are the right way around, so this problem is only |>>> affecting data being retrieved from the OSM server. |>> mh, I guess this cannot be fixed in josm, since the the server returns the |>> stored gps points in arbitrary order. I would even suggest not to draw any |>> direction arrows for gps data from the server. |> They can be sorted by timestamp, can't they? They do have timestamps AFAICS. | | I believe that they are sorted by timestamp. What they aren't sorted | by is the track they came from so you might get points jumbled up from | different tracks. | | The API deliberately tries to expose limited information about the | points for privacy reasons as some points may have come from traces | that are not public.
Why expose the timestamps of private tracks. Expose the order, but please don't expose the timing - apart from the positions themselves, this is the most private part of the data. Thanks, Robert (Jamie) Munro -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH7S2Rz+aYVHdncI0RAmFbAKD8v03s1x1xh0ed6AsPkuSD27QS6ACgub70 2M8xpalyerW3RC/NwR5oRlo= =19Pp -----END PGP SIGNATURE----- _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
