Element Definitions:
|
coverage |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
geographicCov | Optional | Multiple Times |
temporalCov | Optional | Multiple Times |
taxonomicCov | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Coverage information
Summary:
The geographic, temporal, and taxonomic extents of the resource being
described.
Description:
The coverage element provides a series of sub-fields that describe the
overall geographic, temporal, and taxomomic extents of the resource
being described, usually a dataset.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
The coverage element is derived from the NBII standard.
|
geographicCov |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Geographic coverage
Summary:
Geographic coverage information.
Description:
Geographic Coverage is a container for spatial information about a
project, a resource, or an entity within a resource. It allows a
bounding box for the overall coverage (in lat long), and also
allows descriptin of arbitrary polygons with exclusions.
Example:
Please see the individual sub fields for specific examples.
Lineage:
The geographicCov element is derived from the NBII standard.
|
temporalCov |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Temporal coverage
Summary:
Temporal coverage information.
Description:
This field specifies temporal coverage, and allows coverages
to be a single point in time, multiple points in time, or a
range of dates. Dates can be expressed in tems of both
calander dates and geologic dating systems.
Example:
Please see the individual sub fields for specific examples.
Lineage:
The TemporalCoverage complex type was introduced into EML 1.4.
|
taxonomicCov |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Taxonomic coverage
Summary:
Taxonomic coverage information.
Description:
Taxonomic Coverage is a container for Taxonomic information about a
project, a resource, or an entity within a resource. It includes a
list of species names (or higher level ranks) from one or more
classification systems.
Example:
Please see the individual sub fields for specific examples.
Lineage:
The TaxonomicCoverage complex type was introduced in EML 2 and
derived from the NBII taxonomy element.
|
singleDateTime |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A choice of ( |
A sequence of ( |
calendarDate | Optional | Multiple Times |
time | Optional | Multiple Times |
) |
OR
|
geologicAge | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Single Date/Time
Summary:
Means of encoding a single date and time
Description:
The singleDateTime field is intended to describe a single date and
time for an event. There is a choice between two options: a calendar
date with a time, or a geologic age.
Example:
Please see the individual sub-elements for example.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/sngdate
|
calendarDate |
Content of this field:
|
Description of this field:
|
Type: xs:date |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Calendar date
Summary:
The calendar date for an event.
Description:
The calendar date field is used to express a date, giving
the year, month, and day. The format should be one that
complies with the International Standards Organization's
standard 8601. The recommended format for EML is
YYYY-MM-DD, where Y is the four digit year, M is the
two digit month code (01 - 12, where January = 01),
and D is the two digit day of the month (01 - 31).
Example:
2001-01-01 , which is January 1st, 2001.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/sngdate/caldate
|
time |
Content of this field:
|
Description of this field:
|
Type: xs:time |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Time of day
Summary:
The time of day for an event.
Description:
The time field is used to express the hour (and
optionally minute, or minute and second) of the day
for an event, and should comply with the International
Standards Organization's standard 8601. The recommended
format for EML is hh:mm:ssTZD, where hh is the two digit
hour of the day, mm is the two digit minute of the hour,
and ss is the two digit second of the minute. TZD stands
for Time Zone Designator which is used to handle time zone
offsets. Times may be expressed in two ways:
1) UTC (Coordinated Universal Time, also known as
Greenwich Mean Time, or GMT), with a special UTC
designator ("Z"), 2) local time, together with a time zone
offset in hours and minutes. A time zone offset of
"+hh:mm" indicates that the date/time uses a local time
zone which is "hh" hours and "mm" minutes ahead of UTC. A
time zone offset of "-hh:mm" indicates that the date/time
uses a local time zone which is "hh" hours and "mm"
minutes behind UTC.
Example:
1) 08:31:22Z , which means eight thirty one and 22 seconds
in the morning at Coordinated Universal Time (Greenwich
Mean Time).
2) 14:06:09-08:00 , which means six minutes, nine seconds
past two o'clock p.m., Pacific Standard Time (which is
offset eight hours behind UTC)
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/sngdate/time
|
beginningDate |
Content of this field:
|
Description of this field:
|
Type: xs:date |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Beginning date
Summary:
The beginning date for a range of days.
Description:
The beginning date field is used to express the first date
for a range of dates, giving the year, month, and day.
The format should be one that complies with the International
Standards Organization's standard 8601. The recommended format
for EML is YYYY-MM-DD, where Y is the four digit year, M is the
two digit month code (01 - 12, where January = 01),
and D is the two digit day of the month (1 - 31).
Example:
2001-01-01, which is January 1st, 2001.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/rangeOfDates/begdate
|
beginningTime |
Content of this field:
|
Description of this field:
|
Type: xs:time |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Beginning time of day
Summary:
The beginning hour (and optionally minute, or minute and second) of an
event.
Description:
The beginning time (beginningTime) field is used to express the hour
(and optionally minute, or minute and second) for a start time
of a period of time, and should comply with the International
Standards Organization's standard 8601. The recommended format
for EML is hh:mm:ssTZD, where hh is the two digit
hour of the day, mm is the two digit minute of the hour,
and ss is the two digit second of the minute. TZD stands
for Time Zone Designator which is used to handle time zone
offsets. Times may be expressed in two ways:
1) UTC (Coordinated Universal Time, also known as
Greenwich Mean Time, or GMT), with a special UTC
designator ("Z"), 2) local time, together with a time zone
offset in hours and minutes. A time zone offset of
"+hh:mm" indicates that the date/time uses a local time
zone which is "hh" hours and "mm" minutes ahead of UTC. A
time zone offset of "-hh:mm" indicates that the date/time
uses a local time zone which is "hh" hours and "mm"
minutes behind UTC.
Example:
1) 08:31:22Z , which means eight thirty one and 22 seconds
in the morning at Coordinated Universal Time (Greenwich
Mean Time).
2) 14:06:09-08:00 , which means six minutes, nine seconds
past two o'clock p.m., Pacific Standard Time (which is
offset eight hours behind UTC)
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/rangeOfDates/begtime
|
endingDate |
Content of this field:
|
Description of this field:
|
Type: xs:date |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Ending date
Summary:
End date in a range of dates
Description:
The end date field is used to express the last date
for a range of dates, giving the year, month, and day.
The format should be one that complies with the International
Standards Organization's standard 8601. The recommended format
for EML is YYYY-MM-DD, where Y is the four digit year, M is the
two digit month code (01 - 12, where January = 01),
and D is the two digit day of the month (01 - 31).
Example:
2001-01-01, which is January 1st, 2001.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/rangeOfDates/enddate
|
endingTime |
Content of this field:
|
Description of this field:
|
Type: xs:time |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Ending time of day
Summary:
The ending time of day in a period of time
Description:
The 'end time' field is used to express the last hour (and
optionally minute, or minute and second) of the day
for a period of time, and should comply with the International
Standards Organization's standard 8601. The recommended
format for EML is hh:mm:ssTZD, where hh is the two digit
hour of the day, mm is the two digit minute of the hour,
and ss is the two digit second of the minute. TZD stands
for Time Zone Designator which is used to handle time zone
offsets. Times may be expressed in two ways:
1) UTC (Coordinated Universal Time, also known as
Greenwich Mean Time, or GMT), with a special UTC
designator ("Z"), 2) local time, together with a time zone
offset in hours and minutes. A time zone offset of
"+hh:mm" indicates that the date/time uses a local time
zone which is "hh" hours and "mm" minutes ahead of UTC. A
time zone offset of "-hh:mm" indicates that the date/time
uses a local time zone which is "hh" hours and "mm"
minutes behind UTC.
Example:
1) 08:31:22Z , which means eight thirty one and 22 seconds
in the morning at Coordinated Universal Time (Greenwich
Mean Time).
2) 14:06:09-08:00 , which means six minutes, nine seconds
past two o'clock p.m., Pacific Standard Time (which is
offset eight hours behind UTC)
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/rangeOfDates/endtime
|
multipleDatesTimes |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
singleDateTime | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Multiple dates/times
Summary:
Means of encoding multiple individual dates and times.
Description:
The 'multipleDatesTimes' field is entended to be used as a means
of recording multiple dates and times, rather than a single
date/time, or a range of date/times. It allows for multiple
'singleDateTime' (single date) fields to be used in sequence.
Example:
An example would be multiple date/times, encoded in the
International Standards Organization's 8601 Date and Time
standard, as described in the sub-fields of the 'singleDateTime' field
, such as 'calendarDate' and 'time'. The result would be a list of
date/times that: 2001-10-31 08:22Z, 2002-10-31 08:22Z, etc.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/mdattim
|
rangeOfDates |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Range of dates/times
Summary:
Means of encoding a range of dates and times.
Description:
The 'rangeOfDates' field is intended to be used for describing a
range of dates and/or times. It allows for a choice between two
sequences of sub-fields: 1) A 'beginning date' and 'end date'
with optional 'beginning time' and 'end time' fields, or 2) a
'beginning geologic age' and 'ending geologic age'.
Example:
Please see the examples from the 'beginningDate', 'beginningTime',
'endingDate', and 'endingTime' fields for specific examples.
Lineage:
FGDC-STD-001-1998:
/metadata/time_period_information/rngdates
|
geologicAge |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Geologic age
Summary:
A name, code, or date describing an event or period in geologic
time.
Description:
A name, code, or date describing an event or period in geologic
time, expressed either as an absolute date calculated using a
named dating method, or as a relative date that is drawn from
stratigraphy or biostratigraphy. Calendar dates as provided in
the ISO 8601 dating system used in the standard CSDGM are not
adequate to describe geologic time periods. Absolute geologic
time is usually measured in millions of years before present,
but may use different units and relative base times. Relative
geologic time is measured by subdivisions of the earth's geology.
in an order based upon relative age, most commonly, vertical or
stratigraphic position. The actual dating systems used in
geologic studies often tie relative times measured through
stratigraphy or biostratigraphy to a particular absolute time
using radioisotope dating techniques, among others. As these
methods for absolute dating have improved, the estimates of the
dates for strata have changed, consequently, it would be
inaccurate to record absolute dates in situations where relative
dates were measured. This structure is provided as an optional
alternative to the standard calendar dates provided by ISO 8601.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage
|
geologicTimeScale |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Geologic time scale
Summary:
Name of a recognized geologic time scale.
Description:
Name of a recognized geologic time scale. This includes
'Absolute' as the name of the time scale for
measuring geologic dates before the present and names of
geologic dating systems that are arrangements of symbols
or names in order of relative geologic time.
Example:
'Absolute', 'Geomagnetic Polarity Time Scale',
'International Geological Time Scale', 'Oxygen-Isotope'
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage/geolscal
|
geologicAgeEstimate |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Geologic age estimate
Summary:
Description:
Either an absolute geologic date or a relative geologic
age name describing an event or period in geologic time
based on the Geologic Time Scale.
Example:
For example, '300 Ma' (300 million years before present)
is a Geologic_Age_Estimate based on the Absolute
Geologic_Time_Scale, 'C28r' is a chron name from the
Geomagnetic Polarity Time Scale, and 'Maastrichtian' and
'Jurassic' are names from the International Geological
Time Scale. Since different relative geologic time scales
are often not aligned, multiple geologic dates may need
to be specified. For example, the Geomagnetic Polarity
Time Scale chron 'C29r', at the K/T boundary lies in both
the 'Maastrichtian' and the 'Danian' stages from the
International Geological Time Scale, thus if you were
documenting this event using the International Geological
Time Scale, both 'Maastrichtian' and 'Danian' should be
included here.
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage/geolest
|
geologicAgeUncertainty |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Geologic age uncertainty
Summary:
The error estimate for the geologic time.
Description:
The error estimate for the geologic time. This should
include the units of measure, a description of what the
error estimate represents and how it was calculated.
Example:
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage/geolun
|
geologicAgeExplanation |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Geologic age explanation
Summary:
The name and/or description of the method used to
calculate the Geologic age estimate.
Description:
The name and/or description of the method used to
calculate the Geologic age estimate. Detailed information
about the method may be provided through references
contained in the Geologic Citation field.
Example:
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage/geolexpl
|
geologicCitation |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
cit:citation | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Geologic citation
Summary:
Citation for works providing detailed information about
any element of the Geologic age.
Description:
Citation for works providing detailed information about
any element of the Geologic age.
Example:
For example, a publication describing the methodology used
for carbon dating or describing the basic geologic time
scale in more detail could be cited here.
Lineage:
NBII FGDC-STD-001.1-1999:
/metadata/time_period_information/sngdate/geolage/geolcit
|
beginningGeologicAge |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
geologicAge | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Beginning geologic age
Summary:
A name, code, or date for the beginning of an event or period in
geologic time.
Description:
A name, code, or date for the beginning of an event or period in
geologic time.
Example:
For example, '300 Ma' (300 million years before present)
is a Geologic_Age_Estimate based on the Absolute
Geologic_Time_Scale, 'C28r' is a chron name from the
Geomagnetic Polarity Time Scale, and 'Maastrichtian' and
'Jurassic' are names from the International Geological
Time Scale. Since different relative geologic time scales
are often not aligned, multiple geologic dates may need
to be specified. For example, the Geomagnetic Polarity
Time Scale chron 'C29r', at the K/T boundary lies in both
the 'Maastrichtian' and the 'Danian' stages from the
International Geological Time Scale, thus if you were
documenting this event using the International Geological
Time Scale, both 'Maastrichtian' and 'Danian' should be
included here.
Lineage:
FGDC-STD-001.1-1999
/metadata/time_period_information/rngdates/beggeol
|
endingGeologicAge |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
geologicAge | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Ending geologic age
Summary:
A name, code, or date for the end of an event or period in
geologic time.
Description:
A name, code, or date for the end of an event or period in
geologic time.
Example:
For example, '300 Ma' (300 million years before present)
is a Geologic_Age_Estimate based on the Absolute
Geologic_Time_Scale, 'C28r' is a chron name from the
Geomagnetic Polarity Time Scale, and 'Maastrichtian' and
'Jurassic' are names from the International Geological
Time Scale. Since different relative geologic time scales
are often not aligned, multiple geologic dates may need
to be specified. For example, the Geomagnetic Polarity
Time Scale chron 'C29r', at the K/T boundary lies in both
the 'Maastrichtian' and the 'Danian' stages from the
International Geological Time Scale, thus if you were
documenting this event using the International Geological
Time Scale, both 'Maastrichtian' and 'Danian' should be
included here.
Lineage:
FGDC-STD-001.1-1999
/metadata/time_period_information/rngdates/endgeol
|
geographicDescription |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Description of geographic extent
Summary:
Short description of the geographic areal domain of the data set.
Description:
A geographic extent description is especially important when the
extent of the data set is not well described by the
"Bounding_Rectangle_Coordinates", or in the case of data which
are not specifically geospatial, to provide a geographic setting
for the item being documented. Assuming the
"Bounding_Rectangle_Coordinates" do not adequately describe the
extent of the data set, the discrepancy can be identified and
described in this data element. If the item being documented is
not specifically geospatial, the "Bounding_Rectangle_Coordinates"
can define a general polygon, such as a rectangle around a
country, with this "Description_of_Geographic_Extent" element
containing a disclaimer concerning the
"Bounding_Rectangle_Coordinates" and/or further detail concerning
the geographic area of concern for the item being documented. For
example, a study of the diseases of salmon may not have a
specific geographic extent associated with it, but the salmon
involved in the study were collected in Washington and Oregon
states, thus the "Bounding_Rectangle_Coordinates" might form a
general rectangle around the states of Washington and Oregon, but
the "Description_of_Geographic_Extent" might describe the fact
that the extent within Washington and Oregon included only
certain rivers within those states. This data element differs
from the standard data element "Place_Keyword" in that it allows
a free text description of the geographic extent, rather than
just a list of words or phrases useful as an index of location
names associated with the data set.
Example:
Examples include, "Manistee River watershed", "extent of 7 1/2
minute quads containing any property belonging to Yellowstone
National Park", or "ponds and reservoirs larger than 2 acres in
Jefferson County, Colorado". This is especially important when the
extent of the data set is not well described by the
"Bounding_Rectangle_Coordinates".
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
description_of_geographic_extent
|
boundingCoordinates |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Bounding coordinates
Summary:
The 4 points (latitude and longitude pairs) that define a
bounding box on the earth's surface.
Description:
The limits of coverage of a data set expressed by latitude
and longitude values in the order western-most, eastern-most,
northern-most, and southern-most. For data sets that include
a complete band of latitude around the earth, the West
Bounding Coordinate shall be assigned the value -180.0, and
the East Bounding Coordinate shall be assigned the value 180.0
If your bound area is a single point, use only the
northBoundingCoordinate and eastBoundingCoordinate to define
your point. westBoundingCoordinate and southBoundingCoordinate
are optional for this purpose.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates
|
westBoundingCoordinate |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
West bounding coordinate
Summary:
Western-most coordinate of the limit of coverage for a
bounding box, expressed in degrees of longitude.
Description:
The west bounding coordinate field defines the western-most
point of the bounding box that is being described.
This longitude coordinate should be expressed in decimal
fractions of degrees. Whole degrees of longitude shall be
represented by a three-digit decimal number ranging from 0
through 180. When a decimal fraction of a degree is
specified, it should be separated from the whole number of
degrees by a decimal point. Decimal fractions of a degree
may be expressed to the precision desired. Longitudes east
of the prime meridian shall be specified by a plus sign (+),
or by the absence of a minus sign (-), preceding the three
digits designating degrees of longitude. Longitudes west of
the meridian shall be designated by minus sign (-) preceding
the three digits designating degrees. A point on the prime
meridian shall be assigned to the Eastern Hemisphere. A
point on the 180th meridian shall be assigned to the Western
Hemisphere. One exception to this last convention is
permitted. For the special condition of describing a band of
latitude around the earth, the East Bounding Coordinate data
element shall be assigned the value +180 (180) degrees.
Example:
'-118.25', '+25', '45.247'
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/west_bounding_coordinate
|
eastBoundingCoordinate |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
East bounding coordinate
Summary:
Eastern-most coordinate of the limit of coverage of a
bounding box, expressed in degrees of longitude.
Description:
The east bounding coordinate field defines the eastern-most
point of the bounding box that is being described.
This longitude coordinate should be expressed in decimal
fractions of degrees. Whole degrees of longitude shall be
represented by a three-digit decimal number ranging from 0
through 180. When a decimal fraction of a degree is
specified, it should be separated from the whole number of
degrees by a decimal point. Decimal fractions of a degree
may be expressed to the precision desired. Longitudes east
of the prime meridian shall be specified by a plus sign (+),
or by the absence of a minus sign (-), preceding the three
digits designating degrees of longitude. Longitudes west of
the meridian shall be designated by minus sign (-) preceding
the three digits designating degrees. A point on the prime
meridian shall be assigned to the Eastern Hemisphere. A
point on the 180th meridian shall be assigned to the Western
Hemisphere. One exception to this last convention is
permitted. For the special condition of describing a band of
latitude around the earth, the East Bounding Coordinate data
element shall be assigned the value +180 (180) degrees.
Example:
'-118.25', '+25', '45.247'
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/east_bounding_coordinate
|
northBoundingCoordinate |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
North bounding coordinate
Summary:
Northern-most coordinate of the limit of coverage expressed
in latitude.
Description:
The north bounding coordinate field defines the
northern-most point of the bounding box that is being
described. This latitude coordinate should be expressed in
decimal fractions of degrees. Whole degrees of latitude
shall be represented by a two-digit decimal number ranging
from 0 through 90. When a decimal fraction of a degree is
specified, it shall be separated from the whole number of
degrees by a decimal point. Decimal fractions of a degree
may be expressed to the precision desired. Latitudes north
of the equator shall be specified by a plus sign (+), or by
the absence of a minus sign (-), preceding the two digits
designating degrees. Latitudes south of the Equator shall
be designated by a minus sign (-) preceding the two digits
designating degrees. A point on the Equator shall be
assigned to the Northern Hemisphere. Any spatial address
with a latitude of +90 (90) or -90 degrees will specify the
position at the North or South Pole, respectively.
Example:
'-18.44', '+44.35', '86'
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/north_bounding_coordinate
|
southBoundingCoordinate |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
South bounding coordinate
Summary:
Southern-most coordinate of the limit of coverage expressed
in latitude.
Description:
The south bounding coordinate field defines the
northern-most point of the bounding box that is being
described. This latitude coordinate should be expressed in
decimal fractions of degrees. Whole degrees of latitude
shall be represented by a two-digit decimal number ranging
from 0 through 90. When a decimal fraction of a degree is
specified, it shall be separated from the whole number of
degrees by a decimal point. Decimal fractions of a degree
may be expressed to the precision desired. Latitudes north
of the equator shall be specified by a plus sign (+), or by
the absence of a minus sign (-), preceding the two digits
designating degrees. Latitudes south of the Equator shall
be designated by a minus sign (-) preceding the two digits
designating degrees. A point on the Equator shall be
assigned to the Northern Hemisphere. Any spatial address
with a latitude of +90 (90) or -90 degrees will specify the
position at the North or South Pole, respectively.
Example:
'-18.44', '+44.35', '86'
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/south_bounding_coordinate
|
boundingAltitudes |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Bounding altitudes
Summary:
The limits of coverage of a data set expressed by altitude.
Description:
The bounding altitude field is intended to contain
altitudinal (elevation) measurements in relation to the
bounding box being described. It allows for minimum and
maximum altitude fields, as well as a field for the units of
measure. The combination of these fields provide the
vertical extent information for the bounding box. The units
should refer to an accepted datum as the baseline.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/bounding_altitudes
|
altitudeMinimum |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Minimum altitude
Summary:
The minimum altitude extent of coverage.
Description:
The minimum altitude extent of coverage for the
bounding box that is being described. The minimum
altitude should be in reference to a known datum,
which should be described in the altitude units field.
Example:
'12', '100.6' (e.g meters above Mean Lowest Low Water)
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/bounding_altitudes/
altitude_minimum
|
altitudeMaximum |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Maximum altitude
Summary:
The maximum altitude extent of coverage.
Description:
The maximum altitude extent of coverage for the
bounding box that is being described. The maximum
altitude should be in reference to a known datum,
which should be described in the altitude units field.
Example:
'12', '100.6' (e.g meters above Mean Lowest Low Water)
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/bounding_altitudes/
altitude_maximum
|
altitudeUnits |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Units of altitude
Summary:
Units in which altitude is measured.
Description:
Units in which altitude is measured. This field should
be in relation to a known datum which is described in
the units.
Example:
Meters (above Mean Lowest Low Water)
Lineage:
FGDC-STD-001.1-1999
/metadata/identification_information/spatial_domain/
bounding_coordinates/bounding_altitudes/
altitude_distance_units
|
datasetGPolygon |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Polygon data set
Summary:
Data Set G-Polygon coordinates defining the outline of an
area covered by a data set.
Description:
Data Set G-Polygon coordinates defining the outline of an
area covered by a data set.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon
|
datasetGPolygonOuterGRing |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A choice of ( |
gRingPoint | Required | Multiple Times |
OR
|
gRing | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Outer polygon
Summary:
Description:
Data Set G-Polygon Outer G-Ring, the closed
nonintersecting boundary of an interior area.
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/dataset_g_polygon_outer_g_ring
|
datasetGPolygonExclusionGRing |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A choice of ( |
gRingPoint | Required | Multiple Times |
OR
|
gRing | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Exclusion polygon
Summary:
Description:
Data Set G-Polygon Exclusion G-Ring, the closed
nonintersecting boundary of a void area (or hole in an
interior area).
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/dataset_g_polygon_exclusion_g_ring
|
gRingPoint |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
gRingLatitude | Optional | Multiple Times |
gRingLongitude | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
G-Ring point
Summary:
Description:
A single geographic location.
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/g_ring_point
|
gRingLatitude |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
G-Ring Latitude
Summary:
Description:
The latitude of a point of the g-ring.
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/g_ring_point/g_ring_polygon_outer_g_ring/
g_ring_latitude
|
gRingLongitude |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
G-Ring Longitude
Summary:
Description:
The longitude of a point of the g-ring.
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/g_ring_point/g_ring_polygon_outer_g_ring/
g_ring_longitude
|
gRing |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
G-Ring
Summary:
Description:
A set of ordered pairs of floating-point numbers, separated by commas,
in which the first number in each pair is the longitude of a point and
the second is the latitude of the point. Longitude and latitude are
specified in decimal degrees with north latitudes positive and south
negative, east longitude positive and west negative
Example:
Lineage:
FGDC-STD-001-1998:
/metadata/identification_information/spatial_domain/
dataset_g_polygon/g_ring
|
keywordsTaxon |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Taxonomic Keyword Information
Summary:
Taxonomic Keywords and related taxonomic thesaurii.
Description:
The taxonomic keyword fields provide locations for keywords and
the thesaurii from which they are formally defined that are
specific to the taxonomic extent of the dataset or resource.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/keywords_taxon
|
taxonomicKeywordThesaurus |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxonomic keyword thesaurus
Summary:
Reference to eml-attribute.htmla formally registered
thesaurus or similar authoritative source of taxonomic
keywords.
Description:
Reference to a formally registered thesaurus or similar
authoritative source of taxonomic keywords.
Example:
BIOSIS Systematic Thesaurus
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
keywords_taxon/taxonomic_keyword_thesuarus
|
taxomomicKeywords |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxonomic keyword
Summary:
Keywords or phrases describing the taxonomy of the dataset.
Description:
Common use words or phrases describing the taxonomy covered
by the data set.
Example:
Mammalia
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
keywords_taxon/taxonomic_keywords
|
taxonomicSystem |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Taxonomic system
Summary:
Documentation of taxonomic sources, procedures, and treatments.
Description:
Documentation of taxonomic sources, procedures, and treatments.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/taxonomic_system
|
classificationSystem |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Classification system/authority
Summary:
Information about the classification system or
authority used.
Description:
Information about the classification system or
authority used.
Example:
Flora of North America
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/classification_system_authority
|
classificationSystemCitation |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
cit:citation | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxonomic citation
Summary:
Description:
Relevant literature for documenting the used
classification system.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/classification_system_authority/
classification_system_citation
|
classificationSystemModifications |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Classification system modification
Summary:
Description:
A description of any modifications or exceptions made
to the classification system or authority used.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/classification_system_authority/
classification_system_modifications
|
identificationReference |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
cit:citation | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Non-authoritative citation
Summary:
Description:
Information on any nonauthoritative materials (e.g. field
guides) useful for reconstructing the actual
identification process.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/identification_reference
|
identifierName |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
originator | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Identifier's Name
Summary:
Description:
Information about the individual(s) responsible for the
identification(s) of the specimens or sightings, etc.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/identifier
|
originator |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Originator
Summary:
A person or organization asociated with this resource.
Description:
The 'originator' element provides the full name of the
person, organization, or position associated with the
resource. Typically, the originator role is set to
"owner" to indicate the list of parties who "own" the
resource, but other roles such as "principal
investigator", "author", and "editor" are provided.
Example:
Please see the examples within the sub fields for
the responsible party.
Lineage:
This element was derived from elements described in
the FGDC-STD-001.1-1999 standard
(nbii-fgdc-std-001.1-1999)
|
taxonomicProcedures |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxonomic procedures
Summary:
Description:
Description of the methods used for the taxonomic
identification.
Example:
specimen processing, comparison with museum materials,
keys and key characters, chemical or genetic analyses
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/taxonomic_procedures
|
taxonomicCompleteness |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxonomic completeness
Summary:
Description:
Information concerning the proportions and treatment of
unidentified materials ; estimates of the importance,
and identities of misidentifications, uncertain
determinations, synonyms or other incorrect usages; taxa
not well treated or requiring further work; and
expertise of field workers.
Example:
materials sent to experts, and not yet determined
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/taxonomic_completeness
|
vouchers |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
specimen | Optional | Multiple Times |
repository | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Specimen information
Summary:
Description:
Information on the types of specimen, the repository,
and the individuals who identified the vouchers.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/vouchers
|
specimen |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Specimen type
Summary:
Description:
A word or phrase describing the type of
specimen collected.
Example:
herbarium specimens, blood
samples, photographs, individuals, or batches
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/vouchers/specimen
|
repository |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
originator | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Storage location of specimen
Summary:
Description:
Information about the curator or contact
person and/or agency responsible for the
specimens.
Example:
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_system/vouchers/repository
|
originator |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Originator
Summary:
A person or organization asociated with this
resource.
Description:
The 'originator' element provides the full name
of the person, organization, or position
associated with the resource. Typically, the
originator role is set to "owner" to indicate
the list of parties who "own" the resource, but
other roles such as "principal investigator",
"author", and "editor" are provided.
Example:
Please see the examples within the sub fields
for the responsible party.
Lineage:
This element was derived from elements described
in the FGDC-STD-001.1-1999 standard
(nbii-fgdc-std-001.1-1999)
|
generalTaxonomicCoverage |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
General taxonomic coverage
Summary:
A description of the range of taxa addressed in the data set or
collection.
Description:
A description of the range of taxa addressed in the data set or
collection.
Example:
"All vascular plants were identified to family or species,
mosses and lichens were identified as moss or lichen."
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
general_taxonomic_coverage
|
taxonomicClassification |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Taxonomic classification
Summary:
Information about the range of taxa addressed in the data set or
collection.
Description:
Information about the range of taxa addressed in the data set or
collection. It is recommended that one provide information starting
from the taxonomic rank of kingdom, to a level which reflects the
data set or collection being documented. The levels of Kingdom,
Division/Phylum, Class, Order, Family, Genus, and Species should be
included as ranks as appropriate. Because the taxonomic ranks are
hierarchical, the Taxonomic Classification field is self-referencing
to allow for an arbitrary depth of rank, down to species.
Example:
The Taxonomic Classification field consists of a sequence of 4 fields:
taxonomic rank, taxonomic rank value, common name, and finally
Taxonomic Classification (self-referencing). Please see the
sub-fields for specific examples.
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_classification
|
taxonRankName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxon rank name
Summary:
The name of the taxonomic rank for which the Taxon rank value
is provided.
Description:
The name of the taxonomic rank for which the Taxon rank value
is provided. This field allows for the name one of the accepted
levels of Taxa.
Example:
'Kingdom', 'Division/Phylum', 'Class', 'Order',
'Family', 'Genus', and 'Species'
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_classification/taxon_rank_name
|
taxonRankValue |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Taxon rank value
Summary:
The name representing the taxonomic rank of the taxon
being described.
Description:
The name representing the taxonomic rank of the taxon
being described. The values included may be referenced from an
authoritative source such as the Integrated Taxonomic
Information Sytem (ITIS)in the U.S. (http://www/itis.usda.gov)
and in Canada (http://sis.agr.gc.ca/pls/itisca/taxaget). Also,
Species2000 is another source of taxonomic information, found at
(http://www.sp2000.org)
Example:
Acer would be an example of a genus rank value, and rubrum would
be an example of a species rank value, together indicating the
common name of red maple. It is recommended to start with
Kingdom and include ranks down to the most detailed level
possible.
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_classification/taxon_rank_value
|
commonName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Common name
Summary:
Specification of applicable common names.
Description:
Specification of applicable common names. These common names
may be general descriptions of a group of organisms if
appropriate.
Example:
insects, vertebrate, grasses, waterfowl, vascular plants, red
maple.
Lineage:
FGDC-STD-001.1-1999:
/metadata/identification_information/taxonomy/
taxonomic_classification/applicable_common_name
|
Attribute Definitions:
|
Complex Type Definitions:
|
TemporalCoverage |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Temporal coverage
Summary:
Temporal coverage information.
Description:
The temporal coverage fields are intended to be used in describing
the date and time of an event. It allows for three general
descriptions: a single date/time, multiple date/times, and a range
of date/times.
Example:
Please see the individual sub fields for specific examples.
Lineage:
The TemporalCoverage complex type was introduced
into EML 1.4. From FGDC-STD-001.1-1999
|
GeographicCoverage |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Geographic coverage
Summary:
Geographic coverage information.
Description:
Geographic Coverage is a container for spatial information about a
a project, a resource, or an entity within a resource.
Example:
Please see the individual sub-elements for specific examples.
Lineage:
The GeographicCoverage complex type was derived from the eml-entity
module in EML 1.4.
|
TaxonomicCoverage |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Taxonomic coverage
Summary:
Taxonomic coverage information.
Description:
Taxonomic Coverage is a container for taxonomic information about a
a project, a resource, or an entity within a resource.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
The TaxonomicCoverage complex type was introduced in EML 2 and
derived from the NBII taxonomy element.
|
Simple Type Definitions:
|