hydrological processes return to normal levels

#Hydrological processes return to normal levels archive
#Hydrological processes return to normal levels series

The hydrologic cycle involves the continuous circulation of water in the Earth-Atmosphere system.

Preparedness and Mitigation: Individuals (You!).

Preparedness and Mitigation: Communities.

The Positive and Negative Side of Lightning.

Data can be returned in a range of formats including JSON, CSV and web pages. RLOIid=Įach API endpoint provides REST style access List of all monitoring stations can be filtered by name, location and other parameters. Information on monitoring stations at which flows and levels are monitored. Note that the HTML views are offered as an aid to debugging and development,īut they are not intended for presentation to consumers.Īll URIs are relative to the service base URI of. This is a brief summary of the APIs available, see below for details.

#Hydrological processes return to normal levels archive

National River Flow Archive station identifier ( nrfaStationID and nrfaStationURL).National Flood Forecasting Service identifier ( stationReference).the River Levels on the Internet or Check for Flooding identifier ( RLOIid and rloiStationLink).The actual SUID is always available as the stationGuid property of the station metadata, even in cases where the station notation has been disambiguated.Ī number of additional identifier schemes are also available for different subsets of the stations. In those cases the station is identified using a composite key combining the SUID with a disambiguating string (typically a Wiski identifier). In some cases the SUID is not unique, for example due to co-location of multiple distinct sampling points at the same physical station. These are used in the URL for the station and given as the value of the notation property in the station metadata. The primary identifier for most stations uses a GUID style identifier called an SUID ( Station Unique IDentifier).įor Water Quality stations it is based on a shorter ID code. May find it necessary to block users who place excessive demands on the service to the detriment of other users. We reserve the right to enforce limits on the number of concurrent requests (per IP address or identifiable group of IP addresses) and Ideally limit to one request in flight at a time, waiting for each request to finish before issuing the next. N.B.We ask that users who are automatically downloading bulk data to limit the number of non-batch API requests they makeĪt any one time.

#Hydrological processes return to normal levels series

Or split a request for a sub-daily time series into a series of requests for different spans of time. If the service becomes overloaded the limit may be reduced and users may need to either switch to use of the batch api the current hard limit of 2,000,000 rows of data per-call is subject to review. To request more data at a time we provide a batch api alternative which will queue up larger requests, which will then be processed one at a time. This is sufficient to return the whole history of a sub-daily time series, or return all values across all stations for two days. However, we current set a hard limit of 2,000,000 rows, which cannot be overridden. The API calls that return readings data have a soft limit of 100,000 rows per-call which can be overridden by setting a _limit parameter. If downloaded as a single CSV file, that size of data exceeds the number of rows that can be opened in tools such as Excel or LibreOffice. In particular, the entire history of a single sub-daily time series can be up to two million rows. Given this volume of data users should be careful of the volume of data they request and only request the resolution and time span required. The service provides access to over four billion rows of readings.

The API supports estimation of daily logged groundwater by filtering to 9:00am values, see examples below. Note that for logged groundwater data the sub-daily values may be a mix of 15min and hourly intervals. The table entries show the metadata values returned by the API. The column names match the metadata property names returned by the API. The available parameters and time series now available are: parameterName It provides data from nearly eight thousand monitoring stations, and includes sub-daily (typically 15 min) resolution time seriesĪs well as wider range of daily time series. This release of the hydrology service represents a substantial expansion of the range and volume of the data available. The Hydrology API provides access to historic and recent hydrological data including river flows, river levels, groundwater levels, rainfall and water quality.