WeatherTrove

What it produces

WeatherTrove renders a station's weather breaks as finished audio on a repeating schedule. A typical setup pairs a forecast break with a shorter current-conditions break that air back to back as one segment, with the forecast opening it and conditions closing it so neither repeats the other's branding. Breaks are configuration entries rather than fixed features, so cadence, length, and the number of breaks are set per station.

Written for the hour it airs

Each break is written for the moment it renders. A six o'clock morning run sounds like morning drive; a late evening one leads with tomorrow. That framing comes from the clock, so one break rewritten through the day is always current rather than a set of pre-recorded dayparts that slowly stop matching the weather.

Accuracy is enforced, not assumed

Letting generated copy carry measured values is only safe if the values are checked. Every script is verified against the underlying observation and forecast data before it can air — any figure that cannot be traced back to the source data is rejected, and a deterministic template airs in its place while the failure is reported.

The same care applies to the data itself. Readings are converted according to the units the weather service actually declares rather than assumed ones, and a missing humidity or dew point is only filled in from a neighbouring station within a set distance. Beyond that radius the field is simply left out, because a reading from a different airmass has no business being announced as local.

Branding and sponsorship

The station's own wording is configuration: how the station says its name aloud, the open, the close, and pronunciation fixes for anything a synthesized voice would otherwise get wrong. A sponsor slot sits in the open and stays out of the read entirely until it is filled. Weather is one of the most sellable recurring positions on a station precisely because it airs often and everyone listens to it.

How it reaches the air

WeatherTrove writes finished, loudness-normalized audio to a fixed path that a permanent cart in the automation system already points at, replacing the contents of that file rather than importing new tracks. Nothing is written to the automation database, so there is no library to keep clean and no import step to fail. A render longer than the cart allows is refused rather than truncated mid-word.

Status

WeatherTrove is in development as a product for other stations. The underlying system is already producing weather breaks on a working FM station, which is where the handling of units, station distance, pacing, and verification has been proven.