ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Sanjivani Ichake — Fri, 26 Aug 2022 06:44:25 GMT

Hi Ryan,

As discussed over email, below GetRelatedInstance symbol expression will help you to fetch Length of continuous or non continuous mesh element.

this.GetRelatedInstance("OnSameElement:0:MeshSurfaceEntity").GetRelatedInstance("Component__Entity_Embedding:1:Corridor").GetRelatedInstance("Component__Entity_Embedding:0:LinearEntity3d").GetElement().LinearElement_Length3d

I am adding these details here, just to inform other guys about this use case solution and about new blog of GetRelatedInstance expression. This will help them to refer it for future use cases.

Above expression looks pretty complex as there are various relationships involved. To form such expressions, you will need some understanding of internal relationships between elements. To get insight into relationships, we have key-in “ecx items dump” which dumps all instance data of dgn file in one xml file.
I have published one blog recently to give an overview of how to use GetRelatedInstance and how to use the ecx item dump tool.
Here is the blog link:

Creating-item-type-expression-with-GetrRlatedInstance

Regards,
Sanjivani

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Ryan McCormack — Mon, 13 Sep 2021 22:11:47 GMT

Thanks for looking into this Paul and Jan!

Regards,

Ryan

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Jan Šlegr — Mon, 13 Sep 2021 16:03:35 GMT

Hi Ryan,

thanks for the file, that's great there is no workspace/workset dependency.

Unfortunately, I think there is no simple solution available. It's possible to obtain Start and End Stations using these expressions:

this.GetRelatedInstance("OnSameElement:0:MeshSurfaceEntity").MeshSurfaceEntity_StartStation

this.GetRelatedInstance("OnSameElement:0:MeshSurfaceEntity").MeshSurfaceEntity_EndStation

but the results are strings, not numbers, so the distance (difference between start and end) cannot be calculated. I do not know ORD well enough, but I guess it's because the station can be formatted text, and not always simple number. Plus, there is no expression available to convert string to number.

It seems that the length (and direction) is available internally, but to analyze, whether this information can be reached from Item Type element, requires perfect knowledge of ORD internal EC data model ... or to play a day or two with expressions and C# code to check all dependencies, whether such information exists in some EC class.

With regards,

Jan

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Paul Cusack — Mon, 13 Sep 2021 05:52:29 GMT

Hi Ryan,

I'm not aware of any short term plans for that. Whilst I understand that you would see the length as End Station - Start Station the mesh element itself doesn't carry a length property and it could become confusing if applying clipping to the corridor or other changes that modify the mesh. Something for us to think about though as we expand capabilities for digital engineering requirements.

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Ryan McCormack — Mon, 13 Sep 2021 04:26:46 GMT

communities.bentley.com/.../Item-Types-_2D00_-For-BeCommunities-Question.dgn

Hi Jan,

Please find attached a simple model as an example (the file was created in ORD 10.10.01.03 with no workspace/workset). In the file a barrier template has been used in a corridor to create a barrier element. I have then added Item Types to the element called "Item Type Test". I would like to be able to populate the "Length" Item Type with the length of the barrier element.

Please let me know if you require any additional information. Any help would be appreciated.

Regards,

Ryan

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Jan Šlegr — Fri, 10 Sep 2021 07:42:30 GMT

Hi Ryan,

is it possible to share a simple model as an example? A problem with civil model is that it's complex internally (with a plenty of relations) and Item Type can be attached on different places, which can lead to different expressions.

Something like a few elements, with attached Item Type with empty expression with explanation "this parameter from this element should be displayed" may help with the analysis, whether the expression can be created or such functionality has to be implemented by Bentley internally.

With regards,

Jan

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Ryan McCormack — Fri, 10 Sep 2021 06:30:26 GMT

Thanks Paul,

Do you know if it is planned to to make available the same level of information on the components/elements as there is currently on the points/3D linear elements in future releases?

It would be ideal if information such as length, corridor name, horizontal name and profile name (which are currently available on the points/3D linear elements) were also available on the components/elements.

Ryan

RE: ORD 2021 R1 (10.10.01.03) - Item Types - Element Length Expression

Paul Cusack — Fri, 10 Sep 2021 04:49:56 GMT

Hi Ryan,

For template points that become 3D linear elements in the corridor model you can use this.GetElement().LinearElement_Length3d, or if you are seeking a 2D length you can use this.GetElement().LinearElement_Length