A Two-Part-per-Million Unit Difference Can Move a BIM Model 10 Feet
Vectorworks 2027 adds a Geolocation Setup Wizard intended to align surveys, point clouds, GIS layers and imagery around a survey point. It also expands the handling of Revit Families and DXF/DWG Dynamic Blocks as dynamic objects and moves more graphics work to the GPU.
Those are useful changes. For project teams exchanging information across survey, civil, architectural and construction platforms, the geolocation work may be the most consequential.
It also brings an old problem back into view: a model can look correctly located and still use the wrong definition of a foot.
Survey foot and international foot are not interchangeable
On U.S. projects, teams have historically encountered both the U.S. survey foot and the international foot. The difference is only about two parts per million. That sounds insignificant until the conversion is applied to state-plane coordinate values measured in the millions.
At that scale, the resulting offset can be roughly 10 to 15 feet. A tiny unit difference becomes a very visible field problem.
This is not really a choice between “survey feet” and “decimal feet.” Either unit can be written as a decimal. The technical question is whether the coordinates are based on the former U.S. survey foot or the international foot, along with the horizontal coordinate reference system, vertical datum and project transformation.
A setup wizard cannot choose the contractual survey basis
Software can make geolocation easier. It cannot decide which survey is authoritative or resolve an undocumented transformation between consultants.
Before importing a survey, point cloud or linked model, the team should record:
coordinate reference system and zone;
horizontal and vertical datums;
unit definition;
survey point and project origin;
rotation or transformation applied;
elevation basis; and
at least two known points for verification.
The same record should travel with exports. File names such as “site-final” do not communicate coordinate control.
Imported content needs the same discipline
Vectorworks says Revit Families and DWG Dynamic Blocks can retain more dynamic behavior. That can reduce rebuilding, but it does not prove that the imported content is ready for production.
Teams should still check geometry, insertion points, units, parameters, classifications and downstream editability. A dynamic object that behaves differently after exchange can create a quieter problem than a 10-foot offset, but it can be just as disruptive later.
Vectorworks also reports large graphics-performance improvements in specific navigation and selection tests. Those are company benchmarks and should be tested on real office models before a team changes its hardware or production standards.
Vectorworks 2027 appears to reduce friction around geolocation and imported content. The project still needs a written coordinate basis and known-point checks. Better tools make the workflow faster. They do not make a two-part-per-million assumption harmless.
Comments