Clarify arguments used only when producing "web-optimized" COGs about rio-cogeo HOT 4 CLOSED

👋 Bonjour @alexismanin

Thanks for starting this discussion.

Yes, I'm sorry about this. I think what happened is that when I started working on the WebOptimization part, there was only one option web_optimized and then when we enabled more options, we tried to follow GDAL COG options.

I think we could do:

• improve the documentation
• deprecate web_optimized option and change the logic to see if the tms option was passed (yeah one less option 🥳 )
• the tms option should always be of type morecantile.TileMatrixSet (it makes things way more simpler)
• for the other zoom_level_strategy, zoom_level, aligned_levels and resampling, I think just updating the documentation should be enough

from rio-cogeo.

I think we are good to close this 🙏 @alexismanin

from rio-cogeo.

Just a side-note: resampling does not seem bound to web-optimization, because it is used by rasterio warp (WarpedVRT), and that is done anyway.

If I understand well, no reprojection is configurable except through the tms argument, but the warp may still make sense if user has specified dtype parameter.
Although I am wondering if a warp operator that only change output dtype will perform any interpolation/resample.

In any case, I will give a try to your suggestion.

from rio-cogeo.

@alexismanin, the VRT is used also when

• we want to override the nodata
• convert nodata/alpha to mask

but yeah the resampling option shouldn't have any effect when not using the web-optimization. I think I though at one point of adding the dst-crs option but this will conflict with the tms option so I preferred not to pursue.

Although I am wondering if a warp operator that only change output dtype will perform any interpolation/resample.

I hope not 😅 , I can also see that we didn't add tests for the dtype option

from rio-cogeo.