Hello all,
I'm trying to run end-area volumes through an intersection which has custom linestring sections added in areas of the curb returns. The areas for the components are caluclated but the cut/fill areas and volumes don't pick up until I'm back into the perpendicular sections. Is it possible to load the custom cross section set into the End-Area Volumes dialog somehow?
If Inroads is limited to volumes in areas of only perpendicular sections, does anyone have a good way around this? I was thinking of merging the surfaces, but I'd get an area of overlap when I run the second set.
IR XM (v08.09.02.16)
Greetings-
You say you have "custom cross sections". How were these customized? Typically, if one needs to tweak any cross sections that InRoads has produced, one is restricted to only three MicroStation tools:
Modify element
Insert Vertex
Delete Vertex
And that is all. Sure, you can use other tools, but the moment you do, Inroads will no longer recognize the graphics for that section, and therefore will not calculate a volume for that section.
Merging the surfaces to get one DTM to evaluate against is not a bad idea. In that circumstance I would add a volume exception on one set of the sections (since you'll still need two sets of sections - one for each intersecting road) . The exception could start and end at the outside ends of the radius resturns in the intersection. That way, you won't end up double counting the volumes. To check your results, you can run a triangle volume of the merged DTM, and compare that to the results from both sets of sections added together; if you are with a few percent that's generally a good indication your volumes are correct.
HTH,
Jeff
They're custom cross sections directly from the Create Cross Section dialog (create custom cross sections>custom). I have not edited them in any way.
I've included linestrings around the areas of the curb returns in addition to the custom station range. Since they're directly from inroads, I would assume the end-area volume report would pick up quantities from these linestring sections, but it skips over them, whereas, running a points report for example, will not skip these sections.
Thanks for your input, Jeff. I'm going to be testing out volumes from merging the surfaces and see what I can come up with. Hopefully the volume differences are negligible.
End area volumes are not computed on skewed cross sections.
Thanks,
Jason Smithey