Ocean Color Forum - Not logged in
Forum Ocean Color Home Help Search Login
Previous Next Up Topic SeaDAS / SeaDAS 6.x - General Questions / Geolocation of Modis Aqua after March 2011 (locked) (1947 hits)
By tharmel Date 2011-07-27 16:30
Hello,

I am processing level 1A MODIS Aqua data into L2 data for a 2-year period. Everything goes well until the day number 73 of 2011. After this date, I am getting the following error message after application of modis_GEO.csh

"
Determining required attitude and ephemeris files...
modis_atteph.py ./A2011073175000.L1A_LAC.x.hdf
Input  Level 1A   : ./A2011073175000.L1A_LAC.x.hdf
Output Geolocation: ./A2011073175000.GEO

Satellite: aqua
Year: 2011  Day: 073  Hour: 17  Minute: 50
*Terrain Correction Enabled*

Creating MODIS geolocation file...
/home/harmel/SEADAS/seadas_6.2/run/bin/geogen_modis
GEO version: 5.0.14 built on Apr  7 2011 (14:39:53)
geogen_modis exit status: 1

Running validation test on geolocation file...
modis_geocheck.py A2011073175000.GEO 95 --verbose
Percent valid data (100.000000) is less than threshold 95.000000

modis_GEO.csh: ERROR: MODIS geolocation processing failed.
Please ensure utcpole.dat and leapsec.dat are up-to-date in
/home/harmel/SEADAS/seadas_6.2/run/var/modis
Please examine the LogStatus and LogUser files for more information.
"

Have you any idea of how to fix this geolocation failure for the MODIS data after 2011 Day 73?

Thank you,

Tristan

Attachment: LogUser.A2011073175000.GEO (0.9k)
Attachment: LogStatus.A2011073175000.GEO (4.4k)
By gwyn Date 2011-07-27 17:07
Tristan -

There had been a problem with one of the python modules; see
http://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?pid=17086;hl=modis_GEO_utils#pid17086

I'm attaching the revised module; put it in $SEADAS/run/scripts/modules/modis_GEO_utils.py

In fact the LogStatus file indicates that your input granule has 100% missing data:

GEO_get_GRing_points.c, GEO_get_GRing_points():MODIS_W_NO_GEO:288779330
Wed Jul 27 11:39:14 2011
Granule contains no geolocatable pixels.


Probably you need to update your leapsec.dat and utcpole.dat files.  Here's a clue:

PGS_TD_LeapSec():PGSTD_W_JD_OUT_OF_RANGE:27652
input time (at UTC Julian Date 2455635.243060) is past end of table --
a linear approximation was used to determine the leap seconds value


Attachment: modis_GEO_utils.py (13.3k)
By tharmel Date 2011-07-27 20:27
Gwyn,

I updated modis_GEO_utils.py.
I ran the seadas6.2/run/scripts/modis_update_utcpole_leapsec.csh and everything works fine now.

Thank you very much.

Tristan
Previous Next Up Topic SeaDAS / SeaDAS 6.x - General Questions / Geolocation of Modis Aqua after March 2011 (locked) (1947 hits)



Responsible NASA Official: Gene C. Feldman
Curator: OceanColor Webmaster
Authorized by: Gene C. Feldman
Updated: 27 November 2007
Privacy Policy and Important Notices NASA logo