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.