Link Code hatching through transitions

[jmartt]

I'm a bit behind the curve on this, I'd bet, but I hope I'm just not finding what I need instead of finding a limitation, because I'd really like to use this.

I've got a curb assembly that I can attach to a feature line at TBC. I've got another curb assembly that has the same Point Codes, but has a depressed back. For landings at ramps and such. I can assign these assemblies to different regions as I have below. (The two assemblies look the same in plan view, but they've different height backs.)

If I extract feature lines from this corridor, the autofeaturelines span the transitions. That's fine. See below.

But I can't get the Material Area Fill Style from the Link Code in my Corridor code set to span the transitions as well and make it all "hatched" as concrete.

Oh, how I'd like it to.

Am I missing something?

[BrianHailey · Accepted solution]

The hatching is based off the links of the corridor. If you don't have links in the transition, there's no hatching there.

One thing you could do as a work around is to add the baseline into the corridor again for just the hatching and not use it for anything else.

[jmartt]

Thanks, Brian. That's exactly what I did. This particular example is nice that way because the two assemblies look the same in plan, so I can just run a "dummy" regular curb corridor over the entire thing. But I was/am worried that someone, maybe even me, will come back later and mistake the dummy for the real one. 

It is nice to have some confirmation that this is the way it is supposed to work. Thanks again.

[jmartt]

OH! I reread your post and realized that I don't have to make an entirely new corridor for the hatching. I can just, as you say, add the baseline into the SAME corridor again and use it just for hatching. I can even turn off the featurelines in the hatch assembly so I don't get doubles. I did not know you could do that. Very nice!

[Simon_Blain · Accepted solution]

If you don't want 20 zillions regions (small exagerations ahah) and it will also give you a full lenght fline (transition length might not be perfect though, will have to check) you could create a subassembly with the 2 options inside it. That should also fix your hatching problem I imagine.

Without a target it will do the normal curb, if it finds a target it will do the depressed curb (that's how I did mine anyways) if the points have the same code it'll create a single fline the whole way threw.

For easy targets, put them all on the same layer and use select by layer in the corridor target options (make sure they are polyline (or 3d or fline) and not simply line as these don't count for tagets)

See ss for an exemple (it's the same subassembly in the 2 images)

[jmartt]

That's interesting.

I think you've changed the way I'm going to approach this. I think it has mainly to do with the attachment point. I've been trying to work with an attachment point at top back of curb. If I made the attachment point the flowline, then I could control the top of curb with the target FLs (nice suggestion with the ByLayer selection) and I could also change the catch/spill curb transitions with similar FLs for edge of pavement/lip of gutter. It's not really a big deal, I wouldn't think, to add in the transition lengths onto these target FLs. I could even change from curb with gutter to curb without gutter by targeting a horizontal edge of pavement FL. Then, I'd have one corridor for all the curb with one region and continuous FLs and hatching. Top drawer, man. Thanks!

[Simon_Blain]

Happy to have helped 🙂