proof of concept for async data fetching from Python -> JS #1082
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
deck.gl
TileLayerwhere eachgetTileDatarequests data from Python as necessary.We should have
from_rasterioandfrom_async_tiff(or maybe some other API that shows thatasync_tiffis preferred?).Then each constructor should create a TMS document representing the input. Then we should send that TMS to the frontend for it to know how to fetch data from Python.
Note that if we just have a generic tms rendering layer, then we don't need a hard distinction between COG and Zarr.