to_zarr(arr, url, component=None, storage_options=None, overwrite=False, compute=True, return_stored=False, **kwargs)

See https://zarr.readthedocs.io for details about the format.

Parameters

arr: dask.array :

Data to store

url: Zarr Array or str or MutableMapping :

Location of the data. A URL can include a protocol specifier like s3:// for remote data. Can also be any MutableMapping instance, which should be serializable if used in multiple processes.

component: str or None :

If the location is a zarr group rather than an array, this is the subcomponent that should be created/over-written.

storage_options: dict :

Any additional parameters for the storage backend (ignored for local paths)

overwrite: bool :

If given array already exists, overwrite=False will cause an error, where overwrite=True will replace the existing data.

compute: bool :

See ~dask.array.store for more details.

return_stored: bool :

See ~dask.array.store for more details.

**kwargs: :

Passed to the zarr.creation.create function, e.g., compression options.

Raises

ValueError

If arr has unknown chunk sizes, which is not supported by Zarr.

Save array to the zarr storage format

See Also

dask.array.Array.compute_chunk_sizes

dask.array.store

Examples

See :

Local connectivity graph

Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.

Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)

SVG is more flexible but power hungry; and does not scale well to 50 + nodes.

All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them

---

File: /dask/array/core.py#3326
type: <class 'function'>
Commit: