L2GEN Science Processing Algorithm (L2GEN - SPA) User's Guide: February 2017

L2GEN Science
Processing Algorithm
(L2GEN_SPA)
User's Guide
Version 8.10.3
February 2017
GODDARD SPACE FLIGHT CENTER

GREENBELT, MARYLAND
L2GEN Science Processing Algorithm
L2GEN_SPA
General
The NASA Goddard Space Flight Center’s (GSFC) Direct Readout Laboratory (DRL), Code
606.3 developed this software for the International Polar Orbiter Processing Package
(IPOPP). IPOPP maximizes the utility of Earth science data for making real-time decisions by
giving fast access to instrument data and derivative products from the Suomi National Polar-
orbiting Partnership (SNPP), Aqua, and Terra missions and, in the future, the Joint Polar
Satellite System (JPSS) mission.
Users must agree to all terms and conditions in the Software Usage Agreement on the DRL
Web Portal before downloading this software.
Software and documentation published on the DRL Web Portal may occasionally be updated
or modified. The most current versions of DRL software are available at the DRL Web Portal:
http://directreadout.sci.gsfc.nasa.gov/?id=software
Questions relating to the contents or status of this software and its documentation should be
addressed to the DRL via the Contact DRL mechanism at the DRL Web Portal:
http://directreadout.sci.gsfc.nasa.gov/?id=dspContent&cid=66
Algorithm Wrapper Concept

The DRL has developed an algorithm wrapper to provide a common command and execution
interface to encapsulate multi-discipline, multi-mission science processing algorithms. The
wrapper also provides a structured, standardized technique for packaging new or updated
algorithms with minimal effort.
A Science Processing Algorithm (SPA) is defined as a wrapper and its contained algorithm.
SPAs will function in a standalone, cross-platform environment to serve the needs of the broad
Direct Readout community. Detailed information about SPAs and other DRL technologies is
available at the DRL Web Portal.
Software Description
This software package contains the L2GEN_SPA. The L2GEN algorithm was extracted from
the Ocean Biology Processing Group's (OBPG) SeaWiFS Data Analysis System (SeaDAS).
This SPA produces Moderate Resolution Imaging Spectroradiometer (MODIS) Level 2 Ocean
Color (daytime product, includes Chlorophyll-a [CHLOR_A] concentration) and Sea Surface
Temperature (SST) products from inputs of MODIS Level 1B 1km (MOD021KM/MYD021KM)
products, MODIS Geolocation (MOD03/MYD03) products, and other optional ancillary files.
This SPA also produces Visible Infrared Imaging Radiometer Suite (VIIRS) Ocean Color
(daytime product, includes Chlorophyll-a [CHLOR_A] concentration) and Sea Surface
Temperature (SST) products from inputs of VIIRS Sensor Data Record (SDR) products, the
VIIRS Moderate Resolution Terrain Corrected Geolocation product and optional ancillaries.
L2GEN_SPA Page 1 February 2017

This implementation serves as a source of scientific algorithms for the MODIS and VIIRS SST
and Ocean Color products only. For more information on the complete SeaDAS Processing
Package, you may refer to the OBPG's site located at:
http://seadas.gsfc.nasa.gov/
The L2GEN_SPA functions in two modes: Standalone, or as an IPOPP plug-in.
Software Version
Version 1.5 of the DRL algorithm wrapper was used to package the SPA described in this
document. The SPA uses the L2GEN (Version 8.10.3) processing code embedded within the
SeaDAS (Version 7.3) to generate MODIS and VIIRS Ocean products. This SPA represents
MODIS Collections 5 and 6.
Enhancements to this SPA include:

 update to version 8.10.3 of the OBPG l2gen algorithm;
 updated parameter files;
 leapsec inputs for the VIIRS processing component to provide greater time precision
