Pygeohydro

Latest version: v0.19.0

Safety actively analyzes 701139 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 9

0.19.0

-------------------

Internal Changes
~~~~~~~~~~~~~~~~
- Update all dependencies on HyRiver libraries to the latest versions
and modify the code to be compatible with the latest versions of
the libraries.

0.18.0

-------------------

Bug Fixes
~~~~~~~~~
- Bump the minimum version of ``aiohttp-client-cache>=0.12.3`` to fix an
issue with the latest version of ``aiohttp``. (:issue_hydro:`124`)

Breaking Changes
~~~~~~~~~~~~~~~~
- Drop support for Python 3.8 since its end-of-life date is October 2024.
- Remove all exceptions from the main module and raise them from the
``exceptions`` module. This is to declutter the public API and make
it easier to maintain.

0.17.1

-------------------

Internal Changes
~~~~~~~~~~~~~~~~
- Drop support for Python 3.8 since its end-of-life date is October 2024.

Bug Fixes
~~~~~~~~~
- Update the ``nlcd`` module to reflect the changes in the MRLC web service.
There have been some breaking changes in the NLCD web service, and the module
is updated to reflect these changes. Thus, previous versions of the module
will not work with the new NLCD web service. (:issue_hydro:`122`)
- Update the ``nid`` module based on the latest changes to the NID web service.
The changes include the addition of new fields to the NID dataset and the
removal of some fields. The module is updated to reflect these changes.
- Update the ``nfhl`` module to reflect the changes in the NFHL web service.
There have been some breaking changes in the NFHL web service, and the module
is updated to reflect these changes. Thus, previous versions of the module
will not work with the new NFHL web service.

0.17.0

-------------------

New Features
~~~~~~~~~~~~
- Add support for the National Levee Dataset (NLD) from the USACE. The new
class is called ``NLD`` and gives users the ability to subset the NLD
dataset by geometry, ID, or SQL queries. The class has three methods:
``bygeom``, ``byids``, and ``bysql``.

Enhancements
~~~~~~~~~~~~
- Add a new argument to ``EHydro`` for passing a directory to store the
raw downloaded data. This is useful since most times the raw data is
needed for further processing and reuse. So, by storing them in a folder
other than its previous default location, i.e., ``./cache``, users can
easily access and manage them.

Internal Changes
~~~~~~~~~~~~~~~~
- Add the ``exceptions`` module to the high-level API to declutter
the main module. In the future, all exceptions will be raised from
this module and not from the main module. For now, the exceptions
are raised from both modules for backward compatibility.
- Switch to using the ``src`` layout instead of the ``flat`` layout
for the package structure. This is to make the package more
maintainable and to avoid any potential conflicts with other
packages.
- Add artifact attestations to the release workflow.
- Move ``NID`` class to the ``nid`` module to make the package more
organized and the main module less cluttered.

0.16.5

-------------------

New Features
~~~~~~~~~~~~
- Add new function called ``soil_soilgrids`` to get soil data from the
SoilGrids dataset. The signature of the function is the same as of the
``soil_gnatsgo`` function, so they can be used interchangeably.
For more information on the SoilGrids dataset, visit
`ISRIC <https://www.isric.org/explore/soilgrids/faq-soilgrids#What_do_the_filename_codes_mean>`__.

0.16.4

-------------------

Bug Fixes
~~~~~~~~~
- Fix an issue in ``NID.stage_nid_inventory`` where the function was failing
when the response status code was 206 (partial content). This issue is fixed
by checking the response status code and if it's 206, the function will continue
reading the headers and the get the modified date from the response headers.
Also, the function incorrectly didn't check if the local database was up-to-date
with the remote database when the processed database already existed. Now, the
function will check changes in the remote database and re-download the data even if
necessary even if the processed database exists.

Page 1 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.