chronozarr v0.4.0
Status: Draft
Date: 2026-10-19
Spec version string: 0.3.0 for a store whose CRS has an EPSG code, 0.4.0 for any other store (§3.2)
Supersedes: chronozarr v0.3.0, whose stores stay valid under this document. A v0.2.0 store becomes a v0.3.0 store through explicit conversion.
0. Scope and upstream references
chronozarr defines a profile of Zarr v3 for raster time series with true stored values. The profile covers a multiscale pyramid, band descriptions, validity planes, metadata mirrors and static publishing rules. Every array holds ordinary stored values. Applying the declared band scale and offset gives physical units. Stored values need no chronozarr-specific reconstruction. Each store has one north-up grid in one CRS, with or without an EPSG code. The profile composes the zarr-conventions multiscales, proj and spatial conventions. It is aligned with this GeoZarr convention work. It is not certified against an adopted OGC GeoZarr standard.
MUST, MUST NOT, SHOULD, SHOULD NOT and MAY express requirements as in RFC 2119. The requirements of sections 1 to 8 bind writers and the stores they produce, and chronozarr validate checks them. Section 9 binds readers: a reader decodes every store it can read as declared, whether or not the store conforms. Sections 0.3 and 10 are informative. So are examples explicitly labelled informative and implementation observations. All other sections are normative. Upstream requirements incorporated below apply in addition to chronozarr restrictions. Registration URLs identify the literal v0.1 conventions. Snapshot identities record documentation provenance. Stores do not carry them as attributes.
0.1 Normative upstream authorities
| ID | Authority | Sections used by this profile |
|---|---|---|
| Z | Zarr core 3.1 | Concepts and terminology (Hierarchy), Stored representation, Metadata, Array metadata, Group metadata, Chunk grids, Chunk encoding, Storage and Extensions. The store's zarr_format remains 3. |
| F | Zarr Conventions Specification | Definition, Convention Registration via zarr_conventions, Convention Properties and Composability. |
| M | multiscales v0.1 | Configuration, Layout Object, Transform Object, Hierarchical Layout, Group Discovery Methods and Consolidated Metadata. |
| P | proj v0.1 | Properties and Inheritance Rules. |
| S | spatial v0.1 | Properties, spatial, spatial, Coordinate convention, Coefficient ordering and spatial. |
| B | Zarr bytes codec | Codec configuration and byte-order semantics. |
| I | Zarr indexed-sharding codec | Configuration, Index, Index location, Empty chunks, Encoding and Decoding. |
0.2 Rules inherited by reference
The upstream sections in the table define these mechanisms. Later sections give the profile choices that restrict their use.
| Mechanism | Governing upstream section |
|---|---|
| Hierarchy and array/group node semantics | Z, Concepts and terminology / Hierarchy; Stored representation; Metadata. |
| Edge chunk extent and exclusion of elements outside array shape | Z, Chunk grids; Array metadata / shape. The profile's fill-padding choice is in §2.1. |
| Byte order for one-byte element types | B, Configuration / endian. |
| Consolidated discovery and its recommendation | M, Consolidated Metadata. The reader fallback is in §9.2. |
| Six affine coefficients, coefficient ordering and index-to-coordinate corner interpretation | S, spatial / Coordinate convention / Coefficient ordering. North-up and factor-two restrictions are in §§2.3 and 3.3. |
| Shard index representation, index checksums, index placement, empty entries, absent-shard fill and omission of all-fill shards | I, Index, Index location and Empty chunks. Profile interoperability choices are in §7.2. §2.1 recommends that writers store all-fill shards. |
| Node metadata representation and naming | Z, Stored representation; Array metadata; Group metadata. |
| Standard shard decoding and array bounds | I, Decoding; Z, Array metadata / shape and Chunk grids. Profile access and missing-data interpretation are in §§4, 7 and 9. |
Z, Chunk grids and Storage / Chunk key encoding define the regular-grid and default chunk-key-encoding mechanisms. §2.1 selects the profile's choices. Upstream codec specifications define compression algorithms and binary representations. §7.3 restricts the supported configurations.
0.3 Informative reference snapshots
The table lists the snapshots that the migration plan recorded as inspected. Convention registrations use the literal URLs required in §3.1. The historical sources below impose no TileMatrixSet or archived GeoZarr requirements on this profile.
| Source | Inspected immutable snapshot | Date | Role |
|---|---|---|---|
| GeoZarr SWG | d636b05abbfaa9851d3f12e91335bda22a127243 | 2026-07-06 | Informative convention-composition context. |
| Archived OGC draft | 82cba263ff53db4a9ab25366e3e3ed3777ff3f77 | 2025-12-08 | Historical archives-2025 design only. |
| F | d8077b612759013c0380c4ee562ade2873141da4 | 2026-06-18 | Framework. |
| M | 9b78efa75fef0fed302d9cf880037c569354d860 | 2026-06-12 | v0.1, Pilot. |
| P | 5ca5b2f92e5c7245f957d9128b289ee535f0720d | 2026-06-12 | v0.1, Pilot. |
| S | 54d81b7ced0376e63ee10f34db31db7d08dcc28d | 2026-06-12 | v0.1, Pilot. |
| ndpyramid schema | bad4c49461fe51cde7e1035a0504ed4d8780efa3 | 2026-04-06 | Historical layout comparison. |
| Z / B / I | ad8fc8df42441c84039c94569980e485e4c09870 | 2026-09-21 | Core and codec sources. |
Pilot conventions may change before they stabilize. A later upstream convention version requires a deliberate profile revision. This draft declares v0.1. Measurement log records the reader checks, with versions and limits.
0.4 Reserved future work
A storage extension for temporal encoding is reserved for future work. It is outside this baseline. Such an extension must be fail-closed in unaware readers. An unaware reader MUST reject the extension before returning any encoded data as measurements. This document specifies no storage-extension syntax, algorithm, registration or decoding mechanism. The baseline MUST NOT use temporal encoding or require another timestep to decode a data chunk. A safely ignorable convention attribute cannot change the interpretation of stored values into a storage-decoding operation.
1. Scientific and access guarantees
- A conforming writer followed by a conforming read of level 0 MUST return the exact input stored values in the input dtype. Writers MUST NOT quantize, round or apply lossy compression to level-0 data. §5 specifies derived overview rounding.
- Any timestep of any cell at any level MUST require only one data-chunk read after the relevant metadata and, if applicable, shard index are available. A timestep does not depend on other timesteps. Reads of optional validity or coverage planes are plane reads, and they do not count as data-chunk reads.
- Data MUST be stored and returned in the declared data dtype. The format MUST NOT convert between integer and float or quantize stored data. Physical values are derived at read time (§4.4). The stored array does not contain them.
- Group and array metadata MUST fully describe layout, bands, timestamps, CRS, geometry, chunk grid, codecs and declared optional planes. A reader MUST NOT need a sidecar or an external metadata service to determine the store's values and geometry.
- Every data, coordinate and auxiliary array MUST hold its true stored values. A generic Zarr v3 client that supports the declared codecs reads those values. Interpreting physical units and profile validity still requires §§4 and 9.
2. Time-series array profile
2.1 Levels and data cells
The root MUST contain consecutive level groups named "0", "1" and so on, with no gaps. Each group MUST contain the data array named by chronozarr.variable and any declared optional planes. It SHOULD contain the coordinate arrays time, band, y and x, which carry the same information as the mirrors and the transform (§§2.2, 3.4). Readers MUST NOT require them (§9.2). The data variable name defaults to "data". Readers MUST NOT hardcode the name. Level 0 is the native grid. Level shapes follow §5.
| Data-array property | Profile restriction |
|---|---|
| Shape and axis order | MUST be [n_time, n_band, H_k, W_k], with positive axis lengths and dimensions ["time", "band", "y", "x"]. |
| Data dtype | MUST be uint8, uint16, int16 or float32, identical at every level. |
| Grid / keys | MUST select Z's regular grid and default chunk-key encoding with separator /. |
| Unsharded chunks | MUST have shape [1, n_band, cs, cs]; keys are c/{t}/0/{r}/{c}. |
| Sharded chunks | MUST use §7.1; the spatial inner chunk size remains cs. |
| Fill / nodata attribute | MUST follow §4.1. |
| Codec chain | MUST follow §7.3, inside the indexed-sharding codec when applicable. |
cs MUST be a positive even integer, identical at every level, with equal row and column chunk sizes. Writers SHOULD use 256 or 512, with 512 the default. Readers MUST accept other positive even sizes, including small test fixtures. Readers MUST derive cs from the data array's spatial inner chunk dimensions (indices 2 and 3), using I's inner chunk_shape when sharded. They MUST NOT derive cs from multiscales metadata or assume 256 or 512. Every data chunk MUST hold all bands of one timestep of one cell. The band chunk index is 0.
At level k, cell (r,c) is the spatial slice [r*cs:(r+1)*cs, c*cs:(c+1)*cs] for any timestep and band. Row 0 is the north edge. The cell grid MUST equal [ceil(H_k/cs), ceil(W_k/cs)]. Elements that the upstream chunk representation uses as out-of-shape padding MUST equal the ordinary fill_value. §0.2 governs edge extent and bounds handling.
Writers SHOULD store every chunk of the data, mask and coverage arrays, all-fill chunks included, and with sharding every shard, although Z and I let them omit one. A reader requests each chunk of the cells it shows. An absent key costs a request that ends in 404, which browsers log as an error, and a CDN that does not cache 404 answers passes every such request to the origin. Readers MUST still read an absent chunk or shard as fill_value, as Z and I define, because other writers and earlier stores omit them. An append does not write the chunks of existing timesteps (§8.3), so an absent one stays absent.
2.2 Coordinates and dimensions
| Coordinate | Dtype / contents | Requirements |
|---|---|---|
time | int64, Unix epoch milliseconds, length n_time | MUST be strictly increasing. SHOULD carry units: "milliseconds since 1970-01-01T00:00:00" and calendar: "proleptic_gregorian" for native CF datetime interpretation. When present, they MUST have those values. Monthly, weekly and irregular cadences are permitted. |
band | Zarr string with vlen-utf8, or int32, length n_band | MUST contain band names in array order when strings are used; otherwise MUST contain indices 0..n_band-1. |
y | float64, length H_k | MUST contain decreasing projected pixel-centre y coordinates in the declared CRS. |
x | float64, length W_k | MUST contain increasing projected pixel-centre x coordinates in the declared CRS. |
Every array, including coordinates and optional volatility, MUST declare dimension_names. It SHOULD also declare _ARRAY_DIMENSIONS, and when it does the two lists MUST be identical. Readers MUST NOT require _ARRAY_DIMENSIONS. A coordinate array uses its own one-element dimension list. Each coordinate array SHOULD occupy a single chunk. The time and band coordinate values MUST be identical at every level. Coordinates MUST agree with the canonical spatial metadata (§3.3). The x and y coordinates describe centres under S's pixel registration.
The ISO timestamp and band-name mirrors MUST agree exactly with their coordinate sources (§3.4). If band contains integer indices, band_names MUST instead agree with the ordered bands[].name. Names are not compared with those integer indices. Readers MUST NOT require int64 or variable-length string coordinate reads when valid mirrors supply the needed information.
2.3 North-up grid in any CRS
All spatial arrays MUST use the same CRS and north-up affine geometry. The CRS is any that P allows: an authority code in proj:code (EPSG or another authority), WKT2 in proj:wkt2, or PROJJSON in proj:projjson. At least one MUST be present. When they disagree, proj:wkt2 takes precedence, as P says, and a validator MUST report the disagreement. Rotated and south-up grids are outside this profile. In the S coefficient notation, horizontal pixel scale MUST be positive, vertical pixel scale negative, and both rotation/shear coefficients zero. This restricts S's transform. It leaves S's coefficient ordering and mapping unchanged (§0.2).
Writers MUST write proj:wkt2 when the CRS has no authority code, and SHOULD write it whenever they can. They MUST write proj:code when the CRS has an EPSG code. Writers SHOULD retain the native CRS of the source, for example a UTM zone, a Lambert conformal conic or a sinusoidal grid, and SHOULD NOT reproject storage. Reprojecting to Web Mercator does not preserve pixel ground area, which affects area-sensitive block means and statistics, and any reprojection resamples every value. Geometry and mirror agreement follow §3.3.
3. chronozarr attributes and mirrors
3.1 Convention registration and root metadata
The root MUST declare chronozarr and M in attributes.zarr_conventions, using F's Convention Metadata Objects. Every data, mask and coverage array MUST explicitly declare P and S on that array, rather than depend on inheritance for profile conformance. Coordinate arrays and ungeoreferenced volatility MUST NOT declare S. Other registrations MAY appear only when their conventions apply without changing the baseline's ordinary stored values.
Writers MUST emit each M/P/S registration with the following UUID, name and literal schema/spec URL pair. Commit-based URLs MUST NOT be emitted in these registrations. Readers identify a convention by its uuid alone. Other tags, such as refs/tags/v1, other repositories, such as zarr-experimental/geo-proj, and other names, such as proj:, register the same UUIDs. Readers MUST NOT require the name or the URLs to equal the literals below, and MUST read the attributes of a convention whether or not the store registers it (§9). The convention snapshot identities in §0.3 MUST NOT be emitted as store metadata. F's allowed registration fields and semantics apply by reference. No snapshot field or extra version field is added to the registration object.
| Name | UUID | schema_url | spec_url |
|---|---|---|---|
multiscales | d35379db-88df-4056-af3a-620245f8e347 | https://raw.githubusercontent.com/zarr-conventions/multiscales/refs/tags/v0.1/schema.json | https://github.com/zarr-conventions/multiscales/blob/v0.1/README.md |
proj | f17cb550-5864-4468-aeb7-f3180cfb622f | https://raw.githubusercontent.com/zarr-conventions/proj/refs/tags/v0.1/schema.json | https://github.com/zarr-conventions/proj/blob/v0.1/README.md |
spatial | 689b58e2-cf7b-45e0-9fff-9cfc0883d6b4 | https://raw.githubusercontent.com/zarr-conventions/spatial/refs/tags/v0.1/schema.json | https://github.com/zarr-conventions/spatial/blob/v0.1/README.md |
The root chronozarr registration MUST contain name: "chronozarr" and spec_url: "https://github.com/chronozarr/chronozarr/blob/main/spec/CHRONOZARR.md". The chronozarr block records its profile version. This draft assigns no chronozarr UUID or schema URL.
The root MUST carry a chronozarr object (§3.2) and a multiscales object conforming to M (§3.3). Consolidated metadata and its recommendation follow M, Consolidated Metadata (§0.2). Readers MUST retain the nonconsolidated fallback in §9.2.
3.2 chronozarr block
| Field | Type | Profile rule |
|---|---|---|
spec_version | string | Writers MUST write "0.3.0" when the store's CRS has an EPSG code and "0.4.0" when it has none. Readers MUST accept both, and any patch version of either minor (0.3.1, 0.4.2), which they report. They MUST reject every other value, including missing values, before returning data, with a message that names the versions they accept (§9.1). Releases up to 0.4.1 accept only "0.3.0", so every store with an EPSG code stays readable by them. |
variable | string | Data-array name inside each level, default "data". Writers MUST declare it. A reader that finds it absent reads "data" and reports it. |
times | string[] | MUST be written, with length n_time. Each entry MUST be the ISO-8601 rendering of the corresponding time coordinate. |
bands | object[] | MUST be written, with length n_band. Entries are band-description objects (§4.4). |
band_names | string[] | Writers SHOULD write the ordered bands[].name. Readers that find only bands MUST derive the names rather than read the band coordinate. |
nodata | number or null | MUST be declared (§4.1). |
crs | string | SHOULD be written when the CRS has a code, as the proj:code string such as EPSG:32631, and absent otherwise. When present it MUST equal the canonical P code on every spatial array. Readers MUST NOT require it. |
levels | object[] | Writers SHOULD write the ordered mirrors in §3.4. Readers MUST support their absence through §9.2. |
mask_variable | string | MUST equal "mask" if and only if masks are present at every level. Otherwise MUST be absent. |
coverage_variable | string | MUST equal "coverage" if and only if coverage is present at every level. Otherwise MUST be absent. |
volatility_path | string | MAY be present. MUST equal "volatility" if and only if the optional root volatility array is present (§6). Otherwise MUST be absent. |
provenance | object | MAY be present (§4.5). |
shard_bytes | object | MAY be present only for sharded stores (§7.2). |
This block has no temporal-encoding fields. The baseline MUST NOT use attributes to reinterpret ordinary chunks as encoded measurements.
3.3 Multiscales and authoritative geometry
multiscales MUST use M's object form with layout. Its entries MUST be ordered by the consecutive level groups "0", "1" and so on. Each asset MUST be the group path, not a data-array path. Each level after 0 MUST declare derived_from equal to the preceding group and a relative transform with scale: [2,2] and translation: [0,0], under M's Transform Object. Writers MUST write resampling_method as "average". The exact average semantics are chronozarr rules in §5. A reader MUST NOT refuse a store whose resampling_method is another value or is absent. It reads level 0 as stored and reports that the overview levels are not the §5 block means. The base entry MAY carry the identity relative transform. Legacy list/datasets metadata and tile-size hints MUST NOT be written or used for v0.3 discovery.
Informative example of a two-level object:
{
"multiscales": {
"layout": [
{"asset": "0"},
{"asset": "1", "derived_from": "0", "transform": {"scale": [2, 2], "translation": [0, 0]}}
],
"resampling_method": "average"
}
}Every spatial array MUST carry its CRS as §2.3 says, spatial:dimensions: ["y","x"], spatial:transform and spatial:registration: "pixel", and satisfy P/S. If spatial:transform_type is supplied, it MUST be "affine". Every representation present MUST describe the same CRS. Optional spatial:shape MUST equal [H_k,W_k]. Optional spatial:bbox MUST agree with the array's shape and S geometry. Equivalent properties supplied on M layout entries MUST agree with the spatial arrays. P/S are the authoritative CRS and geometry sources. chronozarr mirrors MUST NOT override them.
Level k MUST have the same origin as level 0 and both pixel scales multiplied by 2^k. All spatial arrays in a level MUST agree geometrically. Each level group SHOULD retain transform, resolution and crs mirrors. crs is written when the CRS has a code and MUST then equal proj:code. Readers MUST NOT require any of them, and take the geometry of a level from the canonical S metadata of its arrays. A transform mirror MUST equal the canonical S coefficient list without introducing another mapping. A resolution mirror MUST equal the positive horizontal ground sample distance at that level. A validator MUST check each mirror that is present against the canonical array metadata.
Spatial arrays MAY repeat crs and transform aliases. When present, these MUST agree with P/S. Readers MUST NOT require them. Writers SHOULD emit _CRS on data, mask and coverage arrays for GDAL versions below 3.13. For a CRS with an EPSG code it is {"url":"http://www.opengis.net/def/crs/EPSG/0/<code>"} with an optional matching string wkt. For a CRS with no EPSG code it is {"wkt":"<WKT2>"}. Readers MUST NOT require _CRS. If present, _CRS MUST agree with the CRS in P. Measurement log records the GDAL checks.
3.4 Mirrors and validation
Readers MUST use the available times, band_names and levels mirrors as primary request-saving sources. They MUST NOT require coordinate-array reads to obtain the same information. A validator MUST check mirror/source agreement. Disagreement is an error. It does not permit silent replacement of authoritative P/S metadata.
times[i] MUST render the exact epoch-ms coordinate value. band_names[i] MUST equal bands[i].name and, for string band coordinates, band[i]. The levels mirror MUST contain one entry per M layout entry, in the same order:
| Field | Type | Equality rule |
|---|---|---|
path | string | MUST equal the corresponding multiscales.layout[].asset group path. |
resolution | number | MUST equal the level group value and canonical horizontal pixel scale. |
transform | number[6] | MUST equal the level-group mirror and canonical S transform. |
shape | integer[4] | MUST equal the data array shape [n_time,n_band,H_k,W_k]. |
grid | integer[2] | MUST equal [ceil(H_k/cs),ceil(W_k/cs)]. |
Writers SHOULD emit the mirrors specified above. Readers MUST NOT require any of them. The reader fallbacks in §§3.2 and 9.2 support discovery of baseline values. They need no legacy parser. A validator MUST report an absent mirror as a note and not as a failure. It MUST report a mirror that disagrees with its source as an error.
4. Validity, units and provenance
4.1 Dtype, nodata and fill
| Data dtype | Allowed nodata | Writer default | Overview arithmetic |
|---|---|---|---|
uint8 | Integer 0–255, or null | 0 | Integer (§5). |
uint16 | Integer 0–65535, or null | 0 | Integer (§5). |
int16 | Representable integer, or null | null | Integer (§5). |
float32 | Finite representable number, or null | null | Float (§5). |
chronozarr.nodata MUST be one number or null. Null declares no nodata sentinel. If it is a number, it MUST equal each data array's fill_value and nodata attribute. If it is null, fill_value MUST be 0 and the data array's nodata attribute MUST be absent. NaN MUST NOT be used as nodata. Writers SHOULD NOT store NaN data. Gaps SHOULD be marked using the sentinel or mask.
A pixel's validity follows the first case that applies:
- If the mask exists, the pixel is valid if and only if its mask value is 1.
- If there is no mask and a numeric nodata sentinel exists, the pixel is valid if and only if its data value differs from that sentinel.
- Otherwise, the pixel is valid.
A reader with a mask MUST use it and MUST NOT also compare data to the nodata sentinel. Invalid pixels MUST be treated as missing in band math, statistics, block means and charts. Where mask equals 0, the data value is not interpreted. Writers SHOULD store fill_value there. A missing optional mask does not make the store invalid. It changes which of these validity rules applies.
4.2 Mask
A writer MAY supply {level}/mask, but MUST supply it at every level or at none. The root declaration follows §3.2. Every mask MUST contain true uint8 values 0 (invalid) or 1 (valid), with shape [n_time,H_k,W_k], dimensions ["time","y","x"], matching _ARRAY_DIMENSIONS, and fill_value: 0.
Mask chunks MUST follow the data layout without the band axis:
- unsharded
[1,cs,cs], keysc/{t}/{r}/{c} - sharded
[shard_time,cs,cs]with inner chunks[1,cs,cs], keysc/{ts}/{r}/{c}
The declared spatial metadata and codec chain MUST follow §§3.3 and 7. A coarser mask MUST be the maximum over each 2×2 source block, padded by edge replication as in §5. The result is 1 if any source pixel is valid.
4.3 Coverage
A writer MAY supply {level}/coverage, but MUST supply it at every level or at none. Its declaration follows §3.2. Every coverage array MUST use uint8, shape [n_time,H_k,W_k], dimensions ["time","y","x"], matching _ARRAY_DIMENSIONS, and fill_value: 0. Its layout, chunk sizes, keys, spatial metadata and codec chain MUST match the mask rules, whether or not a mask exists.
Level-0 coverage MUST represent the number of valid observations behind a pixel, saturated at 255. Zero denotes a pixel that was gap-filled or never observed. At a coarser level it MUST be the mean of the four edge-replicated source values, rounded to nearest integer with halves up: (sum + 2) // 4. A coarser value is a rounded summary of its source values. Coverage MUST NOT replace the mask or sentinel validity rule. A gap-filled pixel can be valid with coverage 0. Gap-fill provenance follows §4.5.
4.4 Band descriptions and physical values
Each chronozarr.bands entry MUST be an object. String-only descriptions and source-specific scale inference are outside this profile.
| Field | Type | Rule |
|---|---|---|
name | string | MUST be unique within the store and equal the string coordinate value where band coordinates hold names. |
common_name | string | MAY be supplied; SHOULD use the applicable STAC eo:bands vocabulary, e.g. red, green, blue, nir, swir16 or swir22. |
scale | number | MAY be supplied; default 1. Writers SHOULD write it explicitly. |
offset | number | MAY be supplied; default 0. Writers SHOULD write it explicitly. |
units | string | MAY be supplied; free text, e.g. "reflectance" or "fraction". |
Physical value is stored * scale + offset. Consumers MUST apply that formula whenever valid physical values are shown or combined. Invalid pixels MUST remain missing and MUST NOT be scaled into valid measurements. Consumers doing band math or indices SHOULD select by common_name, falling back to name. They MUST NOT assume a source's reflectance scale. An RGB uint8 band with scale 1 is interpreted in its stored units.
Writers MUST NOT set CF scale_factor or add_offset on data arrays to silently trigger automatic scaling by generic clients. Generic readers see stored values. Conversion to physical units is an explicit consumer operation. The CF time units in §2.2 are independent of this band-value rule.
4.5 Provenance
A writer MAY supply chronozarr.provenance. When present it MUST contain:
| Field | Type | Rule |
|---|---|---|
sources | string[] | Required; collection identifiers or input-data URLs. |
composite | string | Required; temporal-composite description, e.g. "monthly median". |
gap_fill | string | Required; "none" or "carry-forward". Carry-forward means a pixel with no valid observation takes the previous timestep's value. |
notes | string | Optional additional explanation. |
Provenance MUST describe the processing applied. It leaves validity and coverage interpretation unchanged.
5. Overview semantics
Level 0 MUST retain native-resolution stored values. Each level k>0 MUST be derived from level k-1 by a factor-two block mean of true values, excluding invalid pixels under §4.1. A block with no valid pixels MUST produce the declared nodata value, or 0 if nodata is null.
Before reduction, the source MUST be padded to an even height and width by edge replication, including the validity and coverage planes. So H_k = ceil(H_{k-1}/2) = ceil(H_0/2^k), and similarly for width. The origin MUST remain fixed and ground sample distance MUST double at each level (§3.3).
For uint8, uint16 and int16, writers MUST:
- compute the exact sum in a wider integer type (uint32 or int32 as appropriate),
- divide by the valid-pixel count using floor division, and
- store the result in the unchanged data dtype.
Float32 means MUST accumulate in float64 and be stored as float32. Masks and coverage MUST reduce as in §§4.2–4.3. No other overview resampling method is part of this profile.
The spatial chunk size MUST stay constant. Only array shape and cell grid shrink. Levels MUST be consecutive from 0. The default writer MUST stop at the first level whose cell grid is 1×1, including that level. A writer MAY explicitly choose fewer or more levels.
Integer block means do not preserve categorical classes or binary shares. A 2×2 block with three integer 1s and one 0 becomes 0 under floor division. A binary quantity SHOULD be stored as a scaled fraction, e.g. 0/10000 with scale 1e-4 and units "fraction". The coarse stored value then represents the flagged share. Class codes have no meaningful arithmetic mean. A writer requiring majority or nearest categorical overviews must prepare a separately described product. It MUST NOT advertise such a pyramid as this profile's average pyramid. The default mean and its limitations MUST NOT be silently replaced by a categorical rule.
6. Volatility
A store MAY include the root array volatility, declared only through chronozarr.volatility_path. Its absence is conforming. Its absence MUST NOT prevent decoding or scientific interpretation of data. When present, it MUST use true float32 values, shape [grid_rows_0,grid_cols_0], dimensions ["row","col"] with matching _ARRAY_DIMENSIONS, and one chunk covering that shape. It is a cell-ordering metric with no georeferenced pixels. It MUST NOT declare S.
The existing nominal comparison policy is kept for this metric alone. The publisher chooses a positive integer comparison interval s, default 6. Let C={0,s,2s,…} restricted to indices below n_time. Let D be the other timestep indices. For each t in D, q(t) is the closest index in C by absolute index distance, with ties toward the earlier index. The comparison policy is independent of storage and need not be recorded. It is not a decoding instruction. Readers MUST NOT require the comparison policy to decode data or use the stored metric for ordering.
volatility[r,c] = clip(
mean(abs(source[t] - source[q(t)])
over t in D, all bands and all source pixels of level-0 cell (r,c)) / 10000,
0, 1)When written, this value MUST be computed from exact differences: int32 for integer data and float64 for float32 data. The mean MUST include invalid source pixels, as in the existing publisher metric. The mean MUST use level 0 only. The value MUST be 0 if D is empty, including s=1 or n_time=1. An all-zero mean likewise yields 0. Results MUST be clipped to [0,1] and stored as float32. The divisor 10000 is fixed for every dtype. It reflects the original reflectance normalization. It is not a physical unit. For other sources it remains a relative temporal-change metric, and its values are not calibrated change magnitudes.
Readers MAY use volatility to order prefetch or draw change overviews. They MUST distinguish optional metric availability from data decodability. A present array that violates this definition is a conformance error. An absent array is not a conformance error.
7. Storage interoperability restrictions
7.1 Unsharded default and optional time sharding
Writers MUST default to unsharded data, mask and coverage arrays. A writer MAY explicitly choose indexed time sharding. Readers MUST support both forms and determine the form from the codecs, not a filename assumption. Unsharded objects and cells follow §§2.1 and 4. A timestep of a cell costs one object GET and no index read.
A sharded data array MUST select sharding_indexed with shard shape [shard_time,n_band,cs,cs] and inner shape [1,n_band,cs,cs]. Mask and coverage shard shapes MUST be [shard_time,cs,cs], inner shapes [1,cs,cs], using the same positive integer shard_time. Sharding index and empty-chunk semantics are inherited from I (§0.2).
shard_time MUST be an integer at least 1. When sharding is explicitly chosen, the default shard_time is n_time at creation. It MAY exceed n_time. Partial time shards follow I. The number of time shards is ceil(n_time/shard_time). Readers MUST handle multiple time shards. A writer MUST NOT accept a shard_time option without enabling sharding.
Timestep t belongs to time shard ts=floor(t/shard_time) at inner timestep t mod shard_time. The data shard key is c/{ts}/0/{r}/{c}. The plane key is c/{ts}/{r}/{c}. There is one shard object per time shard and spatial cell per level and variable. The data band grid remains one. Readers MUST derive the shapes and mapping from the regular grid and I configuration.
A writer SHOULD choose shard_time so no object exceeds the intended host or CDN cache or range-serving limit, and a whole-object miss is tolerable. A CDN may retrieve a whole large shard for a small index range. Measurement log has the measurements. For appendable stores, unsharded storage SHOULD be used. If object count justifies sharding, writers SHOULD choose a finite interval, e.g. 12 for monthly data, instead of automatically using an entire long archive. Whole-axis sharding is appropriate for archives that will not be appended. An append rewrites the shard receiving new timesteps (§8.3).
This paragraph is informative. Writing every chunk (§2.1) stores all-fill inner chunks in a shard, where I lets a writer mark them empty in the index. A reader then makes one small range read for each all-fill inner chunk it shows, where an empty index entry costs none. On a sharded store whose cells were 69 % empty, a timestep switch over 64 cells took 64 requests in the JavaScript reader, against 8 when the empty cells had no shard (Measurement log).
7.2 Index access, cache and byte-length hints
The index representation, checksum, placement semantics and missing or empty chunk rules are those of I, Index / Index location / Empty chunks (§0.2). Writers SHOULD use index_location: "end" for tested browser interoperability. Readers MUST support both upstream index locations. They MUST cache indices per shard. They MUST reuse one array handle per level, so an implementation's per-array index cache stays effective.
chronozarr.shard_bytes MAY inventory existing data-array shard objects (not mask or coverage), using:
{ "<level group path>": { "<t_shard>/<row>/<col>": <exact object byte length> } }When supplied, the inventory MUST list exactly the data shards that exist at every level, with exact lengths for the published metadata snapshot. A reader MUST use a listed length for a bounded index range. It MUST fall back to HEAD to learn the length of an unlisted shard. Given object length L and index length N determined under I, an end-index bounded request is Range: bytes=(L-N)-(L-1). Without a listed length, suffix-range access or the HEAD fallback follows the host's capabilities. The required HEAD fallback MUST remain available. Missing objects follow I's empty-chunk rules.
Lengths MUST be updated when append rewrites an object. An unchanged shard retains its length. §8.4 specifies snapshot recovery for a replaced trailing shard.
7.3 Codec subset
Codec algorithms, configuration semantics and binary representations follow bytes, zstd, gzip and blosc. This profile restricts the choices:
| Compressor | Profile configuration |
|---|---|
zstd | Default: level 5, checksum false. |
blosc | cname MUST be zstd or lz4. shuffle MUST be noshuffle or shuffle. clevel MUST be 0–9. typesize MUST equal the array element size in bytes. blocksize MUST be 0. |
gzip | Level MUST be 1–9. |
Readers MUST support all three compressors, including both allowed blosc compression and shuffle variants. Writers MUST use exactly one supported compressor preceded by the bytes codec with little-endian configuration for numeric arrays. Byte-order exceptions for one-byte dtypes follow B (§0.2). For string band coordinates, the standard Zarr vlen-utf8 array-to-bytes codec replaces numeric bytes serialization, followed by a supported compressor. This required string representation is not another permitted numeric compressor.
Other compression codecs, other blosc cname values, and shuffle: "bitshuffle" MUST NOT be used. The data, mask and coverage arrays MUST use the same codec chain, apart from element-size and byte-order differences required by their dtypes and the surrounding sharding configuration. Coordinates and optional volatility MAY independently choose any of the three supported compressors. Readers MUST report unsupported data types or codecs by name (§9.2).
8. Static publishing and append
8.1 HTTP host contract
Stores are served as objects by key from a static host. No application server is required. Z's node metadata representation applies by reference (§0.2).
| Host behavior | Requirement |
|---|---|
| GET of an existing key returns its object bytes; an absent key returns 404, not a 200 fallback page | MUST. |
| Range requests return 206 Partial Content with Content-Range | MUST for sharded stores; unsharded stores require only GET. |
| Chunk/shard bytes are served unchanged, with no Content-Encoding or other transformation | MUST. |
Access-Control-Allow-Origin: * | MUST. |
Access-Control-Allow-Headers: Range or *, and OPTIONS preflight answers 200/204 | SHOULD. |
Access-Control-Expose-Headers: Content-Range, Content-Length | SHOULD. |
Cache-Control: public, max-age=31536000, immutable on immutable objects | SHOULD; mutable append objects use §8.3. |
Timing-Allow-Origin: * | MAY. |
Measurement log records the CORS preflight and Timing-Allow-Origin checks. Directory listing MUST NOT be required. Consumers MUST derive keys from metadata and MUST NOT depend on object content types.
8.2 Immutable publication
A re-encode MUST be written under a new prefix, never over an existing published store. The only permitted in-place growth is append under §§8.3–8.4. Append preserves old values.
Initial upload order SHOULD be:
- data and plane chunks and shards
- metadata below the root
- root metadata
The reader uses root metadata as the publication marker. Metadata-last publication leaves a multi-object update non-atomic. Complete working-copy validation is still required.
8.3 Append restrictions and writes
A store MAY grow only at the end of its time axis. New dates MUST be strictly after the previous final date. New dates MUST have compatible grid, bands (including units, scales and offsets), dtype, CRS and nodata. A store with a mask or coverage MUST receive that plane for every new timestep. A store without the plane MUST NOT acquire it through append. Existing grid geometry, level count, cell size, layout and codec configuration MUST remain compatible.
The writer MUST construct an append in a working copy and validate it before publication. It MUST:
- extend every level's data and declared mask and coverage shapes to the new
n_time, - rewrite the time coordinate as a single chunk of the new length, and
- update
chronozarr.times,levels[].shape, affectedshard_bytes, array shapes and consolidated metadata when present.
Optional volatility, if present, MUST be updated to satisfy §6 over the enlarged series. Its absence does not require adding it. Each new overview timestep MUST be derived by the same §5 rules as a fresh encode. M layout and fixed geometry remain unchanged.
Unsharded append MUST write only new timestep chunk objects and the mutable metadata, coordinates and optional metric. With sharding, only shards receiving new timesteps MAY be replaced. These are the previously partial trailing shard and any newly created time shards. Earlier completed shards MUST remain byte-identical. A replaced trailing shard MUST retain byte-identical encoded chunks and unchanged decoded values for all existing timesteps. I does not promise identical offsets in a rewritten object.
Every existing unsharded data, mask and coverage chunk MUST remain byte-identical. All old band, x and y coordinate values and objects, level geometry, and M layout MUST remain unchanged. The existing prefix of the time coordinate MUST remain unchanged in value even though its single chunk is rewritten. No previously published data or validity meaning may change.
The following objects MAY change in place:
- root and descendant node metadata
- each level's time-coordinate chunk
- optional volatility
- previously partial trailing shards
All other existing chunk and shard objects MUST remain immutable. Hosts SHOULD give mutable objects short cache lifetimes. Append publication SHOULD upload objects in this order:
- new or replacement chunks and shards
- time-coordinate chunks and optional volatility
- descendant metadata
- root metadata
Metadata-last ordering provides neither atomicity nor automatic rollback. The working copy and validation are required.
8.4 Reader snapshots and stale-index recovery
A reader holding a previous root metadata snapshot MUST continue to interpret its listed timesteps with the previous shapes and compatible geometry. It MUST reload root metadata to discover new timesteps. Preservation of old bytes and values is required. Preservation of offsets by a particular writer is not a universal guarantee.
For a mutable trailing shard, a reader MUST NOT blindly apply cached offsets from an old shard version to replacement bytes. A reader that detects a version or length mismatch, an invalid index, a failed index checksum or an incompatible chunk read MUST:
- discard the affected index,
- refresh metadata and length information, and
- refetch the current index before retrying.
Readers MUST keep array shapes consistent with their selected metadata snapshot. Older listed timesteps remain readable from the updated shard's index. A stale listed length can put an end-index range at the wrong byte location. Reloading root and array metadata and obtaining the current object length are the recovery path. Once a subsequent shard begins, the previously completed shard MUST remain unchanged. Unsharded stores have no index-replacement hazard.
9. Consumer contract
A store conforms when chronozarr validate finds no problem: it satisfies every MUST of sections 1 to 8. A reader decodes a store when it returns the stored values, the geometry, the validity, and the scale and offset that the store declares, and reports each assumption it makes. A reader MUST decode every store whose values, geometry and validity it can read as declared, whether or not the store conforms.
A reader MUST NOT refuse a store for a deviation that does not change a value:
- a registration that is absent, or spelled otherwise than §3.1 says,
- a
resampling_methodother than"average", or none, - an absent
levels,band_names, level-group orcrsmirror, - an absent coordinate array, or absent CF attributes on the
timearray, - an absent
_ARRAY_DIMENSIONSattribute wheredimension_namesexist, - an absent
chronozarr.variable, - a patch version of
0.3or0.4(§9.1), - a chunk layout other than §2.1 and §7.1: a reader reads any chunking that Zarr decodes, and the one-request guarantee of §1 holds only for the layout the format writes, and
- a
levelsgrid mirror that does not match the stored chunks: the chunks decide.
A reader MUST make each deviation it read through available to its caller as a note, and the note SHOULD say what the deviation means for the values. For example, the overview levels of a store with another resampling_method are not block means, and level 0 is unaffected. chronozarr validate reports a deviation from a MUST as a problem and a deviation from a SHOULD as a note. A reader SHOULD also decode a store with no chronozarr block that declares its levels with multiscales (§9.4). A reader MUST still refuse a store whose values it cannot read as declared: a version it does not know (§9.1), a data type or codec it cannot decode, and metadata that contradicts itself (§9.2).
9.1 Profile and version rejection
A conforming reader MUST first GET {store}/zarr.json (or open the equivalent local root metadata) and check attributes.chronozarr.spec_version. It MUST accept "0.3.0" and "0.4.0", and any patch version of either minor, such as "0.3.1", noting that it does not know that version. It MUST reject any other or missing value before producing data. The error MUST name the unsupported or missing version and the versions accepted. It SHOULD say what to do: a v0.2 store is converted with chronozarr convert, and a store of a later version needs a later reader. For example: Unsupported chronozarr spec_version 0.2.0; expected 0.3.0 or 0.4.0. Convert a v0.2 store with chronozarr convert before opening it.
Readers of this document do not read v0.2 stores. A v0.2 store is converted first. There is no dual-version parser, automatic URL fallback, legacy band-string scale inference or legacy multiscales-list path. The conversion operation is outside the normal reader contract.
Readers MUST enforce the ordinary-value baseline and inherited Z extension rules before returning measurements. Mandatory-extension handling is inherited from Z, Extensions. This profile does not substitute an ignorable attribute flag for that mechanism.
9.2 Metadata discovery and fallback
Readers MUST take:
- timestamps from
chronozarr.times, - band objects from
chronozarr.bands, - the variable name from
chronozarr.variable, ordatawhen it is absent, and - validity inputs from
nodata,mask_variableandcoverage_variable.
They MUST use band-name and level mirrors when present (§3.4), deriving missing band_names from the band objects. When a level group lacks transform or resolution, they MUST take the geometry of the level from the spatial:transform of its data array.
When levels is absent, readers MUST:
- enumerate M's ordered
layout[].assetgroups, and - obtain canonical P/S geometry plus data shape, chunk and codec metadata at each level.
Readers MUST use available consolidated metadata for those properties. They MUST fall back to individual group and array node metadata when consolidation is absent. They MUST:
- derive
csfrom inner chunks (§2.1), - report any unsupported
data_typeor codec by name, and - reject metadata contradictions rather than invent a geometry override.
Mirrors avoid mandatory coordinate-array reads. Readers MUST NOT require the coordinate arrays at all: times come from chronozarr.times, band names from chronozarr.bands and pixel centres from the transform. Validation MAY read the arrays to test agreement.
A generic client is not automatically a conforming chronozarr reader. Measurement log records how xarray and GDAL read a v0.3 store. A chronozarr-aware consumer follows this contract whatever a generic client does.
9.3 Level, value and plane access
Readers MUST select the largest level index k whose resolution does not exceed the requested output ground sample distance, or k=0 if none qualifies. For a requested timestep and spatial cell they MUST read one ordinary data chunk using §§2 and 7, with the standard I decoding and Z bounds rules inherited in §0.2. They MUST NOT require another timestep's chunk to obtain that value.
Readers MUST apply §4.1 validity in math, statistics and charts, and §4.4 scale/offset wherever physical values are shown or combined. They MUST read mask or coverage planes only when their corresponding declarations are present. They MUST NOT treat coverage as a validity substitute. Optional volatility MUST NOT be required for opening or reading data.
Readers SHOULD cache decoded data chunks for the session. They SHOULD prefetch ordinary frames to reduce interaction latency. They MUST retain the per-shard index cache and array-handle reuse rules in §7.2, while recovering correctly for mutable trailing shards (§8.4). Consolidated root discovery and mirrors preserve a single-root-request metadata path.
9.4 Stores with no chronozarr block
A reader SHOULD decode a store that has no chronozarr block when its root multiscales lists the levels and each level has a geometry and a CRS. The levels come from M's layout or from the datasets list of ndpyramid 0.4. Level 0 is the finest level, whatever order the layout lists. The levels MUST share their times, dtype and CRS, and a reader refuses a store whose levels differ in them.
A level is a group of arrays. It holds one array with the dimensions (time, band, y, x), (time, y, x), (band, y, x) or (y, x), or one such array per band, which the reader stacks on a band axis in natural name order, so that b8a follows b07. The reader keeps the bands that every level has. Arrays with other dimensions, shapes or dtypes are left out.
The geometry of a level is the spatial:transform found nearest first on its array, its group, its layout entry and the root. Without one it is the x and y coordinate arrays, read as evenly spaced pixel centres. The CRS comes the same way from proj:code, proj:wkt2 or proj:projjson, else from a crs on the layout entry, else from a CF grid mapping variable. Times come from the CF units of the time array. A grid that is not north-up is refused.
A reader MUST report every value it assumed:
- Scale and offset come from CF
scale_factorandadd_offseton the array, and from_eopf_attrsonly when the array has the dtype that_eopf_attrsnames, since a float32 array under<u2attributes holds decoded values. Without them the scale is 1 and the offset 0, as an assumption. - A pixel is missing when it equals
_FillValue, or the array'sfill_valuewhen that is not Zarr's default 0. NaN needs no marker. Each level has its own. - A store with no time axis is one timestep, dated 1970-01-01 as a placeholder.
- Overview levels are the writer's own resampling and not the §5 block means. Levels whose pixel size is not a power of two times that of level 0 are listed.
A reader MUST refuse a level whose geometry, CRS, dimension names, time array or dtype it cannot read, and says why. chronozarr validate reports such a store as not conforming and says that it decodes.
10. Changes from 0.3 and 0.2
These tables are informative. They list the removals and changes. Retained chronozarr requirements are normative in §§1–9. v0.2 stores require explicit conversion. They are not baseline reader inputs.
Changes from 0.3.0
Every 0.3.0 store remains valid. A reader of this document opens it unchanged.
| v0.3.0 rule | Change in this document | Section |
|---|---|---|
Every CRS MUST be an EPSG code in proj:code. | Any CRS that P allows: proj:code of any authority, proj:wkt2 or proj:projjson. proj:wkt2 takes precedence when they disagree. Writers MUST write proj:wkt2 when there is no authority code and SHOULD write it always. Rotated grids stay excluded. | §§2.3, 3.3. |
spec_version MUST be "0.3.0". | Writers write "0.3.0" when the CRS has an EPSG code and "0.4.0" when it has none. Readers accept both. The split keeps every store with an EPSG code readable by releases up to 0.4.1, which refuse "0.4.0". | §§3.2, 9.1. |
The root crs and the level-group crs MUST be EPSG:<code> mirrors. | SHOULD, written when the CRS has a code. Readers MUST NOT require them. A validator reports an absent mirror as a note. | §§3.2–3.4. |
_CRS is {"url": ...} for an EPSG code. | Also {"wkt": ...} for a CRS with no EPSG code. | §3.3. |
| A reader refuses a store that does not conform. | A reader decodes every store whose values, geometry and validity it can read as declared, and reports what it read through as notes. A store conforms when chronozarr validate finds no problem. | §9. |
| Registrations MUST be the literal v0.1 entries, and a reader checks them. | Writers still emit the literals. Readers match each convention by uuid and ignore the name and URLs, so refs/tags/v1 and geo-proj registrations read. | §3.1. |
resampling_method MUST be "average", and a reader checks it. | Writers still write it. A reader opens another value or none, and reports that the overview levels are not block means. | §§3.3, 9. |
A store with no chronozarr block is not a chronozarr store, and a reader refuses it. | A reader decodes a store that declares its levels with multiscales, from its layout and arrays, and reports each assumption. | §9.4. |
| A reader refuses a chunk layout other than one chunk per timestep and cell. | A reader reads any chunking. Writers keep the layout. | §§2.1, 9. |
spec_version is "0.3.0", and a reader rejects anything else. | Readers also accept 0.3.x and 0.4.x, and report a version they do not know. | §§3.2, 9.1. |
Writers MUST write band_names, levels and the level-group transform and resolution. | SHOULD. Readers take them from bands, the layout and the arrays. A validator reports an absent one as a note. | §§3.2–3.4. |
Every array MUST declare _ARRAY_DIMENSIONS, and the coordinate arrays and the CF attributes of time MUST be present. | SHOULD. dimension_names stay required. A coordinate array or CF attribute that is present MUST still be correct. | §§2.1, 2.2. |
| A writer may omit an all-fill chunk or shard, as Z and I allow. | Writers SHOULD store every chunk and shard, all-fill ones included. Readers MUST still read an absent one as fill. | §2.1. |
Changes from 0.2
| v0.2 rule or surface | Removal / change in v0.3.0 | New section / authority |
|---|---|---|
Version 0.2.x, acceptance of 0.1.x and 0.2.x | Exact 0.3.0 draft version. Every other or missing value is rejected with chronozarr convert guidance. No automatic legacy fallback. | §§3.2, 9.1. |
| Two temporal storage modes and required support for both | Removed. Every array holds ordinary true values. No temporal mode declaration or mode-dependent dtype eligibility. | §§0.4, 1, 4.1. |
| Star-delta anchors, anchor interval/indices, reference map and reference-distance rules | Removed entirely from baseline storage and reader requirements. | §§0.4, 1, 9.3. |
| Modular residual representation, reconstruction, clamp/overflow policy and residual-specific nodata handling | Removed. Only standard Zarr codec decoding remains. | §§1, 4.1, 9.3; Z/I. |
| Residual-zero edge padding versus anchor fill | Removed. Ordinary fill padding applies, with edge geometry and bounds inherited. | §2.1; Z, Chunk grids / shape. |
| Temporal auto/none/star-delta writer selection, sample ratio/threshold and selection metadata | Removed. No temporal selection API or metadata is specified. | §§0.4, 3.2. |
| Cross-shard temporal dependencies and two-data-chunk bound | Removed. One data chunk per timestep and cell after metadata and index discovery. | §§1, 7, 9.3. |
| Anchor-multiple shard sizing and anchor-first prefetch/caches | Removed. Sizing is based on host and append limits. Caches and prefetch use ordinary chunks. | §§7.1–7.2, 9.3. |
| Append additions to temporal maps, fixed references and reuse of earlier anchors | Removed. Append extends ordinary values and preserves old chunks and values. | §8.3. |
| Zarr hierarchy and leaf-node restatement | Replaced by upstream reference. | §0.2; Z, Hierarchy / Metadata. |
| Edge chunk extent and array-bound trimming restatement | Replaced by upstream reference. Fill-padding policy retained. | §§0.2, 2.1; Z, Chunk grids / shape. |
| One-byte bytes-codec endian exception restatement | Replaced by upstream reference. Numeric little-endian profile retained. | §§0.2, 7.3; B. |
| Local consolidated-metadata recommendation | Replaced by M reference. Nonconsolidated reader fallback retained. | §§0.2, 9.2; M, Consolidated Metadata. |
| Local six-coefficient affine definition and corner formula | Replaced by S reference. North-up, factor-two and same-origin restrictions retained. | §§0.2, 2.3, 3.3; S. |
| Shard index uint64 pairs, CRC layout, sentinel values, index-location/empty-shard semantics | Replaced by I reference. Both-location support, end-location advice, cache and length hints retained. | §§0.2, 7.2; I. |
| Node metadata naming versus v2 dotfiles | Replaced by Z reference. | §§0.2, 8.1; Z, Metadata. |
| Standard shard decoding and array bounds in the reader algorithm | Replaced by I/Z reference. Profile access and validity rules retained. | §§0.2, 9.3; I/Z. |
| ndpyramid list, datasets, type and metadata.method/version/args fields | Replaced by M object layout, asset, derived_from, relative transforms and declared average resampling. | §3.3; M. |
pixels_per_tile emission/ignore/legacy acceptance rules | Removed. No legacy tile-size hint or parser. Cell size is derived from inner chunks. | §§2.1, 3.3, 9.1. |
| Implicit convention composition | Explicit root chronozarr/M and spatial-array P/S registrations with literal v0.1 URLs. Snapshots recorded only as informative references. | §§0.3, 3.1. |
| Optional proj/spatial aliases and nonrequirement | Canonical array P/S metadata and registrations required. EPSG proj:code, affine geometry and explicit pixel registration required. | §§2.3, 3.3. |
| EPSG/native CRS mirrors interpreted as authorities | EPSG north-up scope fixed. P/S authoritative, and mirrors validated against them. Rotated and non-EPSG grids excluded; the non-EPSG exclusion ended in 0.4.0. | §§2.3, 3.3–3.4. |
_CRS compatibility alias | Writers SHOULD emit it for GDAL below 3.13. It is not a v0.3 reader requirement. Reader observations distinguish CRS assignment from overview attachment. | §§0.3, 3.3. |
| Levels mirrors tied to legacy datasets paths | Paths now match M layout assets. Geometry equality uses canonical S and Z shape. | §3.4. |
| String-only bands and implicit source-specific physical scaling | Removed. Object-only bands, explicit scale/offset advice and consumer physical-value rules retained. | §§4.4, 9.1. |
| Mandatory volatility, and its dependence on temporal encoding | Volatility MAY be absent. When present, the existing exact-difference/normalization metric uses a nominal comparison policy independent of storage. | §6. |
| Overview reduction followed by temporal encoding | Removed encoding stage. True-value block means, validity, edge replication and rounding retained. | §5. |
| Claims that all shard lengths are immutable | Lengths describe a snapshot and MUST change with rewritten append objects. HEAD and recovery retained. | §§7.2, 8.4. |
| Assumption that a writer keeps old shard chunk offsets | No universal offset guarantee. Old encoded chunk bytes and decoded values preserved. Cached index must be refreshed for changed shards. | §§8.3–8.4. |
| Metadata-last publication described as sufficient to prevent missing-data views | Publication order retained with explicit non-atomicity and working-copy validation. | §§8.2–8.4. |
| Append always updates volatility | Update only when volatility exists. Absence remains conforming. | §§6, 8.3. |
| Sections 0–14 and "Changes from 0.1" history | Reorganized as sections 0–9 plus this table. The old change file is a pointer to this section. Historical implementation and prior-art prose is not a baseline conformance rule. | §10. |
| Reference implementations described as current spec implementations | Removed. This is a draft. Observed generic-reader capabilities are informative. | §§0, 0.3, 9.2. |