Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
supported_map_formats [2015/09/24 20:57]
admin [Map Formats Supported for Writing]
supported_map_formats [2017/05/23 00:06] (current)
hermann [Additional Notes]
Line 1: Line 1:
 ====== Supported Map Formats ====== ====== Supported Map Formats ======
  
-Dinamica EGO 2.0 and above delegates reading and writing most map formats to the [[http://​www.gdal.org|GDAL library]]. This allows Dinamica EGO to handle several previously unsupported file formats.+Dinamica EGO delegates reading and writing most map formats to the [[http://​www.gdal.org|GDAL library]]. This allows Dinamica EGO to handle several previously unsupported file formats. 
 ===== Map Formats Supported for Reading ===== ===== Map Formats Supported for Reading =====
  
Line 172: Line 173:
 The behavior concerning the omission of cell resolution is also different in the current version. So, when the cell dimension is not defined, a one-meter resolution (or one degree, depending on the map projection used) is assumed. Previously, Dinamica would assume a 100 meter or a one degree resolution, depending on the map projection used. The behavior concerning the omission of cell resolution is also different in the current version. So, when the cell dimension is not defined, a one-meter resolution (or one degree, depending on the map projection used) is assumed. Previously, Dinamica would assume a 100 meter or a one degree resolution, depending on the map projection used.
  
-It is only possible to load maps represented by 8, 16 or 32 bits per cell. Other cell types are not supported.+It is only possible to load maps represented by 8, 1632 or 64 bits per cell. Other cell types are not supported.
  
 And an additional note concerning map writing: some formats do not support natively all the informations about map projections,​ map registration,​ cell resolution, layer names, category names etc. To workaround this, the GDAL library automatically writes an additional PAM XML file containing all the informations that can not be stored in the map file itself. This PAM XML is automatically processed when the map is loaded again in Dinamica EGO. And an additional note concerning map writing: some formats do not support natively all the informations about map projections,​ map registration,​ cell resolution, layer names, category names etc. To workaround this, the GDAL library automatically writes an additional PAM XML file containing all the informations that can not be stored in the map file itself. This PAM XML is automatically processed when the map is loaded again in Dinamica EGO.