Suspect that 270 in the WWFF list is a typo. You’d not have ZL and Tokelau sharing a DXCC and at the same time break out the Chathams and sub’s to separate ones.
Like me they probably only found a .pdf with the list and all sorts of page breaks, headers, footers, footnotes that get in the way when you try to extract it into a table! Suspect they gave in & typed it in, with obvious results.
Doesn’t sound like the field is used for much, if no-one’s noticed!
==
You suggest:
go ahead with just the mainland (EntityCode 170) parks for now?
Or put in the whole of the ZL set as 170 even if they lie in the Chathams or other offshore areas.
Or follow the WWFF example and use 270 even though it appears wrong
Or wait till I have time to code them all to the correct DXCC
I agree with this. I’ve ignored this and many other fields to date. And even the fields I rely on I find many errors. Overall, the data in the directory remains largely lacking validation.
Perhaps @M1SDH Steve can tell us what PoLo does with this enum because I cannot see what relevance it has for my operations. The Lat/Long is certainly used and so to is the gridsquare or lat/long for calculating it.
I’m tempted to just put a placeholder in tat field. I was only thinking along the lines of giving PoLo what it already has in terms of field value so the import code doesn’t have to be modified for another program.
So in general, the reference is probably the only mandated field we need. Other fields unlock features in PoLo which improve user experience.
So for this thread and as future reference for others, the fields and how they are used:
Reference: needed as unique ID for activity on what your activating
Name: Can be used for searching for reference, as well as displaying name to user generally.
Lat/Long: Used to filter out nearby references when adding to your operation. Can be generated from Maidenhead Locator.
Maidenhead Locator: Used to give option to select own location, and as map location for other station on P2P, etc. Can be generated from Lat/Long.
DXCC/Entity: Used to filter references when selecting one for the operation, and auto generating prefixes for P2P entry.
Status: Used to remove inactive references when imported. Some schemes just don’t include inactivate references in their file anyway.
Others fields: Fields like state, type, area, county, region, etc. are also displayed when searching for references, but otherwise aren’t currently used for anything.
Given this is limited to a few DXCC in ZL, we can probably skip that field, unless you want the filter feature working when listing nearby references.
OK well ARRL and ADIF stnd lists New Zealand as 170, the wwff Directory file lists it as 270.
typo?
The wwff directory file has mismatches so not something I would rely on…
Alan
start_time is optional. By default will return the last 2 hours of spots. General idea is you set it to the time you last retrieved spots (or time of the last ZLOTA spot you have) to avoid duplication.
zlota_only is optional. Including this parameter with any value retrieves only spots for the ZLOTA scheme. By default we return all spots for all schemes that were created locally at ontheair.nz
ontheair supports multi-site spots (one spot for many programmes). For this API, however, these have been broken out into separate entries. So a spot for a lake in a park at ontheair will show two rows in the results, both with the same id.
The API currently exports all spots created at ontheair. But not spots pulled from other clusters. This means ZLOTA spots created at ParksNPeaks will not be included. I can work on that if needed, but it becomes a can of worms with potential for duplicate spots.
That was added as an authentication method for spotting and log uploads at Sue’s request (iPnP app) as she didn’t want to store multiple sets of credentials for PnP and ontheair.
When we receive an API POST with a PnP key (rather than an ontheair PIN) we validate the credentials at ParksNPeaks before allowing the POST.
It could probably be removed, as Sue never implemented spotting / log uploads to ontheair via the API.
