tsgettoolbox.wdfn_time_series_revisions#
- tsgettoolbox.wdfn_time_series_revisions(*, geometry: Any = None, id: str = None, monitoring_location_id: str = None, time_series_id: str = None, revision_note: str = None, begin: str = None, end: str = None)#
US:station::E:USGS WDFN Time series revisions as time-series
Approved water data are considered published record, but on occasion changes or deletions (revisions) must be made to data after they are approved. Data revisions are rare because of USGS quality assurance practices, including documentation of all data before they are officially approved. This field contains text explanations for data revisions on a specific time series. Changes to data also are indicated with revision qualifier codes alongside the data. Text explanations before 2017 are not necessarily available online, but can be requested. This collection is non-spatial: revision records carry no geometry, so bbox/spatial filters are not supported.
- Parameters:
geometry – The geometry parameter is used to filter the results by a specific geographic area. The value should be a GeoJSON geometry object.
id – A unique identifier for a single revision record.
monitoring_location_id – 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).
time_series_id – A unique identifier representing a single time series. This corresponds to the id field in the time-series-metadata endpoint.
revision_note – Approved water data are considered published record, but on occasion changes or deletions (revisions) must be made to data after they are approved. Data revisions are rare because of USGS quality assurance practices, including documentation of all data before they are officially approved. This field contains text explanations for data revisions at this monitoring location. Changes to data also are indicated with revision qualifier codes alongside the data. Text explanations before 2017 are not necessarily available online, but can be requested.
begin –
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 –
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.