Sign inRegisterCheck connection

What It Means for a Personal Weather Station to Publish

Publishing a PWS means emitting observations to named destinations (website, CWOP/MADIS, maps, banners), each with its own ID and provenance.

Back to Personal weather station guides

A logger in a backyard is a private instrument until it publishes. Publishing is not a blog post and not a screenshot. It is the act of emitting observations to a named destination, under a named identifier, with a time and units, so that someone who does not own the hardware can use the values. The historical URL /published.php existed because a personal weather station (PWS) that only updated its own homepage was incomplete as a data source. The same observations could also travel to citizen-network ingest, to a public map of the Weather Underground era, and to graphic banners other sites hot-linked.

This article is the concept of publishing and the provenance that follows from it. The station page that listed this site’s targets and embed snippets is /weather-published.php. Do not treat the two URLs as copies. Recovered text on this path is historical. Identifiers mentioned in old captures are archive tokens, not a claim that the same backyard still reports to those networks today.

Historical context

Mid-2000s station software—Weather Display and its peers—treated “upload” as a list of destinations. FTP to the operator’s website was one. A packet to the Citizen Weather Observer Program (CWOP) was another. A vendor-specific upload to a public personal-station map was a third. Image hosts produced banners that refreshed on a timer. Each destination was a different contract: different ID grammar, different cadence, different quality-control story, different audience.

The historical TNET Weather page grouped those destinations and explained, in operator language, that the Mesa station sent data outward. Recovered captures named a CWOP-style identifier and a Weather Underground-era station token, plus banner images. Those names are useful as examples of ID types. They are not live status. This rewrite does not republish old banner HTML, does not restore hot-linked graphics, and does not treat a 2000s Arizona weather-fact sidebar as science.

Publishing is a provenance event

An observation without a destination is a local log. An observation that has been published has a chain:

  1. Sensor and siting produce a reading (see station configuration as metadata).
  2. Station software applies the operator’s units, derived fields, and clocks, then writes a file or packet.
  3. Transport copies that object to a destination: FTP, HTTP, APRS-IS, a vendor API.
  4. The destination stores, quality-controls, maps, or redisplays it under its identifier.
  5. A later user retrieves a copy that may no longer match the website the operator sees.

Each hop can fail. A website can show a temperature that never reached CWOP. CWOP can hold a packet the homepage has already overwritten. A banner can cache a rain total the logger has since reset. Provenance means naming the hop you are quoting. “The station said 56 °F” is incomplete. “The station website, at this URL, at this valid time, showed 56 °F in Fahrenheit” is a citable claim. “MADIS stored a CWOP packet with this ID at this observational timestamp” is a different citable claim. Mixing them is how a map pin becomes a false official record.

NOAA’s Meteorological Assimilation Data Ingest System (MADIS) is explicit that CWOP data are stored by observational timestamp, not by the time a website happened to scrape HTML. That distinction is the whole subject of this page.

Four common publication surfaces

The operator’s website

The homepage, a current-conditions table, a networked include, and raw files such as ClientRaw are all publication. The identifier is often a domain name or a place-name. Quality control is the operator’s. Cadence is the FTP or copy timer. This surface is what visitors see and what Wayback captures. It is observed only insofar as the uploaded file still matches the logger. It is not an NWS METAR.

CWOP and MADIS

CWOP is a public–private partnership that collects volunteer surface observations, makes them available, and returns quality-control feedback to contributors. MADIS has ingested CWOP since 1 July 2001. NOAA documents those goals and the ingest path; MADIS also states that CWOP is not Weather Underground.

A CWOP identifier (often a CW plus digits for non-ham sites, or an amateur call sign) is the token that network uses. MADIS may store a related NWS ID form. Those IDs are not ICAO airport codes and not Weather Underground-era map tokens. Feedback from MADIS spatial and consistency checks is an independent look at the series. It does not make a backyard a climate-reference station, and a quiet QC period does not freeze siting: trees grow, a shed appears, a fan fails.

Weather Underground-era personal-station maps

During the years this URL was a working station page, many operators also uploaded to The Weather Underground’s personal-weather-station maps. Station IDs of the form K + state + place + sequence (for example a Mesa, Arizona token on neighboring historical pages) are map identifiers. They made a backyard findable on a public map. They were not MADIS IDs. Collapsing “I published to the map” into “NOAA ingested this” is a provenance error. MADIS’s CWOP FAQ states the programs are not associated.

Treat Weather Underground-era uploads as a historical publication class: a vendor map with its own ID, terms, and later corporate history. Do not assume a 2005 station page describes today’s PWS network, ownership, or access rules.

Graphic banners and other derived products

A banner is a derived image of already-published values. It is useful as a status chip on a forum. It is a poor archival object: the image is overwritten, the snippet on a foreign page may cache, and the visual design can hide missing units or a stale clock. Publishing a banner is still publishing, but what you have published is a graphic interpretation, not a new sensor. Neighboring historical pages that sampled banner layouts are about that graphic product, not about CWOP ingest.

Identifier grammar is part of the observation

A station that publishes widely holds several IDs at once. Honest publication names each ID with its network:

  • Website or include: place-name or URL.
  • CWOP / MADIS: packet ID and any related MADIS form (CWOP FAQ; MADIS CWOP).
  • Weather Underground-era map: the map token, if one was used.
  • Other vendor or hobby networks: whatever token that ingest issued.

Do not invent a MADIS number because a website existed. Do not quote a map ID as a METAR. Do not treat a banner filename as a station identifier. A historical HTML file keyed by a map token is a publication product of that grammar; it is still not an official climate station.

What “up to date” meant—and did not

Operators said they published “accurate up to date info.” Break that phrase.

Accurate is a siting and calibration claim. Publication cannot add accuracy the sensor did not have. A network QC flag can warn that a value disagrees with neighbors; it cannot move the thermometer.

Up to date is a cadence claim. Each destination has its own clock. A ten-minute banner refresh, a one-minute website FTP, and a CWOP packet interval are different valid times. Quote the destination’s time.

Derived fields (dew point, indices, “feels like”) may be computed by station software before upload or by the destination after ingest. Say which.

Publishing does not convert a PWS into an official warning service. Hazards and watches come from the National Weather Service and local emergency authorities.

Practical checklist for operators and later readers

If you run a station:

  • List every destination, its ID, and the date you last confirmed it still receives data.
  • Keep units consistent or label conversions as derived.
  • Record siting so a QC report is interpretable.
  • If you also send the same observations to more than one internet site, NOAA asks that MADIS support be told, because duplicate ingest is a known issue.

If you read an old “published data” page:

  • Treat named IDs as historical unless you re-verify them on the network’s current tools.
  • Do not scrape a Wayback homepage and call it MADIS.
  • Prefer MADIS/CWOP or NWS/NCEI when the claim is climatological.

Modern relevance

The destinations changed names and owners. The scientific act did not. Connection-intelligence and weather-research work still join records by identifier, time, and source. TNET’s public statement of that discipline—without treating a PWS homepage as an official ingest—is data sources, quality controls, and methodology. How TNET distinguishes observed, modelled, and derived information is how the service works. The weather-station hub lists the neighboring instrument pages.

This URL does not disclose TNET forecast internals, does not restore old banners, and does not operate the historical backyard as a live showcase.

Sources