Add HEMA programme #21
Labels
No labels
big job
blocked
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
maybe
meta
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ian/field-spotter#21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Info received via email, thanks Ed DD5LP/G8GLM!
Spot Seed
So... first thing we have is a 'spot seed'. This increments each time a new spot is made. It means we don't download the whole set of spots each time if there hasn't been a change.
http://hema.org.uk/spotSeed.jsp
Latest Spot
The latest spot "one liner" can be extracted here:
http://hema.org.uk/latestSpotForMobile.jsp
We use this to generate the 'alarm' in the system tray when a new spot is added.
Example reply:
17/07/2023 10:34=16/07/2023 11:04;1410;G8XDD/P;G/HSE-002;Ashley Hill;7.165 (SSB);(2E0FEH) SU88=
I'm not sure why the "current" datetime is not UTC, but I don't think we're using it at the moment anyway.
16/07/2023 11:04 - DateTime is the spot date and time in UTC
1410 - is the number of minutes since the spot was made (we use this to show how hot/recent the spot is in the app)
G8XDD/P - Callsign of spotted station
G/HSE-002 - Summit reference
Ashley Hill - Summit name
7.165 (SSB) - Frequency and mode
(2E0FEH) SU88 - Spotter and comments
Spots
http://hema.org.uk/spotsMobile.jsp
This retrieves a complete list of the latest spots. Format as per "Latest Spot" with each spot '=' delimited.
TBD how the spot seed can be provided back to the API to only download new data, and how to get lat/long points for a summit reference
Awaiting feedback from Ed / HEMA folks about how to get lat/long points.
Steve M1SDH has a GeoJson file of HEMA points in his map, but it only covers the UK, and not sure exactly where it came from. Regardless, it would be nice to load spot lat/longs from an API like the rest of the programmes, rather than loading a big data file.
Unblocked - HEMA are adding lat/lon fields to the API. Work can progress.
Closing this issue, moving to spothole as a backend under #60 will resolve this issue automatically.