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

Explore other Mosaic Backends (DB) #142

Closed
vincentsarago opened this issue Dec 7, 2020 · 3 comments
Closed

Explore other Mosaic Backends (DB) #142

vincentsarago opened this issue Dec 7, 2020 · 3 comments

Comments

@vincentsarago
Copy link
Member

DynamoDB backend is really interesting because it enables large-scale mosaic and with the latest changes we can even store a lot of mosaics in a single table.

As Mosaic become more popular (at least on my side 😄) I'll need to explore other DB backends for other cloud providers (e,g Azure Cosmos)

@vincentsarago
Copy link
Member Author

I'm also thinking about read only backends.

By read only I'm mean, we could connect cogeo-mosaic backends to spatial database (or spatial index). Those won't have to have all MosaicJSON implementation but we could just use get_assets to do the spatial query.

with RTreeBackend("spatial_index.r") as mosaic:
    mosaic.assets_for_tile(1,2,3)
    mosaic.assets_for_point(lng, lat)

@kylebarron
Copy link
Member

Permitting read-only backends could allow you to make a read-only adapter to query a postgres-backed STAC API...

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

2 participants