Squawk codes not displaying in web frontend #4

New issue

Closed

opened 2025-08-24 17:58:08 +02:00 by olemd · 0 comments

olemd commented

2025-08-24 17:58:08 +02:00

Owner

Problem Description

Squawk codes are mostly not visible in the web frontend, despite aircraft transmitting them. This affects situational awareness and emergency detection capabilities.

Expected Behavior

Aircraft should display their 4-digit squawk codes in:

Aircraft table view
Map popup when clicking on aircraft markers
Emergency squawk codes (7700, 7600, 7500) should be highlighted

Current Behavior

Most aircraft show empty/blank squawk fields in the web interface
Squawk codes appear to be missing from API responses or not properly displayed
Emergency situations may go unnoticed due to missing squawk information

Technical Details

Potential Issues:

Squawk decoding in /internal/modes/decoder.go may be incomplete
Frontend display logic might not be showing squawk codes properly
API marshaling in /internal/merger/merger.go might be missing squawk fields

Frontend Locations:

Aircraft table: /assets/static/js/modules/ui-manager.js
Map popups: /assets/static/js/modules/aircraft-manager.js

Impact

Safety: Cannot identify emergency squawk codes (7700=emergency, 7600=radio failure, 7500=hijacking)
ATC Coordination: Missing transponder codes needed for air traffic control
Situational Awareness: Incomplete aircraft information display

Investigation Needed

Verify squawk codes are being decoded from Mode S messages
Check if squawk field is included in API responses
Ensure frontend properly displays non-empty squawk codes
Add highlighting for emergency squawk codes (77xx series)

Example

Aircraft with squawk 1000 should show:

{
  "ICAO24": "4ACB58",
  "Squawk": "1000",
  "Emergency": ""
}

Currently showing:

{
  "ICAO24": "4ACB58", 
  "Squawk": "",
  "Emergency": ""
}

## Problem Description Squawk codes are mostly not visible in the web frontend, despite aircraft transmitting them. This affects situational awareness and emergency detection capabilities. ## Expected Behavior Aircraft should display their 4-digit squawk codes in: - Aircraft table view - Map popup when clicking on aircraft markers - Emergency squawk codes (7700, 7600, 7500) should be highlighted ## Current Behavior - Most aircraft show empty/blank squawk fields in the web interface - Squawk codes appear to be missing from API responses or not properly displayed - Emergency situations may go unnoticed due to missing squawk information ## Technical Details **Potential Issues:** - Squawk decoding in `/internal/modes/decoder.go` may be incomplete - Frontend display logic might not be showing squawk codes properly - API marshaling in `/internal/merger/merger.go` might be missing squawk fields **Frontend Locations:** - Aircraft table: `/assets/static/js/modules/ui-manager.js` - Map popups: `/assets/static/js/modules/aircraft-manager.js` ## Impact - **Safety**: Cannot identify emergency squawk codes (7700=emergency, 7600=radio failure, 7500=hijacking) - **ATC Coordination**: Missing transponder codes needed for air traffic control - **Situational Awareness**: Incomplete aircraft information display ## Investigation Needed 1. Verify squawk codes are being decoded from Mode S messages 2. Check if squawk field is included in API responses 3. Ensure frontend properly displays non-empty squawk codes 4. Add highlighting for emergency squawk codes (77xx series) ## Example Aircraft with squawk 1000 should show: ```json { "ICAO24": "4ACB58", "Squawk": "1000", "Emergency": "" } ``` Currently showing: ```json { "ICAO24": "4ACB58", "Squawk": "", "Emergency": "" } ```