[OSM-talk] layers for tracks in the API

Jeffrey Martin dogshed at gmail.com
Sat Aug 18 02:06:56 BST 2007


On 8/18/07, Andy Robinson <Andy_J_Robinson at blueyonder.co.uk> wrote:
>
> Jeffrey Martin [mailto:dogshed at gmail.com] wrote:
> >Sent: 17 August 2007 4:54 PM
> >To: Andy Robinson
> >Subject: Re: [OSM-talk] flight paths
> >
> >
> >
> >On 8/17/07, Andy Robinson <Andy_J_Robinson at blueyonder.co.uk> wrote:
> >
> >       Peter Miller wrote:
> >       >Sent: 17 August 2007 1:09 PM
> >       >To: talk at openstreetmap.org
> >       >Subject: [OSM-talk] flight paths
> >       >
> >       >
> >       >
> >       >Anyone who is following the news this week will know that
> aviation
> >is
> >       >currently in the spotlight.
> >       >
> >       >
> >       >
> >       >Are any people doing work on flight-paths? I for one would be
> >interested to
> >       >know which airport all the planes that pass overhead are coming
> from
> >and
> >       >for the airports that have planned expansion it would be good to
> be
> >able to
> >       >plot the paths radiating from them so people can see if they are
> >affected
> >       >by the work.
> >       >
> >       >
> >       >
> >       >I guess a specialist flight map rendering would be very helpful
> and
> >       >encourage data collection.
> >       >
> >       >
> >       >
> >       >I believe that GPS works on flights and can be used but that
> flight
> >path
> >       >data might also be available from enthusiasts.
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >Any thoughts?
> >       >
> >
> >
> >       Right from the early days of OSM we had a few flight path gps
> traces
> >       uploaded to the server and it was decided that these were a bad
> thing
> >       because they confuse the hell out of everyone when trying to edit
> map
> >data!
> >       The consensus at the time was that while this information was of
> >interest it
> >       really wasn't part of a "streetmap" emphasis and therefore ought
> to
> >be set
> >       up as a project in its own right.
> >
> >       Cheers
> >
> >       Andy
> >
> >       Andy Robinson
> >       Andy_J_Robinson at blueyonder.co.uk
> >
> >
> >
> >       _______________________________________________
> >       talk mailing list
> >       talk at openstreetmap.org <mailto:talk at openstreetmap.org>
> >       http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
> >
> >
> >
> >I might be doing something wrong but when I download with JOSM it gathers
> >all the tracks together.
> >If it downloaded each track as a separate layer then it would be easy to
> >keep the aircraft tracks separate
> >for a future project.
> >
> >On a side note I would like more tools in JOSM to manipulate the track
> >data. If I could highlight the points in time order then I could see when
> I
> >went under the bridge and when I went over it for example.
>
> No, that's correct. Via the API, all points come in blocks, normally
> delivered in logical order but not with any timestamps or other
> information.
> You can open your own GPX files (or download the original files from OSM
> if
> they were made public) if you want to keep them on separate layers. With
> the
> original GPX files you can effectively do more in JOSM than with the data
> via the API.
>
> Cheers
>
> Andy
>
> Andy Robinson
>
>
> I suppose there's a reason I can't download them a separate files. I
really don't want to learn
the API, but I would like to see the overall system set up for remote
collaboration. I have a vision
where other people map the data I collect in Korea. It may never happen, but
I would like the
overall system to support it without having to email waypoint and track
files to people.

When you look at the listing of tracks on the server it animates the points
in little sections. Could
I suppose downloading those sections as layers would require major API
changes.

-Jeff

-- 
http://bowlad.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20070818/469285e4/attachment.html>


More information about the talk mailing list