in output products.
This software will execute on a 64-bit computer and has been tested on computers with 32GB
of RAM, with the following operating systems:
a) Fedora 24 X86_64;
b) CentOS Linux 7 X86_64;
c) OpenSUSE Linux 13.2 X86_64;
d) Kubuntu 14.04 X86_64.
Copyright 1999-2007, United States Government as represented by the Administrator for the
National Aeronautics and Space Administration. All Rights Reserved.
Credits
SeaDAS and its component L2GEN algorithm were provided to the DRL by the OBPG at the
NASA Goddard Space Flight Center.
Prerequisites
To run this package, you must have the Java Development Kit (JDK) or Java Runtime
Engine (JRE) (Java 1.6.0_25 or higher) installed on your computer, and have the Java
installation bin/ subdirectory in your PATH environment variable.
Program Inputs and Outputs

This SPA’s MODIS processing component uses the MODIS 1km L1B Calibrated Geolocated
Radiances (MOD021KM, MYD021KM) HDF product and the MODIS Geolocation HDF

product (MOD03, MYD03), along with ancillary meteorology, ozone, sea ice and SST files as
inputs. Outputs are the MODIS Level 2 Sea Surface Temperature and Ocean Color products.
This SPA’s VIIRS processing component uses the VIIRS moderate resolution SDR products
(Bands M1-M16), the VIIRS Moderate Resolution Terrain Corrected Geolocation product,
along with ancillary leapsec, meteorology, ozone, sea ice and SST files as inputs. Outputs
are the VIIRS Level 2 Sea Surface Temperature and Ocean Color products.
Installation and Configuration
Installing as a Standalone Application:
Download the L2GEN_8.10.3_SPA_1.5.tar.gz and L2GEN_8.10.3_SPA_1.5_testdata.tar.gz

(optional) files into the same directory.
Decompress and un-archive the L2GEN_8.10.3_SPA_1.5.tar.gz and

L2GEN_8.10.3_SPA_1.5_testdata.tar.gz (optional) files:
$ tar –xzf L2GEN_8.10.3_SPA_1.5.tar.gz

$ tar –xzf L2GEN_8.10.3_SPA_1.5_testdata.tar.gz
This will create the following subdirectories:

SPA
l2gen
algorithm
ancillary
station
testdata
testscripts
wrapper
Installing into an IPOPP Framework: This SPA can also be installed dynamically into an
IPOPP framework to automate production of MODIS/VIIRS Sea Surface Temperature and
Ocean Color Level 2 data products. The SPA installation process will install its SPA service(s)
into IPOPP. An SPA service is an IPOPP agent that provides the mechanism necessary for
running an SPA automatically within the IPOPP framework. Once this SPA is installed, users
must enable the SPA service(s) corresponding to this SPA along with any other prerequisite
SPA service(s). Instructions for installing an SPA and enabling its services are contained in
the IPOPP User’s Guide (available on the DRL Web Portal). The SPA services associated
with this SPA are listed in Appendix A.
Software Package Testing and Validation

The testscripts subdirectory contains test scripts that can be used to verify that your current
installation of the SPA is working properly, as described below. Note that the optional
L2GEN_8.10.3_SPA_1.5_testdata.tar.gz file is required to execute these testing procedures.

Step 1: cd into the testscripts directory.
Step 2: The following scripts are inside the testscripts directory: 'run-chlor_a.sh', 'run-
sst.sh’, ‘run-l2gen_viirs-oc.sh’ and ‘run-l2gen_viirs-sst.sh’. Run the scripts one by one.
For example, to run the MODIS Ocean Color algorithm, use:
$ ./run-chlor_a.sh
to run the MODIS Sea Surface Temperature algorithm, use:
$ ./run-sst.sh
to run the VIIRS Ocean Color algorithm, use:
$ ./run-l2gen_viirs-oc.sh
to run the VIIRS Sea Surface Temperature algorithm, use:
$ ./run-l2gen_viirs-sst.sh
A successful execution usually requires 21 minutes or more for all four scripts, depending on
the speed of your computer. If everything is working properly, the scripts will terminate with
messages such as:
Output modis.chlor_a is /home/ipopp/drl/SPA/l2gen/testdata/output/CHLOR_A.hdf

