![](media/image1.jpeg){width="2.0in" height="1.992361111111111in"}

DOC/NOAA/NESDIS/NCDC

**Users Guide for NCDC Standard Template for FGDC Metadata**

**by Charles S. Phillips**

**February, 2004**

**Revised**

**August, 2005**

**Introduction:**

This *Users Guide* is designed to be used with *Guidelines for NCDC
Metadata.doc*, which lays the groundwork for creation and maintenance of
NCDC metadata. *Users Guide* describes the suggested way to use the
*NCDC Standard Template for FGDC Metadata.xml*, called \"template\"
here. The template is based on the most recent version of the core FGDC
Standards available at this writing, which is the \"Content Standard for
Digital Geospatial Metadata, FGDC-STD-001-1998.\" (All documents named
here are digital files.)

The template can be used to create a FGDC-compliant metadata record that
adequately documents a data set, data-related customer product, or other
data-related item that involves geospatial data. Almost any such item
can be documented with this template, including many that do not contain
geospatial data. If *Users Guide* is followed by a metadata writer who
has professional knowledge of both the item and the science involved,
the result will be a high-quality FGDC-compliant metadata record
suitable for import into the NOAA Metadata Manager Repository (NMMR).

This template will create adequate metadata for any geospatial data.
However, it should be noted that some geospatial data types, like
[remote sensing data]{.underline}, have their own approved extensions to
FGDC that are not included in this standard template. Better metadata is
possible for these types by using methods that take account of their
approved extensions.

**Overview of metadata writing:**

The template is a XML file, which consists of many XML tag pairs, also
called simply tags. The first tag pair is \<metadata\>\</metadata\>,
whose first part, \<metadata\>, is at the start of the template. The
second part, \</metadata\>, is far away, at the end of the template. All
other tags are enclosed by the \<metadata\>\</metadata\> tag pair. The
next tag after \<metadata\> is \<idinfo\>. Its second part, \</idinfo\>,
is some distance down into the template; many tag pairs are enclosed
between the \<idinfo\>\</idinfo\> tag pair. Many tags enclose other tags
in this way. Enclosing tags provide structure to the XML file and
support FGDC Standards compliance.

However, tags that \"stand alone\", that do not enclose other tags, is
where the metadata action is. The writer must make entries in those tags
to create a metadata record. In the template, both parts of stand-alone
tags are on the same line. They look like

\<pubtime\>\</pubtime\>

where the two parts of the tag are immediately adjacent, or like

\<origin\>1001 &&&\</origin\>

where the two parts are separated by a \"label\" (\"1001 &&&\" in this
example) that consists of a number followed by one, two, or three
ampersands (&).

Unlabeled stand-alone tags, like \<pubtime\>\</pubtime\> above, tend to
be of lesser importance and are often a source of unwanted complexity.
They are not discussed in *Users Guide* and normally should be ignored;
however, they remain in the template if the writer wishes to use them.

\"Labeled tags\" like \<origin\>1001 &&&\</origin\> are discussed in
*Users Guide*. These tags require action by the metadata writer. The
writer enters information by replacing the label with an entry, like
this:

\<origin\>1001 &&&\</origin\>

becomes

\<origin\>ENTRY\</origin\>

ENTRY may be a few characters or numbers, or a calendar date or time, or
it may be long text consisting of many lines. If a tag will not have an
entry, the writer may optionally delete its two parts.

The labeled tags described in *Users Guide* show three priorities:
mandatory, mandatory-if-applicable, and optional. The number of
ampersands (\"&\") in the labels indicate the priority:

&&& = mandatory

&& = mandatory if applicable

& = optional

Mandatory tags must contain entries.

Mandatory-if-applicable tags must contain entries if certain conditions
are met. Tags with this priority are widespread. Some are almost never
applicable; some are almost always applicable.

Optional tags do not require entries, but can be important sources of
information.

**Important Notes and Links:**

*Definitions:* In *Users Guide*, the word \"item\" will refer to
whatever is being documented. An item may be almost anything
data-related, including but not limited to a web page, paper manuscript,
customer product or service, and of course a data set. Other words:
\"User\" is a customer, researcher, or other person or organization that
may want to receive the item from a \"distributor\". \"Writer\" is a
metadata writer.

*Tools and their use:* *Users Guide* was written with the word processor
software Microsoft Word. *Users Guide* should be printed, or displayed
in a Word window, and should be reviewed while work in the template
proceeds. The metadata writer is strongly encouraged to use a text
editor program like Windows= built-in Notepad to work in the template,
which is a simple text file. Visual SlickEdit is a good commercial text
editor that is well suited to editing XML files.

*Approach:* The writer should gather information about the item to be
documented before starting to write. After that, the suggested approach
is to dive in and write. It is a task of many steps that is best taken
one step at a time. Each tag description tells the writer if other tags
need to be considered.

*FGDC Standards manual vs. tags:* *Users Guide* describes labeled tags
in the template that correspond to selected elements in FGDC Sections 1,
2, 5, 6, and 7. *Users Guide* is divided into the same numbered
Sections. The FGDC element number that each tag corresponds to is given
at the bottom of each tag description.

*Beware of loose labels:* Tag labels require action: A label must be
replaced by an entry, or the tag pair containing an unused label must be
deleted, or the label itself must be deleted.

*Unlabeled tags*: The metadata writer may use unlabeled tags in the
template if needed. However, unlabeled tags have not been tested in
NMMR.

*Tag and retag:* Always assume that a tag can be used no more than once,
unless the tag description says it is repeatable. Each tag pair occurs
only once in the template. But when a tag pair is repeatable, the writer
can make extra copies of the line containing the tag by using the
copy-and-paste feature of a text editor.

*Extra whitespace around tags:* NMMR generally ignores whitespace
characters such as spaces, tabs and carriage returns between a tag entry
and either part of its tag pair. Thus

\<tag\>ENTRY\</tag\>

is equivalent to

\<tag\>

ENTRY

\</tag\>

as far as NMMR is concerned. (These statements do not necessarily apply
to other software that accepts FGDC metadata in the form of XML files.)

*Oncoming obsolescence:* The writer should try to avoid entering
information that is soon to be obsolete. Names of people are an example:
At NCDC, people have historically been mobile in their projects, tasks,
and billets. Naming a NCDC person as a current contact may make a
metadata record obsolete in a short time.

*Standardized words and phrases:* A number of tag entries, such as names
of sensors, observing platforms, and keywords, are best taken from
standardized lists. These lists will be called thesauruses in this
*Users Guide*. At this writing, NOAA/NESDIS does not have its own
thesauruses. NASA=s Global Change Master Directory thesauruses are
recommended for NCDC metadata writers. Links can be found at

<http://gcmd.gsfc.nasa.gov/Resources/valids/keyword_list.html>

Thesauruses with links at the above site are: \"Science Keywords\",
\"Recent Science Keyword Changes\", \"Services Keywords\",
\"Chronostratigraphic Units\", \"Data Centers\", \"Locations\",
\"Projects\", \"Instruments\", and \"Platforms\". Some of these
thesauruses will be recommended in tag descriptions in *Users Guide* as
sources of standardized names.

*Big time savers:* The writer should make a personalized copy of the
template for writing metadata. If certain tags usually hold the same
information in each metadata record, pre-load these tags with the
information in the personalized copy. If certain tags are never used,
delete them. These steps can save considerable metadata writing time.

**FGDC Section 1: Identification Information**

**This section is mandatory. It cannot be left blank. Section 1
identifies, defines, and describes the item. In the template, Section 1
consists of all tags whose labels begin with 1(one). Make entries as
indicated below, starting with tag \"\<origin\>1001 &&&\</origin\>\".**

\<origin\>1001 &&&\</origin\>

Originator of the item

This tag is mandatory and must have an entry, even if inapplicable to
the item. The entry is free text. It is the formal long name of the
originator of the item. Replace label \"1001 &&&\" with an appropriate
originator, or use the word **Unknown**.

This tag must occur once; but it may be repeated any number of times.

If the item is available at NCDC, NCDC should be listed as an
originator. Other organizations that distribute the item, or that
created the item in approximately its present form, can also be listed.
For example, if AFCCC created the item, the entries should look like:

\<origin\>National Climatic Data Center, NESDIS, NOAA, U.S. Department
of Commerce \</origin\>

\<origin\>Air Force Combat Climatology Center, U.S. Air Force, U.S.
Department of Defense \</origin\>

These names are from the GCMD \"Data Centers\" thesaurus mentioned in
the *Standardized words and phrases* paragraph on page 5. The fact that
each example line wraps onto two lines because of its length is not
significant.

See also tag \<center\>1047 &&&\</center\>. That tag names one
originator, and uses the short form of a data center name.

\<origin\>1001 &&&\</origin\> corresponds to element 1.1 \> 8.1 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<pubdate\>1002 &&&\</pubdate\>

Publication Date

This tag is mandatory and must have an entry, if even inapplicable to
the item. It is the item=s publication date or release date. Replace
label \"1002 &&&\" with a date in the format YYYYMMDD. If the date is
unknown or not appropriate to the item, use **Unknown** or **Unpublished
material**.

\<pubdate\>1002 &&&\</pubdate\> corresponds to element 1.1 \> 8.2 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<title\>1004 &&&\</title\>

Title, also called Item Name

This tag is mandatory. The entry is free text. Replace label \"1004
&&&\" with a good Item Name.

Names should be descriptive, readable and consistent. Descriptive and
readable names tend to be of medium length. For example, a global
surface weather data set, collected by the old USSR from the Global
Telecommunications System, might be titled:

\<title\>USSR GTS Global Surface Meteorological Data\</title\>

Suppose there is an upper air data set that came to NCDC with the
surface data set. To provide a consistent name, the upper air data set
would be called:

\<title\>USSR GTS Global Upper Air Meteorological Data\</title\>

\<title\>1004 &&&\</title\> corresponds to element 1.1 \> 8.4 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<edition\>1005 &&\</edition\>

Edition

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item has a version number or edition number. The entry
is free text. Replace label \"1005 &&\" with the version or edition
description, which might be, for example, **1^st^ edition**, **Version
3**, etc.

\<edition\>1005 &&\</edition\> corresponds to element 1.1 \> 8.5 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<geoform\>1006 &&\</geoform\>

Geospatial Data Presentation Form

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item contains geospatial data. The entry is free text.
Replace the label \"1006 &&\" with a word or phrase that describes how
the data is presented, or choose one of the following: **atlas**,
**audio**, **diagram**, **document**, **globe**, **map**, **model**,
**multimedia presentation**, **profile**, **raster digital data**,
**remote-sensing image**, **section**, **spreadsheet**, **tabular
digital data**, **vector digital data**, **video**, or **view**.

\<geoform\>1006 &&\</geoform\> corresponds to element 1.1 \> 8.6 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<sername\>1007 &&\</sername\>

Series Name

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item is part of a series. The entry is free text. A
series is a succession of volumes or issues published with related
subjects or authors, similar format and price, or continuous numbering.
Replace the label \"1007 &&\" with the name of the series publication of
which the item is a part. Note that this tag is used with tag
\<issue\>1008 &&\</issue\> to identify a series.

\<sername\>1007 &&\</sername\> corresponds to element 1.1 \> 8.7.1 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<issue\>1008 &&\</issue\>

Series Issue Identification

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item is part of a series. The entry is free text. A
series is a succession of volumes or issues published with related
subjects or authors, similar format and price, or continuous numbering.
Replace the label \"1008 &&\" with information that identifies the
series publication of which the item is a part, such as an ISBN number.
Note that this tag is used with tag \<sername\>1007 &&\</sername\> to
identify a series.

\<issue\>1008 &&\</issue\> corresponds to element 1.1 \> 8.7.2 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<pubplace\>1009 &&\</pubplace\>

Publication Place

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item was published or released to the user community.
The entry is free text. Replace label \"1009 &&\" with the name of the
city where the item was published (and state or province, and country,
if needed to identify the city).

See also tags \<pubdate\>1002 &&&\</pubdate\> and \<publish\>1010
&&\</publish\>.

\<pubplace\>1009 &&\</pubplace\> corresponds to element 1.1 \> 8.8.1 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<publish\>1010 &&\</publish\>

Publisher

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if the item was published or released to the user community.
The entry is free text. Replace label \"1010 &&\" with the name of the
item=s publisher. If the publisher is a data center, use a name from the
thesaurus \"Data Centers\" mentioned in the *Standardized words and
phrases* paragraph on page 5.

See also tags \<pubdate\>1002 &&&\</pubdate\> and \<pubplace\>1009
&&\</pubplace\> for more about publishing.

\<publish\>1010 &&\</publish\> corresponds to element 1.1 \> 8.8.2 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<onlink\>1012 &\</onlink\>

Online Linkage

This tag is optional, but should be used. The entry is free text.
Replace label \"1012 &\" with the name of an online computer resource
that contains the item. The name of the computer resource should adhere
to the Uniform Resource Locator (URL) convention of the Internet.
\<Onlink\> may be repeated as many times as needed.

For items kept at NCDC, the home page of the NCDC web site is one URL
that should be listed in \<onlink\>. As an example, suppose we want to
list the NCDC site plus two additional URLs. This might look like:

\<onlink\>http://www.ncdc.noaa.gov\</onlink\>

\<onlink\>http://www.secondlocation.example\</onlink\>

\<onlink\>http://www.thirdlocation.example\</onlink\>

Note: The writer should first try to enter primary online computer
resources in tags \<moreinfo\>1050 &\</moreinfo\>, \<preview\>1051
&\</preview\>, and \<obtain\>1052 &\</obtain\>. \<Onlink\> is the place
to put secondary computer resources, additional primary computer
resources, or primary computer resources that do not fit the other
tags\' rather specific requirements.

\<onlink\>1012 &\</onlink\> corresponds to element 1.1 \> 8.10 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<origin\>1021 &&\</origin\>

\<pubdate\>1022 &&\</pubdate\>

\<title\>1024 &&\</title\>

\<edition\>1025 &&\</edition\>

\<geoform\>1026 &&\</geoform\>

\<sername\>1027 &&\</sername\>

\<issue\>1028 &&\</issue\>

\<pubplace\>1029 &&\</pubplace\>

\<publish\>1030 &&\</publish\>

\<onlink\>1032 &\</onlink\>

Tags 1021-1032 are used like tags 1001-1012, except that 1021-1032 are
used only to cite a larger work which contains the item and which must
be obtained to obtain the item (rare).

For example, a scientific paper is included in a publication, and the
paper is not readily available elsewhere. The publication is the larger
work that must be cited. If the paper is available from other sources,
the publication should not be cited.

Makes entries in tags 1021-1032 according to the instructions for
1001-1012, except that the 1021-1032 entries must describe the larger
work.

\<origin\>1021 &&\</origin\> corresponds to element 1.1 \> 8.11 \> 8.1
of the FGDC Standards.

\<pubdate\>1022 &&\</pubdate\> 1.1 \> 8.11 \> 8.2

\<title\>1024 &&\</title\> 1.1 \> 8.11 \> 8.4

\<edition\>1025 &&\</edition\> 1.1 \> 8.11 \> 8.5

\<geoform\>1026 &&\</geoform\> 1.1 \> 8.11 \> 8.6

\<sername\>1027 &&\</sername\> 1.1 \> 8.11 \> 8.7.1

\<issue\>1028 &&\</issue\> 1.1 \> 8.11 \> 8.7.2

\<pubplace\>1029 &&\</pubplace\> 1.1 \> 8.11 \> 8.8.1

\<publish\>1030 &&\</publish\> 1.1 \> 8.11 \> 8.8.2

\<onlink\>1032 &\</onlink\> 1.1 \> 8.11 \> 8.10

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<abstract\>1041 &&&\</abstract\>

Abstract

This tag is mandatory. The entry is free text. Replace label \"1041
&&&\" with a narrative summary of the item. This abstract is similar to
the abstract of a scientific paper.

An overview, not a detailed treatise, is what should be written. Detail
is reserved for other tags. What should be written in the abstract will
vary with the item, but here are some suggestions:

Item history.

Places represented by the item (e.g. data locations).

Physical phenomena represented by data in the item.

Item contents and how it was produced (names of algorithms, etc.).

Sensors, platforms and hardware (or software, as in a model) used to
collect data.

Significance of the item.

Item update plans and other plans.

This abstract can be as long as needed, but one typewritten page is a
good length. The writer should begin a new line after each line\'s
column 78 has been entered. Here is a sample abstract:

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

\<abstract\>

SOWM Hindcast Wind and Wave Climatology for North Pacific, North
Atlantic and Mediterranean is historical digital data set DSI-9786,
archived at the National Climatic Data Center (NCDC). It is a digital
ocean atlas.

SOWM is the Spectral Ocean Wave Model, a computer software methodology
which was developed by Dr. Willard J. Pierson and others and adopted in
December 1974 by what was then the U.S. Navy Fleet Numerical
Oceanography Center (FLENUMOCEANCEN). FLENUMOCEANCEN was a predecessor
of the current Fleet Numerical Meteorology and Oceanography Center
(FNMOC). SOWM is a computer-based procedure that produces a directional
variance spectrum at specified grid points that are a maximum of 180
nautical miles apart. This spectrum defines the sea surface at each grid
point through a two dimensional matrix (direction/frequency) of 12
directions and 15 frequency bands.

The David Taylor Naval Ship Research and Development Center (DTNSRDC), a
predecessor to the U.S. Naval Surface Warfare Center, Carderock Division
(NSWCCD), with Operations Research, Inc. (ORI), developed computer
programs to derive a number of numerical parameters from the SOWM
spectral wave data. The NCDC used many of the concepts from these
programs and others written by FLENUMOCEANCEN to devise a
parameterization program that was used for this atlas (DSI-9786).

This atlas contains climatological summaries for seven parameters: wind
speed and direction, wave height, wave direction, wave slope code, modal
wave period, and wave directionality. The first four parameters had
appeared in U.S. Navy climatologies. The latter three parameters had not
appeared, because they cannot be directly derived from visual
observations. However, they can be very important operating
considerations.

Ship rolling and stability is affected by the wave slope of higher
waves. Wave slope of a regular wave is defined as the ratio of wave
height to wave length.

The modal wave period is the period associated with the maximum wave
energy in the wave spectrum. Modal wave periods associated with
wavelengths of about 0.75 and 1.25 ship lengths (depending on ship
course and speed) can cause resonance pitching and heaving. The modal
wave is not necessarily equal to the wave period associated with the
higher of the two waves, the

sea or the swell as summarized in past U.S. Navy climatologies (U.S.
Navy, 1974).

Wave directionality is the uniformity of the direction of movement of
the waves. If the waves are all moving in a uniform direction, then the
directionality is one. When there is no preferred direction of wave
movement (a completely confused sea state), the directionality is zero.
Obviously, ship response and maneuverability can be affected by the
directional spread of the wave energy.

Data in this atlas are derived using winds and waves from the period
January 1973 to December 1982, i.e. 10 years.

\</abstract\>

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

\<abstract\>1041 &&&\</abstract\> corresponds to element 1.2.1 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<purpose\>1042 &&&\</purpose\>

Purpose

This tag is mandatory. The entry is free text. Replace label \"1320
&&&\" with an explanation of the purpose of the item. The purpose behind
many NCDC customer products is:

\<purpose\>

To make a wide range of climatic data available to researchers and the
public.

\</purpose\>

\<purpose\>1042 &&&\</purpose\> corresponds to element 1.2.2 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<supplinf\>1042.5 &&\</supplinf\>

Supplemental information

This tag is mandatory if applicable. The entry is free text. By
agreement with NASA\'s GCMD, in order to recognize data sets as distinct
from other data-related items, NCDC identifies its data sets by placing
the exact phrase **data set** in this tag. All letters are lower case,
and there is exactly one space between the word \"data\" and the word
\"set\". If the item is not a data set, this tag is optional (any
descriptive information may be placed here), or it may be left blank.

