Zoning rules: how do you compare blocks in GenAnywhere?
How to hold the rule set steady, compare massing and street edges, and know when a site model is enough.
You compare blocks by keeping the rule set constant and changing one variable at a time. Massing, frontage, and open space are the variables that usually move a discussion along. A generated 3D block model makes those differences visible before anyone has drawn a facade, provided you treat its heights and building types as starting points rather than answers.

1 What block-level rules actually decide
Most zoning arguments begin with a number and end with a shape. A district may allow a certain height, a certain share of the lot to be covered, and a certain floor area relative to the site. Those figures describe an envelope, and an envelope can be filled in several ways. Two blocks with identical numbers can produce a continuous street wall in one place and a row of separate slabs in another.
1.1 Separate by-right form from discretionary review
By-right rules describe what can be built without asking for anything extra. Discretionary review covers the parts a board or planning department decides case by case, including design quality, compatibility, and sometimes use mix. When you compare blocks, keep the two categories apart. A block that looks underbuilt may be waiting on a conditional approval, and a block that looks dense may have used bonuses you have not accounted for.
1.2 Read height, coverage, and floor area together
Each number on its own misleads. A generous floor area ratio with a low coverage limit pushes buildings upward. A high coverage limit with a modest height cap pushes them outward and leaves little room for yards. Read the three figures together and you get a rough sense of the bulk a rule set expects. Planning departments publish their adopted codes, and professional bodies such as the American Planning Association offer practice guidance on how those codes are applied in review. That sense of expected bulk is what you carry into a visual comparison, not a calculated yield.
2 Set up blocks you can compare fairly
Fair comparison is mostly housekeeping. If one block is drawn to the parcel line and another includes the road, the apparent difference in density comes from the drawing. Decide on a boundary convention before you open the model, apply it to every block in the set, and write it down in a single line. Someone will ask later how the set was assembled.

2.1 Match boundaries to the same rule set
Start with the governing district for each block and confirm the whole block sits inside it. Where a district boundary crosses a block, either split the block or note the overlap. Mixing a corner parcel from one district with the rest of a block from another produces a comparison that cannot be defended in a meeting. If the district has overlays, such as a historic area or a transit corridor, list them beside the block name.
2.2 Keep scale and view direction consistent
Set the camera to the same height and angle for every block, and keep north at the top of the frame. Perspective exaggerates height, so a low camera turns a six-storey building into a tower. A consistent view lets a reader compare two images without asking how they were made. When one block needs a closer look, add a second view rather than replacing the standard one.
3 Compare massing before you compare details
Massing is the part of the comparison that survives a change of architect. It covers how much building sits on the block, how tall it rises, and where it leaves gaps. Get massing right and the rest of the discussion has a frame. Skip it and every later disagreement becomes an argument about facades, materials, and renderings that should have waited.
3.1 Follow the height step along the street
Walk the street edge and note where heights change. A block that steps down toward lower buildings reads differently from one that ends in a hard wall. The step often matters more than the absolute height, because it controls how the street feels from the pavement. In a model, orbit along the frontage at eye level and check whether the transition looks abrupt or gradual.
3.2 Look at the gaps between buildings
Side yards, courtyards, and service lanes are easy to overlook in a plan drawing and hard to miss in three dimensions. A narrow gap that looks fine on paper can read as a slot canyon once buildings rise around it. Count the gaps, note their width relative to the buildings, and compare that rhythm across the set. Consistent gaps suggest a coherent block; random gaps suggest piecemeal approvals.
4 Judge frontage, corners, and open space
The street edge and the corners do most of the work in how a block is experienced. Open space does the rest. None of this requires a finished design. A massing model with simple volumes is enough to show whether a block turns its back on the street or opens onto it, and that question comes up in almost every review.
4.1 Read the street edge as a line
Draw an imaginary line along the frontage and ask how much of it is built. Long setbacks create forecourts and parking strips; short setbacks create a street wall. Neither choice is wrong, but a block that alternates between the two without reason looks unsettled. Check entrances as well. A block whose doors face a rear lot is telling you something about how it is used.

