No, “MODE” resampling is not available and “NEAREST” is the default interpolation unless you specify otherwise.
The rest of the answer is going to be rather technical, but I’ll try to give you some ideas what to do…
When you request an image from SH service, for your AOI and time interval, you request it at some resolution. SH then finds the most appropriate overview/zoom level from jp2 (e.g. in case of Sentinels) or cog (e.g. in case of BYOC dataset, or LandSat collection, …) for your request, and fetches it. To get to your requested resolution, SH interpolates (either up or down-scales) the data.
processing parameters for
downsampling you are controlling what kind of algorithm will be used in this last step of SH interpolation.
That being said, there are a few more things to be aware of:
- the type of data (you mention yourself categorical data, where proper interpolation is very important)
- the interpolation algorithm that was used to create overview (e.g. in cogs - e.g. when preparing your COGs, you can already create overviews with “MODE” resampling)
- the resolution being requested
So in principle, if you
- prepare your cog overviews with MODE resampling
- request your data at appropriate resolutions (that equal to original/overview resolutions) and in the same coordinate reference system (i.e. remove the need to do spatial interpolation)
you will be ok.
The default interpolation is always “NEAREST”. That being said, with categorical data (like Scene classification layers (SCL) for Sentinel2-L2A), the SH requests data from the highest resolution much more (also when it could already be requesting lower resolution data from jp2), just so that the data is as close to original as possible. I’ll argue that since SCL is created at 10m resolution, resampling it to lower resolution is generally “wrong”, and only makes sense in particular use cases.