Page History
Earthdata Search provides badging with capability icons for datasets that support customizations. Currently, Earthdata Search supports EOSDIS Service Interface (ESI) and OPeNDAP customization. If configured correctly, a UMM-S record will trigger the appropriate icon to be displayed on the associated collection in the Earthdata Search interface, allowing a user to better understand what is available to them.
...
| title | has_* flags |
|---|
The following flags are used by Earthdata Search to trigger badges to display:
| Badge | Type | Flag | Description |
|---|---|---|---|
| Spatial | has_spatial_subsetting |
...
has_transforms – If true, then customizable badge with a transformation icon is shown.
has_variables – If true, then customizable badge with a variable subsetting icon is shown.
has_formats – If true, then customizable badge with a reformatting icon is shown.
has_temporal_subsetting – If true, then customizable badge with a temporal subsetting icon is shown.
| Will be true if spatial subset types are associated with the collection. | |||
| Temporal | has_temporal_subsetting | Will be true if temporal subset types are associated with the collection. |
| Variable | has_variables | Will be true if there are variables associated with the collection. |
| Format | has_formats | Will be true if any of the collection's associated services has more than one "SupportedFormats" value. The collection's "has_formats" flag is false when none of its associated services has more than one "SupportedFormats" value. |
| Transform | has_transforms | Will be true if any of the collection's associated services has a defined “SubsetType” or “InterpolationType”, or multiple “SupportedProjections” values are defined within any of its associated services. A collection’s “has_transforms” flag will only be false if none of its associated services has a defined “SubsetType” or “InterpolationType”, and none of its associated services has more than one “SupportedProjections” value. |
| UI Text Box | ||
|---|---|---|
| ||
| If some of the collections that your DAAC provides do not offer the same capabilities as other collections, you will need a separate UMM-S record that describes the services offered by those collections. For example, If you have 10 collections that offer spatial subsetting, variable subsetting, and reformatting, and 5 collections that offer only spatial subsetting and reformatting, then you will need 2 UMM-S records. One record would be associated with the first 10 and the other with the second set of 5. |
STEP-BY-STEP INSTRUCTIONS
| UI Steps | ||
|---|---|---|
| ||
|
...
|
...
|
...
|
...
|
...
|
...
|
| UI Text Box | ||
|---|---|---|
|
Best Practice Tips
- If some of the collections that your DAAC provides do not offer the same capabilities as other collections, you will need a separate UMM-S record that describes the services offered by those collections. For example, If you have 10 collections that offer spatial subsetting, variable subsetting, and reformatting and 5 collections that offer only spatial subsetting and reformatting, then you will need 2 UMM-S records. One record would be associated with the first 10 and the other with the second set of 5.
| Info | ||
|---|---|---|
| ||
For ESI collections, metadata contained in the tags created by background jobs may also impact the display of the capability iconsbadges. If your collections are showing something other than what you believe should be showing, please contact the EDSC team to investigate. |
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Overview
Content Tools