A Cumulus webcam hub is an index: which cameras exist, how often they capture, and what privacy rule covers the view. It is the table of contents for stills, not the stills themselves. Visitors who bookmarked /webcam wanted that directory. They did not want a how-to on FTP, an overlay experiment, or a single named display script.
This URL is that hub. No live camera is attached. No historical frame is replayed. The capture–stamp–upload–page pipeline is a methods article. Experimental overlays are about burned-in clocks. Named IDs such as SOMT1 are display identifiers. Those pages stay distinct. /webcam stays the catalog and the policy.
Historical context
Personal weather sites added cameras because numbers without a sky felt incomplete. The first public object was often a single current.jpg on the home page. The second camera, or a yard view plus a sky view, forced a directory. Operators created /webcam, /webcams, or a PHP index that listed thumbnails. Incoming links copied the hub URL because it was the menu item.
On a software-citation host such as cumulus.tnetweather.com, the hub also had to refuse two temptations: treating the camera as a live official sky observation, and treating the hub as a CDN for other people’s streams. The original index, thumbnails, and scripts are not rehosted. What the path can still teach is how to list cameras without pretending they are instruments they are not.
What the hub must list
Each row in the index is a camera record, not a weather report.
| Field | Role | |---|---| | Camera ID | Stable token used in URLs and filenames | | View in one line | A verifiable description (“north sky above the gauge”), or “view not recorded” | | Interval | Capture cadence in minutes | | Last-frame rule | When the still is stale relative to that cadence | | Status | Active, retired, missing archive, or never recovered | | Privacy note | Whether the view can include people, windows, or a road |
The hub reuses station identity from the info card: same location line, same timezone. A camera caption that names a different city than /info is a forked station.
Do not put live temperatures in the hub table. Temperature is a logger series. If you show a number next to a thumbnail, you are implying the frame and the air were simultaneous. That coincidence is an overlay problem and a clock-sync problem; it is not a directory problem. Link to the conditions template if visitors want “now.”
Do not expand SOMT1 or any other token into a place name or a scene. The named-display article is the identifier pattern. The hub may list SOMT1 as an ID. It must not invent what the lens saw.
Interval is a hub policy, not a camera-brand feature
Interval belongs on the hub because visitors judge “live” from the index page. A thumbnail labeled “current” that refreshes in the browser every two seconds while the camera writes a file every fifteen minutes is a false live view. State the cadence once per camera, in text.
A still every 5, 10, or 15 minutes is a time-lapse diary. It is not video. The hub should say “still, every n minutes,” not “live cam,” not “streaming.” If two cameras use different cadences, the table must not share one footer interval.
Stale rules belong next to interval. If the file is older than one interval plus a small tolerance, the hub should mark that row stale or hide the thumbnail rather than show yesterday’s sky as a directory tile. A broken image is better than a silent week-old frame in an index that implies currency.
Night and winter do not change the interval policy. They change what the frame can mean (qualitative darkness, snow on a known object). That interpretation is not the hub’s job beyond a one-line view description.
Privacy is a hub rule because the index is public
A weather camera is still a camera. The hub is where you publish the rule, because the index is what other sites scrape and what guests send to relatives.
Practical limits that belong in hub prose, not in a buried FAQ:
- Aim at sky, instruments, or a horizon landmark you can name as weather context.
- Do not list a camera whose intended view is a neighbor’s yard, windows, or identifiable faces.
- Do not stream audio.
- Retention: if the hub links an archive, say how long frames are kept. An unbounded public archive of a street is a different product from a 24-hour sky diary.
- Third-party streams: do not ingest someone else’s webcam into your ID namespace and present it as your station.
These are operator ethics. This rewrite does not describe any historical field of view. It does not claim the original cameras followed the rule. It states the rule the hub should have carried.
If a camera is retired, keep the ID on the hub with status “retired” rather than deleting the row. Incoming links to a child display URL still need the index to say the ID existed. Deleting the row is how identifiers get reused for a new mount—the camera analog of moving a thermometer and keeping the station code.
What the hub is not
It is not a pipeline diagram. Capture, optional stamp, upload, and page are how it is done.
It is not an overlay laboratory. Clocks burned into JPEGs are experimental overlays.
It is not a live feed. This URL does not proxy a camera, does not refresh a JPEG, and does not restore Mesa or SOMT1 imagery.
It is not an official sky observation. WMO cloud amount and type are trained or instrumented estimates. A consumer webcam with automatic exposure is a qualitative diary at best.
It is not a warning product. Lightning in a frame, a wall cloud, or flooding on a drive is not an NWS Watch, Warning, or Advisory. Direct hazard decisions to weather.gov or the local authority.
Practical checklist
- Index lists ID, one-line view or “unknown,” interval, stale rule, status, privacy.
- Station location and timezone match
/info. - No “live” label on a still; cadence is in text.
- Child display URLs are linked by ID, not by guessed place names.
- Retired IDs remain listed; IDs are never reused for a new mount.
- No autoplay, no third-party stream wrapped as a station camera.
- This URL serves HTML policy, not image bytes.
Modern relevance
Network cameras and browser <video> tags made hubs look old. The catalog problem did not go away. A site with four RTSP streams and no public table of IDs, intervals, and privacy is worse than a 2000s thumbnail index, because the streams are easier to hotlink and harder to caption. Operators who publish sky stills next to Cumulus MX JSON still owe the same directory.
TNET does not operate webcams at this path. Anyone who followed /webcam for a picture gets the index rules that picture required.
TNET research bridge
A camera hub is provenance for visual observations: which instrument (the camera ID), which place, which time system. That is the same discipline TNET applies to source identity in data sources, quality controls, and methodology. How observed information is distinguished from modelled products is how the service works.
The weather-station hub groups this catalog with other instrument pages. The Cumulus hub lists software-side neighbors.
Sources
- WMO: Instruments and Methods of Observation (cloud observing practice; a webcam is not a substitute)
- NWS
- TNET: data sources and methodology
- TNET: how the service works
- TNET weather-station hub