| ### Showing:
Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by

Element irm:geospatialCoverage

Namespace | urn:us:gov:ic:irm
Annotations | ? ded:CategoryDescription: Geographic place names or coordinates that relate to the resource, such as a jurisdiction, point, area, or volume on land, in space, or at sea. ded:CategorySource: DCMI: spatial, v. 002; ISO 19115:2003; MARC 342 Geospatial Reference Data; Time-Space-Position Information (TSPI) version 2.0; Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard ded:CategoryComment: The obligation of this category is selected to show metadata creators that they must determine whether the geographic reference subject matter of the resource is applicable for discovery purposes. The geospatialCoverage element structure of prior versions of DDMS (now IRM) has been revised and replaced with Time-Space-Position Information (TSPI) version 2.0-compliant structures. This permits the IRM definition of geospatial concepts to be consistent with standards used across the DoD and the international standards community. geospatialCoverage has a complex structure of elements and attributes. geospatialCoverage includes several optional attributes, and additionally can be marked according to SMP guidelines. There can be an unbounded number of geospatialCoverage elements, each of which must have at least one of geographicIdentifier, boundingGeometry, or postalAddress, and can include more than one of any of these elements as long as they address the same general location. A geographicIdentifier element may include a name, region, countryCode, subDivisionCode, or a facilityIdentifier, the last three being elements with attributes. There can be multiple geographicIdentifier elements of all types, within a geographicIdentifier element. A boundingGeometry element consists of one or more elements using a number of permitted Polygons (Polygon, Envelope, Circle, Ellipse, or Point), and can include multiples of each element. The ddms:boundingBox and ddms:verticalExtend of previous versions of DDMS had been deprecated and replaced with tspi:envelope, while additional geometries defined in TSPI have been included. Note that this is a subset of the polygons defined in TSPI. A postalAddress element uses the AbstractPhysicalAddress structure defined in TSPI. TSPI draws upon the Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard. The technique used in the FGDC standard is the application of substitution groups for the AbstractPhysicalAddress element. Detailed information is available in the FGDC standard. The intent of the boundingGeometry elements (as part of the geospatial coverage category) is to provide a description of the frame of reference for the coordinates in a data set. To work with a geographic data set, a user must be able to identify how location accuracy has been affected through the application of a geospatial reference method, thus enabling the user to manipulate the data set to recover location accuracy. If BE Number is supplied, no other elements are required to be supplied in the Geospatial Coverage category. Note: The National Geospatial Intelligence Agency has taken the lead within the Department of Defense to develop an implementation of ISO 19136:2007 (GML). This standard is widely adopted and implemented within the Geospatial Intelligence commerical and user communities. NGA's strategy for the National System for Geospatial Intelligence is to adopt, profile (and extend) and use relevant standards. When encoding geospatial coordinates, the following guidelines should be followed: 1. Latitude shall be in decimal degrees in the range greater than equal -90 degrees and less than equal +90 degrees. 2. North latitudes shall be positive, south latitudes shall be negative. 3. Longitude shall be in decimal degrees in the range greater than -180 degrees and less than +180 degrees; note that there are two equally acceptable values of longitude for the meridian opposite the prime meridian. 4. East longitudes shall be positive, west longitudes shall be negative. 5. Only the element tspi:Point shall be used to encode a geographic point location as either: (1) two decimal values in the order of latitude then longitude (no commas) when WGS84E_2D, or (2) three decimal values in the order latitude then longitude then height above ellipsoid (no commas) when using the WGS84E_3D CRS. The intent of geospatial coverage is to provide logically and semantically consistent information. Flexibility in the specification does not absolve end users of geospatial coverage from expressing information in a meaningful manner. Users should ensure that combinations of elements are appropriately relatable, consistent, meaningful, and useful for enterprise discovery. The geospatialCoverage element can be marked according to SMP guidelines. ded:Definition: An element containing a geographic indication of one or more places or facilities that relate to the resource. A geographic indication of one or more places or facilities that relate to the resource. See IRM Spec Category: Geospatial Coverage. ded:Obligation: (Mandatory Unless Not Applicable) ded:Comment: There can be an unbounded number of geospatialCoverage elements, each of which must have at least one child element of geographicIdentifier, boundingGeometry, or postalAddress, and can include more than one of any or these elements.
Diagram |
Type | irm:PlaceType
Properties |
content | complex
Used by |
Complex Type | irm:ICResourceMetadataType
Model | irm:geographicIdentifier | irm:boundingGeometry | irm:postalAddress
Children | irm:boundingGeometry , irm:geographicIdentifier , irm:postalAddress
Instance |
    <irm:geospatialCoverage irm:order="" irm:precedence="" xmlns:irm="urn:us:gov:ic:irm">
      <irm:geographicIdentifier>{1,1}</irm:geographicIdentifier>
      <irm:boundingGeometry>{1,1}</irm:boundingGeometry>
      <irm:postalAddress>{1,1}</irm:postalAddress>
    </irm:geospatialCoverage>
