Dallas Love Field Area

I recently visited beautiful Texas & loved it.

I ran into a couple routing issues that have now been addressed, tweaked a family-owned airport near Houston, learned about red light cameras (what is & is not), and wanted to bring up one more thing before I pretty much forget about the area in WME as I don’t want to muddy your waters with my yankee editing :wink: .

The Dallas Love Field area is currently pulled back to the terminal building. This doesn’t comply with the area guidelines I’m familiar with in the NE, nor does it comply with the TX area guidelines. IAW the guidelines, the area should include to the fence line (restricted access area), and overlap the airport access roads & various business points (i.e., rental lots). The runways are not mapped (not required, but generally done).

I was wondering if this was intentional or an oversight. I assume it’s intentional considering the number of conscientious editors in the area.

This is how all international airports in Texas are mapped. We’re doing away with fence line to fence line to better help with routing. As of now, we’re mapping just the terminals. Some runways have been added, some haven’t (that’s low priority).

Interesting. Does the area overlapping access roads cause the issue with routing?

As I understand it, with each area, there’s still a routing point that gets placed and users would be routed to that point, regardless of how large the area is mapped to.

Or is the issue more complex?

It’s more complex

Some of the problem txemt is speaking of is the way Waze interacts with Google search. In Austin which is one of the problematic airports, I have gotten hundreds of “I missed my flight” URs because of the issue.

Sent from my iPad using Tapatalk