Why is my corridor surface extending past feature lines created from point codes?

[JD.Borgeson]

I am trying to make a top surface of what will be a gravel drive.  I have a 20' wide crowned surface with shoulders.  I made the subassemblies in composer and assigned the codes to the points crown, edge of travel surface, and edge of gravel/class 7.  when I make a surface using these, I would think it should be pretty straight forward, but for some reason, it is extending beyond the edge of gravel point.  Help?

[ecfernandez]

Hi @JD.Borgeson, I'm keen to check your *.pkt file if you can post it to see if there are any issues related to codes. Meanwhile, you can add a boundary to your surface to get the desired result.

I have experienced the same issue with top surfaces even with the C3D preloaded subassemblies.

Regards!

[Joe-Bouza]

Check the surface definition for any unintended transforms

[JD.Borgeson]

I don't seem to be allowed to attach a .pkt file on here. here is a screen shot of the subassembly.  I am noticing that the right side on the drive works totally as it is supposed to.  it is just the left side where the surface goes beyond the boundary.  and I have the boundary set as the edge of the corridor. which makes no sense because the left is just a mirror of the right.

[JD.Borgeson]

Thanks for the suggestion.  do you have a moment to elaborate?  I am new to all of this.

[JD.Borgeson · Accepted solution]

All, I figured out the issue!  or at least a work around.  I believe it had to do with my boundary for the corridor surface.  It was set the the boundary of the corridor, but I chose the interactive boundary option and traced the appropriate feature lines.  problem is solved.  Thanks for your responses!

[Joe-Bouza]

Sure. Your description of the surface not lining up with the corridor reminded of an issue of one of our users 

the possible transform I mention is c3d speak for something moved. Also,?seen as geometry drop.

Our user inadvertently moved the corridor surface a tiny bit and no edit/ rebuild seemed to effect the tin.

in the surface properties you can trace the edits/ definition, and the geometry drop list as a transform . Once removed from the definition the corridor and surface were back in sync