hydroinform
This package contains a steady-state stream model and some tools to access .dfs-files from DHI
Usage
Convert .dfs, res1d and res11-files to netCDF:
#Import NetCDF and DFS from hydroinform
from hydroinform import NetCDF, DFS
#Saves "omr4_jag_3DSZ.dfs3 as "omr4_jag_3DSZ.nc"
NetCDF.save_as_NetCDF('omr4_jag_3DSZ.dfs3')
#Saves "omr4_jag_3DSZ.dfs3 as "newname.nc"
NetCDF.save_as_NetCDF('omr4_jag_3DSZ.dfs3','newname.nc')
#Saves only the first item and the second and fourth time step from "omr4_jag_3DSZ.dfs3""
d= DFS.DFSBase.open_file('omr4_jag_3DSZ.dfs3')
NetCDF.save_dfs_as_NetCDF(d, [0], [1,3], 'omr4_jag_3DSZ_one_time.nc')
#Saves the discharge data from "Storaa_HD_quasiStationary_20090701.res1d" as 'Storaa_HD_quasiStationary_20090701.nc'
NetCDF.save_as_NetCDF('Storaa_HD_quasiStationary_20090701.res1d')
Write a pump extraction file to be used with MikeZero:
#Import DFS from HydroInform
from hydroinform import DFS
import datetime
#The number of Items (In this case number of pumping wells)
numberofitems = 5;
#Now create the file.
_tso = DFS.DFS0.new_file(r'c:\temp\extraction.dfs0', numberofitems);
#Loop the items and set the units etc.
for itemCount in range (0, numberofitems):
_tso.items[itemCount].value_type = DFS.DataValueType.MeanStepBackward
_tso.items[itemCount].eum_item = DFS.EumItem.eumIPumpingRate
_tso.items[itemCount].eum_unit = DFS.EumUnit.eumUm3PerYear
_tso.items[itemCount].name = "Item number: " + str(itemCount)
#Loop the years where you have pumping data
tscount = 0;
for year in range(2010, 2016):
#For every year append a new timestep
_tso.append_time_step(datetime.datetime(year, 12, 31, 12))
#Loop the items and set a value for this timestep
for itemCount in range (0, numberofitems):
#Sets the data. Note that timesteps count from 0 and Items count from 1
_tso.set_data(tscount, itemCount+1, year * itemCount)
tscount+=1
#Call dispose which will save and close the file.
_tso.dispose()
Metadata
Release files for hydroinform 0.1.17
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hydroinform-0.1.17.tar.gz | 47.4 kB | Without provenance | Details for hydroinform-0.1.17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hydroinform-0.1.17-py3-none-any.whl | Python 3 | none | any | Details for hydroinform-0.1.17-py3-none-any.whl |
Total release size: 97.1 kB
Release files / hydroinform-0.1.17.tar.gz
| Download URL | hydroinform-0.1.17.tar.gz |
|---|---|
| Size | 47.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4ad429b18ff2c0b56feb6f19eeb7a79af34e04cbb6ff03d5dd3242b1dbcada2
|
|
BLAKE2b-256 checksum How to use checksums |
4c454b0b97be5b2882f930dd959e5256dd5078e3013d5aa52112a801b183ffaf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.8
|
Release files / hydroinform-0.1.17-py3-none-any.whl
| Download URL | hydroinform-0.1.17-py3-none-any.whl |
|---|---|
| Size | 49.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b6f785cbef9149232040466b3872486fd1a03f3a932db61e299fe7f8ce0ba86
|
|
BLAKE2b-256 checksum How to use checksums |
fe99b5b3e4b5bf82c22b5d5b0bb07d41d0ac1bd87fd42152d981a9ec1707a5d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.8
|
Security for hydroinform 0.1.17
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.