Civil3d 2018 lineworks with Leica captivate

[Anonymous]

Hi

I'm trying to setup Captivate and Civil3d to work together with lineworks.

The problem i seem to have is that Leica runs a Start -  Continue system and Civil3d is a Start - Continue - Stop system.

This is what my endings look like:

1003 BE
1003 FO
1002 BE
1002 FO
6000 --
6000 --
1002 BE
1002 FO
1002 --
1003 --

1002 is the code and BE/FO the linework.

The -- means theres no linework and it should not be part of any lines

What happens is that the 1002 BE will connect with the 1002 FO as intended, but then it'll continue down connecting all the 1002 -- aswell.

Now since i'm running Captivate, i use the build in Lineworks, wich only has a Begin and a Continue, choosen via GUI.
I imagine the problem is that i have no End, but that does not seem to be an option for Captivate and i'm guessing there's a way around it.

I've disabled the Automatically begin linework on prefix match option, but that did not fix the issue.
Basically i'd like Civil3d to only process linework if there's a linework code
Any help would be much appreciated!

Kind regards Mikkel

[rl_jackson · Accepted solution]

Now as far as you linework goes. Since you have a FIGURE established for 1002, it's going to connect to all 1002's unless you specifically BEGIN or END the code. You'll need to code it so that 10021 were the at the end will be the "line number" so if your code for 1002 was EP then 10021 would be the left edge and 10022 would be the right edge, just as I use EP1 and EP2 in my description and EP is my figure prefix, in your case you have a 4 digit prefix (1002).

[Anonymous]

With Captivate, 2 lines getting mixed up should not be possible as per what you describe.

Say i were to survey a road and i just need the 2 edges, measuring both sides as 1002. While measuring i will be switching the line number on the controller and it'll draw the line for me. When exported the controller will sort the point list so that all parts of the same line will be beneath each other in descending order.

Following example:

Measured order

Roadline1  x y z 1002 B

Roadline2 x y z 1002 B

Roadline1 x y z 1002 C

Roadline2 x y z 1002 C

Roadline1 x y z 1002 C

Roadline2 x y z 1002 C

Now when exported it'll be sorted to this:

Roadline1  x y z 1002 B

Roadline1 x y z 1002 C

Roadline1 x y z 1002 C

Roadline2 x y z 1002 B

Roadline2 x y z 1002 C

Roadline2 x y z 1002 C

That is done by the controller on export and eliminates the need for a End.

My problem comes when i'm measuring a single point inbetween my lines.

Measured

Roadline1  x y z 1002 B

Roadline2 x y z 1002 B

Roadmid x y z 1002 --

Roadline1 x y z 1002 C

Roadline2 x y z 1002 C

Exported

Roadline1  x y z 1002 B

Roadline1 x y z 1002 C

Roadline2 x y z 1002 B

Roadline2 x y z 1002 C

Roadmid x y z 1002 --

In this case roadmid becomes part of the roadline2.

In my case i'm measuring pipe connections and when i find a pipe i don't know the connection for, i want it as a single point.

What i get from your solution is that i could measure my points like this to avoid the problem then?

Adding a 0 to the prefix would tell it that it's a sepperate "line" and with the automatic begin off that would stay a point.

Roadline1  x y z 1002 B

Roadline2 x y z 1002 B

Roadmid x y z 10020 --

Roadline1 x y z 1002 C

Roadline2 x y z 1002 C

Mikkel

[Anonymous]

I'm not totally sure I follow what you're coding, but C3D linework depends on distinct codes. All 1002 codes will be treated as part of the same figure unless you use a Stop/End code in between figures. I do like @rl_jackson does and make each code distinct from a similar line by appending 1, 2, 3 etc. to the code. So I can carry 4 edges of sidewalk, two backs of curb, two flow lines of curb, flange lines, a CL, a couple phone lines, gas lines, all at once - it doesn't matter how many different lines there are as long as I can keep it straight in my head (Helps being schizo). A typical street cross section, not counting any utilities or other lines, might be SW1 SW2 BC1 FL1 FLG1 CL FLG2, FL2 BC2 SW3 SW4, then move up 50 feet and do it in reverse.

Note that if I have BC1 shots along the way - say for where the curb head is dropped for a wheelchair ramp, I just keep using BC1 and it connects the dots. If I am shooting buried water main paint marks and encounter a tee, same deal - I shoot it with the same code, it becomes another vertices in the figure. As it should be - it is in the water line. If I want to detour and pick up the tee'd line, I would shoot it as a BW1 BW2 ST - BW1 continues and uses the shot, BW2 is started and I can continue BW2 whenever I want.

I am totally unfamiliar with Captivate, but if you can export the data in order needed to have them plot correctly (by figure) you may be able to successfully use both systems, but you would probably have to edit the text point file to add the appropriate stop codes before importing to C3D.

[Anonymous]

and if you didn't want the tee to be part of BW1, you'd code it something different: BW, BWT, BW TEE - anything that is not BW1 (or BW2 or whatever) figure.

[rl_jackson]

Unfortunately Leica took it upon themselves to completely change how coding was accomplished in a Data Collector with the introduction of Viva, about 5-7 years ago. I could not get it to work with C3D then, even with attempts at contacting a Leica Rep., I was still unable to get things working. The company I worked for at the time decided to sell there 6 Leica GPS RTK systems and go with Trimble as they like Carlson use similar coding methods. I see that they haven't made any improvements on working with C3D, but have no problems working with 12D Design Software. I would suggest contacting your local rep to see if they can be of assistance (good luck there).

Note: On the Leica website, they have in the past create plugins for C3D, maybe they have done that again.