Shared Coordinate System

I am trying rhino inside Revit and I am impressed. It changes the Revit level.
Nevertheless, I have a problem. Usual in Revit I link a cad file with the property boundaries. Then I rotate this cad link in a way that my new building be parallel in the view. I acquire coordinates from my cad file in the Revit file and I have two coordinate systems. The project coordinate system and the cad true oriented coordinate system. This is important because Revit needs to know the correct north, especially for shadow studies.
If I understand correctly, rhino inside connects with Revit by internal coordinate point.
Is there a way to make the connection with shared coordinate system?

1 Like

Here are a couple python components geared towards locations, these are typically intermediate scripts until the components are added to RiR.

Playing around with these a bit i’m only getting the current document location, not links or instantiated instances of links document locations.

Hi,

Thanks for your comments.

You are right the Rhino model, so Grasshopper, and the Revit model are aligned at the Rhino Model Origin (0,0,0) and Revit Internal Origin (0,0,0) using same X, Y and Z axis. Currently there is no way to change this, doing so would add a loot of compexlity to the whole Add-in, but would nice to understand exactly what you mean and see if we can remove part of the inconvenience here.

Could you please elaborate more why do you need the connection uses shared coordinates?
Would that help in this specific situation, or is it more a general question?
In the case the Survey Point was placed at point (10, 20, 30), and true north at 90º, do you expect the point (A, B, C) in Rhino-Grasshopper corresponds to the point (B + 10, A + 20, C + 30) in Revit?
Would it help if we provide some components to transform from one coordinate system to the other?

I want to model the site in rhino. Revit site tools are not good and I found that the translation of a rhino mesh to a Revit topo terrain works unexpectedly well. The triangles remain the same witch is just perfect.
In Revit, I want to model the building. But normally I don’t want my building plans to be parallel to the paper (screen). In reality, the actual position of a building is not parallel to the screen. In Revit, I solve this problem with the shared coordinates system. If I export my model using the shared coordinate system and import it in rhino the building aligned correctly in space. But when connecting with rhino inside the building aligned with Revit internal point and it’s not placed correctly in space.
The transformation normally is just a rotation from a specific point and a move.
This must be applied at the beginning of the grasshopper project, independent, and effect the translation vise versa.
More advanced it could apply also a 2d (not 3d) scale factor so it would be able to support transformations from projected geographic systems, which normally used for site design, in local systems suitable for building design.

1 Like

Similarly when i query the elements of linked file it returns the elements at the original location.

In this case i’m looking to harvest the multiple transformed locations of linked documents and transform what i need from the original xyz. Which is i believe what you would want to do with your building to site as well.

If I understood you well you want to model in Shared Coordinate System in Rhino.

What about orienting the building preview in Rhino into Shared Coordinate System and do the opposite with the terrain points?

The first group will preview the Building in Shared Coordinates.
The second one will take the points in Shared Coordinates and will convert them to Internal Origin coordinates to place the Terrain at the correct place.

Do that work for you?

1 Like

Hi @kike,

Where do you get the component from (circled in red) … I cant find it?

They’re here


2 Likes

perfect

1 Like

Hello @stephan.s is the “Internal Origin” component custom python? I don’t see in the Rhino Inside gh components?

Hi @skott,

The Internal Origin is here, but is not visible by default.

Internal origin is always equal to World XY plane

2 Likes

Kike, thanks for useful advices here! I also faced that problem and my goal is to analize Revit Elements from different links for intersection. The problem is that our models set up based on shared coordinates, so the internal origins dont match in Revit. That causes wrong positioning in Rhino Inside. Solution that you mentioned before does not help with Revit Elements (not Geometry), does it? Is it possible to fix and get it to work correctly in RhinoInside or the only way is to fix it in Revit(if yes-how?) Thanks in advice!

You’ll need to use a Orient component (Plane to Plane Transform) in grasshopper on the geometry.

Hi, Japhy, as i mentioned there is no need to transform geometry for me because i dont deal with geometry, but with revit elements. Plane to plane transforms geometry. i need later to find intersections between elements from two links with different internal origin. any other option?

How are you analyzing the Revit Elements? Its seems a some point you will need the geometry from the link, which will need to be transformed (which is what is happening in Revit by Linking to different origins)

I got few linked files setted up in coordination file.I need to find elements intersection Architectural with Heating. Each has different internal origin.That cannot be correctly intersecting if we use Origin to Origin link insert, thats why we used Shared coordinates to set links, so those links intersects properly only by shared coordinates. Im trying to use filter “Intersect Elements Filter” for Architectural project with Heating link( after that im deaaling with data tree structures ), so that i can find intersection points and place some openings in those points. The problem is that “Intersect Elements Filter” doesnt show me any intersections, cause the elements aren’t intersect by Internal Origin. Just in case that Links are placed by Shared coordinates system. Thats why I ask if there is the way to get elements location from both Links setted up by Shared Coordinates (and not by internal origin).

I’ll see if they’ve changed anything since this 2018 post but transforming Element Geometry seems the way to go.