Because we're using reference surfaces. In this case, a reference to a
Proposed Grade surface that was built from a Corridor, Points, and
Breaklines.
Since C3D surfaces cannot directly reference Corridors surfaces, you have to
export that surface. This data is added by adding points to a new surface.
When you do that, it breaks the link between profiles and the surface. We
then add points and breaklines to define typical lot grading. We make a
Shortcut to this surface. If (when) the paving profiles change, that means
the underlying corridor to my PG surf is incorrect, and the surface is wrong
in my shortcuts.
In our search, we found no way to remove the data from the 1st Corridor
iteration from the PG surface, so we have to create a new surface, then add
points and pads again. This new surface is then added to the shortcut menu.
The problem with this approach is that other dwgs that use the shortcut to
generate profile information are now linked to a bad surface. There's no
easy way to repath the XML shortcuts to the new surface, so we just erase
the Reference surface, and create a new one from the new surface. This
requires resampling.
Easy, right? I've gotten the VBA together to sample all the alignments in a
site to a selected surface, so it's not the end of the world, but it would
be nice if it was built in.
JW