Changelog

Changelog#

All notable changes to gdptools are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.4.1 (unreleased)#

First official USGS software information product release. The code changes below are small; most of the work in this release is release engineering, documentation accuracy and test-suite guards.

  • Changed: gdptools.helpers.get_stac_collection now bounds its HTTP reads and accepts a keyword-only timeout. Previously pystac’s default reader set no timeout at all, so an unreachable or stalled NHGF STAC catalog blocked the caller indefinitely and raised nothing. A slow catalog now raises STACCatalogError instead of hanging, which means callers that already handle that exception – including NHGFStacData, NHGFStacZarrData and NHGFStacTiffData – recover where they previously could not. Callers relying on the old unbounded behaviour should pass a larger timeout (#113).

  • Changed (BREAKING): InterpGen’s calc_crs is now required. It previously defaulted to EPSG:6931, an equal-area projection centered on the North Pole, while the parameter governs distance: pt_spacing is in the linear units of that CRS and is measured in this CRS. Measured at 40N, 100W, a true 1000 m separation is 1103 m in EPSG:6931, so pt_spacing=50 sampled every 45 ground meters rather than 50. The default was silently changing results, so it is removed rather than corrected – every other CRS argument in the package is already required, for the same reason. Pass a distance-faithful projected CRS for your area; EPSG:5070 holds within about 1% between roughly 25.7N and 48.4N, loosening to about 1.4% at both edges of its declared area of use. The documentation gains a “Choosing calc_crs” section explaining why conformal and equal-area projections distort distance differently, with measured figures and a snippet for checking your own study area, and every InterpGen example in the docs and docstrings now passes calc_crs. Your results will change: on the regression suite’s test line, pt_spacing=100 yields 465 sample points under EPSG:5070 where the old EPSG:6931 default gave 444, which moves every derived statistic. The new numbers are the correct ones – the old spacing was not 100 m on the ground (#123, #125).

  • Fixed: reprojection no longer rejects valid local coordinate systems. Every reprojection was validated by transforming the fixed point lon=0, lat=0, which has nothing to do with the caller’s data. For a CRS whose domain excludes it – every UTM zone, most State Plane and national grids – PROJ returns infinity there, so gdptools refused the projection and blamed missing PROJ grid-shift files, advising users to configure PROJ_NETWORK and PROJ_DATA for a problem they did not have. The transformation itself worked: the example line data reprojects into UTM zone 15N with entirely finite coordinates. The probe could not detect the condition it named either, since datum-shift grids are regional and a point in the Gulf of Guinea exercises none of the ones a transformation over Iowa needs. It is replaced by two checks that are each true: PROJ is asked whether a usable transformation exists, and the reprojected geometry is checked for non-finite coordinates. A missing datum-shift grid now warns about reduced accuracy instead of failing, since results are still produced. Affects calc_crs on InterpGen and weight_gen_crs on WeightGen, WeightGenP2P and WeightedZonalGen (#124).

  • Fixed (tests): the test suite no longer depends on the machine’s PROJ network setting. PROJ selects a different transformation operation when network access is enabled – EPSG:4326 to EPSG:5070 offers 1 candidate operation with it off and 48 with it on – which changed coordinates enough that 13 tests failed on a clean checkout for anyone who had PROJ_NETWORK enabled, with nothing to indicate the cause was environmental. tests/conftest.py now pins it off for the session and CONTRIBUTING.md records the assumption (#129).

  • Fixed: WeightedZonalGen’s zonal_engine annotation no longer advertises an engine it rejects. It was annotated ZONAL_ENGINES, which includes "exactextract", while raising TypeError on that value because exactextract has no weighted implementation yet (#94) – so a type checker told users a call was valid and the call raised. The class now declares WEIGHTED_ZONAL_ENGINES, Literal["serial", "parallel"], and its fallthrough error lists that narrower set rather than one containing an option that fails. Both classes’ engine errors now name zonal_engine rather than the non-existent agg_engine parameter (#130).

  • Fixed (tests): the merge-gate test selection no longer makes live network calls. Five tests read the climateR catalog from GitHub or gridMET over THREDDS OPeNDAP, costing about 330 s of a 406 s run and making the CI tests job swing between 307 s and 762 s with no change in the code. They are now marked slow. The ClimRCatData catalog-parsing they uniquely covered is kept in the gate by tests/test_climr_catalog_offline.py, built on an 88 KB committed catalog subset, with a slow-marked check that the subset has not drifted from the live catalog. Verified with the network blocked: 412 passed in 77 s (#131).

  • Fixed (CI): the tests-full job’s result is no longer cosmetic. It was when: manual with allow_failure: true, so even when someone pressed it, a failure left the pipeline green – which is exactly what happened on !240, where it caught real breakage introduced by !239 and reported success anyway. The release runbook tells a human to consult this job, so its result has to bind. It now runs automatically on develop and fails the pipeline there, while staying a non-blocking manual button on merge requests so that a third-party outage cannot redden unrelated work. A retry absorbs momentary outages (#128).

  • Fixed (tests): tests/test_notebooks.py can now fail. It could not before, for two independent reasons: pytest.importorskip on pynhd and hvplot, which live in the docs group that no pytest session installed, so the module skipped itself everywhere; and its error scan sat inside an except block that allow_errors=True guarantees is never reached. Nothing had executed a notebook in CI. Fixing it revealed a third defect in the test rather than the notebooks: it executed them from the repository root, so every relative path failed. Notebooks now run in their own directory, as Jupyter and Read the Docs run them. They are marked notebooks rather than slow and run on request – nox -s test-notebooks, or the manual tests-notebooks job – because thirteen notebooks with a 600 s timeout each, driving live services, should not gate trunk (#126).

  • Fixed: a catalog entry can now point at a local file. The catalog-driven code paths appended #fillmismatch – a THREDDS/OPeNDAP query parameter – to every source, so a local path became an unopenable filename; _get_xr_dataset already drew the distinction, the catalog paths did not. This is what allowed the ClimRCatData pipeline to be tested against recorded data rather than a live service: tests/test_climr_catalog_offline.py now runs ClimRCatData through WeightGen and AggGen over 257 KB of committed gridMET, offline, in the merge gate, with pinned output values. Mutation-tested – making masked_mean ignore its area weights fails that test and nothing else, including the checks that only compare the two engines to each other (#126).

  • Changed: pynhd is no longer pinned in pyproject.toml, docs/requirements.txt or environment-docs.yml. The pin resolved to exactly the version the dependency graph already produces – pygeohydro caps pynhd<0.20 – so it did no work, while looking like a decision. Pinning it forward is worse than useless: pynhd==0.20.0 does not fail to resolve, it quietly walks pygeohydro back to 0.14.0 (March 2023) to satisfy that cap, and the notebooks depend on pygeohydro. Unpinned, the HyRiver stack moves together when pygeohydro publishes a release accepting pynhd 0.20. Resolved versions are unchanged by this (#132).

  • Fixed: environment-examples.yml pinned gdptools==0.3.2. That pin had not moved since 0.3.2, so anyone building the examples environment from the documentation got a package predating the removal of the dask engine (0.4.0) and the required calc_crs (0.4.1) — the notebooks in the repository and the environment the docs tell you to create described different packages. Pinned to 0.4.0, and bumping it is now a step in the release runbook, since bump2version does not touch that file (#132).

  • Removed: nine unreachable private functions in gdptools.weights.calc_weight_engines, left over from the dask engine deleted in 0.4.0. All were unreferenced; no public API is affected (#111).

  • Fixed: docstring examples throughout the published API reference. Examples that can run offline now do; those that need a catalog or network are marked as non-executing code blocks rather than presented as runnable (#110).

  • Fixed: several docstrings that documented output that the code does not produce – ZonalGen and WeightedZonalGen column lists, and InterpGen.calc_interp, which always returns a (statistics, points) tuple rather than sometimes returning a DataFrame alone (#122).

  • Added: nox -s check-pypi-version, which fails when PyPI already holds a release newer than the version on the branch – the drift an official release leaves behind on trunk (#108).

  • Added: lint, deptry and xdoctest CI jobs; ruff and deptry now block a merge (#109).

0.4.0 (2026-09-02)#

  • Added: Documentation and tooling for releasing gdptools as an official USGS software information product — a release runbook (docs/usgs-software-release.md), a GitLab issue template carrying the release checklist, and a corrected code.json. Release tags are now bare (0.4.0) rather than v-prefixed. This work prepares for an official USGS software information product release; it does not perform one — no official release has been made, and no DOI has been issued (#106).

  • Fixed: docs/_config.yml no longer drifts from the package version. .bumpversion.cfg tracked only src/gdptools/__init__.py, so the documented version had been stuck at 0.2.21; both files are now bumped together and a test fails if they diverge (#106).

  • Fixed: InterpGen(..., method="parallel") returned interpolated points in the source grid CRS instead of the target CRS. ParallelInterp projected its output with source_crs where SerialInterp uses get_target_crs(); both are documented as projecting “back to original crs”, meaning the CRS of the caller’s target geometries. Whenever the source grid and target geometries used different coordinate systems, the parallel engine silently returned points in the wrong one — switching engines for performance changed the output geometry with no error. For ClimRCatData sources, which never define source_crs, it raised AttributeError instead. The two engines now agree, and the divergence is covered by a regression test that exercises both with differing source and target CRSs (#104).

  • Removed (BREAKING): The dask processing engine is removed across WeightGen, WeightGenP2P, AggGen, InterpGen, ZonalGen, and WeightedZonalGen. Selecting it now raises TypeError. The DaskAgg, DaskInterp, DaskWghtGenEngine, and ZonalEngineDask classes are deleted, and "dask" is no longer a valid value in WEIGHT_GEN_METHODS, AGGENGINES, LINEITERPENGINES, or ZONAL_ENGINES. Use 'parallel' for large datasets or 'serial' for small datasets. For zonal statistics, prefer 'exactextract'. dask and dask-geopandas remain required dependencies: the surviving 'parallel' weight-generation engine still uses dask-geopandas internally for Hilbert-curve spatial partitioning, so installing gdptools still pulls in both packages.

0.3.15 (2026-06-05)#

  • Fixed: AggGen.calculate_agg now returns numpy.nan (not the undeclared NC_FILL_DOUBLE sentinel 9.969209968386869e+36) for float target features with no source-grid overlap. The sentinel was an in-band missing-value marker with no matching _FillValue/missing_value attribute, so CF-aware tools could not detect it and any reduction that did not pre-screen the array (max(skipna=True), np.fmax, plotting, statistics) silently picked it up as real data. NaN is self-identifying, propagates correctly through skipna=True, and is encoded back to _FillValue by the NetCDF writer. Integer outputs, which cannot represent NaN, retain the netCDF integer fill value (declared as _FillValue by build_cf_dataset) (#100).

0.3.14 (2026-06-04)#

  • Fixed: Weighted zonal engines now assign a value to target geometries smaller than a single raster cell. Such sub-pixel zones previously raised an uncaught NoDataInBounds from rioxarray’s clip_box — aborting the calculation — instead of being scored. They now retain the pixel(s) they fall within and receive that value through area-weighted intersection. Reported and originally patched by Angelica De Ros (Diagram Spa) (#101).

  • Security: Upgraded 8 locked dependencies to resolve 16 CVEs disclosed in 2026: aiohttp, idna, mistune, nbconvert, pip, pyarrow, starlette, and urllib3. Raised the pyarrow, urllib3 (runtime), and nbconvert (dev) version floors in pyproject.toml to match.

  • Internal: Removed the deprecated dask weighted-zonal regression test and its baseline ahead of the planned removal of the dask zonal engine.

0.3.13 (2026-04-17)#

  • Fixed: Stricter and more consistent source_time_period validation across all UserData subclasses. Reversed ranges (start > end) and periods that select no time steps — out of range, between labels for monthly or 8-day data, or inside a sub-step window — now raise ValueError with a diagnostic naming the dataset’s actual time range and the nearest available timestamps. Previously these produced silent empty slices that surfaced as confusing IndexErrors during aggregation (#98).

  • Fixed: NHGFStacZarrData, NHGFStacTiffData, and _NHGFStacBase._select_item now route source_time_period through the shared _process_period validator. Malformed date strings are rejected at construction time instead of surfacing as opaque xarray errors later in .sel().

  • Fixed: The “source data time coordinate is formatted as X, you specified Y” format-mismatch hint now applies to all three prep paths (prep_wght_data, prep_agg_data, prep_interp_data), not only prep_wght_data.

  • Fixed: build_cf_dataset now propagates the source time coord’s attrs and encoding onto the returned Dataset. Previously CF metadata (standard_name, axis, bounds) and netCDF encoding (units, calendar) were silently dropped, so output time axes were not CF-recognizable and non-standard calendars (noleap, 360_day) could be corrupted on NetCDF write (#99).

  • Changed: Aggregation engines’ empty-time-slice log message no longer claims the source_time_period argument was specified incorrectly. The new message — “Empty time slice after subsetting” — describes the real cause.

  • Internal: New helpers _assert_period_intersects_time_axis and _sel_with_time_diagnostic in gdptools.utils. _process_period now rejects reversed ranges.

  • Docs: UserData subclass docstrings now document xarray’s inclusive-both-ends slice semantics and the monthly / 8-day / sub-daily gotchas for source_time_period.

0.3.12 (2026-04-17)#

  • Security: Upgraded 4 locked dependencies to resolve 13 CVEs: aiohttp (10 CVEs), pygments (CVE-2026-4539), pytest (CVE-2025-71176), and requests (CVE-2026-25645).

  • Fixed: UserCatData and NHGFStacZarrData no longer mutate the caller’s source dataset when rotating 0–360° longitude into -180…180°. Constructing multiple instances from a single shared xr.Dataset now works; previously the second instance failed with KeyError on a non-monotonic index (#97).

  • Fixed: AggGen.calculate_agg() now returns a CF-1.8-compliant xr.Dataset matching the structure written by NetCDFWriter: adds the crs scalar variable referenced by grid_mapping, along with lat/lon centroid coordinates in EPSG:4326 (#97).

  • Internal: Extracted a shared build_cf_dataset() helper (new module gdptools.agg._cf_dataset) so AggGen._gen_xarray_return and NetCDFWriter.create_out_file cannot drift.

  • Internal: Extracted a _rotate_longitude_if_needed helper in gdptools.data.user_data, removing the duplicated rotation block between UserCatData.__init__ and NHGFStacZarrData.__init__.

  • Internal: NetCDFWriter no longer leaks a process-wide UserWarning filter via warnings.filterwarnings(...). The centroid-computation suppression is now scoped to a warnings.catch_warnings() block inside build_cf_dataset, so other code running after a NetCDF save sees unchanged warning behavior.

  • Internal: Removed stale hvplot entry from dev group in uv.lock; hvplot is a docs-only dependency and was never listed in pyproject.toml dev group.

0.3.11 (2026-02-27)#

  • Deprecated: serial, parallel, and dask zonal engines now emit FutureWarning. Use zonal_engine="exactextract" instead, which provides better performance and handles large datasets with bounded memory.

  • Changed: Moved dask.distributed from top-level import to lazy import inside ZonalEngineDask.weighted_zonal_stats(), so the distributed package is no longer required at import time.

  • Removed: safety dev dependency (redundant with pip-audit; its transitive nltk dependency had CVE-2025-14009).

  • Removed: Unused .safety-policy.yml configuration file.

  • Documentation: Updated zonal statistics and logging demo notebooks with deprecation notices and revised engine comparison table.

0.3.10 (2026-02-21)#

  • Fixed: Read coordinate names (x, y, time) from STAC cube:dimensions metadata instead of hardcoding, enabling support for collections with non-standard dimension names.

  • Fixed: Longitude rotation in utils._get_cat_data_from_url used hardcoded "lon" instead of the actual coordinate name variable.

0.3.9 (2026-02-21)#

  • Added: Structured logging throughout all source modules, replacing ~86 print() calls with logger.<level>().

  • Added: Logging configuration guide in Getting Started docs and logging_demo.ipynb example notebook.

  • Fixed: Format spec {:0.04} corrected to {:0.4f} in zonal_engines.

  • Fixed: Removed leftover debug print() calls.

  • Fixed: Typo “anitmeridian” → “antimeridian” in utils.

  • CI: Added cross-platform conda-forge dependency validation job.

  • CI: Updated lockfile for yanked virtualenv 20.37.0 → 20.38.0.

  • CI: Fixed pip-audit to use --skip-editable instead of --strict (editable local installs aren’t on PyPI).

  • Security: Upgraded bokeh (CVE-2026-21883), pillow (CVE-2026-25990), and nbconvert (CVE-2025-53000).

0.3.8 (2026-02-18)#

  • Fixed: Pydantic ValidationError in CatClimRItem when asset or scenario fields contain float('nan') from the ClimateR catalog parquet.

  • Changed: Switched test fixtures and expected values from TerraClimate to gridMET (tmmx/tmmn/pr) after upstream TerraClimate v1.1 reprocessing broke expected values.

  • Changed: Replaced TerraClimate example notebooks with gridMET equivalents: gridmet_drb_polygon.ipynb (was terraclime_et.ipynb) and gridmet_grid_to_line.ipynb (was Terraclimate-Grid-to-Line.ipynb).

  • Documentation: Expanded NHGFStacData documentation to describe the factory + subclass hierarchy (NHGFStacZarrData, NHGFStacTiffData) with autoclass directives and usage examples for both Zarr and GeoTIFF collections.

  • Documentation: Added NLCD notebook to table of contents and examples table in Getting Started guide.

  • Documentation: Added all user data classes to the API Reference autosummary.

0.3.7 (2026-02-16)#

  • Added: GeoTIFF-backed STAC collection support via new NHGFStacTiffData class. NHGFStacData now auto-detects collection format (Zarr or GeoTIFF) and returns the appropriate handler transparently.

  • Added: NHGFStacData_NLCD.ipynb example notebook demonstrating categorical zonal statistics of NLCD land cover classes for HUC12 basins.

  • Added: _stac_href_to_url() helper for robust S3/HTTPS/bare-path URL construction from STAC asset hrefs.

  • Added: Fast-path direct URL lookup in get_stac_collection() to avoid slow recursive STAC catalog traversal and API rate limiting.

  • Added: Per-link error handling in get_stac_collection() to skip broken STAC child links instead of aborting the entire traversal.

  • Performance: Remote GeoTIFFs are opened with rasterio windowed reading, fetching only the tiles covering the target polygons via HTTP range requests instead of loading the full raster into memory.

  • Fixed: CI shell redirection bug where python>=${PYTHON_REQ} was parsed as file redirection in .gitlab-ci.yml.

  • Fixed: Timezone handling in STAC item selection now normalizes both sides to UTC instead of stripping timezone info.

  • Fixed: Updated test_interp_gen_with_climater expected values after TerraClimate v1.1 upstream reprocessing (ERA5, 2026-02-06).

  • Security: Upgraded 8 locked dependencies to resolve 15 CVEs (aiohttp, cryptography, distributed, filelock, pip, urllib3, virtualenv, wheel).

0.3.6 (2026-01-02)#

  • Added: GitLab CI job conda-forge-validate to test dependency resolution against conda-forge with strict channel priority, catching compatibility issues before feedstock submission.

  • Changed: Bumped minimum Python version from 3.10 to 3.11 due to exactextract>=0.3.0 dependency chain requiring pyproj>=3.7.2, which only has conda builds for Python 3.11+.

  • Changed: Updated pyproj minimum version from 3.3.0 to 3.7.2 to match exactextract requirements.

  • Changed: Removed upper bounds on dependencies for better conda-forge compatibility:

    • xarray>=2024.7.0 (removed <2025.0.0)

    • rasterio>=1.2.9 (removed <1.5.0)

    • rioxarray>=0.15 (removed <0.21)

    • pystac>=1.10 (removed <2.0)

    • statsmodels>=0.14 (removed <1.0)

    • fastparquet>=2024.2 (removed <=2024.5)

    • pyarrow>=10.0.0 (removed <18.0.0)

  • Changed: Migrated development setup from Poetry to UV exclusively - removed conda dependency from development workflow.

  • Fixed: Conda-forge packaging failures caused by strict channel priority and upper bound constraints.

  • Documentation: Updated README.md and environment-examples.yml to reflect Python 3.11+ requirement.

0.3.5 (2026-01-01)#

  • Added: Spatial partitioning for parallel weight generation engine using Hilbert curves to improve cache locality and reduce memory fragmentation.

  • Added: Test coverage for calculate_weights(intersections=True) in polygon-to-polygon weight generation.

  • Added: @pytest.mark.slow markers for network-dependent tests (STAC catalog, notebooks).

  • Added: tests-full nox session to run all tests including slow ones; default tests session now skips slow tests (~2.5 min vs ~7 min).

  • Performance: Optimized area-weighted statistics methods in stats_methods.py:

    • MAWeightedMean and MAWeightedStd: 2-3x speedup by vectorizing masked array operations.

    • MASum, MAMin, MAMax: 2.5-11x speedup by replacing np.ma.masked_array with np.nansum, np.nanmin, np.nanmax.

    • SerialAgg.calc_agg: Reduced overhead by extracting single time slice before iterating polygon-by-polygon.

  • Fixed: source_poly_idx string indexing bug in WeightGenP2P where source_poly_idx[0] on a string returned first character instead of column name.

  • Removed: test_coverage_summary.py (zero functional value).

  • Removed: Redundant date format tests in test_serial.py (already covered in test_weight_agg_gen.py).

  • Changed: Renamed test functions in test_dask.py from test_parallel_* to test_dask_* for clarity.

0.3.4 (2025-12-31)#

  • Added: Vectorized _get_cells_poly_fast function in utils_optimized.py providing 100-280x speedup for regular projected grids with 1D coordinates.

  • Added: Memory-safe chunked mode (mode="chunked") for processing very large grids without exhausting memory.

  • Added: estimate_memory_gb() helper to predict memory requirements before processing.

  • Added: Benchmark script scripts/test_cells_poly_optimization.py for performance testing.

  • Fixed: Renovate configuration error by removing unsupported uv manager from matchManagers.

0.3.3 (2025-12-30)#

  • Added: exactextract zonal statistics engine for high-performance raster-to-polygon statistics using the exactextract library.

  • Added: Support for categorical data in exactextract engine with fraction-based output matching serial/parallel/dask engines.

  • Added: Exactextract examples in the zonal statistics notebook (docs/Examples/Rasters/zonal_stats.ipynb).

  • Added: Tests verifying exactextract output format consistency with existing engines.

  • Changed: Zonal statistics engines now output consistent column names across all engines:

    • Continuous: count, mean, std, min, 25%, 50%, 75%, max, sum

    • Categorical: integer category columns + count

0.3.2 (2025-12-30)#

  • Changed: Migrated from conda/poetry to uv for dependency management.

  • Performance: Optimized spatial intersection calculations in calc_weight_engines.py using contained/boundary partitioning with shapely.within() to skip expensive intersection() calls for fully contained polygons.

  • Performance: Optimized pixel weight calculation in zonal_engines.py with same contained/boundary partitioning strategy.

  • Fixed: Consistent n_jobs=-1 default behavior across all engine functions (Parallel and Dask now both default to cpu_count()/2).

  • Fixed: Coverage session failure in CI due to missing Cython source files.

  • Fixed: CVE-2025-53000 in pip-audit (ignored until nbconvert fix is released).

  • Fixed: rioxarray dependency updated to >=0.15,<0.21.

  • CI: Temporarily disabled mypy and lint jobs pending uv migration stabilization.

0.3.1 (2025-12-18)#

  • Added: get_stac_collection() helper function to fetch collections from the NHGF STAC catalog with recursive search.

  • Added: STACCatalogError exception class for STAC catalog access errors.

  • Fixed: urllib3 CVE-2025-66418 and CVE-2025-66471 by pinning urllib3>=2.6.0.

  • Fixed: STAC-dependent tests resilient to rate limiting and catalog unavailability using xfail.

  • Changed: Modernized .gitlab-ci.yml: consolidated to single stage, added dependency-aware caching, removed redundant apt-get upgrade.

  • Changed: Updated nox -s coverage to generate coverage.xml for GitLab CI artifacts.

  • Changed: Removed explicit pyogrio from environment files (transitive dependency via geopandas).

  • Changed: Switched from mamba to conda in CI (libmamba is now the default solver in miniforge3).

  • Documentation: Updated NHGF STAC example notebooks (NHGFStacData_CONUS404, NHGFStacData_Grid_to_Line) to use get_stac_collection() helper instead of direct pystac calls.

0.3.0 (2025-11-26)#

  • Added: gdptools.depreciation_utils.deprecate_kwargs helper so high-level classes retain backwards compatibility while emitting structured warnings for renamed parameters.

  • Changed: Standardized keyword names across the data-prep classes and documented the legacy aliases that now trigger deprecation warnings:

    • ClimRCatData: cat_dict → source_cat_dict, f_feature → target_gdf, id_feature → target_id, period → source_time_period.

    • UserCatData: ds → source_ds, proj_ds → source_crs, x_coord → source_x_coord, y_coord → source_y_coord, t_coord → source_t_coord, var → source_var, f_feature → target_gdf, proj_feature → target_crs, id_feature → target_id, period → source_time_period.

    • NHGFStacData: collection → source_collection, var → source_var, f_feature → target_gdf, id_feature → target_id, period → source_time_period.

    • UserTiffData: ds → source_ds, proj_ds → source_crs, x_coord → source_x_coord, y_coord → source_y_coord, t_coord → source_t_coord, var → source_var, f_feature → target_gdf, proj_feature → target_crs, id_feature → target_id, period → source_time_period.

  • Changed: Updated the nox -s lint session to execute pre-commit run --all-files, ensuring local lint checks match the enforced pre-commit workflow.

  • Documentation: Expanded helper and data-class documentation to call out the canonical keyword names, the new deprecation behavior, and the preferred CRS guidance for weight generation.

0.2.20 (2024-XX-XX)#

  • Changed: Broadly relaxed dependencies

  • Changed: Bumped pydantic dependency to >= 2.0.0

0.2.18#

  • Added: NHGFStacData class to interface with the NHGF Stac Catalog.

  • Added: NHGFStacData example use cases to documentation.

  • Fixed: Bug in SerialAgg by loading subsetted data before aggregating, improving performance. This was the origin state it was inadvertently changed in a previous commit.

0.2.11 (2024-08-21)#

  • Changed: Updated categorical zonal stats to return the fraction of each category in each polygon.

  • Added: Precision parameter to zonal stats such that the number of significant digits in the output can be set.

0.2.10 (2024-07-18)#

  • Added: New class NHGFStacData as an interface to the NHGF Stac Catalog (still in development).

0.2.9 (2024-04-06)#

  • Added: Ability to specify precision of output

0.2.8 (2024-04-03)#

  • Added: sum and masked_sum statistical methods.

0.2.5 (2023-11-1)#

  • Fixed: Bug in WeightGenP2P. Target polygons are now dissolved by the specified target_poly_idx. The generated weights file should have a unique set of source ids for each target id.

0.2.2 (2023-08-08)#

  • Fixed: Bug in output of AggGen. “parallel” and “dask” engines were not writing the feature_ids with the output.

0.0.1 (2022-03-22)#

  • Added: Original starting version.

→ View the complete version history

For supported Python versions and dependency requirements, see the package metadata on PyPI, which is generated from pyproject.toml and therefore cannot drift from what is actually installed.