02UrbanPlanning — Urban Planning Studio

Install, then try a demo town

The plugin adds a toolbar button and a Plugins → 02UrbanPlanning menu with three entries: 02UrbanPlanning studio (opens the panel), Zoning Code… and Manual (this page).

Your first five minutes

The plan database: one GeoPackage

A plan is one GeoPackage. It holds three plan layers that share one code list, the development layers generated from them, the code tables every layer looks up, and the layer styles, so the plan opens styled in any QGIS. Copy the file and you have copied the plan.

Plan layers (what the planner decides)

Development layers (generated from the plan)

Code tables (the unified database)

Unit and extension tables

The studio panel

The panel has a header with the plan name and horizon and an icon rail with five pages. A Save edits button appears in the header whenever a plan layer has unsaved edits; it writes every pending edit of the plan layers to the GeoPackage. The ? button at the foot of the rail opens this manual.

Restyle all re-applies the catalogue styles (land-use colours, road-class lines, point markers, labels, value maps for coded fields, read-only generated fields and the 3D extrusion of buildings) and saves them as the default style in the GeoPackage.

Draw, step by step

The Draw page carries the plan in numbered steps. Every step follows the one before it: move a road and the blocks, their land use and the balance follow.

1 · Plan area

The plan boundary closes the blocks at the plan edge.

• Draw the plan boundary: click the corners, right-click to close. A new boundary replaces the current one.
• Boundary from selection: select polygons on any polygon layer (made active) and their outline becomes the plan boundary, reprojected to the plan CRS.
• Clip streets at the boundary (on by default): the right-of-way, kerbs and street length stop at the boundary. Without a boundary, blocks are the areas the streets enclose.

2 · Streets

Pick a road class from the chips (each shows its right-of-way in metres), check the cross-section, and draw centrelines. Right-of-way, junction corners, kerbs and blocks are built for you.

• Road class chips: Expressway 60, Arterial 40, Minor arterial 30, Collector 20, Local 15, Access lane 10, Pedestrian 10, Greenway 6 (see section 8). The tooltip lists the right-of-way, carriageway, sidewalks, median, kerb radius and design speed.
• Cross-section: a live drawing of the section and five fields: ROW (property line to property line), Carriageway (both directions), Median, Sidewalk (each side) and Kerb radius (the block corner gets the kerb radius plus the sidewalk). A new road takes these values; every road keeps its own widths in the network layer.
• Draw road: click points; they snap to roads and the boundary. Shift locks the angle to 15° steps, right-click or Enter writes the road, Backspace removes the last point, Esc clears. Where the new road meets or crosses existing roads a shared vertex is inserted on both, so the junction is real.
• Draw curved road: start, a point on the curve, end; the third click writes a circular arc.
• Move junction / bend road: drag a junction and every road vertex there moves together; drag a road elsewhere to bend it at a new vertex. Blocks follow on release.
• Apply class to selected roads: gives the selected centrelines the class and cross-section above.
• Undo the last road edit (the same as Ctrl+Z on the network layer) and Rebuild now.
• Rebuild while editing roads (live rebuild, on by default) and Kerb lines (on by default). A status line reports roads, junctions, blocks, blocks without a use, street length and the rebuild time.

More street tools

• Draw road with rounded corners (next to the curved road): click the corner points as for a straight road; every corner becomes a tangent arc of the Corner radius (default 30 m), and a short segment takes the largest radius that fits.
• Dead ends: None, Turning circle or Hammerhead at every road end that stops inside the plan, sized by the road class: circles of 8–14.6 m kerb radius, hammerheads with 12–18.3 m arms. 14.6 m and 18.3 m are the fire-apparatus turnarounds of the International Fire Code, Appendix D; the smaller sizes are working defaults for refuse trucks. Roads that end on the boundary or run out of the plan get no head.
• Right-of-way width labels: writes the width (20 m) on the centrelines, once per connected group of roads of the same width; road names are kept.

2b · Junctions

Every junction is first built as an ordinary crossing with rounded corners. Pick a solution from the icon row, then click a junction: a small window shows its parameters with plausibility notes and the source of the defaults, and the solution is stored in plan_junctions. It is rebuilt with the plan and follows the junction when it moves; it goes away when the junction does, and comes back with an undo. A click away from a junction (where fewer than two roads meet) is refused with a message. Remove solution makes a junction an ordinary crossing again. Details and default values in section 8.

Under the buttons the section reports the number of solutions and one warning line for junctions that are too close along a class (for example 5 arterial junctions closer than 200 m); Show zooms to them and selects their roads.