4.2 Note where open space lands
Open space can sit at the center of a block, along one edge, or in fragments between buildings. Its position decides who can reach it and how public it feels. In a comparison, mark the open space on each block and describe it in plain terms: a courtyard, a green strip, a paved plaza. The label matters less than the consistency of the description across the set.
5 Know where a generated block model stops
A site model built from map and satellite data is a fast way to get a block into three dimensions. It is not a legal record. Heights are estimated, building types are inferred, and small structures may be missing or merged. Treat the model as a conversation aid and keep the ordinance open beside it.
5.1 Treat heights and types as estimates
The estimate is usually good enough to compare one block with another, which is the whole point of the exercise. It is not good enough to settle a dispute about a particular building. When a height matters to the argument, check it against a planning record, a survey, or a site visit. Note the source next to the number so the comparison stays honest.
5.2 Check the rules against the adopted code
Codes change, and the version posted online may lag the adopted text. Overlays, planned unit developments, and recent amendments can shift what a block may build. Before you present a comparison, confirm the rule set against the current ordinance and the local planning office. The model shows form; the code decides which forms are allowed. If the model will be reused outside your team, read the authorization statement before you share the file.
6 Run a block comparison in GenAnywhere
GenAnywhere takes a mapped area and builds an editable 3D site model from satellite and map data. It identifies building footprints, estimates heights, infers building types, and picks up the vegetation around the site. You can preview buildings, terrain, vegetation, and water as separate layers, replace a single building, move or rotate it, and change its height or type. A finished view exports as GLB for 3D, BIM, GIS, and game engine workflows. These outputs are initial site context, not survey products, and they do not replace the code or the records behind it.
6.1 Select an area and build the baseline
Frame the block with enough margin to include the streets on both sides, then generate the site model. Look at the footprint pattern before you change anything. Most blocks reveal their structure quickly: a row along the street, a back lot, a corner building with a different depth. Keep that version as the baseline, and name it by rule set and date.
6.2 Rebuild the same block with one new assumption
Change one thing at a time. Raise a building, remove one, or adjust the type on a corner, then compare the result with the baseline view. A fixed camera makes the change readable. If you need to test a second rule set, duplicate the block instead of overwriting the original, so the two versions stay side by side for the meeting.
6.3 Export the comparison for review
When the set is ready, export the model as GLB and bring it into the tool your team already uses for review. Add the block name, the rule version, and the date to your notes. The export is a working file, not a submission drawing. Treat it the way you would treat a massing study: useful for the conversation, open to revision.
See how the site model workflow fits a review
7 FAQ
FAQ-1 How do I choose blocks that are worth comparing?
Start with blocks that share a district and a similar street pattern, then add one block that differs in a way you care about. That difference becomes the point of the comparison. If every block differs in several ways, the result tells you little, because you cannot say which change produced the effect. Write down the criteria before you build the models, and keep the same camera for all views.
FAQ-2 Can I change a building height in the model?
Yes. A building in the model can be moved, rotated, or given a new height or type, which makes height scenarios quick to test. Keep in mind that the starting height is an estimate from imagery, and your edited height is a design assumption. Neither one settles a legal question. Use the edit to show a range, then confirm the limits against the adopted code before the comparison goes into a formal review.
FAQ-3 Do I need survey data or a drone flight to start?
No. The model is built from satellite and map data, and the site context is meant as a starting point rather than a survey product. For a massing comparison, that level of context is usually enough to see how blocks differ. If the discussion turns on a property line, an easement, or a legal height, bring in the same records you would use for any planning submission.
FAQ-4 What do I get at the end of the comparison?
The model exports as GLB, which opens in common 3D, BIM, GIS, and game engine tools for review. Each exported model carries a permanent commercial license, though the original files cannot be resold and cannot be used to train AI models. Third-party data inside the model may carry its own terms, so check those separately. Verify the output against your own records before relying on it.
Content and technical notes
This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.
Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.
For technical questions or corrections, contact support@genanywhere.com.
Last reviewed: 2026-11-20.