\<supplinf\>1042.5 &&\</supplinf\> corresponds to element 1.2.3 of the
FGDC standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<entry\>1043 &&&\</entry\>

Entry ID, also called FGDC Number

This tag is mandatory. At NCDC, it is the letter \"C\" followed by five
digits. \"C\" indicates \"NCDC\". Replace label \"1043 &&&\" with the
item\'s unique FGDC Number.

The FGDC Number is a required, unique identifier for everything
documented at NCDC. The FGDC numbers are assigned and managed centrally.
Obtain a FGDC Number by e-mail from metadata support in NCDC\'s Archive
Branch. At present, metadata support is Charles Phillips
([Charles.S.Phillips@noaa.gov]{.underline}).

Note: If an item is a product offered to customers through the product
catalog, the FGDC Number is the first 6 characters of the \"product
number\". The remainder is assigned by customer service.

\<entry\>1043 &&&\</entry\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<sensor\>1044 &\</sensor\>

Sensor

This tag is optional. The entry is free text. If data for the item was
collected using a sensor whose name is known, enter the name in place of
label \"1044 &\". The tag can repeated as many times as needed for
multiple sensors:

\<sensor\>AVHRR \> Advanced Very High Resolution Radiometer\</sensor\>

\<sensor\>AMPR \> Advanced Microwave Precipitation Radiometer\</sensor\>

It is recommended that the GCMD \"Instruments\" thesaurus noted in
*Standardized words and phrases* paragraph on page 5 be used for sensor
names, insofar as possible. A sensor name not taken from that thesaurus
should be technically correct, and/or should appear as it is known to
the scientific community.

\<sensor\>1044 &&&\</sensor\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<source\>1045 &\</source\>

Data Source

This tag is optional. The entry is free text. If data in the item was
collected on platforms or at locations that comprise a short list of
names (not an entire nationwide, observing station network, please!),
list them using this tag. Replace label \"1045 &\" with one name. If the
item contains modeled data, the model that created the data can be
entered in this tag. Repeat the tag as many times as needed for multiple
names:

\<source\>BAPMON \> Background Air Pollution Monitoring
Stations\</source\>

\<source\>C-MAN \> Coastal Marine Network\</source\>

\<source\>GOES-9 \> Geostationary Operational Environmental Satellite
9\</source\>

The names above were taken from the GCMD \"Platforms\" thesaurus
mentioned in *Standardized words and phrases* paragraph on page 5.

\<source\>1045 &\</source\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<campaign\>1046 &\</campaign\>

Campaign, also called Project

This tag is optional. The entry is free text. If the item was created
under a campaign or project, the project can be named here. Replace
label \"1046 &\" with one project name. This tag can be repeated as many
times as needed.

\<campaign\>AIRMON \> Atmospheric Integrated Research Monitoring
Network\</campaign\>

\<campaign\>BAPMON \> Background Air Pollution Monitoring
Stations\</campaign\>

The names above were taken from the GCMD \"Projects\" thesaurus
mentioned in *Standardized words and phrases* paragraph on page 5.
However, this is a NASA project thesaurus, and many NOAA projects may
not be listed.

\<campaign\>1046 &\</campaign\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<center\>1047 &&&\</center\>

Originating Center

This tag is mandatory. The entry is free text. It is the short-form name
of one originator of the item. If the item is available at NCDC, NCDC
should be used as the entry. Replace the label \"1047 &&&\" with the
name:

\<center\>DOC/NOAA/NESDIS/NCDC\</center\>

