# Base coordinate points problem :/

**URL:** <https://forum.dynamobim.com/t/base-coordinate-points-problem/34287>\
**Category:** Uncategorized\
**Created:** [April 2, 2019, 11:07am UTC](https://forum.dynamobim.com/t/base-coordinate-points-problem/34287 "2019-04-02T11:07:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdu2736](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@abdu2736](https://forum.dynamobim.com/u/abdu2736)\
**Post date:** [April 2, 2019, 11:07am UTC](https://forum.dynamobim.com/t/base-coordinate-points-problem/34287/1 "2019-04-02T11:07:33Z")

</div>

Hi 🙂  
I got a problem recently regarding placing a family from point (x,y,x) from node _ClashDetection.mGetClashPoint_ and after i convert it from m to mm. I place the families using note FamilyInstance.ByPoint. very thing is good when the project on 0,0,0 base coordinate points. But when i am sett the project in the right coordinate points it the note FamilyInstance.ByPoint it places the families far away from the model, i hope someone could help me with it 🙂

thank you in advance

 ![Clash%20001](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/3/9/392cf37a9b759bb93248bef7a57d679902c05ceb.jpeg) ![Clash%20002](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/3/e/3e7fb7cdd74030318e7f4541abd49aa0241dab63.jpeg)

---

<div class="post-metadata">

**Author:** ![callbowen](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/callbowen/32/70818_2.png) [@callbowen](https://forum.dynamobim.com/u/callbowen)\
**Post date:** [April 2, 2019, 10:35pm UTC](https://forum.dynamobim.com/t/base-coordinate-points-problem/34287/2 "2019-04-02T22:35:53Z")

</div>

Are you pulling your geometry from linked models? If so, I would take a look at this thread: [Bimorph nodes v2.2 adds holistic support for linked-element clash detection with new LinkElement nodes](https://forum.dynamobim.com/t/bimorph-nodes-v2-2-adds-holistic-support-for-linked-element-clash-detection-with-new-linkelement-nodes/18816)  
Thomas Mahon goes into detail on how to make linked objects show up in the right location. The section you would be looking for is titled: " LinkElements Solve the Revit API Linked Element Transform Limitation"

---

<div class="post-metadata">

**Author:** ![abdu2736](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@abdu2736](https://forum.dynamobim.com/u/abdu2736)\
**Post date:** [April 3, 2019, 5:00am UTC](https://forum.dynamobim.com/t/base-coordinate-points-problem/34287/3 "2019-04-03T05:00:35Z")

</div>

It’s structure model linked with MEP model !

---

<div class="post-metadata">

**Author:** ![callbowen](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/callbowen/32/70818_2.png) [@callbowen](https://forum.dynamobim.com/u/callbowen)\
**Post date:** [April 3, 2019, 2:46pm UTC](https://forum.dynamobim.com/t/base-coordinate-points-problem/34287/4 "2019-04-03T14:46:12Z")

</div>

Good to know! I have found that the easiest way for me to run clash detection with a linked model is by using the Bimorph package. There is a node inside the package that pulls the linked elements in their HOST location (meaning where they currently are in the model). Most of the OOTB nodes pull the location of linked elements from where they are in the LINKED model. (Which, if I understand your problem correctly, is what is going on with your model.)

What I would recommend is looking at Thomas Mahon’s post from my previous link and he explains in detail how to correct your problem.

> [@Bimorph nodes v2.2 adds holistic support for linked-element clash detection with new LinkElement nodes](https://forum.dynamobim.com/t/bimorph-nodes-v2-2-adds-holistic-support-for-linked-element-clash-detection-with-new-linkelement-nodes/18816/1):
>
> ### LinkElements Inherit Dynamo’s Element Class
> 
> To maximise functionality, LinkElements inherit from Dynamo’s Revit.Elements.Element class, meaning instances are compatible with all of Dynamo’s Element nodes and any other nodes that accept Elements as inputs.
> 
> There are some limitations with certain nodes in Dynamo’s Revit library that will not recognise LinkElements. For example, LinkElement Room’s are not compatible with the OOTB Room nodes, such as Room.Number. To resolve these issues, use the LinkElement.Element node to extract the wrapped Revit element (i.e. the Dynamo Revit Element) stored in the LinkElement and pass it into any nodes that are affected by this problem:
> 
> ![LinkElement-Dynamo-Element-BimorphNodes-v2-2](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/5/a/5acf0966681bc051a5b61b8bcfb827d08e567169.png)
> 
> One drawback of extracting the Element is the loss of properties provided by the LinkElement. It means that any operations, such as geometry extraction, revert back to the linked elements origin-to-origin location. To manually resolve this issue, use the OOTB Geometry.Translate node and input the corresponding LinkElements TotalTransform as the ‘context coordinate system’. The ‘from coordinate system’ is always Identity:
> 
> ![LinkElement-TotalTransformed-BimorphNodes-v2-2.png](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/d/9/d90fa145d22d2606189bab0af2b93216ab2f26ca.png)
