We can use Relocate Project to move our project up to 100 but it doesn't really move at all. It was initially intended to allow us to move a building up to a design elevation of 100 instead of 0 so there are no negative elevation values, perhaps more common in North American than elsewhere. I'd say the flaw is that Revit hasn't done a good job of making Relocate Project easier to comprehend. Linking Auto-Origin to Origin isn't flawed, it works fine. Revit will even generate a warning message that allows you to save the change immediately (click Save Now) or postpone saving (click OK) the changes until you are satisfied all repositioning is complete. Move them in the site file and Publish Coordinates again to revise them. A warning message does appear that the file(s) doesn't "share coordinates" so Revit will use the World Coordinate System of the file, which is the same as the other CAD files.so they line up.Ī significant benefit of this approach is how flexible it will be when building models need to move. If all models share this understanding then other CAD files that also use the same origin as their reference will import into Revit projects using Auto-by Shared Coordinates and land in the correct location too. Once satisfied the Publish Coordinates tool will "push" the necessary coordinate information to the building file so it will understand both its project relationship (file) and its real world site position and orientation. Then the building can be linked into the site model and positioned as required. The building model(s) can be created using a convenient Project North orientation. This project uses Acquire Coordinates (or Specify Coordinates at Point) to define the Revit site's relationship to the civil/survey data. Toward that end I believe it is helpful to establish a separate site model that holds survey file data (related civil/survey CAD files etc).
We'll find a new import will land in the old location, assuming we don't move the SP (clipped) away from where it was.Īs an aside - Usually a building's position is derived from site conditions. When we link in CAD files however, using Auto - by Shared Coordinates this forces Revit to import them based on the WCS which is now different. In the situation described in OP, when we link in new files (using Auto-Origin to Origin) they don't see the origin (PBP) as being any different, they appear in the same place relative to the model and PBP. It is even more confusing because we can move them both un-clipped which renders them annotation, to mark points of reference relative to their origin clipped locations. I believe it causes unnecessary confusion when we examine the PBP coordinate values (when selected) because it displays offset values relative to where the SP defines the WCS origin. The PBP and SP start out at the same location in stock templates, but they are NOT marking the same information. If we try the steps above and make sure we can see elevation symbols it becomes more apparent when they don't change their relationship to the PBP after using Relocate Project. In a sense Revit just shifted the world over, underneath our building, and the origin never really changed. Using Relocate Project you see the PBP move but its really the SP that's changed, it just doesn't look like it because the PBP is reporting a different 0,0 coordinate offset now (more on that below).The previous steps are essentially the same as moving the SP (clipped) to the right 1 meter instead (use Undo and try it).The SP identifies the origin of an alternate coordinate system, roughly equivalent to AutoCAD's WCS (World Coordinate System) origin.We'll find the SP is now 1 meter to the right, left behind marking where the origin was.Use Relocate Project, "move" it 1 meter to the left.Make sure the PBP (Project Base Point-circle) and the SP (Survey Point-triangle) are visible.
Relocate Project is a slight of hand trick, try this example: Manually grab all the geometry in my file, and drop it where I need it.Yes, if the entire building really needs to move away from the file's origin, the origin must stay the same.
0 kommentar(er)
