Differences

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

--- supported_map_formats [2012/10/21 19:05]
admin [Supported Map Formats]
+++ supported_map_formats [2013/03/29 16:14]
admin [GDAL Limitations]
@@ 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 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.  |
+| @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.
 ===== Dinamica EGO Limitations =====
@@ Line 167: / Line 168: @@
 It is important to observe some additional details concerning how map reading behaves in the current Dinamica EGO version:
-When the map projection is not found, the map projection is left undefined. Previous Dinamica EGO versions (Dinamica EGO 1.8) assumes a LOCAL projection in these cases.
+When the map projection is not found, the map projection is left undefined. Previous Dinamica EGO versions (Dinamica EGO 1.8) assume a LOCAL projection in these cases.
-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.