Output modis.sst is /home/ipopp/drl/SPA/l2gen/testdata/output/SST.hdf
Output viirs.oc.hdf is /home/ipopp/drl/SPA/l2gen/testdata/output/VIIRS-OC.hdf
Output viirs.sst.hdf is /home/ipopp/drl/SPA/l2gen/testdata/output/VIIRS-SST.hdf
You can cd to the output directory to verify that the science products exist. Test output
product(s) are available for comparison in the testdata/output directory. These test output
product(s) were generated on a 64-bit PC architecture computer running CentOS 7. The
output products serve as an indicator of expected program output. Use a comparison utility
(such as hdiff) to compare your output product(s) to those provided in the testdata/output
directory. Locally generated files may differ slightly from the provided output files because of
differences in machine architecture or operating systems.
If there is a problem and the code terminates abnormally, the problem can be identified using
the log files. Log files are automatically generated within the directory used for execution.
They start with stdfile* and errfile*. Other log and intermediate files may be generated
automatically within the directory used for execution. They are useful for traceability and
debugging purposes. However it is strongly recommended that users clean up log files and
intermediate files left behind in the run directory before initiating a fresh execution of the SPA.
Intermediate files from a previous run may affect a successive run and produce ambiguous
results. Please report any errors that cannot be fixed to the DRL.

Program Operation
In order to run the package using your own input data, you can either use the run scripts within
the wrapper subdirectories, or modify the test scripts within the testscripts subdirectory.
To Use the Run Scripts

Identify the 'run' scripts: The wrapper directory within this package contains subdirectories
for generating each of the four products (i.e., the MODIS Ocean Color, MODIS Sea Surface
Temperature, VIIRS Ocean Color, and VIIRS Sea Surface Temperature products). The
subdirectories contain an executable called 'run'. Execute 'run' within the correct wrapper
subdirectory to generate the corresponding product. For instance, the 'run' within wrapper/sst,
wrapper/chlor_a, wrapper/l2gen_viirs-sst, and wrapper/l2gen_viirs-oc is used for creating the
MODIS Sea Surface Temperature, MODIS Ocean Color, VIIRS Sea Surface Temperature,
and VIIRS Ocean Color products respectively. Note that to execute 'run', you need to have
java on your path.
Specify input parameters using <label value> pairs: To execute the 'run' scripts, you must
supply the required input and output parameters. Input and output parameters are usually file
paths or other values (e.g., a scan time parameter). Each parameter is specified on the
command line by a <label value> pair. Labels are simply predefined names for parameters.
Each label must be followed by its actual value. Each process has its own set of <label value>
pairs that must be specified in order for it to execute. Some of these pairs are optional,
meaning the process would still be able to execute even if that parameter is not supplied. The
three types of <label value> pairs that the L2GEN_SPA uses are:
a) Input file label/values. These are input file paths. Values are absolute or relative paths
to the corresponding input file.
b) Output file label/values. These are output files that are produced by the SPA. Values
are absolute or relative paths of the files you want to generate.
c) Parameter label/values. These are parameters that need to be passed onto the SPA.
The following tables contain labels, and their descriptions, required by the L2GEN_SPA.

Input File Labels & Description Source
Parameters
(MODIS-exclusive)
modis.mxd021km MODIS 1km L1B Calibrated

1. The MODISL1DB_SPA can be used
Geolocated Radiances HDF file
to create this product.
(MOD021KM, MYD021KM)
2. Real time MODIS L1B products over
the eastern US region are available
from the DRL ftp site at:
ftp://is.sci.gsfc.nasa.gov/gsfcdata/aq
ua/modis/level1/MYD021KM.YYDDD
hhmmss.hdf (Aqua)
ftp://is.sci.gsfc.nasa.gov/gsfcdata/terr
a/modis/level1/MOD021KM.YYDDDh
hmmss.hdf (Terra)
Where YY, DDD represents the year
and day of year for the start of the
swath; and hh, mm, ss represents the
hour, minutes, seconds for the start of
the swath.
3. MODIS L1B products for other
locations and times are available for
download at
http://reverb.echo.nasa.gov/reverb/
modis.mxd03 MODIS Geolocation HDF file

