OB_Cloud Data Browser

The OB_CLOUD Data Browser is a tool for browsing the Ocean Biology OB.DAAC satellite data which resides in the NASA Earthdata cloud. This tool interfaces with the Harmony Search Service and leverages CMR (Common Metadata Repository) for granule-level metadata retrieval.

• Mission-aware metadata filtering using satellite/instrument, data level, and product names.

• Integrated spatial and temporal filters, with automatic date validation based on mission-specific coverage.

• Granule preview support, with hover-based thumbnail loading from browse_images, and full-resolution image viewing.

• Granule pagination and result management, decoupling total fetch limit from per-page display.

The search for satellite data can be restricted to a specific satellite mission, data level and product.

This is what is commonly referred to as the satellite mission. Note that for certain sensor designs, (for instance VIIRS, MODIS, OLI, OLCI, etc.) there can be multiple missions. This is usually delineated and contained in short form in the satellite mission name.

Note: you can only select one mission ('Satellite/Instrument') per search. This is because the data levels (and especially the products) are specific to each mission, and those selectors are dynamically configured based on the mission you choose.

The search for satellite data can be restricted based on a time period. Included within this are options to restrict based on whether the data was imaged in the daytime or nighttime.

This is the start date of the data. If this is field is left blank then no start date restriction is applied (effectively meaning the start of the mission).

This is the stop date of the data. If this is field is left blank then no stop date restriction is applied (effectively meaning the current date).

These are the options to restrict based on whether the data was imaged in the daytime or nighttime.

The search for satellite data can be restricted to a user specified geographic region of interest. This is done through parameters known as a geographic 'bounding_box', which is defined by the fields: 'North', 'South', 'West' and 'East'. The search will only return satellite data files which match in part or in full the user requested bounding_box.

Keep in mind that satellite data (such as unprojected level-2 data) is oriented to the actual observation of the earth made by the satellite, and is not generally precisely represented by a North, South, West, East bounding box. So this can result in extra files being returned by the search which do not actually have data in the user requested bounding box.

Northernmost latitude relative to requested region
(used in field 'bounding_box' of API)
Default is effectively 90.0

Southernmost latitude relative to requested region
(used in field 'bounding_box' of API)
Default is effectively 90.0

Westernmost longitude relative to requested region
(used in field 'bounding_box' of API)
Default is effectively -180.0

Easternmost longitude relative to requested region
(used in field 'bounding_box' of API)
Default is effectively 180.0

The internal format which is ultimately used for the spatial fields is the numeric decimal format. However, the browser tool will accept and convert most any format.

The following table illustrates the full list of optional formats (shown in example for a sample point in the Chesapeake Bay).

Format	Lat	Lon
Decimal_Degrees (Numeric)	37.85	-76.15
Decimal_Degrees (Compass)	37.8°N	76.15°W
Degrees (Numeric)	37°	-76°
Degrees (Compass)	37°N	76°W
Degrees_Minutes (Numeric)	37°48′	-76°6′
Degrees_Minutes (Compass)	37°48′N	76°6′W
Degrees_Minutes_Seconds (Numeric)	37°48′00″	-76°6′00″
Degrees_Minutes_Seconds (Compass)	37°48′00″N	76°6′00″W

Note: for the format of minutes and seconds: the single quote and double quote characters can optionally be used instead of the alphanumeric prime characters.

There are several accessory fields which can aid in populating the 'North', 'South', 'West' and 'East' fields. These fields themselves are not actually used in the search, but only to populate the mentioned bounding box fields.

This is a single coordinate point (latitude longitude) to serve as the center of the scene. The 'Box Size' is used in combination with the 'Coordinates' to populate the 'North', 'South', 'West' and 'East' fields.

This is size of the region (in degrees). The 'Box Size' is used in combination with the 'Coordinates' to populate the 'North', 'South', 'West' and 'East' fields.

This value defines the width and height (in degrees) of the region which is centered on the value in the 'Coordinates' field. (See Example 1 below).

This two-dimension value (format lon x lat) defines the width and height (in degrees) of the region which is centered on the value in the 'Coordinates' field. (See Example 2 below).

