11L |P|0592001|
|N|0592001|
| 334829.0026|-1182044.3965|1282715| 5001|150|0592001|
| 96.2| |0592001| only this is recognized as the runway datapoint
| 334825.6765|-1182039.3792| 541|0592001|
| 0| 83.0| |0592001|
| 541| 85.1| |0592001|
| 3487| 96.1| |0592001|
| 4461| 97.1| |0592001|
| 5001| 96.8| |0592001|
The UDDF is the dump of the FAA database. This is the same database that all of the FAA evaluation software uses. There is a significant problem, as the program lists the runway end as zero, not the threshold as zero. The datapoint is RW only, and this is the endpoint, there is no datapoint for displaced thresholds in the software. So when an evaluation is done, the obstacle surfaces are generated from the runway endpoint, not the displaced threshold.
http://www.ngs.noaa.gov/AERO/uddf/WE...A/TOA__02B.F77
TOA has displaced thresholds, so when evaluated by the FAA OE-AAA software, will have a much different result, that if one uses the displaced threshold origins for evaluation.
This is also the reason why many of the procedure designs the FAA generates, and the data on the plates, just dont ever seem to add up.
I used PSP as an extreme example, as there is a 3000 foot displaced threshold, but if you look at NOTAMS, you will see that it shows the obstacle, as an example, 4300 feet from one runway, and 1000 feet from another, yet both thresholds are right next to each other.....