Working development prototype · not a validated operational twinReal community-mapped geometry, estimated building volumes and synthetic movement. Source retrieval date is not an as-built date. Proposed or construction features are hidden by default.
What was retained from v1.4
The original application and source archive are preserved. Its terminal planning, passenger population, staffing, ESG, radio, hub intelligence and turnaround modules remain available in the project library. They are legacy illustrative analyses, not verified inputs to this 3D simulation.
Audit findings carried forward
- The legacy siteplan is explicitly schematic; it has no surveyed coordinate transform.
- Future T2/T3 elements appeared in the “today” view. This model separates construction layers.
- The schedule uses synthetic flights and random stands, without physical routing or exclusive stand reservations.
- Legacy claims of zero conflict and capacity/headroom are not validated operating rules.
- The legacy source assumes 45 m for both runways; OSM tags the south runway as 60 m. Widths and runway operations require current AIP validation.
- Legacy source citations do not include the underlying BARDI document or permission-cleared masterplan image.
Next accuracy gates
- Validate the layout date and control points against current AAI charts and BIAL as-built drawings.
- Replace estimated elevations, heights, stand lead-ins and service paths with authorised measurements.
- Verify rights before incorporating freeware scenery or architectural textures.
- Connect timestamped aircraft, vehicle and stand events; keep live and simulated data modes separate.
The local-metre projection is an approximation for visualization. Taxiway directions, aircraft eligibility, turning radii, swept-path clearance and operational permissions remain unvalidated.