You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One perspective is that this is the inverse of what this project is trying to do so far, which is to treat rasters as tables to run SQL queries against them.
One fuzzy idea for a use case like this would be to read a table of data associated with a latlng and translate it to a (sparse) raster.
Similar to #4, I wonder if column-oriented data like parquet, which most headless tabular data stores are represented today, would naturally fit well with Xarray-style chunks.
The text was updated successfully, but these errors were encountered:
I had a shower thought today. If Zarr is an OLAP DB, then could we treat tables as rasters?
zarr-developers/zarr-specs#290
One perspective is that this is the inverse of what this project is trying to do so far, which is to treat rasters as tables to run SQL queries against them.
One fuzzy idea for a use case like this would be to read a table of data associated with a latlng and translate it to a (sparse) raster.
Similar to #4, I wonder if column-oriented data like parquet, which most headless tabular data stores are represented today, would naturally fit well with Xarray-style chunks.
The text was updated successfully, but these errors were encountered: