Announcements

Starting in December, we will archive content from the community that is 10 years and older. This FAQ provides more information.

Datum Surface Extending Beyond Daylight Point in Sections throughout corridor

Anonymous

Datum Surface Extending Beyond Daylight Point in Sections throughout corridor

Anonymous
Not applicable

Hi.  I'm trying to meet existing ground.  I am using the DaylightInsideROW subassembly but I've tried others as well.  Along the corridor in certain sections the surface I've created using the datum of my subassembly will extend beyond where it meets existing grounds,  this happens on either one or both sides throughout.  Sometimes it will meet EG and then stop like I want it to.  I've set the Corridor Extents as the Outer Boundary. I've searched and searched the forum but I could not find someone with the same problem.

 

I have a single corridor and a single assembly.  The assembly is pretty basic with 2 basic lanes, shoulders and the DaylightInsideROW subassemblies.  I've attached a picture.

 

 I've attached a couple of pictures of the issue occuring in one of the problematic sections.  As you can see in the first picture the right side of the datum surface is meeting daylight and stopping, while the left side meets daylight and then continues on in a weird geometry before stopping at a random point.  In the second picture the same thing is happening but on the other side.

 

Ultimately I'm trying to calculate the cut and fill volumes throughout the corridor.  

 

Can any body help?  

0 Likes
Reply
Accepted solutions (1)
3,505 Views
6 Replies
Replies (6)

sboon
Mentor
Mentor

When you rebuild the corridor are there any warning messages?  Generally you should be getting something about surface boundary not added because it crossed itself somewhere.

 

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

Steve
Expert Elite Alumnus
0 Likes

Anonymous
Not applicable

I'm getting 3 errors of this type:


   Error Thursday, September 29, 2016 1:51:47 PM Roadway yemmaj 318+27.80': Intersection with target could not be computed

 


And a single warning at the end:


   Warning Thursday, September 29, 2016 1:52:16 PM Roadway yemmaj Mask '0' NOT added to corridor surface 'Path Datum' as boundary due to crossing polygon

0 Likes

sboon
Mentor
Mentor

The first two might be an issue, but the third message is definitely a problem.  You likely have corridor sections that cross each other somehow.  The warning message should allow you to zoom to the location of the problem, so that you can fix the corridor.

 

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

Steve
Expert Elite Alumnus
0 Likes

Anonymous
Not applicable
Accepted solution

Corridor surface triangulation is incorrect. To solve this issue edit corridor surface manually or under Surface Properties decrease maximum triangle length.

hmoobvue
Advocate
Advocate

How and what do you do to the surface to resolve the issue?

0 Likes

Abdissa34
Explorer
Explorer

I recently encountered the same problem and found a solution. Of the many things that could cause this is the Frequency value in the corridor properties window under the parameters tab. The issue would be resolved if you set the frequency increment values (for horizontal, vertical and along curves) equal to the sample lines increment values (sampling spacing). Then rebuild the corridor under consideration and regenerate all by using regenall command. I hope this helps you and other users with similar problem. Finally, please ACCEPT AS SOLUTION if this works for you.

0 Likes