Hi,
This is the first time i have such a problem while setting up models.
Using the survey point as a reference, my spot elevation and points (survey and base) Z values are multiplicated by 25.411....
All my units are in mm
Levels set to survey point
Spot elevation units set to survey point.
And this is what i get as a result: 153231/6030 = 25.411...
Let's say i move my survey point from Z : 0 by 1000mm.
I get the same factor in the values. How is it possible and how to solve this problem?
Gelöst! Gehe zur Lösung
Gelöst von RDAOU. Gehe zur Lösung
Edit your level tag and check that the label for the level parameter is not set to override the general units settings.
-luc
My level family uses the default Elevation parameter as the label from the revit file. The family does overide the units but as mm.
The spot elevation uses default units
When i do change the units from mm to imperial, the unit changes but i still get the 25.4x. (note that the level family overides to mm as stated)
The closest i can get is changing it to inches but then my level is at 237.4....
25.4 thats a fixed 10"
Autodesk introduced in 2022 some changes to the way revit API handles units (imperial API). But I can't imagine this could be related.
YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION
@RDAOU
1. Revit 2021.1.3 I looked this morning and there was no new hotfix or update availlable.
2. I noticed it last week when my team told me there was a difference in elevation values between CAD they had of the existing building and the model. The ''master file'' was given to us by the client who wanted us to start with it. Could it be that they started the template Imperial and then switched to Metric?
3. I cleaned some infos in the file as this is an ongoing project (removed logos and client/project data)
The view i used is:
The issue is not what I thought it would be...The wrong readings you are getting is caused by acquiring coordinates from a Linked Document with a specified/defined GIS coordinate system which is using different units or has not been set out properly (or both)....I cannot tell without checking the parent link where the coordinates have been acquired from...Notice in the below GIF the actual height/elevation between survey point and project base point...When I link an blank/untampered with Model with IO/PBP/SP all at 0,0,0 and Acquire coordinates to reset the GIS Coordinate system ... The readings of the PBP and SP in your project go back to normal.
How to fix this issue: Go back to the root cause and check the Link wherefrom the coordinates were originally acquired, fix it there, then reload into your project and acquire coordinates again
SIDE NOTE: You should keep the internal origin side by side to the Project Base Point. It is not a big issue in your project but just not where I would imagine it to be with respect to the project.
YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION
@RDAOU
Thanks it is much appreciated. The file we acquired the coordinate from is a template given by the stakeholder. They asked us to acquire the coordinate from it and use it as a master file for existing levels and grids.
From what i understand: we need to reset de coordinate system of their template, reacquire from a surveyor plan and that should fix it? The problem would have been caused by the units of the surveyor plan used acquire the coordinates and their template's one not being the same?
As for the Internal Origin, i normally put in on the ground floor this way:
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.