Hi, We have other nav data - contributing it to OSM...hrm.
http://x-plane.org/home/robinp/FileDef.htm My immediate concern would be: the data is all GPL last I checked. Now..I have no idea what it MEANS when you have GPL on a non-code work (which I think is the main reason why GPL != CC-BY-SA) but now I am rapidly spiraling into osm-legal territory. Bottom line is you'd have to work out licensing. The data is a combination of imports and processing by Robin Peel (who runs the data) and a bunch of user contributions). Now I can talk a little bit more about suitability... - Some of the data you might get (e.g. airways) are very large in physical size (but small in node count). While I point to a "sectional map" as a mapping use of OSM, the truth is that X-Plane's OSM needs are very much tied to the "ground" map because that's what we visualize. - Most of the data represents individual "features" in the real world fairly well, e.g. a VOR transmitter is represented by the lat/lon location of the antenna, more or less. But airports are a little bit tricky - we have always supported (1) the overlapping of taxiway polygons and (2) no metadata on those polygons. So you could use user contributed apt.dat layouts to draw a potentially very accurate image of the "ground footprint" of the airport, but you would not be able to apply meta data like "that area of pavement is taxiway B". In fact, that meta data problem is very difficult because often the taxiways are just names and lines painted on a huge monolithic paved area. The newest apt.dat 850 format solves this at a very low level, by giving authors control over signs, lines, and pavement, rather than providing premade primitives. We did this because there is just so much real-world variability to markings. (We still use high level primitives for runways, that is, one runway makes all its lights, signs, pavement, and lines.) cheers ben OJ W wrote: > How about this for a link showing some of the features displayed on > typical charts? > > http://www.avn.faa.gov/index.asp?xml=naco/online/aero_guide > > Does X-plane/flightgear have any radionavigation data they could add > to the chart? OSM itself only has airports+runways at the moment. > > > > On Sat, Nov 1, 2008 at 12:52 PM, Iván Sánchez Ortega > <[EMAIL PROTECTED]> wrote: >> El Sábado, 1 de Noviembre de 2008, spaetz escribió: >>>> - Somehow add visual feedback to the final map renders to validate user >>>> data. Since our data is appropriate to aeronautical maps this wouldn't >>>> necessarily fit well with existing infrastructure. >>> an aeronautical layer via the [EMAIL PROTECTED] infrastructure? >> Sounds cool. Now, somebody please explain how an "Aeronautical chart" works: >> >> http://en.wikipedia.org/wiki/Aeronautical_chart >> http://www.skyvector.com (slippy propietary aero chart) >> >> Providing such charts via [EMAIL PROTECTED] seems like a great idea - how >> difficult would it >> to create the stylesheets for osmarender? >> >> -- >> ---------------------------------- >> Iván Sánchez Ortega <[EMAIL PROTECTED]> >> >> Proudly running Debian Linux with 2.6.26-1-amd64 kernel, KDE 3.5.9, and PHP >> 5.2.6-5 generating this signature. >> Uptime: 13:47:42 up 72 days, 2:43, 2 users, load average: 0.69, 0.99, 0.64 >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openstreetmap.org/listinfo/dev >> >> > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > -- Scenery Home Page: http://scenery.x-plane.com/ Scenery blog: http://xplanescenery.blogspot.com/ Plugin SDK: http://www.xsquawkbox.net/xpsdk/ X-Plane Wiki: http://wiki.x-plane.com/ Scenery mailing list: [EMAIL PROTECTED] Developer mailing list: [EMAIL PROTECTED] _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