1. The MODISL1DB_SPA can be used
(MOD03, MYD03)
to create this product.
2. Real time MODIS Geolocation
products over the eastern US region
are available from the DRL ftp site at:
ftp://is.sci.gsfc.nasa.gov/gsfcdata/aq
ua/modis/level1/MYD03.YYDDDhhm
mss.hdf (Aqua)
ftp://is.sci.gsfc.nasa.gov/gsfcdata/terr
a/modis/level1/MOD03.YYDDDhhm
mss.hdf (Terra)
Where YY, DDD represents the year
and day of year for the start of the
swath; and hh, mm, ss represents the
hour, minutes, seconds for the start of
the swath.
3. MODIS Geolocation products for
other locations and times are
available for download at
http://reverb.echo.nasa.gov/reverb/

Parameters
(MODIS-exclusive)
ncep_met_1 Directory path and filename of the For recent meteorological ancillary files:
Near-Real Time (NRT) National ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
(optional) Centers for Environmental obal/oceansmet/SyyyyDDDhh_NCEP.MET
Prediction (NCEP)
meteorological ancillary data For archived meteorology ancillary files:
product available for the nearest ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
time preceding the time of the mporal/global/oceansmet/SyyyyDDDhh_NCE
input swath’s first scan line. P.MET
ncep_met_2 Directory path and filename of the where yyyy, DDD, hh represents the year, day
NRT NCEP meteorological of year, and hour for the ancillary file.
(optional) ancillary data product available
following the time of the input
swath’s first scan line.
ncep_met_3 Directory path and filename of the
NRT NCEP meteorological
(optional) ancillary data product for the
nearest time following the time of
the input swath’s last scan line.
obpg.noaa_toast_1 Directory path and filename of the For recent ozone ancillary files:
climatological product or the NRT ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
(optional) ozone ancillary data product obal/oceanstoast/SyyyyDDD00DDDhh_TOA
available for the nearest time ST.OZONE
preceding the time of the input
swath’s first scan line. Ancillary For archived ozone ancillary files:
ozone data can come from the ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
Earth Probe Total Ozone mporal/global/oceanstoast/SyyyyDDD00DDD
Mapping Spectrometer hh_TOAST.OZONE
(EPTOMS) or Total Ozone
where yyyy, DDD, hh represents the year, day
Analysis using SBUV/2 and
of year, and hour for the ancillary file.
TOVS (TOAST).
opbg.noaa_toast_2 Directory path and filename of the
NRT ozone ancillary data product
(optional) (EPTOMS or TOAST) available
for the nearest time following the
time of the input swath’s first scan
line.
obpg.noaa_toast_3 Directory path and filename of the
(optional) (EPTOMS or TOAST) for the
platform
Value can be either ‘aqua’ or ‘terra’. Indicates the spacecraft of the MODIS L1B
and Geolocation files used as input.

Parameters
(VIIRS-exclusive)
viirs.svmxx VIIRS 750m M1-M16 band SDR

1. The C-SDR_SPA can be used to
HDF5 file path
(where xx = 01 to 16) create these products.
2. Real time VIIRS SDR products over
the eastern US region are available
from the DRL ftp site at:
ftp://is.sci.gsfc.nasa.gov/gsfcdata/np
p/viirs/level1/SVMXX_npp_dyyyymm
dd_thhmmssS_ehhmmssS*.h5
(where XX = 01 to 16)
Where yyyy, mm, dd represents the
year, month, and day of month for the
start of the swath; the first hh, mm, ss,
S represents the hour, minutes,
seconds, and 10th of a second for the
start of the swath and the second hh,
mm, ss, S represents the end time of
the swath.
3. VIIRS SDR products for other
download at
www.class.noaa.gov
viirs.gmtco VIIRS 750m Terrain Corrected

1. The C-SDR_SPA can be used to
Geolocation HDF5 file path
create this product.
2. Real time VIIRS Geolocation
products over the eastern US region
are available from the DRL ftp site at:
ftp://is.sci.gsfc.nasa.gov/gsfcdata/np
p/viirs/level1/GMTCO_npp_dyyyym
mdd_thhmmssS_ehhmmssS*.h5
(where XX = 01 to 16)
Where yyyy, mm, dd represents the
year, month, and day of month for the
start of the swath; the first hh, mm, ss,
S represents the hour, minutes,
seconds, and 10th of a second for the
start of the swath and the second hh,
mm, ss, S represents the end time of
the swath.
3. VIIRS Geolocation products for other
download at
www.class.noaa.gov

