Differences between revisions 4 and 5
Revision 4 as of 2006-07-04 04:10:24
Size: 1269
Editor: AA6YQ
Comment:
Revision 5 as of 2008-04-01 04:50:43
Size: 1337
Editor: AA6YQ
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:


 * [:CreateEntityOverride: Dealing with Ambiguous Callsigns]

Obtaining DX Information from a Callsign

  1. in DXView's Main window, type the Callsign into the Search panel and strike the Enter key or click the Go button

  2. DXView displays the name of the Callsign's DXCC entity, and an approximate location whose accuracy depends on the use of callsign-based districts within that DXCC entity; this location is characterized by

    • a latitude and longitude

    • a Maidenhead grid square

    • the short path distance (SP DX) to your QTH

    • a blue dot on the World Map (click the World button in the Main window's Map panel to make the World Map visible)

    • short and long path Headings for directive antennas

  3. if the callsign's DXCC entity fits entirely within an IOTA tag, that IOTA tag is displayed

  4. if the callsign's DXCC entity fits entirely within an CQ Zone, that CQ zone is displayed

  5. if the callsign's DXCC entity fits entirely within an ITU zone, that ITU zone tag is displayed

  6. [:CreateEntityOverride: Dealing with Ambiguous Callsigns]


[http://groups.yahoo.com/group/dxlab/post Post a question or suggestion on the DXLab reflector]

[:DxInfo:Getting Started with DX Information]

[:GettingStarted:Getting Started with DXLab]

DXInfoCallsign (last edited 2018-07-12 16:56:37 by AA6YQ)