Open kissgyula opened 4 months ago
It likely relates to https://github.com/mapbox/rio-rgbify/issues/39
In my fork at https://github.com/acalcutt/rio-rgbify/ I fixed this with https://github.com/acalcutt/rio-rgbify/commit/6db4f8baf4d78e157e02c67b05afae49289f9ef1 , which set the densify_pts to the default gdal value
It looks like in my later compact branch at https://github.com/acalcutt/rio-rgbify/tree/compact I ended up changing this to 2, which was the minimum. my reasoning for this was it was originally 0 and 2 was as close as you can get to that . also, the information at https://rasterio.readthedocs.io/en/stable/api/rasterio.warp.html says higher numbers can affect performance
densify_pts (uint, optional) – Number of points to add to each edge to account for nonlinear edges produced by the transform process. Large numbers will produce worse performance. Default: 21 (gdal default).
This compact branch, btw, adds in tile deduplication, if you have a lot of empty water areas it can help your mbtiles size. I would love a tester of this :-).
This is addressed here : https://github.com/SilvioDallAcqua/terrain-rgb/blob/main/rgbify.md
I got this error when rio running:
ERROR 1: densify_pts must be at least 2 if the output is geograpic.
Is there anybody who running into this error?