1. First startup Start the VRS X service/application. Open the admin panel: default: http://localhost:8085/admin if AdminPort was changed: http://<host>:<admin-port>/admin Complete activation (if required). Set the administrator password. 2. If the admin panel…
Read documentation →: Startup and LoginGeneral Settings should contain only global radar behavior and presentation options. What to configure here Instance name and high-level identity settings. General map behavior and display options. User-facing options rather than infrastructure…
Read documentation →: General SettingsThis page is a quick navigator for feed topics. Recommended order Configure feed source and MLAT behavior. Use Add Feed Set for multi-port receivers on one IP. Configure merged feeds. Check merged…
Read documentation →: Feeds and Merged FeedsTreat Server Settings as infrastructure and maintenance. 1. Web Server Port and Admin Port Web Server Port Port used by the public radar ( /AircraftList.json , map frontend). Admin Port Port used…
Read documentation →: Server Settings1. Navigation This page is a quick navigator for visual resources and marker customization. Recommended reading: Resources: Flags and Silhouettes Custom Operator Logo Aircraft Colors and Operator Colors Aircraft Model and Operator…
Read documentation →: Resources and Visuals1. User management In Users : create operator accounts, reset/change passwords, remove unused accounts. Avoid using one shared account for multiple operators. 2. Public vs private radar Radar Visibility controls radar access…
Read documentation →: Users and Security1. Minimum backup before changes Before major changes, create: configuration export ( Configuration Export ), database export ( Database Export ), backup of the instance data directory. 2. Update process (operational model)…
Read documentation →: Backup, Update, Recovery1. /admin returns Invalid url Most common causes: port conflict, admin is running on a different port than expected, reverse proxy path/port mismatch. Check: which process listens on admin port, AdminPort and…
Read documentation →: Troubleshooting1. Feed basics In Feeds , define raw data sources ( Mode-S Raw , BaseStation ). Mode-S Raw covers both: Beast family binary ( 30005 , 30006 , 30105 , 31005 ,…
Read documentation →: Feeds: Smart Ports and MLAT1. What Feed Filter does Feed Filter filters messages before they are propagated to the rest of the system. 2. Main options Enable Feed Filter enables/disables filtering globally. Prohibit MLAT Positions strips…
Read documentation →: Feed Filter1. Purpose Merged Feeds build one logical output from multiple source feeds. Recommended model: keep physical sources in Feeds , expose combined output via merged feeds where needed. 2. Merged feed options…
Read documentation →: Merged Feeds1. Upload packages Typical uploads: OperatorFlags.zip (or AirlineLogos.zip ) + optional OperatorFlagsList.csv DVSilhouettes.zip (or Silhouettes.zip ) + optional Silhouettes.csv Supported image formats: .bmp .png 2. Runtime lookup logic Operator flags: frontend requests…
Read documentation →: Resources: Flags and SilhouettesCustom operator logos are managed in /admin/resources under the custom operator logo section. 1. Naming and priority Allowed naming patterns: generic logo: OPERATOR.bmp or OPERATOR.png type-specific logo: OPERATOR-ICAOTYPE.bmp or OPERATOR-ICAOTYPE.png Runtime priority:…
Read documentation →: Custom Operator Logo1. Color priority chain Marker color priority: Aircraft Colors by ICAO hex has highest priority, if missing, Operator Colors is used, if both missing, default marker color is used. 2. Operator color…
Read documentation →: Aircraft Colors and Operator Colors1. AircraftDB Editor workflow search supports ICAO, registration, owner, manufacturer, and type, search returns up to 50 results, selecting row loads full record by AircraftID , create/update/delete operations refresh database lookup cache.…
Read documentation →: AircraftDB Editor and Custom Photos/admin/coverage is an admin-only coverage explorer for enabled merged feeds. It answers a practical question: where did this merged feed actually observe aircraft? It does not draw theoretical antenna range from receiver…
Read documentation →: CoverageThese tools live in the admin Visuals group: /admin/aircraft-model-mappings - menu label Aircraft Models , /admin/operator-aliases - menu label Operator Aliases . They are still present in the admin panel. If they…
Read documentation →: Aircraft Model and Operator AliasesExternal API Integrations: Google Maps & OpenAIP To enhance your radar experience with professional-grade base layers and aeronautical data, VRS X supports integration with third-party providers. These configurations are located in the…
Read documentation →: Map providers and API keysThe radar only asks for what the screen can use VRS X does not treat AircraftList.json as a blind "send every aircraft every time" endpoint. The radar frontend sends the current map…
Read documentation →: Viewport-Aware AircraftList.jsonRadar-scale traffic without melting the browser VRS X can handle very busy airspace without turning the map into an unreadable pile of markers. When you zoom out, the radar switches from individual…
Read documentation →: VRS X Smart Map ClusteringWeather Integration: The METAR Decoder VRS X features a high-precision, state-of-art METAR decoder. It doesn't just display raw weather strings; it parses real-time data from NOAA (National Oceanic and Atmospheric Administration) to…
Read documentation →: VRS X METAR Decoder