Use this guide when a processed dataset is marked with a “too far from site” status in NavVis IVION Processing, blocking you from adding it to Dataset Management. You’ll need admin-level access to your IVION site. By the end, you’ll have identified the coordinate mismatch and applied the correct fix.
Root cause
NavVis IVION limits each site to a 20,000 m radius around its base point. If a processed dataset falls outside that radius, NavVis IVION blocks the data transfer to Dataset Management and marks the dataset “too far from site.”
The mismatch is almost always caused by one of the following:
The site location and the control points use different coordinate systems.
The Easting and Northing values in the control points file are reversed, creating a left-handed coordinate system.
The control points use very large coordinate values (more than 20,000 m from the coordinate origin).
Troubleshooting procedure
1: Verify the site location type
Determine whether the site uses WGS 84 (latitude and longitude) or an EPSG spatial reference system.
Open your IVION site and enter Draft Mode.
Go to Settings > Edit Site Location.
Select Show advanced settings>Spatial reference system.
Note whether the site location is set to Latitude & Longitude (WGS 84) or Spatial Reference System (EPSG). If EPSG, note the code.
2: Inspect the control points file
Download the control points file for the affected dataset to check which coordinate system was used during processing.
In NavVis IVION Processing, go to the Processed data tab.
Select the dataset marked “too far from site.”
Select Download, then select Surveyed control points (.csv).
Open the CSV file and inspect the first line.
If the first line reads #, CRS, EPSG:xxxx, the data was processed using a specific spatial reference system.
If that line is missing, the control points were treated as an arbitrary local coordinate system.
3: Download and check the quality report
The quality report confirms the coordinate system that was active when the data was processed.
In NavVis IVION Processing, select the dataset and download the quality report. For details, see Downloading processed data.
Open the quality report and note the coordinate system: Local Reference System or Spatial Reference System.
4: Identify the root cause and apply the fix
Compare the site location type (Step 1) with the control points (Step 2) and the quality report (Step 3), then apply the matching fix.
Site location | Control points | Fix |
|---|---|---|
EPSG (spatial reference system) | No EPSG header (local system) | Reprocess the data and specify the correct EPSG code when uploading the control points. See Processing Tasks, step 8b/c. |
WGS 84 (latitude and longitude) | EPSG header present | Either change the site location to use the same EPSG system, or reprocess the data using a local reference system. |
WGS 84 (latitude and longitude) | Local system, but coordinate values exceed 20,000 m | Truncate the control point coordinates by removing leading digits so all values are less than 20,000 m. Reprocess the data with the adjusted control points. |
EPSG | EPSG (different system) | Update the site location to match the control points’ EPSG code and position so the difference is less than 20,000 m. |
EPSG | EPSG (same system, but values differ by more than 20,000 m) | Adjust the site location to match the control points more closely. |
Step 5: Check the base point coordinate order
If none of the scenarios in Step 4 apply, check whether the Easting and Northing values are in the correct order. Reversed values create a left-handed coordinate system and trigger the error.
Control points file: ID, Easting/x, Northing/y, Height/z
Base point: Easting/x, Northing/y, Height/z
If the values are reversed, correct the order in the control points file and reprocess the dataset.
Contact support
If none of the steps above resolve the issue, contact NavVis Support at support@navvis.com. Include temporary admin login details for the affected site.