Working far away from Project Base Point?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am setting up my project with the correct geographical location and I am having problems with the origin being too far away. I am linking in CAD files that were exported from a Bentley Product (by another party). So the normal coordinates workflow (that I've read about) does not apply. They aren't Civil CAD files that use shared coordinates for me to copy. They are, however, located in the correct location, hundreds of miles away from the 0,0 origin.
They come in to Revit in the correct coordinate location when I link them origin to origin. Revit is making me leave my origin at 0,0, because the project is too far away. I'm able to move my project survey point, though. I'm not quite sure what that does for me. So I was thinking I could start my project at the real geographical location, with my base point at 0,0, but Revit will not let me see any section or elevation views that I create that far away from my origin. (View cropping is off, and annotations are all visible).
If I move the links back to the project origin, and then "specify coordinates at a point", to locate my building, I am able to see the sections and elevations I create. The problem is, by moving the project to the origin, the additional CAD files don't line up when I link origin to origin, because their origin is 0,0.
We have both CAD and Revit users on this project, and I want them all to be able to link in these CAD files to the correct location without having to transform... What is the proper workflow here? Is it possible to leave the base point at 0 and work on a project hundreds of miles away?
Thanks!