tagging large areas (specifically airports) for Nominatim/osrm routing

I would have thought this should have came up a long time before this but was wondering...

Say I wanted to use OSRM or some other router that uses Nominatim. So I type in an airport name, such as "Denver International Airport". However Nominatim ends up finding the big huge 33,000 acre plot of land and probably does a weighted centroid of this plot of land as the target point, and OSRM goes and tries to send you to a taxiway for airplanes (try it!).

How should these large areas be tagged so that Nominatim will point you to a more sensible, drivable location? I suppose large cities have the same problem but chances are if it's a large city, it's dense enough and likely a road near the centroid, but for airports, especially Denver which by area is one of the largest in the world, this might not be the best location to drive to? Likely it's best to point to the terminal or at least the transit station in the airporit if at all possible IMHO.

Or perhaps this is outside the scope of OSM?

By the way: Example case: In OSRM or OSM website, try searching (with text) for a routing path between:

From: Boulder, Colorado To: Denver International Airport

The problem I see is that the OSRM router will use the service roads to get to the airport, again probably because Nominatim is picking the centroid of the aerodrome/airport. I've tried to mark all the gates and roads to be "private" in order to help the router not select these little alleys and service roads in hopes that the router will always select Peña Boulevard which leads to the terminal along with all ground transportation. Even if this area is still huge, it's more reasonable that a driver will see the signs and know what they're going for instead of getting stuck on a dirt road blocked by an electrified gate...