# components.parameters.bbox.description
Only features that have a geometry that intersects the bounding box are selected.The bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (height or depth).

# components.parameters.bbox-crs.description
Indicates the coordinate reference system for the given bbox coordinates.

# components.parameters.bbox-crs-epsg.description
Indicates the EPSG for the given bbox coordinates.

# components.parameters.crs.description
Indicates the coordinate reference system for the results.

# components.parameters.f.description
The optional f parameter indicates the output format which the server shall provide as part of the response document.  The default format is GeoJSON.  CSV is also available.

# components.parameters.lang.description
The optional lang parameter instructs the server return a response in a certain language, if supported.  If the language is not among the available values, the Accept-Language header language will be used if it is supported. If the header is missing, the default server language is used. Note that providers may only support a single language (or often no language at all), that can be different from the server language.  Language strings can be written in a complex (e.g. "fr-CA,fr;q=0.9,en-US;q=0.8,en;q=0.7"), simple (e.g. "de") or locale-like (e.g. "de-CH" or "fr_BE") fashion.

# components.parameters.offset.description
The optional offset parameter indicates the index within the result set from which the server shall begin presenting results in the response document.  The first element has an index of 0 (default).

# components.parameters.skipGeometry.description
This option can be used to skip response geometries for each feature.

# components.parameters.vendorSpecificParameters.description
Additional "free-form" parameters that are not explicitly defined

# components.responses.Tiles.description
Retrieves the tiles description for this collection

# components.schemas.queryable.properties.description.description
a human-readable narrative describing the queryable

# components.schemas.queryable.properties.language.description
the language used for the title and description

# components.schemas.queryable.properties.queryable.description
the token that may be used in a CQL predicate

# components.schemas.queryable.properties.title.description
a human readable title for the queryable

# components.schemas.queryable.properties.type-ref.description
a reference to the formal definition of the type

# components.securitySchemes.ApiKeyHeader.description
Providing your API key gives you higher rate limits when querying our APIs. You can obtain an API key at https://api.waterdata.usgs.gov/signup

# components.securitySchemes.ApiKeyQuery.description
Providing your API key gives you higher rate limits when querying our APIs. You can obtain an API key at https://api.waterdata.usgs.gov/signup

# info.contact.name
US Geological Survey - Water Data for the Nation

# info.description
These APIs provide OGC-compliant interfaces to USGS water data, letting you download continuous sensor measurements, discrete field measurements, metadata about monitoring locations, and more. These APIs are currently in a beta status, and should not be relied upon for production workloads.

# paths./collections/daily.get.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/items.get.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/items.get.parameters[].description
The properties that should be included for each feature. The parameter value is a comma-separated list of property names.

# paths./collections/daily/items.get.parameters[].description
A universally unique identifier (UUID) representing a single version of a record. It is not stable over time. Every time the record is refreshed in our database (which may happen as part of normal operations and does not imply any change to the data itself) a new ID will be generated. To uniquely identify a single observation over time, compare the `time` and `time_series_id` fields; each time series will only have a single observation at a given `time`.

# paths./collections/daily/items.get.parameters[].schema.description
A universally unique identifier (UUID) representing a single version of a record. It is not stable over time. Every time the record is refreshed in our database (which may happen as part of normal operations and does not imply any change to the data itself) a new ID will be generated. To uniquely identify a single observation over time, compare the `time` and `time_series_id` fields; each time series will only have a single observation at a given `time`.

# paths./collections/daily/items.get.parameters[].description
A unique identifier representing a single time series. This corresponds to the `id` field in the `time-series-metadata` endpoint.

# paths./collections/daily/items.get.parameters[].schema.description
A unique identifier representing a single time series. This corresponds to the `id` field in the `time-series-metadata` endpoint.

