[GRASSLIST:6258] hdf and modis/aster

Ian_MacMillan1 · March 25, 2005, 10:14pm

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

Anyone run into this before?

Thanks,
Ian

PS Using Mac 10.3.8, Grass 6.1cvs (march 22)

-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB

"insert witticism here"

Trevor_Wiens2 · March 26, 2005, 12:54am

On Fri, 25 Mar 2005 14:14:58 -0800
"Ian W. Macmillan" <ian_macmillan@umail.ucsb.edu> wrote:

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

I've not imported hdf4 directly, but used the MODIS reprojection tool to tile and convert the data GeoTiff. Then importing it into GRASS was a breeze.

T
--
Trevor Wiens
twiens@interbaun.com

The significant problems that we face cannot be solved at the same
level of thinking we were at when we created them.
(Albert Einstein)

Maciej_Sieczka3 · March 26, 2005, 11:24am

Ian

What does gdalinfo say about your hdf4 file? I've had an issue that hdf4 "Aster relative DEM" was not recongnized as georeferenced in newer Gdal
versions due to changes in the hdf driver. Maybe that is your case too?

Maciek

----- Original Message ----- From: "Ian W. Macmillan" <ian_macmillan@umail.ucsb.edu>
To: <grasslist@baylor.edu>
Sent: Friday, March 25, 2005 11:14 PM
Subject: [GRASSLIST:6258] hdf and modis/aster

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

Anyone run into this before?

Thanks,
Ian

PS Using Mac 10.3.8, Grass 6.1cvs (march 22)

-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB

"insert witticism here"

Ian_MacMillan1 · March 28, 2005, 2:39pm