This name was taken from the \"Data Centers\" thesaurus mentioned in
*Standardized words and phrases* paragraph on page 5. That thesaurus
gives both long and short names for the data centers.

See also tag \<origin\>101 &&&\</origin\>, which uses the long name, but
is repeatable, allowing multiple originators.

IMPORTANT: When the item is a NVDS/NNDC Online Store customer product,
the name is required to end with \"/NNDC\", as in:

\<center\>DOC/NOAA/NESDIS/NCDC/NNDC\</center\>

\<center\>1047 &&&\</center\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<medium\>1048 &\</medium\>

Medium

This tag is optional. The entry is free text. If the item is distributed
using a specific storage medium or method such as CD-ROM, replace label
\"1048 &\" with the medium name. This tag can be repeated as many times
as needed.

\<medium\>CD-ROM\</medium\>

\<medium\>3 1/2 in. diskette\</medium\>

\<medium\>1048 &\</medium\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<reference\>1049 &\</reference\>

References

This tag is optional. The entry is free text. If bibliographic
references are available, replace label \"1049 &\" with them.

\<reference\>1049 &\</reference\> is part of a NOAA extension to the
FGDC Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<moreinfo\>1050 &\</moreinfo\>

\<preview\>1051 &\</preview\>

\<obtain\>1052 &&\</obtain\>

More Information, Preview, and Obtain URLs

\<Obtain\>: This tag is mandatory-if-applicable. It is applicable and
therefore mandatory if there is an online computer resource, such as a
web site, where a user can download or order (obtain) the item. The
entry is free text. Replace label \"1052 &&\" with the resource, in
Uniform Resource Locator (URL) format. This URL always exists for NCDC
Online Store products and must always be entered for these products.

\<Preview\>: This tag is optional. The entry is free text. If there is
an online computer resource where the item can be previewed before
obtaining, replace label \"1051 &\" with that URL.

\<Moreinfo\>: This tag is optional. The entry is free text. If there is
an online computer resource where more information is available about
the item, replace label \"1050 &\" with that URL.

To list secondary or additional URLs, use tag \<onlink\>1012
&\</onlink\>, a repeatable tag. If a URL is for a larger work that
contains the item (rare), use \<onlink\>1032 &\</onlink\>.

\<moreinfo\>1050 &\</moreinfo\>, \<preview\>1051 &\</preview\>, and
\<obtain\>1052 &&\</obtain\> are part of a NOAA extension to the FGDC
Standards. They are not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<onlsiz\>1053 &\</onlsiz\>

Online Size

This tag is optional. The entry is free text. If the item is accessible
via an online computer download, replace label \"1053 &\" with the size
and units of the file(s) that would be downloaded, such as

\<onlsiz\>36 Mb\</onlsiz\>

\<onlsiz\>1053 &\</onlsiz\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<parent\>1054 &\</parent\>

Parent FGDC Record

This tag is optional. See tags 1021-1032 concerning a larger work
citation. If there are entries in those tags and the larger work is also
a documented item (rare), replace label \"1054 &\" with the larger
work=s FGDC number (from its tag \<entry\>1043 &&&\</entry\>).
\<Parent\> can be repeated as many times as necessary.

\<parent\>1054 &\</parent\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<assocprd\>1055 &\</assocprd\>

Associated Products, also called Associated Items

This tag is optional. The entry is free text. Enter another documented
item, if any, that is related to or associated with the current item in
a significant way. Do this by replacing label \"1055 &\" with the other
item=s FGDC number (from tag \<entry\>1043 &&&\</entry\>).

The writer must decide what is a \"significant\" association between
items.

As an example of a clearly significant association, consider a surface
meteorological data set that requires a station information data set to
identify where and under what conditions the data was observed. There is
clearly a strong relationship between the two data sets, because the
surface meteorological data set cannot be used without the station
information data set. Both data sets need to be documented items. In the
\<assocprd\> tag for the surface meteorological data set, the station
information data set\'s FGDC number would be entered, and vice-versa.

\<Assocprd\> is repeatable as needed for additional documented items
that are associated with the current item.

\<assocprd\>1055 &\</assocprd\> is part of a NOAA extension to the FGDC
Standards. It is not found in the regular FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<caldate\>1071 &&\</caldate\>

\<time\>1072 &\</time\>

Multiple-Event Calendar Dates and Times

These two tags allow the writer to document the calendar dates and,
optionally, the times, of a limited number of separate events that are
relevant to the item. These tags are intended for multiple, not single,
events.

\<Caldate\> is mandatory-if-applicable. It is applicable and therefore
mandatory if the item is associated with a small number of separate
events. Replace label \"1071 &&\" with the calendar date of one event,
using the YYYYMMDD format.

\<Time\> is optional. It is a 24-hour clock time. To use, replace label
\"1072 &\" with the time of one event, using the HHMMSSSS or HHMMSSSSZ
format. SSSS is seconds to the nearest tenth or hundredth. Z indicates
Universal Time.

Both tags appear only once in the template, enough for one event. The
writer should use the text editor\'s copy-and-paste capability to create
a new \<caldate\> and \<time\> for each separate event. \<Caldate\> must
have a calendar date entered for each event, but \<time\> is optional.

An example sequence for three events might be:

\<caldate\>19080115\</caldate\>

\<time\>\</time\>

\<caldate\>19151130\</caldate\>

\<time\>180000\</time\>

\<caldate\>19980201\</caldate\>

\<time\>023000\</time\>

Note in the example that \<time\> in the first event is blank; this
means that the time associated with the first \<caldate\> is
unimportant, unknown or irrelevant. (The label was removed from this
\<time\>. More correctly, the entire \<time\>\</time\> line could have
been deleted.) The other two times are given.

Do not use these tags for a single event, nor for a huge number of
events. Instead, use tags \<begdate\>1073 &&&\</begdate\>,
\<begtime\>1074 &\</begtime\>, \<enddate\>1075 &\</enddate\>, and
\<endtime\>1076 &\</endtime\> for those cases.

\<caldate\>1071 &&\</caldate\> corresponds to element 1.3 \> 9.2 \>
9.1.1 of the FGDC Standards.

\<time\>1072 &\</time\> 1.3 \> 9.2 \> 9.1.2.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<begdate\>1073 &&&\</begdate\>

\<begtime\>1074 &\</begtime\>

Begin Date and Begin Time

\<Begdate\> is mandatory and must contain an entry, even if it is
irrelevant to the item. The entry is a calendar date using the format
YYYYMMDD, or the word **Unknown**. \<Begdate\> is the earliest date
associated with the item. The writer should replace label \"1073 &&&\"
with the date, or with **Unknown** if a date is unknown or inapplicable.

\<Begtime\> is optional. It is a 24-hour clock time using the HHMMSSSS
or HMMSSSSZ format. SSSS is seconds to the nearest tenth or hundredth. Z
indicates Universal Time. \<Begtime\> is the time of day associated with
calendar date \<begdate\>. Replace label \"1074 &\" with a clock time
associated with the calendar date in \<begdate\>.

The begin date and time (\<begdate\> and \<begtime\>) must be earlier
than, or the same as, the end date and time (tags \<enddate\>1075
&&&\</enddate\> and \<endtime\>1076 &\</endtime\>).

\<begdate\>1073 &&&\</begdate\> corresponds to element 1.3 \> 9.3.1 of
the FGDC Standards. \<begtime\>1074 &\</begtime\> 1.3 \> 9.3.2.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<enddate\>1075 &&&\</enddate\>

\<endtime\>1076 &\</endtime\>

End Date

\<Enddate\> is mandatory and must contain an entry, even if it is
irrelevant to the item. The entry is a calendar date using the format
YYYYMMDD, or one of the words **Present** or **Unknown**. \<Enddate\> is
the latest date associated with the item. Replace label \"1075 &&&\"
with the date, or with **Unknown** if the date is unknown or
inapplicable. If the latest date is the ever-moving present day, replace
the label with **Present**.

\<Endtime\> is optional. It is the time of day associated with calendar
date \<enddate\>. Use a 24-hour clock time in the HHMMSSSS or HHMMSSSSZ
formats. SSSS is seconds to the nearest tenth or hundredth. Z indicates
a Universal Time. Replace label \"1076 &\" with the clock time.

The end date and time (\<enddate\> and \<endtime\>) must be the same as,
or later than, the begin date and time (tags \<begdate\>1073
&&&\</begdate\> and \<begtime\>1074 &\</begtime\>).

\<enddate\>1075 &&&\</enddate\> corresponds to element 1.3 \> 9.3.3 of
the FGDC Standards. \<endtime\>1076 &\</endtime\> 1.3 \> 9.3.4.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<current\>1201 &&&\</current\>

Currentness Reference

This tag is mandatory. The entry is free text. The intent of this tag is
to describe what kind of events the dates and times entered in other
tags actually represent. Replace label \"1201 &&&\" with **Ground
condition** or **Publication date**, or free text, as explained below.

Choose **Ground condition** if calendar dates and times are when
observations were taken. This also applies to modeled data that
approximates real data for the dates and times. Most NCDC items will
probably use this choice.

**Publication date** indicates that calendar dates and times are
publication dates, release dates, or dates when data was keyed, or
otherwise entered into a storage system. Thus the data in the item is
older than the dates and times seem to imply.

If there is a different (short) description of nature of the dates and
times, enter it instead of the above choices. **Unknown** is a
possibility.

Armed with the information from this tag, the user will have a better
idea of how current the item really is.

\<current\>1201 &&&\</current\> corresponds to element 1.3.1 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<progress\>1202 &&&\</progress\>

Progress, also called Completeness

This tag is mandatory. It says how complete the item is. Replace label
\"1202 &&&\" with one of these three choices: **Complete**, **In work**,
or **Planned**.

**In work** describes an item to which more data is regularly added, or
which is updated at periodic intervals. (The same name, FGDC Number,
version or edition number, etc. must be used after the addition or
update.) An example is an ongoing data set like DSI-3200.

**Complete** describes an item that there are no plans to update or
modify. An example is a historical, static data set like the Maury
collection of ship observations.

**Planned** is for an item that is in the planning stages.

\<progress\>1202 &&&\</progress\> corresponds to element 1.4.1 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<update\>1203 &&&\</update\>

Maintenance and Update Frequency of Item

This tag is mandatory. The entry is free text. The entry says how often
the item will be updated or maintained following its initial appearance.
Replace label \"1203 &&&\" with an appropriate, brief, free text entry,
or choose one of the following words or phrases: **Continually**,
**Daily**, **Weekly**, **Monthly**, **Annually**, **Unknown**, **As
needed**, **Irregular**, or **None planned**.

\<update\>1203 &&&\</update\> corresponds to element 1.4.2 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<westbc\>1205 &&&\</westbc\>

\<eastbc\>1206 &&&\</eastbc\>

\<northbc\>1207 &&&\</northbc\>

\<southbc\>1208 &&&\</southbc\>

Westernmost, Easternmost, Northernmost, and Southernmost Bounding
Coordinates

These tags are mandatory and must contain entries, even if irrelevant to
the item. The entries are floating-point numbers, with decimal points,
that represent longitude (\<westbc\> and \<eastbc\>) and latitude
(\<northbc\> and \<southbc\>) in degrees and decimal fractions of a
degree. The four coordinates define a the four sides of a \"rectangle\"
on the Earth=s surface that encloses all territory relevant to the item.
In other words, the \"rectangle\" encloses the data occurrence zone.

\<Westbc\> marks the westernmost occurrence of data. No data occurs west
of \<westbc\>. \<Eastbc\>, \<northbc\>, and \<southbc\> are the
easternmost, northernmost, and southernmost data occurrence boundaries,
respectively.

