How to Read Local City Design Results for Smarter Planning

Verify Baseline Geometry First

Most city design reports present a single number—FAR, height, unit count—and call it a day. That number hides the real story: whether the building casts a shadow over a playground, whether the street feels empty at 6 PM, or whether the “dense” tower actually houses fewer people than the walk-up it replaced. This guide shows you how to reverse-engineer those aggregate metrics into concrete outcomes using free GIS tools and public data.

The shift is recent: municipalities and advocacy groups now routinely publish zoning shapefiles and design review documents online, and QGIS has matured into a reliable, scriptable platform for spatial analysis. That means you no longer need a planning degree or expensive software to verify what a proposal will do to your block. You need a workflow—start with raw geometry, overlay environmental layers, then stress-test with household data. That workflow is what follows.

Decode Density Without Falling for FAR

The first number to demand from any design result is not the Floor Area Ratio — it is the unit count. FAR tells you how much floor area a building may hold relative to its lot, but it says nothing about how many people will live in that space. Same FAR, same lot, same shadow, same street-level facade — completely different demands on transit, schools, and retail. Read the diagram, then read the section, then read the unit mix. In that order.

To convert FAR into a realistic population estimate, you need two more numbers: the gross floor area and the average household size. Divide that by the average household size from the U.S. Census American Community Survey block group data for the surrounding neighborhood, and you get a resident count that actually means something for sidewalk width and bus frequency. Most municipal portals publish the zoning designation and lot dimensions; the ACS table is free to download. The math takes ten minutes and it will separate a genuine density increase from a facade of it.

The trap is that high FAR also triggers heat-island scrutiny regardless of what you build. Urban morphology research published in Landscape and Urban Planning identifies floor area ratio and tree canopy coverage ratio as the most important predictors of daytime mean radiant temperature and nighttime physiological equivalent temperature. A project that maxes out FAR to win density bonuses can bake the block even if it includes a token green roof, because the ratio of built mass to open space drives the thermal outcome more than the vegetation itself. If the design result shows a high FAR, check the tree canopy plan before you celebrate the sustainability credits.

Density bonuses deserve particular suspicion. One recurring theme in r/urbanplanning threads is that these incentives often reward developers for providing publicly accessible plazas that are privately owned and effectively gated — the "public benefit" score inflates without changing the physical footprint or the number of units. The bonus buys the city nothing in population terms, yet it lets the developer push FAR higher, which then worsens the thermal profile. When you see a density bonus in the design result, check whether the city received a binding easement or just a revocable permit for the claimed public space.

For a before-and-after block comparison, extract three metrics from the design result: FAR, building height, and setback distance. Compute the change in gross floor area using the formula above, then compare that against the change in unit count. A proposal that increases GFA by 40 percent but adds only 10 percent more units is not delivering density — it is delivering larger flats. That distinction matters for everything from parking demand to school enrollment projections, and it is the single most common discrepancy between what a render promises and what a neighborhood actually experiences.

One practical check: if the city runs a public zoning portal, pull the current designation and compare it to the proposed FAR in the design result. A project that asks for a variance or a bonus should show its math in the application — if the unit count is missing from the summary, that omission is a red flag, not an oversight. You can also benchmark the design against the LEED for Neighborhood Development scorecard, which credits walkable streets, compact development, and mixed-use density; a project that scores well on that rubric usually has its unit mix and street-level activation worked out, not just its floor area.

Your next step today: open the design result, find the lot area, multiply by the stated FAR, and divide by the ACS average household size for the block group. Write that number next to the render. If the resident estimate is lower than the current occupancy of the site, the "density" is a mirage — and you have the arithmetic to prove it at the next public hearing.

Overlay Transit and Flood Zones

Most static PDF maps in a design review package are already obsolete by the time you open them, because they flatten the proposed building onto a single base layer and hide every conflict that lives below or beside it. The fix is to re-plot the design shapefile yourself in QGIS and run an automated overlay against transit corridors and flood zones, which turns a ten-minute visual scan into a repeatable spatial query that flags every intersection the renderer chose not to show.

QGIS is free, open-source GIS software (GNU GPL) that supports buffer construction, spatial querying, and geoprocessing, making it the primary tool for this kind of work. The standard workflow is to add base layers for parcels and zoning, import the proposed design shapefile, set layer transparency, and run a spatial query to identify intersections with transit or flood polygons. The QGIS Training Manual covers the core steps—creating basic maps, adding layers, navigating the map canvas, and classifying vector data—but the Processing Modeler is where the real leverage sits. You can chain the overlay operation into a single automated model that runs the same conflict check on every new design revision, which matters because developers revise massing weekly and the PDF you reviewed on Monday is already stale by Friday.

