Opened 11 years ago

Closed 4 years ago

#4188 closed defect (wontfix)

Geolocation map X offsets in modis lib 250m and 500m producs are a half pixel off

Reported by: winkey Owned by: warmerdam
Priority: normal Milestone: closed_because_of_github_migration
Component: default Version: unspecified
Severity: normal Keywords:
Cc:

Description

The modis products have a fraction stored in another location that hdf-eos SWinqmaps() does not report.

MODIS Level 1B Product User's Guide page 14 http://mcst.gsfc.nasa.gov/uploads/files/M1054.pdf

"dimension maps, which define the relationship between the data fields and the geolocation fields. When the geolocation dimensions have a different size than the data dimension, an offset and an increment define the relation between them. These maps have been described as "the glue that holds the swath together." Unfortunately, the HDFEOS offsets are required to be integers, and the center of the first 1km geolocation pixel is offset by 1.5 250m pixels in the track direction from the first 250m data pixel. Therefore, the MODIS project requires that HDFEOS offsets be supplemented by a separate Fractional Offset file attribute, for each dimension map, that is to be added to the HDFEOS offset to get the true value."

Attachments (1)

M1054.pdf (550.2 KB ) - added by winkey 11 years ago.
MODIS Level 1B Product User’s Guide

Download all attachments as: .zip

Change History (3)

by winkey, 11 years ago

Attachment: M1054.pdf added

MODIS Level 1B Product User’s Guide

comment:1 by winkey, 11 years ago

reported by gdalinfo HDF4_EOS:EOS_SWATH:"MOD02QKM.A2011169.1750.005.NRT.hdf":MODIS_SWATH_Type_L1B:EV_250_RefSB

the second would appear to be the fraction to add to the x offset

HDFEOS_FractionalOffset_4*Max_EV_frames_MODIS_SWATH_Type_L1B=0 HDFEOS_FractionalOffset_40*nscans_MODIS_SWATH_Type_L1B=0.5

comment:2 by Even Rouault, 4 years ago

Milestone: closed_because_of_github_migration
Resolution: wontfix
Status: newclosed

This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.

Note: See TracTickets for help on using tickets.