Checking for non-preferred file/folder path names (may take a long time depending on the number of files/folders) ...
This resource contains some files/folders that have non-preferred characters in their name. Show non-conforming files/folders.
This resource contains content types with files that need to be updated to match with metadata changes. Show content type files that need updating.
HydroServer Demo: Collecting, Organizing, Managing, and Standards-Based Sharing of Hydrologic Observations
| Authors: |
|
|
|---|---|---|
| Owners: |
|
This resource does not have an owner who is an active HydroShare user. Contact CUAHSI (help@cuahsi.org) for information on this resource. |
| Type: | Resource | |
| Storage: | The size of this resource is 72.6 MB | |
| Created: | Apr 28, 2026 at 2:31 p.m. (UTC) | |
| Last updated: | May 04, 2026 at 3:17 p.m. (UTC) | |
| Citation: | See how to cite this resource | |
| Content types: | CSV Content |
| Sharing Status: | Public |
|---|---|
| Views: | 135 |
| Downloads: | 31 |
| +1 Votes: | Be the first one to this. |
| Comments: | No comments (yet) |
Abstract
This resource contains the materials presented to CUAHSI for a demo of the HydroServer software platform. HydroServer is a Hydrologic Information System designed to store, manage, and share a diverse range of time-series data collected at environmental monitoring sites. It is a modular system that provides software tools that help in managing the day-to-day work of running a sensor network and managing the resulting data. The readme file in this resource details the contents and how to launch the example Jupyter Notebooks into the CUAHSI HydroShare-linked JupyterHub environment.
Subject Keywords
Content
README.md
How to Use the Files in this Resource
This HydroShare resource contains presentation slides describing HydroServer's functionality along with example code for interacting with a HydroServer instance.
Resource Contents
The following files are included in this resource:
- Hydroserver_Example1.ipynb: This Jupyter Notebook file contains an example of how to load time series data for a monitoring site from a comma separate values (CSV) file into a datastream in HydroServer.
- Hydroserver_Example2.ipynb: This Jupyter Notebook file contains an example of how to query time series data and associated metadata from HydroServer using the hydroserverpy Python package.
- Hydroserver_Example3.ipynb: This Jupyter Notebook file contains an example of how to use the hydroserverpy Python client package to automate creation, display, and editing of metadata for objects in HydroServer's data model.
- BSF_CONF_BA_SourceID_1_QC_0_Year_2024: This is an example data file containing sensor data used in the first example notebook above to load data for a monitoring site to HydroServer using the hydroserverpy Python client package.
- HydroServer_Presentation.pptx: A PowerPoint presentation file containing the slides from the HydroServer overview presentation.
- HydroServer_Evaluation_Criteria.xlsx: An Excel spreadsheet containing the criteria used to evaluate HydroServer with specific notes about how HydroServer's functionality meets those criterai or not.
IMPORTANT NOTES ABOUT RUNNING THE NOTEBOOKS
- Run the Notebooks in Order: The Notebook files in this resource are designed to be run in order. Run Example 1 before you run Example 2 and 3.
- Get a user account for HydroServer first: The Notebook files in this resource are intended for use with the Playground HydroServer instance https://playground.hydroserver.org. If you want to try them you, you should navigate to the Playground instance first and set up a HydroServer user account there. The notebooks should also work with the CUAHSI HydroServer testing instance. To switch which instance you are using in the code, just change the URL.
Running the Code
Do the following to run the code in this resource:
- Scroll to the top of this HydroShare resource and click the "Open With" button.
- Click "CUAHSI JupyterHub". This will launch the CUAHSI JupyterHub instance with the code and data pre-loaded.
- NOTE: To use this option, you must have a HydroShare user account and be a member of the CUAHSI Cloud Computing Group in HydroShare (sign up at https://www.hydroshare.org/group/156).
- After clicking on the "Open With" button, you will need to log in with HydroShare if you haven't already.
- Select the first Python environment option under "Server Options".
- Scroll to the bottom of the page and click "Start".
- After a few moments your Jupyter Hub Server will activate, and you can double-click on the notebook files in the left column to execute them.
Alternatively, you can download the Jupyter Notebook files and run them locally in your Python environment. If you do that, place them all in the same folder along with the example CSV data file in this resource.
Related Resources
| The content of this resource references | https://github.com/hydroserver2 |
| The content of this resource references | Horsburgh, J. S., Lippold, K., Slaugh, D. L., Ramirez, M. (2025). HydroServer: A software stack supporting collection, communication, storage, management, and sharing of data from in situ environmental sensors, Environmental Modelling & Software, 106637, https://doi.org/10.1016/j.envsoft.2025.106637. |
| The content of this resource references | Horsburgh, J. S., Lippold, K., Slaugh, D. L. (2025). Adapting OGC’s SensorThings API and data model to support data management and sharing for environmental sensors, Environmental Modelling & Software, 183, 106241, https://doi.org/10.1016/j.envsoft.2024.106241. |
Credits
Funding Agencies
This resource was created using funding from the following sources:
| Agency Name | Award Title | Award Number |
|---|---|---|
| National Oceanic and Atmospheric Administration (NOAA) | Cooperative Institute for Research to Operations in Hydrology | NA22NWS4320003 |
| State of Utah Division of Water Rights | None | None |
| World Meteorological Organization | None | None |
How to Cite
This resource is shared under the Creative Commons Attribution CC BY.
http://creativecommons.org/licenses/by/4.0/
Comments
There are currently no comments
New Comment