Exporting Geotiffs

Hi all,

I’m using USGS geotiffs to create real world terrain conditions for a rail simulator, but I want to leverage the noise functions of world machine to increase their resolution. They’re currently only about 90m DEMs. If I can import a geotiff and modify the terrain, can I then export that modified geotiff back out again while saving the meta and elevation information?

Hi there,

Currently WM can’t save the geotiff metadata – there is only one format that supports metadata pass-through and that is the BT format. If you have access to a program like Global Mapper, you can convert your geotiff terrain into a BT and use that.

It would be useful to have geotiff pass-through as well though, so I will put that on the feature backlog for possible inclusion in a future version!

Also in this vein it would be great to get geolocated DEM ability in the file input device so that it can automatically be placed at the correct real world coordinates in WM, with the correct elevation scale and height/width through the meta data. This is currently one of the most painfull things in terms of workflow from a gis package to WM.

Add it to the wish list :slight_smile:

1 Like

Will WM ever support the import and export of 32bit BT or Geotiff formats? We really need floating point height data for real world rail simulation.

Thanks

Hi there,

WM supports 32bit (floating-point) BT import and WM saves BTs as 32bit float. Are you having problems with import/export?

Dear WM,

when importing a 32bit geotiff i do not get in any height info, but blank white rectangle.
I have checked the geotiff with global mapper as well as daylon leveller. This file is ok.

Is there a trick with the 32bit format?

thanx

Huh. I can sucessfully import 32bit geoTIFFs here (although as mentioned above, without their georeferencing info) – can you post an example of the file that you’re having problems with?

I believe I understand a situation where you would see all-white; if your 32bit geotiff contains values above 1.0, WM will clamp them to 1.0; so if you’re storing heights in straight meters, they will all be clipped to white.

It is important to preserve all height values between 0…1.0 exactly as they are, but I can add a new code path in the next update (which is coming out very shortly) that will rescale the input if it goes over 1.0.