Let me add a little additional information regarding this subject, which may help you solve this problem.
First, is a simple one they call this a Figure PREFIX Database, a prefix is generally short for the initial characters (i.e. EP, EC etc.) by limiting the characters and maintaining case as prefixes are case sensitive, just as description keys are ultimately limits the room for error (upper or lower it really doesn't matter, being consistency does). This in-turn makes data collection by you or the field crew more fluent. Who wants to spell the entire word, when it can be truncated in some fashion that is understandable, gets the point across and meets the end goal of obtaining linework.
Second, Description KEYS act and do very similar things and go hand and hand with the PREFIXs. You can use them to further determine what layer your point resides on, or how that point will display the data just as the PREFIX. As a general rule I use KEYS for symbology and PREFIXs for linework, but that's not a rule that is set in stone, use it how you want to (use one or both at the same time), at the end of the day the most import thing is get the job out the door.
Finally, I'm sure you're trying to set things up to run like a well-oiled machine. Trust me in knowing this is not an over-night sensation. You don't sit down one day and make up 200 symbols with codes and the next day come in and import the data into the drawing and ta-da! it's all there. Same as you don't get 6 linetypes for different types of fences to appear on one layer based on the figure code. There is no EASY BUTTON up in here!
HTH
Rick Jackson
Survey CAD Technician VI
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
