[OR Ss4] Survey Coding TMPL - Gone Rogue

I'm working with a TDS RW5 file, originally coded for InRoads Survey. It is a sample file used for training. It uses a number of TMPL codes, most of which work as expected. But this one that was a top of curb, bottom of curb and gutter edge was doing something unexpected. The master figure is create with a code of BC ST PC TMPL and the two parallel figures are started with TC ST PC and EPR ST PC.

So what is the problem? THis is what it looks like on screen with all three figures selected. Notice the locations of the two offset figures compared to their Manipulators locations. And, if I change the code on the master figure to an ST, they suddenly draw correctly but are no longer curved figures. Adding a ArcSingle to the middle point to try an reintroduce the curved figure results in the figure resetting it back to the bogus offsets. And changing the ST PC to an ST on either parallel figure starting point completely removes the figure from the file, renumbering similar figures in the process.

So far, the other TMPL codes in the file seem OK. 

  

Apparently, I spoke too soon. I've found a few others where no parallel figures are created and no amount of edits seems to change anything. If I had to make a recommendation, I'd probably recommend not using the TMPL code.

Parents
  • Hello Chuck. Once again I found this code to be very unpredictable. I thought I posted a thread on the TMPL code issues. It's another NO GO code. I will say, I think your at the end of the list of failed linking codes, as far as I remember. Try a survey redraw to regenerate the linework from linking codes. Also verify your project explorer setting below:

    If you have linear feature linking set to by linking code you'll have never ending trouble. Set it to Force Point List Features in your seed file so its permanent.

    Thanks for posting, others will appreciate knowing I'm sure.

    We are dipping our toes into ORD survey workflows. Not sure if any of these issues are persistent. I'll post my findings.

    Cliff

  • Update on TMPL usage: There is a finite distance that the parallel figure shots must be within the starting point of the master figure. In my example, I had to nudge my offset points forward along the figure by between 0.04 and 0.08 feet to get the lines to draw correctly. I ended up adding a FrontBack value or -0.1 as my first test, which brought the figures back to their expected location. By trial and error, I was able to reduce this value slightly and still have it work.

    I came up with this while experimenting with Copy Parallel. I noticed the command did not like me trying to snap to the originating points, but when I moved the cursor forward along the master figure, the lines seemed to behave normally. I tried a LeftRight code first but the direction of movement  was not promising, so I switched to FrontBack with good results. In a pinch, you could probably use both, or actually modify the angle and/or distance.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Reply
  • Update on TMPL usage: There is a finite distance that the parallel figure shots must be within the starting point of the master figure. In my example, I had to nudge my offset points forward along the figure by between 0.04 and 0.08 feet to get the lines to draw correctly. I ended up adding a FrontBack value or -0.1 as my first test, which brought the figures back to their expected location. By trial and error, I was able to reduce this value slightly and still have it work.

    I came up with this while experimenting with Copy Parallel. I noticed the command did not like me trying to snap to the originating points, but when I moved the cursor forward along the master figure, the lines seemed to behave normally. I tried a LeftRight code first but the direction of movement  was not promising, so I switched to FrontBack with good results. In a pinch, you could probably use both, or actually modify the angle and/or distance.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Children
No Data