While zoomed in very close, I have mistaken the said flight path for border or power line lots of times, so I can imagine the headache if there will be many of these crisscrossing over land data. There's no practical use since we can't route land-based vehicles to them. Licensed pilots know their way anyway, as long as we can give them potential emergency landing areas (open fields & landing strips), as well as give them visual indicators of potential dangers such as their proximity to high towers, power lines & mountains peaks (in case of zero visibility & failing instruments). To the rescue, pilots can reach for their personal gps loaded with osmph. :-)<br>
<br>The ferry routes on the other hand, provides good visual guides of which ports/ferry terminals are connected, and actually used for vehicle routing (eg. roro users). Emergency use: in case of boat accidents and you are on a floating device, you can swim or paddle yourself nearer these ferry routes for greater chance of being seen and rescued. I suggest we collect more of these.<br>
<br><br><div class="gmail_quote">On Mon, Oct 11, 2010 at 1:16 AM, Eugene Alvin Villar <span dir="ltr"><<a href="mailto:seav80@gmail.com">seav80@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi guys,<br>
<br>
There are currently flight paths data in OSM such as the Manila-Davao<br>
path, Manila-Singapore path, Manila-Bacolod path, and maybe others. I<br>
personally don't think these would be useful in OSM per se. Maybe in<br>
another website that collects GPS flight tracks. Take note that<br>
flights do not generally stick to a fixed path and this depends on the<br>
time of day, weather conditions, air traffic levels and other<br>
variables. Thus, a particular path collected by GPS is not necessarily<br>
the "real" path.<br>
<br>
On the other hand, we can say the same thing for ferry routes but we<br>
map these anyway. On the other hand again, ferry routes do not overlap<br>
other data in a confusing way, which flight paths do. (I think I've<br>
seen a node on the Davao-Manila flight path merged with a POI node in<br>
Cavite once before.)<br>
<br>
This issue has been discussed recently in other parts of the OSM community:<br>
<a href="http://help.openstreetmap.org/questions/297/does-it-make-sense-to-upload-aviation-tracks-to-osm" target="_blank">http://help.openstreetmap.org/questions/297/does-it-make-sense-to-upload-aviation-tracks-to-osm</a><br>
<a href="http://www.mail-archive.com/talk@openstreetmap.org/msg33802.html" target="_blank">http://www.mail-archive.com/talk@openstreetmap.org/msg33802.html</a><br>
<br>
What do you guys think? Should we retain and add flight path data or<br>
do we remove them?<br>
<br>
Eugene (osm:seav)<br>
<br>
_______________________________________________<br>
talk-ph mailing list<br>
<a href="mailto:talk-ph@openstreetmap.org">talk-ph@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-ph" target="_blank">http://lists.openstreetmap.org/listinfo/talk-ph</a><br>
</blockquote></div><br>