Is This Content Helpful?
We're glad to know this article was helpful.
Formatting the DLG major/minor code pairs when translating data with ARCDLG.
The major/minor code pairs MUST be defined in INFO as 6,6,I. The items are called:
Major1 and Minor1 must be added to the attribute table for the feature class that the attributes represent. The first pair, major1 and minor1 are the minimum set that must be used. For example, if an attribute for polygons was to be transferred to a DLG file, major1 and minor1 must be added to the PAT. The attribute of interest is moved into major1. The minor1 item is used to further define the meaning of major1. If a value for minor1 is not needed, then its value can be calculated to -99999. However, a value must be assigned if minor1 is present in the feature attribute table, either a legitimate value or -99999. If no attributes are to be transferred to the DLG, then no major/minor code pairs need to be added. The warning message below will appear if no major/minor code pairs exist on any of the feature attribute tables for the coverage:
Arc: arcdlg dlgnomm dlgnomm.dlg
Converting dlgnomm to DLG file dlgnomm.dlg
Node attribute file does not exist or cannot be opened.
Node attributes cannot be written.
AAT file for in_cover lacks proper major/minor pairs.
ACODE file for in_cover does not exist or cannot be opened.
Arc attributes cannot be written.
The message simply means that the DLG file has been created, but no attributes were transferred.
There can be up to 6 major/minor code pairs that can be added to the AAT, PAT, or the NAT. A discussion of the major/minor code pairs can be found in:
Digital Line Graphs for 1:24,000-Scale Maps, Data users guide
This document can be obtained from the USGS.