My first attempt at extruding a city took an afternoon. Building polygons in, heights in, solids out, and it looked fine in the viewer. Then I tried to use it. The heights had three different sources, the ground was flat, and a bridge had been rendered as an office tower. New York's citywide massing model, built for the Department of Information Technology and Telecommunications with AppGeo, is a useful reference for the gap between that first demo and a dataset someone can actually work with.
The inputs, and what they really contain
Building footprints come from planimetric mapping: closed polygons with a source date and an identifier. Heights usually arrive in a separate table or raster, joined by an ID that may or may not be stable. Terrain comes from a digital elevation model. In New York, the horizontal units are US survey feet in the state plane coordinate system, and vertical units are feet as well, which is convenient until someone hands you a file in meters.
Extrusion and its assumptions
The operation is simple. Take the polygon, sample the ground elevation, lift the top by the height value, and close the sides. Then decide what height means. Above ground? Above sea level? Roof line or top of the mechanical penthouse? For massing, roof height is the usual answer, but the choice needs to be written down, because two datasets that disagree by ten feet will produce different shadows at 5 p.m. in December.
Height is not one number
Some heights come from a surface model, which includes parapets, bulkheads, and sometimes antennas. Some come from an attribute that reflects the roof deck. A single tower can have three plausible heights and no obvious way to pick one. My rule is to document the source per building where possible, and to treat the resulting error as a range, not a fact. At low sun angles, a height error of a few feet moves a shadow by many feet.
Tiling a million buildings
One citywide mesh is unusable, both for file size and for rendering. Tile the model on a grid, keep a stable ID for every footprint, and build lower levels of detail for distant tiles. Formats matter: 3D Tiles or glTF for streaming viewers, a spatial database for analysis, and a simplified solid for shadow runs. The same building should carry the same ID in all of them, or every downstream join becomes a guess.
Shadows at city scale
Shadow is where the model earns its keep. Pick a date, a time step, and a sun vector, then intersect each building with the ground and with its neighbors. Terrain matters more than people expect near slopes and waterfronts. Compute on the GPU when you can, cache the results for common dates, and publish the method alongside the output, because a shadow map without a stated time and datum is not evidence.
Keys, joins, and silent failures
Most errors in a model this size are join errors. A footprint without a height becomes a zero-height building that still renders as a flat plate. A duplicate ID attaches a tower's height to a shed. A demolished building keeps its geometry for a year. None of these throw an exception. They just make the result wrong in a way that looks normal, which is the worst kind of wrong.
Filling one missing parcel
Proposed buildings are not in the footprint file yet, which is a problem when the question is about a project that has not been built. I sketched the site boundary and asked GenAnywhere for a rough volume at the district's allowed height. It returned a clean box, which I kept in a separate layer. Generated massing is fine for a screening question. It should never be mistaken for a survey of what will stand there.
QA rules that catch the weird ones
A few automated checks catch most of the damage: heights outside a plausible range for the borough, footprint area against height, buildings that intersect terrain, duplicate identifiers, and anything taller than the tallest recorded tower. Then sample a few blocks on foot. The automated checks find the absurd; the walk finds the merely wrong.
What I would change next time
I would store height provenance per building from day one, publish a confidence flag with the geometry, version the height table separately from the footprints, and keep a change log that names what moved and when. Those are boring features, and they are the difference between a model that gets trusted and one that gets screenshotted.


Top comments (0)