Regional airports are full of buildings designed for a different decade of travel. The terminal I worked on last month opened in 1974 with four gates and a concrete canopy that leaks in exactly two places. The authority wants two more gates and a new security checkpoint. They asked for a model they could open in a meeting, not a full BIM.
I built it over three evenings. This is the pipeline, including the parts that failed.
Scope and ground rules
The model had to answer three questions. Does a two-gate addition fit on the east apron? Does the new checkpoint block the view from the curb? Where does water go if the apron is regraded?
I set rules first. One coordinate system. One unit, feet. No detail below six inches unless asked. Every asset gets a source note. Without those, the model becomes a pile of files that look right and do not line up.
Halfmaps for context
Halfmaps built the site context. I pulled the terminal footprint, apron, and taxiway centerlines from map data, then added photos of the curb and airside facade. The result is a rough mesh with roof heights, enough to see the terminal against the tower and hangars.
The map data puts the whole roof at one height, but the building has three roof levels. I added the high roof and low canopy by hand. Trusting the mesh would have left the second-floor windows floating.
Civil3D for the apron
Civil3D handled the ground. I built a surface from the apron contours, added the taxiway edge, and checked grades against the airport's standards. The existing apron slopes toward two inlets near the fuel farm, which is fine until you add 140 feet of pavement for the new gates.
The new pavement raised the low point about nine inches, enough to pond water at the joint between old and new concrete. I adjusted the cross slope and added a trench drain along the joint. That is what the model is for, and what gets missed when the site is a flat plane.
Cityweft for the terminal massing
Cityweft generated the building blocks. I imported the terminal footprint, set heights for the concourse, ticketing hall, and canopy, and produced simple massing of the terminal and surrounding hangars. The blocks are not architecture. They are a way to see the terminal in its setting.
That matters at a regional airport because everything is visible from somewhere. The massing showed the new gates would be hidden from the curb but very visible from the long-term lot. It also showed the tower lining up with the new concourse roof, which looked intentional and was not.
GenAnywhere for the addition
For the addition I used GenAnywhere. I drew a box over the east apron, set it to two stories, and let the AI generate building volume inside it. The tool fills a mapped area with massing, which is useful when the question is fit rather than floor plan.
The first box ran into the taxiway safety area. I pulled the edge back 50 feet and ran it again. The second fit, but the hold room was too shallow for two gates. The third pushed the box north and added a pier, which is the scheme the airport is now studying.
Tripo3D for the jet bridge
The terminal has two jet bridges from the original build. They are unusual, with a fixed walkway that drops before the cab, and I wanted that geometry.
I photographed them from the apron and ran the images through Tripo3D. The mesh came back with the right proportions and a slightly melted handrail. Scale was the problem: Tripo3D exports in meters, my scene is in feet, so the first import was three times too large. A five-minute fix if caught, a confusing afternoon if not.
The manifest
Every asset got an entry: name, source, units, coordinate system, date, and an accuracy note. The manifest is a plain text file. It is not glamorous, but it is why the model survived a revised apron survey.
The rebuild took 40 minutes. Halfmaps re-imported, the Civil3D surface was replaced, massing regenerated, and the box re-run with the new boundary. The bridge was reused. Two things broke: the trench drain lost its connection to the new surface, and the massing blocks shifted with the footprint. Both were caught in ten minutes because the manifest told me what depended on what.
What I would change
Start with the coordinate system, not the geometry. Photograph the jet bridge before you need it. And do not let a map mesh set your roof heights.
The model is not a terminal. It is an argument about fit, drainage, and sightlines that fits in a laptop bag. For a small airport with a small budget, that is the right size.
Top comments (0)