3 · Land use

Pick a use from the palette (grouped by colour family), then click or drag across blocks: every block the cursor crosses takes the use. Blocks that still need a use are drawn with an orange dashed outline. The tooltip of each swatch shows the code, the name, the description and the main rules (FAR, coverage, storeys, density, typology).

• Apply to selected blocks: gives the chosen use to the blocks selected on the zoning layer.
• Split a block: draw a division line across a block. It may stop a little short of the edges (it is extended by 2.5 m). Both parts keep the use; give one of them another.
• Number blocks: numbers blocks from top-left to bottom-right and keeps existing numbers; Shift+click renumbers every block. Block labels read the land-use code and the number (for example R2 / B7).
• Clear the use of the selected blocks.

Changing a block's land use clears the rule overrides typed on that block (FAR, coverage, storeys, height, density, typology), because they belonged to the old use.

Style painter

Three buttons under the palette copy a block's decisions to other blocks. Pick a block's style (eyedropper): click a block and its land use and rule overrides (FAR, coverage, storeys, height, density, typology) become the brush. Paint the picked style: click or drag across blocks and they take that land use and those overrides. Copy rules to the selection: only the overrides go to the selected blocks; each keeps its own land use.

3+ · Drawing aids

Construction helpers under the land-use step. Lines go into the network through the edit buffer, so Ctrl+Z undoes them and the blocks follow. Draw as sets whether parallel, perpendicular, angle and offset lines become roads (with the class of step 2) or division lines; Distance (default 60 m, 0 = follow the cursor), Strips (with across) and Angle snap (off, 5°, 15°, 30°, 45°, 90°) set the aids.

U · Planning units

Neighbourhoods, districts, sectors or quarters, superblocks and delivery phases over the blocks, each with its own population, homes and jobs. Give a name (optional) and a kind, then Draw a unit (click the corners, right-click closes) or Unit from selected blocks (the selected blocks and the streets between them become one unit). Number units numbers them top-left to bottom-right (Shift+click renumbers all), and Unit balance fills a table of area, people, homes and jobs per unit (buildings where they exist, otherwise the zoning-code capacity). Every block belongs to the unit it overlaps most; click a row to go to the unit.

4 · Overlays

Overlays are boundaries over the land use: heritage, hazard, phasing and special areas. Pick an overlay, then draw its area on the map (right-click closes). Overlays are stored in plan_zoning with origin = overlay, drawn above the land use with a dashed outline and a light diagonal hatch in the overlay colour, and never change the land budget. The ten types are listed in section 9.

5 · Points

Facilities, stops and landmarks: pick a type and click on the map (clicks snap to the network). Each point gets the type's name, which you can edit. The 21 types are listed in section 9.

6 · Parcels

Blocks are subdivided by the lot width, lot area, depth and frontage of their use with the bundled ParcelFlux engine; public uses become one lot per block. Choose Every block with a use or Selected blocks, the Width variation (0–40 %, lot widths vary randomly by ±that share) and the Seed (same seed, same parcels), then press Generate parcels. Details in section 10.

7 · Buildings

Setbacks, site coverage, FAR, storey and height caps and the typology of each use shape the buildings; residents and jobs are counted on them. Choose Every parcel, Selected parcels or Parcels of selected blocks and press Generate buildings. 3D view opens a 3D map view in which buildings are extruded by their height. Details in section 11.

Two options and a comparison sit above the button:

• Tower podium: Mixed use & commercial (default), Every tower or No podiums. A podium is two storeys along the street with the tower set back 3 m above it.
• Chamfer block corners (on by default): perimeter blocks and corner rows turn the rounded street corner into a short straight facade; off, the building follows the curve of the kerb.
• Compare typologies: select one numbered block on the zoning layer; every typology is tried on its parcels without writing anything, and a table compares floor area, coverage, storeys and homes. ★ marks the form with the most floor area that still builds on nine lots in ten. Apply to block stores the chosen typology as the block's override and rebuilds its buildings.

7+ · Site plan

Lays out every built lot (or the selected parcels or blocks): parking by the zoning-code rule (spaces per 100 m² of floor area), paths and plazas, gardens, trees and play areas, written to plan_site. Parking is Surface, then underground (surface bays first, a basement for what does not fit), Surface only (the rest is reported as a shortfall) or All underground. Tiles show the parking provided, the shortfall, trees and play areas. Generate the buildings first; re-subdividing a block removes its buildings and site elements, since they stood on the old lots.

