Skip to content

0.8.4

Choose a tag to compare

@Praddy-GByte Praddy-GByte released this 04 Oct 13:53
· 30 commits to main since this release

A basin delineated on the DEM carries no HydroBASINS id

backend="auto" refines anything below 2,000 km2 on the elevation model, which 0.8.3 made the default. Two things downstream still assumed the basin in hand had come from the HydroBASINS graph: subbasins() traverses the level-12 units inside a basin, and attributes() looks the basin up in BasinATLAS, which is keyed by HydroBASINS id. A DEM-derived polygon carries no such id, so both raised an error that named the backend rather than the request, and a small basin — the case the threshold change was meant to serve — could not reach either.

Both now ask for the HydroBASINS delineation when the basin they were handed does not have one, and record in the log why the backend changed. The ArcGIS Sub-Catchments tool does the same.

Every request now says which version made it

cache._USER_AGENT was the literal basinkit/0.1.0 and was never derived from anything, so every provider — ISRIC, Copernicus, HydroSHEDS, the STAC endpoints — had been seeing 0.1.0 for eight releases. soil.soil_profile carried a second copy of the same literal. Both now build the header from __version__ at call time. Providers rate-limit by User-Agent, so a stale one is not only a cosmetic lie.

One requester-pays scene no longer fails a whole Sentinel-2 mosaic

A few items in Earth Search's sentinel-2-l2a still point at s3://sentinel-s2-l2a, the requester-pays bucket of JP2s this package avoids for Landsat for the same reason. Over the Koshi at Chatara, one scene in six was such an item, and it failed the entire composite with an AWS credentials error naming neither the scene nor the bucket. stac_stack now leaves those out and reports how many, raising only if nothing public remains.

A step whose input never arrived says so

A step that consumes an earlier analysis's output raised a bare KeyError, which the sweep recorded against the consumer rather than the producer. It now names the analysis that did not complete.

Landscape form no longer fails on a basin with knickpoints

It asked the output sink for its field list; QgsFeatureSink has no fields(), so the call only survived where there was nothing to write. The fields now travel back from the algorithm that built them.

The report cover states the version that produced it

The ArcGIS sweep's PDF had its version typed into the cover, so a 0.8.3 run produced a report whose first page read 0.7.0. It now reads the run manifest, as the collage beside it already did.