A shared current-conditions include is a data product that happens to be rendered as HTML. When the HTML looks dated, the temptation is to “redesign the network page.” The scientific risk is that a restyle silently becomes a new schema: a dropped column, a renamed field, a missing timestamp. The historical URL /SWN_new/SWN-page.php is the document of that risk. The _new directory is a parallel copy of the networked include whose job was presentation—markup, CSS, layout—not a new set of weather instruments.
This address is distinct from /SWN/SWN-page.php, which explains the include’s data contract (identifier, time, units). Here the subject is the restyle itself: why operators kept a second path, what may change in a refresh, and what must not. Recovered dumps of this URL are historical. They are not current Mesa weather. Observation numbers from those tables are not reprinted here as a live report.
Historical context
Personal-weather sites of that era shipped PHP fragments the way later teams ship design systems. A directory named SWN held the production include. A sibling directory named SWN_new held a candidate replacement. That naming is ordinary web operations: keep the old fragment answering requests while a new stylesheet, table layout, or accessibility pass is tested at a second URL.
The path token SWN still names the same kind of module: a networked current-conditions include shared across partner sites. This article does not invent an official organization behind the letters. Recovered dumps described a southwestern affiliation of personal weather websites; that historical labeling is not treated here as a live, independently verified mesonet. The _new suffix is the claim this URL can support: a redesigned include, not a second network.
A dated member roster on a recovered capture of this path carried an August 2009 stamp. That is a snapshot of who was listed and how the fragment looked. It is not a reason to treat the restyle as today’s weather, and it is not proof of a neat linear succession from “old” to “new” to “done.” Production and sandbox includes often coexist for years.
Why a restyle path exists
Three pressures drive a parallel HTML/CSS refresh of a conditions include.
Browsers change. Tables that sorted on click, spacer GIFs, and inline font tags rot. A refresh can move presentation into CSS, add a readable heading hierarchy, and stop relying on layout that only one browser family rendered.
The include is reused. Partner sites embed the fragment. If you overwrite the production path with a layout that is fifty pixels wider, you break every host that wrapped it in a sidebar. A _new URL lets members opt in.
Accessibility and semantics improve. A table of stations is still a table: headers should name fields, units should sit in those headers, and “Offline” should be text, not a blank cell the color of the background. Those are presentation and markup choices. They do not require new sensors.
None of those pressures is a license to change what a row means. The observation fields—who, when, which variable, which unit—are the contract described on the production include article. A restyle that preserves them is a restyle. A restyle that drops the clock from every row is a data regression wearing new CSS.
Presentation versus schema
Separate the layers.
| Layer | May change in _new | Must not change without a versioned contract |
|---|---|---|
| Colors, fonts, spacing, map chrome | Yes | — |
| Column order on screen, responsive stacking | Yes, if headers still name fields | Silent reorder with no headers |
| Which fields are visible | Risky: hiding is not deleting, but a partner may have parsed the HTML | Removing a field from the harvest |
| Field names, units, ID, timestamp | No | A new schema needs a new documented version |
| Derived badges (conditions word, empirical fire index) | Labels and styling | Recalculating with a different formula while keeping the old name |
HTML is a terrible API, but for years it was the API. Partner sites, scrapers, and even the include’s own sort-by-column script keyed on column position. That is why a visual refresh is an interoperability event. If a consumer indexed “column 4 = humidity,” inserting a dew-point column in the middle is not a cosmetic change. It is a broken decode.
The disciplined restyle therefore freezes the field set and changes only how those fields are painted. If a column must be added or removed, the include’s documentation—and any version token in the path or a comment header—should say so. /SWN_new/ is already a version token. Treat it that way.
What a recovered “new” table still teaches
Without reprinting numbers, the structure of a restyled include is still evidence of intent. A typical row still had to show a station identity, a temperature, humidity, wind, rain, and pressure, often with a conditions label and a pressure-trend word. Some presentations also showed an empirical fire-danger category.
Two restyle failures show up even in archive HTML:
Thinner tables look cleaner and hide the clock. If the production include showed a last-update time and the restyle does not, the prettier page is the worse observation product. Freshness is not decoration. It is how a reader knows the row is not last week’s harvest.
Derived columns get visual priority. A colored fire-danger chip or a sky icon draws the eye first. Those values are derived or categorical. They must not outrank the timestamp and the units. Official fire-weather and severe-weather statements come from the National Weather Service and local authorities, not from a hobby index painted in red.
A restyle can also improve honesty: “Offline” as a first-class state, units in headers, and a collection-window note for the harvest. Those are presentation choices that serve the contract.
Distinct from the production include and from the root alias
Keep the three URLs straight.
/SWN/SWN-page.phpis the namespaced include and the place to teach the data contract.- This URL is the parallel restyle: HTML and CSS, same scientific fields.
/swn-page.phpis the root alias—the short path an embed orincludeoften used.
Do not merge them. A backlink to /SWN_new/ was a link to a candidate layout, not a link to a different mesonet, and not a link to a live Mesa meter. Station configuration still sits underneath every row: siting and sensor metadata do not change because the table got a new stylesheet.
A restyle checklist that protects observations
Before a conditions include is restyled, freeze a field list in writing: identifier, observation or harvest time (with zone), temperature, humidity, wind, rain, pressure, and any derived columns, each with a unit. Then:
- Change CSS and markup only, and re-test any partner embed width.
- Keep machine-readable headers on every numeric column.
- Do not remove the timestamp to “simplify.”
- If a derived badge stays, label it as derived.
- If the harvest cannot reach a member, publish offline—do not freeze the last pretty number.
- If the field list must change, bump the path or a version note; do not silently edit production.
That checklist is the whole scientific content of _new. The weather did not change. The HTML did.
Modern relevance
Widgets, Web Components, and JSON APIs are restyles of the same problem. A redesigned card that omits units or time is the _new failure in a new skin. Schema versioning (a documented field list, a version field in the payload) is how a visual refresh stays honest.
TNET distinguishes observed, modelled, and derived information in how the service works. That distinction is the right next step after a restyle conversation: presentation is not a new observation. Provenance and freshness for public weather records used in later research are stated in data sources, quality controls, and methodology. The weather-station hub collects the related instrument pages.
This URL is not a live include, not a download of historical CSS, and not a claim that TNET operates a regional station network today.
Sources
- TNET, How the service works
- TNET, Data sources, quality controls, and methodology
- NOAA / NCEP MADIS, Citizen Weather Observer Program: madis.ncep.noaa.gov/madis_cwop.shtml