Ngiab-data-preprocess

Latest version: v4.1.0

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

Scan your dependencies

Page 5 of 8

2.1.1

using the pyogrio driver instead of the fiona driver means that the automatic crs conversions no longer happen automatically, this addresses that issue and:

- Fixes selection by lat lon
- Fixes the map selection when fiona isn't installed

- Additionally fixes the catchment you clicked on not being highlighted

2.1.0

require geopandas >= 1.0.0 to fix issues installing on arm
crossreference flowpath_attributes and hydrolocations tables to resolve gages being associated with more than one waterbody and nexus

2.0.1

Selecting a time range after the end of the zarr forcing data would cause the caching to fail and redownload all of the forcing data. This is now fixed.

As of writing, this range is `1979-02-01T00:00:00 - 2023-01-31T23:00:00` inclusive

2.0.0

What's Changed
* Remove gdal by JoshCu in https://github.com/CIROH-UA/NGIAB_data_preprocess/pull/37

wb id has been replaced with cat id.
**Previously**, waterbody id was used as the unique identifier for processing the data. The waterbody and everything that flows into it would be added to the selection. The nexus that the selected waterbody flows into would also be added to the selection. This caused incomplete delineation in cases where multiple waterbodies flowed into this final nexus.
In other words, delineation only included waterbodies that merged before entering the catchment area, and exluded those that merged inside the catchment.

_This wasn't clear or intuitive when clicking on a catchment on the map._

Now catchment ids are used in place of waterbody ids, and when you click on a catchment or use the cli, everything that contributes to the outflow of that catchment will be included in the selection.

<details>
<summary><h1>Step by step delineation process comparison</h1></summary>

Old (pseudo inflow and incorrect)
1. Click on a catchment
2. Get the waterbody id for that catchment
3. Get everything upstream of that waterbody
4. Add just the nexus the waterbody flows into

New Catchment id
1. Click on a catchment
2. Get the waterbody id for that catchment
3. Get the nexus that waterbody flows into (the outlet of that catchment)
4. Get everything upstream of that nexus
</details>

**Full Changelog**: https://github.com/CIROH-UA/NGIAB_data_preprocess/compare/v1.4.4...v2.0.0

2.0.0beta

What's Changed
* Remove gdal by JoshCu in https://github.com/CIROH-UA/NGIAB_data_preprocess/pull/37

wb id has been replaced with cat id.
**Previously**, waterbody id was used as the unique identifier for processing the data. The waterbody and everything that flows into it would be added to the selection. The nexus that the selected waterbody flows into would also be added to the selection. This caused incomplete delineation in cases where multiple waterbodies flowed into this final nexus.
In other words, delineation only included waterbodies that merged before entering the catchment area, and exluded those that merged inside the catchment.

_This wasn't clear or intuitive when clicking on a catchment on the map._

Now catchment ids are used in place of waterbody ids, and when you click on a catchment or use the cli, everything that contributes to the outflow of that catchment will be included in the selection.

<details>
<summary><h1>Step by step delineation process comparison</h1></summary>

Old (pseudo inflow and incorrect)
1. Click on a catchment
2. Get the waterbody id for that catchment
3. Get everything upstream of that waterbody
4. Add just the nexus the waterbody flows into

New Catchment id
1. Click on a catchment
2. Get the waterbody id for that catchment
3. Get the nexus that waterbody flows into (the outlet of that catchment)
4. Get everything upstream of that nexus
</details>

**Full Changelog**: https://github.com/CIROH-UA/NGIAB_data_preprocess/compare/v1.4.4...v2.0.0-beta

1.4.4

The previous release removed the extra downstream catchment selection, but removed all catchments but the first to flow into a nexus. This corrects the delineation to fetch ALL the water bodies that flow into a nexus, not just the first.

**Full Changelog**: https://github.com/CIROH-UA/NGIAB_data_preprocess/compare/v1.4.3...v1.4.4

Page 5 of 8

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.