In R5 the default is now COP90, which gives full worldwide coverage.


The "Draw" option displays the loaded data tiles in the viewport. 

This is useful to see the extent of the data you have loaded. Especially if you are sending your scene to Team Render.  

TIP: If you hold down shift and hover your mouse over the landscape, the data source tile name is displayed in the status bar.



The "Aspect" setting lets you distort the projection.


For larger areas, be sure to only choose the 90m layers. Otherwise it takes longer to download and consumes a lot of resources both locally on your machine, and on our servers.

i.e. a 30m layer is typically 9 times more data than a 90m layer. That means it takes 9 times longer to download, 9 times longer to extract, and consumes at least 9 times more memory.


Once you have downloaded the area you require, you should turn off downloads, by disabling the Allow Downloads option.



Flushing memory clears all data from ram and reloads it.

TIP: If you hold down shift, and press flush, it will force reload of any blocks that may have previously been identified as missing.


Notes 

  1. SRTMv3 only goes up to 60 degrees north/south.
  2. Europe obviously only covers Europe.


Custom Height data


if you have your own data layer you can insert it here.

the feather option defines how your custom height data blends with the base data (i.e. how it transition into SRTMv3 90m)


  • A custom data layer can be an ASC height grid in WGS84 geographic. it must be in geographic coordinates.
  • tiff can be used as well, as long as it is 32 bit, and stripped for any georef data. it needs a matching world file for referencing.
  • You can order custom height data from cinemaplugins.com. Just get in touch or make a support ticket. Let us know what data you need. Best is to make a gpx file for the area you are interested in and send it with your request.


You can use programs such as global mapper to produce custom data, but teaching you how to use those programs is not part of our support.


In R6.225 or greater special handling was added for layers containing bathymetry (values below sea level).

  • When you add a layer, and bathy is detected (values below sea level), it will ask you if you want to treat the layer as bathy. if you answer yes, it sets any values above zero to "nodata", which means they are replaced with normal height data. It also scales up the layer so that it matches the resolution of loaded height data. That can then be expensive on memory if you are working on a huge area.
  • Please be aware of the memory requirements required to ensure that low res bathy can merge well with higher res height data, without nasty artifacts. This requires that a lower res layer be scaled up to match the geographic sampling of the higher res base height data.

  • To remove a layer, delete the filename.
  • You can not change the bathy state. you select this when you add a layers and it stays that way, until you delete the layer.