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.
| 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 3.9 MB | |
| Created: | Mar 15, 2017 at 6:30 p.m. (UTC) | |
| Last updated: | Feb 04, 2019 at 10:58 p.m. (UTC) | |
| Citation: | See how to cite this resource |
| Sharing Status: | Public |
|---|---|
| Views: | 3401 |
| Downloads: | 187 |
| +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
Content
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
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