Hi @raoufdjema15 excuse for the late reply.
I’m not familiar with that coordinate system (lambert 93) and I’m not sure if Rhino has any option to georeference the document with those units, or perhaps through another third-party plugin.
You can georeference a file in Rhino from the Document Properties > Location:
The 0,0,0 coordinates of your model will correspond to that geolocation, and the one that will be exported to IFC as the georeference.
With the EarthAnchorPoint command you can indicate a point in your model corresponding to the model’s position in latitude, longitude, and elevation.
Hi @raoufdjema15 ,
I’m wondering if the following would work: set Rhino’s EarthAnchorPoint to the origin of Lambert93 (EPSG:2154) in WGS84 coordinates and then moved your geometry based on a known reference point (in EPSG:2154 coordinates) in your model.
When the rhino model is exported using visual arq, does it convert its position in XY according to longitude and latitude of earth anchor point ?
Or is possible to export the IFC with XY position that it has in the rhino model space ?
Our experience with VA at the office so far (really possitive) :
We have made a bit of progress with this at the office. We like how visual arq is user friendly and extensive (espacially with drafting and overall project management).
We are planning to use visualarq for architecture but also for urban design and landscape architcture.
The only problem we are having is with IFC files locations after export.
I use third party softwares such as simple bim, ifc toolbox, or ifc.js to relocate and move ifc exported using visualarq. Wich is not optimal when exchanging ifc file with other companies that want to open it in revit.
My questions are :
How does geometry placement work with visualarq’s ifc placement ?
For instance, if and a geometry with these coordinates : 0,0,1, is exported using ifc, how can i make sure it will land in the same place when linked into revit (for example) ?
We found that defining model base point changes ifc global coordinates and defining earth anchor point changes ifcsite coordinates. But when exporting geometries near rhino’s origin, the ifc geometry gets places very far away, do you know why ?
Is there any plan to assign ifc properties by layer ?