Hi, airport NZHM is missing in the database for the TDS GTNXi. TDS support recommended me to report this issue here. Thanks.
Hi,
Thank you very much for your report - this airport will not exported because we don´t have any runway-coordinates for that. It seems that the AIP doesn´t offer this airport and the details to this airport. I´m sorry.
Cheers,
Richard
1 Like
Sorry, I am not familiar with what AIP is. I’m not an expert. 
I only realized, that the airport does exist in the 2502 AIRAC, that’s why I was surprised, that it is missing in the TDS GTNXi with the updated AIRAC. I thought the data is exactly the same.
What do you mean with:
The same as what? What I mean is the same as what the real world AIP offered.
Cheers
Richard
Then why is there Custom Data/CIFP/NZHM.dat or in GNS430/navdata/Airports.txt:
A,NZHM,HANMER,-42.569722,172.798056,980,13000,15000,3000,0
R,06,57,3025,98,0,0.000,0,-42.569722,172.798056,980,3.00,40,2,0
R,24,237,3025,98,0,0.000,0,-42.569722,172.798056,980,3.00,40,2,0
The airport is also listed in Navigraph Charts, including runways w/dimensions and bearings.
You must be thinking of another airport?
Regards,
Tim
…not sure where I would find the runway thresholds but Navigraph/Jeppesen must have found it somewhere (see above).
Regards,
Tim
Again, I am not an expert and I do not know what an AIP is. I own the TDS GTNXi and I have a Navigraph subscription. The TDS navdata is updated through Navigraph hub. In SimBrief, in Navigraph Charts and in LittleNavMap (also updated with latest AIRAC) the airport NZHM is listed / available. When all the software I use, is on the same AIRAC cycle / navdata, I expected the same airport being available everywhere.
Sidenote: there seems to be another grass-strip north of NZHM. My friend who does not have a Navigraph subscription told me, that the northern airstrip is actually NZHM in his old navdata. Can this be the source of confusion here?
EDIT: Sorry, that is / was NZHR, please ignore this last paragraph.
Hi again,
We have the airport and runways, but as I have written, the runway threshold coordinates are missing. Therefore, we don’t export such airports to avoid crashes or unexpected errors.
@Rodeo314 :
Looking more deeply at the data you posted, you see that the threshold coordinates are missing. XP is the only one which can handle runways without threshold coordinates.
Also, in the charts, you don’t have any coordinates for the runways, only the idents and length, …
So, we have this airport and the runways (without coordinates) in our database, therefore available in Simbrief and Charts, … but not in the data. We don’t export such records (airports without runway thresholds).
To the AIP question:
It’s a kind of handbook from each country that includes the latest information about the airports in the country, which is the base for the data provider. When this AIP (as in this case) doesn’t offer any runway thresholds, they are also missing in most cases in the source data. The same goes for airports; when the AIP of this country doesn’t offer the airport (because it is closed, military, private, etc.), it will also not be included in the source data. So, AIP New Zealand (https://www.aip.net.nz/) is the real-world information handbook for New Zealand.
I hope that helps
Richard
Thank you for the details, Richard. This clarified it for me.
Would you pls let me know, where I can find this information in the docs to share it with others, who experience the same issue? Thx.
It’s absent in CIFP/NZHM.dat but that files has missing thresholds for dozens of runways where the coordinates are available elsewhere:
https://forum.navigraph.com/t/missing-runway-threshold-coordinates-in-xp11-xp12-data/10790
https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084
…so its absence from there is not a reliable indicator of whether Navigraph has the runway coordinates.
The thresholds are available in GNS430/navdata/Airports.txt
A,NZHM,HANMER,-42.569722,172.798056,980,13000,15000,3000,0
R,06,57,3025,98,0,0.000,0,-42.569722,172.798056,980,3.00,40,2,0
R,24,237,3025,98,0,0.000,0,-42.569722,172.798056,980,3.00,40,2,0
Typically, when an airport has no runway coordinates, it’s absent altogether from Navigraph’s various databases, for example FGAN, ENLI, ENFY, ENSN, ENJB:
https://forum.navigraph.com/t/simbrief-support-request-unanswered/8644
https://forum.navigraph.com/t/icao-airfields-currently-not-in-the-database/14564
Meaning it’s not in GNS430/navdata/Airports.txt, it’s not available for planning on Simbrief, and the runway-info panel in Navigraph Charts is blank:
NZHM fits none of these “usual” criteria, it’s in Airports.txt, it’s available as an origin/destination on Simbrief, the Charts runways panel is not blank, which is why I was confused as to why it’s not exported.
I did find it absent from the “TDS GTNXi for X-Plane” SQLite database (tbl_pg_runways), but also present in e.g. “SimToolkitPro v0.4 (and above)” under tbl_runways.
I’ve also found it in the Fenix database, AirportLookup shows NZHM as being airport 11273, and the Runways table for 11273 shows two records (06 and 24) including latitude and longitude coordinates.
So basically I am still very much confused as to why it (NZHM) is present in some databases (with runways incl. lat/lon) but not in others.
Regards,
Tim
Tim, please show me where you see the runway threshold coordinates?
When you would look in detail of your screenshots and your references, you will see that these are not the threshold coordinates but the airport reference points.
Thank you
Richard
Oh, duh, they are indeed the same coordinates for both thresholds 
Then, is it possible that NZHM (or at least the associated runway records) are actually present by mistake in some of the databases I mentioned (as opposed to “missing” from the other databases)?
Regards,
Tim
As in XP, it depends on the add-on. As I have written, we have the airport and runway records (but without runway-threshold coordinates).
So, it is included in Simbrief, our charts, plus XP, and really, really in a few datasets (depending on their specifications). So, it´s not a “mistake”. It´s the result of the data specification of the addon-devs.
Cheers,
Richard
1 Like
@Skytrevor, @Rodeo314:
… but what I can offer is, to speak with Tiberiu from TDS, possible it´s also ok for him and his devices, when I enter the ARP coordinates instead the threshold coordinates? 
I will check it …
Cheers,
Richard
1 Like
That’ll be great. Thanks for the clarification again. 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.