Hi guys.
Can anyone explain why the BaseRegion AppliedAssemblyCollection return the Applied assembly Id for the previous Region when the regions are continuous? I know this was adressed by @Paolo_Emilio_Serra1 in Baseline.Region startstation skipped - #2 by Paolo_Emilio_Serra1. However I’m interested in where this first section is stored and how to expose it because ExportCorridorToSolids seem to find the right data to create two different applied sections at the region break. Also featurelines are made with the right points and corridors disply just fine… it must be store somewhere isnt it?
by the way: LandXML export generated the same behaviour as the API.
I tried getting the applied assemblieds with the AppliedAssemblies with the API (property on baselineregions):
’
Several options and disadvantage:
create a small gap → this is quite visible in other software like Navisworks
drop region on every iteration → corridor rebuild necessary
single baseline + regions combination → basically the designers split regions quite often reintroducing this problem