Part 1-Template Dvmnt

7/27/2019 Part 1-Template Dvmnt.

1/82

National Mapping ProgramTechnical Instructions

Part 1Template Development andUse

Standards for 1:24,000-Scale

Digital Line Graph and

Quadrangle Maps

U.S. Department of the InteriorU.S. Geological Survey

National Mapping Division


2/82

Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle MapsPart 1: Template Development and Use

4/96 1-ii

CONTENTS Page

1. Template Development . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Extraction Specifications . . . . . . . . . . . . . . . . . . . . 1-2

1.1.1 Feature Definitions . . . . . . . . . . . . . . . . . . 1-3

1.1.2 Attributes and Attribute Values . . . . . . . . . . . . 1-5

1.1.3 Delineation . . . . . . . . . . . . . . . . . . . . . . 1-5

1.1.4 Representation Rules . . . . . . . . . . . . . . . . . . 1-6

1.1.5 Capture Conditions . . . . . . . . . . . . . . . . . . . 1-6

1.1.6 Attribute Information . . . . . . . . . . . . . . . . . 1-9

1.1.7 Source Interpretation Guidelines . . . . . . . . . . . 1-10

1.1.7.1 All Sources . . . . . . . . . . . . . . . . . 1-10

1.1.7.2 Graphic . . . . . . . . . . . . . . . . . . . 1-10

1.1.7.3 Revision . . . . . . . . . . . . . . . . . . 1-11

1.2 Product Generation Rules . . . . . . . . . . . . . . . . . . . . 1-13

1.2.1 Inclusion Conditions . . . . . . . . . . . . . . . . . 1-14

1.2.2 Generalization . . . . . . . . . . . . . . . . . . . . 1-14

1.2.3 Symbolization . . . . . . . . . . . . . . . . . . . . 1-15

1.2.4 Conflict Detection and Resolution . . . . . . . . . . 1-17

1.2.4.1 Reading Conflict Detection and Resolution Rules 1-17

1.2.4.2 Spatial Operators . . . . . . . . . . . . . . 1-19

1.2.4.3 Resolution Strategies . . . . . . . . . . . . 1-22

1.2.5 Names and Labels . . . . . . . . . . . . . . . . . . . 1-23

1.3 Discrepancy Report. . . . . . . . . . . . . . . . . . . . . . . 1-24


3/82


4/96 1-iii

APPENDIXES Page

1A Instructions for Using Feature Templates During DLG-3 Revision . 1A-1

1B Part 5 Feature Index to DLG-F Feature . . . . . . . . . . . . . 1B-1

1C Part 6 Feature Index to DLG-F Feature . . . . . . . . . . . . . 1C-1

1D DLG-F to DLG-3 Feature Crosswalk . . . . . . . . . . . . . . . . 1D-1

1E DLG-3 to DLG-F Feature Crosswalk . . . . . . . . . . . . . . . . 1E-1


4/82


4/01 1-iv

LIST OF PAGES

A complete and current copy of Part 1 of Standards for 1:24,000-Scale Digital

Line Graphs and Quadrangle Maps consists of the pages (and most recent creation

or revision dates) listed below.

Page Date

1-ii 4/96

1-iii 4/96

1-iv 4/01

1-1 4/96

1-2 4/96

1-3 4/96

1-4 4/96

1-5 4/96

1-6 4/96

1-7 4/96

1-8 4/96

1-9 4/01

1-10 4/96

1-11 4/96

1-12 4/96

1-13 4/961-14 4/96

1-15 4/96

1-16 4/96

1-17 4/96

1-18 4/96

1-19 4/96

1-20 4/96

1-21 4/96

1-22 4/96

1-23 4/96

1-24 4/96

1A-1 4/96

1A-2 4/96

1A-3 4/96

Page Date

1A-4 4/96

1A-5 4/96

1B-1 4/96

1B-2 4/96

1B-3 4/96

1B-4 4/96

1B-5 4/96

1B-6 4/96

1B-7 4/96

1C-1 4/96

1C-2 4/96

1C-3 4/96

1C-4 4/96

1C-5 4/96

1C-6 4/96

1C-7 4/011C-8 4/96

1C-9 4/96

1D-1 4/96

1D-2 4/96

1D-3 4/96

1D-4 4/96

1D-5 4/01

1D-6 4/96

1D-7 4/96

1D-8 4/96

1D-9 4/96

1D-10 4/96

1D-11 4/96

1D-12 4/96

Page Date

1D-13 4/96

1D-14 4/96

1D-15 4/96

1D-16 4/96

1D-17 4/96

1E-1 4/01

1E-2 4/96

1E-3 4/96

1E-4 4/01

1E-5 4/96

1E-6 4/96

1E-7 4/96

1E-8 4/96

1E-9 4/96

1E-10 4/96

1E-11 4/961E-12 4/01

1E-13 4/96

1E-14 4/96


5/82


4/96 1-1

1. TEMPLATE DEVELOPMENT

The following information describes how to use the feature

templates. The sections explain what is included in each part of

the template and any global rules that apply throughout the

templates. If a rule applies to all features, it is a global rule.

An example is a rule for how to measure a feature to determine if it

meets capture conditions. The templates contain only exceptions to

the global rule or additional information that is unique to the

feature. If nothing appears in the template to change a global

rule, then the rule applies.

Throughout the templates, if something being described meets the

definition and capture conditions of a feature, the feature nameappears in all CAPS. Generic descriptions of features appear in

lower case type to indicate they may not meet the definition of the

feature and should not be considered as that feature.

There are three reasons why an entry in the template does not

contain information.

1. There is no applicable information, indicated by N/A.

Examples:

o Attribute/Attribute Value list when a feature has no

attributes

o Attribute Information when a feature has no attributes

o Various specifications in the symbol table that don't

apply

2. There is information not yet developed, indicated by TBD.

Examples:

o Rules for Names and Labels

3. In some cases, information could be developed, but none is

currently available, indicated by a blank.

Examples:

o Generalization

o Conflict Detection and Resolution


6/82


4/96 1-2

1.1 EXTRACTION SPECIFICATIONS

The data extraction specifications in the feature templates contain

all the information required to collect feature data. These

specifications tell what is collected as a certain feature and when

and how the feature is collected. The extraction specifications

include:

1.1.1 Feature Definitions

1.1.2 Attribute and Attribute Values

1.1.3 Delineation

1.1.4 Representation Rules

1.1.5 Capture Conditions

1.1.6 Attribute Information

1.1.7 Source Interpretation Guidelines

The templates are as concise and positive as possible, and each

template is meant to stand alone. Therefore, definitions,

attributes, and attribute values describe what the feature looks

like, not what it DOES NOT look like. Similarly, capture conditions

explain when to capture a feature, not when NOT TO capture the

feature. If this approach had not been used, each template could be

too cumbersome, and too confusing, to be useful.

The capture conditions reflect the NMD policy of cartographic

collection, which restricts data content and position based on

graphic limitations of scale and legibility. Only content that can

be displayed on the printed map is collected and all offsets in

position necessary to accommodate symbolization are performed at the

time of data collection. This policy, and the feature templates,

will change as user requirements for geographic content and position

become known and as technology and resources are developed to

support the implementation of product generation rules for content

generalization and symbol conflict resolution.


7/82


4/96 1-3

1.1.1 Feature Definitions

Feature definitions are used to decide how to classify a feature.

Attributes, delineation, and capture conditions limit which

occurrences of a feature, from a class of features, the NMD

collects. The main goal in classifying features is to define the

features so that the distinctions between them are clear.

The features and their definitions were developed by studying a

variety of sources including; NMD documentation; the Defense Mapping

Agency's Feature and Attribute Coding System; Geographic Names

Information System feature classes; the Spatial Data Transfer

Standard feature list; publications from other Federal agencies,

including National Ocean Service, Bureau of Land Management, Forest

Service, and the Fish and Wildlife Service; and the CanadianNational Topographic Data Base feature list. Attempts were made to

coordinate feature definitions with other organizations, however,

feature selection is somewhat different from one agency to another

and even between units within each agency.

The feature definitions provide the distinguishing characteristics

needed to differentiate between features. Although the difference

between STREAM/RIVER and LAKE/POND is obvious, the distinction

