The latest issue I am having with OpenRoads stems from the way it is importing alignment information from a gpk. I am trying to import an alignment that has a "shift" which is a traditional geopak cogo command which acts like a station equation, but intentionally does not recognize the distance between as stationed distance. Here is a snippet of the alignment as described in my original gpk:
Curve Data *----------* Curve 1150 P.I. Station 728+29.72 N 161,641.3780 E 529,420.0954 Delta = 1° 36' 26.67" (LT) Degree = 0° 30' 09.53" Tangent = 159.9050 Length = 319.7891 Radius = 11,398.8330 External = 1.1215 Long Chord = 319.7786 Mid. Ord. = 1.1214 P.C. Station 726+69.81 N 161,481.4793 E 529,418.6631 P.T. Station 729+89.60 N 161,801.2539 E 529,417.0419 C.C. N 161,583.5827 E 518,020.2874 Back = N 0° 30' 47.61" E Ahead = N 1° 05' 39.05" W Chord Bear = N 0° 17' 25.72" W Point 1155 N 161,801.2539 E 529,417.0419 Sta 729+89.60 ----- Shift: 24.0000 (LT) at station 729+89.60 Point 1160 N 161,800.7956 E 529,393.0462 Sta 729+89.60 Curve Data *----------* Curve 1165 P.I. Station 731+10.54 N 161,921.7089 E 529,390.7369 Delta = 1° 13' 05.78" (LT) Degree = 0° 30' 13.34" Tangent = 120.9353 Length = 241.8616 Radius = 11,374.8330 External = 0.6429 Long Chord = 241.8570 Mid. Ord. = 0.6428 P.C. Station 729+89.60 N 161,800.7956 E 529,393.0462 P.T. Station 732+31.46 N 162,042.5457 E 529,385.8573 C.C. N 161,583.5827 E 518,020.2874 Back = N 1° 05' 39.05" W Ahead = N 2° 18' 44.84" W Chord Bear = N 1° 42' 11.95" W Course from PT 1165 to PC 1170 N 2° 18' 44.84" W Dist 784.5136
Here is a snippet of what is described after the "import geometry" tool is used in OpenRoads:
Curve Data *----------* Curve 35WSB_24 P.I. Station 728+29.72 N 161,641.3780 E 529,420.0954 Delta = 1° 36' 26.67" (LT) Degree = 0° 30' 09.53" Tangent = 159.9050 Length = 319.7891 Radius = 11,398.8330 External = 1.1215 Long Chord = 319.7786 Mid. Ord. = 1.1214 P.C. Station 726+69.81 N 161,481.4793 E 529,418.6631 P.T. Station 729+89.60 N 161,801.2539 E 529,417.0419 C.C. N 161,583.5827 E 518,020.2874 Back = N 0° 30' 47.61" E Ahead = N 1° 05' 39.05" W Chord Bear = N 0° 17' 25.72" W Course from PT 35WSB_24 to PC 35WSB_27 S 88° 54' 20.95" W Dist 24.0000 Curve Data *----------* Curve 35WSB_27 P.I. Station 731+34.54 N 161,921.7089 E 529,390.7369 Delta = 1° 13' 05.78" (LT) Degree = 0° 30' 13.34" Tangent = 120.9353 Length = 241.8616 Radius = 11,374.8330 External = 0.6429 Long Chord = 241.8570 Mid. Ord. = 0.6428 P.C. Station 730+13.60 N 161,800.7956 E 529,393.0462 P.T. Station 732+55.46 N 162,042.5457 E 529,385.8573 C.C. N 161,583.5827 E 518,020.2874 Back = N 1° 05' 39.05" W Ahead = N 2° 18' 44.84" W Chord Bear = N 1° 42' 11.95" W Course from PT 35WSB_27 to PC 35WSB_30 N 2° 18' 44.84" W Dist 784.5136
Notice how the second chain description snippet is not the same as the first set of information. How is it that the import geometry tool in OpenRoads cannot make sense of supposedly supported legacy format alignment information? Was this not tested by Bentley prior to release? This is the latest of many very disappointing and in my opinion, completely unreasonable errors/omissions/bugs to be present in a software that is classified as a stable fully functional release. I have beta tested software that is more functional and stable than this piece of software.
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Beebe,
Here is a copy of my dgn and gpk. The name of the alignment that I was unsuccessful in importing is named 35WSB. I wasn't sure what you meant by dataset, so if you need additional information please let me know. Is there any workaround that has been developed to mitigate the import defect? I am working on a project where I am referencing data from our client and it is subject to change occasionally. I need a way of being able to accurately import geometry from a gpk.
jobd27.gpkALIGN_PRO.dgn