I was hoping you might have something in there that would help us solve the issues we're having with "Export Road", but I fear there is no solution at this time. But just in case, this is what we're running into... Is there any way around these issues, or is it in the realm of "wishing"?
The basic issue we run into is that we regularly do not have an existing ground surface. We have plans for a roadway, with typical sections, but no real EG. So we can't really build a corridor with Daylight subassemblies, and target them to the EG surface in C3D.
In the "old days", this wasn't a problem. But without a target, the Daylight subassemblies are deleted from the built corridor, and never make it to the "Export Road" routine.
And even when we DO have (or can manage to fake) an EG surface, the conditions may be different when the roadway is actually slopestaked. So a station that may look like it's in a cut situation in the computer is really in a fill situation when the field guy gets out there to stake it. Unfortunately, the current behavior of the "Export Road" routine does not seem to function in a manner that allows this to be easily-fixed. True, if the outside catch points are converted to slopes, it DOES create a slope that goes in both directions. But it uses the same slope for both, so it doesn't work for situations where we need (e.g.) a 4:1 slope in cut situations, and a 3:1 slope in fill situations.
We've been able to make SOME use of this stuff. For example, we can omit the daylight slopes from our corridor model. Then we do "Export Road" to dump out the job file, which we then convert to a DC file and dump back into TGO. Then, in TGO, we can add the final cut/fill slopes to the outside of each template. But this involves a lot of manual work in TGO, which we'd prefer to omit.
So, any of this sound familiar?
Sinc