between STREAM/RIVER and CANAL/DITCH may not be so obvious. In this

example, a feature that could be either a STREAM/RIVER or a

CANAL/DITCH can be classified by comparing the two definitions.

Although both STREAM/RIVER and CANAL/DITCH are linear water bodies,

the definition for CANAL/DITCH specifies that it is artificial and

that it is used to transport water, to drain or irrigate land, to

connect two or more water bodies, or to serve as a waterway for

watercraft. Therefore, CANAL/DITCH is distinguished from

STREAM/RIVER by (1) the fact that it is artificial, and (2) the fact

that it has specific uses. If the feature in question does not meet

these two criteria, it is not a CANAL/DITCH.


8/82


4/96 1-4

Although the feature definitions include those characteristics of a

feature that the NMD uses to distinguish among features, the

templates do not necessarily specify how to make the distinction.

How one goes about deciding if something is artificial or natural,

or if it is used for some special purpose or not, is beyond the

scope of the templates. Annotation guides can be developed to

support the content of the templates. These guides could contain

graphic examples that illustrate map and real world identification

and delineation of features.

There are some cases where the distinction between features is not

clear, usually because past practices do not lend themselves to the

classification method used to develop the domain of features. There

are also cases where the definition is clear, but, again, because ofpast practices in the NMD, there might be some confusion. For

example, the definition of a LAKE/POND states that it is a "body of

standing water," so a dry lake doesn't fit the definition. However,

the NMD symbol books describe dry lakes under lakes and ponds and in

the DLG-3 format they are collected as lakes with a descriptive

attribute of dry. In this case, a rule is developed in Source

Interpretation Guidelines to reinforce the definition. The rule in

this example is: "Do not capture dry lakes as LAKE/POND. See

PLAYA."


9/82


4/96 1-5

1.1.2 Attributes and Attribute Values

Attributes describe characteristics of features. Many of these

characteristics fall into one of three groups: (1) "Type" describes

the function or purpose of a feature; (2) "Category" describes the

form or nature of a feature; and (3) "Status" describes the state or

existence of the feature or characteristic.

Definitions for attributes and attribute values are generic. The

definition for the attribute "Elevation" is "The vertical distance

from a given datum." This applies whether elevation is applied to

a LAKE/POND or a STREAM/RIVER or a CONTOUR.

In some cases, more than one value for a given attribute can be

selected. The ability to provide multiple values for an attributemakes it unnecessary to capture multiple features. For example, if

a mine produces multiple products, only one instance of the feature

mine is captured and the applicable products are assigned as values

to the attribute Product. Currently, the templates do not identify

those attributes that can be multi-valued, although the information

is stored in the standards data base.

For most features, there is a discrete list of appropriate attribute

values. However, for a few features, such as RESERVATION, the

number of potential descriptors is quite large and it is not

possible to create an exhaustive list of values. Selecting an

alphanumeric value for the attribute "Text" provides the necessary

flexibility to describe a RESERVATION.

1.1.3 Delineation

Delineation specifications describe what the limits of a feature are

and what to include in the feature that meets capture conditions.

The delineation generally describes real world entities.


10/82


4/96 1-6

1.1.4 Representation Rules

The representation rules are described in two tables. The first

table lists the relationships in which a feature may participate and

the second table lists the feature object types used to represent

the feature.

The relalationship table presents the relationship name, the

cardinality, and the related feature object. The cardinality

expresses the minimum and maximum number of times one instance of a

feature can be involved in the relationship. However, the current

design of the standards database is flawed and the cardinality

cannot be entered properly, so the cardinality is not populated.

The representation conditions table presents the feature objectsused to represent a feature and the criteria to determine which

feature object is used. The values displayed in the columns for

"AREA", "SHORTEST" and "LONGEST" are sizes based on an areal

measurement, the shortest axis, or the longest axis of the feature.

A feature is represented by a specific feature object when the size

criteria in the appropriate column is met. If a feature can only be

represented by one feature object, then the only value shown will be

">0" in one of the columns. If no values appear in any column, then

special conditions must be present to indicate the appropriate

feature representation. Special conditions may also exist in

conjunction with values in table.

1.1.5 Capture Conditions

The feature definitions describe what to capture, and the capture

conditions describe when to capture it. Capture conditions are

generally independent of source. The capture conditions currently

reflect the content of a standard update product. Because primary

mapping has been completed for the entire United States, most

National Mapping Program activity is focused on revision.

Information on data capture that pertains to specific sources or

revision methods is found in the Source Interpretation Guidelines

section.


11/82


4/96 1-7

The templates must contain the criteria necessary to ensure that NMD

products are accurate and consistent in style and content.

Therefore, the capture conditions present the requirements for the

content of NMD products, not just the step-by-step decisions an user

needs to make in deciding whether to capture a particular feature.

An If...Then" format is used for the capture conditions. The basic

format is as follows:

If FEATURE is CONDITION,Then capture.

When there are multiple capture conditions, each statement stands

alone. If the feature meets one of the conditions, it is captured.

Capture conditions are given in inches at map scale. In general,

features are measured along the longest axis (length) and/or the

shortest axis (width). Square features are measured along either

axis, round features are measured by the diameter, and irregular

features are measured against the axes of the best fitting rectangle

(nonoriented). Linear features are measured as the accumulative

measurement along the centerline of the feature for length and the

predominant distance across the feature (measured perpendicular to

the centerline) for width. Any specific or unique requirements for

measurement are addressed separately for each feature.


12/82

2

2 4

1

0.1

0.1

2 ft.

2 ft.


4/96 1-8

For areal measurements, the capture conditions are expressed as X

square inches. Square inches indicate that the value is an areal

value. Thus, 4 square inches indicates an area equivalent in extent

to a square which measures 2" by 2", or to a rectangle which

measures 1" by 4". Two examples of area = 4 square inches are:

Decimal values are handled in the same way; an area described as

0.01 square inches indicates an area equivalent in size to a squarewhich measures 0.1" by 0.1". An example of area = 0.01 square inches

is:

Do not confuse this terminology with the usage "2 foot square,"

where neither the value nor the unit is areal. For example:

The areal value terminology is used in the templates because it

allows an area to be defined independently of lengths and widths.

If there areminimum length or width requirements, then these values

are included in the capture conditions in addition to the area

value.


13/82


4/01 1-9

1.1.6 Attribute Information

Attribute Information describes how to value the attributes once the

feature is captured. Any required conditions and/or attribute value

combinations are given. All attributes must be valued.

There are three global attribute values that apply to many

attributes. These are "Unspecified", "Not Applicable", and

"Unknown".

o Unspecified is used when the value is not known, but is not

necessary. For example, a spring shown on the map with no

additional label would have the value Unspecified for the

attribute Water Characteristics.

o Not Applicable is used when a particular occurrence of a

feature cannot have a particular attribute value. For

example, if the water level of a STREAM/RIVER is not

controlled for navigation, the value for Elevation = Not

Applicable, because the attribute does not apply and therefore

cannot be valued.

o Unknown is used when a required value is not known. For

example, if the class of a road cannot be determined during

collection or revision, the value would be unknown. Other

sources will be required to determine the appropriate value.


14/82


4/96 1-10

1.1.7 Source Interpretation Guidelines

Source Interpretation Guidelines provide additional information for

interpreting the capture conditions when capturing data using

specific source materials or methods. They also contain any

modifications to the capture conditions specific to the source or

capture methods.

1.1.7.1 All sources

This information helps interpret the capture conditions regardless

of the source or method used in data capture. Included are such

things as when to capture a coincident feature based on the capture

conditions, when to capture more than one instance of the feature,

and when to capture something as a different feature instead of the

feature in the template. For those features that can occur in morethan one theme, this section provides the guidelines for which theme

should contain a specific feature instance.

1.1.7.2 Graphic

This information helps interpret the capture conditions when the

source is a map. Included are guidelines for interpreting the

symbology for proper classification, delineation, and capture.

When deciding to capture a feature from a graphic source, the

capture conditions still apply. Features that do not meet the

capture conditions are not captured. Generally, this reflects

changing requirements. For example, a number of offshore features

shown on NMD maps prior to 1961 are no longer required and should

not be captured, even though they appear on the graphic.

