Tornado, hail, lightning and hurricane records — largely event reports rather than instrument readings.
Authoritative sources exist and publish continuously. Adapter not built.
That a tornado was reported, where, and along what track.
Reported maximum stone size at a location.
Detected strike position and timestamp from a detection network.
Position, pressure and wind at each advisory.
That a warning was in force for a polygon at a time.
Someone recorded that a thing happened. An observation, not a reading.
An instrument read a value at a place and a time.
An analyst or a model produced this from other data. It is a product, not a sensor.
Covers an area, not a point. There is no nearest station, and we will not invent one.
Measured at a fixed station. The record discloses which one and how far it is from you.
An authoritative body's analytical product. Its uncertainty is the source's own.
Published by an authoritative operator of the instrument.
Most of this lane is event records, not measurements. A tornado report is an observation someone made, with a different provenance shape and different failure modes — absence of a report is not absence of a tornado, and the record must never be read that way.
Not named here yet. Candidate sources for this lane exist and are identified internally, but they have not been verified against the primary documentation — and an unverified source attribution on a public page is the exact mistake this company exists to avoid. They appear here when they have been checked, not before.
Deciding whether event records belong in the same record model as measurements is open work. Until it is settled, nothing here is sold.
Hail damage claimed for a storm that missed. A lightning claim where the nearest recorded strike was miles away. A warning-time dispute over whether an evacuation was reasonable.
That framing is our analysis of where disputes arise, not a claim of fact about any matter.
We are not capturing this lane today, so there is nothing here to sell you and we are not going to pretend otherwise. What we do want is to know what you would actually ask it. Requests decide what gets built next — that is not a courtesy, it is how the order is set.