\<Westbc\> and \<eastbc\> must be in the range of values -180.0 to 180.0
inclusive, where -180.0 and 180.0 represent the same longitude line
running from Pole to Pole through the middle of the Pacific Ocean.
Negative values represent the western hemisphere, and positive values
represent the eastern. Replace labels \"1205 &&&\" and \"1206 &&&\" with
appropriate floating-point numbers.

\<Northbc\> and \<southbc\> must be in the range of values -90.0 to 90.0
inclusive, where -90.0 and 90.0 are the South and North Poles,
respectively. Negative numbers represent the southern hemisphere, and
positive numbers represent the northern. \<Northbc\> must be equal to or
greater than \<southbc\>. Replace labels \"1207 &&&\" and \"1208 &&&\"
with appropriate floating-point numbers.

Number of decimal places: If the writer uses latitudes and longitudes
that do not coincide with any data but are general boundaries, one
decimal place containing a zero (0) is suggested. For example, 72.0.
General boundaries are the suggested entries. If data occurrence
locations are used, one decimal place containing a zero (0) is also
recommended for locations that are known to the nearest whole degree.
For locations known to the nearest minute, use at least three decimal
places. For example, -56.124. For locations known to the nearest second,
use at least five decimal places. For example, 137.45712.

If the data are global, or if latitude and longitude are irrelevant to
the item, the writer should use the default global values:

\<westbc\>-180.0\</westbc\>

\<eastbc\>180.0\</eastbc\>

\<northbc\>90.0\</northbc\>

\<southbc\>-90.0\</southbc\>

\<westbc\>1205 &&&\</westbc\> corresponds to element 1.5.1.1 of the FGDC
Standards.

\<eastbc\>1206 &&&\</eastbc\> 1.5.1.2

\<northbc\>1207 &&&\</northbc\> 1.5.1.3

\<southbc\>1208 &&&\</southbc\> 1.5.1.4

*Note: The FGDC Standards provide an optional method of defining
irregular closed polygons around data occurrence locations. A polygon is
defined by a sequence of latitude-longitude pairs in connect-the-dots
order, beginning and ending with the same pair. Data exclusion polygons
are also provided for. However, accurate polygons take more time to
prepare than a \"rectangle\", and their value to the user is open to
debate. Please note that the polygon cannot replace the \"rectangle\";
\"rectangle\" is unconditionally mandatory. If there is interest in the
polygon method, an description can be placed in an appendix of this
Users Guide.*

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<theme\>

\<themekt\>1301 &&&\</themekt\>

\<themekey\>1302 &&&\</themekey\>

\</theme\>

Theme Keyword

This is one of many tag groups in the template. It is bounded by the
enclosing tag pair \<theme\>\</theme\>. In this discussion, the word
\"group\" will refer to this Theme Keyword tag group. The enclosed tags
\<themekt\> and \<themekey\> can appear only inside the group, and
nowhere else.

One instance of the Theme Keyword group is mandatory. The group can be
repeated as needed.

\<Themekt\> (Theme Keyword Thesaurus) is mandatory and must occur
exactly once in each instance of the group. \<Themekt\> contains the
name of a thesaurus from which keywords are selected. Replace label
\"1301 &&&\" with the name of a thesaurus. The group can contain
keywords from this thesaurus, only.

\<Themekey\> (Theme Keyword) is mandatory and must occur one or more
times in each instance of the group. Each \<themekey\> contains one
keyword from the thesaurus named in \<themekt\>. Replace label \"1302
&&&\" with one theme keyword.

*Keywords are used in computerized search methods that a user might
employ to locate information about the documented item. Keywords should
come from standardized lists of keywords that here are called
\"thesauruses\".*

There must be a separate Theme Keyword group for each thesaurus. Theme
Keywords from at least 3 of the following 4 thesauruses should be
included in any NCDC metadata. See the notes for details.

\(1\) ISO 19115 Topic Category -- Every metadata record should include
this group of keywords. A web version of the thesaurus was not found,
but a copy is in Appendix A, \"ISO 19115 Topic Category Keywords\".

Suppose that a writer decides that the keyword
\"ClimatologyMeteorologyAtmosphere, 004\" fits the documented item. Then
the Theme Keyword group should look like:

\<theme\>

\<themekt\>19115 Topic Category\</themekt\>

\<themekey\>ClimatologyMeteorologyAtmosphere\</themekey\>

\<themekey\>004\</themekey\>

\</theme\>

\(2\) DIF Scientific Disciplines -- Every metadata record should include
these. These keywords are the branches of science (scientific
disciplines) that are represented by the documented item. A simple and
useful thesaurus for this purpose is the DIF Discipline Keyword
thesaurus. DIF is Directory Interchange Format, which is an older
metadata content and format standard. It is still used by NASA for
metadata in its Global Change Master Directory (GCMD). There are DIF
manuals available, such as various versions of the Directory Interchange
Format Manual published by NASA-Goddard. It is suggested that NCDC use
the \"Earth Sciences\" section of the Discipline thesaurus, which is
short. Here it is in its entirety:

Earth Sciences \> Atmosphere

Earth Sciences \> Interior and Crust

Earth Sciences \> Land

Earth Sciences \> Ocean

The above thesaurus has two levels of names separated by a right angle
bracket (\>). Each represents a generalized scientific discipline.
Additional levels can be added to a generalized discipline that makes
the discipline more specific. Here is a list of more specific scientific
disciplines that NCDC writers might use. It also illustrates the layout
of the group:

\<theme\>

\<themekt\>DIF Discipline Keyword Thesaurus\</themekt\>

\<themekey\>Earth Sciences \> Atmosphere \> Meteorology\</themekey\>

\<themekey\>Earth Sciences \> Atmosphere \> Weather\</themekey\>

\<themekey\>Earth Sciences \> Atmosphere \> Climatology\</themekey\>

\<themekey\>Earth Sciences \> Atmosphere \>
Paleoclimatology\</themekey\>

\<themekey\>Earth Sciences \> Land \> Hydrology\</themekey\>

\<themekey\>Earth Sciences \> Land \> Forestry\</themekey\>

\<themekey\>Earth Sciences \> Land \> Agriculture\</themekey\>

\<themekey\>Earth Sciences \> Land \> Geology\</themekey\>

\<themekey\>Earth Sciences \> Land \> Snow and Ice\</themekey\>

\<themekey\>Earth Sciences \> Ocean \> Oceanography\</themekey\>

\<themekey\>Earth Sciences \> Ocean \> Marine Biology\</themekey\>

\<themekey\>Earth Sciences \> Ocean \> Snow and Ice\</themekey\>

\</theme\>

The writer should choose from the list only those disciplines that are
relevant to the item.

\(3\) Data Parameters -- When the item includes data, the metadata
should include these keywords. The suggested thesaurus for parameters is
the GCMD \"Science Keywords\" thesaurus, mentioned in the *Standardized
words and phrases* paragraph on page 5. The full name of the thesaurus
is \"GCMD Sciences Keyword Valids\". This is a large thesaurus.
Downloading a copy of it, and keeping the copy current, is a good
approach.

Consider an example item: The data consists of daily maximum and minimum
temperatures and daily precipitation totals from surface meteorological
stations. The group might look like this.

\<theme\>

\<themekt\>GCMD Sciences Keyword Valids\</themekt\>

\<themekey\>Earth Science \> Atmosphere \> Atmospheric Temperature \>
Maximum/Minimum Temperature \> Daily Maximum Temperature\</themekey\>

\<themekey\>Earth Science \> Atmosphere \> Atmospheric Temperature \>
Maximum/Minimum Temperature \> Daily Minimum Temperature\</themekey\>

\<themekey\>Earth Sciences \> Atmosphere \> Precipitation \>
Precipitation Amount \> Daily Precipitation Total\</themekey\>

\</theme\>

(Microsoft Word wrapped the keywords in the above example onto two lines
apiece. NMMR ignores this. But the wrap makes keywords hard for a person
to read. If the writer uses a text editor, automatic line wrap does not
occur.)

