In Legacy InRoads, when you used a curve on a survey, by default, it strokes both horizontal and vertical but offered a toggle for each when you wrote to graphics or wrote to a surface.
We used to always stroke both. However, I knew this caused some minor issues on intersection curb returns when there were sidewalk curb-cuts for ADA ramps. The bottom of curb shots were always OK, but the top of curb shots would fit a curve both horizontally and vertically around the curb radius attempting to make a smooth curve both ways. What this resulted in, on the vertical side, was to cause an upward bulge as the figure was leading into the top of the curb cut. Then as the top of curb sloped down the curb cut, the vertical figure would pass through the shots at the top of the curb cut and the bottom of the curb cut. Then, the figure would bulge down, lower than the bottom of the curb before then passing through the bottom and top of the curb cut on the opposite side of the ADA ramp. Finally, after passing through the top of the curb cut point, it would again bulge upwards before flattening out with the next top of curb shot.
These were thought to be too insignificant to worry about for a long time. Recently however, we had a project to reconstruct a long ramp along the length of a sidewalk. We needed to evaluate the existing slopes using the survey data. The problem was, that this existing sidewalk ramp was a long circular curve with landings every so often as required by ADA standards. When we looked at a profile of the edges and center of the ramp, we could not see the landings clearly.
If we took the survey point elevations and distances between the points, we could calculate slopes, but were perplexed as to what made the survey created DTM appear to not reflect what the elevations indicated.
Recalling the curb-cut ramp issues, as a test, we wrote a new surface, where we only stroked the horizontal curves. This flattened out the vertical lines and the slopes and landings were instantly recognizable on the profile plot.
We setup filters to toggle certain features off and write a portion of the surface. Then a second filter was created to toggle those features off and the other features on before writing the remainder of the survey to the same surface. On one group, the vertical and horizontal curves were stroked and on the other, only the horizontal curves were stroked.
Is there a way to create a similar workflow in Civil Survey? If not, then I believe a CR is in order.
Bump!
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Bump, Bump!
Bump? Has this ever been resolved? We always use stroke horizontally only when constructing our sidewalk in InRoads SS2/SS4. We have the exact same issue. I'm thinking that this might be resolved 7 years later but I would still be interested in knowing how to toggle between both!
P.
Sadly no. I really need to put in a CR on this.
Thanks for the feedback. To our group wanting to move over to ORD from PIRSS4 this would be a major setback (enough to prevent us from changing software) and I could imagine it being the same for many others as well. I am subscribed to this thread, looking forward to seeing how this develops.
Hi Chuck, is there anything I can do to help with getting this CR done? You can contact me by email to discuss at:
peter.vallieres@montreal.caBasically, what we need to do is get the arc in the second image to be "vertically linear" as shown by the dashed curve in the third image. In PIR, we could activate "Horizontal and Vertical Stroking" when writing the survey data to graphics. Which does not seem to be possible OpenRoads. I have got to be missing something.
Caddcop doesn't work for Bentley. He, like the rest of us, is powerless to make Bentley correct anything.
You can always file a Service Ticket with Bentley Support. If there is a workaround, they will let you know, and they can add you to any request for change.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Hi MaryB, I understand perfectly. We are all mere mortals. I've never filed a Service Ticket with Bentley before, that's why I was asking for help or perhaps an existing ticket number to reinforce the need for this update. I guess there should be some kind of portal in the connection client that I can look into for filing requests... I will take a deeper look into things. Thanks for the feedback.
From the CONNECT Center: