-
Notifications
You must be signed in to change notification settings - Fork 43
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
create a rasterio driver for large-image? #898
Comments
It isn't hard to add additional tile sources -- there are a few basic functions (getTile, getMetadata) that need to be defined. The init method needs to determine the image size and a few other parameters. The main developers mostly work in environments where GDAL is available (via our self-published linux wheels or via conda), so this hasn't been needed -- but we always encourage additional tile sources and could be convinced this could be added as part of our efforts. |
Let me propose a PR then and you'll let me know if it make sense |
to avoid requesting GDAL. will be reintroduced when girder/large_image#898 is closed
Added in #1115 |
don't get me wrong the question is not "is geospatial version of large_image necessary" but more about the use of GDAL itself.
GDAL is a great library but it has the really bad habit of being the worst possible neighbor in a python environment. I started to use https://localtileserver.banesullivan.com/installation/index.html for my project and since I publish the latest version all the pip-related environments failed because of gdal inconsistency and version crash.
I search in the GDAL repository itself and there is a very long thread of about a potential wheel distribution for GDAL OSGeo/gdal#3060 that seems on stale.
As large_image seems to be developed for python environments being pip-friendly seems like a desirable objective. Do you already considered using a pure rasterio driver ?
The text was updated successfully, but these errors were encountered: