Missing Data SDOU and other airports in Brazil

[ufischdick]

My local airport, SDOU in Brazil is missing for me on my TDS GTN. I’ve reached out to them thinking they could be the problem. Heard back from them they believe there’s some issue with the db. A whole lot of airports I’ve checked around the area are gone as well so I’d like to raise the question to you whether there’s an issue with the db itself or if the problem is on my side. That’s in MSFS 2024, I’ve tried all I could, read the forum here, removed addons, reinstalled all navigraph software, reinstalled TDS, updated content.xml as per instructions posted here.

If there’s any other information you need from me let me know.

Ty

[NAVData]

Hi,
We are still in contact with the TDS developer regarding this issue. We need time to analyze the reason. I will keep you informed when we have identified the reason and/or resolved the issue.

Thank you
Richard

[ufischdick]

I know you said you’d get back when a solution is found but in case it’s been forgotten I wanted to check if anything was found.

[NAVData]

It is not forgotten - we are still working on it, and you should expect it back with 2513.

Cheers,
Richard

[NAVData]

Hi again,
Now the final answer. This issue is fixed as of 2513, so you can expect all missing airports to be included in all datasets.

Merry Christmas!

Cheers
Richard

[Rodeo314]

Out of curiosity:

I notice with the current cycle 2512, in e.g. the X-Plane Custom Data GNS430 database, there are no actual runway coordinates for SDOU:

A,SDOU,JORNALISTA BENEDITO ,-22.973611,-49.911389,1516,0,0,4900,0
R,16,160,4921,98,0,0.000,0,-22.973611,-49.911389,1516,3.00,40,1,0
R,34,340,4921,98,0,0.000,0,-22.973611,-49.911389,1516,3.00,40,1,0

Both thresholds are set to the ARP coordinates, was that perhaps why they were filtered out in some databases such as the one powering the TDS GTN? Or was it a different reason?

Regards,

Tim

[ufischdick]

Thank you!

And merry Christmas

[tFlyer]

From the TDS end, we would like to thank Richard and the entire Navigraph team for the prompt and professional attention offered to this bug, as well as for the bug fix in the next navdata cycle!