Improve the way hamsat alerts work, and add the ability to detect satellite names from spot comments. Closes #149

This commit is contained in:
Ian Renton
2026-09-23 22:08:36 +01:00
parent 981fea57ed
commit c26482f06b
15 changed files with 90 additions and 35 deletions
+16
View File
@@ -21,6 +21,7 @@ info:
* Removed `alert_type` from alert data. Contest, DXpedition and Satellite alerts now give those values in `sig` instead, alongside the existing outdoor activity programmes. Teeeeechnically a breaking change but AlertType is so new I doubt anyone is using it yet, so slipped this one in anyway. Sorry :)
* Added QRP, RaDAR Rally, /AM and /MM activities
* Added `has_refs` and `alerts_possible` to Activity data
* Added `dx_grid`, `dx_latitude` and `dx_longitude` to alert data
### 2.1
@@ -1452,6 +1453,21 @@ components:
type: integer
description: ITU zone of the DX operator
example: 14
dx_grid:
type: string
description: >
Maidenhead grid locator for the activator's location, if known.
example: IO91aa
dx_latitude:
type: number
description: >
Latitude of the activator's location, if known, in degrees.
example: 51.2345
dx_longitude:
type: number
description: >
Longitude of the activator's location, if known, in degrees.
example: -1.2345
freqs_modes:
type: string
description: An indication of the frequencies and modes that the activation will use, if provided.
+5
View File
@@ -266,6 +266,11 @@ function addAlertRowsToTable(tbody, alerts) {
} else {
items[i] = `${escapeHtml(a["sig_refs"][i]["id"])}`
}
// If this is a satellite alert the ref will just be the satellite, but DX grid is also important, so
// show that if we can.
if (a["sig_refs"][i]["sig"] === "Satellite" && a["dx_grid"]) {
items[i] += " from " + a["sig_refs"][i]["dx_grid"];
}
}
activityRefs = items.join(", ");
}