8 · Balance

Live plan figures (population, dwellings, jobs, blocks without a use) and a bar of the land shares by colour family. Open the balance switches to the Balance page.

Under the quick balance a note compares the plan capacity with the target population and shows the share of residents within walking distance of every amenity, once a projection or an accessibility run exists (section 15).

Saving and live rebuild

The live rebuild watches the network layer. When a road, the boundary or a division line is added, moved, deleted or changed, the streets, kerbs and blocks are rebuilt after a short pause (about a third of a second), so a quick series of edits triggers one rebuild. Blocks keep their identity: each new block takes the attributes of the old block it overlaps most; when one block becomes two, both halves keep the land use and the larger half keeps the number.

The Zoning Code

The Zoning Code window (Code page, or Plugins → 02UrbanPlanning → Zoning Code…) holds every rule the plan uses. Values are stored in the plan GeoPackage (plan_zoning_code) and drive the parcels, the buildings and the plan balance. Press Save to write them; the zoning and building styles are refreshed. Regenerate the buildings to apply new rules to them.

Tabs

Every rule explained

Block overrides

Six rules can be typed on a block in plan_zoning: far, coverage, max_storeys, max_height, density and typology. A value typed on a block overrides the code for that block only; an empty field uses the code. Overrides are cleared when the block gets another land use.

The Code page also offers presets (Generic, Low-rise suburban, Compact city), JSON import and export, and a legend preview (section 14).

Land-use catalogue: 37 codes in LBCS colour families

Colours follow the convention planners read worldwide, the colour families of the APA Land-Based Classification Standards (LBCS): residential in yellows to browns by density, mixed use in orange, commercial in reds, industrial in purples, public and institutional uses in blues, parks and open space in greens, transport and utilities in greys, rural and natural land in pale olive. Within each family the tones are tuned so neighbouring classes stay distinguishable on screen and in print. Every colour can be changed in the Zoning Code; hatched codes carry a pattern over the fill.

Zoning-code defaults

The working defaults every new plan starts from. Replace them with your local regulation in the Zoning Code.

Road classes and the network engine

Eight functional classes. A new road takes its class's cross-section; each road keeps its own widths in plan_network, so a section can be changed road by road. Streets are generated into plan_zoning as land use T1 (street right-of-way), expressways as T2 and greenways as P5.

How streets, kerbs and blocks are built

1. Junctions. Points where two or more centrelines meet (shared ends, T-ends and crossings, within 5 cm) are junctions.
2. Right-of-way. Each centreline is buffered by half its right-of-way with flat ends. Where a centreline ends on another road its end gets a disc of the same half width, so L-corners and T-junctions close cleanly; dead ends stay square.
3. Junction corners. At every junction the right-of-way is closed locally with a radius equal to the largest kerb radius plus sidewalk of the roads that meet, which fills the re-entrant corners with true circular arcs. Only fillet-sized pieces near the junction are kept, so narrow blocks elsewhere are never swallowed.
4. Streets by class. The right-of-way is split by class, higher classes first, so the junction square belongs to the major road.
5. Kerbs. The same is done for the carriageway with the kerb radius. Medians are cut out and opened at every junction where another road joins, with rounded noses; a plain continuation of the same road keeps its median.
6. Blocks. Plan area minus right-of-way (or, without a boundary, every area the streets enclose), split by division lines. Leftovers smaller than 25 m² or thinner than about 1 m are slivers, not blocks.

Junction solutions

A solution is a point in plan_junctions (solution, params as JSON, name, notes) applied on top of the steps above on every rebuild. Its islands are written to plan_zoning as street land with the class ISL and the land use P5, so the balance counts them as green buffer, and blocks + streets + islands still add up to the plan area. All dimensions are editable per junction; the defaults are working values to check against your local design standard.

Junction spacing. After every rebuild, at-grade junctions closer than a minimum along their class are reported: expressway 1,000 m, arterial 200 m, minor arterial 120 m (working defaults in the order of unsignalised access spacing in access-management practice, e.g. the TRB Access Management Manual, 2014). Override them per plan with the setting junction_spacing_<CLASS>. At-grade junctions on an expressway are flagged too.

Local rebuild

The live rebuild remembers the previous result and rebuilds only a window around what changed: streets, islands and kerbs are patched inside it and every block touching it is rebuilt whole, with its land use and number. The result is the same as a full rebuild (a stress test checks this after every one of dozens of random edits). A full rebuild is used for the first rebuild, after an option change, for boundary and division-line edits, for changes reaching more than half the plan, and for plans with fewer than 40 roads. A full rebuild of a big plan shows a progress window with Cancel, which leaves the plan as it was.

