GeoTIFF GDAL_NO_DATA_VALUE anomaly

tjhb
Global Mapper UserTrusted User
Hello Mike,
There's an anomaly with the interpretation and display of some source tiles of SRTM v4.1 (from CGIAR).
In general, sea is encoded as missing data. For most tiles, the GDAL_NO_DATA_VALUE value is -32768. These tiles show correctly.
But for 25 tiles, all of which show only a small, low island surrounded by sea, the GDAL_NO_DATA_VALUE is 255. (Perhaps someone was determined to use unsigned integers for these tiles somewhere in the workflow.)
Global Mapper interprets this value correctly when calculating metadata (since the maximum elevation calculated for these tiles is always less than 255).
But it seems to ignore it for the display of data (and for colouring and shading). The 255 values are all shown as valid elevations, rather than as sea.
Here is one of the 25 tiles.
srtm_20_18.zip
I had always assumed it was a data fault at the CGIAR end, but apparently it is just an unusual encoding.
Regards,
Tim Baigent
There's an anomaly with the interpretation and display of some source tiles of SRTM v4.1 (from CGIAR).
In general, sea is encoded as missing data. For most tiles, the GDAL_NO_DATA_VALUE value is -32768. These tiles show correctly.
But for 25 tiles, all of which show only a small, low island surrounded by sea, the GDAL_NO_DATA_VALUE is 255. (Perhaps someone was determined to use unsigned integers for these tiles somewhere in the workflow.)
Global Mapper interprets this value correctly when calculating metadata (since the maximum elevation calculated for these tiles is always less than 255).
But it seems to ignore it for the display of data (and for colouring and shading). The 255 values are all shown as valid elevations, rather than as sea.
Here is one of the 25 tiles.
srtm_20_18.zip
I had always assumed it was a data fault at the CGIAR end, but apparently it is just an unusual encoding.
Regards,
Tim Baigent
Comments
-
Tim,
I took a look and found that the GDAL_NO_DATA_VALUE was only being obeyed when it was lower that the valid range and not above it. I've got it fixed now. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper14.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v14.xx installation folder to give it a try. If you are using the 64-bit v14 version there is a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper14_64bit.zip .
Thanks,
Mike
Global Mapper Guru
gmsupport@bluemarblegeo.com
http://www.bluemarblegeo.com/ -
Thanks very much Mike. Perfect now.
Categories
- 12.5K All Categories
- 5.5K Features Discussion
- 314 Downloading Imagery
- 1.3K Elevation Data
- 377 Georeferencing Imagery Discussion
- 611 GM Script Language
- 50 User Scripts
- 112 GPS Features
- 397 Projection Questions
- 803 Raster Data
- 1.3K Vector Data
- 6.5K Support
- 161 Announcement and News
- 893 Bug Report
- 557 SDK
- 1.2K Suggestion Box
- 3.7K Technical Support
- 542 Other Discussion
- 128 GIS Data Sources
- 26 Global Mapper Showcase
- 229 How I use Global Mapper
- 104 Global Mapper Forum Website