Scenery Missing Data

[John775]

One of the sceneries that I'm working on, looks like there is some missing data from the .bil files downloaded from Earth Explorer, is there a way that this missing data can be patched and if so how, the screenshot below is what I see, the scenery is flyable in Condor and have taken a couple of screenshots but can't find where they are located, I'm running Condor2 on MacBook Pro on BootCamp, any help will be welcome.

[John775]

Here is another screenshot but much closer where you can see the height.

[Andy1248]

Use the height flatten tool to set the terrain at the height you want. I.e fill the hole.

[John775]

Use the height flatten tool to set the terrain at the height you want. I.e fill the hole.

Ok, thank you, just thought that there maybe a quicker way, like when you can patch missing data when using 3dem for when designing V1 scenery, as 3dem is unable to handle .bil files.

[Andy1248]

Although my posted fix was to use the flatten tool to fill in the missing data, but on some sceneries this missing data is quite extensive and the flatten tool method would result in a too big a task.

Is there any other sources of SRTM data at 1 arc second that has these areas patched/corrected.

Or is there another method being used by scenery developers to correct this.

The USGS terrain source as recommended by the Condor Guide has .bil files data with lots of height errors, mountainous areas are especially bad.

[Andy1248]

I think that I may have found a way round this. 30 metre terrain can be downloaded from here:

http://dwtkns.com/srtm30m/

It is from a NASA source and requires a Nasa Earthdata login. The Terrain data is in .hgt format.

.hgt file can be imported into QGIS provided the Point Sampling Tool is loaded.

The process then onward is the same as per the Condor Landscape guide.

I have not yet found any voids in the terrain. The area I am working as a test scenery is the Provence area.

[GregHart1965]

Thanks for this Andy. Coming back to scenery making (sucker for punishment! ) so will check this out.
The Aster GDem stuff is very bumpy and rough, although it may be the resampling method that is causing it so will investigate that and this data source.