Topic: Point File Example

[Chris]

does anyone have a point file that uses the newer linework code set for Civil 3D that they would be/are able to share.  We are transitioning from Eagle Point to Civil 3D and we're trying to figure out the best way to go.  Right now our two options are, use a custom program to completely re-write our point files to something C3D can use, or retrain our survey department to code it using the C3D format.  I'd really like to know how C3D can handle a single point, at which multiple lines come together (Back of curb, Front of Walk, edge of drive).  Are there several shots at that one point, or can C3D handle the multiple linecodes.

Thanks,

[Chris]

ok, eventually if you search and search through AutoCAD's convoluted help system, you can achieve the answers you are looking for. Point file problem almost solved.  I got multiple lines to start/end at a single point.  Now my question is, is there a way to show the leading element and comment in the point's formatted description.
I've got a shot, the code is BC C/DUBDOWN  I want the description to say BC DUBDOWN

Thanks,

[mjfarrell]

ok, eventually if you search and search through AutoCAD's convoluted help system, you can achieve the answers you are looking for. Point file problem almost solved.  I got multiple lines to start/end at a single point.  Now my question is, is there a way to show the leading element and comment in the point's formatted description.
I've got a shot, the code is BC C/DUBDOWN  I want the description to say BC DUBDOWN

Thanks,

That happens later in the point label style as configured in your description key set.  If I understand your question.

As to the first part of the question you will be better served to retrain the surveyors to take maximum advantage of the various line coding that C3D allows.

[Chris]

That is the plan, have the surveyors use c3d codes. I really don't want to maintain a conversion program. I've been looking at the descriptor keys and can't figure out how to display comments in the descriptions

[mjfarrell]

I think for the type of 'comments' you are after a custom point file ormat and user defined properties might be in order.
Perhaps send or post a sample of your output file for me to look at.
This is the type of thing I usually assist in resolving during a training session.

[Chris]

Using OOTB C3D codes:
1,5000.000,5000.000,925.00,BC C/DUBDOWN

I'd like the point description to say:
BC DUBDOWN

but if you cant display comments, I guess we'll just have to settle with BC

[mjfarrell]

Using OOTB C3D codes:
1,5000.000,5000.000,925.00,BC C/DUBDOWN

I'd like the point description to say:
BC DUBDOWN

but if you cant display comments, I guess we'll just have to settle with BC

That may be the coding...however what is the ascii output file content?

One can use up to NINE pieces of information in your description, and user defined properties to enrich what you get for point descripitons and labels.
I have effectively helped others work this into their procedures to gather additional data for urban sanitary and storm drain features.

[Chris]

thats how the guys in the field would code it BC C/DUBDOWN.  Thats how I see it in the txt file that I get to reduce.

perhaps I dont understand what you are asking for.

I suppose they could code it BC C DUBDOWN and then for the formatting I could use $0 $2 to show what I want.

[mjfarrell]

thats how the guys in the field would code it BC C/DUBDOWN.  Thats how I see it in the txt file that I get to reduce.

perhaps I dont understand what you are asking for.

I suppose they could code it BC C DUBDOWN and then for the formatting I could use $0 $2 to show what I want.

YES!

I know what BC is....Although WHAT in the worlds is DUBDOWN?

[Chris]

dubdown is the part of the curb head that is lower for sidewalk ramps/driveway openings.

[mjfarrell]

dubdown is the part of the curb head that is lower for sidewalk ramps/driveway openings.

Around these parts we call those "wings" or "ramps"...nothing is lost in translation.   

I have yet to discover what they call them here in Doha. It's anyones quess at this stage.

[sinc]

Here's a little "cheat sheet" I started putting together for our field guys.

The only difference between this and C3D's defaults is that, since the "Continue" command is pretty much unnecessary, I made "C" stand for "Close" instead of "Continue".  I believe I have "Continue" set to CONT, although I notice it's missing from the cheat sheet.  Our field guys pretty much never use "Continue", so I hadn't really paid much attention to it.  (They pretty much never use "End", either.)

Something that looks like a possible conflict in what you're doing is that "BC" is also the command for "Begin Curve".  It seems like things could get hairy if you have a "BC" figure prefix as well as a "BC" linework command code.

[Chris]

With Eagle Point we used - for point on curve. So to eliminate the issue with BC and ec, we went with b- and e- I think we've nailed down a system that'll work. I spent a while working on it today. I'll take a look at your example and see if there is anything that might work better for us.

[Dent Cermak]

Chris, here's what you need:













(Keeping my head low to dodge the flack that is sure to come!!!   )

[Chris]

sorry, I also need to be able to create plan and profile sheets.