Lands Design

Because Lands Design is a Rhino plugin, users typically need a separate Rhino license and must be comfortable with Rhino’s interface and modeling concepts. Teams that primarily work in 2D CAD or in a dedicated landscape package may face a learning curve. This dependency can also complicate procurement and IT support compared with a single, standalone application. Organizations without Rhino in their stack may not realize the product’s full value.

Landscape documentation needs (construction details, annotation standards, sheet management) can be highly specific, and the completeness of deliverables depends on how a team structures its Rhino-based workflow. Some firms may find they need additional setup, templates, or complementary tools to match established CAD/BIM documentation practices. This can be a consideration when comparing to products designed primarily around production drafting. Output consistency may require more internal standards work.

Plant libraries, symbols, and region-specific standards often require localization and ongoing maintenance. Users may need to build or curate their own plant database content to match local species, naming conventions, and graphic standards. This can add upfront effort during implementation. The level of out-of-the-box regional content may not match tools that ship with extensive localized catalogs.