Opened 9 years ago
Last modified 5 years ago
#6051 closed defect
Problems reading older MODIS Sea Ice Extent and IST Daily L3 Global 4km EASE-Grid Day HDF data — at Version 1
Reported by: | markusm | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | 1.11.2 |
Severity: | normal | Keywords: | HDF, MODIS |
Cc: |
Description (last modified by )
The problem is in detail described here http://gis.stackexchange.com/questions/155326/reprojecting-modis-sea-ice-extent-and-ist-data-using-gdal, but in a nutshell:
GDAL is able to read and write new MOD29 data, but older ones get garbled up. I tried both gdal_translate and the Python API. I am now certain that the problem is not related to a wrong coordinate reference system (NSIDC confirmed that both old and new datasets should use EPSG:3409).
gdal_translate -unscale -srcwin 500 500 3500 3500 -a_srs epsg:3409 HDF4_EOS:EOS_GRID:"MOD29E1D.A2009345.005.2009346083234.hdf":MOD_Grid_Seaice_4km_South:Ice_Surface_Temperature_SP MOD29E1D.A2009345.005.2009346083234.tif
gdal_translate -unscale -srcwin 500 500 3500 3500 -a_srs epsg:3409 HDF4_EOS:EOS_GRID:"MOD29E1D.A2014345.005.2014351005302.hdf":MOD_Grid_Seaice_4km_South:Ice_Surface_Temperature_SP MOD29E1D.A2014345.005.2014351005302.tif
The exact same happens when using the GDAL Python API, test program attached.
These are the test files that I used: ftp://n5eil01u.ecs.nsidc.org/SAN/MOST/MOD29E1D.005/2009.12.11/ and ftp://n5eil01u.ecs.nsidc.org/SAN/MOST/MOD29E1D.005/2014.12.11/ .
Change History (2)
by , 9 years ago
Attachment: | process_ist.py added |
---|
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
Python test script