ORD - Break/Split a 3d Linear Element

Hi everyone,

Bentley have provided a work around, see the attached image. Its a fair bit of work, but it does work.

This issue has been logged. Defect 1135302:Not able to manipulate/break/drop 3D linear elements

Cheers,

Glen

Hey Glen,

Do you know if Bentley has resolved this issue?

I ask that because I have found that using the split curve command removes the first segment of the 3d Linear Element that I am trying to split, removing valuable data.

Cheers,

Keith

Hi Keith,

A quick solution to split the elements for "static" 3d use is to export to DWG (as DWG doesn't support void/gaps in linstrings).

This is not really a bug, because it is the product of your 3d corridor modeling. To avoid the issue Glen had we have adopted a workflow where we use 3 corridors for bridge overpasses - one on each approach and one for the bridge. We then also use clipping boundaries to accomodate bridge skews, etc.

Another method is to use 3 templates- all copies of each other, but with different point names. Then when you apply the 3 template drops (in the same corridor), you will get seperate linestrings per template drop.

Hi Keith,

A quick solution to split the elements for "static" 3d use is to export to DWG (as DWG doesn't support void/gaps in linstrings).

This is not really a bug, because it is the product of your 3d corridor modeling. To avoid the issue Glen had we have adopted a workflow where we use 3 corridors for bridge overpasses - one on each approach and one for the bridge. We then also use clipping boundaries to accomodate bridge skews, etc.

Another method is to use 3 templates- all copies of each other, but with different point names. Then when you apply the 3 template drops (in the same corridor), you will get seperate linestrings per template drop.

Hi Mark,

Thanks for your response, I am trying to create a terrain from information imported from a genio file similarly to what Glen mentioned in his original post and not from a corridor that has been created in ORD.

So as you mentioned a work around for my issue may be to export to .dwg format, but I am assuming it will lose it's feature definition, etc, in doing so?

Thats right - because the source Genio strings have discontinuities in them, the original data can't be used as is to partially triangulate. Although a bit messier you could still export to DWG, reference it in and use Graphical filters to filter by Level, etc. or worst case, use Feature Remapper to create a new Featurized version of the exported data.

Hi,

To me it seams quite obvious that users want to be able to manipulate elements manually and not have to rely on corridor tools and ruled elements all the time.

Instead of (or at least as an alternative) to introducing another corridor, wouldn't it be better to make a move towards introducing user friendly tools for manual manipulation of elements? That is, completely removing the rules and not just partially...

Is there something going on in this direction?

Regards,
Kristoffer Pettersson