Data Integrations

An architecture-ready interface for light-pollution and Bortle-class sky-brightness data by location — which sets how faint an object a site can reach. Wired into the deep-sky planner; a site's darkness is reported only from a connected light-pollution source.

CONNECTED: total cloud cover from MET Norway, averaged across the night's dark window and reported alongside the observing plan rather than folded into it — a clear sky does not make a full Moon dark. Requested only when the reader presses the button, from their own browser, with the coordinates rounded to about a kilometre. Satellite cloud IMAGERY is a separate thing and is not connected.

An architecture-ready interface for atmospheric seeing — the steadiness of the air that sets how fine a detail a night can show. Wired into the astrophotography planner; seeing values appear only from a connected forecast source, never invented. NOT satisfied by the connected cloud-cover forecast: seeing is turbulence, forecast from entirely different model output, and a clear night with terrible seeing is an ordinary one.

An architecture-ready interface for sky transparency — how much haze and moisture dim faint objects. Wired into the deep-sky planner; transparency is reported only from a connected source.

Local weather — the first thing that decides whether a session happens. CONNECTED for total cloud cover only, from MET Norway, and fetched by the reader's own browser when they ask for it so their coordinates never reach this platform. Rain, wind and temperature come with the same forecast but are not what an observer is deciding on; nothing else about the weather is assumed.