User guide: how to read this site
This guide walks through every section of the site and explains what it shows and how to read it. Two things matter everywhere: what kind of number you are looking at — MEASURED, FORECAST, MODELLED or DERIVED — and how fresh it is. Start on the Home page, then open the sections below as you need them.
- The Home page
- My Station
- How often does this update?
- Bands
- Map
- Paths
- Forecast
- Alerts
- QO-100 page
- Source Status
- How to interpret conditions in practice
- Where the numbers come from
Every term used on the site is defined in the glossary; here the focus is on how the pieces fit together.
Quick links: Home · Station · How often it updates · Bands · Map · Paths · Forecast · Alerts · QO-100 · Source Status · Glossary
Prefer a document you can keep, print or share? Download the beta guide as a PDF.
The 30-second version
- What it is — a free HF propagation outlook for South African amateurs.
- Where to start — Home: the Outlook plus the SFI/Kp tiles.
- How to pick a band — Bands: use one rated GOOD or better.
- How far it will go — Paths: a band below the MUF with high reliability.
- How to plan ahead — Forecast: the next 24–48 hours.
- The trust rule — MEASURED > FORECAST > MODELLED > DERIVED, and check freshness first.
The Home page
DERIVEDThe Home page answers “should I get on the radio now?” It combines the current conditions into one big rating — the HF Outlook — and shows the measurements behind it.
Your station line and Refresh now
The banner keeps two things personal. The line under the buttons shows your own saved station — for example “Your station: ZS1ABC · JF96 · ZS1 Western Cape · nearest model: Cape Town” — with a change link to the Station page. If you have not set a station, it says conditions are shown for Cape Town and invites you to set yours. It replaces the old static “Cape Town reference” note.
Next to View Band Conditions there is a Refresh now button (the Install button sits beside it when the app can be installed). It asks the server to recalculate the path model for your saved area instead of waiting for the page's own 5-minute poll; if you have not set a station it recalculates the Cape Town reference tables. The server allows one recalculation every 30 minutes, and the page shows progress and reloads the data when the run finishes — see How often does this update?.
HF Outlook
The big rating is DERIVED by this project from the current solar and geomagnetic state plus the time of day. It is one of five levels, matching the band ratings:
| Rating | What it means |
|---|---|
| EXCELLENT | Conditions are strongly supported right now; expect strong, reliable signals and good DX potential. |
| GOOD | Usable and dependable, with normal fading. Good chance of contacts. |
| FAIR | Marginal. Signals may be weak, fluttery or short-lived; openings can be brief. |
| POOR | Largely unsupported. Occasional weak openings possible. |
| CLOSED | No useful propagation expected at this time. |
DERIVED means a summary calculation on top of other data — not an official forecast, and not a guarantee for your exact antenna or location.
Space Weather tiles
Four quick numbers, all MEASURED by NOAA:
- SFI
- The solar flux index (10.7 cm radio flux) — a proxy for solar activity and ionisation. Higher generally supports higher HF bands.
- Kp
- The planetary K index (0–9) — a measure of geomagnetic disturbance. Quiet is 0–3, unsettled around 4, storm from 5 upward.
- Sunspots
- The observed sunspot number — the long-standing indicator of the solar cycle. More spots, more ionisation, better high bands.
- X-ray
- The background X-ray flux class (A, B, C, M, X). C-class flares can cause minor fadeouts; M and X can cause significant shortwave fadeouts on the sunlit side.
The small ↑ / ↓ under each tile shows how the value has moved since the previous reading — rising or falling.
Key numbers at a glance
| Indicator | Rough guide |
|---|---|
| SFI | Below 100 is low, 100–150 is normal, above 150 is high. |
| Kp | 0–3 quiet, around 4 unsettled, 5+ storm. |
| Sunspots | Higher = more ionisation, better high bands. |
| X-ray | C-class: minor fadeouts; M and X: significant fadeouts on the sunlit side. |
Best Bands Now
A compact list of the bands worth trying right now, each with the same five ratings. Like the Outlook it is DERIVED — a starting point, not a promise.
Alert strip
When NOAA has issued an alert or warning, a strip appears across the top of the page. It flags something unusual — a flare, a storm — and points to the Alerts section for the detail.
Tip: start here, then open the sections below. The Outlook tells you whether, the Bands tell you where, and the Paths tell you how far.
Set your station on the Station page and the Home outlook, best bands and sun times become specific to your own square — see My Station below.
My Station
YOUR LOCATIONOn the Station page you can tell the site where you are, so the local figures are worked out for your own square instead of an assumed one. There is nothing to install and nothing to sign up for.
- Your callsign (optional) — for example ZS1ABC. It is checked for a valid format, and if the ZS call area disagrees with the locator you entered you get a soft warning, not an error.
- Your Maidenhead locator — four characters, for example JF96. Four or six characters are accepted; only the first four are used. South African squares only: the site checks your locator against its list of South African squares and will not accept one outside the country.
Open the page from the Station item in the menu, from the My Station card on the Home page, or by clicking the small chip in the header (for example JF96 · ZS1) that appears on every live page.
Stored in this browser only. Your callsign and locator are kept in this browser — never uploaded and never sent to the server. Nothing about your station leaves your device.
For your square the page shows five things:
- Your square
- The locator, its centre latitude and longitude, the ZS call area and province, and the nearest model anchor with the distance to it.
- Sun and grey line
- Sunrise, sunset and solar noon in both SAST and UTC, the current state (DAYLIGHT, TWILIGHT or NIGHT), and whether the grey line is over your square. This is exact for every square.
- Bands rated for your location
- The same band-rating model the server uses, run in your browser with your own latitude, so it can differ slightly from the Cape Town table.
- Forecast for your location
- NOAA's predicted F10.7 and the R/S/G scales with a note on the local effect, plus tonight's hours of darkness in UTC for your square.
- Paths from your anchor
- The DX and domestic path tables computed for the nearest of the six anchors, with the distance from your square to that anchor shown.
Its path tables follow the same 30 DX destinations (and six domestic call areas) as the Paths page, resolved through your nearest anchor.
Tip: local conditions — sun times, the grey line and the band ratings — are calculated exactly for your own square. Only the path predictions come from your nearest anchor, which can be up to about 600 km away; six anchors (Cape Town, Gqeberha, Kimberley, Bloemfontein, Durban and Johannesburg) were chosen so that no operator is further than that. All of this runs in your browser and costs the server nothing.
To change your location, edit the locator — everything recalculates at once for the new square. To remove your details, press Forget, which clears them from the browser.
How often does this update?
CADENCEThe numbers change on a schedule, not on demand. Measured data and the published snapshot are refreshed every 10 minutes; the path tables are recomputed far less often, because each run costs tens of seconds of CPU. This is the honest cadence:
| What | How often | Note |
|---|---|---|
| NOAA data and the published snapshot | Every 10 minutes | The hfsa-collector.timer job; when the model cache is still valid a collector run costs about 2.5 s. |
| ITU-R P.533 path model for Cape Town | About once an hour | The cache is reused only within the same UTC hour; each recompute costs about 58 s of CPU. |
| Per-anchor models for the six locator groups | Every 3 hours | The hfsa-anchors.timer job; 5 anchors × ~59 s is about 5 minutes of CPU. |
| Real-world WSPR validation | Every 6 hours | Predictions are compared with actual WSPR spots; it re-runs P.533 for the past 24 hours. |
| The page itself | Snapshot every 5 minutes; clock every 60 seconds | It re-polls the published snapshot and re-syncs its clock automatically in the background. |
So measured data can be at most about 10 minutes old. The Cape Town path tables are at most about an hour old, and the per-anchor path tables at most about 3 hours.
Refresh now
On the Home page there is a Refresh now button, next to View Band Conditions. It now genuinely asks the server to recalculate, rather than only re-pulling the published snapshot. When you press it the browser sends a request; the server enforces a 30-minute limit, then the path model runs for your saved area, and the page shows progress and reloads the data when it finishes. If you have not set a station, it recalculates the Cape Town reference tables instead. The button reads Recalculating… while the run is in progress and Refresh in N min during the cooldown.
If the recalculate endpoint is not available, the button falls back silently to reloading the latest published snapshot, so the page never breaks. The cooldown is enforced by the server, which keeps a stuck finger off the refresh key.
Bands
DERIVEDThe Bands page lists every amateur HF band with its frequency range and a current rating.
- Each row shows the band (for example 20 m), its frequency range (14.000–14.350 MHz) and a rating.
- The rating is DERIVED from the current solar and geomagnetic state and the time of day.
- What each rating suggests is spelled out in the glossary — from EXCELLENT (strong, reliable) down to CLOSED (no useful propagation expected).
Tip: pick a band here, then check the Paths table to see how far it will carry you.
Map
LIVE LAYERSThe global map is drawn live from current data. The day/night geometry is exact; the paths drawn on it are modelled. It is a full-width page: on a desktop screen the canvas fills the window, so the whole terminator and the long DX paths fit at once.
- Daylight / night shading
- The two halves of the Earth behave very differently:
- The dark area is where the Sun is below the horizon right now.
- The D layer absorbs the lower bands in daylight.
- The F layer supports the higher frequencies.
- Grey line
- The twilight band along the day/night boundary. Paths that run along it can enjoy unusually good DX, because both ends sit in near-darkness while the D layer has already weakened. The map draws it explicitly.
- Subsolar point
- The single point where the Sun is directly overhead at that moment; the whole day/night pattern follows from it.
- Path colours
- Each drawn path is coloured by its modelled reliability: green is dependable, amber is marginal, red is unlikely. The legend under the map repeats this key.
A modelled MUF heat overlay (ITU-R P.533) is planned as a later phase.
Paths
MODELLEDThe Paths table predicts circuits from Cape Town for 6 South African call areas plus 30 DX destinations — including Australia, Japan, the US East and West Coasts, Western Europe, the UK, Brazil, Argentina, India, China, Kenya, Mauritius and the Falklands, among others. Every destination is modelled independently for the month, hour and sunspot number, so each row is its own calculation rather than an interpolation from a neighbour.
- MUF in practice
- The Maximum Usable Frequency is the ceiling for that path at that time. The band you plan to use must sit below the MUF: if the MUF is below your band, signals pass through the ionosphere into space instead of returning to Earth.
- Reliability
- A percentage estimate of how often the circuit would meet a usable signal-to-noise level. Higher is more dependable — a statistical figure from a model, not a measurement.
- Two models
- Every path is computed twice: with the international standard ITU-R P.533 method, and again with VOACAP as an independent cross-check. Where the two disagree, the disagreement is shown rather than hidden.
These figures are MODELLED, not measured — a calculation of the ionosphere over your antenna, not an observation of it. See the glossary.
Tip: look for your destination with a band below the MUF and a high reliability figure.
Forecast
NOAA FORECASTEverything here is FORECAST — NOAA's prediction of the coming hours and days, not a measurement.
- Kp chart
- The predicted planetary K index for the next 48 hours, plotted on the 0–9 scale. Times are UTC. The bars are colour coded from quiet (green) through unsettled (amber) to storm (red); Kp 5 is the storm threshold.
- Predicted F10.7
- The expected solar flux over the coming days — a hint of whether the higher bands will stay supported.
R / S / G scales
| Scale | What it forecasts |
|---|---|
| R | Radio blackouts |
| S | Solar radiation storms |
| G | Geomagnetic storms |
Each scale runs 1–5, minor to extreme. NOAA issues a scale only when an event is expected: for R and S the scale field is usually null (NOAA sends a probability instead) and G is explicitly 0. The site used to print that null as 0, so every quiet day read “R 0 · S 0 · G 0” — a display bug, not a data fault.
On a quiet day you now see a single QUIET marker instead. When there is an event, the coloured R1–R5 / S1–S5 / G1–G5 chips appear as before, and NOAA's probability is shown in the tooltip (for example “chance 10%”). Quiet days are normal, especially at low solar activity — they are not a sign that something is broken.
Tip: use this for planning — what you will find on the air tonight or tomorrow — rather than for what is happening this minute.
Alerts
NOAANOAA issues coded bulletins when space weather crosses a threshold. This site decodes them into plain language.
- Alert / warning / watch
- An alert means the threshold has been reached — the most immediate. A warning means conditions are expected or in progress. A watch means conditions are possible.
- Severity chips
- Each item carries a chip such as R1 or G2 — the event's position on the R/S/G scales, colour coded from minor (green) to extreme (red).
- Message codes
- The original NOAA product code, for example ALTK04, is shown too, so you can look up the raw bulletin if you want it.
When an alert shows, expect consequences on the air:
- R events — shortwave fadeouts on the sunlit side.
- G events — disturbed conditions with a depressed MUF, hurting high-latitude paths most.
Re-check the Forecast, favour the lower bands, and expect the unexpected.
QO-100 page
NOT HFThe QO-100 page covers the geostationary amateur satellite, which sits far above the ionosphere — so none of the HF conditions on this site apply to it. There is no MUF, no D-layer absorption, no grey line and no geomagnetic depression.
- Pointing — fixed azimuth and elevation from Cape Town. Because the satellite is geostationary, once your dish is aimed it stays aimed.
- Solar outage — the window, twice a year, when the Sun lines up behind the satellite and can wash out the downlink for a few minutes a day over several days.
- Live monitors — links to external activity monitors, since there is no public API that reports the transponder's state.
Only weather along your line of sight — heavy rain (rain fade) — affects it, not HF propagation.
Source Status
This panel tells you how much to trust what you are reading. Each row shows:
- the source name — which dataset it is (solar flux, Kp, alerts, and so on);
- its state — LIVE (fresh, within about 20 minutes), CACHED (older than usual, or the last good snapshot while the provider is unreachable), STALE (past the threshold — still shown, but not current) or UNAVAILABLE (no valid data);
- its age in minutes — how long since the value was observed.
- Time base
- The top row shows the site clock, disciplined by GPS via NTP. Ages and timestamps are measured against that accurate standard, not your device's clock.
- Cross-check
- A separate line compares the two propagation models (ITU-R P.533 and VOACAP) and reports how often they agree — a useful confidence signal for the path tables.
If something is STALE, do not trust the numbers it feeds — treat them as a rough picture only and check back later. The full explanation of the states is in the glossary.
How to interpret conditions in practice
A short routine that turns the site into a working decision:
- Set your station first (if you have not already) on the Station page, then check the Outlook and the Kp/SFI tiles on the Home page. Is it worth switching the radio on at all? Setting your station makes these local to your square.
- Pick a band from the Bands list — one rated GOOD or better if you want an easy contact.
- Check the Paths table for your destination: your band must sit below the MUF, and a high reliability figure means a dependable circuit.
- Look at the map for the grey line — if it is near you or your target, DX windows may be open even when the ratings are modest.
- Watch the forecast for the next 24–48 hours — a rising Kp or a G-scale event tomorrow may change tonight's plan.
The golden rule: every number is labelled MEASURED / FORECAST / MODELLED / DERIVED. Trust measured more than forecast, forecast more than modelled, and modelled more than derived — and always check the freshness state first. See the classification and freshness entries in the glossary.
Where the numbers come from
- Measurements and forecasts come from NOAA SWPC — U.S. Government data in the public domain.
- Path predictions come from the ITU-R P.533 international standard method, with VOACAP run as an independent cross-check.
- The clock behind every timestamp and age is GPS-disciplined via NTP.
- Each source, its type and its reuse rights are recorded on the Data Sources page.