Release v2.1.0 · GeoTIFF/geoblaze

v2.1.0 (2023-07-23)

Updated convertCrsBboxToImageBbox to properly exclude pixels that barely touch a polygon (i.e. whose pixel centroid doesn't intersect the aoi geometry). This will mean that stats results for rectangular aois could change. You might also see an error thrown saying no valid pixels, whereas before some intersecting pixels were mistakenly included in the calculation. Changes are only expected for rectangular geometries whether they are defined as bounding boxes or rectangular polygons (geoblaze is smart enough to identify a bbox masquerading as a polygon). Non-rectangular geometries should not be affected by any of these changes.

Refactored convertCrsBboxToImageBbox in utils.module.js, so that only pixels whose centroid is within the provided rectangle are used for stats calculations. This is making sure rectangles and bounding boxes are treated the same as other polygons.

Fixed bug in our Github CI workflow whereby gdal_translate wasn't working, because I had forgotten to add instructions to install it

added roundDown function to utils.module.js (copying it from dufour-peyton-intersection)
added more testing
committed some new test data files

Merge pull request #214 from GeoTIFF/rect-2023-07-22 44a3987
updated test value 542b7fd
updated bash script to exit on any error 4444890
added gdal to github actions d6f4de4
expected EXPECTED_BBOX_STATS 3c15b36
updated median test value 028bd52
updated median test value a090cec
updated test value 6f9c7be
added antimeridian test file 26e1a8e
debugging ci aa9a26e
debugging fetching of geojson 87c0739
replace cross-fetch/node-fetch with built-in fetch for intersect-polygon.test.js 83a2da1
updated expected test data for a histogram test a201e37
removed extra console.dir 33e5622
fixed issues whereby calculating stats in a rectangle would pull all pixels that touch the rectangle and not just those whose centroid is inside e6599d3
Create CHANGELOG.md afa32b9