Here you will find an explanation and best practices for solving issues around spatial location.
Category: Filtering
Warning message: Site located (x, y) km from coordinate system origin. It is too far and globe placement may be inaccurate. Consider re-creating the input file with better positioning.
Issue:
The iModel location and GCS origin distance must be within the normal range (16KM) so the model location will be correct.
Cause:
The values in the IFC file as generated by the source application are very far away from the coordinate system orgin.
Solution:
Correct the Design Data: Such issues are always related to the source data. iTwin Spatial Alignment articles will help you validate data positioning and make required changes to design applications based on your data type. Once the file is corrected, re-synchronize the file into the iModel.
Contact Bentley Support for assistance if these issues cannot be solved.
Info message:
The following elements are out of range: <list of elements>
Each entry in the list identifies an element by its name and its source element identifier.
Issue:
While calculating the spatial extents (the bounding box) of your iModel, the synchronization detected one or more elements located far outside the area occupied by the rest of your data. These are called "outlier" elements. In this case, the synchronization could not determine which source model or source file the outlier elements came from.
Cause:
Solution:
Info message:
In model '<model name>', the following elements are out of range: <list of elements>
Each entry in the list identifies an element by its name and its source element identifier.
Issue:
While calculating the spatial extents (the bounding box) of your iModel, the synchronization detected one or more elements located far outside the area occupied by the rest of your data. These are called "outlier" elements. In this case, the synchronization identified which source model the elements came from, but could not determine the source file.
Cause:
Solution:
Info message: In the file '<file name>', within model '<model name>', the following elements are out of range: <list of element names and element IDs>
Issue:
While the connector was computing the iModel's project extents, it found one or more elements whose location falls outside the calculated spatial bounds of the iModel. This message is produced when both the source file and the model containing those elements are known, so the affected elements can be pinpointed. It is informational and is intended to help you locate stray or mislocated geometry.
Cause:
This message is typically produced for one of the following reasons:
Solution:
Additional Information:
Info message: This model used ECEF location <-X>, <Y>, <Z) (<datum> <latitude> <longitude>, ele <elevation>, eas <SP-x>, nor <SP-y>) instead of existing GCS settings due to user-defined location and enabled 'allow-revit-ignore-gcs' feature flag.
Issue:
No issue, this only provided for information.
Cause:
Not applicable.
Solution:
Not applicable.
Warning message: The geo-location point (Survey Point (SP) <SP-X>, <SP-Y>) was moved to the local zero coordinate (Project Base Point (PBP) <PBP-X>, <PBP-Y>) due to the distance <length> km between them being too large in order to provide more accurate elements placement. It is better to follow Autodesk's recommendations to fix this in source file: http://help.autodesk.com/view/RVT/2018/ENU/?guid=GUID-3F79BF5A-F051-49F3-951E-D3E86F51BECC
Issue:
Graphic distortion can occur when the Survey Point (SP) and Project Base Point (PBP) are positioned more than 10 miles (or 16 km) apart. are. During Revit file processing, the Survey Point (SP) was moved to the Project Base Point (PBP).
Cause:
The graphics get distorted when the Survey Point (SP) and the Project Base Point (PBP) are far apart.
Solution:
To resolve the graphic distortion issue, adjust the Revit file by bringing the Survey Point (SP) and Project Base Point (PBP) closer together and closer to the Revit internal origin. This can be done by relocating the Project Base Point near the Survey Point, or vice versa, depending on project requirements. It's important to ensure that the overall model remains centered near the internal origin to maintain geometric accuracy and avoid display issues.
Warning message: The coordinate system library could not use the geo-location data contained in the model based on the default <datum name> datum. Please update the geo-location information in the input file.
Issue:
Failed to create the geographic coordinate system (GCS) from file based GCS info.
Cause:
The coordinate system library could not create the GCS from the datum present in the provided file.
Solution:
Please contact Bentley Support mentioning this error and they will help analyze the problem and suggest a fix.
Error message: The coordinate system library could not use the geo-location data contained in the model based on the default <datum name> datum. Please update the geo-location information in the input file.
Issue:
Failed to create the geographic coordinate system (GCS) from file based GCS info.
Cause:
The coordinate system library could not create the GCS from the datum present in the provided file.
Solution:
Please contact Bentley Support mentioning this error and they will help analyze the problem and suggest a fix.
Error message: The coordinate system library could not create ECEF coordinate system using '%s' datum from the file. Please update the geo-location in the input Revit file.
Issue:
Failed to create the ECEF coordinate system from the file based GCS info.
Cause:
The coordinate system library could not create the ECEF coordinate system from the datum present in the provided file.
Solution:
Please contact Bentley Support mentioning this error and they will help analyze the problem and suggest a fix.
Warning message: This file reprojection has failed due to geo-positioning error; its coordinate system origin (X, Y, Z) was used as is.
Issue:
Reprojection calculation failed.
Cause:
Coordinate system library failed to calculate reprojection.
Solution:
Recheck the location info in the Revit file or contact Bentley Support mentioning this error and they will help analyze the problem and suggest a fix.
Info message: The file was published without geo-coordinate reprojection. Its Survey Point has <X, Y> coordinates instead of <X1,Y1> with reprojection usage.
Issue:
The Model was not reprojected.
Cause:
The option to skip reprojection of Revit models is enabled.
Solution:
If the model is not geo-located, then it is fine to skip reprojection. If the model is geo-located, then please contact Bentley Support to have reprojection skipped for this model and then re-synchronize this model. Alternatively, you can edit the file in Revit, please see the knowledge base article for detailed instructions.
Warning message: This file was reprojected to <distance> km away, its elements placement might be wrong. Please contact Bentley support to have reprojection skipped for this model and then re-synchronize this model. Alternatively, you can edit the file in Revit, please see the knowledge base article for detailed instructions. For manual editing use Internal coordinate (ICS-Y): <value> and Internal coordinate (ICS-X) <value>.
Issue:
The model placement may not be proper.
Cause:
Reprojection is too far away from the GCS in the iModel.
Solution:
Info message: This file was reprojected to (<X,Y,Z>) from original location (<X,Y,Z>) in <Datum name> <latitude> <longitude> geo-coordinates at (<SP-X, SP_Y>)
Issue:
The file was reprojected compared to the previous synchronization.
Cause:
The model was moved in Revit, or the location was changed compared to the previous synchronization.
Solution:
This is to inform that the Revit model was moved during this synchronization and no action is required.
Error messages:
Error message: Project extents are too tall: <value> meters (expected less than 900 meters). Element geometry this expansive will affect display performance and often indicates corrupt elements or transforms.
Error message: Project extents are too low: <value> meters (expected greater than 11000 meters). Element geometry this expansive will affect display performance and often indicates corrupt elements or transforms.
Error message: Project extents are too high: <values> meters (expected plane dimension less than 9000000). Element geometry this expansive will affect display performance, and often indicates corrupt elements or transforms.
Error message: Project extents are too high: <values> meters (expected less than 8850 meters). Element geometry this expansive will affect display performance, and often indicates corrupt elements or transforms.
Error message: Project extents are too narrow: <values> (ratio of largest footprint dimension to height; expected greater than 0.10). Element geometry this expansive will affect display performance, and often indicates corrupt elements or transforms.
Error/Warning message: Calculated extents along z is too big <value> x <value> = <value> m. Clamping it to <value>x<value>
Error message: Element '' is excluded due to invalid extents: too small height 0.00 mm. Please try to re-publish this Review file from original source again.
Error message: Element(s) were considered statistical outliers and were excluded from the project extents. They may not be visible in this project. This often indicates corrupt elements or transforms.
Issue:
The position of some elements in the synchronized data will cause display performance issues.
Cause:
Some elements in the synchronized data are outside the viewable range for an iModel.
Solution:
Check Design Elements: Update the source files to correctly place or delete elements depending on your needs and practices. For example you could identify those outliers if you enable the iModel Display Extents in your viewer, or you can see those listed in the Geospatial Metadata widget warnings section.
Define Maximum Extents if needed: If you can't fix the input data, use this guide on creating an iModel that will help constrain the iModel extents.
Adjust the iModel Display Extents: if non-visible elements are required you can adjust the iModel Displat Extents. [Coming Up]
Synchronize Files in the Correct Order:
For Reality Data: Synchronize with a defined GCS first, a DGN with an identical GCS second, followed by other models.
For non-DGN files: Synchronize a DGN with a defined GCS first, followed by non-DGN models next.
For files without a GCS defined: Synchronize a DGN with a defined GCS first, followed by models with an undefined GCS next.
Review GCS Systems: Ensure there are identical GCS systems in the source files. Fix any inconsistencies. Each design application will have specific information about setting and using GCS data. You can find more information in the iTwin Spatial Alignment articles or directly in design applications documentation. In the case of dgn files, file referencing support could be used as a technique to locate incompatible files.
Info message: Using IfcCoordinateReferenceSystem Name = <>
Issue:
The connector logs the Name of the IfcCoordinateReferenceSystem found in the IFC file. This is used for tracing and validating georeferencing assumptions.
Cause:
Solution:
Info message: Setup GCS from IFC: lat , lon , azimuth
Issue:
The connector has initialized the iModel’s Geographic Coordinate System (GCS) using geolocation information found in the IFC file (datum, latitude, longitude, and azimuth).
Cause:
Solution:
Error message: Calculated extents along z is too big <high value> x <low value> = <height> m. Clamping it to <new high value> x <new low value>
Issue:
The overall vertical (top-to-bottom) size of the iModel calculated from the source data is unrealistically large — taller than the highest point on earth. Rather than accept that, the vertical extent was automatically reduced to a reasonable height centered on where most of the content actually sits.
Cause:
Effect:
Solution:
Additional Information: