I am in the process of making my desc keys/styles/layers etc. I have it all pretty much stamped out, accept i cant for the life of me get civil to dump points WITHOUT a known desc. key into a specific layer, as of now my setup dumps points WITOUT known desc. keys into the Current Layer and not the one i select in the "_AllPoints" group's assigned style.
Solved! Go to Solution.
Create a separate key file with one key in it using the code ~?. Put this key file at the bottom of the list when importing data. Any point not matched by your normal list will be caught by this one. I use this key to prepend "NO MATCH" to the full description. I then have a pre-created point group that includes "NO MATCH*". This will place all of the unmatched points in one group for further processing.
You could also set your default point setting to put them into a particular layer and then isolate it and add it manually to a group.
Alright, that worked! So now I have one more problem, when I import points from a point file, when I import its almost all working right, all accept the "Begin" or "b" points the surveyors use, come in on the current layer and not the correct one as defined in the Desc. Key file....
See attached image, everything comes in correct accept the "b" and "e" stuff for the lines
Since the introduction of line work code sets, you can put linework codes after the description. If your field crews are used to the autodesk style of coding they will be happy for the switch, since with this change they can have multiple line codes in a single shot.
B EDGEPAV would be EDGEPAV B.
In the short term, you can convert the file to a field book and import through the survey database. This will strip out the linework codes.
Thanks, Its gonna be hard trying to get these guys to break that habbit they have used for almost 20 years. Decisions like that is the reason everyone is so irate and pissed about the civil switch.
They don't have to switch. You can still import field books with the old coding style via the survey database.
Most of the crews we work with would rather have the new style since it allows for less shots in the field.
What is the procidure to convert a .txt (PNEZD) to a .fbk? I understand how to do the oppisite inside civil after the import (with the network) but am confused about how exactly to convert it before the import so that the "b" and "e" stuff gets tossed and it works right.
Use Survey Data Collection Link to convert an ascii coordinate file to an autodesk field book with linework. It is located in the home tab of the ribbon under "Create Ground Data". There are other tools such as Stringer Connect if you don't like Survey Link.
You can then import the field book into a survey database using either the import survey data wizard or import the fieldbook directly into a network.
Thanks a ton for your help! So now ive hit another snag, I get them imported, and it appears that my 'no match' desc. key file is being picked up first and its throwing all the points on the MISC layer. Earlyer you said that I should put my "no match" desc. key file "at the bottom of the list" when importing, im sure this is whats causing this, I just dont know how to switch the order in which civil uses the desc. key files....
In the Settings tab under points, right click on Description Key Sets and choose Properties. A Description Key Set Search Order dialog box will appear. Make sure that the "No Match" key set is at the bottom of the list and click OK. You can then select all of your points, right click and re-apply the description keys.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.