Some capture conditions cannot be evaluated just by looking at the

map. For example, when a feature is represented with a point symbol

and the capture conditions state a size requirement, it is not

possible to evaluate the true size of the feature from the graphic.

If compliance with the capture conditions cannot be determined, then

the feature is collected. Further evaluation will be done at the

time of revision.


15/82


4/96 1-11

In some cases, instructions are given to collect features for which

the symbology has been suppressed on the map. For example,

instructions are given on how to capture PLSS information when PLSS

lines are dropped from the map because they are coincident with a

boundary or a road.

1.1.7.3 Revision

This information helps interpret the capture conditions during

revision. The term "revision" applies to the process by which data

are updated to reflect changes that have occurred since the date of

the existing DLG or, for simultaneous collection and revision, the

Digital Raster Graphic (DRG).

Guidelines in this section are divided by the category of revision.Headings in this section are: Revision - General, Revision -

Standard, and Revision - Limited. If no guidelines appear in any of

these revision categories, then the guidelines in the remainder of

the feature template apply.

Revision - General

Revision - Standard

Revisions - Limited - The goal for a limited update is that feature

content will be current, but will include only: (1) those feature

types that are photoidentifiable on a monoscopic source,

supplemented with limited ancillary sources, and (2) those feature

types from existing DLG's or DRG's that are not photoidentifiable

but are not particularly prone to change. Some feature types are

not revised at all while other feature types are revised with

limited attribution. Existing data may or may not be revised.

Ancillary sources may be required to revise some data. All of this

information is provided in the limited update section.

If no limited update guidelines appear, the feature and all its

attributes are revised using guidelines in the remainder of the

template.


16/82


4/96 1-12

If a feature is not revised during a limited update, guidelines

state this and give information on how to handle existing DLG data.

The guideline "Do not revise. Delete existing features." means the

feature is not revised and all feature instances are deleted from

the DLG. The guideline "Do not Revise. Retain existing features."

means the feature is not revised and features that already exist in

the DLG are retained except when that feature is replaced by another

instance of a feature type that is revised in a limited update.

If a feature is revised, but only under certain conditions, those

conditions will be stated, as well as how to handle existing DLG

data. For example, in the feature PIPELINE, the guideline states

"Revise aboveground pipelines only. Retain existing features."

There are some cases where only existing DLG data are revised and

only under certain conditions. The guideline "Do not add new

features. Revise existing features (conditions)." applies to these

cases.

Special instructions may also apply to attribution. If attribution

cannot be determined in limited update, that will be noted in this

section. For example, the guideline for BUILDING states that

Building Type = Unspecified for limited update. In addition it

will be noted whether the value applies to existing data or not. In

the case of BUILDING, the guideline states "Existing buildings will

be given Building Type = Unspecified."

If data is being collected from a DRG as part of a simultaneous

collection/revision project, the limited update instructions still

apply. When revising data from a DRG, the term "retain" is

interpreted to mean "collect" and the term "delete" is interpreted

to mean "do not collect". So, the guideline "Do not revise. Retain

existing features" means "Do not revise. Collect existing features"

The guideline "Do not revise. Delete existing features" means "Do

not revise. Do not collect existing features."


17/82


4/96 1-13

1.2 PRODUCT GENERATION RULES

The feature definitions, delineation, extraction specifications, and

representation rules provide the guidelines for creating a data

base. Upon creation of the data base, an additional set of rules is

needed to provide guidelines for manipulating and processing the

data to generate a particular cartographic product. These product

generation rules are divided into five groups:

1.2.1 Inclusion conditions

1.2.2 Generalization

1.2.3 Symbolization

1.2.4 Conflict detection and resolution

1.2.5 Names and labels

The information in the Product Generation sections is not as

complete as the information in the Data Extraction sections.

Additions and modifications to the rules will occur as research

continues. The Symbolization section is the most complete. The

Conflict Detection and Resolution section and the Names and Labels

section contain rules that have been identified thus far in the

process, but these sections will require additional research.

Inclusion Conditions and Generalization requirements are described

in the template under the heading "Data Extraction or Product

Generation." Depending on the content of the data base, these

activities could take place at different times in the production

process. Current collection policy dictates that the database

contains only the information required to create a map, therefore

the inclusion conditions are equivalent to the capture conditions

and generalization is not required. A collection policy that

permits more geographic collection, would mean that the database

contains information other than that required to create a specific

product. Inclusion Conditions and Generalization for specific

products then will be defined.


18/82


4/96 1-14

1.2.1 Inclusion Conditions

Inclusion conditions are used to select feature instances from the

data base to meet the requirements of a particular product. The

policy in data extraction is to capture only what is required for a

map, inclusion conditions are often "all required."

In the future, specifications and rules will be developed for other

products, such as 1:50,000-scale topographic maps, that will be

produced using the 1:24,000-scale database. In these cases, the

inclusion conditions will reflect requirements for reduced content.

1.2.2 Generalization

Generalization is a process whereby feature detail is removed so

that the resolution of the map is appropriate to its scale. NMDcurrently has a cartographic collection policy, so this function

takes place as the data are collected and completion of this section

is not required. As the move is made toward geographic collection

and there is more content in the data base than will be shown on a

map, these rules will be developed.


19/82


4/96 1-15

1.2.3 Symbolization

Specifications for symbolizing and labeling feature objects are

presented in tabular form and are organized according to the

dimensionality of the feature object to be symbolized. All 0-D

(point) symbols are listed first, then all 1-D (linear) symbols, and

then all 2-D (areal) symbols.

A feature is shown as specified in the symbol tables. If a feature

object is resymbolized during conflict detection, the rules appear

in the Conflict Detection and Resolution section of the template.

Each entry in the symbol specification table includes a diagram of

the symbol. Labels that are not derived from attribute values are

shown as they appear on the graphic and in the primary placementposition (position that will appear on the graphic unless a

placement conflict occurs). An example is the lable "Geyser" for

the feature GEYSER.

Often, attribute values provide the information to be used for names

and labels. The symbolization table uses boxes to indicate those

attribute values which will be used as labels. For example, the

proper name of a feature is stored as a value of the attribute Name.

The symbol diagram shows the 3-letter code associated with the

attribute, outlined in a box NAM. This indicates that the

alphanumeric text stored as the value for Name is printed as the

Name label. As another example, the feature SPRING has the

attribute Water Characteristics, with possible values of Alkaline,

Hot, Sulphur, or Unspecified. A box outlining the code for Water

Characteristics (WAC) indicates that the label equates to whatever

value is stored for Water Characteristics for an instance of the

feature SPRING. All attribute values used as labels are shown in

this manner. Values of "Unspecified," "Not Applicable," and

"General Case" are not used as labels, and when an attribute has one

of these values, no lavel is generated.


20/82


4/96 1-16

Attribute Column

This column lists only those attributes whose values affect

symbolization.

Value Column

This column lists the attribute values which determine the

symbolization. The table contains a separate entry for each

combination of attribute values that requires a unique symbol. (In

the contex of the symbolization table, a symbol includes not only

the graphic part of the symbol, but also the name and (or) label

associated with that symbol).

Symbol Specifications Column

This column contains a standarized set of words to describe thesymbols. Each symbol is divided into standarized units or

components (lines, circles, rectangles, etc.). Lineweight, color,

dash length and spacing, and other parameters are included for each

component, as appropriate. In some cases, two or more symbol

components are combined to produce a symbol (e.g., the symbol for a

school building consists of a square, line, and triangle).

Type Specifications column

If an attribute value provides a label for a symbol, the attribute

name appears as a bold heading in this column, with additional

parameters listed describing the color, style, size and spacing of

the text. (The 3-letter code associated with the attribute name is

shown as part of the symbol). Other text used to label the symbol

is described under the bold heading Label:

Symbol #

Each symbol for each feature object is given an ID code. The code

consists of a letter indicating the dimensionality of the feature,

P for O-D (point) feature objects, L for 1-D (linear) feature

objects, and A for 2-D (aeral) feature objects, plus a three digit

number. The numbers are consecutive starting with 001. Each

dimension starts over again with 001 (e.g., P001, P002, L001, L002,

A001). When used in combination with the feature type (or feature

object code), this code provides a unique code for each feature