The actionable rule is simple: if a proposed building’s footprint intersects a 100-year flood plain polygon, the design likely requires expensive elevation adjustments or flood-proofing materials that never appear in the aesthetic render. That intersection is the single highest-cost hidden variable in a design result, because it triggers FEMA compliance, insurance rate changes, and foundation engineering that can add months to the approval timeline. Most municipal GIS portals publish flood plain shapefiles as open data, so you can pull the polygon directly rather than tracing it from a static map. The same logic applies to transit corridors: a design that looks transit-oriented on paper may actually sit 400 meters from the nearest station entrance when you measure the walking path rather than the straight-line distance.

One caveat that field threads consistently raise: OpenStreetMap data standards are excellent for street geometry, but you should verify street widths and block perimeters manually when re-plotting designs, because open-source footprints can lag behind recent municipal demolitions or new construction. A building that was demolished last quarter may still appear as a solid block in OSM, which will throw off your setback calculations and shadow studies. Cross-check against the city’s own parcel layer before you trust any measurement derived from open data.

For a practical next step today: download the flood plain shapefile from your city or county GIS portal, import it into QGIS alongside the proposed design shapefile, and run a simple intersection query. If you get any hits, request the elevation certificate and flood-proofing specification from the developer before the next public hearing—that single document will tell you more about the project’s real viability than the entire render package.

Assess Thermal Comfort and Shadows

Most design reviews treat the shadow study as a single document, but the only diagram that matters for pedestrian impact is the winter solstice one. Summer diagrams flatter the proposal because the sun arcs high and buildings cast short, contained shadows. At the winter solstice, the sun stays low, so a six-story building can throw a shadow that stretches across an entire plaza and lingers there from mid-morning until early afternoon. If the design result only includes a summer solstice diagram, ask for the December 21 equivalent before you sign off on any public space that faces north or northeast.

The structural bulk of the building, not just its height, drives the heat problem. Research from Bologna’s urban heat island studies shows that building density and mean building height influence air temperature independently of vegetation cover; the mass of the built form traps heat even when mature trees are present. The trees help, but they do not cancel the thermal mass of the surrounding walls. When you read a design result, separate the canopy coverage ratio from the building geometry and evaluate each on its own terms.

Sky View Factor is the metric that explains why wider streets fail to cool. The common assumption is that a wider street lets more sky in, so heat escapes and the canyon cools. That only works if the building height stays constant. If the street width and the building height both increase proportionally, the Sky View Factor stays the same and the canyon effect persists, trapping heat and pollution at the pedestrian level. A design that widens the road but also adds two stories to the flanking buildings has not improved thermal comfort; it has just moved the same problem into a larger envelope. Check the height-to-width ratio, not the street width alone.

Building height is a function of floor height and number of floors, which means two designs with identical FAR can produce very different shadow impacts. A six-story building with 14-foot floor-to-floor heights casts a longer shadow than a six-story building with 10-foot floors, even though both have the same footprint and unit count. The section diagram reveals this; the height number on the cover page does not. When you review a design result, find the section cut that shows the ground floor and the first few floors, and measure the actual floor-to-floor heights. If the proposal uses tall ground-floor retail spaces, the shadow impact on the sidewalk and any adjacent park will be worse than the FAR suggests.

Tree shading reduces physiological equivalent temperature in urban canyons, which is the metric that determines whether outdoor seating is usable in summer. A design with a high FAR and no corresponding increase in tree canopy coverage ratio will produce a significant rise in nighttime PET, making patios and sidewalk cafes unusable during the warm months. The counterintuitive part is that the trees matter most at night, when they block the longwave radiation re-radiated from the building walls. A canopy that shades the pavement during the day is good, but a canopy that interrupts the view of the wall from the street is what actually lowers nighttime PET. Look for tree placement that breaks the line of sight between the building facade and the pedestrian zone.

Compare two options to see the tradeoff in practice. Option B delivers more housing units, but it will have higher ambient temperatures and worse pedestrian comfort because the structural bulk traps heat and the sparse canopy cannot interrupt the radiation from the walls. The planning decision is not which one is denser; it is which one meets the thermal comfort threshold for the intended use. If the design result shows a high FAR and a low canopy ratio, flag it for thermal review before you approve the environmental assessment.

