help page showing

What is OneStop:

OneStop is a distributed, scalable, event-driven database and search engine for environmental data. It is being built by CIRES researchers on a grant from the NOAA National Centers for Environmental Information.

For additional documentation go thegithub OneStop documentation page.

How to use this interface:

To get started searching type a term into the Search Box above and submit or click the Search Button

Querying tips:

  • Use the filters menu on the search results page to limit the results to only those that intersect the given constraints. Once a filter has been applied, a tag will be placed above the search results.
  • Wrap a search phrase in double quotes for an exact match:
    • "sea surface temperature"

    Note: Capitalization is ignored.

  • Use + to indicate that a search term must appear in the results and - to indicate that it must not. Terms without a + or - are considered optional.
    • temperature pressure +air -sea

    Note: This means hyphens within search terms will be treated as spaces; use double quotes to search for a term with a hyphen in it.

  • Use of AND, OR, and AND NOT provides similar logic to + and -, but introduces operator precedence which makes for a more complicated query structure. The following example gives the same results as the previous one:
    • ((temperature AND air) OR (pressure AND air) OR air) AND NOT sea
  • Not sure if you misspelled something? Not to worry, simply place a tilde after the word you're unsure on:
    • ghrst~
  • The title, description, and keywords of a data set's metadata can be searched directly by appending the field name and a colon to the beginning of your search term (remember -- no spaces before or after the colon and wrap multi-word terms in parentheses). Exact matches can be requested here as well:
    • description:lakes
    • title:"Tsunami Inundation"
    • keywords:(ice deformation)
  • Metadata can also be searched by using a regex. Regex terms can be written using two different methods. The easiest method is to use double quotes to capture the regex along with the reserved characters literally. Regex terms must be enclosed with forward slashes. Regex terms not enclosed with double quotes must have every reserved character escaped by a backslash.
    • "/^GHRSST"
    • "/^GHRSST.*(Version 2)$"
    • \/\^GHRSST
    • \/\^GHRSST\.\*(Version 2)\$\/

More Information

Find more information about interacting directly with the OneStop API.