Here is the full output of gdalinfo. Bit long, but I think it looks normal (I don't have a ton of experience with these files yet).

GRASS 6.1.cvs (SonoraLL):~ > gdalinfo MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf
Driver: HDF4/Hierarchical Data Format Release 4
Size is 512, 512
Coordinate System is `'
Metadata:
   title=MODIS/ASTER Airborne Simulator (MASTER) Level-1B Data
   ExperimentName=Baja Mexico
   FlightDate=29 April 1999
   FlightNumber=99-003-02
   GeographicArea=Tres Virgenes, Line 17
   ClockUsedToProcess=GPS Clock
   DataSliceNumber=17
   FlightLineNumber=26
   TotalFlightLines=40
   Credits=Gumley & Hubanks/design, Fitzgerald & Cleven/modify, maintain
   MASDataUsersGuideSource=MAS World Wide Web site at http://ltpwww.gsfc.nasa.gov/MAS/Home.html
   VIS/NIRCountSensitivityAdjustment=No
   DataVersion=Version 1.0
   SoftwareVersion=Version 9.0
   CalibrationVersion=Baja_4/16-5/26 ver 0.1
   data_set= MASTER Baja Mexico
   data_product=straight-line flight tracks
   geog_flag=c
   day_night_flag=d
   granule_version=1
   metadata_version=9a
   producer_granule_id=Version 1.0 Baja_4/16-5/26 ver 0.1
   data_quality=Excellent
   granule_size=3.986607e+08
   begin_date=19990429 214107
   end_date=19990429 214403
   lat_LL=27.49829
   lon_LL=-112.6536
   lat_UL=27.49786
   lon_UL=-112.809
   lat_UR=27.53468
   lon_UR=-112.8115
   lat_LR=27.53519
   lon_LR=-112.6534
   Principle_Investigator=Joann Stock (Caltech)
   Other_Aircraft_Sensors=RC-30
   CreationDate=24-Aug-99 00:16:00
Subdatasets:
   SUBDATASET_1_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":17
   SUBDATASET_1_DESC=[4378x50] BlackBody1Temperature (16-bit integer)
   SUBDATASET_2_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":18
   SUBDATASET_2_DESC=[4378x50] BlackBody2Temperature (16-bit integer)
   SUBDATASET_3_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":19
   SUBDATASET_3_DESC=[4378x50] AnalogGain (16-bit integer)
   SUBDATASET_4_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":20
   SUBDATASET_4_DESC=[4378x50] AnalogOffset (16-bit integer)
   SUBDATASET_5_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":21
   SUBDATASET_5_DESC=[4378x50] BlackBody1Counts (16-bit integer)
   SUBDATASET_6_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":22
   SUBDATASET_6_DESC=[4378x50] BlackBody2Counts (16-bit integer)
   SUBDATASET_7_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":23
   SUBDATASET_7_DESC=[4378x50] Head1Counts (16-bit integer)
   SUBDATASET_8_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":24
   SUBDATASET_8_DESC=[4378x50] Head2Counts (16-bit integer)
   SUBDATASET_9_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":25
   SUBDATASET_9_DESC=[4378x50] Therm1Temperatures (16-bit integer)
   SUBDATASET_10_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":26
   SUBDATASET_10_DESC=[4378x50] Therm2Temperatures (16-bit integer)
   SUBDATASET_11_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":27
   SUBDATASET_11_DESC=[4378x50] Therm3Temperatures (16-bit integer)
   SUBDATASET_12_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":28
   SUBDATASET_12_DESC=[4378x50] Therm4Temperatures (16-bit integer)
   SUBDATASET_13_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":29
   SUBDATASET_13_DESC=[4378x50] CalibrationSlope (32-bit floating-point)
   SUBDATASET_14_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":30
   SUBDATASET_14_DESC=[4378x50] CalibrationIntercept (32-bit floating-point)
   SUBDATASET_15_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":31
   SUBDATASET_15_DESC=[4378x716] PixelLatitude (32-bit floating-point)
   SUBDATASET_16_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":32
   SUBDATASET_16_DESC=[4378x716] PixelLongitude (32-bit floating-point)
   SUBDATASET_17_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":33
   SUBDATASET_17_DESC=[4378x716] SensorZenithAngle (32-bit floating-point)
   SUBDATASET_18_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":34
   SUBDATASET_18_DESC=[4378x716] SensorAzimuthAngle (32-bit floating-point)
   SUBDATASET_19_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":35
   SUBDATASET_19_DESC=[4378x716] SolarZenithAngle (32-bit floating-point)
   SUBDATASET_20_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":36
   SUBDATASET_20_DESC=[4378x716] SolarAzimuthAngle (32-bit floating-point)
   SUBDATASET_21_NAME=HDF4_SDS:UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":43
   SUBDATASET_21_DESC=[4378x50x716] CalibratedData (16-bit integer)
Corner Coordinates:
Upper Left ( 0.0, 0.0)
Lower Left ( 0.0, 512.0)
Upper Right ( 512.0, 0.0)
Lower Right ( 512.0, 512.0)
Center ( 256.0, 256.0)

On Mar 26, 2005, at 3:24 AM, Maciek Sieczka wrote:

Ian

What does gdalinfo say about your hdf4 file? I've had an issue that hdf4 "Aster relative DEM" was not recongnized as georeferenced in newer Gdal
versions due to changes in the hdf driver. Maybe that is your case too?

Maciek

----- Original Message ----- From: "Ian W. Macmillan" <ian_macmillan@umail.ucsb.edu>
To: <grasslist@baylor.edu>
Sent: Friday, March 25, 2005 11:14 PM
Subject: [GRASSLIST:6258] hdf and modis/aster

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

Anyone run into this before?

Thanks,
Ian

PS Using Mac 10.3.8, Grass 6.1cvs (march 22)

-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB

"insert witticism here"

Maciej_Sieczka3 · March 28, 2005, 9:59pm

Ian

Anybody correct me if I'm wrong, but it seems that gdalinfo doesn't recognize any info about the georefercing in your hdf - see "Coordinate System is `'".
This is likely the reason of your problems. Either your file is not georeferenced or there is something wrong with the hdf driver in gdal. Dig the gdal mailing list and bugtracker for relevant info and consider bugging gdal developers if needed then.

Maciek

----- Original Message ----- From: "Ian MacMillan" <ian_macmillan@umail.ucsb.edu>
To: "Maciek Sieczka" <werchowyna@epf.pl>
Cc: "GRASS Users Mailing List" <grasslist@baylor.edu>
Sent: Monday, March 28, 2005 4:39 PM
Subject: Re: [GRASSLIST:6258] hdf and modis/aster

Here is the full output of gdalinfo. Bit long, but I think it looks
normal (I don't have a ton of experience with these files yet).

GRASS 6.1.cvs (SonoraLL):~ > gdalinfo
MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf
Driver: HDF4/Hierarchical Data Format Release 4
Size is 512, 512
Coordinate System is `'
Metadata:
  title=MODIS/ASTER Airborne Simulator (MASTER) Level-1B Data
  ExperimentName=Baja Mexico
  FlightDate=29 April 1999
  FlightNumber=99-003-02
  GeographicArea=Tres Virgenes, Line 17
  ClockUsedToProcess=GPS Clock
  DataSliceNumber=17
  FlightLineNumber=26
  TotalFlightLines=40
  Credits=Gumley & Hubanks/design, Fitzgerald & Cleven/modify, maintain
  MASDataUsersGuideSource=MAS World Wide Web site at
http://ltpwww.gsfc.nasa.gov/MAS/Home.html
  VIS/NIRCountSensitivityAdjustment=No
  DataVersion=Version 1.0
  SoftwareVersion=Version 9.0
  CalibrationVersion=Baja_4/16-5/26 ver 0.1
  data_set= MASTER Baja Mexico
  data_product=straight-line flight tracks
  geog_flag=c
  day_night_flag=d
  granule_version=1
  metadata_version=9a
  producer_granule_id=Version 1.0 Baja_4/16-5/26 ver 0.1
  data_quality=Excellent
  granule_size=3.986607e+08
  begin_date=19990429 214107
  end_date=19990429 214403
  lat_LL=27.49829
  lon_LL=-112.6536
  lat_UL=27.49786
  lon_UL=-112.809
  lat_UR=27.53468
  lon_UR=-112.8115
  lat_LR=27.53519
  lon_LR=-112.6534
  Principle_Investigator=Joann Stock (Caltech)
  Other_Aircraft_Sensors=RC-30
  CreationDate=24-Aug-99 00:16:00
Subdatasets:
   SUBDATASET_1_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":17
  SUBDATASET_1_DESC=[4378x50] BlackBody1Temperature (16-bit integer)
   SUBDATASET_2_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":18
  SUBDATASET_2_DESC=[4378x50] BlackBody2Temperature (16-bit integer)
   SUBDATASET_3_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":19
  SUBDATASET_3_DESC=[4378x50] AnalogGain (16-bit integer)
   SUBDATASET_4_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":20
  SUBDATASET_4_DESC=[4378x50] AnalogOffset (16-bit integer)
   SUBDATASET_5_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":21
  SUBDATASET_5_DESC=[4378x50] BlackBody1Counts (16-bit integer)
   SUBDATASET_6_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":22
  SUBDATASET_6_DESC=[4378x50] BlackBody2Counts (16-bit integer)
   SUBDATASET_7_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":23
  SUBDATASET_7_DESC=[4378x50] Head1Counts (16-bit integer)
   SUBDATASET_8_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":24
  SUBDATASET_8_DESC=[4378x50] Head2Counts (16-bit integer)
   SUBDATASET_9_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":25
  SUBDATASET_9_DESC=[4378x50] Therm1Temperatures (16-bit integer)
   SUBDATASET_10_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":26
  SUBDATASET_10_DESC=[4378x50] Therm2Temperatures (16-bit integer)
   SUBDATASET_11_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":27
  SUBDATASET_11_DESC=[4378x50] Therm3Temperatures (16-bit integer)
   SUBDATASET_12_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":28
  SUBDATASET_12_DESC=[4378x50] Therm4Temperatures (16-bit integer)
   SUBDATASET_13_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":29
  SUBDATASET_13_DESC=[4378x50] CalibrationSlope (32-bit floating-point)
   SUBDATASET_14_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":30
  SUBDATASET_14_DESC=[4378x50] CalibrationIntercept (32-bit
floating-point)
   SUBDATASET_15_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":31
  SUBDATASET_15_DESC=[4378x716] PixelLatitude (32-bit floating-point)
   SUBDATASET_16_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":32
  SUBDATASET_16_DESC=[4378x716] PixelLongitude (32-bit floating-point)
   SUBDATASET_17_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":33
  SUBDATASET_17_DESC=[4378x716] SensorZenithAngle (32-bit floating-point)
   SUBDATASET_18_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":34
  SUBDATASET_18_DESC=[4378x716] SensorAzimuthAngle (32-bit
floating-point)
   SUBDATASET_19_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":35
  SUBDATASET_19_DESC=[4378x716] SolarZenithAngle (32-bit floating-point)
   SUBDATASET_20_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":36
  SUBDATASET_20_DESC=[4378x716] SolarAzimuthAngle (32-bit floating-point)
   SUBDATASET_21_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":43
  SUBDATASET_21_DESC=[4378x50x716] CalibratedData (16-bit integer)
Corner Coordinates:
Upper Left ( 0.0, 0.0)
Lower Left ( 0.0, 512.0)
Upper Right ( 512.0, 0.0)
Lower Right ( 512.0, 512.0)
Center ( 256.0, 256.0)

On Mar 26, 2005, at 3:24 AM, Maciek Sieczka wrote:

Ian

What does gdalinfo say about your hdf4 file? I've had an issue that hdf4
"Aster relative DEM" was not recongnized as georeferenced in newer Gdal
versions due to changes in the hdf driver. Maybe that is your case too?

Maciek

----- Original Message ----- From: "Ian W. Macmillan"
<ian_macmillan@umail.ucsb.edu>
To: <grasslist@baylor.edu>
Sent: Friday, March 25, 2005 11:14 PM
Subject: [GRASSLIST:6258] hdf and modis/aster

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

Anyone run into this before?

Thanks,
Ian

PS Using Mac 10.3.8, Grass 6.1cvs (march 22)

-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB

"insert witticism here"

cmbarton · March 29, 2005, 6:46am

According to the gdal maintainer (a few months back), there are problems
with the GCP and related data in Modis hdf files. So you can't use gdalwarp
to georeference them. The georeferenceing data in Terra ASTER hdf files is
OK. My r.in.aster script will georeference and import these data.

Michael
____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

From: Ian MacMillan <ian_macmillan@umail.ucsb.edu>
Date: Mon, 28 Mar 2005 06:39:19 -0800
To: Maciek Sieczka <werchowyna@epf.pl>
Cc: GRASS Users Mailing List <grasslist@baylor.edu>
Subject: [GRASSLIST:6269] Re: hdf and modis/aster

Here is the full output of gdalinfo. Bit long, but I think it looks
normal (I don't have a ton of experience with these files yet).

GRASS 6.1.cvs (SonoraLL):~ > gdalinfo
MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf
Driver: HDF4/Hierarchical Data Format Release 4
Size is 512, 512
Coordinate System is `'
Metadata:
   title=MODIS/ASTER Airborne Simulator (MASTER) Level-1B Data
   ExperimentName=Baja Mexico
   FlightDate=29 April 1999
   FlightNumber=99-003-02
   GeographicArea=Tres Virgenes, Line 17
   ClockUsedToProcess=GPS Clock
   DataSliceNumber=17
   FlightLineNumber=26
   TotalFlightLines=40
   Credits=Gumley & Hubanks/design, Fitzgerald & Cleven/modify, maintain
   MASDataUsersGuideSource=MAS World Wide Web site at
http://ltpwww.gsfc.nasa.gov/MAS/Home.html
   VIS/NIRCountSensitivityAdjustment=No
   DataVersion=Version 1.0
   SoftwareVersion=Version 9.0
   CalibrationVersion=Baja_4/16-5/26 ver 0.1
   data_set= MASTER Baja Mexico
   data_product=straight-line flight tracks
   geog_flag=c
   day_night_flag=d
   granule_version=1
   metadata_version=9a
   producer_granule_id=Version 1.0 Baja_4/16-5/26 ver 0.1
   data_quality=Excellent
   granule_size=3.986607e+08
   begin_date=19990429 214107
   end_date=19990429 214403
   lat_LL=27.49829
   lon_LL=-112.6536
   lat_UL=27.49786
   lon_UL=-112.809
   lat_UR=27.53468
   lon_UR=-112.8115
   lat_LR=27.53519
   lon_LR=-112.6534
   Principle_Investigator=Joann Stock (Caltech)
   Other_Aircraft_Sensors=RC-30
   CreationDate=24-Aug-99 00:16:00
Subdatasets:

SUBDATASET_1_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":17
   SUBDATASET_1_DESC=[4378x50] BlackBody1Temperature (16-bit integer)

SUBDATASET_2_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":18
   SUBDATASET_2_DESC=[4378x50] BlackBody2Temperature (16-bit integer)

SUBDATASET_3_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":19
   SUBDATASET_3_DESC=[4378x50] AnalogGain (16-bit integer)

SUBDATASET_4_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":20
   SUBDATASET_4_DESC=[4378x50] AnalogOffset (16-bit integer)

SUBDATASET_5_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":21
   SUBDATASET_5_DESC=[4378x50] BlackBody1Counts (16-bit integer)

SUBDATASET_6_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":22
   SUBDATASET_6_DESC=[4378x50] BlackBody2Counts (16-bit integer)

SUBDATASET_7_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":23
   SUBDATASET_7_DESC=[4378x50] Head1Counts (16-bit integer)

SUBDATASET_8_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":24
   SUBDATASET_8_DESC=[4378x50] Head2Counts (16-bit integer)

SUBDATASET_9_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":25
   SUBDATASET_9_DESC=[4378x50] Therm1Temperatures (16-bit integer)

SUBDATASET_10_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":26
   SUBDATASET_10_DESC=[4378x50] Therm2Temperatures (16-bit integer)

SUBDATASET_11_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":27
   SUBDATASET_11_DESC=[4378x50] Therm3Temperatures (16-bit integer)

SUBDATASET_12_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":28
   SUBDATASET_12_DESC=[4378x50] Therm4Temperatures (16-bit integer)

SUBDATASET_13_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":29
   SUBDATASET_13_DESC=[4378x50] CalibrationSlope (32-bit floating-point)

SUBDATASET_14_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":30
   SUBDATASET_14_DESC=[4378x50] CalibrationIntercept (32-bit
floating-point)

SUBDATASET_15_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":31
   SUBDATASET_15_DESC=[4378x716] PixelLatitude (32-bit floating-point)

SUBDATASET_16_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":32
   SUBDATASET_16_DESC=[4378x716] PixelLongitude (32-bit floating-point)

SUBDATASET_17_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":33
   SUBDATASET_17_DESC=[4378x716] SensorZenithAngle (32-bit
floating-point)

SUBDATASET_18_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":34
   SUBDATASET_18_DESC=[4378x716] SensorAzimuthAngle (32-bit
floating-point)

SUBDATASET_19_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":35
   SUBDATASET_19_DESC=[4378x716] SolarZenithAngle (32-bit floating-point)

SUBDATASET_20_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":36
   SUBDATASET_20_DESC=[4378x716] SolarAzimuthAngle (32-bit
floating-point)

SUBDATASET_21_NAME=HDF4_SDS:
UNKNOWN:"MASTERL1b_9900302_26_19990429_2141_2144_V01.1.hdf":43
   SUBDATASET_21_DESC=[4378x50x716] CalibratedData (16-bit integer)
Corner Coordinates:
Upper Left ( 0.0, 0.0)
Lower Left ( 0.0, 512.0)
Upper Right ( 512.0, 0.0)
Lower Right ( 512.0, 512.0)
Center ( 256.0, 256.0)

On Mar 26, 2005, at 3:24 AM, Maciek Sieczka wrote:

Ian

What does gdalinfo say about your hdf4 file? I've had an issue that
hdf4 "Aster relative DEM" was not recongnized as georeferenced in
newer Gdal
versions due to changes in the hdf driver. Maybe that is your case too?

Maciek

----- Original Message ----- From: "Ian W. Macmillan"
<ian_macmillan@umail.ucsb.edu>
To: <grasslist@baylor.edu>
Sent: Friday, March 25, 2005 11:14 PM
Subject: [GRASSLIST:6258] hdf and modis/aster

Hi all, I am trying to import some MASTER data (combined MODIS and
ASTER) that is an hdf4 file (it should have the same exact format as
MODIS data). After realizing that I need to import the subdatasets
(which import fine into an XY location), I have run into a problem. It
seems that the data I want is in one subdataset, but the latitudes and
longitudes are in separate subdatasets. How can I import this so that
the data I want is actually georeferenced?

I tried gdal_translate on a whim (gdal_translate -of GTiff -b 1
subdataset myfile.tif), but I ended up with a geotiff that either
gives
me an error of "cellhd.proj = 0 (unreferenced)" or if r.in.gdal -o
"G_set_window(): Illegal latitude for South".

Anyone run into this before?

Thanks,
Ian

PS Using Mac 10.3.8, Grass 6.1cvs (march 22)

-----------------------------------------------------
Ian MacMillan
Geological Sciences-UCSB

"insert witticism here"

Maciej_Sieczka3 · March 29, 2005, 7:54pm

From: "Michael Barton" <michael.barton@asu.edu>

According to the gdal maintainer (a few months back), there are problems
with the GCP and related data in Modis hdf files. So you can't use gdalwarp
to georeference them. The georeferenceing data in Terra ASTER hdf files is
OK.

Right. Fortunatelly they are taking care of this:

From: "Andrey Kiselev" <dron@ak4719.spb.edu>
To: <gdal-dev@xserve.flids.com>
Sent: Monday, March 28, 2005 8:51 PM
Subject: Re: [Gdal-dev] no georef in Aster relative DEM

Full support for HDF-EOS Swath products will be available soon.

Maciek