Sheeting a single alignment that has two pgl profiles

RE: Sheeting a single alignment that has two pgl profiles

Dennis Wadas — Thu, 08 Sep 2022 16:32:00 GMT

Nope, because you can project those profiles from the baseline to each offset alignment you need to set a point control on. Keep in mind when you project a profile with vertical curves the projected profile is a chorded line string version of your real profile on the baseline. It's good enough for modeling though.

RE: Sheeting a single alignment that has two pgl profiles

MaryB — Thu, 08 Sep 2022 16:21:13 GMT

I agree with this.

We are required to show a number of profiles, and they all need to be annotated off the baseline. For the plan set we are required to produce, it doesn't matter that I am displaying the profile of the left EOP, it needs to be stationed along along the BL.

As an example, I consider a ditch line profile. We know that the ditch line will not be exactly as long as the baseline because, when the baseline curves back and forth, the offset ditch line will be longer or shorter than the baseline depending on whether it is on the inside or outside of the curve. The people reading my plans do not care. The ditch starts at station X+XX and ends at Y+YY, and the grade shown along the ditch needs to be based on that algebraic station to station length, not the actual length of geometry. I also need straight line segments, with defined PVIs - not a fuzzy projected profile. Let's make this even better, because I often need to show ditch profiles above or below datum for plans readability.

It sounds as if, to properly display this type of design data on my sheets, I need to define all of these profiles on the baseline. But doesn't that defeat the entire purpose of modeling?

RE: Sheeting a single alignment that has two pgl profiles

Shawn Cooke — Thu, 08 Sep 2022 14:57:55 GMT

You may verify you don't need two separate sets of BL stations if their profiles and super are independent (at least at necessary ranges where they will be different) . You can still cut cross sections and associate design intent horizontally off the CL through that range, but your profile data should reflect those stations in addition to alignment BL displayed in planview for clarity.

RE: Sheeting a single alignment that has two pgl profiles

Shawn Cooke — Thu, 08 Sep 2022 14:31:15 GMT

Glad you figured something out! One of the keys to harnessing ORD as a team is file information federation, not only from a software efficiency perspective, but also sharing work among others (even yourself months later ;D) communicating design intent to others and maintaining as much "intuitiveness" as possible. Breaking those out helps describe your intent, yet hold to standards that may or may not pass a compliancy report.

There's nothing wrong with having two separate corridors for each direction of your design. One corridor can point control to another corridor's template point (while each tied to the same CL stationing.) In fact, you can setup your templates used by the two corridors to utilize two separate PGLs as vertical controls. You do not need to use the profile a corridor is placed on as the template vertical control (it does require an active profile, but a floating template origin can make it possible to use a secondary vertical control.)

RE: Sheeting a single alignment that has two pgl profiles

Dennis Wadas — Thu, 08 Sep 2022 14:26:08 GMT

Another reason I want to store my PGL profiles on the centerline alignment is for the annotation of the profile. If I were to store the profile on my offset alignments and then project it to the centerline, I end up with a chorded version of the real profile and it wont annotate vertical curve info (because its now a streched and skewed chorded version of the real profile). This projected profile works great for modeling but not showing the contractor the actual profile info.

RE: Sheeting a single alignment that has two pgl profiles

Shawn Cooke — Thu, 08 Sep 2022 14:16:04 GMT

There are a few concerns with following a set of client standards and isolating the same feature def and its profile symbology (e.g. existing terrain profile display; making a LT_PGL and RT_PGL version). So it could depend on the client workspace. There could be a solution to modify the element template used to assign a version of the feature def to better isolate. Not sure which way around is longer....

RE: Sheeting a single alignment that has two pgl profiles

Dennis Wadas — Thu, 08 Sep 2022 14:15:43 GMT

Yesterday, I actually created my sheets by making a few new levels to put my PGL's on and it worked great. However, our client (the state DOT) will not like me creating new levels outside their dgnlib. With Geopak, I could just create two separate profile drawings with opposing profiles and I was good to go.

I guess another idea would be to just have two alignment files but I'm sure you can imagine what a disaster that could be.

I have performed searches like crazy on this subject and was really surprised nothing much came up. It seems really common to have a divided highway with both sides not following the same profile and all running off a single centerline alignment. Imagine modeling if you do not use a single alignment. You would need to model each side separately because the stationing would not be the same on each side as soon as a curve is introduced.

RE: Sheeting a single alignment that has two pgl profiles

MaryB — Thu, 08 Sep 2022 13:55:01 GMT

I can agree that you may have wanted to create actual PGL alignments to go with your PGL profiles.

Shawn - does your solution mean that ORD doesn't let you filter which profile(s) are shown in sheets? Your solution seems like a long way around, and not entirely intuitive.

RE: Sheeting a single alignment that has two pgl profiles

Shawn Cooke — Thu, 08 Sep 2022 13:31:33 GMT

You could try creating two separate alignment models in your alignment file each containing separate PGL profiles (name the model as needed to describe each), running your profile named boundaries with those separate models. Once one drawing/sheet is made, reference the other profile saved view generated by its "create drawing" as the secondary view. The alignment can be exported as LandXML then imported into the second model.