This selector contains pre-defined stored geographic locations. Each entry is a single point location, defined by a location name and it's associated coordinates. Selecting a location will then load the value into the "Coordinates" field. The loaded 'Coordinates' field, in combination with the 'Box Size', will then automatically update the 'North', 'South', 'West' and 'East' fields.

For reference: the non-editable configuration file which contains the 'Preset Locations' is:

A few examples illustrating the how the 'Preset Locations', 'Coordinates', and 'Box Size' fields combine to auto-populate the 'North', 'South', 'West' and 'East' fields.

Example 1
Setting 'Box Size' with a single number

In this example the user sets the 'Box Size' and the 'Coordinates'. The 'North', 'South', 'West' and 'East' fields then get auto-filled.

Here the 'Box Size' is set to a number ('1') and the 'Coordinates' are also set. Then the 'North', 'South', 'West' and 'East' fields get auto-filled.

A 'Box Size' of '1' means that the box will span west-east by 1 degree and span north-south by 1 degree centered about the 'Coordinates'.

Hence:
◦ 'North' is set to the lat of 'Coordinates' plus 0.5 degrees
◦ 'South' is set to the lat of 'Coordinates' minus 0.5 degrees
◦ 'West' is set to the lon of 'Coordinates' minus 0.5 degrees
◦ 'East' is set to the lon of 'Coordinates' plus 0.5 degrees

Example 2
Setting 'Box Size' with a two-dimension number

In this example the user sets the 'Box Size' and the 'Coordinates'. The 'North', 'South', 'West' and 'East' fields then get auto-filled.

Here the 'Box Size' is set to a number ('1x2') and the 'Coordinates' are also set. Then the 'North', 'South', 'West' and 'East' fields get auto-filled.

A 'Box Size' of '1x2' means that the box will span west-east by 1 degree and span north-south by 2 degrees centered about the 'Coordinates'.

Hence:
◦ 'North' is set to the lat of 'Coordinates' plus 1 degrees
◦ 'South' is set to the lat of 'Coordinates' minus 1 degrees
◦ 'West' is set to the lon of 'Coordinates' minus 0.5 degrees
◦ 'East' is set to the lon of 'Coordinates' plus 0.5 degrees

The user can define their own locations and regions with two optional selectors ('User Locations' and 'User Regions') which are available in the preferences. Locations are defined as single point coordinates whereas 'Regions' are defined as geographic areas with 'North', 'South', 'West' and 'East' bounds.

Selecting the user-defined 'User Locations' will set the "Coordinates" field, which in turn will set the North, South, West and East fields.

The 'User Locations' field is not available by default, but can easily be added by going to the Preferences page:
(Menu > SeaDAS > Settings > Seadas Toolbox > Earthdata Cloud)
and checking "Include 'User Locations' Selector".

Entries can be added to the 'User Locations' selector by manually editing the following file:
~/.seadas/auxdata/regions/user_locations.txt.

#  Name = Lat Lon
#  (coordinates can be space and/or comma delimited)

My Sample Location = 37°48′00″N, 76°6′00″W

Selecting the user-defined 'User Regions' will directly populate the North, South, West and East fields.

The 'User Regions' field is not available by default, but can easily be added by going to the Preferences page:
(Menu > SeaDAS > Settings > Seadas Toolbox > Earthdata Cloud)
and checking "Include 'User Regions' Selector".

Entries can be added to the 'User Regions' selector by manually editing the following file:
~/.seadas/auxdata/regions/user_regions.txt.

#  Name = North  South  West  East
#  (coordinates can be space and/or comma delimited)

My Sample Region = 39°36′00″N, 35°54′00″N, 77°30′00″E, 74°18′00″E

The bottom row of buttons controls the execution of the search and how the results are displayed.

The search is displayed in table form. Hovering over each filename in the results table, a preview image of the file is displayed if an image preview is available for the file.

Selecting this adds it to the files to be downloaded. Multiple files can be downloaded at once.

This tool is under-construction for a future SeaDAS release. It will make a subset of the selected files.

This opens a file finder window for saving the downloads directory. All files will be downloaded into a single directory.