gdal cannot handle hdf EOS data

Bug #284578 reported by Graziano
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gdal
Fix Released
Unknown
gdal (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Ubuntu gdal in intrepid (sorry, I have no previous ubuntu hardy around for a test) does NOt handle hdf eos data files

Testfile ftp://e4ftl01u.ecs.nasa.gov/MODIS_Composites/MOLT/MOD12Q1.004/2004.01.01/MOD12Q1.A2004001.h09v04.004.2006117173005.hdf

Reading dataset I have

ERROR 1: GDreadfield() failed for block.
ERROR 1: IReadBlock failed at X offset 0, Y offset 0
ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0

I am on debian 64bit and gdal fails to build from source. Found only one other guy reporting something similar on gdal-dev mailing list (http://lists.osgeo.org/pipermail/gdal-dev/2008-March/016512.html), and was given hint to rebuild from source.
So I am just stuck with this.

Graziano.

Tags: upstream
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in gdal (Ubuntu):
status: New → Incomplete
Revision history for this message
Niels Felsted Thorsen (felsted) wrote :

Hi

I get a similar error using gdalwarp on karmic beta (also in jaunty), both the 64 bit version (32 bit version is working fine).

Running:

$ gdalwarp -t_srs '+proj=utm +zone=33 +datum=WGS84' -srcnodata -3000 -dstnodata -10000 "HDF4_EOS:EOS_GRID:MOD13Q1.A2006161.h21v13.005.2008234103220.hdf:MODIS_Grid_16DAY_250m_500m_VI:250m 16 days NDVI" out.tif

Produces this error:

     Creating output file that is 3531P x 5798L.
     Processing input file HDF4_EOS:EOS_GRID:MOD13Q1.A2006161.h21v13.005.2008234103220.hdf:MODIS_Grid_16DAY_250m_500m_VI:250m 16 days NDVI.
     ERROR 1: GDreadfield() failed for block.
     ERROR 1: IReadBlock failed at X offset 0, Y offset 0
     ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0

The file used can be found here:

ftp://e4ftl01u.ecs.nasa.gov/MODIS_Composites/MOLT/MOD13Q1.005/2006.06.10/MOD13Q1.A2006161.h21v13.005.2008234103220.hdf

Revision history for this message
Even Rouault (even-rouault) wrote :

This is/was not a Ubuntu packaging bug but a core GDAL one. It works for sure with latest GDAL SVN trunk, maybe with 1.7.1, but the various fixes done recently as http://trac.osgeo.org/gdal/ticket/3386 are related so latest trunk is probably needed.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Concur, this is the same bug. Marking Triaged, the fix will arrive with 1.8.x

Changed in gdal (Ubuntu):
status: Incomplete → Triaged
tags: added: upstream
Changed in gdal (Ubuntu):
importance: Undecided → Low
summary: - gdal in intrepid cannot handle hdf EOS data
+ gdal cannot handle hdf EOS data
Changed in gdal:
status: Unknown → Fix Released
Revision history for this message
Bas Couwenberg (sebastic) wrote :

GDAL 1.7.3 is available in precise, and trusty has 1.10.1. Both should include the fix.

Changed in gdal (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.