• 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.

10m terrain mesh for MSFS

I merged all the rasters and split them into two files, reprojecting into WGS84. The resolution is much better than stock P3D but it seems like the elevation is off. The Mediterranean shows 14 feet above sea level, and when I took off from Bar Yehuda I was in a hole. I wouldn't think high tide would be a 14 foot difference, but I guess a potential option would be to see if it's possible to subtract 14 feet from the dataset, but there most likely something else going on.

Have you run into anything similar?
 
crushnik said:
I merged all the rasters and split them into two files, reprojecting into WGS84. The resolution is much better than stock P3D but it seems like the elevation is off. The Mediterranean shows 14 feet above sea level, and when I took off from Bar Yehuda I was in a hole. I wouldn't think high tide would be a 14 foot difference, but I guess a potential option would be to see if it's possible to subtract 14 feet from the dataset, but there most likely something else going on.

Have you run into anything similar?
Click to expand...

This may be an idea for @Paavo if he can consider this option (Geoid vs Ellisoid) into MSFS Toolkit


altTypeThis is used to determine the referential for the alt field.Enum:
GEOID
ELLIPSOID		No

From Alaska Satellite Facility

"DEM Information​

What is a Digital Elevation Model?​

A digital elevation model (DEM) is the digital representation of the land surface elevation with respect to a given reference datum. DEM is frequently used to refer to any digital representation of a topographic surface and is the simplest form of digital representation of topography. DEMs are used to determine terrain attributes such as elevation, slope and aspect at any location.

Why does the DEM included with ASF’s ALOS PALSAR RTC product show different elevations than the source DEM (SRTM or NED) over the same area?​

Most DEMs are geoid-based and require a correction before they can be used for terrain correction. The DEM included in an ASF RTC product was converted from the orthometric height of the source DEM to ellipsoid height using the ASF MapReady geoid_adjust tool. This tool applies a geoid correction so that the resulting DEM relates to the ellipsoid. An online tool is available that computes the height of the geoid above the WGS84 ellipsoid, and will show the amount of correction that was applied to the source DEM used in creating an RTC product."

https://asf.alaska.edu/wp-content/uploads/2019/05/sar-faq-dem.png
 
Last edited:
You must log in or register to reply here.
Back
Top