Runway Driven Group Visibility

Runway-Driven Group Visibility

vSMR can show/hide any existing AVISO group from EuroScope's active ARR/DEP runway selections, including runways at another airport. This affects main AVISO and insets, including CoFrance. It never selects active airports/runways or edits vSID rules.

LFPG defaults

East Arrows (ground-layout-east) follows 08/09; West Arrows (ground-layout-west) follows 26/27, considering both arrival and departure selections. Mixed east/west or no active direction hides both. The operational selection is read from EuroScope's active sector, independently of the view's geometry sector.

Runtime Menu toggles still work while automation is enabled. A manual choice remains until that rule's source airport changes its ARR/DEP selection or the rule itself changes. A change from 26L to 27R also reapplies the rule; unrelated airports/profile saves do not. Reopening/loading a map applies rules afresh. Disable a rule for permanent manual control.

Configure a rule

Merge runway_group_visibility into the root of vSMR_Data/config.json; do not replace your other settings. Bundled defaults belong to replaceable default.json, not user configuration. Back up the file, close the Control Center before external edits and keep valid JSON.

Example: show LFPG's West Arrows when LFPO departure runways 06 or 07 are active:

{
  "schema_version": 1,
  "runway_group_visibility": {
    "LFPG": {
      "ground-layout-west": {
        "enabled": true,
        "airport": "LFPO",
        "operation": "departure",
        "runways": ["06", "07"],
        "exclude_runways": [],
        "match": "any",
        "visible_when_matched": true,
        "visible_when_unmatched": false
      }
    }
  }
}

The outer key (LFPG) is the map airport. The next key is an existing group ID, not its displayed name; find it in that GeoJSON's vsmr_groups array. airport is the source airport to monitor and need not be the currently selected vSMR airport, but its runway data must exist in the active EuroScope sector.

Field	Meaning
enabled	Boolean; default true. false returns this group to manual control.
airport	Required source-airport ICAO for an enabled rule.
operation	either (default), arrival or departure.
runways	Required nonempty array. 26 matches 26/26L/26C/26R; 26L matches only 26L.
exclude_runways	Optional array; any matching active runway blocks the rule, using the same operation filter.
match	any (default) or all. Other active runways are allowed unless excluded.
visible_when_matched	Boolean; default true. Set false to invert matching visibility.
visible_when_unmatched	Boolean; default false, including missing source/no selected runways.

Objects merge by airport/group ID; arrays replace inherited arrays. Use "exclude_runways": [] to clear bundled exclusions when changing a rule. Unknown fields/invalid values cause that group's rule to be ignored and logged. Rules do not create groups or alter feature membership. Changing West alone does not change East.

To disable both LFPG defaults, merge this property into config.json:

"runway_group_visibility": {
  "LFPG": {
    "ground-layout-east": { "enabled": false },
    "ground-layout-west": { "enabled": false }
  }
}

This is a property fragment, not a complete JSON document. Rule/runway changes are picked up during refreshes without rewriting saved user settings. If EuroScope itself overwrites runway choices on connection, check its Set Active APT by Owned sector setting; changing a map rule does not change host runway ownership behavior.

Diagnose visibility

Verify selected runways in both ARR and DEP, the active sector, group ID, source airport, exclusions and operation. A manually hidden style remains a separate condition from group visibility. Enable .smr log normal before reproducing, then export .smr diagnostics. Changed decisions are logged as AVISO runway visibility, including the source and observed ARR/DEP runways.

This map automation is separate from vSID automatic configuration and RIMCAS runway monitoring.