ncep_met1 Directory path and filename of the For recent meteorological ancillary files:
Near-Real Time (NRT) National ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
(optional) Centers for Environmental obal/oceansmet/SyyyyDDDhh_NCEP.MET
Prediction (NCEP)
meteorological ancillary data For archived meteorology ancillary files:
product available for the nearest ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
time preceding the time of the mporal/global/oceansmet/SyyyyDDDhh_NC
input swath’s first scan line. EP.MET
ncep_met2 Directory path and filename of the where yyyy, DDD, hh represents the year, day
NRT NCEP meteorological of year, and hour for the ancillary file.
(optional) ancillary data product available
following the time of the input
swath’s first scan line.
ncep_met3 Directory path and filename of the
NRT NCEP meteorological
(optional) ancillary data product for the
obpg.noaa_toast1 Directory path and filename of the For recent ozone ancillary files:
climatological product or the NRT ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
(optional) ozone ancillary data product obal/oceanstoast/SyyyyDDD00DDDhh_TOA
available for the nearest time ST.OZONE
preceding the time of the input
swath’s first scan line. Ancillary For archived ozone ancillary files:
ozone data can come from the ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
Earth Probe Total Ozone mporal/global/oceanstoast/SyyyyDDD00DD
Mapping Spectrometer Dhh_TOAST.OZONE
(EPTOMS) or Total Ozone
Analysis using SBUV/2 and
where yyyy, DDD, hh represents the year, day
TOVS (TOAST).
of year, and hour for the ancillary file.
opbg.noaa_toast2 Directory path and filename of the
(optional) (EPTOMS or TOAST) available
for the nearest time following the
time of the input swath’s first scan
line.
obpg.noaa_toast3 Directory path and filename of the
(optional) (EPTOMS or TOAST) for the
leapsec Leapsec ancillary file DRL ftp site for leapsec files:
ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/le
(optional) apsec.yyyymmddhh.dat
Where yyyy, mm, dd, hh represents the year,

month, day, and hour for the leapsec ancillary
file.

Parameters
(common to MODIS &
VIIRS)
noaa_oisst Directory path and filename of the For recent OISST ancillary files:
weekly NOAA Optimum ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
(optional) Interpolated SST (OISST) obal/sst/oisst.yyyymmdd
ancillary input for the nearest time
prior to the time period For archived OISST ancillary files:
corresponding to the input swath. ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
mporal/global/sst/oisst.yyyymmdd
where yyyy, mm, dd represents the year,

month, and day of month for the ancillary file.
obpg_seaice Directory path and filename of the For recent SEAICE ancillary files:
daily NSIDC Sea Ice ancillary
(optional) input for the nearest time prior to ftp://is.sci.gsfc.nasa.gov/ancillary/temporal/gl
the period corresponding to the obal/oceansice/NyyyyDDD00_SEAICE_NSID
input swath. C_24h.hdf
For archived SEAICE ancillary files:
ftp://is.sci.gsfc.nasa.gov/ArchivedAncillary/te
mporal/global/oceansice/NyyyyDDD00_SEAI
CE_NSIDC_24h.hdf
where yyyy, DDD represents the year and day

of year for the ancillary file.

