Open siddharth0248 opened 1 day ago
@j08lue
Sample data:
So, this is a simple threshold operation - all values below threshold
are set to nodata
.
The nodata
value is also replaced/set (to a hard-coded value of -9999
) in the process, though, but it looks like it had that value, at least in this file.
As we discussed, there is still no dedicated API functionality for conditional masking like this, but I expect nonetheless that it can be done with the current API, without modifying the data.
We should explore the use of an expression
passed to TiTiler. These are just numexpr
strings. Not sure they support where
, though. Here is a URL to experiment with: https://earth.gov/ghgcenter/api/raster/cog/preview?url=s3://ghgc-data-store/tm54dvar-ch4flux-monthgrid-v1/methane_emis_total_201601.tif&colormap_name=purd&rescale=0.48%2C24
Alternatively, we could register a custom algorithm
in TiTiler that does the masking - i.e. if we created a new algorithm called mask_below
, or so, the API call could look like ?algorithm=mask_below&algorithm_params=10
@siddharth0248, can you please confirm
threshold
for the TM5 data?tm54dvar-ch4flux-monthgrid-v1
collection unmasked?Ok, where
expressions actually work. Passing where(b1<{threshold}, -9999, b1)
, e.g. where(b1<10, -9999, b1)
does the trick:
We should make sure we instruct users who e.g. load the data into Python or QGIS from the same source also apply this masking. Otherwise, they will get different values e.g. when calculating zonal statistics.
That is the disadvantage of applying the masking on the fly and not fixing the files - slightly worse interoperability.
Some data providers request clipping data below a specific threshold value so that the colormap starts at this threshold and extends to an upper limit. For example, in TM5 Var, we clipped the values below 0.48 and then set the min-max range in the metadata to 0.48 and 12. If we hadn’t clipped the data, we would have seen many more pixels, and we also want to avoid designating them as "no-data." Currently, my approach involves masking out these values during the data transformation using the provided script. Could this functionality be incorporated into rio-tiler to enhance sustainability?