In each parameter keyword in the above example, the first four levels
(everything in the keywords before \"Daily\") comprise a parameter taken
directly from the thesaurus. Thesaurus parameters are mostly general.
Fifth level is an optional specific parameter name (e.g. \"\> Daily
Maximum Temperature\"). In a few cases, thesaurus parameters are
specific enough that this optional parameter name may not be needed. To
maintain consistency, an optional parameter should always look the same,
each time the writer uses it.

\(4\) Service keywords -- When a documented item is primarily a service,
the metadata should include these keywords. The GCMD \"Earth Sciences
Services\" keywords thesaurus, mentioned in the *Standardized words and
phrases* paragraph on page 5, can be useful. Consider the following
example of these keywords, which describes a service such as CLIMVIS.

\<theme\>

\<themekt\>GCMD Earth Science Services Keywords Valids\</themekt\>

\<themekey\>EARTH SCIENCE SERVICES \> Data Analysis And Visualization \>
Visualization/Image Processing\</themekey\>

\</theme\>

\<themekt\>1301 &&&\</themekt\> corresponds to element 1.6.1.1 of the
FGDC Standards.

\<themekey\>1302 &&&\</themekey\> 1.6.1.2.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<place\>

\<placekt\>1303 &&\</placekt\>

\<placekey\>1304 &&\</placekey\>

\</place\>

Place Keyword

This is one of many tag groups in the template. It is bounded by an
enclosing tag, \<place\>\</place\>. In this discussion, the word
\"group\" will refer to this Place Keyword tag group. The tags
\<placekt\> and \<placekey\> can appear only inside the group, and
nowhere else. Place Keywords are typically names of physical and
political features on the Earth\'s surface. Place Keywords are
horizontally-oriented locations.

The Place Keyword group is optional. The group can be repeated as many
times as needed. Where entries are made, use free text.

\<Placekt\> (Place Keyword Thesaurus) is mandatory-if-applicable. It is
applicable if the group occurs. \<Placekt\> occurs exactly once in one
group and is the name of one thesaurus of location names from which all
place keywords in this group are selected. Replace \"1303 &&\" with the
name of the thesaurus.

\<Placekey\> (Place Keyword) is mandatory-if-applicable in the same
sense as \<placekt\> and must occur at least once. But it may be
optionally repeated in one group as many times as needed. Replace each
\"1304 &&\" with one place keyword from the thesaurus named in
\<placekt\>. Place keywords from other thesauruses may not be used in
the same group.

One Place Keyword group is suggested for NCDC metadata. The suggested
thesaurus is \"Locations\", mentioned in the *Standardized words and
phrases* paragraph, page 5. NASA calls this thesaurus \"GCMD Location
Valids\". The writer should download a copy and keep it current.

Consider an item that includes global sea surface temperatures. Then the
group might look like:

\<place\>

\<placekt\>GCMD Location Valids\</placekt\>

\<placekey\>Global Ocean\</placekey\>

\</place\>

All of the world=s oceans and most of the seas, bays, and major lakes
are in the thesaurus. These could certainly have been entered in the
above example, but it would have been a long task. Instead, the single
keyword \"Global Ocean\" was chosen in the hope that search software may
use a special search when the word \"Global\" is found. (The thesaurus
also includes \"Global Land\" and \"Global\".)

As another example, consider an item that includes data from the 50
United States:

\<place\>

\<placekt\>GCMD Location Valids\</placekt\>

\<placekey\>North America\</placekey\>

\<placekey\>United States of America\</placekey\>

\<placekey\>Polar\</placekey\>

\<placekey\>Mid-latitude\</placekey\>

\<placekey\>Hawaiian Islands\</placekey\>

\</place\>

The thesaurus does not list the U. S. states. States can be put on the
end of \"United States of America\" keywords if desired:

\<placekey\>United States of America \> Alabama\</placekey\>

\<placekey\>United States of America \> Mississippi\</placekey\>

\<placekey\>United States of America \> Tennessee\</placekey\>

etc.

A few keywords at the end of the \"Locations\" thesaurus are
vertically-oriented locations (e.g. \"Ionosphere\"). These should not be
used here, since the place keyword is a horizontally-oriented location.
For vertically-oriented location tags, see the tag group
\<stratum\>\<stratkt\>1305 && \</stratkt\>\<stratkey\>1306
&&\</stratkey\>\</stratum\>.

\<placekt\>1303 &&\</placekt\> corresponds to element 1.6.2.1 of the
FGDC Standards.

\<placekey\>1304 &&\</placekey\> 1.6.2.2.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<stratum\>

\<stratkt\>1305 &&\</stratkt\>

\<stratkey\>1306 &&\</stratkey\>

\</stratum\>

Stratum Keyword

This is one of several tag groups in the template. It is bounded by an
enclosing tag, \<stratum\>\</stratum\>. In this discussion, the word
\"group\" will refer to this Stratum Keyword tag group. The tags
\<stratkt\> and \<stratkey\> can appear only inside the group, and
nowhere else. Stratum Keywords are typically names of
vertically-oriented locations above, on, and below the Earth\'s surface.

The Stratum Keyword group is optional. It may be repeated as many times
as needed.

\<Stratkt\> (Stratum Keyword Thesaurus) is mandatory-if-applicable. It
is applicable and therefore mandatory when the group occurs. \<Stratkt\>
must occur exactly once in a group. It is the name of a thesaurus from
which all stratum keywords in this occurrence of the group are selected.
Replace label \"1305 &&\" with the name of a thesaurus.

\<Stratkey\> (Stratum Keyword) is mandatory-if-applicable in the same
sense as \<stratkt\>. It must occur at least once in a group, but it may
be optionally repeated as many times as needed. Replace label \"1306
&&\" with one stratum keyword from the thesaurus named in \<stratkt\>.
Stratum keywords from other thesauruses may not be used in one group.

The group can optionally be repeated as many times as needed in order to
include stratum keywords from different thesauruses.

One group of Stratum Keywords is suggested for NCDC metadata. The
suggested thesaurus is \"Locations\", mentioned in the *Standardized
words and phrases* paragraph, page 5. NASA calls this thesaurus \"GCMD
Location Valids\". Most of the keywords in this thesaurus are place
keywords (horizontal locations). But there is a small group of useful
stratum keywords near the bottom.

As an example, consider an item that includes buoy data consisting of
sea surface temperature, wave data, air temperature, and winds. Then the
stratum keyword group may look like:

\<stratum\>

\<stratkt\>GCMD Location Valids\</stratkt\>

\<stratkey\>Sea Surface\</stratkey\>

\<stratkey\>Troposphere\</stratkey\>

\</stratum\>

\<stratkt\>1305 &&\</stratkt\> corresponds to element 1.6.3.1 of the
FGDC Standards.

\<stratkey\>1306 &&\</stratkey\> 1.6.3.2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<temporal\>

\<tempkt\>1307 &&\</tempkt\>

\<tempkey\>1308 &&\</tempkey\>

\</temporal\>

Temporal Keyword

This is one of several tag groups in the template. It is bounded by an
enclosing tag, \<temporal\>\</temporal\>. In this discussion, the word
\"group\" will refer to this Temporal Keyword tag group. The tags
\<tempkt\> and \<tempkey\> can appear only inside the group, and nowhere
else. Temporal Keywords are typically names of times or time periods.

The Temporal Keyword group is optional. It may be repeated as many times
as needed.

\<Tempkt\> (Temporal Keyword Thesaurus) is mandatory-if-applicable. It
is applicable and therefore mandatory when the group occurs. \<Tempkt\>
must occur exactly once in each group. Replace label \"1307 &&\" with
the name of a thesaurus from which all temporal keywords in this
occurrence of the group are selected.

\<Tempkey\> (Temporal Keyword) is mandatory-if-applicable when the group
occurs. It must appear at least once in each group, but it may be
optionally repeated as many times as needed. Replace label \"1308 &&\"
with one temporal keyword from the thesaurus named in \<tempkt\>.
Temporal keywords from other thesauruses may not be used in one group.

One thesaurus for temporal keywords refers to the geologic time scale.
It is \"Chronostratigraphic Units\" and is mentioned in *Standardized
word and phrases* section, page 5. NASA calls the thesaurus \"GCMD
Chronostratigraphic Unit Valids\". Here is the complete thesaurus:
\"Archaen\", \"Cambrian\", \"Carboniferous\", \"Cenozoic\",
\"Cretaceous\", \"Devonian\", \"Eocene\", \"Holocene\", \"Jurassic\",
\"Mesozoic\", \"Miocene\", \"Mississippian\", \"Neogene\",
\"Oligocene\", \"Ordovician\", \"Paleocene\", \"Paleogene\",
\"Paleozoic\", \"Pennsylvanian\", \"Permian\", \"Pleistocene\",
\"Pliocene\", \"Precambrian\", \"Proterozoic\", \"Quaternary\",
\"Silurian\", \"Tertiary\", and \"Triassic\".

This thesaurus is not recommended for data related to recent events,
such as meteorological data.

\<tempkt\>1307 &&\</tempkt\> corresponds to element 1.6.4.1 of the FGDC
Standards.

\<tempkey\>1308 &&\</tempkey\> 1.6.4.2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<accconst\>1901 &&&\</accconst\>

Access Constraints

This tag is mandatory and must have an entry, even if irrelevant to the
item. The entry is free text. Replace label \"1901 &&&\" with an
explanation of any restrictions and legal perquisites for accessing the
item. This includes any access constraints applied to assure the
protection of privacy or intellectual property, and any special
restrictions or limitations on obtaining the item. Or, enter **None**.
At NCDC, **None** is the most likely entry.

\<accconst\>1901 &&&\</accconst\> corresponds to element 1.7 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<useconst\>1902 &&&\</useconst\>

Use Constraints

This tag is mandatory and must have an entry, even if irrelevant to the
item. The entry is free text. Replace label \"1902 &&&\" with an
explanation of any restrictions and legal perquisites for using the item
after access is granted. These include any use constraints applied to
assure the protection of intellectual property, and any special
restrictions or limitations on using the item. Or, enter **None**. At
NCDC, **None** is the most likely entry.

\<useconst\>1902 &&&\</useconst\> corresponds to element 1.8 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntorg\>1904 &\</cntorg\>

Contact Organization (for technical contact)

This tag is optional. The entry is free text. Replace label \"1904 &\"
with the name of the organization that can be contacted for more
technical information about the data, if one is known. If NCDC is the
technical contact organization, this tag and all following tags dealing
with technical contact can be ignored, since NCDC is mentioned
plentifully elsewhere.

The need for a technical contact other than NCDC arises because NCDC
archives many items that were prepared elsewhere. NCDC may know little
about the item, except what is in the (often sparse) documentation that
came with it.

\<cntorg\>1904 &\</cntorg\> corresponds to element 1.9 \> 10.2 \> 10.1.2
of the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntper\>1905 &\</cntper\>

Contact Person (for technical contact)

This tag is optional. The entry is free text. Use this tag if there is
only person at the organization named in tag \<cntorg\>1904 &\</cntorg\>
who can serve as technical contact. Replace the label \"1905 &\" with
the person\'s name.

\<cntper\>1905 &\</cntper\> corresponds to element 1.9 \> 10.2 \> 10.1.1
of the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntpos\>1908 &\</cntpos\>

Contact Position (for technical contact)

This tag is optional. The entry is free text. Replace label \"1908 &\"
with the position description or job title of a person at the
organization named in tag \<cntorg\>1904 &&\</cntorg\> who can be the
technical contact. A few possible entries are **Principal
Investigator**, **Customer Service**, **Research Scientist, Flight
Director,** etc.

\<cntpos\>1908 &\</cntpos\> corresponds to element 1.9 \> 10.3 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntaddr\>

\<addrtype\>1926 &&\</addrtype\>

\<address\>1927 &\</address\>

\<city\>1928 &&\</city\>

\<state\>1929 &&\</state\>

\<postal\>1930 &&\</postal\>

\<country\>1931 &\</country\>

\</cntaddr\>

Address (for technical contact)

This is an optional tag group, and contains address(es) of the
organization named in tag \<cntorg\>1904 &&\</cntorg\>. If no
organization is named, this tag group should not be used. In this
description, the word \"group\" will be used to refer to this tag group.

This group is optional, and may be repeated as many times as necessary.
Each group contains one address of the organization named in \<cntorg\>.

\<Addrtype\> is Address Type. It is mandatory-if-applicable. It is
applicable and therefore mandatory when the group occurs. The entry is
free text. Replace label \"1926 &&\" with the kind of address.
Possibilities are: **Mailing** if the address is a mailing address but
is not where the organization is located, such as a post office box.
**Physical** if the address is where the organization is physically
located, but is not a mailing address. **Mailing and physical** if the
address is both a mailing address and the organization\'s physical
location. Or, use free text to describe the address if none of the above
three choices are appropriate. **Mailing and physical** is the best
choice for NCDC at Asheville. There can be both on-site and post office
box mailing addresses; then at least two occurrences of the group, one
for each address and its type, are required.

\<Address\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs and when there is an organization name,
street address, or post office box number in the address. Replace label
\"1927 &&\" with one piece of that information . \<Address\> is
repeatable inside one group to allow for multiple lines. Typically, this
tag might appear twice, once for the organization name and once for the
street address or post office box number. A room number can go after the
street address on the same line, or in a third occurrence of
\<address\>.

\<City\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"1928 &&\" with the name
of a city, town, or municipality in the address.

\<State\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"1929 &&\" with the name
of the U. S. state, Canadian province, or similar political entity in
the address.

\<Postal\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"1930 &&\" with an
appropriate postal code for the address. For the U. S., it would be a
zip code.

\<Country\> is optional. Replace label \"1931 &\" with the name of the
appropriate country. For the U. S., **USA** is suggested.

\<addrtype\>1926 &&\</addrtype\> corresponds to element 1.9 \> 10.4.1 of
the FGDC Standards.

\<address\>1927 &\</address\> 1.9 \> 10.4.2

\<city\>1928 &&\</city\> 1.9 \> 10.4.3

\<state\>1929 &&\</state\> 1.9 \> 10.4.4

\<postal\>1930 &&\</postal\> 1.9 \> 10.4.5

\<country\>1931 &\</country\> 1.9 \> 10.4.6

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntvoice\>1932 &\</cntvoice\>

Contact Voice Telephone Number (for technical contact)

This tag is optional, and should be used if tag \<cntorg\>1904
&&\</cntorg\> contains an entry. The entry is free text. Replace label
\"1932 &&\" with a voice telephone number, including the area code,
where the organization named in \<cntorg\> can be contacted about the
metadata. This tag must occur at least once, and is optionally
repeatable as many times as needed.

\<cntvoice\>1932 &\</cntvoice\> corresponds to element 1.9 \> 10.5 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntfax\>1933 &\</cntfax\>

Contact Facsimile (Fax) Telephone Number (for technical contact)

This tag is optional, but should not be used unless tag \<cntorg\>1904
&&\</cntorg\> contains an entry. The entry is free text. Replace label
\"1933 &\" with a facsimile (fax) telephone number, including the area
code, at the organization named in \<cntorg\>. This tag is repeatable as
many times as needed.

\<cntfax\>1933 &\</cntfax\> corresponds to element 1.9 \> 10.7 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cnttdd\>1934 &\</cnttdd\>

Contact TDD/TTY Telephone Number (for technical contact)

This tag is optional, but should not be used unless tag \<cntorg\>1904
&&\</cntorg\> contains an entry. The entry is free text. Replace label
\"1934 &\" with a telephone number, including the area code, by which
hearing-impaired people can reach the organization named in \<cntorg\>.
This tag is repeatable as many times as needed.

\<cnttdd\>1934 &\</cnttdd\> corresponds to element 1.9 \> 10.6 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntemail\>1935 &\</cntemail\>

Contact Electronic Mail (e-mail) Address (for technical contact)

This tag is optional, but should not be used unless tag \<cntorg\>1904
&&\</cntorg\> contains an entry. The entry is free text. Replace label
\"1935 &\" with an e-mail address where the organization named in
\<cntorg\> can be contacted. This tag is repeatable as many times as
needed.

\<cntemail\>1935 &\</cntemail\> corresponds to element 1.9 \> 10.8 of
the FGDC Standards.

**FGDC Section 2: Data Quality Information**

**This section is mandatory-if-applicable. It is applicable and
therefore mandatory if data quality is relevant to the item. The section
describes data quality issues associated with the item. In the template,
Section 2 consists of all tags whose labels begin with 2. Fill in as
described below, starting with tag** **\<attraccr\>2001
&&\</attraccr\>.**

**If data quality is not applicable to the item, make no entries in tags
whose labels begin with 2. If data quality is unknown or unavailable,
this fact can be stated in Section 2.**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<attraccr\>2001 &&\</attraccr\>

Attribute Accuracy Report

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 2 is used and attribute accuracy is relevant
to the item.

The entry is free text of indefinite length. Replace label \"2001 &&\"
with a description of the accuracy of the data in the item, but not
positional accuracy. The description might include tests performed,
methodologies, statistical analyses, cross-referencing, parallel
independent measures, results obtained, etc. **Unknown, Not available**,
and **Not provided** will be appropriate entries in some cases.

Making an entry in this tag requires thorough knowledge of the item and
the science involved.

This description can be as long as needed. The writer should begin a new
line after each line\'s column 78 has been entered.

Note: Positional accuracy is described in tags \<horizpar\>2006
&\</horizpar\> and \<vertaccr\>2009 &\</vertaccr\>.

\<attraccr\>2001 &&\</attraccr\> corresponds to element 2.1.1 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<logic\>2004 &&\</logic\>

Logical Consistency Report

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 2 is used. The entry is free text of
indefinite length. Replace label \"2004 &&\" with an explanation of the
fidelity of relationships in the item, and tests used. For example: If
the data has topology, so state. Describe the associations assumed by
the GIS (Left-Polygon, Right-Polygon, Adjacency, etc.). Describe changes
in the relationships. Describe any geometric problems.

Making an entry in this tag requires a sound knowledge of the item and
the science involved. If logical consistency is irrelevant to the item,
enter **Not applicable**. If unknown, enter **Unknown**.

This description can be as long as needed. The writer should begin a new
line after each line\'s column 78 has been entered.

\<logic\>2004 &&\</logic\> corresponds to element 2.2 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<complete\>2005 &&\</complete\>

Completeness Report

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 2 is used. The entry is free text. Replace
label \"2005 &&\" with an explanation of how complete the item is.
Describe data omissions, selection criteria, generalizations,
definitions used, and other rules used to produce the item in its
present form.

This description can be as long as needed. The writer should begin a new
line after each line\'s column 78 has been entered.

\<complete\>2005 &&\</complete\> corresponds to element 2.3 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<horizpar\>2006 &\</horizpar\>

\<vertaccr\>2009 &\</vertaccr\>

Horizontal and Vertical Positional Accuracy Reports

These tags are optional. Both tags\' entries are free text. These tags
must be treated as a pair: The writer must make entries in both tags, or
in neither. In \<horizpar\>, replace \"2006 &\" with an explanation of
the accuracy of the horizontal coordinate measurements associated with
item and describe the tests used to establish the accuracy. In
\<vertaccr\>, replace label \"2009 &\" with a similar explanation of the
accuracy of vertical measurements.

Making entries in these tags requires a thorough knowledge of the item
and the science that is involved.

These descriptions can be as long as needed. The writer should begin a
new line after each line\'s column 78 has been entered.

For explanations about accuracy other than horizontal and vertical
positional accuracy, please use tag \<attraccr\>2001 &&\</attraccr\>.

\<horizpar\>2006 &\</horizpar\> corresponds to element 2.4.1.1 of the
FGDC Standards.

\<vertaccr\>2009 &\</vertaccr\> 2.4.2.1

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<procstep\>

\<procdesc\>2101 &&\</procdesc\>

\<srcused\>\</srcused\>

\<procdate\>2103 &&\</procdate\>

\<proctime\>\</proctime\>

\<srcprod\>\</srcprod\>

\<proccont\>

\<cntinfo\>

\<cntorgp\>

\<cntorg\>\</cntorg\>

\<cntper\>\</cntper\>

\</cntorgp\>

\<cntperp\>

\<cntper\>\</cntper\>

\<cntorg\>\</cntorg\>

\</cntperp\>

\<cntpos\>\</cntpos\>

\<cntaddr\>

\<addrtype\>\</addrtype\>

\<address\>\</address\>

\<city\>\</city\>

\<state\>\</state\>

\<postal\>\</postal\>

\<country\>\</country\>

\</cntaddr\>

\<cntvoice\>\</cntvoice\>

\<cntfax\>\</cntfax\>

\<cnttdd\>\</cnttdd\>

\<cntemail\>\</cntemail\>

\<hours\>\</hours\>

\<cntinst\>\</cntinst\>

\</cntinfo\>

\</proccont\>

\</procstep\>

Process Description and Process Date (Lineage of item)

This is a tag group inside the enclosing tag \<procstep\>\</procstep\>.
In this description, the word \"group\" refers to this Lineage group.

One occurrence of the group is mandatory-if-applicable. It is applicable
and therefore mandatory if FGDC Section 2 is used. Group can optionally
be repeated as many times as necessary.

The intent of this group is to allow the writer to explain how the item
was created from another source or other sources, such as existing data
sets. This is like a \"family tree\" and is called lineage. Making an
entry in this group requires a thorough knowledge of the item and the
science involved.

There are many unlabeled tags in this group that could receive entries;
but only two labeled tags, \<procdesc\>2101 &&\</procdesc\> and
\<procdate\>2103 &&\</procdate\> are recommended for NCDC use. These two
tags cannot occur by themselves. They must occur inside the group.

\<Procdesc\> is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 2 is used and the group occurs. The entry is
free text. Replace label \"2101 &&\" with a description of the process
of creating the item from a source such as other data or an existing
data set. If there is no such process and source, the suggested entry is
**Not derived from another source**. Otherwise, give the name of the
source, including the FGDC Number, if any, and explain the process of
creating the item. If the process has a long and complex \"family tree\"
with grandparent and perhaps great-grandparent sources, describe only
one major step of the process in this occurrence of \<procdesc\>. The
description can be as long as needed. The writer should begin a new line
after each line\'s column 78 has been entered. (\<Procdesc\> is an
opportunity to name people and organizations who helped in the data
collection or processing, who might not otherwise be mentioned.)

\<Procdate\> is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 2 is used, and the group occurs. The entry is
the calendar date when the process described in \<procdesc\> was
completed. Replace label \"2103 &&\" with that calendar date in YYYYMMDD
format, or choose from **Unknown** or **Not complete**. If the entry in
\<procdesc\> is **Not derived from another source**, enter **Unknown**
in \<procdate\>.

If there are more sources to describe, repeat the group for each one.

\<procdesc\>2101 &&\</procdesc\> corresponds to element 2.5.2.1 of the
FGDC Standards.

\<procdate\>2103 &&\</procdate\> 2.5.2.3

**FGDC Section 5: Entity and Attribute Information (Detailed Description
of Data)**

**This section is mandatory-if-applicable. It is applicable and
therefore mandatory if data parameters are in the item. Section 5 is
where the parameters (station ID, platform and sensor IDs, dates, times,
data fields, quality flags, etc.) are described in detail. Section 5
consists of all tags whose labels begin with 5. If parameters are not
associated with the item, do not make entries in these tags.**

**There are unlabeled tags in Section 5 of the template that are
designed for detailed data descriptions using the entity and attribute
method. This method is not suggested for most NCDC items. However, if
NCDC writers want to use the entity and attribute method, they may do
so; and a description of this method can be placed in an appendix to
this *Users Guide*.**

**A simplified method is suggested for most NCDC metadata. Fill in the
labeled tags whose labels begin with 5 as described below, starting with
tag \<eaover\>5001 &&\</eaover\>.**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<eaover\>5001 &&\</eaover\>

Entity and Attribute Overview (Detailed Parameter Description)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 5 is used. It is free text. Replace label
\"5001 &&\" with a detailed explanation of the item\'s data parameters.

Making an entry in this tag requires thorough knowledge of the item and
the science involved.

The content of this detailed description depends greatly on the nature
of the item and its packaging. Information that will be available only
in the metadata should be presented in detail. Information that is part
of the item can be described in summary.

The description can be as long as needed. The writer should begin a new
line after each line\'s column 78 has been entered.

Below are several subsections, starting with *General*, that offer
suggestions for what information should be given.

*General:*

For almost any data, the user has a need to know what parameters are the
data values, how the values are presented (bits, bytes, integers,
floating point numbers, text, dates, etc.), what are the measurement
units (feet, joules, etc.) which data values are valid (\"domain\"),
what is the floating point number precision, what conversion factors
must be applied by the user to get a true data value from a given value.

The writer may choose to describe not just the measured or modeled
parameters, but also other supporting parameters such as
station/platform data, locations, dates, and times, flags and
qualifiers, sensor voltages and constants, etc.

*For simple digital data files:*

The item consists of one or more digital files for which the user must
provide his/her own means to access and utilize the data.

The writer must describe the file sizes, names, what kind of information
each file contains, the file type (e.g. ASCII, binary, EBCDIC, etc.).
Say whether each file is composed of logical or physical records and, if
so, what marks the end of a record. Document each different kind of data
field in each file. If there is more than one record format, say which
data field goes with which record format. In addition to the information
mentioned in *General* (above), the writer should also say how many bits
or bytes a parameter occupies and where in the file or in a record it
begins (e.g. \"Air Temperature\" occupies five bytes and begins in
column 28 of each record).

If the writer has done a good job, this description will allow a
computer programmer unfamiliar with the data to be able to write a
program that will successfully read and utilize the simple data files.

*For data and software packages:*

The item is a package containing both data and data-accessing software.

The writer needs to say how to use the package. List the software's
requirements for computer type (mainframe, Unix workstation, PC, etc.)
and operating system (Windows, DOS, Unix, Linux, etc. with minimum
version number). Document the parameters as outlined in *General*
(above). Describe what the user can do with the package (e.g. on the
map, plot daily total precipitation and maximum temperature; reformat;
output to a file or user service; etc.). If there is a users guide with
the item that covers all of this, this metadata description can be
brief.

Sample entry for simple digital data files (partial):

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

\<eaover\>

Data are provided to NCDC in two similar formats. The first format,
which

NCDC has designated as DSI-6420a, has the following format description

provided by the data supplier:

\(1\) This is how the data are arranged on the AOC slow tape. The data
are

recorded as 16 bit HP words. Most of the data is recorded as integer
counts

and must be converted to volts and then to meaningful units. All of the

navigation data is stored in a special format, and can only be read by

performing special bit shifting operations. If examination of the raw

navigation data is desired, ask AOC for a copy of the bit shifting
subroutine

called PACK.

Beginning with the 2000 Hurricane Season, locations 32-38 contain GPS
data

from the ASHTECH BR2G system (BR2G prefix).

This element table is for the NOAA42- N42RF-Aircraft during the 2003

Hurricane season, the Tamdar project, and a wind calibration flight.

Array

Location Description

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

1 Type of record (4)

2 Number of words in record (222)

3 MS byte: Slow tape ID LS byte: Aircraft \#

4 Size of slow tape logical record = 220

5-10 Micro 29 time - yr,mo,da,hr,mn,sc

11-13 Time based generator 1 - hr,mn,sc; binary (not BCD)

14-16 Time based generator 2 - same as TBG 1

17-19 GPS time of fix - hr, min,sec; same as TBGs

20-21 GPS altitude - MS bit = -102400\*32 ft

22-23 GPS latitude - MS bit = -PI\*4 radians

24-25 GPS longitude - MS bit = -PI\*4 radians

26-27 GPS north vel. - MS bit = -1638.4\*2 knots

28-29 GPS east vel. - MS bit = -1638.4\*2 knots

30-31 GPS vert. vel. - MS bit = -2048\*2 ft/s

32 BR2G GPS data Time; 0 - 3600, lsb = 1/100 sec

33 BR2G GPS Altitude; +/- 32767, lsb = 1 ft

34-35 BR2G GPS Latitude; msb = -PI\*4 radians

\.....

\.....

\.....

\</eaover\>

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

\<eaover\>5001 &&\</eaover\> corresponds to element 5.2.1 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<eadetcit\>5002 &&\</eadetcit\>

Entity and Attribute Detail Citation

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 5 is used. If there is another readily
accessible location (besides tag \<eaover\>5001 &&\</eaover\> in this
metadata) where a detailed description can be found, replace label
\"5002 &&\" with that location. Otherwise, enter **None**.

\<eadetcit\>5002 &&\</eadetcit\> corresponds to element 5.2.2 of the
FGDC Standards.

**FGDC Section 6: Distribution Information**

**This section is mandatory-if-applicable. It describes procedures that
are in place to distribute the item to users. This section is applicable
and therefore mandatory if distribution procedures exist. If there are
no distribution procedures, Section 6 should not be used (rare).**

**Section 6 in the template consists of all tags whose labels begin with
6.**

**Section 6's intended method for documenting standard distribution
procedures is not suggested for use at NCDC. However, NCDC writers may
use it; and, if there is enough interest, a description of the method
can be placed in an appendix of this *Users Guide*.**

**The suggested method below is to document the distribution process as
a custom process. Make entries in tags whose labels begin with 6,
starting with tag \<cntorg\>6001 &&\</cntorg\>.**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntorg\>6001 &&\</cntorg\>

Contact Organization (for item distribution purposes)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 6 is used. The entry is free text. Replace
label \"6001 &&\" with the name of the organization that distributes the
item. In NCDC metadata, this organization will almost always be NCDC.

\<cntorg\>National Climatic Data Center, NESDIS, NOAA, U.S. Department
of Commerce \</cntorg\>

This name is from the GCMD \"Data Centers\" thesaurus mentioned in the
*Standardized words and phrases* paragraph on page 5.

\<cntorg\>6001 &&\</cntorg\> corresponds to element 6.1 \> 10.2 \>
10.1.2 of the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntper\>6002 &\</cntper\>

Contact Person (for item distribution purposes)

This tag is optional. The entry is free text. If there is one and only
one person who must be contacted at the organization named in
\<cntorg\>6001 &&\</cntorg\> concerning distribution, replace label
\"6002 &\" with the person\'s name. At NCDC, there is not normally one
person who is solely responsible for distribution of any item.

\<cntper\>6002 &\</cntper\> corresponds to element 6.1 \> 10.2 \> 10.1.1
of the FGDC Standards.

\<cntpos\>6005 &\</cntpos\>

Contact Position (for item distribution purposes)

This tag is optional. The entry is free text. Replace label \"6005 &\"
with the position description or job function that handles distribution
of this item at the organization named in

\<cntorg\>6001 &&\</cntorg\>. A few possible entries are **Principal
Investigator**, **Customer Service**, **Research Meteorologist**, etc.

\<cntpos\>6005 &\</cntpos\> corresponds to element 6.1 \> 10.3 of the
FGDC Standards.

\<cntaddr\>

\<addrtype\>6006 &&\</addrtype\>

\<address\>6007 &&\</address\>

\<city\>6008 &&\</city\>

\<state\>6009 &&\</state\>

\<postal\>6010 &&\</postal\>

\<country\>6011 &\</country\>

\</cntaddr\>

Contact Address (address of the organization for distribution purposes)

This is the address(es) of the organization named in tag \<cntorg\>6001
&&\</cntorg\>.

Contact Address is a tag group which is mandatory-if-applicable. It is
applicable and therefore mandatory if FGDC Section 6 is used. This tag
group must appear at least once; but it may be repeated as many times as
necessary. In the rest of this description, the word \"group\" will be
used to refer to this Contact Address tag group.

\<Addrtype\> is Address Type. It is mandatory-if-applicable. It is
applicable and therefore mandatory if FGDC Section 6 is used and the
group occurs. The entry is free text. Replace label \"6006 &&\" with the
type of address. Possibilities are: **Mailing** if the address is a
mailing address, but is not the organization\'s location, such as a post
office box. **Physical** if the address is where the organization is
located, but is not a mailing address. **Mailing and physical** if the
address is both a mailing address and the organization\'s location. Or,
use free text to describe the address if none of the above three choices
are appropriate. **Mailing and physical** is the best choice for NCDC at
Asheville. Many organizations have both on-site and post office box
mailing addresses. In such cases, at least two occurrences of the group,
one for each address of each type, are required.

\<Address\> is mandatory-if-applicable. It is applicable and therefore
mandatory when FGDC Section 6 is used, and the group occurs, and there
is an organization name, street address, or post office box number in
the address. Replace label \"6007 &&\" with one part of the address.
\<Address\> is repeatable inside one group to allow for multiple address
lines. At NCDC at Asheville, \<address\> would occur twice. The first
entry would be **National Climatic Data Center**. The second entry would
be **151 Patton Avenue, Room 120**.

\<City\> is mandatory-if-applicable. It is applicable and therefore
mandatory when FGDC Section 6 is used and the group occurs. Replace
label \"6008 &&\" with the name of a city, town, or municipality that is
part of the address. For NCDC at Asheville, the entry would be
**Asheville**.

\<State\> is mandatory-if-applicable. It is applicable and therefore
mandatory when FGDC Section 6 is used and the group occurs. Replace
label \"6009 &&\" with the name of a U. S. state, Canadian province, or
similar political entity. For NCDC at Asheville, the entry would be
**North Carolina** or **NC**.

\<Postal\> is mandatory-if-applicable. It is applicable and therefore
mandatory when FGDC Section 6 is used and the group occurs. Replace
label \"6010 &&\" with an appropriate postal code. For the U. S., it
would be a zip code. For NCDC at Asheville, **28801** is suggested.

\<Country\> is optional. Replace label \"6011 &\" with the name of the
appropriate country. For the U. S., **USA** is suggested. Do not use
\<country\> unless FGDC Section 6 is used.

\<addrtype\>6006 &&\</addrtype\> corresponds to element 6.1 \> 10.4.1 of
the FGDC Standards.

\<address\>6007 &&\</address\> 6.1 \> 10.4.2

\<city\>6008 &&\</city\> 6.1 \> 10.4.3

\<state\>6009 &&\</state\> 6.1 \> 10.4.4

\<postal\>6010 &&\</postal\> 6.1 \> 10.4.5

\<country\>6011 &\</country\> 6.1 \> 10.4.6

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntvoice\>6012 &&\</cntvoice\>

Contact Voice Telephone Number (for distribution purposes)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 6 is used. The entry is free text. Replace
label \"6012 &&\" with a voice telephone number, including the area
code, where the organization named in tag \<cntorg\>6001 &&\</cntorg\>
can be contacted about distribution. This tag is repeatable as many
times as needed. At NCDC at Asheville, **828-271-4800** is the one voice
telephone number for customer service.

\<cntvoice\>6012 &&\</cntvoice\> corresponds to element 6.1 \> 10.5 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntfax\>6013 &\</cntfax\>

Contact Facsimile (Fax) Telephone Number (for distribution purposes)

This tag is optional. The entry is free text. Do not use this tag unless
FGDC Section 6 is used. Replace label \"6013 &\" with a facsimile (fax)
telephone number, including the area code, where the organization named
in tag \<cntorg\>6001 &&\</cntorg\>can be contacted about distribution.
This tag is repeatable as many times as needed. At NCDC at Asheville,
for example, **828-271-4876** is the fax telephone number for customer
service.

\<cntfax\>6013 &\</cntfax\> corresponds to element 6.1 \> 10.7 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cnttdd\>6014 &\</cnttdd\>

Contact TDD/TTY Telephone Number (for distribution purposes)

This tag is optional. The entry is free text. Do not use this tag unless
FGDC Section 6 is used. Replace label \"6014 &\" with a telephone
number, including the area code, by which hearing-impaired people can
contact the organization named in tag \<cntorg\>6001 &&\</cntorg\> about
distribution. This tag is repeatable as many times as needed.

\<cnttdd\>6014 &\</cnttdd\> corresponds to element 6.1 \> 10.6 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntemail\>6015 &\</cntemail\>

Contact Electronic Mail (e-mail) Address (for distribution purposes)

This tag is optional. The entry is free text. Replace label \"6015 &\"
with an e-mail address where the organization named in tag
\<cntorg\>6001 &&\</cntorg\> can be contacted about distribution. This
tag is repeatable as needed. At NCDC at Asheville,
**NCDC.Orders@noaa.gov** is the e-mail address for customer service. Do
not use \<cntemail\> unless FGDC Section 6 is used.

\<cntemail\>6015 &\</cntemail\> corresponds to element 6.1 \> 10.8 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<resdesc\>6018 &&\</resdesc\>

Resource Description (for distribution purposes)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 6 is used and if a resource description is
available or appropriate for the item. The entry is free text. Replace
label \"6018 &&\" with a short name or ID by which the item can be
requested from the organization named in tag \<cntorg\>6001
&&\</cntorg\>. For an NCDC data set, this might be the DSI number, such
as **DSI-3200**.

\<resdesc\>6018 &&\</resdesc\> corresponds to element 6.2 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<distliab\>6019 &&\</distliab\>

Distribution Liability (for distribution purposes)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 6 is used. The entry is free text. Replace
label \"6019 &&\" with a statement about the legal liability for the use
of the item that the organization named in tag \<cntorg\>6001
&&\</cntorg\> assumes. For NCDC, a good one is:

**Disclaimer: While every effort has been made to ensure that these data
are accurate and reliable within the limits of the current state of the
art, NOAA cannot assume liability for any damages caused by any errors
or omissions in the data, nor as a result of the failure of the data to
function on a particular system. NOAA makes no warranty, expressed or
implied, nor does the fact of distribution constitute such a warranty.**

\<distliab\>6019 &&\</distliab\> corresponds to element 6.3 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<custom\>6101 &&\</custom\>

Custom Ordering Procedure (for distribution purposes)

This tag is mandatory-if-applicable. It is applicable and therefore
mandatory if FGDC Section 6 is used. The entry is free text. Replace
label \"6101 &&\" with an explanation of what steps to follow and what
fees are required to obtain the item from the organization named in tag
\<cntorg\>6001 &&\</cntorg\>.

\<custom\>6101 &&\</custom\> corresponds to element 6.5 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<techpreq\>6102 &\</techpreq\>

Technical Prerequisites (for the user)

This tag is optional. The entry is free text. Do not use \<techpreq\>
unless FGDC Section 6 is used. Replace label \"6102 &\" with a
description of technical capabilities that the user must have to use the
item. For example, a computer with internet browser to download digital
files may be needed. The user or staff may need to write a computer
program that will read and utilize the data files.

\<techpreq\>6102 &\</techpreq\> corresponds to element 6.6 of the FGDC
Standards.

**FGDC Section 7: Metadata Reference Information**

**This section is mandatory. It may not be left blank. It provides
information about the metadata instead of the item, including the
metadata\'s timeliness and what person or organization is responsible
for it. In the template, Section 7 consists of all tags whose labels
begin with 7. Fill in the labeled tags as indicated below, starting with
tag \<metd\>7001 &&&\</metd\>.**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<metd\>7001 &&&\</metd\>

Metadata Date

This tag is mandatory. Replace label \"7001 &&&\" with a calendar date
in the format YYYYMMDD. The date is when the metadata was last updated,
or its date of creation.

\<metd\>7001 &&&\</metd\> corresponds to element 7.1 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<metrd\>7002 &&\</metrd\>

\<metfrd\>7003 &\</metfrd\>

Metadata Review Date

and

Future Metadata Review Date

\<Metrd\> is mandatory-if-applicable. It is applicable and therefore
mandatory when a previous version of the metadata exists. Replace label
\"7002 &&\" with a calendar date in YYYYMMDD format. The date is when
the metadata was last reviewed. The date in \<metrd\> should be the same
or later than the date in tag \<metd\>7001 &&&\</metd\>.

\<Metfrd\> is optional. Replace label \"7003 &\" with the future
calendar date in YYYYMMDD format when the next review, if any, is
planned for the item\'s metadata. If there is no planned review date, do
not use this tag.

\<metrd\>7002 &&\</metrd\> corresponds to element 7.2 of the FGDC
Standards.

\<metfrd\>7003 &\</metfrd\> 7.3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntorg\>7004 &&&\</cntorg\>

Contact Organization (for metadata)

This tag is mandatory. The entry is free text. Replace label \"7004
&&&\" with the name of the organization that is responsible for the
metadata. If the organization is NCDC, the suggested entry is

\<cntorg\>National Climatic Data Center, NESDIS, NOAA, U.S. Department
of Commerce \</cntorg\>

This name is from the GCMD \"Data Centers\" thesaurus mentioned in the
*Standardized words and phrases* paragraph on page 5.

\<cntorg\>7004 &&&\</cntorg\> corresponds to element 7.4 \> 10.2 \>
10.1.2 of the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntper\>7005 &\</cntper\>

Contact Person (for metadata)

This tag is optional. The entry is free text. Normally, this tag should
not be used. But if there is only one person who should be contacted
about the metadata at the organization named in tag \<cntorg\>7004
&&&\</cntorg\>, replace the label with the person\'s name.

\<cntper\>7005 &\</cntper\> corresponds to element 7.4 \> 10.2 \> 10.1.1
of the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntpos\>7008 &\</cntpos\>

Contact Position (for metadata)

This tag is optional. The entry is free text. Replace \"7008 &\" with
the position description or job function of people at the organization
named in tag \<cntorg\>7004 &&&\</cntorg\> who can be contacted about
the metadata. A few possibilities are **Principal Investigator**,
**Customer Service**, **Research Meteorologist**, etc.

\<cntpos\>7008 &\</cntpos\> corresponds to element 7.4 \> 10.3 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntaddr\>

\<addrtype\>7026 &&&/addrtype\>

\<address\>7027 &\</address\>

\<city\>7028 &&\</city\>

\<state\>7029 &&\</state\>

\<postal\>7030 &&\</postal\>

\<country\>7031 &\</country\>

\</cntaddr\>

Contact Address (for metadata)

This is a tag group which is mandatory. In the rest of this description,
the word \"group\" will be used to refer to this tag group. The group
must appear at least once; but may optionally be repeated as many times
as necessary.

This is the address of the organization named in tag \<cntorg\>7004
&&&\</cntorg\>.

\<Addrtype\> is Address Type. It is mandatory-if-applicable. It is
applicable and therefore mandatory when the group occurs. The entry is
free text. Replace label \"7026 &&\" with the kind of address.
Possibilities are: **Mailing** if the address is a mailing address but
is not where the organization is located, such as a post office box.
**Physical** if the address is where the organization is physically
located, but is not a mailing address. **Mailing and physical** if the
address is both a mailing address and where the organization is
physically located. Or, use free text to describe the address if none of
the above three choices are appropriate. **Mailing and physical** is the
best choice for NCDC at Asheville. Many organizations have both on-site
and post office box mailing addresses; in such cases, at least two
occurrences of the group, one for each address of each type, are needed.

\<Address\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs and when there is an organization name,
street address, or post office box number in the address. Replace label
\"7027 &&\" with one part of the address. \<Address\> is repeatable
inside one group to allow for multiple lines. At NCDC at Asheville,
\<address\> would occur twice. The first entry would be **National
Climatic Data Center**. The second entry would be **151 Patton Avenue,
Room 120**.

\<City\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"7028 &&\" with the name
of a city, town, or municipality that is part of the address. For NCDC
at Asheville, the entry would probably be **Asheville**.

\<State\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"7029 &&\" with the name
of a U. S. state, Canadian province, or similar political entity. For
NCDC at Asheville, the entry would be **North Carolina** or **NC**.

\<Postal\> is mandatory-if-applicable. It is applicable and therefore
mandatory when the group occurs. Replace label \"7030 &&\" with an
appropriate postal code. For the U. S., it would be a zip code. For NCDC
at Asheville, **28801** is suggested.

\<Country\> is optional. Replace label \"7031 &\" with the name of the
appropriate country. For the U. S., **USA** is suggested.

\<addrtype\>7026 &&&/addrtype\> corresponds to element 7.4 \> 10.4.1 of
the FGDC Standards.

\<address\>7027 &\</address\> 7.4 \> 10.4.2

\<city\>7028 &&\</city\> 7.4 \> 10.4.3

\<state\>7029 &&\</state\> 7.4 \> 10.4.4

\<postal\>7030 &&\</postal\> 7.4 \> 10.4.5

\<country\>7031 &\</country\> 7.4 \> 10.4.6

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntvoice\>7032 &&&\</cntvoice\>

Contact Voice Telephone Number (for metadata)

This tag is mandatory. The entry is free text. Replace label \"7032
&&&\" with a voice telephone number where the organization named in tag
\<cntorg\>7004 &&&\</cntorg\> can be contacted about the metadata. The
number must include the area code. This tag must occur at least once,
and is optionally repeatable as many times as needed. At NCDC at
Asheville, for example, **828-271-4800** is the voice telephone number
for customer service.

\<cntvoice\>7032 &&&\</cntvoice\> corresponds to element 7.4 \> 10.5 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntfax\>7033 &\</cntfax\>

Contact Facsimile (Fax) Telephone Number (for metadata)

This tag is optional. The entry is free text. Replace label \"7033 &\"
with a facsimile (fax) telephone number, including the area code, where
the organization named in tag

\<cntorg\>7004 &&&\</cntorg\> can be contacted about the metadata. This
tag is repeatable as many times as needed. At NCDC at Asheville,
**828-271-4876** is the fax telephone number for customer service.

\<cntfax\>7033 &\</cntfax\> corresponds to element 7.4 \> 10.7 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cnttdd\>7034 &\</cnttdd\>

Contact TDD/TTY Telephone Number (for metadata)

This tag is optional. The entry is free text. Replace label \"7034 &\"
with a telephone number, including the area code, by which
hearing-impaired people can contact the organization named in
\<cntorg\>7004 &&&\</cntorg\> about the metadata. This tag is repeatable
as many times as needed.

\<cnttdd\>7034 &\</cnttdd\> corresponds to element 7.4 \> 10.6 of the
FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<cntemail\>7035 &\</cntemail\>

Contact Electronic Mail (e-mail) Address (for metadata)

This tag is optional. The entry is free text. Replace label \"7035 &\"
with an e-mail address where the organization named in \<cntorg\>7004
&&&\</cntorg\> can be contacted about the metadata. This tag is
repeatable as many times as needed for multiple e-mail addresses. At
NCDC at Asheville, the e-mail address for customer service is
[**NCDC.Orders@noaa.gov**](mailto:NCDC.Orders@noaa.gov).

\<cntemail\>7035 &\</cntemail\> corresponds to element 7.4 \> 10.8 of
the FGDC Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<metstdn\>7038 &&&\</metstdn\>

Metadata Standard Name

This tag is mandatory. Replace label \"7038 &&&\" with the name of the
metadata standard being used. At this writing, the standard used at NCDC
is

\<metstdn\>FGDC Content Standards for Digital Geospatial
Metadata\</metstdn\>

\<metstdn\>7038 &&&\</metstdn\> corresponds to element 7.5 of the FGDC
Standards.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\<metstdv\>7039 &&&\</metstdv\>

Metadata Standard Version

This tag is mandatory. Replace label \"7039 &&&\" with the version of
the metadata standard being used. At this writing, the version of the
standard at NCDC is

\<metstdv\>FGDC-STD-001-1998\</metstdv\>

\<metstdv\>7039 &&&\</metstdv\> corresponds to element 7.6 of the FGDC
Standards.

**Appendix A -- ISO 19115 Topic Category Keywords**

***Farming, 001***

rearing of animals and/or cultivation of plants

e.g., agriculture, crops, livestock

***Biota, 002***

flora and/or fauna in natural environments

e.g., flora and fauna, ecology, wetlands, habitat

***Boundaries, 003***

legal land descriptions

e.g., political and administrative boundaries

***ClimatologyMeteorologyAtmosphere, 004***

processes and phenomena of the atmosphere

e.g., processes and phenomena of the atmosphere

***Economy, 005***

economic activities, conditions, and employment

e.g., business and economics

***Elevation, 006***

height above or below the earth\'s surface

e.g., altitude, bathymetry, dem\'s, slope, derived products

***Environment, 007***

environmental resources, protection, and conservation

e.g., natural resources, pollution, impact assessment, monitoring, land
analysis

***GeoscientificInformation, 008***

information pertaining to the earth sciences

e.g., geology, minerals, earthquakes, landslides, volcanoes, soils,
gravity, permafrost, hydrogeology, erosion

***Health, 009***

health, health services, human ecology, and safety

e.g., disease, illness, factors affecting health, hygiene, substance
abuse

***ImageryBaseMapsEarthCover, 010***

base maps

e.g., land cover, topographic maps, imagery, annotations

***IntelligenceMilitary, 011***

military bases, structures, activities

e.g., military bases, structures, activities

***Inland Waters, 012***

inland water features, drainage systems and characteristics

e.g., rivers, glaciers, lakes, water use plans, dams, currents, floods,
water quality, hydrographic charts

***Location, 013***

positional information and services

e.g., addresses, geodetic networks, control points, postal zones,

place names

***Oceans, 014***

features and characteristics of salt water bodies

e.g., tides, tidal waves, coastal information, reefs

***PlanningCadastre, 015***

information used for appropriate actions for future use of the land

e.g., land use maps, zoning maps, cadastral surveys, land ownership

***Society, 016***

characteristics of society and culture

e.g., anthropology, archaeology, religion, demographics, crime and

justice

***Structure, 017***

man-made construction

e.g., architecture, buildings, museums, churches, factories, housing,

monuments, shops, towers

***Transportation, 018***

means and aids for conveying persons and/or goods

e.g., roads, airports, airstrips, shipping routes, tunnels, nautical

charts, vehicle and vessel locations, aeronautical charts, railways,

trails

***UtilitiesCommunication, 019***

energy, water and waste systems, and communications infrastructure

e.g., hydroelectricity, geothermal, solar, and nuclear sources of
energy, water purification and distribution, sewage collection and
disposal, electrical and gas distribution, data communication,
telecommunication, radio, communication networks