Hey guys, I am trying to sync my TSC7 (Trimble Access 2020.02) to Civil 3D 2020. As far as linework goes. Right now I download my data txt. file and dxf. file into TBC process it. Then bring it over into Civil 3D. But I want to skip that step and bring all of my data txt. file straight into Civil 3D and it create the linework correct. Well that's where I'm running into the issues. My linework is all connected and none of my radius show up in the DWG. I have already reset my Figure Prefix Database. And 2nd question. On my Linework Code Set. Does that have to be entered into the Feature Definition Manager or do I make it the description? Or do I have to wait till I get back to the office and do it in Excel? Or do I just need to change my whole system I have going here??ÿ
?ÿ
?ÿ
?ÿ
I have already reset my Figure Prefix Database. And 2nd question. On my Linework Code Set. Does that have to be entered into the Feature Definition Manager or do I make it the description? Or do I have to wait till I get back to the office and do it in Excel? Or do I just need to change my whole system I have going here?
I'd be wary of just pushing CSVs out of the controller to C3D without QC and adjustment of raw data, but that's neither here nor there.
Since you're going to be processing everything in C3D, once you set up your linework code set and figure prefixes, all you have to do is code them appropriately in the field. Whether or not you choose to create an FXL using the Feature Definition Manager is up to you.
But you will probably want to in order to see linework in the field. In that case, just replicate the control codes and feature codes from your C3D template. It won't have any effect at all on C3D since you're processing with C3D.
C3D and TBC are remarkably similar in how they process linework. A couple of minor differences, but that's it.
There?ÿcan be a lot to setup in Civil3D if you want to get very detailed.?ÿ Looking at your point file, I saw no end or begin line control codes in there.?ÿ You show Figure Prefix Database, but no mention of the Description Key which sets up all the codes it can bring in.?ÿ Although with some tree looking things in your image, you might have done some setup in the Description Key.?ÿ
Civil3D's linework code set are the same as Control Codes in TBC/Feature Definition Manager.?ÿ It's best these control codes go after your code, e.g. EP B or EP E.?ÿ ?ÿIn Civil3D it is setup by default that you don't need to use a begin line code, but if you don't you will need to use an end line code.?ÿ If you have the same setup in a Feature Definition Manager FXL file as you do in Civil3D, you will sett your line work on the Access map allowing you to fix a code immediately instead of having to deal with a bunch of crossing lines on a possibly much later day during office work.
It also seems odd that you have codes with spaces in them, e.g. CL DRIVEWAY.?ÿ TBC and Civil3D uses the space to discern between a different code or control code.
@robertusa Thank you! That was extremely helpful. So I enter the BC, EC, B, E, ect. to the description keys. Then I put the BC, EC, B, E, ect. in my feature definition manager under my control codes. And it should start working? Also concerning the CL DRIVEWAY. I am making a new FDM in TBC and I will keep that in mind when I'm making the new one.?ÿ
The B, E, BC, EC should be in there as default in C3D??s ??sample? line work code set. They do not get put into the description key.
In my coding system back of curb is "TBC" and I have changed the Linework Code to "PC" to start a curve, and "PT" to end it. "B" & "E" begin and end lines (or, more correctly, "figures") . So the point coding of a string of points on a TBC would go like this:
?ÿ ?ÿTBC B?ÿ ?ÿ ?ÿ(beginning the line)
?ÿ ?ÿTBC
?ÿ ?ÿTBC
?ÿ ?ÿTBC PC?ÿ (beginning the curve)
?ÿ ?ÿTBC
?ÿ ?ÿTBC?ÿ ?ÿ ?ÿ (any number of points on the curve)
?ÿ ?ÿTBC
?ÿ ?ÿTBC PT?ÿ (end the curve)
?ÿ ?ÿTBC
?ÿ ?ÿTBC
?ÿ ?ÿTBC E (ending the line)
?ÿ
With the code for the gutter line being "GL" I can run the coding for TBC and GL as I go...
?ÿ ?ÿTBC B (begin the back of curb line)
?ÿ ?ÿGL B (begin the gutter line)
?ÿ ?ÿGL
?ÿ ?ÿTBC
?ÿ ?ÿTBC
?ÿ ?ÿGL
?ÿ ?ÿTBC PC (begin back of curb curve)
?ÿ ?ÿGL PC (begin gutter line curve)
?ÿ ?ÿGL
?ÿ ?ÿTBC
?ÿ ?ÿTBC
?ÿ ?ÿGL
?ÿ ?ÿGL PT (end gutter line curve)
?ÿ ?ÿTBC PT (end back of curb curve)
?ÿ ?ÿTBC
?ÿ ?ÿGL
?ÿ ?ÿGL E (end gutter line figure)
?ÿ ?ÿTBC E (end back of curb figure)
?ÿ
In truth all my field codes end with an asterisk - a wild card - TBC*, GL*, EC* (edge of concrete) ,etc. So I can run both sides of a concrete road simultaneously as such:
?ÿ ?ÿEC1 B
?ÿ ?ÿEC2 B
?ÿ ?ÿEC2
?ÿ ?ÿEC1
?ÿ ?ÿEC1
?ÿ ?ÿEC2
?ÿ ?ÿEC2 E
?ÿ ?ÿEC1 E
?ÿ?ÿ
@mark-mayer Okay, that's pretty cut and dry. I don't think my son could mess that one up. ????ÿ
I do really appreciate your help. Thank you!
@mark-mayer Okay Mark, I got it all working great! Thanks again. One more question. On the TSC7/Trimble Access 2020.02. Can you run multiple lines (SDWLK1 & 2, BC, FC, GL, CLRD) at once? I could do it with my old data collector. But this one is still brand new.
@member_of_the_patriot_fam give it a try with dummy point coordinates just sitting there in the office. ?ÿReport back here with the results.
Can you run multiple lines (SDWLK1 & 2, BC, FC, GL, CLRD) at once?
Yes you can. Suppose you have a sidewalk edge terminating at a back of curb, for example. Using the field codes in the examples above:
?ÿ TBC B
?ÿ TBC
?ÿ TBC EC B
?ÿ EC
?ÿ EC
?ÿ EC E
?ÿ TBC
?ÿ .......?ÿ
@mark-mayer Okay Mark, I got it all working great! Thanks again. One more question. On the TSC7/Trimble Access 2020.02. Can you run multiple lines (SDWLK1 & 2, BC, FC, GL, CLRD) at once? I could do it with my old data collector. But this one is still brand new.
Access has supported multiple codes for a long time, so no worries there.
I highly recommend getting familiar with Measure Codes (as opposed to Measure Points) and the CAD Toolbar.
Far faster than Measure Points for any project that needs more than a couple of codes. Using the CAD toolbar means you don't even have to remember or know the line control codes - it automatically pulls them from the designated FXL.
It can also be automated for cross-section work, so you can literally walk back and forth and push Enter at each line feature without having to advance the code or modify anything...
EC for my operation equals End Curve.
PC PT POC RCC make sense to field people
but they let the artichokes, planners, and engineers decide on the codes.
worse still: CTB is back of curb, and the pain for this mildly dyslexic person has been painful to say the least.
???
?ÿ
worse still: CTB is back of curb, and the pain for this mildly dyslexic person has been painful to say the least.
This mildly dyslexic person cringed when he saw that code.
We have offices in California; it gets confusing when I jump back and forth between local projects and Cali projects, because down there everything is based on top FACE of curb rather than top back. Makes for some odd looking linework, and difficult surfaces for sure.
