from_zarr(url, component=None, storage_options=None, chunks=None, name=None, inline_array=False, **kwargs)

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

Parameters

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 loaded, something like 'foo/bar' .

storage_options: dict :

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

chunks: tuple of ints or tuples of ints :

Passed to dask.array.from_array , allows setting the chunks on initialisation, if the chunking scheme in the on-disc dataset is not optimal for the calculations to follow.

name : str, optional

An optional keyname for the array. Defaults to hashing the input

kwargs: :

Passed to zarr.core.Array .

inline_array : bool, default False

Whether to inline the zarr Array in the values of the task graph. See dask.array.from_array for an explanation.

Load array from the zarr storage format

See Also

from_array

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#3266
type: <class 'function'>
Commit: