Skip to content
Merged
7 changes: 4 additions & 3 deletions docs/working-with-zarr-ndarray-sedonadb.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -273,7 +273,7 @@
"id": "d8f29e2b",
"metadata": {},
"source": [
"Note that `planes[0]` currently forces a copy of the raster out of the Arrow buffer (a pyarrow limitation), so this path is **not yet zero-copy**. Rows correspond to chunks rather than a guaranteed order, so apply your own ordering (or carry a chunk identifier) if you need to know which tile and year a given plane covers."
"Rows correspond to chunks rather than a guaranteed order, so apply your own ordering (or carry a chunk identifier) if you need to know which tile and year a given plane covers."
]
},
{
Expand Down Expand Up @@ -317,12 +317,13 @@
],
"metadata": {
"kernelspec": {
"display_name": "Python 3 (ipykernel)",
"display_name": ".venv",
"language": "python",
"name": "python3"
},
"language_info": {
"name": "python"
"name": "python",
"version": "3.13.8"
}
},
"nbformat": 4,
Expand Down
2 changes: 1 addition & 1 deletion docs/working-with-zarr-ndarray-sedonadb.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ print(band.shape, band.dtype)
(128, 128) float32


Note that `planes[0]` currently forces a copy of the raster out of the Arrow buffer (a pyarrow limitation), so this path is **not yet zero-copy**. Rows correspond to chunks rather than a guaranteed order, so apply your own ordering (or carry a chunk identifier) if you need to know which tile and year a given plane covers.
Rows correspond to chunks rather than a guaranteed order, so apply your own ordering (or carry a chunk identifier) if you need to know which tile and year a given plane covers.

## Reading from cloud storage

Expand Down
Loading