ORD 2019 R2 - Crossing Side Slope Annotation Issue

Hi,

I am having some trouble with side slope annotation.

If a corridor contains only cut or fill then the annotation, for the most part, works fine. As soon as there is a crossing slope going from cut to fill the corridor doesn't annotate at all (test11.dgn).

I am using Draft_DNC and Matchline for the cut and fill feature definitions because they make it easier to see the difference between cut and fill in plan view.

A secondary issue I am having is that the annotation works but doesn't go the full length of the earth works. An example being, once annotated, tadpoles only show up for 20m of a 190m length (test10 Junction Tadpoles.dgn).

A final note on this topic, I have noticed that if I use the annotate element tool, it annotates all elements with the same feature definition or level in the whole file. So it's more of a annotate feature definition or level tool rather than being element specific.

Any help with this is appreciated.

Josh

Slope Annotation Issues.zip

Parents
  • Hi Josh,

    We've given up on ORDs Side Slope Annotation for the same reasons you have found and some other random things, plus the fact that you cant annotate Linear Templates and the delay in corridor processing it causes (even though the side slope annotation is not dynamic).

     

    Here is something one of our local Microstation developers, CADDPro, is developing for ORD - in addition to his legacy linear feature batter tick / tadpole tool, the ability to extract batter ticks / tadpoles directly from OpenRoads End Condition Component Meshes themselves, essentially automating the whole process .

     

    I'm betting the fact that there is a "Transverse Features" option in some of the Corridor Feature Definitions that does not do anything that this was the original intent for Side Slope Annotation...

     

    Regards,

    Mark


    OpenRoads Designer 2022 R3 (10.12)  |  Microstation 2023  |  ProjectWise CE 3.4

Reply
  • Hi Josh,

    We've given up on ORDs Side Slope Annotation for the same reasons you have found and some other random things, plus the fact that you cant annotate Linear Templates and the delay in corridor processing it causes (even though the side slope annotation is not dynamic).

     

    Here is something one of our local Microstation developers, CADDPro, is developing for ORD - in addition to his legacy linear feature batter tick / tadpole tool, the ability to extract batter ticks / tadpoles directly from OpenRoads End Condition Component Meshes themselves, essentially automating the whole process .

     

    I'm betting the fact that there is a "Transverse Features" option in some of the Corridor Feature Definitions that does not do anything that this was the original intent for Side Slope Annotation...

     

    Regards,

    Mark


    OpenRoads Designer 2022 R3 (10.12)  |  Microstation 2023  |  ProjectWise CE 3.4

Children