meteo: the shared foundation

@azohra/meteo.core is the foundation of the meteo by Azohra platform: the shared physical vocabulary every other @azohra/* meteorology package builds on — units and conversions, angle and wind-vector math with one sign convention platform-wide, zod schema primitives, the upstream-failure vocabulary, and the machinery each capability uses to emit its JSON Schema artifacts.

Looking for a product, not a foundation?

• Forecasts — the published site-forecast contract, pure derivations, analysis, comparison, history, transport, and the Meteogram presentation tier → @azohra/meteo.briefing
• The forecast engine — fetch provider bytes, derive, and publish the documents yourself → @azohra/meteo.forecast
• Live stations — live weather-station reading, derivation, and display → @azohra/meteo.station
• Provider bytes — the pure-TypeScript GRIB2 decoder → @azohra/meteo.grib, and the JPEG 2000 decoder inside it → @azohra/meteo.j2k

What lives here

Curated exports only — core is deliberate API, not a junk drawer; nothing moves here merely to shorten an import:

• Units — the platform’s unit vocabulary and conversions (units.ts)
• Angles — angular math and compass conventions (angles.ts)
• Wind — the platform’s ONE wind sign convention (wind.ts)
• Schema primitives — shared zod building blocks: ianaTimeZone, httpUrl, and the positionFields position claims (schema.ts)
• Failures — the upstream-failure vocabulary (failures.ts)
• Schema artifacts — the rendering machinery behind each capability’s emitted JSON Schema artifacts (schema-artifacts.ts)

Everything exports through the one curated root surface — the package declares no subpaths:

import { KMH_PER_MPS } from "@azohra/meteo.core";

Dependencies: zod only.

The documentation

Page	Covers
Units, angles, one wind sign	The unit vocabulary, angle helpers, and the wind sign convention every platform package shares
Failures and schema artifacts	The closed upstream-failure vocabulary, and how capabilities render their JSON Schema artifacts