Currently, iRIC is implemented with the assumption that GeoTIFF are imported for grid attributes with real value type, like elevation or rainfall.
But sometimes we want to import GeoTiff into integer value like:
0 = Normal cell
1 = Obstacle
or,
0 = No vegetation
1 = Vegetation
In such cases, it often happens that GeoTiff stores integer values at each cells, but the value table is not the same with the definition in solver definition file. For example, GeoTIFF stores ground surface usage as values 0 to 10 (ex. 0 = undefined, 1 = city, 2 = river or ocean, 3 = vegetation, ...), and use it for "vegetation" attribute.
To import GeoTiff data as geographic data like this, we need to specify mapping about GeoTIFF values and grid attribute values. like:
0 -> Normal cell
1 -> Obstacle
or
3 -> Vegetation
others -> No vegetation
We add the function to specify mapping when importing GeoTIFF to such grid attributes.
Currently, iRIC is implemented with the assumption that GeoTIFF are imported for grid attributes with real value type, like elevation or rainfall.
But sometimes we want to import GeoTiff into integer value like:
or,
In such cases, it often happens that GeoTiff stores integer values at each cells, but the value table is not the same with the definition in solver definition file. For example, GeoTIFF stores ground surface usage as values 0 to 10 (ex. 0 = undefined, 1 = city, 2 = river or ocean, 3 = vegetation, ...), and use it for "vegetation" attribute.
To import GeoTiff data as geographic data like this, we need to specify mapping about GeoTIFF values and grid attribute values. like:
or
We add the function to specify mapping when importing GeoTIFF to such grid attributes.