Setting Revit Site Coordinates: A Practical Workflow
- Steve Fagan
- 5 days ago
- 9 min read
Set accurate Revit site coordinates by placing a stable Project Base Point, acquiring or specifying Survey Point coordinates from a geolocated DWG or Civil 3D export, then using Publish or Acquire Coordinates to sync every linked file. Get that sequence right once, and every consultant model, DWG export, and spot coordinate on your drawings lines up without a fight.
Here’s the fast path:
Confirm your Project Base Point location and pin it once the team agrees.
Acquire coordinates from a geolocated civil DWG, or manually enter Grid Northing/Easting values through Specify Coordinates at Point.
Set the True North rotation if project north differs from true north.
Publish coordinates to every linked model, then reload to confirm alignment.
You’ll know it worked when linked models load Auto - By Shared Coordinates with zero warning messages and your spot coordinates match the survey data your civil engineer handed you.
Key Takeaways
Accurate Revit site coordinates come down to a stable Project Base Point, coordinates acquired from a properly geolocated source, and shared coordinates published consistently across every linked file.
Point | Details |
Know your three origins | Internal Origin is fixed and untouched; PBP is your local zero; Survey Point ties the model to real-world coordinates. |
Geolocate before linking | Bring a geolocated DWG or Civil 3D export in at project start to avoid backfilling coordinates later. |
Verify with Auto - By Shared Coordinates | A clean reload with no warnings confirms your linked models actually agree on coordinates. |
Fix drift by moving and saving | Move a linked model inside the site file and choose Save Now to push corrected coordinates. |
Practice in guided course labs | S15studio’s Revit training includes sample geolocated files for hands-on Acquire and Publish practice. |
Table of Contents
What Are the Project Base Point and Survey Point in Revit?
Revit actually tracks three separate origins, and mixing them up is the single most common source of coordinate headaches on a project.
The Internal Origin is the one you never touch. It’s a fixed point buried in the software, invisible by default, and it exists purely as Revit’s internal reference for where your model geometry sits in space. The catch: your geometry has to stay within 32 kilometers (20 miles) of the Internal Origin, or you’ll start seeing jittering, snapping failures, and other graphical glitches that are maddening to diagnose after the fact.
The Project Base Point (PBP) is your model’s local zero, the (0,0,0) you use for everyday measurements and dimensioning within the site. Teams typically place it at a grid intersection on larger jobs or a convenient building corner on smaller ones, but the placement matters less than the consistency across your linked files.
The Survey Point (SP) is different: it anchors your model to a real-world geodetic reference, like a benchmark or property corner, so your building lines up with civil coordinates and GIS data. The Project Base Point defines your local coordinate system while the Survey Point orients the model to the broader world.
One more wrinkle worth knowing before you start moving these points around: whether they’re clipped changes everything.
Clipped (paperclip icon closed): moving the point changes its coordinate value relative to the Internal Origin.
Unclipped (paperclip icon open): moving the point shifts your entire model geometry relative to that point instead.
Pro Tip: Check the clip state before you drag either point. Unclipping a Survey Point by accident and moving it can silently shift your whole model, and you won’t notice until a linked file refuses to align.
Why Should You Geolocate a Revit Project Early?
Geolocating at the start of a project, rather than backfilling it later, saves you from three recurring problems: misaligned civil links, DWG exports that lose their GIS coordinates, and spot coordinates on your drawings that don’t match the surveyor’s numbers.
Skip it, and you’ll usually hit one of these:
Starting the model without a geolocated DWG on hand, then trying to reverse-engineer coordinates later.
Different team members placing the Project Base Point inconsistently across linked files.
Overlooking a unit mismatch or leaving the True North angle unset until a consultant flags it.
Practitioner experience backs this up directly: acquiring coordinates from an accurately geolocated file is far more reliable than manual approximation, which tends to produce downstream coordination struggles that are painful to untangle mid-project.
Pro Tip: Ask your civil engineer or surveyor for a geolocated DWG before you start modeling, not after your architectural model is half built. Retrofitting coordinates onto an existing model is always harder than starting with them in place.
How Do You Set Up Site Coordinates in Revit Step by Step?
Once you have survey data in hand, the actual setup in Revit follows a predictable sequence. Here’s how it plays out in practice.
Step 1: Prepare your source file. Confirm the units and scale on the civil DWG or Autodesk Civil 3D export before you bring anything into Revit. A units mismatch here cascades into every coordinate you set afterward.
Step 2: Link the DWG. Import it using Auto - By Shared Coordinates if the file already carries coordinate data, or Origin to Origin if you’re aligning manually.
Step 3: Acquire or specify coordinates. If the linked DWG is properly geolocated, use Acquire Coordinates and Revit pulls the values directly. If you’re working from a surveyor’s report instead of a linked file, use Specify Coordinates at Point, entering the Grid Northing and Grid Easting values manually. When the linked file lacks coordinates, specifying values before linking the site data ensures the model aligns correctly once the civil data does arrive.
Step 4: Set True North. If project north and true north diverge, rotate the model accordingly so renderings, shadow studies, and site plans read correctly.
Verification checklist:
Turn on visibility for both the PBP and SP in your site plan view.
Check spot coordinates against the survey point, not just the project origin.
Reload every linked model and confirm it loads Auto - By Shared Coordinates with no warning dialogs.
When entering values manually, match your project’s length units exactly, or add a unit suffix like “m” so Revit converts automatically. Get this wrong and your coordinates will look plausible but be off by a factor of feet versus meters, which is a nightmare to catch visually.
How Do Named Positions and Linked Model Positioning Work?
The Location and Site dialog, found under the Manage tab, is where multiple Named Positions (Sites) live for a single project. Think of these as saved coordinate configurations, useful when a project spans multiple parcels or phases. Whichever one you mark as the Current site controls how linked models interact with shared coordinates, so switching the Current position mid-project is a common cause of “why did my link just move” confusion.
When you link a model, you choose how it positions itself relative to your host file:
Auto - By Shared Coordinates aligns the link using coordinates both files already agree on. Use this once shared coordinates are established.
Origin to Origin stacks internal origins directly. Use this for a quick, temporary link before coordinates exist.
Center to Center and By Shared Coordinates (Custom) exist for edge cases, but most production workflows live in the first two.
Publish Coordinates pushes your host model’s location out to a linked file. Acquire Coordinates pulls the reverse, taking a linked file’s location into your model. One project usually acts as the site or base file that everyone else acquires from.
Pro Tip: If you’re working with cloud-hosted models on Autodesk Construction Cloud, know that Publish Coordinates may not be available for cloud links, and you’ll need to lean on Acquire Coordinates workflows or coordinate the setup before models move to the cloud.
Why Do Linked Revit Models Show Coordinate Warnings?
The warning “the host model and the link do not share the same coordinate system” means exactly what it says: the two files have never agreed on a shared coordinate reference, so Revit is asking you to pick one before it positions the link.
Start your diagnosis visually. Turn on PBP and SP visibility in both the host and the linked file. Linked model points display in gray, which makes it straightforward to spot a mismatch by comparing distances and angles between host and linked origins at a glance.
Common fixes, in order of how often they solve the problem:
Run Acquire Coordinates again if the source file’s coordinates changed since the last link.
Move the linked model to the correct position inside your site or base file, then choose Save Now on the resulting warning. That action pushes the corrected coordinates directly into the linked file.
Use Specify Coordinates at Point for manual correction when no reliable linked source exists.
Watch for coordinate drift too, where small rounding differences compound across multiple linked files over months of edits, and for snapping issues that appear once your geometry creeps near that 32 km/20 mile proximity limit from the Internal Origin.
Pro Tip: When a link looks misaligned but the warning didn’t fire, check spot coordinates on both files side by side. It tells you immediately which origin each file is actually reporting from.
What Team Conventions Prevent Coordinate Errors?
Most coordinate disasters trace back to a team decision that never got made explicitly. Fix that at the project setup stage and you avoid the rework later.
Agree on Project Base Point placement in your kickoff meeting, whether that’s a grid intersection or a building corner, and pin it once it’s final so nobody nudges it by accident.
Keep all model geometry within the 32 km/20 mile guideline from the Internal Origin to avoid rendering glitches and snapping failures.
Set project units once at the start and stick to them; when GIS coordinates arrive from a civil consultant in a different unit, add the suffix so Revit converts rather than misreads the value.
When exporting to DWG, check the export coordinate settings to confirm whether the output references the Project Base Point or the Survey Point. Getting this backward is a frequent cause of civil engineers reporting your export is “off” by a fixed offset.
Bake PBP and SP visibility settings, plus a sample Named Position, into your office template so every new project starts from the same baseline.
Consistent origin practices across a discipline team pay off well beyond coordinates alone. A shared coordination model approach reduces clash-detection headaches later in the project.
What Should a Project Coordinate Checklist Include?
Before you send a model out to consultants or bring in their linked files, run through this:
Confirm the Project Base Point is placed and pinned.
Verify Survey Point coordinates match the civil engineer’s benchmark data.
Check True North rotation against the site plan.
Reload every linked model and confirm zero coordinate warnings.
Document the datum and any manual offsets in your BIM execution plan.
Trainers who’ve walked dozens of teams through this setup tend to repeat the same three habits: pin the PBP the moment it’s finalized, keep a throwaway sample model around specifically for practicing Acquire and Publish workflows, and stash a known-good geolocated DWG in your office resource library so nobody starts a project coordinate-blind.
Pro Tip: Write down your project’s datum and any manual coordinate offsets in the BIM execution plan the day you set them. Six months later, nobody remembers why the Survey Point sits 4.2 meters off true grid north, and that detail matters when a new consultant joins.
Why disciplined coordinate setup actually pays off
Getting the Project Base Point and Survey Point right at the start isn’t paperwork, it’s risk management. Every hour spent confirming coordinates before linking saves several hours of clash rework later, and it makes onboarding a new structural or MEP consultant almost frictionless.
Practice Revit Coordinate Workflows With Guided Course Labs
Reading through the Acquire, Specify, and Publish workflow is one thing. Running it yourself on a real geolocated DWG, watching what happens when you deliberately misalign a link, and having a trainer walk you through the fix is what actually makes it stick. S15studio’s course labs include sample geolocated files built specifically for practicing these coordinate workflows, so you can break something on purpose and learn exactly how to recover it, instead of discovering the failure mode for the first time on a live project.
The Complete Revit and AutoCAD Training program walks through site coordinate setup as part of its project-based curriculum, with direct trainer support when your linked models won’t cooperate. If you’re newer to Revit and want the fundamentals first, the Revit introduction course covers site basics before you tackle multi-consultant coordination. Either way, you get lifetime access to the sample files, so you can revisit the coordinate exercises whenever a new project throws you a curveball. Check the course pages to see which level fits where you’re starting from.
Sources
Recommended
Comments