Geopak cross section error: [There are no Cross Section Cell to process...]

I recently made a minor tweak to an alignment design.  At this point I re-ran pattern lines and was going to re-run the existing ground cross sections when I received the following error message:  "There are no Cross Section Cell to process with regards to current settings" while using the Draw Cross Sections from Surfaces tool.  

My cross section file does populate with the correct pattern line locations and coordinates/elevations but no existing ground line will run.  This confirms that it is pulling accurate (but incomplete) info from both the pattern line DGN as well as from the TIN.

I have checked and double checked that the correct information is filled out in the tool box (dgn with pattern lines, pattern line info, TIN, etc) and everything is as it should be.  

I have made no changes to my MS or Geopak versions in the last year+ and I had just successfully run existing ground cross sections last week with the previous version of the alignment (with all of the same file names and input information). 

As a test after I started having this issue, I was able to successfully run existing ground cross sections on a different segment of the project that had a different TIN model so the program(s) themselves are working fine...  

At this point I'm drawing a blank as to what the issue is and any help would be much appreciated.

MS version (SS2 V8i):           08.11.07.443

Geopak version (SS2 V8i):  08.11.07.427

Parents Reply
  • Thanks for the quick response Nico - I was able to successfully run ex. ground x-sections by station when I tried it by that method.

    As I really prefer using pattern lines due to their more easily verifiable location, I kept looking for a solution and I was eventually able to get it working correctly using pattern lines.

    My solution was to re-run my alignment in COGO, then I re-ran pattern lines and it worked as intended so something must have been corrupt in my alignment (stationing stayed exactly the same and I didn't change the method I stored the chain so I'm not sure what might have gone wrong)

    Answer Verified By: Nico Roman 

Children
No Data