Hello allI am a new user of FG from Argentina. I use to flight around Buenos Aires an I am interesting in some specific sceneries like SABE, SAEZ, SAZM, SAAR.The world scenery of FG has a bug in SABE. The airport is in the middle of River. Does anybody know how to fix this?Thera are several good sceneries developed for MSFS. Is there any possibility to import those sceneries into FG?

>Hello all>>I am a new user of FG from Argentina. I use to flight around>Buenos Aires an I am interesting in some specific sceneries>like SABE, SAEZ, SAZM, SAAR.>>The world scenery of FG has a bug in SABE. The airport is in>the middle of River. Does anybody know how to fix this?this is most likely not caused by incorrect airport coordinates, but rather my mismatching data for the corresponding GIS layers used to create the corresponding scenery tiles-in fact, this can be considered to be a known problem for several areas covered by FG scenery.>Thera are several good sceneries developed for MSFS. Is there>any possibility to import those sceneries into FG? sorry, in general:no-at least not easily-neither from a technical point of view, nor from a legal one (licensing).

>>Hello all>>>>I am a new user of FG from Argentina. I use to flight around>>Buenos Aires an I am interesting in some specific sceneries>>like SABE, SAEZ, SAZM, SAAR.>>>>The world scenery of FG has a bug in SABE. The airport is in>>the middle of River. Does anybody know how to fix this?>>this is most likely not caused by incorrect airport>coordinates, but rather my mismatching data for the>corresponding GIS layers used to create the corresponding>scenery tiles-in fact, this can be considered to be a known>problem for several areas covered by FG scenery.Due to the problem is in the coast line, I guess the solution is to develope a new scenery for SABE. I don't have great experience in development but I can contribute with some information of the area. Furthemore, I will try to do it myself using (if existed) some tool to create sceneries in FG, and of couse with some help of someone with more experience.I would apreciate some tips to star...>>>Thera are several good sceneries developed for MSFS. Is>there>>any possibility to import those sceneries into FG? >>sorry, in general:no-at least not easily-neither from a>technical point of view, nor from a legal one (licensing).

>Due to the problem is in the coast line, I guess the solution>is to develope a new scenery for SABE.depending on how exactly these scenery errors are caused, this issue may either be automatically resolved as soon as the FlightGear scenery is rebuilt, or you might in fact have to manually adjust the data from the GIS layers.>I don't have great>experience in development but I can contribute with some>information of the area. Furthemore, I will try to do it>myself using (if existed) some tool to create sceneries in FG,>and of couse with some help of someone with more experience.>>I would apreciate some tips to star...In general, FlightGear scenery is a pretty static thing-that is, there is currently no easy way to modify the scenery and have these changes take effect in the simulator without rebuilding all affected scenery tiles, which in turn would require the "terragear" tool suite.By using "terragear" as search query, you should be able to come up with several relevant discussions when searching the mailing list archives.Alternatively, or additionally, you may want to consider subscribing to the FlightGear mailing lists, where your questions are likely to be answered more promptly and also more competently.http://www.flightgear.org/mail.html

>>Due to the problem is in the coast line, I guess the solution>>is to develope a new scenery for SABE.>>depending on how exactly these scenery errors are caused, this>issue may either be automatically resolved as soon as the>FlightGear scenery is rebuilt, or you might in fact have to>manually adjust the data from the GIS layers.The issue is more complex than it looks at the first sight.There are two different types of coastlines available that provide world-coverage and could be used for building the FlightGear Scenery. One is a 'standalone' coastline that is pretty accurate and is named GSHHS. The other one is the the outline of political boundaries that come with the VMap0 landcover data which is being used to add different cover types to the SRTM-based terrain.Now if you would use the GSHHS coastline you'd experience gaps between the coastline and the available landcover data. Because of this reason the Scenery has been built with the (inaccurate) VMap1-based coastline.I was lucky to find supporters at the OSGeo project to host my database of the landcover data we currently have - as well as folks from GIS-related projects who intend to provide tools to us that allow us to fix issues in the current set of data. You'll find the current collection of landcover data here: http://flightgear.telascience.org/VMap0 is a dataset with worldwide coverage and has been used to build the latest scenerey. VMap1 is a dataset that's available only for parts of the US and which I expect to get merged in the near future.GSHHS provides some coastlines, SWBD is the coastline extracted from the SRTM mission (heavily inaccurate) and MGRS is a simple grid.Select VMap1: landcover to see the coastline currently in use.Getting the landcover data fixed around the world as a looong way down the road. We hope to be able to offer some convenient tools in a few months that allow everybody to participate in this effort.Martin.

>I was lucky to find supporters at the OSGeo project to host my>database of the landcover data we currently have - as well as>folks from GIS-related projects who intend to provide tools to>us that allow us to fix issues in the current set of data.>You'll find the current collection of landcover data here:>> http://flightgear.telascience.org/Thanks and grear application !!!>>VMap0 is a dataset with worldwide coverage and has been used>to build the latest scenerey. VMap1 is a dataset that's>available only for parts of the US and which I expect to get>merged in the near future.GSHHS provides some coastlines, SWBD>is the coastline extracted from the SRTM mission (heavily>inaccurate) and MGRS is a simple grid.>Select VMap1: landcover to see the coastline currently in>use.As I could see FG is using VMAP0 coastline and SABE is in fact in the middle of the river. GSHHS is more accurate as you said. SABE is in its real place just next to the river and there are others details of the coast of Buenos Aires.>>Getting the landcover data fixed around the world as a looong>way down the road. We hope to be able to offer some convenient>tools in a few months that allow everybody to participate in>this effort.I got it. So I have to wait... Thanks again for your help.Martin

>As I could see FG is using VMAP0 coastline and SABE is in fact>in the middle of the river.Yup, I guess you'll see similar effects around the world. We know some places in Canada that suffer from the same effect.>>Getting the landcover data fixed around the world as a looong>>way down the road. We hope to be able to offer some convenient>>tools in a few months that allow everybody to participate in>>this effort.>>I got it. So I have to wait... Thanks again for your help.I'm sorry that you have to wait, but actually we're unable to fix this in a short timeframe. Just to give you a rough idea of what we're talking about: The database behind this Mapserver contains about 7 GByte of geodata in more than 12 million objects (points, lines, polygons).There is simply no "quick fix" for dealing with this sort of inaccuracies and the infrastructure that allows public participation in improving the data is still in the works. Actually we have to implement something like versioning of database table contents - not impossible but a tricky task in such an environment .... and our manpower is limited, as always,Martin.