Well I would like to know as I go
One of those is Washington DC Terry. Did you tell me that was something you were going to change? I am running that test copy you sent me.
Rich
Grid locator query
Re: Grid locator query
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Grid locator query
Just noticed Log4OM is not allowing me to update the gridsquare by opening the record and changing it. I have clicked update, save and exit and the old center of the earth grid stays.
If I search for the record, detach grid and manually type it into the table it works.
If I search for the record, detach grid and manually type it into the table it works.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Grid locator query
Even after updating the Grid Squares the map still points back to same location off Africa
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Grid locator query
This issue with K9FD is caused because it is listed in the Clublog exception file which does not contain a grid reference
Here is one of the Clublog exceptions for this call:
<ExceptionRecord>
<End xsi:nil="true" />
<Start>2010-07-15T01:00:00+01:00</Start>
<Latitude>21.3</Latitude>
<Longitude>-157.9</Longitude>
<Cont>OC</Cont>
<Ituz>0</Ituz>
<Cqz>31</Cqz>
<Adif>110</Adif>
<Entity>HAWAII</Entity>
<Call>K9FD</Call>
So your QRZ lookup which contains the correct Grid reference is being overridden by the Clublog data and because that does not provide the reference Log4OM is using the 'Centre of the world' locator.
Try turning off the Clublog exception check in the Log4OM options/settings 1 tab and then try entering the call again for lookup
I need to check with Lele to see if we can use the QRZ locator when the call exists in the Clublog exception file or perhaps calculate the locator from the Lat/Lon provided in the Clublog file.
Here is one of the Clublog exceptions for this call:
<ExceptionRecord>
<End xsi:nil="true" />
<Start>2010-07-15T01:00:00+01:00</Start>
<Latitude>21.3</Latitude>
<Longitude>-157.9</Longitude>
<Cont>OC</Cont>
<Ituz>0</Ituz>
<Cqz>31</Cqz>
<Adif>110</Adif>
<Entity>HAWAII</Entity>
<Call>K9FD</Call>
So your QRZ lookup which contains the correct Grid reference is being overridden by the Clublog data and because that does not provide the reference Log4OM is using the 'Centre of the world' locator.
Try turning off the Clublog exception check in the Log4OM options/settings 1 tab and then try entering the call again for lookup
I need to check with Lele to see if we can use the QRZ locator when the call exists in the Clublog exception file or perhaps calculate the locator from the Lat/Lon provided in the Clublog file.
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Grid locator query
We can do everything... But when an exception exists there is the concrete possibility that the qrz locator is not correct. Assuming that possibility is 50% the right choice is to not trust the qrz information, as a wrong locator is harder to identify at a later time, versus a default evidently wrong locator that require some investigations a software cannot do
Daniele Pistollato - IW3HMH
Re: Grid locator query
In my opinion, using two sources for a single data point is not a good idea. Which is the correct one? And, both could be wrong.
If you one DB for information at any given time, it's easier to find an issue.
ClubLog needs to add this field if it's not there now.
If you one DB for information at any given time, it's easier to find an issue.
ClubLog needs to add this field if it's not there now.
K7PT-Chuck "#1 Top of the Honor Roll"
Re: Grid locator query
Yes, turning that off fixed the map issue. The path is pointing to Hawaii now.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team