From e33df034677e3d7df0494dad194b7fcde971a644 Mon Sep 17 00:00:00 2001 From: RichardScottOZ Date: Sun, 4 Aug 2024 09:23:07 +0930 Subject: [PATCH 1/2] chunnks Signed-off-by: RichardScottOZ --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bafd6ce..c6b0f23 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ That's it! ## Why does this work? Underneath Xarray, Dask, and Pandas, there are NumPy arrays. These are paged in -chuncks and represented contiguously in memory. It is only a matter of metadata +chunks and represented contiguously in memory. It is only a matter of metadata that breaks them up into ndarrays. `to_dataframe()` just changes this metadata (via a `ravel()`/`reshape()`), back into a column amenable to a DataFrame. From 7a242d7d84f0e57a7838686aca71552842524473 Mon Sep 17 00:00:00 2001 From: RichardScottOZ Date: Sun, 4 Aug 2024 09:25:58 +0930 Subject: [PATCH 2/2] space Signed-off-by: RichardScottOZ --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c6b0f23..cc2d3c5 100644 --- a/README.md +++ b/README.md @@ -100,7 +100,7 @@ Xarray Datasets. This approach is being pursued Deeper still: I was thinking we could make a [virtual](https://fsspec.github.io/kerchunk/) filesystem for parquet that would internally map to Zarr. Raster-backed virtual -parquet would open up integrations to numeroustools like dask, pyarrow, duckdb, +parquet would open up integrations to numerous tools like dask, pyarrow, duckdb, and BigQuery. More thoughts on this in [#4](https://github.com/alxmrs/xarray-sql/issues/4).