DEMO WORKSPACEIllustrative traffic only. No authorised PTFS feed is connected.
AUTHORISED TELEMETRY
Feed Health
Inspect the PTFS integration contract, connection freshness and the fields genuinely supplied by your provider.
Connection status
NOT CONNECTED
Last successful update
Unavailable
Data freshness
No observations received
Provider capabilities
Unknown fields remain unavailable. The current pilot and aircraft spawner are always kept separate.
- Intended server
- Unavailable
- Observed server
- Unavailable
- Server coverage confirmed
- Unconfirmed
- Pilot identity
- Unavailable
- Spawner identity
- Unavailable
- Other crew
- Unavailable
- Position / altitude
- Unavailable
- Groundspeed
- Unavailable
- Airspeed
- Unavailable
- Vertical speed
- Unavailable
- Polling interval
- 20 seconds
Connection requirements
No provider is assumed. Owning a PTFS private server alone does not establish a telemetry connection.
- Obtain legitimate provider permission for the intended PTFS server.
- Configure PGAN_FEED_URL, PGAN_FEED_TOKEN (if required) and PGAN_SERVER_ID in the builder’s secure Secrets configuration.
- Use the documented HTTP JSON contract, or adapt a provider’s authorised WebSocket protocol server-side.
- Allow the provider’s actual network host in the function configuration if required.
- Test server coverage, coordinate calibration, identities and freshness before using the traffic operationally.
The radar uses a schematic PTFS sector, not a geographic map. Calibrated provider x/y positions are required. Real-world aviation tracking and live PTFS identity are not claimed.
Validate a provider payload
Check a JSON file locally without saving it or marking it live.
Recent integration errors
No integration attempts have produced recorded errors. This does not indicate a live connection.