Merging Clutter Codes within a Land Use Database

Clutter data provided in an MSI-Planet or ArcView ASCII grid format may contain more than 15 clutter codes. The EDX software before version 9.1 / 6.1 can use up to 15 codes so it may be necessary to translate or merge some of the original codes. For example, the original database might contain a class for “open land” and one for “pasture land”. These two categories are essentially the same as far as radio propagation is concerned so they could be merged into one class. In order to merge or translate classes it is first necessary to make a file containing the following information:

original_code(1), new_code(1)
original_code(2),new_code(2)
. .
original_code(n), new_code(n)

As an example, the file might look like this:
5, 6
7, 3
9, 3
21, 7
22, 7
23, 12
24, 9
25, 9

Note that a clutter code can be translated as well as merged (7 becomes 3 so that 7 can be a merge of 21 and 22). Original_codes not in this “merge” file are left as is If the source data is ArcView ASCII grid the “merge” file needs to have the same name as the clutter data source file but with “.mrg” added to the end (ex: clutter_data.asc.mrg). Put this merge file in the same folder as the clutter data file. If the source data is in MSI Planet format then name the “merge” file “clutter_translate” and put it in the same folder as where the Planet data “index” file is.