The PropView screenshot used in the article shows the critical frequencies but not the open bands. This is a view is one might choose when trying to better understand HF propagation, but not when using PropView for its primary purpose: to identify the best bands and times to work a sought-after DX station. A PropView forecast showing short-path openings between my Boston-area QTH and the forthcoming DXpedition to the Laccadive Islands is shown here; the thicker the line, the more probable the opening.

The review says, "Enter latitude and longitude of both ends of the circuit, the antenna take-off angle, power, noise level, SFI and desired availability." It fails to mention that PropView automatically interoperates with DXView (another member of the DXLab Suite), allowing the user to specify the location of the DX end of the circuit by entering a call sign, a DXCC prefix, an IOTA tag, or a grid square -- or by simply clicking a location on DXView's world map. DXView further augments PropView by using the geomagnetic K-index to visually depict interaction between a signal's path and the auroral ovals. Interoperation with complementary applications was discussed in reviews of other applications, but omitted for PropView.

The review fails to mention PropView's NCDXF/IARU beacon monitoring capability, which includes the ability to automatically QSY one's transceiver (via Commander, another DXLab application) to monitor a specified set of beacon/band combinations. By comparing the forecast for a relevant beacon with received signal levels, one can calibrate the propagation forecasts for nearby locations.