# properties.id.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`.

# properties.monitoring_location_id.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).

# properties.field_visit_id.description
A universally unique identifier (UUID) for the field visit. Multiple measurements may be made during a single field visit.

# properties.time.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.

# properties.channel_location_distance_unit.description
The units for channel location distance.

# properties.last_modified.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.

# properties.channel_location_direction.description
Location of the measurement from the gage.