For several months I've been adding UK airfields to FSX. Mostly farm strips, but a few bigger ones. I never knew the UK had so many airfields. It probably has the highest density of airfields/airstrips in the world. For example, there are more than a dozen within 5 miles of where I live! Only two of which were stock FSX airfields. This is why I started this mad project. I wanted to fly to my local airstrips.
To add an airfield, I first make a rough sketch of using google earth. The sketch has lines for the runways and taxiways, and polygons for the aprons and hanger foundations. In addition I add a polygon for the area that I want to flatten and remove the auto gen scenery, and another for the area around the airfield, but that is for clearing the scenery (not for flattening it) .
I the process the kml file to turn it into an FSX airport XML file using a program that I wrote. The boundary and area polygons are saved as aprons. I then fettle that using Tim Arnot's airport design editor. I replacing my place holder aprons with polygons with airport background polygons. I then add hangers where needed and add some extra rectangle polygons on the extended centerline of the runways to remove the trees. Finally I add a windsock.
It works for me.
Hello:
Just a quick clarification as I review this thread (14 pages long as of today
).
Tim Arnot (in addition to being a "great guy") ...is the author of Plan-G, which is now being updated for use with MSFS.
BTW: In Google Earth it is indeed possible to trace over the imagery and output KMZ or KML format GIS data files which can be processed via pre-FSX-KML and further edited into FSX scenery objects via FSXKML, and then compiled via SDK SHP2VEC.
Note that the GIS projection format output by Google Earth is always in "
EPSG:4326" <aka Geographic (Lat - Lon) projection, WGS84 datum>, which happens to be the exact same GIS format required by SDK SHP2VEC.
However,
EPSG:4326 is a "
warped" GIS format, and should
not be used as source code for vertices when creating Airport objects via XML code, nor should it be used as graphical vector background images in a 3D modeling application to create 3D scenery objects etc..
For such Google output KMZ or KML files be used as source code for vertices when creating Airport objects via XML code, or as graphical vector background images in a 3D modeling application to create 3D scenery objects etc.,
they must first be re-projected in a GIS application ...from their existing
EPSG:4326 to a
non-warped GIS format
EPSG:3857 otherwise required for those aspects of FS scenery development to match IRL objects.
en.wikipedia.org
wiki.openstreetmap.org
Saved screenshots and exported JPGs output by Google Earth are AFAIK, always in a
non-warped GIS format, thus they
are compatible with use as background images to trace over the imagery in a airport design utility such as ADE, or in a 3D modeling application create 3D scenery objects etc.
GaryGB