Revit was drawn for buildings, so the things landscape lives on — terrain, grade, paving, planting — are the parts you finish by hand. RevSphere takes the operations you repeat on every project and turns them into batch tools that run in a few clicks. Built by the practitioner who needed them.
Deadline tomorrow. You shape-edited the floor to model the fall across the site, and now the paving hatch prints stretched and skewed across the plan — useless on a drawing that’s about to be issued.
Next to it sits the material legend you’re assembling swatch by swatch, by hand. And somewhere on the list, the canopy target you’ve been eyeballing, because adding up tree crowns properly is its own evening’s work. None of this is design. It’s the tax Revit quietly charges landscape for not being built with it in mind.
Revit’s world is made of walls, levels and rooms. The things landscape actually works in — terrain, grade, paving materials, planting coverage — are second-class citizens, reachable only through workarounds you rebuild on every project.
And no architecture-first vendor is going to fix it; there’s no building-industry market in the landscape edge cases. So the work falls to you, by hand, every time — an hour here, an evening there, on operations a computer should have handled.
RevSphere is the opposite bet: build the tools for the landscape discipline, by someone who does the work. It takes the operations you keep redoing by hand and makes each one a button on the Revit ribbon.
The skewed hatch prints flat. The legend assembles itself. The canopy target becomes a number you can defend. You stay in Revit, on your own model — the busywork just stops being yours.
Each module solves one concrete operation, and they share the same Revit-free geometry core — so the overlays, the area take-offs and the canopy math all behave consistently across a project, backed by the same tested math.
Shape-edit a floor or toposolid to model the fall and the plan hatch prints skewed. Surface Hatch lays a flat, view-correct material overlay over it so the plan reads clean — and only ever regenerates its own overlays.
点Builds the material legend for you — swatches and family top-symbols laid into a Legend view, scaled to the sheet — instead of assembling it swatch by swatch.
线Turns floor and region footprints into Area Boundary Lines, Areas, a schedule and a colour legend in one pass — the area take-off otherwise traced and tabulated by hand, kept in sync as the design moves.
面Tree-canopy coverage as a number you can defend: it unions the crown circles inside a boundary so overlaps count once — across both new and existing trees — so the EFSG 35% target stops being a guess.
∴Select two or more floors and it boolean-unions their footprints into one clean slab, preserving or filling the enclosed voids. Merge Regions does the same for overlapping filled regions.
∵Two newer terrain tools are already on the ribbon and in testing: Generate Floor turns an imported CAD site outline into a real Revit floor, and Drape to Surface drops a floor onto sampled terrain so it follows the ground. Further out, GradeForge — point-to-point floor grading with AS 1428 / EFSG compliance checks — is specced and waiting on its geometry slice. The newer tools are flagged as in-testing on purpose; the page won’t dress them up as finished.
The fair question about any tool that writes to your model is: what will it touch? RevSphere is built so the answer is always only what it made.
It only ever touches what it made. Every overlay, legend and area line RevSphere generates is tagged in the model's Extensible Storage, so its Sync deletes only RevSphere content — never your drawing.
It runs on live Revit 2025 and 2026 project work, not a demo reel — in daily use while the public release is in final polish.
The geometry it relies on — loop detection, boolean union, the canopy union — lives in a Revit-free core with more than 300 offline tests, so the numbers it hands you are repeatable, not a black box.
One installer covers both Revit 2025 and 2026 — nothing to wire up per version.
Each page a 点, each link a 线, the whole a 面. Hover a node to trace its connections.