Survey Chains

In SS2 we were able to offset a survey chain horizontally and vertically how would I do this now in SS4 looks like that command does not exist any more

Thanks

Parents
  • We are using SS4 GEOPAK so I guess it would be something close to the new Open Roads tools - we can still use the old legacy tools just trying to migrate to the new tools

    Dan

    PowerGEOPAK SS10 and ORD

  • In the new Linking Codes, there is a TMPL code. However, the code requires a master linear features, and at least one shot of each offset feature. It does not support a code of a horizontal and vertical offset.
    So the crew needs to shoot one figure of the TMPL just as though they were just shooting a figure. Then following the master figure starting shot, they have to shoot a shot for each parallel figure, using the code and a Start code. Then, for every additional shot of the master figure, offset/parallel figures are drawn, until a new figure is started with the same code as the master figure.
    This is virtually identical to InRoads Survey's TMPL code. But the extended help page that was in prior version of InRoads is missing from the InRoads Ss4 versions help document, or I would have pasted in an example.
    In a pinch, you might be able to fake an offset shot using a duplicated master shot, combining it with a UpDown, LeftRight and FrontBack code. The offset will be treated as a 90 degree offset from the master figure, so if you have to use the faked offset shot, ues whatever offset codes needed to get the point as close to the correct offset as possible.

    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • you could do this (TEMPLATE ALONG A PATH) with standard Microstation "Extrude profile along a path". You will find it in the 3d forms toolboxes, (not sure right out my head without microstation in front)

    Regards

    Frank

    since 1985: GIS, CAD, Engineering (Civil)  Senior Consultant : [Autodesk Civil 3D , Esri ArcGIS, VertiGIS: in previous days : Bentley MS V4 - V8i, GeoGraphics, Bentley Map V8i, InRoads,  HHK Geograf, IBr DAVID] :  Dev: [C, C++, .NET, Java, SQL, FORTRAN, UML]
    [direct quote by: http://en.wikipedia.org/wiki/Helmut_Schmidt]: "Wer Kritik übel nimmt, hat etwas zu verbergen"
    Wer Grammatik- und/oder Rechtschreibfehler findet, der darf sie behalten :-)

  • This isn't easy in SS4. A word of warning about the TMPL coding. I was using it extensively. I stopped when I noticed it was not consistently being applied. Sometimes it would work and other times it would glitch and not draw the additional breakline. In other words it seemed semi-permanent at best. Results may vary.....I'm very interested on what workflow you settle on.
  • The way Civil 3D does its version of the TMPL code is different, requiring a master figure and offset values for the parallel figures. The plus side to this is that the offsets or horizontal and vertical measurements, not extra shots. The down side is that they are drawn using the same survey figure settings as the master figure.
    We found we can use the ST, PC, PT, NT, CL RECT, DIST, EXTARC, JPT and SPC codes of traditional InRoads Survey with Civil 3D by setting up a custom linework code set.
    But Open Roads Survey is screwing this up. They have made a number of codes either obsolete or added a new code that replaces two codes used together.
    We always processed our surveys in InRoads Survey and use an XML Report to export our ASCII point file with a custom XML Report that even setup the $1, $2, $3 codes as needed from the various attributes.
    The new Open Roads Survey does not support any kind of export that is even remotely useful. In general, if our crews kept to the above list, we could export the codes as used as part of the D of our PNEZD file. The new field book does not retain the original point descriptions. It does retain a cryptic reformatted list which will require some fancy XSL coding to reconstruct into the original codes.
    So if and when we loose the ability to use InRoads Survey, we will probably have to look at using Civil 3D directly with our raw files.
    This could mean having to teach crews two methods of collecting survey data. This is not progress. There should be no reason that our crews need to know which program is being used to process their survey. We currently use one set of codes for all clients and have the office side worry about which settings and software are to be used. Having an entirely new coding paradigm for Open Roads that is unlike any other just complicated things too much, IMHO.

    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • I too feel the pain that Chuck feels. In my opinion, OpenRoads has complicated the survey post-processing effort. Granted, I've been using InRoads Survey since its initial FieldWorks release, but the changes brought about in the latest evolution have made things complex in so many ways. Survey collection needs to be a quick simple coding process, and having the field crews have to relearn, adjust, and re-think their coding is always a challenge. I'll be sticking with InRoads Survey for as long as I can until I figure out how to simplify the post-processing workflow and coding for the next-gen software. I just have my fingers crossed that when the Survey side of ORD CONNECT is released that it can easily inhale and digest legacy InRoads Survey coding practices.
     
    Civilly yours,
    The Zen Dude (also known as "Mark")
    Civil Software Guru & Philosopher
    InRoads User since its birth in the 80's
    OpenRoads Documentation / Training / Support
    Zen Engineering, Owner
  • caddcop:

    I'm not an active Inroads user. I use OpenRoads with Geopak. I use the linking codes all the time between C3D and Geopak. In fact being able to adopt our land development side workflow and coding system into OpenRoads has allowed us to double our manpower for Transportation projects. There a few wrinkles like the offset survey chain workflow. I just plow through it. Microstation still pounds ACAD / C3D working in 3d survey environment.

    Is this what the link codes dialog box looks like in Inroads? This is very flexible. Same basic dialog for feature code alias as well.

Reply
  • caddcop:

    I'm not an active Inroads user. I use OpenRoads with Geopak. I use the linking codes all the time between C3D and Geopak. In fact being able to adopt our land development side workflow and coding system into OpenRoads has allowed us to double our manpower for Transportation projects. There a few wrinkles like the offset survey chain workflow. I just plow through it. Microstation still pounds ACAD / C3D working in 3d survey environment.

    Is this what the link codes dialog box looks like in Inroads? This is very flexible. Same basic dialog for feature code alias as well.

Children
  • I have to replay later when I am where I have Access to a full InRoads Suite Ss2 & its help file. Once I can I will edit this response to contain more information.

    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • Thanks Guys for all the info

    We are looking into the TMPL angle and trying to create some dummy input we can test against
    I was wondering can we predefine a survey template? SO if I know I am shooting B6 curb and can start my line and use the b6 template

    Dan

    PowerGEOPAK SS10 and ORD

  • Dan

    This is a sample of linking code commands available through ascii import.Point-Coding.zip

  • Is there a help file that explains all of the new linking codes, with examples. Like used to be in the Survey help of InRoads. There used to be two versions - one brief and one more detailed. Actually, there may have been even more, as a few new codes were added sometime after V8.0. The help file in Open Roads w/InRoads does not contain all of the pages that were in the earlier help files.

    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • I have this pdf file. Its been very helpful. Not sure how much applies to Inroads vs. Geopak. Take a look hope it helps.