In reply to G3XQE:
I have just worked G4WTB/P on 40m CW who had alerted for G/CE-006.
Worked but not in a SOTA sense. Try and log it.
A reverse beacon spot was also present with the same summit reference.
I double clicked on the Summit Reference link and it brought up
Aconbury Hill never before activated.
After working him and he had gone qrt I came to log the contact only
to get the message not a “valid summit on the date logged”.
Excellent, that bit of the database is working. You’re probably not in agreement.
Sure enough when checking the summits list I found that the list of CE
summits only goes up to CE-005.
How was it possible that the alert and spot could be generated for a
non valid summit which also seemed to have a summit data page ???
Well… at one time the summit was valid. That means there was once a CE-006. I’m not sure but probably SOTAwatch checks the summit you spot/alert is in its lists of summits but doesn’t check the valid to date.
Was this summit perhaps deleted some time in the past ???
It was. If you check the ARM for G you find this entry
"09-May-02 1.5 CE-006 deleted and replaced with
WB-024 (fixing initial allocation error)
If in doubt then only the database is considered to be correct (www.sotadata.org.uk).
Someone must have been using an 11 year old list. It’s one of the reasons that copying the data from SOTA websites is considered bad IF you don’t update your copies at least once/month. Copying the data is fine but if you let others make use of that data then you must keep it up to date or this kind of error will arise.
I’m not sure if you can claim WB-024 or not Ken.
EDIT: Ah, Tom seems to think you can.