I noticed that in the current charts for KORD (Chicago O’Hare), some taxiways are missing or incorrectly displayed. There are noticeable discrepancies compared to my simulator (MSFS 2020 with FSDreamTeam scenery), which shows the taxiways correctly.
In the attached screenshot, you can see that not only are some taxiway labels incorrect, but entire taxiways are missing from the charts. This issue is particularly evident near taxiways U and A, but other connections also seem to be incomplete.
Could you please check if your current data matches the official airport layouts, and if an update to the charts is necessary? If these discrepancies are due to differences in simulator data, a clarification would also be greatly appreciated.
Given the amount (and, as far as I can tell, frequency) of taxiway changes at KORD, it’s quite unlikely that this (or any other available scenery) has a layout accurate to the current real-world situation.
The Jeppesen charts and airport moving maps provided to us by Navigraph under license should be much closer.
There’s always the official airport chart from the FAA but it’s not exactly “readable” (closed taxiways are marked with X, as far as I can tell):
I understand that there are frequent changes to taxiways at KORD and that NOTAMs play a crucial role in keeping things up to date. However, my primary concern is not just about discrepancies with the simulator or real-world data.
The issue lies within the Navigraph app (or Cloud Charts), where the airport layout for KORD seems incomplete or incorrectly displayed. Specifically, some taxiways appear to simply end or are abruptly cut off, even though they are shown in grey, which indicates they should be visible. This issue is independent of whether the taxiways are active or closed, as it affects the visual representation of the airport itself.
For example, in the attached screenshot, you can clearly see several areas where taxiways are either missing or incorrectly truncated. This creates confusion when trying to navigate the airport using your charts.
Could you please confirm if this is an issue with the charts themselves or if there’s something wrong with how they are rendered in the Navigraph app?
