MODIS Aqua level 1A to Level 1B

Create GEO files

modis_GEO.py

I am using the command line even though I have SeaDAS-7.0 beta installed.

There are path issues going on for me 

/Users/user 1/Desktop/Project
modis_GEO.py MYD01.A2007265.0530.005.2013122114904.hdf 

/Users/user 1/Desktop/Project
modis_GEO.py MYD01.A2007044.0425.005.2013122114642.hdf

>dir

MYD01.A2007044.0425.005.2013122114642
MYD01.A2007044.0425.005.2013122114642.GEO

Appears that l2gen can utilise Level 1A SeaWifs but not modis.

Next 

Create Level 1B files

l1bgen

In 

/Applications/seadas-7.0-beta/Processing/run/bin/macosx_intel

there is 

l1bgen_modisa

In the seaDAS-7.0-beta GUI modis_L1b.py is used.

Standard Install has no window is opened when called

Personal SeaDAS built from GIT master branch 4 May 2013

On selecting modis_l1bgen error regarding input path. Possible because I have a space in the path. 

Move my data to a short path with no spaces and checked the permissions, 

Error message indicates a dislike for my input file name.

Shortening

MYD01A2007044.hdf

MYD01A2007044.hdf.GEO

MYD01A2007265.hdf

MYD01A2007265.hdf.GEO

Still getting error the null pointer exception is coming back to a file currently in flux on the development . Not worth pursuing, and I do not believe my system is not sufficiently standard to provide useful  provide feedback to the developer.

Back to command line in SeaDAS 7.0 beta processing module.

Having file names with multiple '.' is definitely an issue for the modis_L1b.py script

Trying the GUI once more after renaming

MYD01A2007044.GEO

MYD01A2007044.hdf

MYD01A2007265.GEO

MYD01A2007265.hdf

Still not able to run,

Using the names above with the command line. 

/projects/chldata>

modis_L1B.py MYD01A2007265.hdf 

MYD01A2007265.GEO

MYD01A2007265.L1B_HKM

MYD01A2007265.L1B_LAC

MYD01A2007265.L1B_QKM

MYD01A2007265.hdf

Sweet