[PowerCivil 08.11.09.789] Some inconsistencies in On-demand classes and Feature Definitions

Hi.

I am working my way through the "2 OpenRoads Basics Learning Path". I have some problems following the hands-on workbook for "Pad and Parking Lot Modeling".

I am working with the metric files, but it seems that the following problems also occur in the imperial files.

  1. Missing Settings in the Civil Training Workspace (Version: 1.0, Released: November 2014)
    1. Missing Element Template: Linear/Grade_Draping
    2. Missing Feature Definition: Draft_Draping
    3. Cut and Fill Slope Table 1 seems to be missing some 3D definitions for Constrution Limit / Exterior Line

  2. The referenced terrain model (Existing_Terrain-Metric.dgn) does not show up as a target in the Target Aliasing tool The terrain is set to active.



  3. The Profile Intersection Point can not be extracted for the straight driveway elements as shown in the workbook. Error message: "Elements Dont Intersect".

  • I've attached a cleaned-up version of the beginning metric dgn file.  It now has the same Element Templates and Feature Definitions as the Imperial file.  The new file also has engineering rules rather than just geometry (I'm not sure how the engineering rules got lost, it must have occurred in the translation to metric.

    Concerning your cut and fill templates for the sidewalk, they work fine, the issue seems related to the Existing Terrain/Aliasing problem.

    The absence of Existing Terrain in the Target Aliasing list is odd.  Your error was the first I'd seen.  In the midst of trying a bunch of combinations, including not having the Existing Terrain as the Active Terrain, I was able to "break" the list, like yours, but I could not do it consistently.  It worked all but once. 

    Concerning the driveway: one thing that helps in these “filleted” lines is to select the “full line”.  If you hover over the “gap” – the part of the line cut out by the fillet, it will be available for selection. 

     

    With the metric file you are using, however, the driveway side “line and fillet” relationship does not exist, due to the way the metric file was created.  The Quick Profile Transition steps also will not work.  The updated file maintains the rules and should work. The workaround in your file is to note the radius of the fillets and to delete them.  Use Trim to Intersection to extend the driveway lines to the road Edge of Pavement.  Create the curb returns using Simple Arc Between Elements.  You should be able to continue from there.

    Pad and Parking-Metric-NUWU.dgn


    Jeff Martin, PE, Civil Consultant, Bentley Systems

  • Thanks.

    I will take a look at your tips. I don't doubt that I might have made some mistakes with the Active Terrain. After I sent my message I managed to modify the geometry, so I guess I just learned more through this process.

    I will work my way through the workbook with the updated design file and see if I understand a bit more. :-)

    Regards,
    Thomas Hauglien
    Subsea CAD Engineer
    http://www.reinertsen.com/

  • "Bugs" have a spectrum of reproduceability. Target Aliasing is pretty robust. Because I was able to reproduce it in one case, it proves that you're not delusional (or at least not alone in your delusion). I would have liked to have been able to reproduce it a second time, so I could tell software development how to reproduce it (and, therefore, fix it).

    Jeff Martin, PE, Civil Consultant, Bentley Systems