Version: dev

plan_dimension_coordinates

Stable function · Runtime I/O

Tier: stable · Kind: function · Topic: Runtime I/O

JuliaTypeScriptPythonRustGo
plan_dimension_coordinatesoutside profilenot exportedplan_dimension_coordinatesoutside profile

Julia

plan_dimension_coordinates(gridding::AbstractVector{VarGridding}, meta::OutputMeta)
plan_dimension_coordinates(gridding, meta::OutputMeta) -> Vector{DimCoord}

Resolve the coordinates registry (§8.3) into the CF dimension coordinates for a set of VarGridding s: for each distinct spatial dim, if the registry has an entry KEYED BY THAT DIM NAME carrying inline values, emit a DimCoord (validating its length against the dim’s grid length) with the entry’s standard_name/units/axis attrs. Registry entries whose key is not a dim name (auxiliary coordinates) and source-backed entries are skipped in v1 (the dimension-coordinate path handles inline values); they are the documented next drop-in. Dims with no registry entry emit no coordinate (bare integer axis, as before).

Source

TypeScript

Not available in TypeScript. TypeScript is outside the runtime I/O capability profile (Julia, Python, Rust): data-source providers, refresh cadence, output sinks, checkpoints.

Python

Python does not export this function.

Rust

pub fn plan_dimension_coordinates(gridding: &[VarGridding], meta: &OutputMeta) -> Result<Vec<CoordPlan>, OutputError>

Resolve the coordinates registry (§8.3) into the CF dimension coordinates for a set of VarGridding s — the Rust mirror of Julia’s plan_dimension_coordinates.

For each distinct spatial dim, in first-seen order, a registry entry KEYED BY THAT DIM NAME carrying inline values produces a CoordPlan with the entry’s standard_name / units / axis. Entries whose key is not a dim name (CF auxiliary coordinates) and source-backed entries are skipped: they resolve against build artifacts, not the document, and are the documented next drop-in on the same registry. A dim with no entry emits no coordinate — a bare integer axis.

Errors OutputError::CoordLengthMismatch when an entry’s values length does not match the axis it names.

Source · Rust docs

Go

Not available in Go. Go is outside the runtime I/O capability profile (Julia, Python, Rust): data-source providers, refresh cadence, output sinks, checkpoints.