Description Translation Library - Numeric Field coding | Back to User Tips

For clients using numeric coding (Leica and other brands too), you can type in each description individually in our Description Translation Library, or if you have a long list there is a way to import this data to the Description Translation library. All you need is a file in a clean ASCII format and follow these steps to add information to the library:

1) Start MapScenes, MapScenes Pro or MapScenes 2006, as you normally would.

2) Open any drawing and exit from the Assistant (if it comes up).

3) At the command prompt type (dumpccpd) including the brackets and then press Enter.

4) This command will create 3 files: desctran.db, prompts.db, and mscad.csv.

In MapScenes all three files will be created in the MapScenes\MSCAD directory.
In MapScenes Pro all three files will be created in the MapScenesPro\MSCAD directory.
In MapSccenes 2006 all three files will be created in the \Program Files\MicroSurvey\MapScenes2006\MSCAD directory.
DO NOT TOUCH the prompts.db, and mscad.csv files.

5) In Explorer find the DESCTRAN.DB file, use NotePad to open and edit. It will look like the following, but may have either no descriptions or others you may have manually entered already. Do not touch the header lines or the 0 line.

 

You can cut and paste in your list of numbers and descriptions, to the bottom of this file, then use NOTEPAD carefully to make a clean file with vertical columns for this to work. Below is an example of a file you may have that you wish to add to the DESCTRAN.DB file.

55 Shoulder
102 EndSglY
103 WhiteSt
104 ArroBack
105 ACWalk
106 RoofLine
107 Mailbox

Make sure the numbers line up on the left and your descriptions start at column 13 (add extra spaces as required to move the description over). Do NOT use the TAB key, make sure the characters in between the number and description are blank spaces. The numbers should not have any 0's before the actual number (088 should be changed to 88)

If you had any sample data in the file that is no longer required, then erase the example data to clean the file up. Make sure to keep the header and first line with the zero entry.

6) Save and close the DESCTRAN.DB file.

7) Switch back to MapScenes, MapScenes Pro or MapScenes 2006 and run the command: (newccpd)

8) Click OK at the Alert error message and ignore it.

9) List your Description Translation Library to ensure the file was read correctly, you can view it:
MapScenes and MapScenes Pro: MapScenes menu -> AutoMAP System -> Description Translation Library -> List Description Translation Library.
MapScenes 2006: -> MsMeasurement menu -> AutoMAP System -> Description Translation Library -> List Description Translation Library.

10) Now when you bring in your data to the drawing, at the Import Toggle Check dialog box, make sure to place a check mark in the Description Translation box for this translation from numeric to alpha characters to take place.

NOTE: To use the XYZ coding for automated line work with the numeric coding, I suggest adding a 1 in front for lines and 2 for curves. Then add these to the library file as new descriptions. For example: if 12 code is for EP, so 112 will be ZEP and 212 will be XEP. So you will have 3 edge of pavement descriptions: 112 will just bring in a point, 112 will join other 112 codes with straight lines, and 212 codes will produce Fit curved lines between the points.

Cheers,

Glen W. Cameron, CET

Technical Support Manager