從地圖選取範圍建模丹佛國際機場：六條跑道與立體結構

I have been building a small 3D model of Denver International for a side project, mostly to test how much of a large facility you can reconstruct from a map selection. The first pass looked great. The second taught me that a footprint is not a model.

The selection box problem

I opened GenAnywhere, selected the whole airport, and let it generate a massing model. What came back was clean: a cluster of white peaks in the middle, six long runways laid out across a flat plain, and the concourse piers between them. At city scale, it reads exactly like the satellite view.
Then I tried to place the underground train. There was nowhere to put it. The apron was a solid surface, the terminal was a roof with no floor beneath it, and the deicing pads were just more gray pavement. The model was correct from above and empty from the side.
GenAnywhere generates geometry from an area you draw on the map. It is fast and a good first skeleton. It is not a survey, and it does not know what happens below the surface.

A runway number is a bearing

Denver has six runways. The longest, 16R/34L, runs 16,000 feet. The others carry identifiers like 17L/35R, 07/25, and 08/26. Those numbers are not names. They are magnetic headings divided by ten, rounded to the nearest ten degrees, with L, R, or C for position.
That matters in a data model. Magnetic north moves, slowly but measurably, and runway designations are occasionally changed to match. If you use the painted number as a primary key, a routine magnetic update becomes a migration. Store the true bearing, the magnetic variation, and the date range instead. Let the label be derived.

The airport is a graph, not a polygon

Once I stopped treating the airport as one surface, the structure became obvious. The terminal connects to the train. The train connects to three concourse stations. Each concourse connects to gates, each gate to a jet bridge, each bridge to an apron stand, and the apron connects to a taxiway network that feeds six runways.
The train is the part most surface models miss because it runs in a tunnel under the apron. You can have a beautiful terminal mesh and still be unable to answer a simple question: how long does it take to get from a gate in Concourse B to the threshold of 16R at eight in the morning?

Build it in layers

I ended up with three layers. The surface layer holds runways, taxiways, aprons, service roads, and parking. The vertical layer holds the terminal roof, the concourse buildings, the control tower, and the jet bridges. The below-grade layer holds the train tunnel, the stations, baggage handling, and utilities.
Each layer has its own level of detail. At city scale the roof is a silhouette with peaks; at gate scale it is fabric panels and cables. Mixing those levels in one mesh is how models become unusable.

Snow is a network problem

Denver's plow crews can bring a runway back to bare pavement in roughly a quarter of an hour, working in a staggered formation, but that only matters if aircraft can also reach a deicing pad, get sprayed, and rejoin the queue. Runway length is not the constraint on a storm day. Pad capacity and taxi routing are.
A model that stores only runway polygons cannot simulate that. A model with nodes, edges, and capacities can at least ask the question.

Three checks before you trust it

First, check runway geometry against the label. Compute the bearing of the centerline and compare it with the painted designation. If they disagree by more than a few degrees, something is wrong with your source data.
Second, check the terminal-to-concourse link. If your model has no train stations, it is a diorama, not an airport. Every gate should be reachable from the terminal through a known path.
Third, store elevation. Denver's field elevation is 5,434 feet, and altitude affects aircraft performance, runway length requirements, and even the way you interpret a published obstacle chart. A flat zero-elevation plane is a convenient lie.

What the selection box is good for

I still start with GenAnywhere. It gives me the site boundary, the roof silhouette, the runway layout, and enough context to see how the pieces sit on the plains. That saves a day of tracing footprints by hand.
After that, the model has to be rebuilt from better sources: airport diagrams, surveyed coordinates, and operational data. The selection box gets you the shape. The graph gets you the airport.