Blocks removed by an edit are remembered in the plan: when an undo or a redrawn road brings a block back in the same shape, it gets its old land use, overrides and number again.

Overlays and point types

Overlays (10)

Point types (21)

Point types marked with an amenity group belong to that provision family; the Balance page measures provision by zoned land.

Network line kinds

plan_network stores one kind per line: road (road centreline), boundary (plan boundary), division (land-use division line), overlay (overlay boundary), rail (railway), waterway (waterway), utility (utility line), kerb (kerb line (generated)). Road centrelines, the boundary and division lines drive the rebuild; railways, waterways and utility lines are drawn and styled but do not cut blocks.

Parcels: the ParcelFlux engine

Subdivision uses a bundled copy of the ParcelFlux engine (ParcelFlux plugin v0.3.8, same author, GPL-3.0-or-later), so no other plugin is needed. Blocks are grouped by the lot rules of their use (lot width, minimum lot area, lot depth, minimum frontage) and each group is subdivided in one run.

1. Each block is read as regular (four corners) or irregular; an irregular block keeps its real shape and its oriented bounding box guides the line direction.
2. The two shortest edges are the block's ends; division lines run perpendicular to them.
3. A block wider than 1.8 lot widths gets a double row of lots (back to back), a narrower one a single row.
4. Division lines are placed at the lot width, varied by the Width variation slider with a seeded generator, so the same seed gives the same parcels.
5. Lines are clipped to the block and split it; fragments smaller than 35 m² are merged into the neighbour with the longest shared edge (three passes); lots larger than four times the minimum lot are split again.

Blocks of uses that build but are not subdivided (education, health care, civic, community, worship, public safety, sports, transit and utilities) become one lot each, flagged whole block, so the building step can place their buildings. Parks, plazas, streets and water get no parcels. Generating parcels for a set of blocks replaces only the parcels of those blocks; parcels are numbered block by block, north to south and west to east, and every lot records its street frontage.

Buildings: typologies and how the caps combine

For every lot the engine classifies the edges (front, side, rear; side edges shared with the next lot are party walls for attached, semi-detached and perimeter types), cuts the setbacks off edge by edge (party walls get none), and shapes the footprint by typology, always oriented to the street. The footprint is trimmed to the tighter of the site-coverage limit and the FAR (a one-storey building never exceeds the FAR); footprints below the typology's minimum width or depth, or under 25 m², are rejected. Storeys come from the FAR, the storey cap and the height cap, whichever is tightest, and floor area, dwellings (capped by density), residents and jobs are written on the building. Regenerating replaces the buildings of the processed parcels.

Reading a building

Buildings are drawn in a darker tone of their land-use colour and labelled with their storeys (4F = four floors) at large scales. Each building carries storeys, height, footprint, gfa, dwellings, population (dwellings × household size) and jobs; the plan balance reads these numbers wherever a block has buildings.

How a footprint is placed

• Facing the street. Each lot gets a local frame on its main front, and the footprint is the largest rectangle in that frame that fits the buildable area within the typology's width and depth limits. A lot with no street frontage faces its open block edge.
• The tighter cap wins. The footprint target is the smaller of coverage and FAR ÷ storeys, so a one-storey building never exceeds the FAR; storey, height and density caps apply on top. Lots below the minimum width or depth of the typology are skipped and reported with the reason.
• Pairs and rows. Semi-detached houses pair only with a side neighbour on the same street line; in an odd row one lot stays detached. Attached rows share one rear line, and perimeter blocks close into continuous courtyard rings.

Site plan

Balance and indicators

The balance is meaningful from the first block onwards: a block with buildings counts its buildings; any other block counts its zoning-code capacity (FAR × area for floor area, the residential share and dwelling size for dwellings, capped by density). The Balance page reports how many blocks are counted from buildings.

Key figures

The land budget lists every land use (and streets) with its area in hectares and its share of the plan area, with a bar of shares by colour family; blocks without a use are shown separately.

UN-Habitat neighbourhood targets

The plan is measured against UN-Habitat (2014), A New Strategy of Sustainable Neighbourhood Planning: Five Principles. Each target is a meter on the Balance page and a row in the report.

The other two principles of the strategy, social mix (a share of affordable housing) and limited land-use specialisation (fewer than 10 % of blocks in a single use), concern housing tenure and the mix inside blocks; they are named in the Reference tab of the Zoning Code and are left to the planner's judgement.

