Site-Specific Time Series Data
Last updated
Last updated
Access Token. Please get in touch with the WaDE Team at WaDE_WSWC@hotmail.com to get an API access token. The token protects the API from bots and attacks. The WaDE team plans to support a personalized token for each user as part of the WesDAAT user management system. We apologize for the inconvenience.
Retrieves historical time series data for two types of data in WaDE for a site by passing in the appropriate options; you can search for available inventory in the system.
Reservoirs and Observation Site Time Series Water Data Reservoir and Observation Site data refer to the historic water flows or volumes by gage stations that States operate year-round or seasonally. This data is separate from streamflow information gathered through federal agencies such as USGS or the U.S. Bureau of Reclamation. Knowing river and reservoir status can help with long-term planning and flood forecasting modeling. Two relative measurements often used are discharge and gage height. Discharge is the rate at which a volume of water passes by a particular location. Gage height is a measurement of the distance between the water's surface above the stream gage's datum reference point (i.e., a unique reference point used to accommodate for changes in a stream channel over time). Reservoirs and Observation Site Water Recordings demo: https://waterdataexchangewswc.shinyapps.io/SiteSpecificReservoirAndObservationSiteDemo/
Public Supply Time Series Data - (Water Use) Refers to the reported deliveries to urban water service areas, known as the place of use (i.e., farmstead, municipal city boundary, residential use, etc.), along with the water source intake locations, known as point of diversion (i.e., river, canal, groundwater, etc.). Put another way, water is withdrawn from site-specific locations and then applied (i.e., depleted) at a different location. Site-Specific Public Supply Water use demo: https://waterdataexchangewswc.shinyapps.io/AggregatedBudgetWaterUseDemo/
Click on the arrow next to the "response" block n the link below to see the API schema and an example response.
Creating easy to ready table for related POD sites per POU site from RelatedPODSites and RelatedPOUSites fields.
Create temp POU table, create temp POD table, then concatenate into single output table.
By passing in the appropriate options, you can search for available inventory in the system
search results matching criteria