[ORD] Cross sections to even heights?

This may be something I'll have to live with, but I'm going to need your help explaining it to my PMs.

I see when I place my named boundaries, I have the option to define the "envelope" around my section - min. distance above and below the actual section linework. This does indeed give me a buffer of (say) 5' above the highest elevation in the section. But it's literally 5' above the highest elevation, whatever that may be.

The bottom elevation of the grid appears to be set to an even 5' increment, like 735. But the top of the grid is not at an even 5' increment it's not even at an even 1' increment. I have two consecutive sections, one of which has grid to 752.07, and another to 751.70. Why...???

Like, no, I get the logic of what is happening. But it looks bad (to me) and my engineers are VERY used to seeing grids to even 5' increments. Preferably the same size when possible. This "whatever" elevation is likely to cause consternation and complaints. So I'd like to find some way around it if I can! If a cross section can fit between 735 and 752.47, it can certainly fit on a grid from 735 to 755. This is what we are all used to seeing, and this is what I would like to create.

Is there any known way to create a rounded ceiling instead of a hard envelope for generating cross section boundaries/drawings? Is there any way to edit the height of the named boundaries after placement, to force them to an "even height"?

Parents
  • Easiest way I've found is to create a TM with 2 breaklines at the elevations that you want your grid band elevation. So for your example, a min. breakline at constant elevation 735 and a max. breakline at constant elevation 755. Create a TM of those 2 elements and use a FD that places it on a construction level. I usually have these breaklines located at a constant offset (offset geometry = offset I am showing in my XS grid) relative to the baseline I am placing named boundaries about. Set your clearances to be 0 for top and bottom. This method works pretty well when you don't have a lot of elevation change across your project. If you do, make multiple TMs through the ranges/elevation bands you want to see. Create a named boundary group for the first range, then append to that group to get the rest.

    HTH,

    Justin

    Justin Guiliano, PE

    Answer Verified By: MaryB 

  • That's exactly what I was thinking about. I'm in "flyover country" - some projects have notable elevation changes, but a lot of them don't.

    No different than what I used to do in Geopak to get my sections spaced properly on my sheets - I would create a construction shape to cover the desired elevation range.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Yeah, and now the grids run up to some "random" elevation...It's not wrong but it's not the way people want to see things 'round here.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Can they complain when Excel or Word does something different than the way they want to see it?

    When we first started using CAD, some people complained that the way Stationing on alignments looked, was different than how we drafted it. A few even went so far as to change it manually to look like it always looked. Doing so broke up every element of an alignment into separate pieces at every 50' increment. Then, they complained when their files seemed slow.

    One department even had a custom program written to draw stationing "their way". I am glad we are beyond that.

    In some ways, the argument that "This is what the program does automatically. If you want something different, be prepared to pay someone to manually modify it every time, for every change, for every project from now on." will hopefully dissuade them from their possition. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • Oh, I know...

    It's actually funny to me that items like cross section grids will be that big a deal. I have one engineer who INSISTED that there HAD to be three cross sections on a sheet, no matter what the software was going to do about it. 

    But I also recall getting into a surprisingly heated discussion about the fact the 11x17 printouts were not exactly half-sized sheets of  24x36 plans. I tried to explain that for a true half-size, we needed to create 22x34 full-size plans instead, but he was convinced that I was too lazy to figure it out, and just plain wrong.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Not every Engineer is as smart as they think they are.

    We actually changed our standard plan sheets from 24 X 26 to 22 X 34 so we could get true half size drawings. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • But is it a real issue if it is a personal preference vs. something that is an actual CADD standard?

    That is a big thing that held us back  in the early days of ORD, but we have since just focused on what is actually required by the client and things are much better now.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.1  |  ProjectWise 2023

Reply Children
No Data