Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
supported_map_formats [2016/07/12 03:46] hermann |
supported_map_formats [2024/05/29 18:59] (current) hermann [GDAL Limitations] |
||
|---|---|---|---|
| Line 157: | Line 157: | ||
| | 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. | | ||
| | @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: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. | | + | | @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 unsigned. | |
| | @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. | | | @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. | | ||
| Line 173: | 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, 16, 32 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. | ||