Mx v8i ss2.
Dear colleagues,
Dutch design rules usually don't request compound arcs in intersections, so this is a first for me. And an unsuccesfull one, as I get erratic results. So I tried one with minimal interference: empty model, two two-point intersecting strings with levels, compound arc using the Jason Walsh video I found here.
It still won't work:
The weird thing is between the end of the R=40 arc and the dynamic report's placemark's point, no intermediate points exist (the line is curve fitted in between).
Any ideas?
Included: Mx Output Window, a bit garbled as copy paste removes double spaces:
DESIGN TMP W147 Curve fitting invoked017 0.01 W120 System values have been modified VALUES ADOPTED : SEARCH TOLERANCE 0.0010 LEFT OFFSETS -100.0000 RIGHT OFFSETS 100.0000 SECONDARY TOLERANCE 20.0000 SECONDARY OFFSET 20.0000 CHORD TO ARC TOLERANCE 0.01000 REFERENCE ANGLE 0.00000 CURVE FITTING INVOKED STANDARD CONTENTS 7700 STATIONS STRING PSSA NO DATA CHECK ON NON-STANDARD DATA ANGLE DEFINITION: INPUT: GRAD OUTPUT: GRAD COORDINATE DEFINITION: INPUT: XY OUTPUT: XY VERTICAL OFFSETS APPLIED FLAT TRIANGLES PERMITTED NO TRIANGULATION REPORT STANDARD DESIGN RULES APPLIED.146J001J000MZZZ 20. 1. 1. 1.147 40. 15.75 60. 20.25 ADJACENT STRING DETAILS--------------------------------------------------------- NAME PNT -----X---- ------Y---- ---Z--- ----C---- --WCB-GRAD-- --RADIUS- %SLOPE J001 2 143502.980 486166.054 3.000 446.169 200.34157 INFINITY 0.000J000 1 143481.750 486188.163 1.000 510.220 98.20274 INFINITY 0.000ELEMENT SUMMARY----------------------------------------------------------------- -CHAINAGE -------X----- -------Y----- -WCB-GRAD-- --RADIUS-- --LENGTH-- START 0.000 143502.37068 486166.05755 200.34157END 93.576 143481.80642 486186.15688 98.20274CENTRE 143482.37097 486166.16485 20.000 93.576 ADJACENT STRING DETAILS--------------------------------------------------------- NAME PNT -----X---- ------Y---- ---Z--- ----C---- --WCB-GRAD-- --RADIUS- %SLOPE J001 2 143503.006 486170.952 3.000 441.272 200.34157 INFINITY 0.000MC02 68 143463.006 486171.167 1.372 67.780 16.09157 20.00 -2.578ELEMENT SUMMARY----------------------------------------------------------------- -CHAINAGE -------X----- -------Y----- -WCB-GRAD-- --RADIUS-- --LENGTH-- START 0.000 143503.00590 486170.95190 200.34157END 148.281 143429.34764 486192.77860 36.33802CENTRE 143463.00648 486171.16651 40.000 148.281 W766 String J001 has had 1 extra points generated ADJACENT STRING DETAILS--------------------------------------------------------- NAME PNT -----X---- ------Y---- ---Z--- ----C---- --WCB-GRAD-- --RADIUS- %SLOPE MC02 25 143489.160 486147.352 2.663 24.382 277.95274 20.00 -2.478J000 1 143494.255 486188.516 1.000 522.730 98.20274 INFINITY 0.000ELEMENT SUMMARY----------------------------------------------------------------- -CHAINAGE -------X----- -------Y----- -WCB-GRAD-- --RADIUS-- --LENGTH-- START 0.000 143475.58224 486184.97743 77.95274END 19.085 143494.25477 486188.51578 98.20274CENTRE 143495.94842 486128.53969 60.000 19.085 W766 String J000 has had 1 extra points generated END OF MINOR OPTION 146/147 ---------------------------------------------------- 999
It looks like you are putting in a right hand curve to connect south to west, when it should be a left hand curve.
Answer Verified By: RBo
I did. I'm used to 145 options signalling left/right hand offset/curve errors by drawing the arc in the wrong quadrant, and/or bulging inwards. That's why I used fully intersecting temporary strings, to allow for any solution. Appearantly, the 146-147 cannot show a correct wrong hand curve solution, hence the confusion. Thank you Mark for introducing me into the wonderful world of compound curves