From a9003162ccb77b20cbe210f387ad34addd30486f Mon Sep 17 00:00:00 2001 From: Ian Renton Date: Thu, 30 Oct 2025 12:34:00 +0000 Subject: [PATCH] Docs --- README.md | 2 +- views/webpage_about.tpl | 5 ++++- webassets/apidocs/openapi.yml | 26 ++++++++++++++++++++++---- 3 files changed, 27 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 769dc63..391f1f2 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ The API is deliberately well-defined with an OpenAPI specification and auto-gene Spothole itself is also open source, Public Domain licenced code that anyone can take and modify. -Supported data sources include DX Clusters, the Reverse Beacon Network (RBN), the APRS Internet Service (APRS-IS), POTA, SOTA, WWFF, GMA, WWBOTA, HEMA, and Parks 'n' Peaks. +Supported data sources include DX Clusters, the Reverse Beacon Network (RBN), the APRS Internet Service (APRS-IS), POTA, SOTA, WWFF, GMA, WWBOTA, HEMA, Parks 'n' Peaks, ZLOTA, WOTA, the UK Packet Repeater Network, and NG3K. ![Screenshot](/images/screenshot2.png) diff --git a/views/webpage_about.tpl b/views/webpage_about.tpl index 8770431..4efff9f 100644 --- a/views/webpage_about.tpl +++ b/views/webpage_about.tpl @@ -6,7 +6,6 @@

While there are several other web-based interfaces to DX clusters, and sites that aggregate spots from various outdoor activity programmes for amateur radio, Spothole differentiates itself by supporting a large number of data sources, and by being "API first" rather than just providing a web front-end. This allows other software to be built on top of it.

The API is deliberately well-defined with an OpenAPI specification and API documentation. The API delivers spots in a consistent format regardless of the data source, freeing developers from needing to know how each individual data source presents its data.

Spothole itself is also open source, Public Domain licenced code that anyone can take and modify. The source code is here. If you want to run your own copy of Spothole, or start modifying it for your own purposes, the README file contains a description of how the software works and how it's laid out, as well as instructions for configuring systemd, nginx and anything else you might need to run your own server.

-

Supported data sources include DX Clusters, the Reverse Beacon Network (RBN), the APRS Internet Service (APRS-IS), POTA, SOTA, WWFF, GMA, WWBOTA, HEMA, and Parks 'n' Peaks.

The software was written by Ian Renton, MØTRT and other contributors. Full details are available in the README.

This server is running Spothole version {{software_version}}.

FAQ

@@ -16,6 +15,10 @@

As well as spots, it also provides a similar feed of "alerts". This is where amateur radio users who are going to interesting places soon will announce their intentions.

What are "DX", "DE" and modes?

In amateur radio terminology, the "DX" contact is the "interesting" one that is using the frequency shown. They might be on a remote island or just in a local park, but either way it's interesting enough that someone has "spotted" them. The callsign listed under "DE" is the person who spotted the "DX" operator. "Modes" are the type of communication they are using. You might see "CW" which is Morse Code, or voice "modes" like SSB or FM, or more exotic "data" modes which are used for computer-to-computer communication.

+

What data sources are supported?

+

Spothole can retrieve spots from: Telnet-based DX clusters, the Reverse Beacon Network (RBN), the APRS Internet Service (APRS-IS), POTA, SOTA, WWFF, GMA, WWBOTA, HEMA, Parks 'n' Peaks, ZLOTA, WOTA, and the UK Packet Repeater Network.

+

Spothole can retrieve alerts from: NG3K, POTA, SOTA, WWFF, Parks 'n' Peaks, and WOTA.

+

Between the various data sources, the following Special Interest Groups (SIGs) are supported: POTA, SOTA, WWFF, GMA, WWBOTA, HEMA, IOTA, MOTS, ARLHS, ILLW, SIOTA, WCA, ZLOTA, KRMNPA, WOTA, WAB & WAI.

How is this better than DXheat, DXsummit, POTA's own website, etc?

It's probably not? But it's nice to have choice.

I think it's got two key advantages over those sites:

diff --git a/webassets/apidocs/openapi.yml b/webassets/apidocs/openapi.yml index 30322d8..2e13821 100644 --- a/webassets/apidocs/openapi.yml +++ b/webassets/apidocs/openapi.yml @@ -78,11 +78,14 @@ paths: - HEMA - WCA - MOTA - - SiOTA + - SIOTA - ARLHS - ILLW - ZLOTA - IOTA + - WOTA + - WAB + - WAI - name: needs_sig in: query description: "Limit the spots to only ones with a Special Interest Group such as POTA. Because supplying all known SIGs as a `sigs` parameter is unwieldy, and leaving `sigs` blank will also return spots with *no* SIG, this parameter can be set true to return only spots with a SIG, regardless of what it is, so long as it's not blank. This is what Field Spotter uses to exclude generic cluster spots and only retrieve xOTA things." @@ -151,6 +154,9 @@ paths: - PSK - BPSK31 - OLIVIA + - MFSK + - MFSK32 + - PKT - name: mode_type in: query description: "Limit the spots to only ones from one or more mode families. To select more than one mode family, supply a comma-separated list." @@ -291,11 +297,14 @@ paths: - HEMA - WCA - MOTA - - SiOTA + - SIOTA - ARLHS - ILLW - ZLOTA - IOTA + - WOTA + - WAB + - WAI - name: dx_continent in: query description: "Limit the alerts to only ones where the DX (the operator being spotted) is on the given continent(s). To select more than one continent, supply a comma-separated list." @@ -653,6 +662,9 @@ components: - PSK - BPSK31 - OLIVIA + - MFSK + - MFSK32 + - PKT example: SSB mode_type: type: string @@ -728,11 +740,14 @@ components: - HEMA - WCA - MOTA - - SiOTA + - SIOTA - ARLHS - ILLW - ZLOTA - IOTA + - WOTA + - WAB + - WAI example: POTA sig_refs: type: array @@ -888,11 +903,14 @@ components: - HEMA - WCA - MOTA - - SiOTA + - SIOTA - ARLHS - ILLW - ZLOTA - IOTA + - WOTA + - WAB + - WAI example: POTA sig_refs: type: array