DEV Community

GeoGenius
GeoGenius

Posted on

The City as a Constraint System: GenAnywhere's Data Model for Zoning, Corridors, and Public Space

Most planning software treats a city plan as a pile of layers: a zoning polygon here, a street centerline there, a park boundary somewhere else. The layers coexist but never argue. GenAnywhere takes the opposite position. It models an urban plan as a set of typed entities bound by invariants, so that a zoning change that contradicts a street section, or a street section that starves a public space, fails validation the moment it is entered. The plan becomes a constraint system, and the constraint system is where the actual planning intelligence lives.

The entity vocabulary

At the base of the model sit four entity families. A District is a bounded area carrying an identity, an existing-conditions baseline, and a vision statement. A Corridor is a linear entity describing a street or trail by its cross-section: walking width, planting zone, lane count, curb treatment, and stormwater strategy. A PublicSpace is a polygonal entity typed as park, square, plaza, pocket park, or linear park, each type carrying its own minimum-size and access invariants. A Parcel is the smallest unit, carrying a housing type drawn from a spectrum and a height envelope.

What makes these entities typed rather than decorative is that each type constrains its fields. A Corridor typed as green alley cannot carry four travel lanes. A PublicSpace typed as pocket park cannot exceed its area ceiling. A Parcel on a main-street Corridor inherits a ground-floor activation requirement automatically. The type is the policy, encoded once and enforced everywhere.

Invariants as the planning intelligence

The interesting work happens in the invariants that bind entities together. GenAnywhere ships a family of them, and planning teams extend the set per project. A canopy invariant requires that the tree planting zones across a District's Corridors sum to a target coverage, so removing a planting zone somewhere forces an addition elsewhere. A connectivity invariant requires every Parcel to reach a PublicSpace within a walking threshold, which is how the fifteen-minute neighborhood stops being a slogan and becomes a checkable property. A stormwater invariant requires that the curb strategies along a Corridor absorb the runoff its impervious area generates, tying street design directly to hydrology.

Validation runs continuously. Change a Corridor's lane count and the connectivity and stormwater invariants re-evaluate immediately; if the change breaks one, the edit is rejected with the specific invariant named. Planners report that this changes their behavior in a useful way: instead of discovering contradictions at a public hearing, they discover them at the keyboard, seconds after introducing them.

Street sections as first-class geometry

The Corridor entity deserves special attention because it is where policy meets experience. Rather than storing a street as a centerline with a width attribute, GenAnywhere stores the full cross-section as an ordered sequence of zones from building face to building face. That ordering is what makes the section renderable and comparable: two Corridors can be diffed zone by zone, and a road diet is expressed not as a vague narrowing but as the removal of a specific travel zone and the addition of a median planting zone and two curb-extension zones.

Because the cross-section is ordered geometry, the renderer can produce a street-level view of any Corridor at any station along its length, draped with the District's building typologies. This is the asset pipeline in miniature: entities in, validated scene out. The same pipeline that produces a review graphic for a council packet produces the illustrative views used in public engagement, which guarantees that what the public sees is geometrically the same street the engineers validated.

Housing spectrum and the missing middle

The Parcel entity's housing type is drawn from an ordered spectrum rather than a flat list, ranging from single houses through duplexes, fourplexes, courtyard buildings, and small apartment blocks up to mid-rise. The ordering matters because transition invariants reference it: a Parcel's height envelope may not jump more than a fixed number of rungs above its neighbor across a shared lot line. This single invariant reproduces the gentle stepping that makes older American neighborhoods feel coherent, and it prevents the cliff-edge transitions that generate most infill opposition.

Ground-floor behavior is handled the same way. A Parcel fronting a Corridor typed as main street inherits an activation requirement; the same Parcel fronting a green alley inherits a service-face requirement instead. The requirement travels with the relationship, not with the parcel, which is why rezoning a block in GenAnywhere automatically re-derives its frontage obligations.

Rendering, review, and the asset pipeline

Every validated entity set can be rendered at three scales: the District aerial for orientation, the Corridor street-level view for experience, and the PublicSpace vignette for character. Renders are deterministic given the entity set, so a review graphic can always be regenerated exactly, and a plan amendment produces a diff of renders rather than a new unrelated illustration. Engagement teams use the diff directly: here is the street as validated today, here is the street as the amendment would make it, same station, same light, same lens.

The practical consequence is that the plan document, the validation state, and the public imagery are three projections of one model. Nothing can drift out of sync because there is only one source. For planning teams tired of reconciling a memo, a map, and a rendering that disagree in small embarrassing ways, that single source is the entire value proposition. The city, in GenAnywhere's framing, is not a picture. It is a system of promises that check each other, and the pictures are just what the promises look like from the sidewalk.

Top comments (0)