If you create a new override for JD1BMM, then when you set the override's DXCC entity to Minami Torishima, SpotCollector or DXView will automatically populate the other components of the override: CQ zone, ITU zone, IOTA tag, and grid square. Its the grid square that SpotCollector uses to compute the heading (bearing, azimuth) from your QTH.
I suspect that you created your JD1BMM override before SpotCollector and DXView were updated to allow the specification of CQ and ITU zones, IOTA tags, and grid squares in overrides. As a result, your JD1BMM override does not specify a grid square, which is why SpotCollector isn't computing a heading for JD1BMM spot database entries.
To fully populate your JD1BMM override, its probably quickest to simply delete it and re-create it.
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
--- In dxlab@..., "aa6yq" <aa6yq@...> wrote:
Have you created an entity override for JD1BMM that specifies Minami Torishima? Does this override specify a grid square?
73,
Dave, AA6YQ
--- In dxlab@..., "gu0sup" <pcooper@> wrote:
Hi all,
I've just noticed that whenever a spot for JD1BMM comes through the cluster, there is NO heading noted.
There is a heading for all other calls I've seen, but not for this particular call.
I opened DXV, and if you enter JD1BMM, then click GO, it does not show any LAT/LON, SP DX, cont or grid, and no CQ or ITU zone.
I clicked on DXCC, and all the data "appears" to be there.
Also, if you enter JD1OMM (for Ogasawara), then all info appears correctly, and if you have the DXCC database open, it goes to the JD1-O entry.
BUT...... if you do the same for JD1BMM, it does NOT go to the entry for Minami Torishima.
Is this an oddity? Or is it something I have done??
BTW....... DXK and SC both know I have not worked it.
73 de Phil GU0SUP