Output File Labels Description Output Format Description
(MODIS-exclusive)
modis.chlor_a MODIS Ocean Color output HDF file path Please refer to
(Daytime only) oceancolor.gsfc.nasa.gov/DOCS/
(only required for
MODIS Ocean Color
processing)
modis.sst MODIS Sea Surface Temperature output
HDF file path
(only required for
MODIS Sea Surface
Temperature
processing)
Output File Labels Description Output Format Description
(VIIRS-exclusive)
viirs.oc.hdf VIIRS Ocean Color output HDF file path Please refer to
(Daytime only) oceancolor.gsfc.nasa.gov/DOCS/
(only required for
VIIRS Ocean Color
processing)
viirs.sst.hdf VIIRS Sea Surface Temperature output
HDF file path
(only required for
VIIRS Sea Surface
Temperature
processing)
Execute the 'run': The following are examples of command lines to run the MODIS Ocean
Color, MODIS Sea Surface Temperature, VIIRS Ocean Color, and VIIRS Sea Surface
Temperature algorithms respectively from the testscripts directory:
$ ../wrapper/chlor_a/run \
modis.mxd021km ../testdata/input/MOD021KM.A2015266.1530.005.2015267021159.hdf \
modis.mxd03 ../testdata/input/MOD03.A2015266.1530.005.2015266202157.hdf \
modis.chlor_a ../testdata/output/CHLOR_A.hdf \
platform terra \
ncep_met_1 ../testdata/input/S201526612_NCEP.MET \
obpg.noaa_toast_1 ../testdata/input/S20152660026623_TOAST.OZONE \
noaa_oisst ../testdata/input/oisst.20150916 \
obpg_seaice ../testdata/input/N201526600_SEAICE_NSIDC_24h.hdf
$ ../wrapper/sst/run \
modis.mxd021km ../testdata/input/MOD021KM.A2015266.1530.005.2015267021159.hdf \
modis.mxd03 ../testdata/input/MOD03.A2015266.1530.005.2015266202157.hdf \
modis.sst ../testdata/output/SST.hdf \
platform terra \

ncep_met_1 ../testdata/input/S201526612_NCEP.MET \
obpg.noaa_toast_1 ../testdata/input/S20152660026623_TOAST.OZONE \
$../wrapper/l2gen_viirs-oc/run \
viirs.svm01 ../testdata/input/SVM01_npp_d20150923_t1817209_e1818451_b20237_c20150924134117287877_noaa_ops.h5 \
viirs.gmtco ../testdata/input/GMTCO_npp_d20150923_t1817209_e1818451_b20237_c20150924134152153831_noaa_ops.h5 \
viirs.oc.hdf ../testdata/output/VIIRS-OC.hdf \
ncep_met1 ../testdata/input/S201526618_NCEP.MET \
obpg.noaa_toast1 ../testdata/input/S20152660026623_TOAST.OZONE \
leapsec ../testdata/input/leapsec.2017012700.dat \
$../wrapper/l2gen_viirs-sst/run \
viirs.gmtco ../testdata/input/GMTCO_npp_d20150923_t1817209_e1818451_b20237_c20150924134152153831_noaa_ops.h5 \
viirs.sst.hdf ../testdata/output/VIIRS-SST.hdf \
ncep_met1 ../testdata/input/S201526618_NCEP.MET \
obpg.noaa_toast1 ../testdata/input/S20152660026623_TOAST.OZONE \
leapsec ../testdata/input/leapsec.2017012700.dat \
A successful execution usually requires 21 minutes or more for all four scripts, depending on
the speed of your computer. If execution fails, you will see an error message indicating the
cause of failure (e.g., a file cannot be found, or a label cannot be recognized). Correct it and
run again. If the problem has some other cause, it can be identified using the log files. Log
files are automatically generated within the directory used for execution. They start with
stdfile* and errfile* and can be deleted after execution. Other log and intermediate files may

