• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Loowit Sceneries update - FS Resample / QGIS issues, etc.

Messages
96
Country
us-washington
So, I'm back after a hiatus, mostly brought forth by PC woes but also by research. I have a much better laptop now, and there's been some progress made to the project regarding Mount St. Helens and its pre-1980 appearance.

Last week, in what I thought was never going to ever happen, the USGS released a 10-meter mesh of Mount St. Helens and the entire Spirit Lake/North Fork Toutle River area. The mesh was an undertaking between the USGS and a student intern from the Portland (OR) Community College GIS and Geospatial Technologies program. The release of this mesh solves much of the issues I had been having previously with flattening the valley slope, and presents a much higher detail fidelity around Spirit Lake.

HOWEVER.
In the compilation of the mesh for FSX, there are, or IS, a problem. After compiling for FSX, where there is no mesh data in the GeoTIFF, it appears as a rather large "plateau." I could not remember how I resolved this issue nor could I find it in any previous thread.


Attached are screenshots.
The native projection is NAD83 UTM10, and was reprojected in QGIS to EPSG:4326 WGS84. For some reason, attempting to compile the BGL using the native NAD83 UTM10 GeoTiff results in Resample.exe failing to do so.


Also attached is the code in the *.INF file. These parameters worked in the past, but aren't now. Any suggestions?




[Source]
Type=GeoTIFF
Layer=Elevation
SourceDir="."
SourceFile="MSH_Pre_1980_test3.tif"
MinValidValue=344
NullCellValue=-32767

[Destination]
DestDir="."
DestBaseFileName="MSH_Pre_1980_Test"
DestFileType=BGL
LOD=6,16
FractionBits = 3
BaseValue = 1000


FSX1MSH.jpg
FSX2MSH.jpg
FSX2MSH_QGIS.jpg
 
Hi,

I think you will have to set the no data value in your INF file. So check which value is used in the GeoTIFF to specify no data and make sure you have that configured. That should probably fix it.
 
Hi,

I think you will have to set the no data value in your INF file. So check which value is used in the GeoTIFF to specify no data and make sure you have that configured. That should probably fix it.
I have tried setting no data parameter to 0.00 in QGIS during the export but all that does, is set the areas outside of the mesh itself to sea level, and instead of the slight cliffs on the west flank (seen above) they're now 4,000 foot high cliffs.

Under the no data column in QGIS for the reprojected mesh, it displays as 3.4e+38, which makes it even more confusing.
 
I'm not talking about no data in QGIS. You need to tell resample in the INF file what the no data value of your TIF is. Else it can not handle it correctly.
 
I'm not talking about no data in QGIS. You need to tell resample in the INF file what the no data value of your TIF is. Else it can not handle it correctly.
I did that in the INF file in several test attempts but was unsuccessful, hence why I posted.
 
You would have to check in QGIS what the value is and then put that value in your inf file. In the INF file you posted above I don't see any null value specified.
 
Back
Top