Amenity provision

For each amenity the balance compares the land zoned for it (the area of blocks with the listed land-use codes) with the need of the planned population (hectares per 1,000 residents × population ÷ 1,000), and reports the provision ratio and the zoned area per person. A ratio of 100 % or more meets the standard.

The Balance page also holds walking accessibility with the 2SFCA provision index, the population projection, the balance per planning unit and the Excel / CSV export (section 15).

Outputs

Plan sheet (print layout and PDF)

Choose the paper (A0, A1, A2, A3 or A4, landscape) and a title, then Create layout (opens the Layout Designer) or Export PDF… (300 dpi). The sheet has a framed map at a rounded scale (1:500 to 1:100,000) fitted to the plan, the title and a subtitle with the planning authority and horizon year, a legend filtered to the classes drawn on the map, the land-budget table (up to 22 rows) with plan area, population, dwellings, jobs and gross FAR, a north arrow, a scale bar and a title block with scale, CRS, date and author. A layout of the same name is replaced, so the sheet can be regenerated after every change and refined in the Layout Designer.

HTML plan report

Write HTML report… saves one self-contained HTML file: key figures (plan area, population, dwellings, jobs, floor area, gross FAR, gross and net densities), the land budget with colour swatches and bars, the UN-Habitat targets with met / not met, and amenity provision (zoned, needed, m² per person, provision %).

Share the plan

Save a copy of the plan… first saves pending edits, then copies the GeoPackage. It carries the layers, the styles and the zoning code, so it opens styled in any QGIS.

On the sheet the legend is set in two columns and measured at its drawn size; when it is too tall its type shrinks before anything is cut. The land budget is a table with colour swatches and a bold total row, and uses that do not fit are merged into one N other uses row. The map frame keeps its shape and is set to a round scale, which the footer prints. Prepared by appears only when an author is set.

Multi-sheet plan sheets at a true scale and the full report with projection, accessibility and charts are described in section 15.

Plan check, revisions, presets and legend

Check the plan (Plan page)

Check the plan lists the problems a reviewer would mark before the plan is shared, as errors, warnings and notes; click an issue to zoom to it and select the features. Window shows the list in a larger window, and Re-check after every rebuild keeps it current while you draw.

Revisions (Plan page)

Save snapshot writes the zoning and network as they are now (unsaved edits included) to <plan>_snapshot_<date-time>.gpkg next to the plan. Pick a snapshot, or any other 02UrbanPlanning GeoPackage with …, and press Compare with the current plan: blocks are matched by overlap and the comparison reports added and removed blocks, changed land uses, changed rule overrides and area changes. The result is added to the map as a styled layer (green = gained, red = lost) with a table of each land use before, after and the change in hectares.

Presets and exchange (Code page)

Start from a preset or move a code between plans; the current code is first backed up as JSON next to the plan.

• Generic: the catalogue defaults, a balanced code for a first plan anywhere.
• Low-rise suburban: lower FAR and heights, deeper setbacks, more parking and open space, for detached and semi-detached neighbourhoods.
• Compact city: higher FAR and densities, build-to lines, less parking, for walkable perimeter blocks and mixed-use streets.

Import… loads a zoning code (JSON) exported from another plan; Export… writes this plan's zoning code and amenity standards as JSON. Regenerate the buildings after a preset or an import to apply it.

Legend preview (Code page)

The land-use legend as the plan sheet shows it, filtered by text (code, name, typology), by colour family, or to Only uses in the plan.

Accessibility, projection, exports and plan sheets

Walking accessibility and 2SFCA (Balance page)

Analyse walking access measures, for every amenity standard, the network distance from every residential block to the nearest facility, over the plan's road centrelines (expressways excluded), noded at every crossing. It runs offline in a fraction of a second on a neighbourhood plan.

• Facilities are the blocks zoned for the amenity, reached from any frontage (their boundary is sampled every 40 m), and the plan points of a matching type, reached from the nearest street.
• A residential block is reached from its interior point plus the walk to the nearest street, and is served when its network distance to the nearest facility is within the amenity's walk distance.
• Coverage is the share of the planned population living in served blocks.
• The provision index is a two-step floating catchment (2SFCA): each facility's zoned land is divided by the population within its walk distance, every block sums the ratios of the facilities that reach it, and the sum is expressed against the standard (m² per person), so 1.0 means the standard is met.

