This presentation is a summary of the work that we have been doing, shown with real-world Landscape Architecture projects from around the world.

We at Gensler's largest Landscape Architecture studio based in London have been developing a workflow to work in BIM/Revit for the past 4 years. Too often, the BIM model of the building allows high-quality coordination but is let down when it comes to Landscape Architecture, going back to relying on 2D workflows. You can see different floors in the image below.Of all the design disciplines in the construction industry, landscape architects have been left behind the furthest by BIM. Create a floor type for each hardscape component (roads, sidewalk, grass, soil, etc.). Therefore, you should use floors to represent site elements on simple sites. Creating subregions and building pads is a painful process for many users. Toposurface can be pretty problematic, however. It’s the most common workflow, and it’s how you are usually taught to model. Most Revit users use the Toposurface tool to create the site. 1- On Simple Sites, Use Floors Instead of Toposurface We will cover planting and parking in an upcoming guide.

This post mostly focuses on topography, roads and curbs. This guide wouldn’t be possible without Lauren Schmidt of team Parallax, who shared her knowledge in a recent episode of Revit Pure Live.Īlso, thanks to the team at Arch-Intelligence, who created the great Environment plugin which is covered in this post. The good news is that the community took things into their own hands, found great workflows, and build amazing plugins to solve issues and pain points with the landscaping features.

Landscape architects and users modelling complex sites often get frustrated by what is offered by Autodesk. Let’s be clear: Revit’s default landscape and site tools are not very good.

Using revit for landscape architecture