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
Next revision Both sides next revision
supported_map_formats [2013/03/04 17:40]
admin [GDAL Limitations]
supported_map_formats [2015/09/24 20:57]
admin [Map Formats Supported for Writing]
Line 144: Line 144:
 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 155:
 | 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 =====