Skip to main content

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock ( focusable="false" ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.


Field measurements metadata

Schema

Name Title Type Units Values Description
geometry geometry
id Field measurement series ID string
A unique identifier representing a single collection series. This corresponds to the `field_measurement_series_id` field in the `field-measurements` endpoint. Collection series are defined as the set of field measurements at a given monitoring location for a single parameter code using a single reading type.
monitoring_location_id Monitoring location ID string
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).
parameter_code Parameter code string
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://api.waterdata.usgs.gov/ogcapi/v0/collections/parameter-codes/items](https://api.waterdata.usgs.gov/ogcapi/v0/collections/parameter-codes/items).
parameter_name Parameter name string
A human-understandable name corresponding to `parameter_code`.
parameter_description Parameter description string
A description of what the parameter code represents, as used by WDFN and other USGS data dissemination products.
begin Time series first observation timestamp - UTC string
The datetime of the earliest observation in the time series. Together with `end_utc`, this field represents the period of record of a time series. Note that some time series may have large gaps in their collection record. 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 `begin_utc` that intersects the value of datetime are selected.
end Time series most recent observation timestamp - UTC string
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_utc` value reflects. Together with `begin_utc`, this field represents the period of record of a time series. It is additionally used to determine whether a time series is "active". 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 `end_utc` that intersects the value of datetime are selected.
last_modified Last modified date string
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.