object symbol.


21/82


4/96 1-17

Symbol numbers for symbols that are the result of conflict detection

and resolution rules are number consecutively beginning with 100.

For 1:100,000-scale data, if the symbol is the same as that for a

1:24,000-scale product, the symbol number is the same. If the

1:100,000-scale symbol is different, it is given a number beginning

with 200 (or 300 if it is the result of a conflict detection and

resolution rule.)

1.2.4 Conflict Detection and Resolution Rules

Conditions exist in the real world that cannot be accurately

represented on a map; features in the real world may be very close

together so that their symbols on the map will coincide. These

conditions must be addressed at the time of product generation.

After the symbology is placed, as specified in the symbology tables,conflict detection and resolution rules describe how to resolve

these symbolized feature conflicts.

The rules for conflict detection and resolution are not complete at

this time. These rules need to be completely developed prior to

implementation of a geographic collection policy.

1.2.4.1 Reading Conflict Detection and Resolution Rules

Each rule defines a problem (conflict detection) and gives

instructions on how it is solved (resolution). The rules are

written in the "If...Then" format, with a specific conflict between

two symbolized features forming the "If" portion, and an action

statement forming the "Then" portion. A generic rule serves to

illustrate the basic format:

If Primary Conflict Feature conflicts withTarget Conflict Feature,

Then take specified action on Primary Conflict Feature.

The first symbolized feature mentioned in the rule is defined as the

Primary Conflict Feature, and it is the feature that will be acted

upon in the resolution. The other symbolized feature mentioned in

the rule is defined as the Target F=Conflict Feature. The verb that

describes the conflict between the Primary Conflict Feature and the

Target Conflict Feature is defined as the "spactial operator" (e.g.,

symbol_coalesces). Each spatial operator describes the nature of


22/82


4/96 1-18

the possible conflict between the two symbolized features. The

resolution portion of the rule, following the "Then," contains a

"resolution strategy". A resolution strategy, which is a

specifically defined term, such as "resymbolize", determines what

action should be taken to resolve the conflict.

The following points are important to remember:

o Measurement values apply to spacing between symbols and not

from symbol center to symbol center.

o The resolution portion of the rule does not have to restate

which symbol is acted upon, because it always refers to the

Primary Conflict Feature.

o The resolution portion of the rule calls for action on either

a symbol or a symbol section. Symbol refers to the entire

symbol for a given feature (If MILE MARKER coincides BRIDGE,

then suppress_symbol). Symbol section refers to a portion of

the feature that is in conflict (e.g., If BOUNDARY coincides

with Boundary Point, then suppress_section).

o A conflict detection rule appears only in the template of the

Primary Conflict Feature.

o Conflict detection and resolution rules handle only those

conflicts that NMD wants to resolve. There are symbol

coincidences and overlaps that are acceptable and for which

conflict detection and resolution rules are not needed.

Example: A bench mark symbol on a contour line is an

acceptable symbol coincidence.


23/82


4/96 1-19

An example of a Conflict Detection and Resolution Rule is:

If BRIDGE (Primary Conflict Feature) coincides (spatial operator)

ROAD, RAILWAY, or CANAL/DITCH (Target Conflict Feature), Then

suppress_section (resolution).

Translation: If the symbol for BRIDGE is coincident with the symbol

for ROAD, RAILWAY, or CANAL/DITCH, then don't show the coincident

part of the BRIDGE symbol.

1.2.4.2 Spatial Operators

Current conflict detection rules use three spatial operators:

o symbol_coalesce

o symbol_follows

o coincides

The symbol_coalesce operator tests symbolized graphic data. This

spatial operator is a test for the closeness of two symbolized

features. Two features coalesce if the minimum separation of the

outlines of their symbols is less than a specified separation

distance. This separation distance is a required parameter that

must be stated in the conflict detection and resolution rule.

Example:

If TANK symbol_coalesces ROAD, separation = 0.005", Then

symbol_displace.

(The symbol should be moved only until the specified separation is

reached.)


24/82


4/96 1-20

The symbol_follows operator tests symbolized graphic data. The

operator tests for the closeness of two symbolized map features over

a specified distance. The separation distance, and the length that

the features must remain within this separation distance, are

required parameters. The symbolized features follow each other if

the minimum separation of their outlines is less than the specified

separation distance for at least the specified length.

Example: If PIPELINE symbol_follows ROAD, separation = x", distance

= y", Then suppress_section.

The coincides operator uses centerline data. The operator tests for

strict coincidence of at least part of the centerline data. The

test for coincides is performed by determining if the features own

any of the same topology, either points, chains, or polygons. Two

features are coincident if they share at least one spatial object,

complete equivalence is not a requirement for the coincident

condition. Table 1describes the valid topology for coincidences.

Example: If WELL coincides WINDMILL, Then suppress_symbol.


25/82

P, N N N P, N *

N C C C * *

N C C C

C

P, N * C * *

C

C Pg


4/96 1-21

Table 1

Valid Topology for Coincides Spatial Operator

0-D 1-D 2-D 2-D

(perimeter) (fill)

0-D

1-D

2-D

(perimeter)

2-D

(fill)

P = Point, N = Node, C = Chain, Pg = Polygon

* Node must be on a chain that is internal to the polygon

** The chain cannot be part of the boundary of the polygon


26/82


4/96 1-22

1.2.4.3 Resolution Strategies

The current action statements listed below describe how the detected

conflict is resolved.

Symbol_displace Alter the centerline geometry of the

feature object to achieve the specified

separation distance.

Resymbolize Remove the symbolization of an entire

feature object and replace it with the new

symbol as provided in the rule.

Resymbolize_section Remove the symbolization of only a portion

of a feature object and replace it with the

new symbol provided in the rule.

Suppress_symbol Suppress the display of an entire feature

object.

Suppress_section Suppress the display of a portion of a

feature object.

Rotate_symbol Change the orientation of a symbol or

symbol component to a given angle.

Orient_symbol Change the orientation of a symbol or

symbol component with respect to another

feature.


27/82


4/96 1-23

1.2.5 Names and Labels

Basic name and label information is contained in the symbol portion

of the template. The names and label section contains additional

information. This section is divided into two subsections: (1)

selection and (2) placement. The selection subsection contains

rules for determining when a particular feature is named or labeled.

Rules for determining where to place the name or label are listed in

the placement subsection. Like the section on conflict detection

and resolution, this section of the template is not yet fully

developed.


28/82


4/96 1-24

1.3 Discrepancy Report/Request for Review of Requirements

Complete a Discrepancy Report when an error is found in the feature

templates or when a statement in the templates is not understood and

a more clearly written statement is requested. The signature of a

supervisor is required for submittal.

Complete a Request for Review of Requirements when a modification,

addition, enhancement, or deletion of the requirements in a feature

template is identified and the requested change makes a fundamental

modification to the existing requirement(s). Before submitting a

Request for Review of Requirements, please review the technical

review notes (available from members of the mapping center standards

team) for that particular feature and theme to evaluate whether the

issue has already been discussed and resolved.

Submit the form Discrepancy Report/Request for Review of

Requirements to:

Standards Team Leaders at Rocky Mountain Mapping Center and Mid-

Continent Mapping Center.


29/82

Discrepancy Report/Request for Review of Requirements

Discrepancy Report Request for Review of Requirements (Check one)

Name of Originator: Phone #:

Supervisor's Signature: Date:

Office (Unit, Section, or Branch):

Location: EDC MAC MCMC RMMC WMC HQ

Product: 1:24,000 1:24,000 Single Edition 1:100,000

Core Content National Hydrography Dataset __

Template Heading:

Change requested:

Mapping Center Authority's Signature:

(Required only for Request for Review of Requirements)

Date Received:

Analysis of Request:

Action: Change rejected Change made Requires policy decision

Date:


30/82

Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle MapsPart 1: Template Development and UseAppendix 1A

1A-1

APPENDIX 1A

Instructions For Using Feature Templates During DLG-3 Revision


31/82


1A-2

INSTRUCTIONS FOR USING

FEATURE TEMPLATES DURING DLG-3 DIGITAL REVISION

The current DLG-3 attribute codes are defined by symbols on a map. DLG-3

