Masterplan a whole precinct in minutes. Pick the site on a map, set the brief, then sketch: sweep a curvy boulevard through the land and drop pins to nominate a park, school, hospital or tower cluster, and a rule-based engine designs everything else around your moves. Blocks, typologies, tram line, trees and trunk services regenerate live, measured against distilled Victorian planning guidance, with an auto-fixer that searches the brief for a more compliant scheme. Built to show the technology, not to replace the urban designer.
What this demonstrates
Generative masterplanning + compliance intelligence. The same generative masterplanning and machine-readable ruleset architecture we deploy for precinct feasibility platforms, encoded here with distilled Victorian urban design and subdivision standards.
Demonstration only. Results are indicative and should not be relied upon for planning, regulatory, building, legal or design decisions. Professional review is required.
Urban Design Guidelines for VictoriaIllustrative pipeline for a production deployment
Design guidelines (PDF → rules)
Urban Design Guidelines for Victoria, Plan Melbourne and Clause 56, encoded as machine-readable criteria
Site & context
Site extents located on the map, with real-world context for the brief
Your sketch
A boulevard spine swept through the land and nominated-use pins, as hard design constraints
Movement & typology library
Street reservations, tram standards and building typology templates with yield rules
Masterplanning feasibility engine
Output
Masterplan feasibility pack
3D massing, land use and infrastructure layers, street cross-sections, schedules and a clause-by-clause compliance report from one parametric model
This browser demo runs a distilled ruleset; client deployments encode the full planning controls for the actual site and land results in Revit, GIS or custom platforms.
How these demos relate to the systems we build for clients.
Two ways. The spine you draw becomes the boulevard's real centreline: the street grid grows as offset rows and cross streets from that curve, so bending the line reshapes every block. Pins are hard constraints: the nearest block adopts the nominated use, and the engine assigns everything else (towers, mid-rise, housing, centre, parks) around them. The site and your sketch are never overridden, even by the auto-fixer.
An indicative distillation of Victorian planning and urban design guidance: open space provision and the 400 m walk rule (Clause 53.01, Plan Melbourne's 20-minute neighbourhoods), walkable block lengths and connectivity (Clause 56), tower separation and overshadowing of parks (Better Apartments-style standards), boulevard enclosure and active frontage (Urban Design Guidelines for Victoria), education and health triggers, integrated water management and street canopy. Every check cites its source and explains its fix. Client deployments encode the full controls for the actual site.
A 3D precinct model; seven 2D masterplan layers (land use, figure ground, movement and public transport, green and water, in-ground services, walkability, compliance); typical street cross-sections for the boulevard, connector, local and park-edge streets showing tram, in-ground services at their standard depths, canopy shading and the real building context either side; land use, yield and infrastructure schedules; and a PDF feasibility pack with the plan, register and sections.
It searches the brief's design-controllable parameters (open space target, block dimensions, typology shares, storey caps, tram stop spacing, community uses) for the closest scheme that clears more criteria, and reports every change with the before-and-after score. The site, your sketched spine and your pins stay fixed because they are constraints, not design decisions; anything it cannot clear is listed as needing a site or policy trade-off.
No, it is an educational demonstration of GIRIH X technology. Its value is speed at feasibility: developers and agencies can test dozens of structure, density and open-space options in minutes with a live compliance readout, then take the shortlist into masterplanning with their consultants. In client work the same engine runs on the real cadastre with the applicable planning scheme, and results land in Revit, GIS or the client's own platform.
Everything in the Playground is built with the same stack we deploy for clients: configurators driven by real product masters, planners connected to BIM data, and AR experiences served straight from the product catalogue.
Start a Conversation