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 [2013/03/04 17:40]
admin [GDAL Limitations]
supported_map_formats [2017/05/23 00:06]
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 144: Line 145:
 The support to Arc/Info ASCII Grid (.asc) in GDAL is read only. So, Dinamica EGO provides the writing capability itself. This format can read images using [[Cell Type Type|cell types]] "​Signed 32 Bit Integer"​ and "IEEE 754 32 Bit Real". All cell types can be written, but they are automatically converted back to one of those formats next time Dinamica EGO reads the image again. The support to Arc/Info ASCII Grid (.asc) in GDAL is read only. So, Dinamica EGO provides the writing capability itself. This format can read images using [[Cell Type Type|cell types]] "​Signed 32 Bit Integer"​ and "IEEE 754 32 Bit Real". All cell types can be written, but they are automatically converted back to one of those formats next time Dinamica EGO reads the image again.
  
-The current ERMapper (.ers) support in GDAL ignores class names. To workaround this limitation, support to reading and writing this file format is provided by Dinamica EGO itself.+The current ERMapper (.ers) support in GDAL ignores class names. To workaround this limitation, support to reading and writing this file format is [[ermapper_format|provided by Dinamica EGO itself]].
  
 ===== GDAL Limitations ===== ===== GDAL Limitations =====
  
-The GDAL implementation (and some times the underlying file format) imposes limitations ​on the representation of projections,​ layer names, category names and their corresponding colors. Some of these limitations and their corresponding workarounds are listed in the table below:+The GDAL implementation (and some times the underlying file format) imposes limitations ​to the representation of projections,​ layer names, category names and their corresponding colors. Some of these limitations and their corresponding workarounds are listed in the table below:
  
 ^ Limitation ^ Workaround ^  ^ Limitation ^ Workaround ^ 
Line 155: Line 156:
 | Several file formats do not support storing category colors. ​ | Use a [[supported_map_formats#​Virtual Format|VRT file]] or an auxiliary PAM XML file to keep this information. The ERMapper file format has the best support to category names and colors. ​ | | Several file formats do not support storing category colors. ​ | Use a [[supported_map_formats#​Virtual Format|VRT file]] or an auxiliary PAM XML file to keep this information. The ERMapper file format has the best support to category names and colors. ​ |
 | Several file formats do not support the storage of layer names. ​ | Use a [[supported_map_formats#​Virtual Format|VRT file]] or an auxiliary PAM XML file to keep this information. The ERMapper file format also has support to layer names. ​ | | Several file formats do not support the storage of layer names. ​ | Use a [[supported_map_formats#​Virtual Format|VRT file]] or an auxiliary PAM XML file to keep this information. The ERMapper file format also has support to layer names. ​ |
-| The categories must start from 0 and their definition must be contiguous. ​ | Unfortunately,​ the only way to workaround this limitation is defining dummy categories (Dinamica EGO does this when representing non-contiguous categories in a GDAL supported format) or using the ERMapper file format. ​ | +@yellow:The categories must start from 0 and their definition must be contiguous. ​ | Unfortunately,​ the only way to workaround this limitation is defining dummy categories (Dinamica EGO does this when representing non-contiguous categories in a GDAL supported format) or using the ERMapper file format. ​ | 
-| Some formats ​using specified number of bits per sample, do not preserve category colors.  | Unfortunately,​ the only way to workaround this limitation is using a different format or choosing a number of bits per sample that does not have this limitation for a given format. For example, Geotiff format only present ​category colors when 8 bits per pixel is used.  | +@yellow:Some formats ​do not preserve category colors when a specified number of bits per sample ​is used.  | Unfortunately,​ the only way to workaround this limitation is using a different format or choosing a number of bits per sample that does not have this limitation for a given format. For example, Geotiff format only stores ​category colors when the cell type is 8 bits.  |  
 +| @pink:​Categories represented by negative values are not supported. ​ | Unfortunately,​ there is no way to workaround this limitation, except by avoiding the use of negative categories.  |
  
 The ERMapper file format is handled by Dinamica EGO itself and not delegated to the GDAL library. For that reason, the PAM XML file can not be used with this format. The ERMapper file format is handled by Dinamica EGO itself and not delegated to the GDAL library. For that reason, the PAM XML file can not be used with this format.
- 
 ===== Dinamica EGO Limitations ===== ===== Dinamica EGO Limitations =====
  
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.