instructions state how to interpret the symbols on the map, how to collect a

particular feature, and which code to use. All of the decisions about how a

symbol, which represents a real world phenomenon, got on the map in the first

place are described in various other documents. These include Topographic and

Technical Instructions, mapping center compilation guidelines, reports of phone

calls, supplemental instructions, notes in the margins, and oral history.

The Standards for 1:24,000-scale Digital Line Graphs and Quadrangle Maps have

been developed over the past 3-4 years by reviewing all of the instructions that

could be found about a particular feature, resolving inconsistencies, and

formatting this information in a feature template. The feature templates wereextensively reviewed by teams at the mapping centers and by management to ensure

that they capture current NMD requirements for defining and collecting real world

features. The feature templates provide consistent, concise, unambiguous

instructions that describe what we show on our maps.

DATA EXTRACTION

The feature templates provide the following information:

Feature Definitions - whether the feature is a road or a trail, for example.

Delineation - what the edges of the feature are.

Capture Conditions - what criteria the feature must meet to be considered for

collection (content worthy).

The information in these sections applies whether making a map or collecting DLG-

3 or DLG-F data. Use the feature definition to decide which feature you are

looking at on the Digital Orthophoto Quadrangle (DOQ), use the delineation to

decide what the edges of the feature are, and use the capture conditions to

decide if the feature is collected or not.

For example, a small standing (as opposed to flowing) water body appears in the

image. It is probably a LAKE/POND or a RESERVOIR. It has a natural shoreline,

so is not a constructed basin. Based on the feature definition, it is a

LAKE/POND and not a RESERVOIR.


32/82


1A-3

Use the delineation to determine the extent of the LAKE/POND. It is naturally

formed and appears to be perennial, so based on the delineation, the edge of the

LAKE/POND is the position of the shoreline when the water is at the stage that

prevails for the greater part of the year (average water elevation.)

Use the capture conditions to determine if this feature should be collected. In

this example the State is South Carolina, which is not an arid area. At average

