Skip to content

Working with non cloud-optimized datasets (e.g. 3DEP 1m DEMS, NEON) #66

@scottyhq

Description

@scottyhq

Just documenting something to be aware of:

our loading functions are designed to get subsets from cloud-hosted files, unfortuntaley these are not always COGs (https://github.com/OSGeo/gdal/blob/master/swig/python/gdal-utils/osgeo_utils/samples/validate_cloud_optimized_geotiff.py)

wget https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/1m/Projects/CO_WestCentral_2019_A19/TIFF/USGS_1M_12_x76y427_CO_WestCentral_2019_A19.tif

python validate_cloud_optimized_geotiff.py USGS_1M_12_x76y427_CO_WestCentral_2019_A19.tif

USGS_1M_12_x76y427_CO_WestCentral_2019_A19.tif is NOT a valid cloud optimized GeoTIFF.
The following errors were found:
 - The offset of the main IFD should be 8. It is 143211950 instead
 - The offset of the IFD for overview of index 0 is 13246, whereas it should be greater than the one of the main image, which is at byte 143211950

They are at least tiled with overviews, but there may be a lot of network requests / slow performance, select metadata from gdalinfo below:

Driver: GTiff/GeoTIFF
Files: USGS_1M_12_x76y427_CO_WestCentral_2019_A19.tif
Size is 10012, 10012
Coordinate System is:
PROJCRS["NAD83 / UTM zone 12N",

Image Structure Metadata:
  COMPRESSION=LZW
  INTERLEAVE=BAND
  PREDICTOR=3

Band 1 Block=256x256 Type=Float32, ColorInterp=Gray
  Min=1678.988 Max=1893.657 
  Minimum=1678.988, Maximum=1893.657, Mean=1765.101, StdDev=41.513
  NoData Value=-999999
  Overviews: 5006x5006, 2503x2503, 1252x1252, 626x626, 313x313

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions