Just a small "glitch" in the programming if you happen upon a perfect close traverse and try to store it using the traverse commands (i.e. Compass rule). You get an error stating that the desired accuracy is not achieved where in actual case it's infinitely better! See the below from the Coordinate Geometry screen;
<* 7 Store Point 10002 10000 50000 X 10,000.000 Y 50,000.000 Point 10002 stored. <* 8 TRAV 1001 <* 9 COMP <* 10 CLO 4000 10 <* 11 BACK REF 360 <* 12 LIN 10002 TO 10003 100 90 <* 13 LIN 10003 TO 10004 100 90 <* 14 LIN 10004 TO 10005 100 90 <* 15 LIN 10005 TO 10002 100 90 <* 16 END TRAV - - - - - - - - - - - - - - - - - - - - - - COMPASS ADJUSTMENT - - - - - - - - - - - - - - - - - - - - - - Closure information: Total error 0.000 Error in X 0.000 in Y 0.000 Closure accuracy: 1.#IO Total Perim 400.000 Fix Perim 0.000 Perim 400.000 Closing link 0° 00' 00" Warning : Accuracy not achieved. Traverse points will not be stored. - - - - - - - - - - - - - - - - - - - - - - - - - - - - FIELD COORDS INFORMATION - - - - - - - - - - - - - - - - - - - - - - - - - - - - Point X Y 10002 10,000.000 50,000.000 10003 10,100.000 50,000.000 10004 10,100.000 50,100.000 10005 10,000.000 50,100.000 10002 10,000.000 50,000.000 COURSE FIELD FIELD FIELD FROM TO DISTANCE BEARING ANGLE 10002 10003 100.000 90° 00' 00" 90° 00' 00" 10003 10004 100.000 0° 00' 00" 90° 00' 00" 10004 10005 100.000 270° 00' 00" 90° 00' 00" 10005 10002 100.000 180° 00' 00" 90° 00' 00"
Chris
Our certification team has tested and verified that this is a bug. A defect has been placed into the pipeline for fix. Defects are always weighed and prioritized so a definitie fix date cannot be stated with any certainty at this time.
Robert GarrettSenior Product EngineerBentley Systems Inc.