water elevation, the LAKE/POND is 400 feet wide (0.2" at 24K) and 600 feet long

(0.3" at 24K). The capture conditions require the capture of a LAKE/POND if it

is greater than .05" along the shortest axis. The example meets the capture

criteria and so it is captured.

After the feature is classified and the decision to capture is made, the

representation in the digital file must be determined. At this point the feature

templates cannot be used.

The feature templates provide rules for how to represent features using the DLG-F

data model. Information in the Representation Rules section of the template

describes what kind of feature objects (0-dimensional, 1-dimensional or 2-

dimensional) are used to represent the features and in what relationships the

features may participate. This information applies only to DLG-F data and cannot

be used when collecting DLG-3 data. The current DLG-3 attribute coding standards

must be used to determine whether the feature is collected as a point, line, or

area and what codes should be attached to the spatial elements.

In the LAKE/POND example, the DLG-3 code 050 0421 describes a lake or pond.

Because the lake is 0.2" by 0.3", it is digitized as an area and given the code

050 0421. The lake, however, may need additional DLG-3 codes.

Generally, the attributes and values defined in the feature templates correspond

to descriptive or parameter codes in DLG-3 features. The main difference is that

for DLG-F features, all attributes must be explicitly valued, whereas in DLG-3

features, certain characteristics are implied by the absence of a code.

There are several attributes listed for LAKE/POND in the feature template. The

first is Elevation. The corresponding DLG-3 code 05N XXXX. The Attribute

Information section in the feature templates indicates that the value for

elevation is required only if there is a printed elevation. If the lake being

digitized had a printed elevation, code 05N XXXX would be added. Otherwise, the

code is not added. Note that the feature template requires an explicit

description of the stage that the elevation value represents. This information

is not explicitly collected in the DLG-3 format.


33/82


1A-4

The next attribute in the feature template is Hydrographic Category. The

corresponding DLG-3 code is 050 0610 (intermittent). Potential values are

defined in the template and the appropriate value is selected based on

definitions provided. Because the lake is perennial, no additional DLG-3 code

is required.

The next attribute in the feature template is Name. This information is not

collected in the DLG-3.

The last attribute in the feature template is Water Characteristics. The only

corresponding DLG-3 code is 050 0608 (salt). The choices in the template are

"salt" and "unspecified," which means the distinctive properties of the water are

identified only if the lake is "salty." Because there is no evidence (either

from the photographs or from the ancillary source) that the lake is "salty," no

additional DLG-3 code is required.

PRODUCT GENERATION

The feature templates also contain product generation information needed to

produce a graphic product. The Product Generation section of the templates

includes symbol tables with all of the symbol specifications needed to create a

graphic symbol based on combinations of attributes and values. These symbols

reflect specifications found in Part 5, "Publication Symbols," Standards for

1:24,000- and 1:25,000-Scale Quadrangle Maps. Use the symbol tables in the

feature templates to determine the graphic representation of a feature.

The conflict detection and resolution and the type selection and placement

sections of the template are not fully developed. The rules that are identified

in these sections reflect current mapping practices. For situations notidentified in the templates, apply whatever rules are currently in use in

traditional mapping.


34/82


1A-5

SUMMARY: How to use the feature templates in DLG-3 revision:

1. Determine what feature to collect from the feature definition found in the

templates (use Part 5 and Part 6 crosswalk tables in the appendices as an

aid).

2. Determine if the feature should be collected from the capture conditions

found in the templates.

3. Determine what the edges of the feature are (what to include when

digitizing) using the delineation section of the templates.

4. Find the appropriate DLG-3 code from the crosswalk table.

5. Digitize as a point, line, or area and code the elements using the DLG-3

specifications.

6. Determine the need for any additional DLG-3 codes by evaluating the

attribute list and attribute information in the feature templates.

In most cases, there will be a DLG-3 descriptive attribute code that

corresponds to the attributes and values in the feature templates. There

are cases where the feature templates provide more information than was

captured in the DLG-3 format, even though it appeared on the map. The

DLG-F format will capture this information. However, if the information

has not been coded in the past, it still will not be coded in DLG-3 and

references in the feature templates can be ignored.

7. Use existing DLG-3 instructions for other DLG-3 codes for which there isno corresponding feature or attribute in the feature templates. For

example, DLG-F models "flow direction" very differently from the DLG-3

model, so there are no corresponding guidelines for codes like upper

origin of stream. There are some DLG-3 codes that are cartographic

representations for which there is no equivalent in the feature templates.

These include things like bridge abutments, arbitrary extension lines, and

closure lines, which should be collected using the DLG-3 instructions as

guidelines.

8. Use the symbol specifications found in the symbol tables in the feature

templates. For what to do with conflicting symbols, use whatever

information can be found in the Conflict Detection section of the

templates and rely on other traditional sources to fill in the gaps. Do

the same for type selection and placement rules.

The end result is a DLG-3 file that looks like any other DLG-3 file, except that

new features have been added using the definitions, delineations, capture

conditions, and attribute information from the feature templates.


35/82

Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle MapsPart 1: Template Development and UseAppendix 1B

4/96 1B-1

APPENDIX 1B

Part 5 (Publication Symbols) Index to DLG-F Feature


36/82


4/96 1B-2

The following table is provided as an aid in translating the symbol

labels listed in the index to Part 5: Publication Symbols of

Standards for 1:24,000- and 1:25,000-Scale Quadrangle Maps to DLG-F

features. This table is only to direct the user to the appropriate

feature template and does not imply that the feature indicated is

the correct feature in all cases. This table is based on the

version of Part 5 that includes Change Notice Number 2.


37/82

Part 5 Index To DLG-F Feature

Part 5 Index Entry DLG-F Feature DLG-F Theme


4/96 1B-3

Airboat Trail LANE Transportation

Airport AIRCRAFT FACILITY Transportation

Alkali flat BARREN LAND Nonveg. Surface Cover

PLAYA Hydrography

Apron RUNWAY/APRON/TAXIWAY Transportation

Aqueduct CANAL/DITCH Hydrography

PIPELINE Hydrography

Archeological site ARCHEOLOGICAL SITE/RUIN Built-up

Area between shoreline

and sounding datum

line FORESHORE HydrographyArea limits CABLE/PIPELINE SITE Built-up

Area to be submerged AREA TO BE SUBMERGED Hydrography

Athletic field ATHLETIC FIELD Built-up

Bathymetric contour CONTOUR (BATHYMETRIC) Topo-bathy only

Battle trench EMBANKMENT Built-up

Beach, gravel BARREN LAND Nonveg. Surface Cover

Beacon TOWER Built-up

Bench mark

Boardwalk BOARDWALK Built-up

Boat ramp LAUNCHING RAMP Built-up

Boundary BOUNDARY LINE Boundaries

Boundary monument BOUNDARY POINT Boundaries

POINT MONUMENT Boundaries

Breakwater PIER/BREAKWATER/JETTY Built-up

Breastworks EMBANKMENT Built-up

Bridge BRIDGE Transportation, Hydrography

Building BUILDING Built-up

Built-up area BUILT-UP AREA Built-up

Cableway CABLEWAY Built-up

Campground CAMPGROUND Built-up

Campsite CAMPGROUND Built-up

Canal CANAL/DITCH Hydrography

Canal lock GATE Hydrography

Carline RAILWAY Transportation

Carolina bay BASIN Named Landforms

Causeway PIER/BREAKWATER/JETTY Built-up

Cave entrance CAVE ENTRANCE Named Landforms

Cemetery CEMETERY Built-up

Channel LANE Transportation

Cliff dwelling ARCHEOLOGICAL SITE/RUIN Built-up

Cog railway RAILWAY Transportation

Coke ovens KILN Built-up


38/82




4/96 1B-4

College BUILDING Built-up

INSTITUTIONAL SITE Built-up

Compressor station PIPELINE REGULATION STA. Built-up

Continental Divide DIVIDE Named Landforms

Contour CONTOUR Hypsography

Control point

Conveyor CONVEYOR Built-up

Coral reef REEF Hypsography

Corral HOLDING PEN Built-up

Cranberry bog CULTIVATED CROPLAND Vegetative Surface Cover

Crevasse field CREVASSE FIELD HydrographyCul-de-sac CUL DE SAC Transportation

ROAD Transportation

Cut CONTOUR Hypsography

Dam DAM/WEIR Hydrography

Dike EMBANKMENT Built-up

Ditch CANAL/DITCH Hydrography

Diversion dam DAM/WEIR Hydrography

Donation land claim PLSS AREA PLSS

Drawbridge DRAW SPAN Transportation

Drive-in theater OUTDOOR THEATER Built-up

DRIVE-IN THEATER SCREEN Built-up

Dry lake or pond PLAYA Hydrography

BARREN LAND Nonveg. Surface Cover

Drydock DRYDOCK Built-up

Duck pond INUNDATION AREA Hydrography

Dune area DUNES Nonveg. Surface Cover

Evaporator RESERVOIR Hydrography

Feedlot HOLDING PEN Built-up

Fence line FENCE LINE Built-up

Ferry LANE Transportation

Field line FENCE LINE Built-up

Fish hatchery AQUACULTURE SITE Built-up

Fish ladder FISH LADDER Hydrography

Flat PLAYA Hydrography

FORESHORE Hydrography

Floodgate GATE Hydrography

Flume FLUME Hydrography

Footbridge BRIDGE Transportation

Ford FORD Transportation

Foreshore flat FORESHORE Hydrography

Found closing corner SURVEY CORNER PLSS

Found section corner SURVEY CORNER PLSS


39/82




4/96 1B-5

Fumarole FUMAROLE Hydrography

Gaging station GAGING STATION Hydrography

Geyser GEYSER Hydrography

Glacial moraine MORAINE Nonveg. Surface Cover

Glacier ICE MASS Hydrography

Grave CEMETERY Built-up

Gravel beach BARREN LAND Nonveg. Surface Cover

Helipad AIRCRAFT FACILITY Transportation

HELIPAD Transportation

Highway ROAD Transportation

Holiday areaHomestead monument SURVEY CORNER PLSS

Horiz Control Sta.

House of worship BUILDING Built-up

Inadequate survey area

Incline railway RAILWAY Transportation

Intertidal zone FORESHORE Hydrography

Jetty PIER/BREAKWATER/JETTY Built-up

Lake LAKE/POND Hydrography

Land grant line LAND GRANT PLSS

SURVEY LINE PLSS

Land grant monument SURVEY CORNER PLSS

POINT MONUMENT PLSS

Land subj inundation INUNDATION AREA Hydrography

Landing strip RUNWAY/APRON/TAXIWAY Transportation

Landmark object see specific feature

Lava INCLINE/FLOW Named Landforms

BARREN LAND Nonveg. Surface Cover

Levee EMBANKMENT Built-up

Located object see specific feature

Location monument SURVEY CORNER PLSS

POINT MONUMENT PLSS

Mangrove TREES Vegetative Surface Cover

SWAMP/MARSH Hydrography

Marsh SWAMP/MARSH Hydrography

Meander Corner SURVEY CORNER PLSS

Mine

dump DISPOSAL SITE Built-up

entrance MINE ENTRANCE Built-up

open pit MINE Built-up

shaft MINE ENTRANCE Built-up

strip MINE Built-up

Mineral monument SURVEY POINT PLSS


40/82




4/96 1B-6

POINT MONUMENT PLSS

Mining claim SURVEY LINE PLSS

SPECIAL SURVEY AREA PLSS

Monorail MONORAIL Transportation

Mud flat BARREN LAND Nonveg. Surface Cover

Mud pot MUD POT Hydrography

Nonearthen shore NONEARTHEN SHORE Hydrography

Oil sump RESERVOIR Built-up

Open pit mine MINE Built-up

Orchard CULTIVATED CROPLAND Vegetative Surface Cover

Overpass UNDERPASS TransportationPenstock PIPELINE Built-up

Permanent snowfield ICE MASS Hydrography

Picnic area PARK Built-up

REST SITE Transportation

Pier PIER/BREAKWATER/JETTY Built-up

Pipeline PIPELINE Hydrography, Built-up

Pit MINE Built-up

Platform OFFSHORE PLATFORM Built-up

Pond LAKE/POND Hydrography

Power substation SUBSTATION Built-up

Power transmission lineTRANSMISSION LINE Built-up

Prospect PROSPECT Built-up

Pulloff area REST SITE Transportation

ROAD Transportation

Pumping station PIPELINE REGULATION STA Built-up

Quarry MINE Built-up

Racetrack RACETRACK Built-up

Raceway RACETRACK Built-up

Railroad RAILWAY Transportation

Railroad cut CONTOUR Hypsography

Railway RAILWAY Transportation

Ramp, boat or seaplane

Range line SURVEY LINE PLSS

Rapids RAPIDS Hydrography

Recreational slide RECREATIONAL SLIDE Built-up

Redoubt EMBANKMENT Built-up

Reef REEF Hydrography

Reference monument BOUNDARY POINT PLSS

Reservoir RESERVOIR Hydrography

Rest Area REST SITE Transportation

River mileage marker MILE MARKER Hydrography

Road ROAD Transportation


41/82




4/96 1B-7

Road cut CONTOUR Hypsography

Roadside park REST SITE Transportation

Rock ROCK Hydrography

Rocks, group of HAZARD ZONE Hydrography

Roundhouse BUILDING Built-up

Ruins ARCHEOLOGICAL SITE/RUINS Built-up

Runways RUNWAY/APRON/TAXIWAY Transportation

Sand BARREN LAND Nonveg. Surface Cover

Sand Dunes DUNES Nonveg. Surface Cover

Sand in open water BARREN LAND Nonveg. Surface Cover

School BUILDING Built-upINSTITUTIONAL SITE Built-up

Scrub SHRUBLAND Vegetative Surface Cover

Seaplane Landing Area LANE Transportation

Seaplane ramp LAUNCHING RAMP Built-up

Seawall WALL Built-up

Section line SURVEY LINE PLSS

Seep SPRING/SEEP Hydrography

Service area REST SITE Transportation

Sewage disposal plant SEWAGE DISPOSAL PLANT Built-up

RESERVOIR Built-up

Sewerline, submerged PIPELINE Built-up

Shoal HAZARD ZONE Hydrography

BAR Named Landforms

Shoreline SHORELINE Hydrography

Siphon PIPELINE Hydrography

Ski lift CABLEWAY Built-up

Sludge pit RESERVOIR Built-up

Sluice gate GATE Hydrography

Snowfield, permanent ICE MASS Hydrography

Snowshed BUILDING Built-up

Sounding datum line Sounding Datum Line Hydrography

Special survey mon. SURVEY CORNER PLSS

Spillway SPILLWAY Hydrography

Spoil area SPECIAL USE ZONE Hydrography

Spoil bank EMBANKMENT Built-up

Spot elevation SPOT ELEVATION Hypsography

Spring SPRING/SEEP Hydrography

Stockyard HOLDING PEN Built-up

Stream STREAM/RIVER Hydrography

Swamp SWAMP/MARSH Hydrography

Swimming pool RESERVOIR Hydrography

Tailings DISPOSAL SITE Built-up


42/82




4/96 1B-8

Tailings pond RESERVOIR Hydrography

Tank TANK Built-up

Taxiway RUNWAY/APRON/TAXIWAY Transportation

Telephone line TRANSMISSION LINE Built-up

Tennessee Valley Divide DIVIDE Named Landforms

Tide Station GAGING STATION Hydrography

Tidegate GATE Hydrography

Tollgate GATE Transportation

Township line SURVEY LINE PLSS

Tract PLSS AREA PLSS

Traffic circle ROAD TransportationTrail TRAIL Transportation

Trees, scattered TREES Vegetative Surface Cover

Tunnel TUNNEL Hydrography, Transportation

Turntable TURNTABLE Transportation

Underpass UNDERPASS Hydrography, Transportation

University INSTITUTIONAL SITE Built-up

Valve station PIPELINE REG. STA. Built-up

Vert control sta.

Vineyard CULTIVATED CROPLAND Vegetative Surface Cover

Wall WALL Hydrography, Built-up

Wash WASH Hydrography

Water filtration plant FILTRATION PLANT Built-up

RESERVOIR Hydrography

Waterfall WATERFALL Hydrography

Weir DAM/WEIR Hydrography

Well WELL Hydrography, Built-up

Wharf WHARF Built-up

Wind generator WINDMILL Built-up

Windmill WINDMILL Built-up

Witness corner SURVEY CORNER PLSS

Wooded swamp SWAMP/MARSH Hydrography

TREES Vegetative Surface Cover

Woods TREES Vegetative Surface Cover

Wreck WRECK Hydrography

HAZARD ZONE Hydrography

Wreckage, exposed HAZARD ZONE Hydrography


43/82

Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle MapsPart 1: Template Development and UseAppendix 1C

4/96 1C-1

APPENDIX 1C

Part 6 (Supplementary Publication Symbols) Index to DLG-F Feature


44/82


4/96 1C-2

The following table is provided as an aid in translating the symbol

labels listed in the index to Part 6: Supplementary Publication

Symbols of Standards for 1:24,000- and 1:25,000-Scale Quadrangle

Maps to DLG-F features. This table is only to direct the user to

the appropriate feature template and does not imply that the feature

indicated is the correct feature in all cases. This table is based

on the version of Part 6 that includes Change Notice Number 8.


45/82


4/96 1C-3


46/82


4/96 1C-4


47/82


4/96 1C-5


48/82


4/96 1C-6


49/82


Part 6 Index To DLG-F Featu re

Part 6 Index Entry DLG-F Featu re DLG-F Theme

4/01 1C-7

Railway, incline RAILWAY Transportation

Range line SURVEY LIN E PLS S

Rapids RA PIDS Hydrography

Reef REEF Hydrography

Reference monument BOUNDA RY POINT Boundaries

Reservoir RESERVOIR Built- up, Hydrography

Road ROAD Tran sportation

Rock ROCK Hydrography

Roundhouse BUILDING Built- up

Route markers ROUTE Tran sportationRuins ARCHEOLOGICAL SITE /RUINS Built-u p

Salt evaporator RESERVOIR Hydrography

Sand area BARREN LAND Nonveg. Su rface Cover

DUNES Nonveg. Su rface Cover

Sand, in open water BARREN LAND Nonveg. Su rface Cover

Sand, shifting DUNES Nonveg. Su rface Cover

Sand pit, large MINE Built-up

School BUILDING Built- up

INSTITUTIONAL SITE Built-u p

Scrub SHRUBLAND Vegetative Surf ace Cover

Seawall WALL Built-u pSection corner SURVEY CORNER PLSS

Section line SURVEY LIN E PLS S

Sewage disposal RESERVOIR Hydrography

Sewage disposal plant SEWAGE DISPOSAL PLANT Built-up

Shoal HAZARD ZONE Hydrography

BAR Named Landforms

Shoreline SHORELINE Hydrography

Siphon PIPELINE Hydrography

Ski lif t CA BLEWAY Built- up

Sludge pit RESERVOIR Built- up

Sluice gate GATE Hydrography

Snag HA ZA RD ZONE Hydrography

Snowf ield, permanent ICE MASS Hydrography

Snowshed BUILDING Built- up

Soundings SOUNDING Hypsography

Spoil bank EMBA NKMENT Built- up

Spot elevation SPOT ELEVATION Hypsography


50/82


4/96 1C-8


51/82


4/96 1C-9


52/82

Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle MapsPart 1: Template Development and UseAppendix 1D

4/96 1D-1

APPENDIX 1D

DLG-F Feature to DLG-3 Code Crosswalk


53/82


4/96 1D-2

The following table provides a guide to aid in the translation of

DLG-F features to DLG-3 codes. This table is intended only to

direct the user to the appropriate DLG-3 code and does not imply

that the code indicated is the correct code in all cases. The

user must rely on the DLG-3 documentation and the feature template

to determine the correct feature and its associated DLG-3 code.

This table is based on the 7/95 version of Part 3: Attribute

Coding of Standards for Digital Line Graphs.


54/82


4/96 1D-3

DLG-FFeatu

retoDLG-3CodeCrosswal

k

(H

ydrographyTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

AreaofComplex

Channels

050

0413

Braide

dStream

Areato

beSubm

erged

050

0108

Areat

o

beSubmerged

Bay/Inlet

Nocode

Bridge

050

0602

Overpa

ssing

170

0213

Footbr

idge

170

0001

Bridge

Abutment

170

0612

Double

-Decked

170

0618

OnDra

wbridge

170

0602

Overpa

ssing,OnBridge

180

0001

Bridge

Abutment

180

0611

OnDra

wbridge

180

0602

Overpa

ssing,OnBridge

Canal/Ditch

050

0414

Ditch

orCanal

050

0415

Aquedu

ctorPipeline

Connector

Nocode

CrevasseField

050

0411

Crevas

se

(Glacial)

Dam/Weir

050

0406

Damor

Weir

Estuary

050

0116

Bay,E

stuary,Gulf,Ocean,Sea

FishLadder

050

0425

FishL

adder

Foreshore

050

0115

Flats

(Tidal,Mud,Sand,orGrav

el)

Flume

050

0416

Flume

Fumarole

050

0304

Geyser

GagingStation

050

0403

Gaging

Station

Gate

050

0409

Gate

Geyser

050

0304

Geyser

HazardZone

050

0206

Limiti

ngDangerLine

050

0117

Shoal

050

0125

FoulG

round

050

0126

MineD

angerArea

050

0410

Rock

200

0467

Expose

dWreckorWreckage

200

0468

Sunken

Wreck

200

0465

Pile,

Dolphin,Stump,orSnag


55/82


4/96 1D-4

DLG-FFeatu


k

(H

ydrographyTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

IceMass

050

0103

Glacie

rorPermanentSnowfield

InundationArea

050

0119

DuckP

ond

050

0105

Inunda

tionArea

Lake/Pond

050

0421

Lakeo

rPond

LockChamber

050

0407

LockC

hamber

MileMarker

055----

River

MileMarker

MudPot

050

0304

Geyser

NonearthenShor

e

050

0201

Manmad

eShoreline

Pipeline

050

0417

Pensto

ck

050

0418

Siphon

050

0415

Aquedu

ctorPipeline

Playa

050

0100

Alkali

Flat

050

0421

Lakeo

rPond

(dry)

Post

200

0465

Pile,

Dolphin,Stump,orSnag

Rapids

050

0400

Rapids

Reef

050

0422

Reef

Reservoir

050

0101

Reserv

oir

050

0102

Covere

dReservoir

050

0104

SaltE

vaporator

050

0106

Aquacu

lturePond

050

0107

Indust

rialWaterImpoundment

050

0109

Sewage

DisposalPond

050

0110

Tailin

gsPond

050

0124

Filtra

tionPond

050

0118

SodaE

vaporator

200

0451

Swimmi

ngPool


56/82


4/01 1D-5

DLG-F

Feat

ure

to

DLG-3

Code

Crosswal

k

(

Hydrography

Theme)

DLG-F

Feature

DLG-3

Code

DLG-3

Definition

Rock

050

0410

Rock

Sea/Ocean

050

0116

Bay,E

stuary,

Gulf,

Ocean,

or

Sea

050

0122

Gut

Shoreline

050

0207

Appare

nt

Shoreline

Bridge

050

0203

Indefi

nite

Shoreline

050

0209

Low-Wa

ter

Line

050

0200

Shorel

ine

050

0605

Right

Bank

050

0606

LeftB

ank

Sink/Rise

050

0003

Sink

Snag/Stump

200

0465

Pile,

Dolphin,

Stump,

or

Snag

Sounding

Datum

Line

050

0208

Soundi

ng

Datum

Special

Use

Zon

e

050

0424

Spoil

Area,

Dredged

Area,

or

Dump

Area

Special

Use

Zon

e

Limit

No

code

Spillway

050

0408

Spillw

ay

Spring/Seep

050

0300

Spring

Stream/River

050

0413

Braide

d

Stream

050

0412

Stream

050

0420

Wash

Submerged

Strea

m

050

0412

Stream

(with

050

0612,

Submerged

or

Sunken

Swamp/Marsh

050

0111

Marsh,

Wetland,

Swamp,

or

Bog

050

0112

Mangro

ve

Area

Tunnel

050

0604

Tunnel

Underpass

050

0617

Underp

assing

050

0602

Overpa

ssing

Wash

050

0420

Wash

Water

Intake/Ou

tflow

050

0303

Riser

050

0405

Water

Intake

Watercourse

No

code

Waterfall

050

0401

Falls

Well

050

0302

Flowin

g

Well

050

0301

Nonflo

wing

Well


57/82


4/96 1D-6

DLG-FFeatu


k

(Tr

ansportationTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

AircraftFacili

ty

Nocode

Bridge

170

0213

Footbr

idge

170

0618

OnDra

wbridge

170

0602

Overpa

ssing,OnBridge

180

0611

OnDra

wbridge

180

0602

Overpa

ssing,OnBridge

Cul-De-Sac

170

0005

Cul-De

-Sac

DrawSpan

170

0007

Drawbr

idge

180

0007

Drawbr

idge

Ford

170

0606

Submer

gedor

inFord

Gate

170

0004

Gate

170

0403

Tollga

te

Helipad

190

0404

Helipa

d

Interchange

Nocode

Lane

170

0214

RoadF

erryCrossing

180

0207

Railro

adFerryCrossing

Monorail

190

0208

Monora

il

Railway

180

0201

Railro

ad

180

0202

Railro

ad

inRoad

180

0204

Carlin

e

180

0208

Railro

adSiding

180

0205

CogRa

ilroad,InclineRailway,o

r

Loggin

gTram

RailwayYard

180

0209

Railro

adYard

RestSite

200

0453

Recrea

tionArea,PublicUseArea


58/82


4/96 1D-7

DLG-FFeatu


k

(Tr

ansportationTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

Road

170

0402

Ramp

i

nInterchange

170

0203

Primar

yRoute,Class

1,Divided,

Lanes

Separated

170

0204

Primar

yRoute,Class

1,One-Way,

Other

ThanDividedHighway

170

0202

Primar

yRoute,Class

1,Symbol

Divide

d

byCenterline

170

0201

Primar

yRoute,Class

1,Symbol

Undivi

ded

170

0208

Second

aryRoute,Class

2,OneWa

y,

Other

ThanDividedHighway

170

0206

Second

aryRoute,Class

2,Symbol

Divide

d

byCenterline

170

0207

Second

aryRoute,Class

2,Symbol

Divide

d,LanesSeparated

170

0205

Second

aryRoute,Class

2,Symbol

Undivi

ded

170

0209

Road,

Class

3,SymbolUndivided

170

0218

Road,

Class

3,Divided,

Lanes

Separated

170

0221

Road,

Class

3,OneWay

170

0217

Road,

Class

3,Symbol

Divide

dCenterline

170

0210

Road,

Class

4

170

0219

Road,

Class

4,OneWay

170

0222

Road

i

nTransition

170

0223

Road

i

nServiceFacility,RestA

rea

170

0405

Nonsta

ndardSectionofRoad

170

0401

Traffi

cCircle

170

0212

Trail,

Class

5,Four-WheelDrive


59/82


4/96 1D-8

DLG-FFeatu


k

(Tr

ansportationTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

Route

Nocode

Runway/Apron/Ta

xiway

190

0403

Landin

gStrip,Runway,Apron,

Taxiwa

y

TrafficInspect

ionFacility

170

0404

Weigh

Station

Trail

170

0211

Trail

170

0605

Labele

d

"OldRailroadGrade"

Tunnel

170

0601

InTun

nel

180

0601

InTun

nel

TunnelEntrance

170

0002

Tunnel

Portal

180

0002

Tunnel

Portal

Turntable

180

0401

Turnta

ble

Underpass

170

0607

Underp

assing

180

0605

Underp

assing

170

0602

Overpa

ssing,OnBridge

180

0602

Overpa

ssing,OnBridge


60/82


4/96 1D-9

DLG-FFeat

uretoDLG-3CodeCrosswal

k

(

BoundariesTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

BoundaryLine

090

0202

Disput

edBoundary

090

0201

Indefi

nite

(orApproximate)Boun

dary

BoundaryLineo

rSurveyLine

090

0203

Histor

icalLine

BoundaryPoint

090

0001

Bounda

ryMonument

090

0301

Refere

nceMonument

forBoundary

City

090

0101

Incorp

oratedCity,Village,Town

,

Boroug

h,orHamlet

County

092

0---

County

orCountyEquivalentFIPS

Code

(

parameter)

MinorCivilDiv

ision

090

0100

Civil

Township,District,Precin

ct,

orBar

rio

Nation

090

0197

Canada

090

0198

Mexico

PointMonument

Nocode

Reservation

090

0150

Large

Park

(City,County,Privat

e)

090

0151

Small

Park

(City,County,Privat

e)

090

0134

Misc.

CountyReservation

090

0110

Federa

lPrison

090

0136

Hawaii

anHomestead

090

0107

Indian

Reservation

090

0108

Milita

ryReservation

090

0111

Miscel

laneousFederalReservatio

n

090

0129

Miscel

laneousStateReservation

090

0104

Nation

alForest

090

0103

Nation

alPark

090

0106

Nation

alWildernessArea

090

0132

State

Forest

090

0130

State

Park

Reservation

090

0133

State

Prison

090

0131

State

WildlifeArea

090

0105

Nation

alWildlifeArea

State/Territory

091

00--

State

orStateEquivalentFIPSC

ode

(param

eter)


61/82


4/96 1D-10

DLG-FFeatu


k

(PLSSTheme)

DLG-FFeature

DLG-3Code

DLG-3

Definition

LandGrant

300

0103

LandG

rant

300

0106

Overla

pping

landgrants

PointMonument

Nocode

PrincipalMerid

ian

Nocode

PublicLandSur

veySurveyArea

300

0110

PLSSA

rea

300

0108

Privat

esurvey

inOhio

300

0104

Privat

eextensionsofpublic

lan

d

survey

300

0105

Areao

fpublicandprivatesurve

y

overla

p

300

0102

Donati

on

landclaim

300

0111

Tract

SpecialSurvey

Area

300

0101

Homest

eadentrysurvey

300

0112

U.S.S

urvey

300

0113

Indian

allotment

SurveyCorner

300

0001

Found

PLSSsectioncorner

300

0004

Me

Documents

Part 1-Template Dvmnt