Lane Subassembly Start and End Width

[barrz84]

I'm unfamiliar with Subassembly composer however, I was wondering if anyone had created a lane subassembly with start width and end width to perform simple lane width corridor transitions without having to draft polylines/featurelines etc and target them when the computer can do it for you?!!

I still can't believe this isn't an OOTB subassembly!

Also if anyone knows of a global database of custom subassemblies that people have created and shared for others to enjoy please send me a link!! No luck with google!

Thanks in advance!

Brad

[Yonas89]

Hello, Brad,

you still need to tell your corridor how to react at certain situations. We usually use offset alignments as offset targets to perform transitions regions. However if you don't like using offset targets, it's always possible to create custom subassembly, which would do it without targets, but then you will have to split your corridor into many regions I guess. If you could tell me exactly what you need, I can try to create one for you.

[mathewkol]

Brad, I believe such a subassembly would actually be very limiting and this is why it has not been included. The current method of using plan geometry to control Lane width transitions is very quick and easy, especially with alignment offsets as Yonas89 suggested.

If your proposed subassembly were introduced, how would you handle a road where the label lives in an out many times? Multiple regions and multiple assemblies? This is not efficient.

Unless I'm misunderstanding the intent of your idea.

[mathewkol]

OK, auto correct. I meant "...where the lane goes in and out...", not "...where the label lives in and out..."

Sorry.

[barrz84]

Hi Yonas89,

I know about offset alignments as targets etc etc and have done many in my time however, I'm purely after a assembly I can use within the one region to transition my lane width. Therefore all I need is the standard lane assembly but with 2 width inputs - start width and end width. This way I can create a region 20m long and over that length it transitions between the 2 lane widths without the need for any targets etc.

Thanks!

[barrz84]

Hi Matthew,

I think you are misunderstanding the intent.

Maybe for highway design or long straight alignments the offset alignments and widening tools are great however, I'm working with tight horizontal geometry with many compound curves and reverse curves in a land division. For me to spend the time trying to draft some polyline targets rather than have a 30m region in my corridor that transitions automatically from 4.0m to 3.5m lane width around a tricky horizontal alignment...I think I know which I'd prefer! Let the computer do it! Other civil design softwares have this basic process.

Cheers!

[cwr-pae]

That is something that has been missing from C3D since the beginning. The ability to have a region transition from the preceding regions assembly to the following regions assembly. Maybe put it in the Idea Station?

[Yonas89]

Hello Brad,

I have made a quick pilot subassembly, which basically creates a linear transition of your lane width in your region, depending on your  start/end width input parameters. I hope it's what you are aiming to do.

[barrz84]

Hi Yonas89,

That is almost exactly what I need! 

If the OOTB subassembly 'LaneSuperelevationAOR' had this one extra parameter I'd be set!

The only thing with yours is there's no 'lane slope' input? Other than that I think I could work out how to add a few more layers of pavement depth and add some link codes to work with my code set. Just need some tutorials on SAC and i'll be right!

Thanks!

[Yonas89 · Accepted solution]

Hello Brad,

well I just wanted to show you the way how it can be done. I have modified a subassembly a bit according your needs. I added slope and superelevation options, and also availability to overwrite codes of links points and shape to those which are most suitable to your code set style, thus you can assemble as many layers as you want.

[barrz84]

Thankyou so much Yonas89 that is perfect!!

Exactly what I've been looking for on many occasions!!

Now if they had a subassembly for a kerb that you could input start and end dimensions we could also transition kerb types within a corridor region!

Thanks again!

[Yonas89]

aa, that's interesting. I'm glad I was able to help.

[Anonymous]

I just used your transition .pkt and was wondering how you came up with the formula:

StartWidth+((Baseline.Station-Baseline.RegionStart)*(EndWidth-StartWidth))/(Baseline.RegionEnd-Baseline.RegionStart)

to define the variable "define variable"?

Thanks in advance.

Sean

[Yonas89]

Hey @Anonymous,

not sure if this is what you have asked for, but please find this attached image below. It's a simple mathematical proportion I have used.

[Anonymous]

Many thanks! That's plenty of info. And more thanks for replying so quickly. Have a great day!!!