[OSM-talk] relating trace points to gpx files

[Etienne]

Andrew
This sounds like a problem that JOSM can help with.

You can load all of your gpx files into JOSM and then view them individually
or superimposed on each other.  If your files contain erroneous track points
then they should show up pretty well in JOSM.

Once you've got JOSM then you may find that it is a better tool than the
applet for editing with.  The absence of an underlying satellite image is at
first disconcerting, but you quickly find, as your confidence in editing
grows, that you don't need it.

For privacy reasons, once tracklogs have been uploaded to the server it is
not possible to tell which points come from which log file, unless the user
has explicity marked them as public, and even then you can only get this
information by finding their original track log file, not via the applet.

BTW I mapped some bits of Sydney during my recent visit.  There also seems
to be someone else who is doing a bit there as well.  Maybe you should start
an Australia wikiproject on the wiki?

Etienne


On 7/10/06, Andrew Loughhead <andrew at incanberra.com.au> wrote:
>
> Is there any way I can find which gpx file relates to some specific
> trace points?  I have uploaded a few files at once, which I believed to
> be quite clean.  In the applet I see all the nice clean data, but there
> are also some extra points which I think are garbage.  I am fairly
> confident there is no one else uploading data for my suburb (or city for
> that matter) so I don't think the other points are someone else's.  I've
> tried finding these bad points in my local copies of the gpx files with
> no luck, so I want to know if the server can tell me.
>
> cheers
> Andrew.
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20060710/e41e0f2e/attachment.html>