Field-to-Finish type Linework/Coding and Smartworx

[bmeyers]

Bob,

With the release of Civil 3D 2010, and later versions as well, you now have the ability to edit the “Figure Commands.” The Figure Commands are the codes that you use to control the linework. Now, we just add a “B” after the descriptor if we want to begin a line. e.g. TBC B. If you want to do it this way you have to edit the Linework code Set. If you give me your email I’ll send you a helpful pdf from Autodesk University. Let me know if I’m totally off base here or not.

[aksuperchamp]

BM- Thanks for the reply, you’re not really off base.

My issue isn’t really with the Figure Commands of Civil3d, but more with how Smartworx/Leica deals with coding. I know I can shoot that “TBC B” point and it will start a TBC line, however my issue is that I want the line to continue through my next shot which might be coded “CI/TBC” (Curb Inlet @ Top Back Curb), and so on… The way they have things setup the line stops when it sees the code change from TBC to anything else.

So everything works great as long as you only draw lines through identical codes, which works great for running EP/SHLD/TOP/TOE/etc… The main feature that throws a wrench in the works is utility lines running through poles/pedestals/jbox’s/meters/etc… I just want to be able to shoot the different items, and have the linework continue.

One other item that I didn’t hit on in my original post is that I absolutely despise line ID’s! (EP01, EP02, etc) We don’t do “cross-section” or “zig-zag” type data collection, so we don’t have the need to run multiple lines concurrently, so I don’t want to have to keep track of which line ID is currently running.

Thanks!

Bob K.
Anchorage, AK

[bmeyers]

I am not familiar with Smartworx. Maybe adding a “C” for continue at the end of the code would do it. I hated keeping track of the line ID! I always just added a Beg code if I couldn’t remember the last ID…which was often. For example, several ditches that are separated by driveways. A nice sketch can go a long way too!

[cptdent]

You should be able to use multiple descriptors to do your line work and symbology. Such as “OHE +7″,”OHE PP1TR” “OHE -7”.

[MoeShetty]

“””>
> I want to be able to start a line, for example an Overhead Electric line, and then take shots on a Power Pole, a Power Pole with transformer, maybe a shot on the line itself, and then end the line on another Power Pole shot, all the while having the software drawing an Overhead Electric line through the points.
>
> Currently Smartworx will end the line you started as soon as you change the point code.
> “””
sounds like OHE should be a point with begin line code, and, of course, the EP is a point code. measure the EP as a point, measure the OHE next. go to your line editor and keep the OHE line open after that. manually open and close in smartworx.
or, measure the ep’s first, switch to OHE and stick wwith it until you run out of line of sight etc.

hope this helps.

[aksuperchamp]

I guess my point is that while I’m willing to change the workflow, I’m finding that I’m having to do much more work to end up with the same results as I had before… So much for new technology!

Here is an excerpt from an old .FBK file that is typical of the scenario that Im trying to resolve:

BEG OHELEC
PRISM 5.150
F1 VA 63089 358.19128 942.923 90.31557 “PPGUY”
F1 VA 63090 358.42443 941.640 90.30282 “PP”
F1 VA 63091 9.23562 928.789 90.51538 “PPTRANS”
F1 VA 63092 12.08144 640.496 91.08426 “PP”
F1 VA 63093 19.18201 359.730 91.44484 “PP”
F1 VA 63094 16.17220 352.360 91.43508 “PPGUY”
END

In this example we began the OHELEC line on a Guy Pole, drew it through a Power Pole, then a Power Pole with Transformer, then 2 more Power Poles, and ended on another Guy Pole. The only extra steps involved in the whole process to get the linework drawn was to say BEG OHELEC and END.

Now with the “New & Improved” software, to get the same result I have to generate something like this:

F1 VA “8” 23.30078 6.474 60.23553 “PP/ B”
F1 VA “9” 27.46176 6.470 60.23542 “PP/ PP/TR”
F1 VA “10” 31.20282 6.466 60.23533 “PP/ PP/TR/LU”
F1 VA “11” 40.06555 6.453 60.23496 “PP/ ELEC/ETB”
F1 VA “12” 49.23488 6.448 60.23442 “PP/ E”

So now instead of a simple BEG and END line, I have to either generate a Codelist that contains all possible combinations of Line/Point Codes so that I can select them from a list, or the crews have to remember the formatting required so that they can hand-enter the entire code string for each shot.

Granted, both of these methods generate the correct result in Civil3D, but I find that the first method is FAR more productive and efficient.

[MoeShetty]