One practical check for your next review: open the design result in QGIS, set the building layer to 50% transparency, and overlay the tree canopy layer. If the canopy polygons do not intersect the building facades at the pedestrian level, the shading benefit is minimal. Then run the same overlay for the winter solstice shadow polygon and the nearest transit stop. A bus shelter that loses direct sun at 8 AM in January becomes a passenger comfort issue that generates complaints all winter. That single spatial query, done in under ten minutes, will tell you more about the real-world impact of the proposal than the entire environmental review narrative.

Case Study: Reading the 'Infill' Proposal

The quickest way to kill a bad infill proposal is to run the parking math before you read the design narrative. Extract the Floor Area Ratio and setback first—assume FAR 2.0 and a 10 ft setback—then cross-check those against the block group's actual household profile from the US Census ACS, which publishes household size and car ownership at that granularity. As of the 2024 ACS 5-year estimates, the average household size in that block group is 2.2 people, and car ownership runs 0.8 cars per household. That is the baseline the developer's "low impact" claim has to survive.

The decision rule here is blunt: reject the design unless the developer either reduces unit size to fit more affordable units or increases the parking provision, because the current math contradicts the "low impact" narrative. A 12.5-unit building with 10 parking spaces is not low impact; it is deferred impact. The same logic applies to any density bonus the report touts—when you see a density bonus in the design result, ask what the city actually received in exchange. If the bonus bought a few trees but added 15 units without adding parking or transit capacity, the trade is a net loss for the neighborhood. One practical check: if the city runs a public zoning portal, pull the current designation and compare it to the proposed FAR before you trust any measurement derived from open data.

You can verify the street width and block perimeter yourself using OpenStreetMap, which is free and accurate enough for a first-pass review, though accuracy varies by city. Cross-check the building footprint against the city's own parcel layer to catch any demolition lag in the open-source data. The shadow-on-transit-stop check is the one most planners skip, and it is the one that generates the most post-approval complaints—a bus shelter that loses direct sun at 8 AM in January becomes a passenger comfort issue that generates 311 calls, even if the summer solstice diagram looks fine. If the design result only includes a summer solstice diagram, request the December 21 equivalent and also ask for the 8 AM and 4 PM sun angles to verify the transit-stop impact.

Your next action today: pull the ACS block group data for the site in question, run the unit count and parking stress test with the formula above, and compare the result against the proposal's stated parking provision. If the numbers don't close, the rendering is irrelevant.

Automate Your Own Review Workflow

Real municipal data often arrives with projection mismatches or missing attributes, so check the layer’s coordinate reference system against the city’s standard before you trust any intersection result. A mismatch between NAD83 and WGS84 can shift a footprint by several meters—enough to create a false flood-zone hit or miss a real one.

For anything you plan to submit as a public comment, do not run the overlay manually. Use the Processing Modeler to chain the steps: Input Design Shapefile, Intersect with Flood Zone, Output Conflict List. The Modeler lets you connect these operations so the output of one feeds the next, which removes the manual error that creeps in when you re-select polygons by hand. It also creates a citable record: the model itself documents your method, and the output layer shows exactly which parcels intersect. One practitioner on a municipal GIS forum describes this as the difference between “I think it overlaps” and “here is the intersection layer and the model that produced it.” The latter survives a public hearing; the former gets dismissed as an opinion.

Date-stamp every source layer before you export anything. Municipal GIS departments update their parcel and zoning layers quarterly, and an old baseline invalidates your analysis even if the geometry is correct. Write “As of August 2026” in the metadata or the comment header, and pull a fresh shapefile from the city’s open-data portal on the day you run the model. If the city updates its flood map mid-review, your comment will be judged against the new layer, and an undated analysis looks like an error rather than a snapshot. This is a routine failure mode in public comments: the analysis is sound, but the data is stale, so the whole submission gets discounted.

What to do next

Use the design results as a starting point for deeper verification, not as a final answer. Cross-check the key metrics against independent data sources and your own spatial analysis before drawing conclusions.

By following these steps, you transform a static design result into a dynamic, verifiable analysis that holds up in public review. The goal is not to oppose development, but to ensure the numbers match the narrative before the city makes a decision.

Also worth reading: Vatican City Urban Planning Challenges in the World's Smallest Sovereign City-State · A Close Look At AI Urban Planning At Salt Lake City City Creek Landing · 7 Key Urban Planning Applications of Generative AI 2024 Survey Results Revealed · 7 Essential Urban Planning Books That Shaped Modern City Design From Jacobs to Mumford

Sources: data, wikipedia, illustrarch, researchgate, iotforall