Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rio error #6

Open
kissgyula opened this issue Feb 27, 2024 · 3 comments
Open

Rio error #6

kissgyula opened this issue Feb 27, 2024 · 3 comments

Comments

@kissgyula
Copy link

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?

@acalcutt
Copy link
Owner

It likely relates to mapbox/rio-rgbify#39

In my fork at https://github.com/acalcutt/rio-rgbify/ I fixed this with acalcutt/rio-rgbify@6db4f8b , which set the densify_pts to the default gdal value

@acalcutt
Copy link
Owner

acalcutt commented Feb 27, 2024

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 :-).

@utagawal
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants