in this project i have kept both project base point and survey point at ground level , but when creating toposurface when i enter 0 as level , it cretes it at the bottom of the objects . Why is this?
Gelöst! Gehe zur Lösung
Gelöst von barthbradley. Gehe zur Lösung
Gelöst von barthbradley. Gehe zur Lösung
Gelöst von Ilic.Andrej. Gehe zur Lösung
Gelöst von Ilic.Andrej. Gehe zur Lösung
Where's your Internal Origin at? That the Zero Origin for Toposurface Internal Points.
Project Internal Original = Project Base Point Startup Location
it is because you moved PBP in clipped state.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
FWIW: The Toposurface POINTS (the points you place while inside Toposurface editing mode) are relative to the Internal Origin of the Project -- not the Project Base Point. So if you set the Absloute Elevation to zero and place a Point, it will be placed at the IO's Plane.
...I'll add that if you move the Project Based Point while CLIPPED (2019 and earlier), everything moves. Essentially, it's smoke and mirrors though. Really, only the Survey Point is moving.
Something is wrong with the site, I cant insert the screencast in the post, so I'm just gonna put the link below. This screencast shows the problem and the solution...
Yes, the topography points are relative to the internal origin. But, moving the PBP in clipped state is like sending people into a warm hole. After they do that, they don't have any idea where that internal origin is. After all this time, I am still confused with Revit coordinate system. All I know is that autodesk help says "unclip before moving PBP or SP". So, here this screencast shows what folks can do if they forgot to unclip and suddenly got themselves swimming in a warm hole.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
Locating the Internal Origin in pre-2020 versions is done by right-clicking on the UNCLIPPED Project Base Point and clicking "Move to Startup Location".
In this screencast I did just that, but that wasn't enough to fix the issue that this member is having.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
Where are you receiving your insight from? Have you worked with this OP regarding this issue before? I only see the OP's one post and no follow-up posts from him/her.
I'm not sure if I understood the question well. Do you ask me what is my source? I had to work on some projects that I got from a 3rd party. Those projects had this issue. I busted my head about this and then just experimented...
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
No, you misunderstood me. You said above "that wasn't enough to fix the issue that this member is having". How do you know this?
I'm using English for more than ten years and sometimes still say things in a wrong way. So, I apologize for that. What I meant was:
"A long time ago, I had a similar issue like this member has now and just moving PBP to start up location wasn't enough to fix it"
The topography point elevation is the absolute one and if its value is zero and at the same time ON the ground level, we can only assume that what this guy wants is to match the ground level elevation with the sea level. Well, now he can't do that cause he moved PBP when it was clipped.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
@Ilic.Andrej wrote:
we can only assume that what this guy wants is to match the ground level elevation with the sea level.
Well, that's the case, then all the OP needs to do is drag the Toposurface up in Elevation/Section View.
@barthbradley wrote:
@Ilic.Andrej wrote:
we can only assume that what this guy wants is to match the ground level elevation with the sea level.
Well, that's the case, then all the OP needs to do is drag the Toposurface up in Elevation/Section View.
Yes, but then if he adds new toposurface points afterwards, everything will be messed up again. He would need to move the toposurface down then back up and so on, undermining the fact that the coordinates are messed up.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
Coordinates? I am not following you. Spot Elevations and Contours labels, and what not, report Z distances relative to their "Elevation Base" setting, which is typically the Survey Point. It has nothing to do with the altitude of the Toposurface (or the Toposurface's Internal Point Elevations) in the Project
@barthbradley wrote:
Coordinates? I am not following you. Spot Elevations and Contours labels, and what not, report Z distances relative to their "Elevation Base" setting, which is typically the Survey Point. It has nothing to do with the altitude of the Toposurface (or the Toposurface's Internal Point Elevations) in the Project
Why would spot elevation value be different than the actual altitude? I have never seen a survey that has that kind of annotation. This is why I think that the spot elevation value should match the toposurface internal point elevation. It can be achieved only if the survey point was moved when unclipped. I guess when Revit says "Elevation origin: Survey Point", it actually refers to "Elevation origin: Survey Point Origin", not the position of the point itself.
Andrej Ilić
phonetical: ændreɪ ilich
MSc Arch
Autodesk Expert Elite Alumni
It's all relative. Alternatively, the OP could model his Toposurface in a separate "Site" Project, Link his building into that "Site" Project and then lower the Building.
Thank you so much for the very professional video clip and explanation you ofered . Excuse me for the late follow up as i had to experiment on it for a bit before replying and also had to go to my office, In this project you explanation was quite corrrect , but i also found out what @barthbradley said about the internal origin post which the Revit software wont let you change . So , when you drag the PBP or Survey Point away from the internal origin point , you may set up the datum level at that point by 'specify coordinate point' option and making whatever line of that to be the PBP 'ZERO' . But as @barthbradley said the internal origin point wont move, the topography points still use this internal origin as their absolute orih]gin point . So , You may have to drag whatever 'PBP zero' of the elevation you have created to actually make it same as the 'internal origin zero' and therfore make it same as the level line altitude. I hope what i say make sense. In the screenshot i have done again , you can see that i have set up the foundation level to be zero and also suing the 'specify coordinatepoint' option , you can even right click on the pbp and unclip and set the elevation to zero , it will automatically align itself with this line . But when you right click on it and click 'move to startup location , it will always still go to ththe internal base point of the project( which you cannot move). So i thank you and @barthbradley alot for your discussions ...
thank you so much fior your help . sorry for the late follow up as i had to experiment abit and had to go to my office . Your discussion with @Ilic.Andrej really helped me out . Also , i may have found out some other important tips that you may also not have noticed and have explained in my reply to @Ilic.Andrej . Please feel free to read on it and let me know if it's correct . Thanks again
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.