On Tue, May 09, 2000 at 05:21:32PM +0000, Wilbert Knol wrote:
> The sub-entities thing would be useful, but it doesn't always work. E.g. in the
> US I understand the prefix no longer indicates the State. The same is true in
> ZL... a ZL4 *could* now be in ZL1. Perhaps an additional field (boolean) to
> indicate the sub-entity is meaningful... I will have a look tonight to see how
> CT handles that.
OK. I've heard that the US is quite a mess. However, I think that the
prefix lookup would just offer a default prefix, and that we could override
it on a QSO-by-QSO basis (or callsign-by-callsign basis).
Would we want to store sub-entities that were not meaningful?
I think for the ZL4 example we might do
ZL = New Zealand, with general co-ordinates of ZL
ZL1 = blah, with more specific co-ordinates, zone etc
ZL2 = blah, with more specific co-ordinates, zone etc
...
with no record for ZL4 (so the program would fall back to the ZL record).
> Also, an IOTA field would be useful (I think it looks like e.g. 'EU-123') so
> perhaps best stored as text.
Yes.. lots of work populating that field though.
> In addition, beam heading fields would be good... long path and short path
> (integers), to be populated by an external bit of code at some later stage.
I'm not sure I follow. The latitude and longitude fields should be used
along with the user's current latitude and longitude to work out the
beam headings. I don't think it makes sense to store beam headings in
the database, since they are specific to the viewer.
> Well, was the country file copyright? If not, let's use it. It is widely used by
If it doesn't say what license it uses, we can't assume we're free to use it.
> contesters (who also contribute) and is kept up to date to ensure max points
> are claimed. Every man and his dog downloads this stuff before the major
> contests. Perhaps double-check with the editor of the cty file (AD1C??)
>
> Why duplicate what the contesters are already doing.
Fine if we can get permission. Would you like to contact them?
Thanks,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
