What determines if a pixel is 'valid' for /cog/statistics

[mmnoo]

Does the /cog/statistics endpoint only consider pixel values that are completely within an area of interest?

If yes, it might be nice to be able send in a parameter to instruct the calculations to account for pixel values that intersect the edge of the area of interest.

[vincentsarago]

@mmnoo depends on your titiler version but starting with version 0.15.0 the /cog/statistics [POST] endpoint will return statistics weighted with the spatial coverage of the intersecting shape.

only consider pixel values that are completely within an area of interest?

By default rio-tiler will includes all pixels that touches the shape, but as I said in titiler we've added spatial weight.
https://github.com/cogeotiff/rio-tiler/blob/775ecfd513b452765154c20f9693db764e6cf69f/rio_tiler/io/rasterio.py#L573-L581

We could maybe make this configurable but I'm not sure I have time right now

ref:

• improve cutline handling cogeotiff/rio-tiler#598 (review)
• improve cutline handling cogeotiff/rio-tiler#598 (comment)
• improve cutline handling cogeotiff/rio-tiler#598 (review)
• improve cutline handling cogeotiff/rio-tiler#598 (review)