Good try - thanks. I was hoping you had a solution the rest of the WWW has yet to solve. The use of State Plane Coordinates are very valuable for many "other" uses outside of Revit. They are fine to use in Revit as well. The state plane is like a table cloth under your "site" - the "origin" (SP) does not need to be hundreds of miles away - it can be within the state plane coordinate system very close to your building site. I'd recommend using NGS/NOAA Maps to find "local" SPs - relatively speaking. The issue is the differential relationship (x,y,z) between where model elements reside and the IO. Regardless of whatever "movement" you can perform in Revit, I've yet to see Autodesk come up with a solution for this.
this looks like more about relocating the project base point and not about the internal origin. the revit internal origin can not be manipulated, like the project base point, survey point can.
Let me explain why this is Incorrect: This workflow is 100% for relocating internal origin. You are correct that the internal origin itself cannot be moved. However, you can move everything relative to the internal origin to effectively relocate the internal origin!
Having a geolocation allows the architect to export files in alignment to civil3D. Dont use that shared location if you dont want to. We can have multiple shared locations. One geolocation and multiple arbitrary locations. Depending on which location is set as current dictates where 0,0 is for algning various import and exports. Not all files align at rvt internal origin. Having various shared locations allows us to work near rvt internal origin and accomodate others.
Yeah, this video is incorrectly named and misleading. You cannot relocate the internal origin in revit. You are just moving your model elements to align with the internal origin.
did you mention something about autocad civil? civil3D? as far as i understand from our landscape planner, civil 3D *only works in project coordinates, so if you have a project at the 0,0,0 point it is better for them. *having the project located on real world coords is, as far as i understand from the landscape planner, confusing and nobody does it. Do you know anything about that?
I do not. The architecture firm I work with uses civil 3d and they do their jobs in real world coordinates. That's interesting to hear you say this. I always felt like it made very little difference for them to use state plane coordinate system rather than project 0,0,0. Thanks for sharing. I'll keep my ears open on this one as I get further in my career
PLEASE GET STRAIGHT TO THE POINT MAN. 12 minutes for something that could've been done in 2
Good try - thanks. I was hoping you had a solution the rest of the WWW has yet to solve. The use of State Plane Coordinates are very valuable for many "other" uses outside of Revit. They are fine to use in Revit as well. The state plane is like a table cloth under your "site" - the "origin" (SP) does not need to be hundreds of miles away - it can be within the state plane coordinate system very close to your building site. I'd recommend using NGS/NOAA Maps to find "local" SPs - relatively speaking. The issue is the differential relationship (x,y,z) between where model elements reside and the IO. Regardless of whatever "movement" you can perform in Revit, I've yet to see Autodesk come up with a solution for this.
this looks like more about relocating the project base point and not about the internal origin. the revit internal origin can not be manipulated, like the project base point, survey point can.
Let me explain why this is Incorrect: This workflow is 100% for relocating internal origin. You are correct that the internal origin itself cannot be moved. However, you can move everything relative to the internal origin to effectively relocate the internal origin!
@@b_gumm moving in this way will I lose the cropping in the views plans etc?
@@IgnazioDeiana you are moving the model elements, so yes.
@@b_gumm ok this is bad.any alternative to avoid losing the set views. my project is already in advance state
@@IgnazioDeiana dynamo
Having a geolocation allows the architect to export files in alignment to civil3D. Dont use that shared location if you dont want to. We can have multiple shared locations. One geolocation and multiple arbitrary locations. Depending on which location is set as current dictates where 0,0 is for algning various import and exports. Not all files align at rvt internal origin. Having various shared locations allows us to work near rvt internal origin and accomodate others.
Well said on the several shared site coordinates. I never thought of that...and thats a pretty basic thing to do. Appreciate the response.
Yeah, this video is incorrectly named and misleading. You cannot relocate the internal origin in revit. You are just moving your model elements to align with the internal origin.
Duh. Which the video states. Make a better video then
did you mention something about autocad civil? civil3D? as far as i understand from our landscape planner, civil 3D *only works in project coordinates, so if you have a project at the 0,0,0 point it is better for them.
*having the project located on real world coords is, as far as i understand from the landscape planner, confusing and nobody does it. Do you know anything about that?
I do not. The architecture firm I work with uses civil 3d and they do their jobs in real world coordinates. That's interesting to hear you say this. I always felt like it made very little difference for them to use state plane coordinate system rather than project 0,0,0.
Thanks for sharing. I'll keep my ears open on this one as I get further in my career
@@b_gumm I have a call about this exact subject next week with the civil responsible. can report back with info on best practice. good stuff.
@@as1295 would love to hear what you find out. Contact me thru here or via my personal info listed on my channel
Great Tutorial
Glad I could be of help