be generated automatically within the directory used for execution. They are useful for
traceability and debugging purposes. However it is strongly recommended that users clean
up log files and intermediate files left behind in the run directory before initiating a fresh
execution of the SPA. Intermediate files from a previous run may affect a successive run and
produce ambiguous results. The 'run' can be executed from any directory the user chooses.
This can be done by prefixing it with the file path for the 'run' script.
NOTES:
1. Meteorology: During near-real time Direct Broadcast (DB) processing, you may either
use ncep_met_1 (ncep_met1 for VIIRS) only to specify a single meteorology input, or
specify no meteorology ancillary inputs at all. In case none of the three optional
meteorology inputs is specified, a default climatological meteorology product (included
with this package) will be used automatically. However during non-real time
processing, the user may use all three meteorological ancillary inputs.
2. Ozone: During NRT DB processing, you may either use obpg.noaa_toast_1
(obpg.noaa_toast1 for VIIRS) only to specify a single ozone input, or specify no ozone
ancillary inputs at all. In case none of the three optional ozone inputs is specified, a
default ozone product (included with this package) will be used automatically. However
during non-real time processing, the user may use all three ozone ancillary inputs.
3. SST and SEAICE: If the noaa_oisst or the obpg_seaice inputs are not specified, a
default climatological SST and SEAICE ancillaries (included with this package) will be
used automatically.
4. Leapsec ancillary files are cumulative. Use the latest leapsec file available regardless
of the input file date. The leapsec files provided by the DRL are time-stamped as
follows: leapsec.yyyymmddhh.dat. If not specified, a default leapsec file (included with
this package) will be used automatically.
5. The data products generated by this SPA may be visualized with the DRL's H2G_SPA
(Hierarchical Data Format [HDF] to Georeferenced Tagged Image File Format
[GeoTIFF] Converter Science Processing Algorithm). H2G is designed specifically for
Direct Readout applications to create geolocated GeoTIFF images, jpeg browse
images, and png browse images for parameter datasets in SNPP products and EOS
products. H2G_SPA and its User Guide are available for download from the DRL Web
Portal. Please refer to Appendix A for information on enabling image production for this
SPA in IPOPP.
To Use the Scripts in the testscripts Directory

One simple way to run the algorithms from the directory of your choice using your own data
is to copy a run-*.sh script (e.g. run-chlor_a.sh) from the testscripts directory to the selected
directory. Change the values of the variables like WRAPPERHOME, INPUTHOME and
OUTPUTHOME to reflect the file paths of the wrapper directories and the input/output file
paths. Then modify the input/output file name variables. Run the script to process your data.

Appendix A
SPA Services
Installation of this SPA in IPOPP mode will make the SPA services listed in Table A-1 available
to IPOPP. These SPA services along with any other prerequisite SPA services (listed in Table
A-2) will need to be enabled to allow IPOPP to automate production of the MODIS/VIIRS
Ocean Color and Sea Surface Temperature data products. Furthermore, users who wish to
generate image products from the data products generated by this SPA will need to enable
the image-generating SPA services listed in Table A-3. The SPAs containing the prerequisite
and the image-generating SPA services listed in Tables A-2 and A-3 can be downloaded from
the DRL Web Portal, in case they are not already available in your IPOPP installation. Details
about these other SPAs are available in the respective SPA User's Guides. Please refer to
the IPOPP User’s Guide for instructions on how to install an SPA in IPOPP and enable the
corresponding SPA services.
Table A-1. SPA Services
MODIS SPA Data Products produced

services for this
SPA
chlor_a Product Name Destination
(when installed in IPOPP)
MODIS Ocean Color Level 2 $HOME/drl/data
(Daytime only) /pub/gsfcdata/<aqua|terra>/modis/level2/CH
LOR_A.YYDDDhhmmss.hdf
sst Product Name Destination
MODIS Sea Surface $HOME/drl/data
Temperature Level 2 /pub/gsfcdata/<aqua|terra>/modis/level2/SS
T.YYDDDhhmmss.hdf
VIIRS SPA services Data Products produced
for this SPA
l2gen_viirs-oc Product Name Destination
VIIRS Ocean Color Level 2 $HOME/drl/data
(Daytime only) /pub/gsfcdata/npp/viirs/level2/VIIRS-
OC_npp_dyyyymmdd_thhmmssS_ehhmms
sS*.hdf
l2gen_viirs-sst Product Name Destination
VIIRS Sea Surface Temperature $HOME/drl/data
Level 2 /pub/gsfcdata/npp/viirs/level2/VIIRS-
SST_npp_dyyyymmdd_thhmmssS_ehhmm
ssS*.hdf
MODIS: Where YY, DDD represents the year and day of year for the start of the swath; and
the hh, mm, ss represents the hour, minutes, and seconds for the start of the swath.
L2GEN_SPA Page A-1 February 2017

