- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Good Evening,
We use laser scanning and insert Recap projects (RCPs) or individual point clouds (RCS) that are on land survey control. These coordinates are large. I see the following problems with Revit when inserting onto a Shared Coordinate System:
- When inserting a point cloud, Revit uses a scale factor, corresponding to International Feet, of 3.280840. The scale factor is truncated to 6 decimal places.
- Changing the scale factor to 3.280833 (corresponding to US Survey Feet), the point cloud coordinates are short because the decimal places are truncated to 6 decimals. This means a survey coordinate of 1,700,000 feet now appears 2 inches smaller inside Revit.
- In Revit 2015, the point cloud is not allowing us to snap to the point cloud if the coordinates are large. The same clouds with smaller coordinates will allow snapping to the cloud. This was not an issue with Revit 2014.
- One can insert one large point cloud into Revit 2015 on Shared Coordinates. If you export out parts of that same point cloud from Recap, and reference those parts into Revit, they link into Revit 2015 at slightly different locations.
- Problems with large coordinates handling Point Clouds do not appear to be problems when linking in large coordinate AutoCAD/Civil 3D files. There seems to be a problem with the interaction with Recap.
We see hundreds of scan jobs a year. The interaction between Navisworks, Revit, and AutoCAD are very important with regards to point clouds. Of the products, Revit is having the most trouble. These items need to be ironed out to make the products more intuitive to the end users. A great alternative is if Autodesk makes it official that point clouds over a certain coordinate value should not be used. Maybe that’s the 20 mile warning? Right now, I don’t believe that is clear.
Solved! Go to Solution.