Point Clouds with large (OS) coordinates and Revit.

[Anonymous]

Hi,

I am trying to create a Revit model from a Pointcloud exported from ReCap with OS coordinates. As everyone is probably aware this throws up errors as the coordinates are larger than 30000 and graphical problems occur. I am finding it very difficult to draw due to these graphical problems. Can anyone suggest a better way to insert a georeferenced Pointcloud into Revit and not have issues? I tried moving the Project Base Point (and even the Survey Point) to various location, but still the errors occur when the Pointcloud is inserted.

If I were to truncate the coordinates of the Pointcloud, would that make life easier? If so would I do that in ReCap? Futhermore if I worked in Revit with truncated coordinates, how would I then be able to convert everything back to OS to send to the client?

I'm new to Revit (and by no means an expert in ReCap) and can't seem to find the exact solution I'm looking for in various forums/YouTube.

Any help would be greatly appreciated.

Thanks,
Danny

[Anonymous]

Hi, was there a source for this "You will get an error message saying that the data is too far, but that is misleading and can be ignored." Still in 2021 getting this extremly misleading warning after georefing+aquireing coord with DWG

[Anonymous]

[info-3d-software]

Hello,

I'm working with a large coordinate project and point cloud as well. Do you have a video that goes through this process you mentioned? Or maybe a larger copy of those images? I tried downloading the images but they are very pixelated when I opened them.

Thank you I appreciate your help!

Kelly

[Stijn8N2DF]

7 years later, and we're on Revit 2024. This issue still persists. Shortening long coordinates can't be done for every survey controlled data that comes in, it's just ridiculous to request.

Imagine you're modelling from a pointcloud that's survey controlled, then import survey DWGs that you then have to move around every time, just to suit the shortened coordinates.

By now there should have been a solution rather than a workaround.. as pointclouds with coordinates >30,000 still 'jump around' 50-100mm from their x,y position vs the position that they're displayed on screen.