 |
Help on Interface Screens
: 3.47. Local Granule ID Search
|
What is a Local Granule ID?
A local granule ID applies only to data obtained from EOS platforms.
It is a series of characters which provide important information about the
granule to the EOS scientist. Local granule IDs are created at the DAAC where
the data granule (and parent data set) originate. Because local granule IDs
are used for EOS data sets only, local granule ID searches are sent only
to EOS data servers (e.g. GSFC-ECS, NSIDC-ECS, EDC-ECS, and LARC-ECS).
Note that an EOS data granule has both a data granule ID (See help page for
Data Granule ID Search) and a local granule ID associated with it. The
local granule ID contains more information about the data granule than does
the data granule ID.
Local granule IDs have a specific format that is dependent upon from which
EOS instrument the data is taken, and the data's science discipline.
MODIS(Atmospheres)
- Format: ESDTSHORTNAME.AYYYYDDD.HHMM.VER.YYYYDDDHHMMSS.ext
- Example: MOD02HKM.A2000065.1725.003.2000195110535.hdf
- ESDTSHORTNAME: Earth science data type shortname for the data set
- A:Acquisition data prefix -- fixed
- YYYYDDD: Year and day of year (julian date) that data was acquired
- HHMM: Hour and minute of start time of the data acquisition
- VER: 3 digit collection version number
- YYYYDDDHHMMSS: Julian processing date and time
- ext: suffix denoting type of file
MODIS (Land Processes)
- Format: ESDTSHORTNAME.AYYYYDDD.hxxvyy.VER.YYYYDDDHHMMSS.ext
- Example: MOD09A1.A2000185.h11v05.001.2000193081710.hdf
- ESDTSHORTNAME: Earth science data type shortname for the data set
- A:Acquisition data prefix -- fixed
- YYYYDDD: Year and day of year (julian date) that data was acquired
- hxxvyy: Tile ID (hxx: horizontal tile number, vyy: vertical tile number)
- VER: 3 digit collection version number
- YYYYDDDHHMMSS: Julian processing date and time
- ext: suffix denoting type of file
MODIS (Oceans)
- Level 1 and Level 2 data format: Same as MODIS Atmosphere
- Level 3 data formats:
- ESDTSHORTNAME.parameter.Ayyyyddd.HHMM.DDyyyyddd.VER.yyyydddHHMMSS.ext
- ESDTSHORTNAME.parameter.ADDyyyyddd.VER.yyyydddHHMMSS.ext
- Example: MO36FD10.aer_model1.ADD2001120.004.2002193081710.hdf
- ESDTSHORTNAME: Earth science data type shortname for the data set
- Parameter: Parameter name
- A: Represents EOS-AM1 satellite
- yyyy: Year
- ddd: Day of year
- HH: Hour
- MM: Minute
- SS: Seconds
- Date after the .A. is the start date and time of the scan
- Date after .DD. is the start-data day
- VER: 3 digit collection version number
- Date after VER is the processing date
- ext: suffix denoting type of file
MISR
- Format: MInd Level 2 data format: Same as MODIS AtmosphereSR_AM1_ProductName_MinMax_Mode_Season_Path_Orbit_Camera_Site_TimeSeries_Version.ext
- Example: MISR_AM1_GRP_ELLIPSOID_GM_P015_O001184_DF_01.hdf
-
ProductName is made up of any set of characters (including
possibly "_"). For example, "AGP", "GRP_TERRAIN", "AS_OCEAN_QA".
Use of "QA" for QA files and "BR" for browse products is an
informal convention, but not actually required by the MISR naming
convention. This field is required.
-
The MinMax indicates if the parameters in the file are minimum or
maximum values. This is currently only used for QA thresholds
(which are *not* products, so you aren't likely to see this field).
The value is either "MIN" or "MAX". This field is optional.
-
Mode is one of "GM", for global mode; "LM", for local mode;
"CL" for calibration mode. This field is optional.
-
Season is one of "SPR", for spring; "SUM" for summer; "FALL",
for fall; "WIN" for winter, or the first 3 letters of a month name
(e.g., "JAN"). This field is optional.
-
Path is a number from 1 to 233. It is a string like
"Pnnn", where the number is exactly 3 digits using leading zeroes
if needed, e.g., "P157", "P002". This field is optional, but is
required if the Orbit field is filled in.
-
Orbit is the absolute orbit sequence number
from start of the mission. This is a string like "Onnnnnn", where
the number is exactly 6 digits using leading zeroes if needed,
e.g., "O376534", "O000010". This field is optional.
-
Camera is the camera type, in all caps, e.g., "DF", "BA". This
field is optional. Some data sets only depend on the camera angle,
not its sign (e.g., the same file is used for "DF" and "DA"
cameras). For these types of data sets, the camera name is "DCAM",
"CCAM", "BCAM", "ACAM" or "NCAM".
-
Site gives the local mode site number. It is a string like "SITEn",
e.g., "SITE1", "SITE4". This field is required if the mode is "LM", and
illegal otherwise. An alternative to a site number is to follow site with
a name, which contains no "_", e.g., "SITE_ROGERSLAKE". Local mode sites
were originally given numbers, giving file names like "SITE1", but it is
planned to use descriptive names like "SITE_ROGERSLAKE" in the future.
-
Time Series gives the time order of a series of files, e.g.,
the threshold updates for generating the RCCM. It is a string like
"Tnnn", where the number is exactly 3 digits, using leading zeros
if needed, e.g., "T001". This field is optional.
-
Version contains both a format and data content version,
e.g., "F01_01". The format Fxx part was a later addition, some
files only contain the data content version number.
-
ext is the file extension chosen for the file, e.g., ".hdf".
Choose Data Set and Local Granule ID
The Local Granule ID Search is similar to the Primary Data Search Form,
in that it provides results that contain descriptions of a specified granule
from one data set.
For a local granule ID search:
- You must specify a data set (the form will not let you proceed until
this has been specified). The Data Set button in this section takes you to another page that lets
you specify your data set.
- Enter the local granule ID of the granule in the supplied text box. Note that
you must already know the precise local granule ID.
- You are only able to search for one local granule ID at a time.
- You may enter a string of up to 80 characters maximum to specify a local
granule ID.
- A default global geographic area is set and is not editable.
Choose Additional Options
Max Search Time:
Some searches take a long time to run. Your search
will automatically stop when the maximum search time is reached, any partial
results will be displayed. You can change the maximum search time
to any whole number of minutes up to the default maximum.
Query Name:
The name the system will try to give to the query when you save
the query (download) to your local machine. Note, that some versions
of Microsoft Internet Explorer ignore this and create their own bizarre
file names.
Start Search
Once you've specified a data set and local granule id,
click on the Start Search! button to start your search.
Upload/Download a Query
At the bottom of the page, you'll see this section.
If you've named your query, you can download a copy of it
to your local machine and save it by clicking on the Download query button.
If you've already got a saved query, you can click on the browse button to
show the browser where your query is and then upload it with the Upload
Query button. The search type will be set to your current selection and not
the search type from the uploaded file.
Search Types
Using these links located on the lower left side of the page,
you can switch to the Primary Data Search Form,
Detailed Document Search Form, the
Summary Document Search Form or the
Data Granule ID Search by clicking on the
proper link.
You can also switch to the Primary Data Search Form by clicking the
link at the top of the page.
Local Granule ID search supports the following criteria for refining your search:
Send us your comments.
NASA/GSFC Task Representative:
Medora Macie, Mail Code 423, NASA/GSFC, Greenbelt, MD 20771