-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Interface with rio-tiler
#157
Comments
It sounds interesting. How do you envisage to work with different bands? Get a single band only? Or provide a method of generating RGB (where applicable, i.e. Landsat)? Supporting a single band does not seem to be overly complicated, but it can get complex quite quickly with multiple bands to deal with. |
Yes, that's a good point. One solution could be start only by taking either "true-color" files or 1-band only. One of the use cases I was thinking might be interesting is if population datasets (e.g. WorldPop, GHSL, etc.) begin adopting the COG standard, it might be useful to be able to use them directly as a XYZ-type of basemap? More generally, do people see this could be of value in some use cases? |
Having worked for a few months on the In your first comment you mention the example used in the MosaicJSON is an extension to combine lots of source files in a seamless map, but then you need to pregenerate that json file that describes where to join each source file. I haven't used P.S. I also wrote an intro COG blog post about this |
It'd be really cool if we could build a bridge to
rio-tiler
. This would allow to use data on COGs directly as contextual basemaps.If I read it correctly, they support direct tiling from a file on the web:
So it'd be up to
contextily
to wire this in with our machinery to pull tiles from an extent:I don't think this would be too onerous. Would it be worth the effort/interest in having this "exist"? Looping @jorisvandenbossche, @martinfleis and @vincentsarago on this as their view will surely be better informed than mine. Do you think this is worth the time implementing?
The text was updated successfully, but these errors were encountered: