| ← | Move left |
| → | Move right |
| ↑ | Move up |
| ↓ | Move down |
| + | Zoom in |
| - | Zoom out |
| Home | Jump left by 75% |
| End | Jump right by 75% |
| Page Up | Jump up by 75% |
| Page Down | Jump down by 75% |
Saved on the map
Shared across the whole team
No saved reports yet
Analyze a location, then use "Report readings here" to record what your meter showed. That is what drops a pin.
New report
This location
Sign in to save a report
Reports are shared with your team and feed the prediction model, so they have to come from a known account. Analysis works without one.
How the number is made
Every term the engine applies
margin = signal_at_tuner − fcc_threshold − interference
Margin is dB above the FCC minimum field strength. 0 is exactly the minimum. Expand any station and open “show calculation” to see every term that produced it.
Two thresholds, not one
The FCC figure is its noise-limited service contour (47 CFR 73.622(e)) - the line its own reception map draws coverage with. Ours sits 10–19 dB above it, because the contour marks where a rooftop antenna on a clear path can decode a signal, not where a customer is happy with the picture. Colours follow the FCC comparison; every station row shows both numbers.
Receive system, vs the OET-69 reference
Rooftop is the reference, so both its figures are 0. Height above the reference (6 / 15 / 30 ft) adds ~6 dB per doubling.
Transmitter data
FCC TV Query (transition.fcc.gov/fcc-bin/tvq) - public domain
What is not modelled
Building materials, trees, roof geometry, antenna aim, feedline length, preamps, multipath and co-channel interference. Terrain is sampled from elevation data along each path; where that is unavailable a coarse estimate is used and the station reports 0 m obstruction, which is a guess rather than a measurement.
Predictions are estimates. File what your meter actually shows with “Report readings here” - those readings are what the model is measured against.
Report a problem
Goes straight to the DROP board
Sign in to send a report
Reports go onto a shared tracker, so they have to come from a known account - otherwise anyone with the address could flood it.