VIIRS: Where yyyy, mm, dd represents the year, month and day of month for the start of the
swath; the first hh, mm, ss, S represents the hour, minutes, seconds and 10th of a second for
the start of the swath and the second hh, mm, ss, S represents the end time of the swath.
Table A-2. Prerequisite SPA services
Prerequisite SPA services (MODIS) SPA in which they are available

l0l1aqua (for Aqua MODIS) MODISL1DB_SPA
l0l1terra (for Terra MODIS)
l1atob
gbad (for Aqua MODIS) GBAD_SPA
Prerequisite SPA services (VIIRS) SPA in which they are available

VIIRS_C-SDR C-SDR_SPA
Table A-3. Image-generating SPA services
Image-generating SPA services SPA in which they are available

chlor_a-geotiff H2G_SPA
sst-geotiff H2G_SPA
viirschlor-geotiff H2G_SPA
viirssst-geotiff H2G_SPA
NOTE: Please refer to the H2G_SPA User’s Guide for more details about the image products,
including their locations and filename patterns when they are generated in IPOPP.
L2GEN_SPA Page A-2 February 2017

L2GEN Science Processing Algorithm (L2GEN - SPA) User's Guide: February 2017

Uploaded by

Copyright:

Available Formats

L2GEN Science Processing Algorithm (L2GEN - SPA) User's Guide: February 2017

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L2GEN Science Processing Algorithm (L2GEN - SPA) User's Guide: February 2017

Uploaded by

Copyright:

Available Formats

L2GEN Science

GODDARD SPACE FLIGHT CENTER

Algorithm Wrapper Concept

L2GEN_SPA Page 1 February 2017

The L2GEN_SPA functions in two modes: Standalone, or as an IPOPP plug-in.

Enhancements to this SPA include:

Program Inputs and Outputs

L2GEN_SPA Page 2 February 2017

Installation and Configuration

Installing as a Standalone Application:

Download the L2GEN_8.10.3_SPA_1.5.tar.gz and L2GEN_8.10.3_SPA_1.5_testdata.tar.gz

Decompress and un-archive the L2GEN_8.10.3_SPA_1.5.tar.gz and

$ tar –xzf L2GEN_8.10.3_SPA_1.5.tar.gz

This will create the following subdirectories:

Software Package Testing and Validation

L2GEN_SPA Page 3 February 2017

to run the MODIS Sea Surface Temperature algorithm, use:

to run the VIIRS Ocean Color algorithm, use:

to run the VIIRS Sea Surface Temperature algorithm, use:

Output modis.chlor_a is /home/ipopp/drl/SPA/l2gen/testdata/output/CHLOR_A.hdf

L2GEN_SPA Page 4 February 2017

To Use the Run Scripts

L2GEN_SPA Page 5 February 2017

modis.mxd021km MODIS 1km L1B Calibrated

modis.mxd03 MODIS Geolocation HDF file

L2GEN_SPA Page 6 February 2017

L2GEN_SPA Page 7 February 2017

viirs.svmxx VIIRS 750m M1-M16 band SDR

viirs.gmtco VIIRS 750m Terrain Corrected

L2GEN_SPA Page 8 February 2017

Where yyyy, mm, dd, hh represents the year,

L2GEN_SPA Page 9 February 2017

where yyyy, mm, dd represents the year,

For archived SEAICE ancillary files:

where yyyy, DDD represents the year and day

L2GEN_SPA Page 10 February 2017

L2GEN_SPA Page 11 February 2017

L2GEN_SPA Page 12 February 2017

To Use the Scripts in the testscripts Directory

L2GEN_SPA Page 13 February 2017

Table A-1. SPA Services

MODIS SPA Data Products produced

L2GEN_SPA Page A-1 February 2017

Table A-2. Prerequisite SPA services

Prerequisite SPA services (MODIS) SPA in which they are available

gbad (for Aqua MODIS) GBAD_SPA

Prerequisite SPA services (VIIRS) SPA in which they are available

Table A-3. Image-generating SPA services

Image-generating SPA services SPA in which they are available

L2GEN_SPA Page A-2 February 2017

You might also like