Survey stake out points.

[Anonymous]

I'm new at Civil3d with a background of Microstation and Geopak.

When I bring in the fbk file of a stakeout, we create a new point to set the hub/pin/whatever and use the stakeout point as the description.  When importing the fbk the points description isn't the stakeout point but building corner.  Why it defaults to this code I have no idea?  And I cannot find anywhere to edit the "survey database" to find out why.  In Geopak you have a survey managers database that you create the codes in and can edit all there attributes there.  Not finding anything like this in Civil3d.

Thanks for any and all help.

[jmartt]

I don't know why it would default to building corner. But you can change the Description Keys in settings like in the above screenshot.

[Anonymous]

Thanks for the reply.  And I can change the description there.  But I'm interested in the root of the problem being point (10100), description (10063) is coming in as a building corner.  Rather I thought since there is no code (which I can't find a list of or how they were created) Civil3d would just use it's description as a shot and throw it on layer 0 or something of a default point layer.

Again I due appreciate the help, brick wall after brick wall.

[jmartt]

I haven't used field book files at all. But I wonder if you're importing your survey data in the right format? I have a bit of a panic attack everytime I forget to click on the PNEZD format when I bring the shots in.

What is your description key code for building corner? Is there any field in your data with that code, somehow? Like maybe it's a brass cap and the key set is reading "BC" as Building Corner? Is Building Corner the first description key you have? If you make one above it and re-import, does the new first one become the default? This could maybe give you some clue as to what is happening.

If you can post your drawing, I'm sure that would help.

I'm gonna hafta defer to people better suited to answer. I'm shooting in the dark with field book files. Don't despair. You'll get it to work.

[Anonymous]

I've found the problem.  I didn't realize that description key sets are in the actual template file.  There were some legacy field codes that used 1006* as a code. So using my point number of a description (10063) caused a hiccup.  I deleted these key sets out of the file and re-imported and all is well.  And I changed the template as well.

Thanks for the help and steering me in the right direction.  Still getting the feel of the differences of Geopak survey and Civil3d.