# paths./collections/daily/items.get.parameters[].description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/daily/items.get.parameters[].schema.description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/daily/items.get.parameters[].description
Parameter codes are 5-digit codes used to identify the constituent measured and the units of measure. A complete list of parameter codes and associated groupings can be found at [https://help.waterdata.usgs.gov/codes-and-parameters/parameters](https://help.waterdata.usgs.gov/codes-and-parameters/parameters).

# paths./collections/daily/items.get.parameters[].schema.description
Parameter codes are 5-digit codes used to identify the constituent measured and the units of measure. A complete list of parameter codes and associated groupings can be found at [https://help.waterdata.usgs.gov/codes-and-parameters/parameters](https://help.waterdata.usgs.gov/codes-and-parameters/parameters).

# paths./collections/daily/items.get.parameters[].description
A code corresponding to the statistic an observation represents. Example codes include 00001 (max), 00002 (min), and 00003 (mean). A complete list of codes and their descriptions can be found at [https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html](https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html).

# paths./collections/daily/items.get.parameters[].schema.description
A code corresponding to the statistic an observation represents. Example codes include 00001 (max), 00002 (min), and 00003 (mean). A complete list of codes and their descriptions can be found at [https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html](https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html).

# paths./collections/daily/items.get.parameters[].description
The date an observation represents. You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `time` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/daily/items.get.parameters[].schema.description
The date an observation represents. You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `time` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/daily/items.get.parameters[].description
The value of the observation. Values are transmitted as strings in the JSON response format in order to preserve precision.

# paths./collections/daily/items.get.parameters[].schema.description
The value of the observation. Values are transmitted as strings in the JSON response format in order to preserve precision.

# paths./collections/daily/items.get.parameters[].description
A human-readable description of the units of measurement associated with an observation.

# paths./collections/daily/items.get.parameters[].schema.description
A human-readable description of the units of measurement associated with an observation.

# paths./collections/daily/items.get.parameters[].description
Some of the data that you have obtained from this U.S. Geological Survey database may not have received Director's approval.  Any such data values are qualified as provisional and are subject to revision.  Provisional data are released on the condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its use. This field reflects the approval status of each record, and is either "Approved", meaining processing review has been completed and the data is approved for publication, or "Provisional" and subject to revision. For more information about provisional data, go to [https://waterdata.usgs.gov/provisional-data-statement/](https://waterdata.usgs.gov/provisional-data-statement/).

# paths./collections/daily/items.get.parameters[].schema.description
Some of the data that you have obtained from this U.S. Geological Survey database may not have received Director's approval.  Any such data values are qualified as provisional and are subject to revision.  Provisional data are released on the condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its use. This field reflects the approval status of each record, and is either "Approved", meaining processing review has been completed and the data is approved for publication, or "Provisional" and subject to revision. For more information about provisional data, go to [https://waterdata.usgs.gov/provisional-data-statement/](https://waterdata.usgs.gov/provisional-data-statement/).

# paths./collections/daily/items.get.parameters[].description
This field indicates any qualifiers associated with an observation, for instance if a sensor may have been impacted by ice or if values were estimated.

# paths./collections/daily/items.get.parameters[].schema.description
This field indicates any qualifiers associated with an observation, for instance if a sensor may have been impacted by ice or if values were estimated.

# paths./collections/daily/items.get.parameters[].description
The last time a record was refreshed in our database. This may happen due to regular operational processes and does not necessarily indicate anything about the measurement has changed.
You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `last_modified` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/daily/items.get.parameters[].schema.description
The last time a record was refreshed in our database. This may happen due to regular operational processes and does not necessarily indicate anything about the measurement has changed.
You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `last_modified` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/daily/items.options.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/items/{featureId}.get.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/items/{featureId}.options.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/queryables.get.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/daily/schema.get.description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# paths./collections/monitoring-locations.get.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/items.get.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/items.get.parameters[].description
The properties that should be included for each feature. The parameter value is a comma-separated list of property names.

# paths./collections/monitoring-locations/items.get.parameters[].description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/monitoring-locations/items.get.parameters[].description
The agency that is reporting the data. Agency codes are fixed values assigned by the National Water Information System (NWIS). A list of agency codes is available [at this link](https://help.waterdata.usgs.gov/code/agency_cd_query?fmt=html).

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The agency that is reporting the data. Agency codes are fixed values assigned by the National Water Information System (NWIS). A list of agency codes is available [at this link](https://help.waterdata.usgs.gov/code/agency_cd_query?fmt=html).

# paths./collections/monitoring-locations/items.get.parameters[].description
The name of the agency that is reporting the data.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The name of the agency that is reporting the data.

# paths./collections/monitoring-locations/items.get.parameters[].description
Each monitoring location in the USGS data base has a unique 8- to 15-digit identification number. Monitoring location numbers are assigned [based on this logic](https://help.waterdata.usgs.gov/faq/sites/do-station-numbers-have-any-particular-meaning).

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Each monitoring location in the USGS data base has a unique 8- to 15-digit identification number. Monitoring location numbers are assigned [based on this logic](https://help.waterdata.usgs.gov/faq/sites/do-station-numbers-have-any-particular-meaning).

# paths./collections/monitoring-locations/items.get.parameters[].description
This is the official name of the monitoring location in the database. For well information this can be a district-assigned local number.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
This is the official name of the monitoring location in the database. For well information this can be a district-assigned local number.

# paths./collections/monitoring-locations/items.get.parameters[].description
The Water Science Centers (WSCs) across the United States use the FIPS state code as the district code. In some case, monitoring locations and samples may be managed by a water science center that is adjacent to the state in which the monitoring location actually resides. For example a monitoring location may have a district code of 30 which translates to Montana, but the state code could be 56 for Wyoming because that is where the monitoring location actually is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The Water Science Centers (WSCs) across the United States use the FIPS state code as the district code. In some case, monitoring locations and samples may be managed by a water science center that is adjacent to the state in which the monitoring location actually resides. For example a monitoring location may have a district code of 30 which translates to Montana, but the state code could be 56 for Wyoming because that is where the monitoring location actually is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
The code for the country in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The code for the country in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
The name of the country in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The name of the country in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
State code. A [two-digit ANSI code](https://www2.census.gov/geo/docs/reference/state.txt) (formerly FIPS code) as defined by the American National Standards Institute, to define States and equivalents. A three-digit ANSI code is used to define counties and county equivalents. [A lookup table is available.](https://www.census.gov/library/reference/code-lists/ansi.html#states) The only countries with political subdivisions other than the US are Mexico and Canada. The Mexican states have US state codes ranging from 81-86 and Canadian provinces have state codes ranging from 90-98.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
State code. A [two-digit ANSI code](https://www2.census.gov/geo/docs/reference/state.txt) (formerly FIPS code) as defined by the American National Standards Institute, to define States and equivalents. A three-digit ANSI code is used to define counties and county equivalents. [A lookup table is available.](https://www.census.gov/library/reference/code-lists/ansi.html#states) The only countries with political subdivisions other than the US are Mexico and Canada. The Mexican states have US state codes ranging from 81-86 and Canadian provinces have state codes ranging from 90-98.

# paths./collections/monitoring-locations/items.get.parameters[].description
The name of the state or state equivalent in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The name of the state or state equivalent in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
The code for the county or county equivalent (parish, borough, etc.) in which the monitoring location is located. [A list of codes is available.](https://help.waterdata.usgs.gov/code/county_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The code for the county or county equivalent (parish, borough, etc.) in which the monitoring location is located. [A list of codes is available.](https://help.waterdata.usgs.gov/code/county_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The name of the county or county equivalent (parish, borough, etc.) in which the monitoring location is located. [A list of codes is available.](https://help.waterdata.usgs.gov/code/county_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The name of the county or county equivalent (parish, borough, etc.) in which the monitoring location is located. [A list of codes is available.](https://help.waterdata.usgs.gov/code/county_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Codes for primary governmental or administrative divisions of the county or county equivalent in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Codes for primary governmental or administrative divisions of the county or county equivalent in which the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
A code describing the hydrologic setting of the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/site_tp_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A code describing the hydrologic setting of the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/site_tp_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
A description of the hydrologic setting of the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/site_tp_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A description of the hydrologic setting of the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/site_tp_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The United States is divided and sub-divided into successively smaller hydrologic units which are classified into four levels: regions, sub-regions, accounting units, and cataloging units. The hydrologic units are arranged within each other, from the smallest (cataloging units) to the largest (regions). Each hydrologic unit is identified by a unique hydrologic unit code (HUC) consisting of two to eight digits based on the four levels of classification in the hydrologic unit system.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The United States is divided and sub-divided into successively smaller hydrologic units which are classified into four levels: regions, sub-regions, accounting units, and cataloging units. The hydrologic units are arranged within each other, from the smallest (cataloging units) to the largest (regions). Each hydrologic unit is identified by a unique hydrologic unit code (HUC) consisting of two to eight digits based on the four levels of classification in the hydrologic unit system.

# paths./collections/monitoring-locations/items.get.parameters[].description
The Basin Code or "drainage basin code" is a two-digit code that further subdivides the 8-digit hydrologic-unit code. The drainage basin code is defined by the USGS State Office where the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The Basin Code or "drainage basin code" is a two-digit code that further subdivides the 8-digit hydrologic-unit code. The drainage basin code is defined by the USGS State Office where the monitoring location is located.

# paths./collections/monitoring-locations/items.get.parameters[].description
Altitude of the monitoring location referenced to the specified Vertical Datum.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Altitude of the monitoring location referenced to the specified Vertical Datum.

# paths./collections/monitoring-locations/items.get.parameters[].description
Accuracy of the altitude, in feet. An accuracy of +/- 0.1 foot would be entered as “.1”. Many altitudes are interpolated from the contours on topographic maps; accuracies determined in this way are generally entered as one-half of the contour interval.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Accuracy of the altitude, in feet. An accuracy of +/- 0.1 foot would be entered as “.1”. Many altitudes are interpolated from the contours on topographic maps; accuracies determined in this way are generally entered as one-half of the contour interval.

# paths./collections/monitoring-locations/items.get.parameters[].description
Codes representing the method used to measure altitude. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Codes representing the method used to measure altitude. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The name of the the method used to measure altitude. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The name of the the method used to measure altitude. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The datum used to determine altitude and vertical position at the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The datum used to determine altitude and vertical position at the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The datum used to determine altitude and vertical position at the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The datum used to determine altitude and vertical position at the monitoring location. [A list of codes is available.](https://help.waterdata.usgs.gov/code/alt_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Indicates the accuracy of the latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_acy_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Indicates the accuracy of the latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_acy_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Indicates the accuracy of the latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_acy_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Indicates the accuracy of the latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_acy_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Indicates the method used to determine latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Indicates the method used to determine latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Indicates the method used to determine latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Indicates the method used to determine latitude longitude values. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_meth_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Coordinates are published in EPSG:4326 / WGS84 / World Geodetic System 1984. This field indicates the original datum used to determine coordinates before they were converted. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Coordinates are published in EPSG:4326 / WGS84 / World Geodetic System 1984. This field indicates the original datum used to determine coordinates before they were converted. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Coordinates are published in EPSG:4326 / WGS84 / World Geodetic System 1984. This field indicates the original datum used to determine coordinates before they were converted. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Coordinates are published in EPSG:4326 / WGS84 / World Geodetic System 1984. This field indicates the original datum used to determine coordinates before they were converted. [A list of codes is available.](https://help.waterdata.usgs.gov/code/coord_datum_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
The area enclosed by a topographic divide from which direct surface runoff from precipitation normally drains by gravity into the stream above that point.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The area enclosed by a topographic divide from which direct surface runoff from precipitation normally drains by gravity into the stream above that point.

# paths./collections/monitoring-locations/items.get.parameters[].description
The contributing drainage area of a lake, stream, wetland, or estuary monitoring location, in square miles. This item should be present only if the contributing area is different from the total drainage area. This situation can occur when part of the drainage area consists of very porous soil or depressions that either allow all runoff to enter the groundwater or traps the water in ponds so that rainfall does not contribute to runoff. A transbasin diversion can also affect the total drainage area.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The contributing drainage area of a lake, stream, wetland, or estuary monitoring location, in square miles. This item should be present only if the contributing area is different from the total drainage area. This situation can occur when part of the drainage area consists of very porous soil or depressions that either allow all runoff to enter the groundwater or traps the water in ponds so that rainfall does not contribute to runoff. A transbasin diversion can also affect the total drainage area.

# paths./collections/monitoring-locations/items.get.parameters[].description
A short code describing the time zone used by a monitoring location.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A short code describing the time zone used by a monitoring location.

# paths./collections/monitoring-locations/items.get.parameters[].description
A flag indicating whether or not a monitoring location uses daylight savings.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A flag indicating whether or not a monitoring location uses daylight savings.

# paths./collections/monitoring-locations/items.get.parameters[].description
Local aquifers in the USGS water resources data base are identified by a geohydrologic unit code (a three-digit number related to the age of the formation, followed by a 4 or 5 character abbreviation for the geologic unit or aquifer name). [Additional information is available at this link.](https://help.waterdata.usgs.gov/faq/groundwater/local-aquifer-description)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Local aquifers in the USGS water resources data base are identified by a geohydrologic unit code (a three-digit number related to the age of the formation, followed by a 4 or 5 character abbreviation for the geologic unit or aquifer name). [Additional information is available at this link.](https://help.waterdata.usgs.gov/faq/groundwater/local-aquifer-description)

# paths./collections/monitoring-locations/items.get.parameters[].description
National aquifers are the principal aquifers or aquifer systems in the United States, defined as regionally extensive aquifers or aquifer systems that have the potential to be used as a source of potable water. Not all groundwater monitoring locations can be associated with a National Aquifer. Such monitoring locations will not be retrieved using this search criteria. [A list of National aquifer codes and names is available.](https://help.waterdata.usgs.gov/code/nat_aqfr_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
National aquifers are the principal aquifers or aquifer systems in the United States, defined as regionally extensive aquifers or aquifer systems that have the potential to be used as a source of potable water. Not all groundwater monitoring locations can be associated with a National Aquifer. Such monitoring locations will not be retrieved using this search criteria. [A list of National aquifer codes and names is available.](https://help.waterdata.usgs.gov/code/nat_aqfr_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].description
Groundwater occurs in aquifers under two different conditions. Where water only partly fills an aquifer, the upper surface is free to rise and decline. These aquifers are referred to as unconfined (or water-table) aquifers. Where water completely fills an aquifer that is overlain by a confining bed, the aquifer is referred to as a confined (or artesian) aquifer. When a confined aquifer is penetrated by a well, the water level in the well will rise above the top of the aquifer (but not necessarily above land surface). [Additional information is available at this link.](https://help.waterdata.usgs.gov/faq/groundwater/local-aquifer-description)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
Groundwater occurs in aquifers under two different conditions. Where water only partly fills an aquifer, the upper surface is free to rise and decline. These aquifers are referred to as unconfined (or water-table) aquifers. Where water completely fills an aquifer that is overlain by a confining bed, the aquifer is referred to as a confined (or artesian) aquifer. When a confined aquifer is penetrated by a well, the water level in the well will rise above the top of the aquifer (but not necessarily above land surface). [Additional information is available at this link.](https://help.waterdata.usgs.gov/faq/groundwater/local-aquifer-description)

# paths./collections/monitoring-locations/items.get.parameters[].description
The depth of the finished well, in feet below land surface datum. Note: Not all groundwater monitoring locations have information on Well Depth. Such monitoring locations will not be retrieved using this search criteria.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The depth of the finished well, in feet below land surface datum. Note: Not all groundwater monitoring locations have information on Well Depth. Such monitoring locations will not be retrieved using this search criteria.

# paths./collections/monitoring-locations/items.get.parameters[].description
The total depth to which the hole is drilled, in feet below land surface datum. Note: Not all groundwater monitoring locations have information on Hole Depth. Such monitoring locations will not be retrieved using this search criteria.

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
The total depth to which the hole is drilled, in feet below land surface datum. Note: Not all groundwater monitoring locations have information on Hole Depth. Such monitoring locations will not be retrieved using this search criteria.

# paths./collections/monitoring-locations/items.get.parameters[].description
A code indicating the source of water-level data. [A list of codes is available.](https://help.waterdata.usgs.gov/code/water_level_src_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.get.parameters[].schema.description
A code indicating the source of water-level data. [A list of codes is available.](https://help.waterdata.usgs.gov/code/water_level_src_cd_query?fmt=html)

# paths./collections/monitoring-locations/items.options.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/items/{featureId}.get.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/items/{featureId}.options.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/items/{featureId}.options.summary
Options for Monitoring locations item by id

# paths./collections/monitoring-locations/queryables.get.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/monitoring-locations/schema.get.description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).

# paths./collections/time-series-metadata.get.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/items.get.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/items.get.parameters[].description
The properties that should be included for each feature. The parameter value is a comma-separated list of property names.

# paths./collections/time-series-metadata/items.get.parameters[].description
A unique identifier representing a single time series. This corresponds to the `id` field in the `time-series-metadata` endpoint.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A unique identifier representing a single time series. This corresponds to the `id` field in the `time-series-metadata` endpoint.

# paths./collections/time-series-metadata/items.get.parameters[].description
A human-readable description of the units of measurement associated with an observation.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A human-readable description of the units of measurement associated with an observation.

# paths./collections/time-series-metadata/items.get.parameters[].description
Parameter codes are 5-digit codes used to identify the constituent measured and the units of measure. A complete list of parameter codes and associated groupings can be found at [https://help.waterdata.usgs.gov/codes-and-parameters/parameters](https://help.waterdata.usgs.gov/codes-and-parameters/parameters).

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
Parameter codes are 5-digit codes used to identify the constituent measured and the units of measure. A complete list of parameter codes and associated groupings can be found at [https://help.waterdata.usgs.gov/codes-and-parameters/parameters](https://help.waterdata.usgs.gov/codes-and-parameters/parameters).

# paths./collections/time-series-metadata/items.get.parameters[].description
A code corresponding to the statistic an observation represents. Example codes include 00001 (max), 00002 (min), and 00003 (mean). A complete list of codes and their descriptions can be found at [https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html](https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html).

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A code corresponding to the statistic an observation represents. Example codes include 00001 (max), 00002 (min), and 00003 (mean). A complete list of codes and their descriptions can be found at [https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html](https://help.waterdata.usgs.gov/code/stat_cd_nm_query?stat_nm_cd=%25&fmt=html).

# paths./collections/time-series-metadata/items.get.parameters[].description
The last time a record was refreshed in our database. This may happen due to regular operational processes and does not necessarily indicate anything about the measurement has changed.
You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `last_modified` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
The last time a record was refreshed in our database. This may happen due to regular operational processes and does not necessarily indicate anything about the measurement has changed.
You can query this field using date-times or intervals, adhering to RFC 3339, or using ISO 8601 duration objects. Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

  - A date-time: "2018-02-12T23:20:50Z"
  - A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
  - Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
  - Duration objects: "P1M" for data from the past month or "PT36H" for the last 36 hours

Only features that have a `last_modified` that intersects the value of datetime are selected. If a feature has multiple temporal properties, it is the decision of the server whether only a single temporal property is used to determine the extent or all relevant temporal properties.

# paths./collections/time-series-metadata/items.get.parameters[].description
The datetime of the earliest observation in the time series. Together with `end`, this field represents the period of record of a time series. Note that some time series may have large gaps in their collection record. This field is currently in the local time of the monitoring location. We intend to update this **in version v0** to use UTC with a time zone.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
The datetime of the earliest observation in the time series. Together with `end`, this field represents the period of record of a time series. Note that some time series may have large gaps in their collection record. This field is currently in the local time of the monitoring location. We intend to update this **in version v0** to use UTC with a time zone.

# paths./collections/time-series-metadata/items.get.parameters[].description
The datetime of the most recent observation in the time series. Data returned by this endpoint updates at most once per day, and potentially less frequently than that, and as such there may be more recent observations within a time series than the time series `end` value reflects. Together with `begin`, this field represents the period of record of a time series. It is additionally used to determine whether a time series is "active". We intend to update this **in version v0** to use UTC with a time zone.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
The datetime of the most recent observation in the time series. Data returned by this endpoint updates at most once per day, and potentially less frequently than that, and as such there may be more recent observations within a time series than the time series `end` value reflects. Together with `begin`, this field represents the period of record of a time series. It is additionally used to determine whether a time series is "active". We intend to update this **in version v0** to use UTC with a time zone.

# paths./collections/time-series-metadata/items.get.parameters[].schema.title
Time series most recent observation timestamp

# paths./collections/time-series-metadata/items.get.parameters[].description
Indicates the period of data used for any statistical computations.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
Indicates the period of data used for any statistical computations.

# paths./collections/time-series-metadata/items.get.parameters[].description
Indicates whether the data from this time series represent a specific statistical computation.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
Indicates whether the data from this time series represent a specific statistical computation.

# paths./collections/time-series-metadata/items.get.parameters[].description
Thresholds represent known numeric limits for a time series, for example the historic maximum value for a parameter or a level below which a sensor is non-operative. These thresholds are sometimes used to automatically determine if an observation is erroneous due to sensor error, and therefore shouldn't be included in the time series.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
Thresholds represent known numeric limits for a time series, for example the historic maximum value for a parameter or a level below which a sensor is non-operative. These thresholds are sometimes used to automatically determine if an observation is erroneous due to sensor error, and therefore shouldn't be included in the time series.

# paths./collections/time-series-metadata/items.get.parameters[].description
An optional human-readable identifier used to specify where measurements are recorded at a monitoring location.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
An optional human-readable identifier used to specify where measurements are recorded at a monitoring location.

# paths./collections/time-series-metadata/items.get.parameters[].description
A flag identifying if the time series is a "primary" time series. "Primary" time series (which have this flag) are standard observations which undergo [Bureau review and approval processes](https://www.usgs.gov/survey-manual/5028-fundamental-science-practices-review-and-approval-scientific-data-release). Non-primary time series, which will have missing values for "primary", are provisional datasets made available to meet the need for timely best science and to assist with daily operations which need real-time information. Non-primary time series data are only retained by this system for 120 days. See the [USGS Provisional Data Statement](https://waterdata.usgs.gov/provisional-data-statement/) for more information.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A flag identifying if the time series is a "primary" time series. "Primary" time series (which have this flag) are standard observations which undergo [Bureau review and approval processes](https://www.usgs.gov/survey-manual/5028-fundamental-science-practices-review-and-approval-scientific-data-release). Non-primary time series, which will have missing values for "primary", are provisional datasets made available to meet the need for timely best science and to assist with daily operations which need real-time information. Non-primary time series data are only retained by this system for 120 days. See the [USGS Provisional Data Statement](https://waterdata.usgs.gov/provisional-data-statement/) for more information.

# paths./collections/time-series-metadata/items.get.parameters[].description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A unique identifier representing a single monitoring location. This corresponds to the `id` field in the `monitoring-locations` endpoint. Monitoring location IDs are created by combining the agency code of the agency responsible for the monitoring location (e.g. USGS) with the ID number of the monitoring location (e.g. 02238500), separated by a hyphen (e.g. USGS-02238500).

# paths./collections/time-series-metadata/items.get.parameters[].description
A description of what this time series represents, as used by WDFN and other USGS data dissemination products.

# paths./collections/time-series-metadata/items.get.parameters[].schema.description
A description of what this time series represents, as used by WDFN and other USGS data dissemination products.

# paths./collections/time-series-metadata/items.options.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/items/{featureId}.get.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/items/{featureId}.options.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/items/{featureId}.options.summary
Options for Time series metadata item by id

# paths./collections/time-series-metadata/queryables.get.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# paths./collections/time-series-metadata/schema.get.description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# servers[].description
These APIs provide OGC-compliant interfaces to USGS water data, letting you download continuous sensor measurements, discrete field measurements, metadata about monitoring locations, and more. These APIs are currently in a beta status, and should not be relied upon for production workloads.

# tags[].description
These APIs provide OGC-compliant interfaces to USGS water data, letting you download continuous sensor measurements, discrete field measurements, metadata about monitoring locations, and more. These APIs are currently in a beta status, and should not be relied upon for production workloads.

# tags[].description
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collected manually at the monitoring location once each day. With improved availability of computer storage and automated transmission of data, the daily data published today are generally a statistical summary or metric of the continuous data collected each day, such as the daily mean, minimum, or maximum value. Daily data are automatically calculated from the continuous data of the same parameter code and are described by parameter code and a statistic code. These data have also been referred to as “daily values” or “DV”.

# tags[].description
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard statistic, at a single monitoring location. This endpoint provides metadata about those time series, including their operational thresholds, units of measurement, and when the earliest and most recent observations in a time series occurred.

# tags[].description
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was established. It also includes information about the type of location, such as stream, lake, or groundwater, and geographic information about the location, such as state, county, latitude and longitude, and hydrologic unit code (HUC).