The walking catchments (the reachable street network buffered by 45 m) and the residential blocks, served and not served, are added to the map; Show styles the blocks by one amenity or by how many amenities are within reach.

Population projection (Balance page)

Grow a base-year population to the plan horizon; the horizon population becomes the target population the balance checks.

Enter the model, base year, base population, growth rate (% a year), saturation (logistic only) and horizon, or type past census counts (2000: 8200, 2010: 9100, 2020: 10400) and press Fit to set the rate that matches them and take the last count as the base. Project and set the target writes the result.

Per planning unit and exports (Balance page)

With planning units drawn, a table gives the area, people, jobs and people per hectare of every unit. Export the balance writes every table (land budget, capacity, amenity provision, UN-Habitat targets, per unit, accessibility, projection) as one Excel workbook (Excel…, one sheet per table) or one CSV file (CSV…, the tables one after the other).

Plan sheets (Output page)

A grid of sheets at a true scale (1:500, 1:1,000, 1:2,000, 1:5,000 or 1:10,000) on the chosen paper, with an optional overlap in metres. The grid starts at the top-left corner of the plan and sheets that would show nothing are left out. Create sheet layouts makes one print layout per sheet (named, for example, … — Sheet 1 of 4 (1:1,000, A1)): the map at the exact scale, a legend filtered to what the sheet shows, an index map with the land use, the sheet grid and the current sheet highlighted, the sheet number (Sheet 1/4), north arrow, scale bar and title block. One PDF… exports every sheet as a page of one PDF; PDF per sheet… writes one file per sheet.

Full plan report (Output page)

Write the full report… saves the HTML plan report with the population projection and the last walking-access run added, and its charts.

Processing provider

The plugin registers a 02UrbanPlanning provider in the Processing Toolbox, so the plan chain runs in models, batch mode and scripts. Every algorithm takes a Plan GeoPackage; left empty, it uses the plan open in the project.

FAQ and troubleshooting

“Choose a projected CRS in metres” when I create a plan.

The plan needs a projected CRS in metres (a national grid or a UTM zone). Pick one in the CRS field of the New plan section. The map may stay in any CRS; drawing is transformed to the plan CRS.

My edits are not in the GeoPackage.

Road, boundary, division-line and point edits go into the layer edit buffer so they can be undone. Press Save edits in the panel header (it appears when something is unsaved) or save the layers in QGIS. Generated streets, kerbs, parcels and buildings are written directly.

Blocks do not follow my road edits.

Check Rebuild while editing roads on the Draw page, or press Rebuild now. Roads must actually meet: snap the ends to other roads (the road tool snaps automatically) so a junction exists. A road that stops short leaves a dead end, and the block around it stays whole.

A block lost or kept the wrong land use after a big change.

Each new block inherits from the old block it overlaps most. After a large redesign, check the orange-dashed blocks (no use) and repaint them; Number blocks with Shift renumbers everything if the numbering no longer reads well.

A block has no parcels or buildings.

Its use may have Parcels or Buildings switched off, a lot width of 0 or the typology No buildings (parks, plazas, water). Setbacks larger than the lot leave no buildable area, and footprints under 25 m² are skipped. Generate parcels before buildings.

The balance population differs from the buildings.

Blocks without buildings are counted from their zoning-code capacity. Generate buildings for every block to count only buildings, and press Refresh on the Balance page.

New rules did not change the buildings.

The zoning code is applied when buildings are generated. After saving the code, run Generate buildings again (and Generate parcels when lot rules changed).

3D view does not open.

The 3D map view needs the QGIS 3D module. Buildings carry their 3D extrusion in the layer style; View → 3D Map Views → New 3D Map View shows them in any QGIS with 3D.

Citation and licence

Cite the software

@software{eminoglu_02urbanplanning_2026,
  author  = {Eminoğlu, Yusuf},
  title   = {02UrbanPlanning: Urban Planning Studio for QGIS},
  version = {0.2.0},
  year    = {2026},
  license = {GPL-3.0-or-later},
  url     = {https://geophilo.com/zero2urbanplanning/}
}

References

• American Planning Association. Land-Based Classification Standards (LBCS), colour coding of land-use families.
• UN-Habitat (2014). A New Strategy of Sustainable Neighbourhood Planning: Five Principles. Nairobi: UN-Habitat.
• Fields in Trust (2015). Guidance for Outdoor Sport and Play: Beyond the Six Acre Standard. London: Fields in Trust.

The plugin is a planning-studio tool: its figures make every plan decision traceable and comparable, and the adopted plan and its regulation remain the reference for the statutory values.