website: added map to the features and described g1ybb workflow

github_docs/de-Contest-Workflow.md

@@ -246,6 +246,19 @@ G1YBB verwendet die Richtungsanzeige besonders konsequent. Grün markierte Stati
 
 KST4Contest automatisiert dabei nicht das QSO. Der Vorteil besteht darin, dass QRG, Richtung, Aircraft-Scatter-Informationen und weitere Bewertungsdaten bereits vorliegen, wenn die Gelegenheit entsteht. Die verbleibende Aufgabe ist eine schnelle betriebliche Entscheidung.
 
+Eine weitere, besonders konsequente Betriebsweise nutzt die Stationskarte als geografische Arbeitsliste:
+
+1. Der **wkd**-Filter blendet bereits gearbeitete Rufzeichen aus der Benutzerliste und damit auch aus der Karte aus.
+2. G1YBB wählt eine interessante Station auf der Karte aus.
+3. **Trigger cluster spot** übergibt die bekannte QRG an Minos.
+4. Ein Klick auf den Spot wechselt in Minos auf diese QRG.
+5. Nach dem QSO wird der Kontakt geloggt.
+6. Die Log-Synchronisation aktualisiert den Worked-Status; der Filter entfernt die Station anschließend aus Benutzerliste und Karte.
+
+Die Karte wird so zu einer räumlichen Liste der noch abzuarbeitenden Stationen. Dieser Ablauf ist optional. Er setzt eine zuverlässig eingerichtete Log-Synchronisation und DX-Cluster-Verbindung voraus und ist vor allem für Operatoren interessant, die den Contest bewusst auf diese geografische Weise strukturieren möchten.
+
+[G1YBB zeigt diesen Workflow im Video.](https://www.youtube.com/watch?v=BCNCjowPgec)
+
 ---
 
 ## Optionale Schnittstellen im Workflow

github_docs/de-DX-Cluster-Server.md

@@ -242,5 +242,6 @@ Die Schnittstelle wurde mit folgenden Logprogrammen verwendet:
 
 - UCXLog
 - N1MM+
+- Minos
 
 Weitere Logger können funktionieren, wenn sie eine normale TCP-Verbindung zu einem DX-Cluster-Server unterstützen.

github_docs/en-Contest-Workflow.md

@@ -246,6 +246,19 @@ G1YBB uses the directional indication particularly consistently. Stations highli
 
 KST4Contest does not automate the QSO. Its advantage is that QRG, direction, aircraft scatter information and other evaluation data are already available when the opportunity appears. The remaining task is a quick operating decision.
 
+Another particularly consistent operating method uses the station map as a geographical worklist:
+
+1. The **wkd** filter removes already worked callsigns from the user list and therefore from the map.
+2. G1YBB selects an interesting station on the map.
+3. **Trigger cluster spot** passes the known QRG to Minos.
+4. Selecting the spot moves Minos to that QRG.
+5. The completed QSO is logged.
+6. Log synchronisation updates the Worked state, and the filter removes the station from both the user list and the map.
+
+The map consequently becomes a spatial list of the stations still to be worked. This workflow is optional. It requires reliable log synchronisation and a working DX Cluster connection and is mainly useful for operators who deliberately want to organise the contest in this geographical way.
+
+[Watch G1YBB demonstrate this workflow.](https://www.youtube.com/watch?v=BCNCjowPgec)
+
 ---
 
 ## Optional Interfaces in the Workflow

github_docs/en-DX-Cluster-Server.md

@@ -248,6 +248,7 @@ The interface has been used with:
 
 - UCXLog
 - N1MM+
+- Minos
 
 Other loggers may work if they support a normal TCP connection to a DX Cluster server and accept conventional `DX de ...` spot lines.
 

github_docs/en-Features.md

@@ -806,7 +806,7 @@ Marker colours provide a compact status indication:
 |---|---|
 | Blue | Normal station marker |
 | Yellow | The callsign has already been worked on at least one band |
-| Green | The station is inside the current antenna sector and is relevant as a directional candidate |
+| Green | A directional opportunity has been derived for the station from directed chat messages |
 | Orange | Currently selected station |
 
 The selected state has the highest display priority, followed by the directional warning and Worked state. A selected station therefore remains orange even if it also meets one of the other conditions.

website/src/features/band-recognition.md

@@ -14,6 +14,7 @@ tagsList:
   - ON4KST
   - contest workflow
 related:
+  - station-map
   - directional-opportunities
   - priority-score
   - dual-chat

website/src/features/directional-opportunities.md

@@ -13,6 +13,7 @@ tagsList:
   - QRB
   - contest workflow
 related:
+  - station-map
   - band-recognition
   - dx-cluster
   - rotator-control

website/src/features/dx-cluster.md

@@ -12,8 +12,10 @@ tagsList:
   - QRG detection
   - UCXLog
   - N1MM+
+  - Minos
   - contest logger
 related:
+  - station-map
   - directional-opportunities
   - log-sync
   - priority-score
@@ -227,6 +229,7 @@ The local DX Cluster interface has been used with:
 
 - UCXLog
 - N1MM+
+- Minos
 
 Other loggers may work if they can open a normal TCP connection to a DX Cluster server and accept conventional `DX de ...` spot lines.
 

website/src/features/rotator-control.md

@@ -13,6 +13,7 @@ tagsList:
   - UDP
   - SPID
 related:
+  - station-map
   - directional-opportunities
   - priority-score
   - timeline

website/src/features/station-map.md

@@ -0,0 +1,97 @@
+---
+title: Station Map and Path Analysis
+icon: 🗺️
+category: Contest Awareness
+since: "1.41"
+summary: Use the filtered chat-member list as a geographical contest worklist and examine the selected radio path with terrain, Fresnel and link-budget estimates.
+description: KST4Contest projects the current filtered station context onto a map and provides an engineering estimate of the selected path.
+tagsList:
+  - station map
+  - path analysis
+  - terrain profile
+  - Fresnel zone
+  - link budget
+  - Open-Meteo
+  - Copernicus GLO-90
+  - contest workflow
+related:
+  - band-recognition
+  - directional-opportunities
+  - dx-cluster
+  - rotator-control
+---
+
+## Why use a map during a contest?
+
+A table is efficient when callsigns, scores or QRBs need to be sorted. It is less immediate when the operator wants to see which unworked stations remain in one direction or how they relate to the current antenna sector.
+
+Since version 1.41, the KST4Contest station map provides this geographical view of the same operating context. It is not an independent list. The filters applied to the chat-member table also determine which stations appear on the map.
+
+![Station map with path analysis](/manual/assets/station_map_path_analysis.png)
+
+## A geographical contest worklist
+
+With the **wkd** filter enabled, worked callsigns disappear from the user list. They also disappear from the map. What remains is a spatial worklist of stations which may still be relevant to the contest.
+
+The map retains the context already known by KST4Contest:
+
+- normal, Worked, directional-opportunity and selected marker states;
+- known bands and open `B+` opportunities;
+- the configured antenna direction, beamwidth and maximum QRB as a visible sector; and
+- a Maidenhead locator grid for geographical orientation.
+
+Only stations with a usable six-character locator can be positioned. Active chat variants of the same normalised base callsign are combined into one marker, while their actual message destinations remain separate.
+
+Green has a specific meaning: it marks a directional opportunity derived from directed ON4KST messages. It does not merely mean that the marker happens to lie inside the local antenna sector.
+
+## Selection remains connected to the chat
+
+Selecting a marker selects the corresponding active chat member in the main window. KST4Contest scrolls to the entry in the user list, updates **Further Info** and prepares the complete visible callsign as the message target.
+
+The suffix and chat category are retained. Combining several active variants into one geographical marker therefore does not turn them into one interchangeable ON4KST login.
+
+The selected path is shown as a connection line. The map can then remain a quick selection surface or be used together with the lower path-analysis panel.
+
+## G1YBB's map-driven workflow
+
+G1YBB uses the map particularly consistently as a geographical contest worklist:
+
+1. Enable the Worked filter so that already worked stations are removed.
+2. Select an interesting station on the map.
+3. Use **Trigger cluster spot** to send its known QRG to the connected logger.
+4. Select the spot in Minos and move the radio to that QRG.
+5. Complete and log the QSO.
+6. Log synchronisation updates the Worked state, and the filter removes the station from both the user list and the map.
+
+This creates a direct visual progression through the remaining stations. It is an optional and deliberately consistent operating method, not a prerequisite for using the map or KST4Contest.
+
+[Watch G1YBB demonstrate this workflow.](https://www.youtube.com/watch?v=BCNCjowPgec)
+
+## What does the path analysis calculate?
+
+For the selected station, KST4Contest currently requests terrain elevations from the Open-Meteo elevation service. The provider uses Copernicus GLO-90 data, and one path is sampled with no more than 100 evenly distributed elevation points.
+
+The resulting profile combines information including:
+
+- terrain and the geometrical line between both antennas;
+- radio and terrain horizons;
+- the first Fresnel zone and its minimum clearance;
+- possible Fresnel-zone intrusion and a rough diffraction estimate;
+- a frequency selected from current QRG or band context; and
+- an estimated link budget using power, antenna gain, feeder loss and path loss.
+
+The **Frequency** shown in the panel is the value actually used for the calculation. It should be checked before interpreting the Fresnel zone or link budget, especially on the microwave bands.
+
+## Engineering estimates, not measured conditions
+
+The nominal resolution of the terrain model is not the distance between requested points. On a long path, 100 samples can leave substantial gaps, and narrow obstacles may remain undetected.
+
+The calculation also cannot know the exact remote antenna height and pattern, buildings, vegetation, current atmospheric refractivity, interference or whether a detected QRG is still in use. Line of sight, Fresnel clearance, horizons and the link budget therefore remain technical estimates.
+
+In practical terms: the map keeps the remaining contest stations geographically visible, while the path analysis exposes useful assumptions about one selected route. Neither view predicts propagation or guarantees a QSO.
+
+[Read the complete map and path-analysis description in the manual.](/manual/en/features/#station-map-and-path-analysis-from-v141)
+
+[Open the map controls in the user-interface manual.](/manual/en/user-interface/#station-map)
+
+[Open the path-analysis and link-budget settings.](/manual/en/configuration/#path-analysis-and-link-budget)