> I guess my point is that while I’m willing to change the workflow, I’m finding that I’m having to do much more work to end up with the same results as I had before… So much for new technology!
>
> Here is an excerpt from an old .FBK file that is typical of the scenario that Im trying to resolve:
>
> BEG OHELEC
> PRISM 5.150
> F1 VA 63089 358.19128 942.923 90.31557 “PPGUY”
> F1 VA 63090 358.42443 941.640 90.30282 “PP”
> F1 VA 63091 9.23562 928.789 90.51538 “PPTRANS”
> F1 VA 63092 12.08144 640.496 91.08426 “PP”
> F1 VA 63093 19.18201 359.730 91.44484 “PP”
> F1 VA 63094 16.17220 352.360 91.43508 “PPGUY”
> END
>
> In this example we began the OHELEC line on a Guy Pole, drew it through a Power Pole, then a Power Pole with Transformer, then 2 more Power Poles, and ended on another Guy Pole. The only extra steps involved in the whole process to get the linework drawn was to say BEG OHELEC and END.
>
> Now with the “New & Improved” software, to get the same result I have to generate something like this:
>
> F1 VA “8” 23.30078 6.474 60.23553 “PP/ B”
> F1 VA “9” 27.46176 6.470 60.23542 “PP/ PP/TR”
> F1 VA “10” 31.20282 6.466 60.23533 “PP/ PP/TR/LU”
> F1 VA “11” 40.06555 6.453 60.23496 “PP/ ELEC/ETB”
> F1 VA “12” 49.23488 6.448 60.23442 “PP/ E”
>
> So now instead of a simple BEG and END line, I have to either generate a Codelist that contains all possible combinations of Line/Point Codes so that I can select them from a list, or the crews have to remember the formatting required so that they can hand-enter the entire code string for each shot.
>
> Granted, both of these methods generate the correct result in Civil3D, but I find that the first method is FAR more productive and efficient.

ok, might want to set ‘use last attribute’ in smartworx, and put attribute choice lists into the codes that you think will need them. set your ‘working’ attribute to 1, this makes att 1 the one that controls line numbers. att’s 2 and beyond will control the other elements, such as code RCS rod and cap set; maybe has diameter, color and label. IPF iron pipe found might have condition, diameter,etc.

[aksuperchamp]

Update…

I can get Smartworx to spit out the linework coding in the Attribute fields, which is fine on most accounts. Also, I can add Code Information to a shot that also gets appended to the Description in the .FBK file, which actually seems like an easier solution, since that way I can add in point numbers for other points I want to draw in/out of.

Now I’m faced with Civil3D not wanting to continue figures through points with the linework function as part of the point description. Essentially Civil3D is doing the same thing that Smartworx was doing… C3D will draw figures through any code when commanded like we used to do it with TDS Notes, but when the linework is a part of the description, it stops the line when the description changes.

For example: In this instance, I get a line drawn from 24 to 26, bypassing 25.

F1 VA 24 277.59599 12.000 90.00006 “CBL BEG”
F1 VA 25 280.00000 10.000 90.00003 “CL”
F1 VA 26 281.59599 10.113 90.00006 “CBL END”

Any other thoughts?

Thanks again for the help!

Bob K.
Anchorage, AK

[MoeShetty]

i will pass the thread on to our c3d draftsman. he can shine a little on it as well. look for me tomorrow, and send me your email.

[aksuperchamp]

Next update…

So far, not great…

In a last ditch effort, I’ve turned to Leica Format Manager to try and come up with a custom .frt file that will export a .FBK like I want it. My current solution for this .frt/.fbk file is to use Free Codes to control Linework Beg/End, etc independently of the points.

Ive gotten the basic topo survey functions to work, now the trick is getting the Traverse/Sets of Angles, and Offsets functioning as they should…

Thanks again for the help!

Bob K.
Anchorage, AK

[rl_jackson]

Bob,

Did you ever get a handle on this, I have suddenly been thrust into the world of Lieca/Smartworx from the TDS world and I’m completely lost on the sitiuation.

Any help would be great.

[aksuperchamp]

In short, not really…

Our process works, but is FAR, FAR from ideal. The .FRT file I made works “so-so” to get data off the guns and into C3D, but I still don’t have an answer for avoiding the Survey Database functionality in C3D.

Plus, about 95% of our work is RTK, so the issue hasn’t been as pressing. I see another round of head-scratching coming up sooner than later, and have a feeling that we will transition to a completely different coding structure to try and make things work better across platforms. (GPS vs. Gun)

You can email me if you have specific questions, or want a copy of the .FRT file that I came up with. Like I said, its nowhere near perfected, but it works when it has to…

Good luck!

Bob K.
Anchorage, AK

[rl_jackson]

Bob,

If you could contact me at your convience I’d appriciate any help at all.

You can email me at rl_jackson at verizon dot net