https://github.com/openearth/hydro-engine
Hydro Engine is a service and a command-line tool to query static and dynamic hydrographic data derived from Earth Observations
https://github.com/openearth/hydro-engine
google-earth-engine hydrology remote-sensing
Last synced: 6 months ago
JSON representation
Hydro Engine is a service and a command-line tool to query static and dynamic hydrographic data derived from Earth Observations
- Host: GitHub
- URL: https://github.com/openearth/hydro-engine
- Owner: openearth
- License: mit
- Created: 2017-06-23T08:58:20.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2018-11-01T16:51:19.000Z (over 7 years ago)
- Last Synced: 2024-06-11T17:13:43.568Z (about 2 years ago)
- Topics: google-earth-engine, hydrology, remote-sensing
- Language: Jupyter Notebook
- Homepage:
- Size: 13.1 MB
- Stars: 28
- Watchers: 13
- Forks: 9
- Open Issues: 16
-
Metadata Files:
- Readme: README.md
- Changelog: HISTORY.rst
- Contributing: CONTRIBUTING.rst
- License: LICENSE
Awesome Lists containing this project
README
**Hydro Engine** is a small service and a command-line tool built on top of [Google Earth Engine](http://earthengine.google.com) that allows querying various hydrological variables, useful as an input for hydrological models.
[](https://travis-ci.org/openearth/hydro-engine)
The command-line Python tool can be installed using the following commands:
```
> pip install hydroengine
```
Once the package is installed, you can use ```hydroengine``` command to download input data needed for your hydrological model.
Upstream catchments, rivers and various raster variables can be queried using following commands:
```
> hydroengine region.json --get-catchments catchments.json
> hydroengine region.json --get-rivers rivers.json
> hydroengine region.json --get-raster dem dem.tif 1000 EPSG:4326
> hydroengine region.json --get-lakes lakes.json
> hydroengine region.json --get-lake-variable 183160 water_area area.json
```
See [examples/run.sh](https://github.com/Deltares/hydro-engine/blob/master/examples/run.sh), showing how different data types can be downloaded.
All data types can be queried for an input area or location (GeoJSON polygon geometry). A polygon may define a flood location. For example, in the figure below, a single point near Houston is used to query upstream catchments and a drainage network, providing runoff water for that location.
Supported functionality:
* Querying upstream catchments as a single or multiple polygons. Source: [HydroBASINS](http://www.hydrosheds.org/page/hydrobasins)
* Querying upstream drainage network as polylines. Source: [HydroSHEDS](http://hydrosheds.org)
* Querying raster variables:
* dem [m] - in meters, source: 30m SRTM v4
* hand [m] - Height Above the Nearest Drainage ([HAND](http://global-hand.appspot.com))
* FirstZoneCapacity [-] - ?
* FirstZoneKsatVer [-] - ?
* FirstZoneMinCapacity [-] - ?
* InfiltCapSoil [-] - ?
* M [-] - ?
* PathFrac [-] - ?
* WaterFrac [-] - ?
* thetaS [-] - ?
* soil_type [-] - soil type, based on ?
* landuse [-] - land use type, based on MODIS 500m
* LAI01...LAI12 - leaf area index monthly climatology, source: [eartH2Observe](http://www.earth2observe.eu/)