HydroDS Documentation
| Authors: | ${ author.name | nameWithoutCommas } ${ author.organization } ${ author.email } | This resource does not have an author who is an active HydroShare user. Contact CUAHSI (help@cuahsi.org) for information on this resource. | |
|---|---|---|---|
| Owners: |
|
This resource does not have an owner who is an active HydroShare user. Contact CUAHSI (help@cuahsi.org) for information on this resource. | |
| Resource type: | Composite Resource | ||
| Storage: | The size of this resource is 3.9 MB | ||
| Created: | Mar 15, 2017 at 6:30 p.m. | ||
| Last updated: | Feb 04, 2019 at 10:58 p.m.
|
||
| Citation: | See how to cite this resource |
| Sharing Status: | Public |
|---|---|
| Views: | 1237 |
| Downloads: | 155 |
| +1 Votes: | Be the first one to this. |
| Comments: | No comments (yet) |
Abstract
This document provides brief descriptions of HydroDS, a data processing web-based service for distributed/gridded hydrological models. HydroDS enables the generation of distributed (gridded) data for variables commonly used in hydrologic models in three widely used file formats: GeoTiff raster, shapefile, and multi-dimensional NetCDF. HydroDS provides functions for watershed delineation, terrain processing, estimation of canopy variables, and retrieval of climate data. The functions can be used independently or chained together to form a workflow that performs a set of related tasks.
Subject Keywords
Deleting all keywords will set the resource sharing status to private.
Content
This resource contains links to external content. Linked content is
NOT stored in HydroShare, and we can't guarantee its availability, quality, or
security.
readme.txt
This folder contains documenttation for the HydroDS. To open the files, inside the folder hydrodsDoc/html open "genindex.html" and you will see indexed entrees where the service functions are organized alphabetically. Clicking on a link leads to the documentation for each service function. To see descriptions of all functions, open "hydrods_python_client.html". The order of the functions inside "hydrods_python_client.html" represents my suggested order of implementation--which is also roughly the order of calling the services to process UEB inputs.
How to Cite
Gichamo, T. (2019). HydroDS Documentation, HydroShare, http://www.hydroshare.org/resource/130373d3ebde4df489a4781e62211574
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