Attributes |
QName | Type | Use | Annotation
--- | --- | --- | ---
irm:order | xsd:int | optional | ded:Definition: An attribute of geospatialCoverage that specifies a user-defined order of an element (specifically when multiple countryCode and subDivisionCode elements exist) within the given IRM resource. Specifies a user-defined order of an element within the given document. All elements in the document which specify the order attribute should be interpreted as entries in a single, ordered list even though they may appear on different elements. Values must be sequential, starting at 1, and may not contain duplicates. ded:Obligation: (Optional) ded:Comment: This is an integer entry. Values must be sequential, starting at 1, and may not contain duplicates.
irm:precedence | irm:simpleTokenType | optional | ded:Definition: An attribute of geospatialCoverage that states the priority claimed or received as a result of preeminence. When CountryCode has a value, this attribute is used to distinguish the primary focus when a described data asset covers two or more countries. Priority claimed or received as a result of preeminence. When used on the element CountryCode, this attribute is used to distinguish the primary focus when an intelligence product covers two or more countries. Permissible values are Primary, Secondary. ded:Obligation: (Optional) ded:Comment: This is a text field. Normal values are Primary or Secondary. Priority claimed or received as a result of preeminence. When used on the element CountryCode, this attribute is used to distinguish the primary focus when an intelligence product covers two or more countries. Permissible values are Primary, Secondary.
Source |
    <xsd:element name="geospatialCoverage" type="irm:PlaceType">
      <xsd:annotation>
        <xsd:documentation>&#x2028;
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:CategoryDescription">ded:CategoryDescription: Geographic place names or coordinates that relate to the resource, such as a jurisdiction, point, area, or volume on land, in space, or at sea.</p>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:CategorySource">ded:CategorySource: DCMI: spatial, v. 002; ISO 19115:2003; MARC 342 Geospatial Reference Data; Time-Space-Position Information (TSPI) version 2.0; Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard</p>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:CategoryComment">ded:CategoryComment: The obligation of this category is selected to show metadata creators that they must determine whether the geographic reference subject matter of the resource is applicable for discovery purposes. The geospatialCoverage element structure of prior versions of DDMS (now IRM) has been revised and replaced with Time-Space-Position Information (TSPI) version 2.0-compliant structures. This permits the IRM definition of geospatial concepts to be consistent with standards used across the DoD and the international standards community. geospatialCoverage has a complex structure of elements and attributes. geospatialCoverage includes several optional attributes, and additionally can be marked according to SMP guidelines. There can be an unbounded number of geospatialCoverage elements, each of which must have at least one of geographicIdentifier, boundingGeometry, or postalAddress, and can include more than one of any of these elements as long as they address the same general location. A geographicIdentifier element may include a name, region, countryCode, subDivisionCode, or a facilityIdentifier, the last three being elements with attributes. There can be multiple geographicIdentifier elements of all types, within a geographicIdentifier element. A boundingGeometry element consists of one or more elements using a number of permitted Polygons (Polygon, Envelope, Circle, Ellipse, or Point), and can include multiples of each element. The ddms:boundingBox and ddms:verticalExtend of previous versions of DDMS had been deprecated and replaced with tspi:envelope, while additional geometries defined in TSPI have been included. Note that this is a subset of the polygons defined in TSPI. A postalAddress element uses the AbstractPhysicalAddress structure defined in TSPI. TSPI draws upon the Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard. The technique used in the FGDC standard is the application of substitution groups for the AbstractPhysicalAddress element. Detailed information is available in the FGDC standard. The intent of the boundingGeometry elements (as part of the geospatial coverage category) is to provide a description of the frame of reference for the coordinates in a data set. To work with a geographic data set, a user must be able to identify how location accuracy has been affected through the application of a geospatial reference method, thus enabling the user to manipulate the data set to recover location accuracy. If BE Number is supplied, no other elements are required to be supplied in the Geospatial Coverage category. Note: The National Geospatial Intelligence Agency has taken the lead within the Department of Defense to develop an implementation of ISO 19136:2007 (GML). This standard is widely adopted and implemented within the Geospatial Intelligence commerical and user communities. NGA's strategy for the National System for Geospatial Intelligence is to adopt, profile (and extend) and use relevant standards. When encoding geospatial coordinates, the following guidelines should be followed: 1. Latitude shall be in decimal degrees in the range greater than equal -90 degrees and less than equal +90 degrees. 2. North latitudes shall be positive, south latitudes shall be negative. 3. Longitude shall be in decimal degrees in the range greater than -180 degrees and less than +180 degrees; note that there are two equally acceptable values of longitude for the meridian opposite the prime meridian. 4. East longitudes shall be positive, west longitudes shall be negative. 5. Only the element tspi:Point shall be used to encode a geographic point location as either: (1) two decimal values in the order of latitude then longitude (no commas) when WGS84E_2D, or (2) three decimal values in the order latitude then longitude then height above ellipsoid (no commas) when using the WGS84E_3D CRS. The intent of geospatial coverage is to provide logically and semantically consistent information. Flexibility in the specification does not absolve end users of geospatial coverage from expressing information in a meaningful manner. Users should ensure that combinations of elements are appropriately relatable, consistent, meaningful, and useful for enterprise discovery. The geospatialCoverage element can be marked according to SMP guidelines.</p>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:Definition">ded:Definition: An element containing a geographic indication of one or more places or facilities that relate to the resource. A geographic indication of one or more places or facilities that relate to the resource. See IRM Spec Category: Geospatial Coverage.</p>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:Obligation">ded:Obligation: (Mandatory Unless Not Applicable)</p>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA" data-ded="ded:Comment">ded:Comment: There can be an unbounded number of geospatialCoverage elements, each of which must have at least one child element of geographicIdentifier, boundingGeometry, or postalAddress, and can include more than one of any or these elements.</p>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
Schema location | IC-IRM.xsd Copy and paste this link to your file browser, clicking the link MAY open in the browser. Opening in an XML aware editor is best.

## This document has been approved for Public Release by the Office of the Director of National Intelligence. See Distribution Notice for details. Click Here