DCC Geospatial Data Standard V1

DCC Geospatial Data Standard

V1.07

August 19, 2011

DCC Geospatial Data Standard V1.07 i

DCC Geospatial Data Standard – V1.07 August 2, 2011

1 General ................................................................................................................................ 2

1.1 Introduction ...................................................................................................................... 2 1.2 Data Sources ................................................................................................................... 2 1.3 Data Delivery and Exchange ....................................................................................... 2 1.4 Coordinate System ......................................................................................................... 3 1.5 Feature Type .................................................................................................................... 3

2 Geospatial Data – Authored by Contractors ................................................................... 4 2.1 Layers ................................................................................................................................ 4 2.2 Software Format .............................................................................................................. 4 2.3 Feature Attributes ............................................................................................................ 4 2.4 Data Currentness ............................................................................................................ 4 2.5 Data Accuracy................................................................................................................ 5 2.6 MetaData ......................................................................................................................... 6

3 Geospatial Data – Sourced ............................................................................................... 7 3.1 Layers ................................................................................................................................ 7 3.2 Software Format .............................................................................................................. 7 3.3 Feature Attributes ............................................................................................................ 7 3.4 Data Currentness ............................................................................................................ 7 3.5 Data Accuracy................................................................................................................ 8 3.6 Metadata ......................................................................................................................... 9

Appendix 1 – Elements of ISO 19115 that comprise the DCC Metadata Standard ........... 10 Appendix 2 – Metadata Keywords ......................................................................................... 17

DCC/DND Geospatial Data Standard V1.07 Page 2 of 20

1 General

1.1 Introduction

Defence Construction Canada (DCC) places high importance on the quality of geospatial data provided to support its partner, Department of National Defence (DND). The following sections describe the standards that all outside agencies must meet when submitting geospatial data deliverables. Geospatial data submitted to DCC that fails to meet the following guidelines may be rejected or requested to be re-submitted as per the requirements outlined in this document.

1.2 Data Sources

Geospatial data submitted by a Contractor can be categorized by data that is either:

1. Created directly by a contracted agency OR

2. Sourced from an outside organization (commercial, federal, provincial, municipal geospatial data supplier).

Since DCC understands that Contractors are not able to control the quality of information sourced from outside agencies, the DCC Geospatial Data Standard has been purposely organized to provide Contractors with specific guidelines to guide the compilation of information from the two sources itemized above. Specifications that pertain to information collected by the contractor are found in Section 2.0, GeospatialData – Authored by Contractors. Specifications that pertain to information collected from an outside organization or data supplier are found in Section 3.0, Geospatial Data – Sourced from Outside Organizations.

1.3 Data Delivery and Exchange

The exchange of geospatial data between DCC and outside organizations will be carried out in the following sequence:

1. The Contractor will carry out the collection of geospatial data as per the described DCC Geospatial Data Standard, and when applicable a specific layer and attribute standard (see section 2.3).

2. At any point, DCC may require the Contractor to submit a sample subset of the data being collected to ensure it meets the deliverable standards prior to the accepted deliverable date. This helps to identify data issues before the major final deliverable is due.

3. All final geospatial data deliverables will be uploaded to the DCC FTP Site if not exceeding 200MB in combined size. Deliverables exceeding 200MB in size must be delivered on static media such as a CD or DVD.


1.4 Coordinate System

All data sourced or created (raster or vector) shall be properly georeferenced. All data created for sites in Canada must be in Universal Transverse Mercator (UTM) projection, with the appropriate zone (e.g. zone 18), using the Canadian Spatial Reference System North American Datum – 1983 (CSRS Nad83). Data that is sourced shall be delivered in its original coordinate system and projection and should not be reprojected. All data created at a national level must utilize the CSRS North American Datum – 1983 (CSRS Nad83).

1.5 Feature Type

The manner in which features are collected relates to how these features will be analyzed or modeled within a GIS framework. Some features can be mapped as a point, line, or polygon, however, this decision affects how the feature can be analyzed singularly or with other features. Therefore, the following table explains which feature type (point, line, and polygon) must be used to create and collect geospatial data for this project*:

GIS Layer GIS Feature Type Jurisdictional Information Polygon Terrain Information Contour Polyline

Spot Elevation - Point DEM/DTM – Raster Surface

Hydrologic Information Water Body – Polygon Water Course – Polyline Areas – Polygon Flow Direction – Point

Transportation Infrastructure Centrelines – Polyline Pavement, easement, etc. – Polygon

Underground Infrastructure Lines – Polylines Valves, junctions, etc. – Point

Land Use Polygon Land Ownership Polygon Vegetation Polygon Environmental Information Contaminated areas – Polygon

Sampling locations – Point Soil Information Polygon Geologic Information Polygon Terrain Slope/Aspect Raster Surface

* this is not an exhaustive layer list but a general guideline


2 Geospatial Data – Authored by Contractors

This section describes the specifications that Contractors must adhere to when producing proprietary information on behalf of DND. This category of information includes the suite of features that have been produced in any geospatial format through surveys, interpretation, digitization and mapping.

2.1 Layers

Within the context of this document, a ‘layer’ refers to a thematic representation of geographic features and their attributes. Examples might include roads, rivers, buildings, or political boundaries. All the features in a layer share the same coordinate system, are located within a common geographic extent, and have the same type of geometry (point, line, or polygon).

2.2 Software Format

All geospatial data authored by a Contractor will be in one of the following digital formats:

Vector geospatial data ESRI Geodatabase* *An ESRI File Geodatabase is the preferred spatial data format for submissions.

Raster geospatial data GeoTIFF - imagery TIFF and TFW – imagery LizardTech (MrSID) – imagery ECW – imagery ESRI Grid – dem, hillshade, surfaces, etc.

2.3 Feature Attributes

Within the context of this document, the term ‘feature attributes’ describes the array of non-spatial information that relates to a geographic feature in a GIS. DCC reserves the right to request which feature attributes and attribute values must be present in all datasets. If applicable, DCC will provide an independent document (data dictionary) and/or a published data model to describe the specific details relating to the content and structure of all datasets within a statement or scope of work.

2.4 Data Currentness

The dynamic nature of information causes it to become outdated immediately after it has been collected. Since this is a very real factor, efforts must be made on the part of the contractor to lessen this effect as much as possible. Information being collected by the Contractor is expected to be reflective of the date that it was collected.


2.5 Data Accuracy

The absolute external positional accuracy of geospatial data is given as the difference between a feature’s position in the dataset and its real ground position, measured in reference to the coordinate reference system. The level of accuracy for data authored by a contractor will be dictated by the type of feature(s) to be collected, and the prescribed method of collection. Generally speaking, the authored data delivered to DCC will fall into three categories: Data captured with survey-grade GPS The horizontal positional accuracy requirement for all data collected via survey-grade GPS is <25 cm. If vertical coordinate measurements are being captured then the vertical positional accuracy requirement is <45cm. The dataset must be accompanied with metadata that includes a statement of the horizontal accuracy, and, where applicable, the vertical accuracy. The statement should be similar to the following:

GPS data were differentially corrected using Trimble base station data. The accuracy of the locations collected range from less than 1 cm to 25 cm depending on the number of satellites in view, the position of satellites in relation to each other, the strengths of the satellite signals and the distance of the base station from the GPS receiver. The positions are typically accurate to a centimeter or less.

Data captured with a recreational (single-point-positioning) GPS The horizontal positional accuracy requirement for all data collected via recreational GPS is <10m. If vertical coordinate measurements are being captured then the vertical positional accuracy requirement is <16m. Data in this category must be accompanied with metadata that includes a statement of the horizontal accuracy, and, when applicable, the vertical accuracy. The statement should be similar to the following:

Waypoints were collected using a Garmin GPSmap 60Cx unit. The unit is a 12 channel SiRFstar III™ high-sensitivity GPS receiver (WAAS-enabled), which continuously tracks and uses up to 12 satellites to compute and update plotted positions. The accuracy of the unit is <10 metres 95% typical.

Data captured from multiple sources and/or sources of unknown accuracy Data captured from multiple data sources, including maps of unknown accuracy, are not held to a specific horizontal or vertical accuracy standard. Nevertheless, the contractor must provide a statement in the metadata reporting that the accuracy cannot be assessed along with an explanation why. When available, the maximum horizontal/vertical accuracy value extracted from all sources should be provided. The metadata must also include a detailed description of the process steps (lineage) and list all source data. DCC reserves the right to request which level of accuracy is required based on the types of features being captured. If applicable, DCC will provide an independent


document to describe the accuracy requirements of all datasets within a statement or scope of work.

2.6 MetaData

Each independent information source, or geospatial layer, provided to DCC will be accompanied with metadata. Failure to provide metadata for each geospatial layer will inevitably lead to a failure in data quality. The specific version of the metadata standard deployed by DCC is congruent with the standard utilized by DND Mapping and Charting Establishment (MCE). MCE is using the North American Profile (NAP) of the ISO 19115 geospatial metadata standard and is implementing this profile in accordance with the ISO 19139 XML implementation specification. Appendix 1 lists the minimum metadata descriptors that must be present for all geospatial datasets submitted to DCC, and is in accordance with the ISO 19115 implementation specification. Metadata can be delivered in the ESRI ISO format (version 10.0 or higher) or in XML format as per the ISO 19139 XML implementation specification (only if working with a version of ArcGIS previous to 10). Please note that while some of the metadata elements listed are optional in the ISO 19115 metadata standard, DCC requires that they be provided unless otherwise indicated. In order to comply with these ISO standards, contractors can use the metadata editor included in ArcCatalog of the ArcGIS software package version10.0 or higher. If contractors have an older version of ArcGIS, DCC recommends using the GeoNetwork Opensource software available at http://geonetwork-opensource.org, but Contractors may use other software to comply.


3 Geospatial Data – Sourced

This section describes the specifications that Contractors must adhere to when providing geospatial data sourced from agencies other than themselves (commercial, federal, provincial, municipal data providers).

3.1 Layers

Independent data providers most often maintain their own data models and structures that have been documented. DCC insists that Contractors do not modify or manipulate layer nomenclatures inherent in these sourced data sets to ensure their integrity.

3.2 Software Format

If the geospatial data is sourced from an outside agency, the information shall be provided in its original format.

3.3 Feature Attributes

Independent data providers most often maintain their own data models and structures which have been well documented. DCC requires the Contractor to obtain and provide the data dictionary for any sourced datasets unless it is already provided in the metadata. A data dictionary is a document outlining the description of fields and values contained in each field. DCC insists that Contractors do not modify or manipulate feature attribute structures inherent in these sourced datasets to ensure their integrity.

3.4 Data Currentness

How ‘up-to-date’ a geospatial dataset is upon delivery impacts an organization’s ability to make well-informed decisions. Some information sources can change more frequently than others, therefore it is necessary to demand a currentness threshold for specific sources of information. The following table lists features typically requested by DND and how up-to-date (no older than) the geospatial dataset must be to be accepted by DCC:

GIS Layer Currentness Jurisdictional Information - Published/updated within the last 2 years

(federal, provincial, municipal) - Published/updated within last year (electoral)

Terrain information - Published/updated within the last 10 years Hydrological information - Published/updated within the last 10 years Transportation infrastructure - Published/updated within the last 5 years Underground infrastructure - Published/updated within the last year Land use - Published/updated within the last 2 years Land ownership - Published/updated within this year Vegetation - Published/updated within the last 5 years (unless the

authoring agency has not issued a version in the timeframe)


GIS Layer Currentness Environmental information - Published/updated within the last 5 years Soil information - Published/updated within the last 10 years Geologic information - Published/updated within the last 10 years Terrain Slope/Aspect - Published/updated within the last 10 years UXO Features - May vary due to current and historical significance Imagery - Acquired within the last 5 years

Note: If the contracted authority is unable to source information that is as/more current than the table listed above, the Contractor must provide written confirmation from the authoring organization to demonstrate the feature dataset is the most current version available. This documentation must be provided to DCC with the submission of the final data deliverable.

3.5 Data Accuracy

The geospatial accuracy of features impacts the reliability of decisions and assumptions made on the basis of the information. The following table explains the required accuracy thresholds:

GIS Layer Accuracy (+/- m) Jurisdictional Information 25m Terrain information 25m horizontal, 10m vertical Hydrological information 25m Transportation infrastructure 25m Underground infrastructure 2m Land use 25m Land ownership 15m Vegetation 25m Environmental information 25m Soil information 100m Geologic information 100m Terrain Slope/Aspect 25m UXO Features 25cm

Note: If the contracted authority is unable to source information that is as/more accurate than the table listed above, the Contractor must provide written confirmation from the authoring organization to demonstrate the feature dataset is the most accurate version available. This documentation must be provided to DCC with the submission of the final data deliverable.


3.6 Metadata

Each independent information source/geospatial layer provided to DCC will be accompanied with metadata. Failure to provide metadata for each geospatial layer will inevitably lead to a failure in data quality. For geospatial data sourced from an agency other than a prime contractor, the dataset must at least include the following metadata elements, which are to abide by ISO standards (see section 2.6:

Authoring agency Authoring agency – contact information Date created Date last modified Coordinate system, projection, and datum parameters Collection method (exact description of the method used to build/collect

the data with associated scale)


Appendix 1 – Elements of ISO 19115 that comprise the DCC Metadata Standard

Metadata Element Comment NAP Metadata Reference 19139 XML Element(s)** Metadata Information Metadata date stamp Date the metadata was created.

Format: YYYY-MM-DDThh:mm:ss

MD_Metadata.dateStamp gmd:MD_Metadata >gmd:dateStamp >gco:DateTime

Metadata language Language used for documenting metadata. Default value: eng

MD_Metadata.language gmd:MD_Metadata >gmd:language

Metadata character set Character coding standard in the metadata. Must be ‘’utf8’’.

MD_Metadata.CharacterSetCode gmd:MD_Metadata >gmd:characterSet >gmd:MD_CharacterSetCode

Metadata author Contact information for the metadata author. Should include the individual’s name and position, organization name, phone and fax number, address, and e-mail address

MD_Metadata.contact > CI_ResponsibleParty

gmd:MD_Metadata >gmd:contact >gmd:CI_ResponsibleParty

Metadata standard name Name of the metadata standard/profile used. Must be ISO 19115:2003/19139

MD_Metadata.metadataStandardName gmd:MD_Metadata >gmd:metadataStandardName

Resource Identification Information Dataset title Name of the dataset MD_ Identification

> MD_DataIdentification.citation > CI_Citation.title (Character String)

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:title

Abstract Brief narrative summary of the content of the resource

MD_Identification > MD_DataIdentification.abstract

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:abstract

Publication date Date the data was issued MD_Identification > MD_DataIdentification.citation > CI_Citation.date > CI_Date and CI_Date.dateType > CI_DateTypeCode.publication

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:date >gmd:CI_Date


>gmd:date >gmd:dateType

Creation date Date the data was brought into existence MD_Identification > MD_DataIdentification.citation > CI_Citation.date > CI_Date and CI_Date.dateType > CI_DateTypeCode.creation

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:date >gmd:CI_Date >gmd:date >gmd:dateType

*Revision date Date the data was altered/amended.

Conditional – only required if the data has been revised.

MD_Identification > MD_DataIdentification.citation > CI_Citation.date > CI_Date and CI_Date.dateType > CI_DateTypeCode.revision

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:date >gmd:CI_Date >gmd:date >gmd:dateType

*Series name Information about the series or collection which the resource is a part.

Conditional – only required if the data belongs to a series.

Example: CANVEC, Quickbird-Pan-Ortho

MD_Identification > MD_DataIdentification.citation > CI_Citation.series > CI_Series

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:series >gmd:CI_Series >gmd:name

*Edition Version of the cited resource.

Conditional – only required if the dataset has a version number/date

MD_Identification > MD_DataIdentification.citation > CI_Citation.edition

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:edition

Responsible party - originator Contact information for the party responsible for creating the data. Must include the individual’s name and position, organization name, phone and fax number, address, and e-mail address.

Use the role to specify “originator”.

MD_ Identification >MD_DataIdentification.pointOfContact > CI_ResponsibleParty > CI_RoleCode.originator

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:citedResponsibleParty >gmd:CI_ResponsibleParty >gmd:individualName >gmd:organisationName


>gmd:positionName >gmd:contactInfo >gmd:role

Responsible party - point of contact

Contact information for the party who can be contacted for inquiries about the data. Must include the individual’s name and position, organization name, phone and fax number, address, and e-mail address

Use the role to specify “pointOfContact”.

MD_ Identification > MD_DataIdentification.pointOfContact > CI_ResponsibleParty > CI_RoleCode.pointOfContact

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:citation >gmd:CI_Citation >gmd:citedResponsibleParty >gmd:CI_ResponsibleParty >gmd:individualName >gmd:organisationName >gmd:positionName >gmd:contactInfo >gmd:role

Dataset language Language used in the dataset. Use standard ISO three letter codes.

Example: eng

MD_ Identification > MD_DataIdentification.language > MD_LanguageCountryCode

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:language

Dataset topic categories The main theme(s) of the dataset MD_ Identification > MD_DataIdentification.topicCategory > napMD_TopicCategoryCode

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:topicCategory >gmd:MD_TopicCategoryCode

Keywords

Refer to Appendix 2 for a list of suggested keywords.

2 theme keywords (subjects or topics – i.e. munitions, boundaries, national park)

2 place keywords (geographic locations – i.e. Canada, Trenton, tundra)

2 temporal keywords (specific periods in time – i.e. 1942, night, Mesozoic, June)

2 stratum keywords (layers in the environment – i.e. troposphere, littoral)

2 discipline keywords (branches of instruction – i.e. geology, geophysics)

MD_ Identification > MD_Keywords.keyword > MD_Keywords.type > napMD_KeywordTypeCode

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:descriptiveKeywords >gmd:MD_Keywords >gmd:keyword >gmd:type >gmd:MD_KeywordTypeCode

Spatial representation type Method used to spatially represent geographic MD_ Identification > MD_DataIdentification.spatialRepresentationType

gmd:identificationInfo >gmd:MD_DataIdentification


information (vector, grid, TIN, table) > MD_DataIdentification.spatialRepresentationType >gmd:spatialRepresentationType >gmd:MD_SpatialRepresentationTypeCode

*Scale denominator Conditional – only required for vector data.

Applies to paper maps and digital vector data derived from a hardcopy map or chart.

MD_ Identification > MD_DataIdentification.spatialResolution > MD_Resolution.equivalentScale > MD_RepresentativeFraction

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:spatialResolution >gmd:MD_Resolution >gmd:equivalentScale >gmd:MD_RepresentativeFraction >gmd:denominator

*Spatial resolution Conditional – only required for raster data MD_ Identification > MD_DataIdentification.spatialResolution > MD_Resolution.distance

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:spatialResolution >gmd:MD_Resolution >gmd:distance

Geographic extent Geographic position of the dataset, provided in decimal degrees

MD_ Identification > MD_DataIdentification.extent > EX_Extent > EX_GeographicExtent > EX_GeographicBoundingBox

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:extent >gmd:EX_Extent >gmd:geographicElement >gmd:EX_GeographicBoundingBox

Temporal extent Time period covered by the dataset MD_ Identification > MD_DataIdentification.extent > EX_Extent > EX_TemporalExtent

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:extent >gmd:EX_Extent >gmd:temporalElement >gmd:EX_TemporalExtent

*Vertical Extent Vertical domain of the dataset.

Conditional: Must be specified if the dataset has a z component

MD_ Identification > MD_DataIdentification.extent > EX_Extent > EX_VerticalExtent

gmd:identificationInfo >gmd:MD_DataIdentification >gmd:extent >gmd:EX_Extent >gmd:verticalElement >gmd:EX_VerticalExtent

Reference System Information Ref. system code Alphanumeric value identifying the coordinate

reference system (CRS). The CRS identifier is to be taken from the EPSG register (http://www.epsg.org/databases/Discv7_1.html).

MD_ReferenceSystem > RS_Identifier.code

gmd:referenceSystemInfo >gmd:MD_ ReferenceSystem >gmd:referenceSystemIdentifier >gmd:RS_Identifier >gmd:code


Example: 2958 (4 digit EPSG code)

Ref. system title Name of the reference system

Example: NAD83(CSRS)/UTM zone 17N

MD_ReferenceSystem > RS_Identifier.authority > CI_Citation.title

gmd:referenceSystemInfo >gmd:MD_ ReferenceSystem >gmd:referenceSystemIdentifier >gmd:RS_Identifier >gmd:authority >gmd:CI_Citation >gmd:title

Data Quality Information Lineage Information about the events or source data used

in constructing the data. This may include a statement but must include a description of each process step.

DQ_DataQuality > LI_Lineage.statement > LI_ProcessStep.description

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:lineage >gmd:LI_Lineage >gmd:statement >gmd:processStep >gmd:LI_ProcessStep >gmd:description

Source data - description Description of the source data used in creating the data

DQ_DataQuality > LI_Lineage > LI_Source.description

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:lineage >gmd:LI_Lineage >gmd:source >gmd:LI_Source >gmd:description

*Source data - scale denomination

Denominator of the representative fraction on a source map or chart

Conditional – only required if the source data is a map or chart

DQ_DataQuality > LI_Lineage > LI_Source.scaleDenominator

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:lineage >gmd:LI_Lineage >gmd:source >gmd:LI_Source >gmd:scaleDenominator >gmd:MD_RepresentativeFraction >gmd:denominator

Source data - reference system Spatial reference system used by the source data. EPSG code required.

DQ_DataQuality > LI_Lineage > LI_Source.sourceReferenceSystem

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:lineage >gmd:LI_Lineage >gmd:source


>gmd:LI_Source >gmd:sourceReferenceSystem >gmd:MD_ReferenceSystem >gmd:referenceSystemIdentifier >gmd:RS_Identifier >gmd:code

Source data - citation Title of the source data, publication date, and responsible party of the source data

DQ_DataQuality > LI_Lineage > LI_Source.sourceCitation

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:lineage >gmd:LI_Lineage >gmd:source >gmd:LI_Source >gmd:sourceCitation >gmd:CI_Citation >gmd:title >gmd:date >gmd:citedResponsibleParty

Absolute External Positional Accuracy

Closeness of the reported coordinate values to values accepted as or being true.

Mandatory: absolute external horizontal accuracy

Conditional: Vertical positional accuracy is only required if the dataset includes vertical measurements (i.e. heights)

Use the measure description to provide a statement about the positional accuracy of the data. Use value and value unit to provide the numeric measure of accuracy and the unit of measure. If the positional accuracy cannot be assessed then the value unit and value elements should be left empty.

DQ_DataQuality > DQ_AbsoluteExternalPositional Accuracy. MeasureDescription >DQ_QuantitativeResult.valueUnit >DQ_QuantitativeResult.value

gmd:dataQualityInfo >gmd:DQ_DataQuality >gmd:report >gmd:DQ_AbsoluteExternalPositionalAccuracy >gmd:MeasureDescription >gmd:result >gmd:DQ_QuantitativeResult >gmd:valueUnit >gmd:value

Distribution Information Distribution format Description of the data file format.

Mandatory: format name, version

MD_Distribution > MD_Format.name > MD_Format.version

gmd:distributionInfo >gmd:MD_Distribution >gmd:distributionFormat >gmd:MD_Format


>gmd:name >gmd:version

Digital transfer size Estimated size of the transfer unit in the specified format, expressed in megabytes

MD_Distribution > MD_DigitalTransferOptions. transferSize

gmd:distributionInfo >gmd:MD_Distribution >gmd:transferOptions >gmd:MD_DigitalTransferOptions >gmd:transferSize

Distributor Information about the distributor. Must include the individual’s name and position, organization name, phone and fax number, address, and e-mail address.

For data authored by the contractor on behalf of DCC/DND please provide the following information:

GIS Manager, Defence Construction Canada Email:[email protected] 161 Laurier Ave. West, Suite 301 Ottawa, ON, Canada, K1P 5J3

MD_Distribution > MD_Distributor.distributorContact > CI_ResponsibleParty > CI_RoleCode.distributor

gmd:distributionInfo >gmd:MD_Distribution >gmd:distributor >gmd:MD_Distributor >gmd:distributorContact >gmd:CI_ResponsibleParty >gmd:individualName >gmd:organisationName >gmd:positionName >gmd:contactInfo >gmd:role

Constraint Information Legal Constraints The legal restrictions or prerequisites to using the

resource or accessing the metadata.

DCC will supply this information

MD_Constraints > MD_LegalConstraints

gmd:MetadataConstraints >gmd:MD_LegalConstraints >gmd:accessConstraints >gmd:useConstraints

Security Constraints Restrictions applied to the resource or metadata to protect security concerns

DCC will supply this information

MD_Constraints > MD_SecurityConstraints

gmd:MetadataConstraints >gmd:MD_SecurityConstraints >gmd:classification

*Note: “Conditional metadata elements” – Information for these elements must be provided when appropriate. See the comment field for details about when the information is required.

** Items in bold require a value to be entered.


Appendix 2 – Metadata Keywords

Below is a list of possible keywords grouped into 5 categories as per the above metadata requirements. Contractors shall populate the keywords section of the metadata with words from this list. If the keywords in this list are not sufficient to describe the dataset created, please contact the DCC GIS group for guidance ([email protected]). Theme Keywords

Administrative boundaries keywords:

Boundaries Air quality control regions Coastal vegetation line Coastal zone Emergency communication districts Enterprise zone Fire management areas Fire protection regions Fish management regions Greenways National Forest National Park National Monument Open burning areas Park and recreation regions Forward Sortation Areas Regulated use zones School districts Shellfish management areas Provincial boundary Provincial Forest Provincial Park Watersheds Wildlife management units Zoning

Bioscience keywords: Alien plant Amphibian Anadromous fish Anadromous fish habitat Anadromous fish distribution Aquatic habitat Aquatic species Brush Endangered species Endemic Existing vegetation Fish Forbs

Elevation keywords: Altitude Aspect Bare earth Bathymetry Break lines Contour Depression Digital Elevation Model (DEM) Digital Terrain Model (DTM) Elevation bands Hillshade Hypsography LiDAR Raster Relief Sea level Slope Surface Terrain Topography Triangular Irregular Network (TIN)

Geoscience keywords: acid rain air temperature aquiclude aquifer biota coarse grained sediment coast coastal basin coastal bluff coastal desert coastal development coastal environment coastal plain coastline

Military keywords: Practice bombing range UXO BCATP


Grass Habitat Hatchery Historic vegetation Invasive species Invertebrate Lichen Mammal Marsh Migration Moss Nesting Potential vegetation Rearing habitat Reptile Riparian areas Sedge Seed zones Shellfish Shrubs Terrestrial species Trees Tree breeding Tree improvement Vegetation Vernal pool Vertibrate Weeds Wetlands Wildlife habitat

Cadastral keywords: Assessor’s maps Monument Ownership Parcels Right-of-way Section Subdivision Survey control

British Commonwealth Air Training Plan Legacy site Rocket range Mortar Pit Discarded Military Munition Armament Weapon Armed forces Defence Chemical weapon Biological weapon Military zone Training area Range

Stratum keywords

Anthroposphere Underground transportation Subsurface Landscape Tree cover Building space Above ground utilities

Atmosphere Troposphere Stratosphere Mesosphere

Aquatic Intertidal Estuarian Littoral Benthic Riparian

Cryosphere Land surface Soil

Surface Subsurface Subsoil Lower subsoil


Bathysphere Sea surface Epipelagic Bathypelagic

Biosphere Forest

Root zone Understory Low canopy Mid canopy Upper canopy

Parent material Bedrock Alluvium Colluvium Sediment

Discipline keywords

Anthropology keywords: Anthropology Archaeology

Biology keywords: Biochemistry Biodiversity Conservation Biology Ecology Ecosystems Environmental Biology Life Sciences Marine Biology Microbiology Water Resources,

Environmental Impacts Chemistry keywords:

Biochemistry Environmental Chemistry

Education keywords: Education/Instructional Programs Health and Safety Education

Geology keywords: Arctic Sciences Coastal Geology Earth Sciences Geology Marine Geology Physical Geology Geophysics

History keywords: Historical Documents History Military History

Management keywords: Utilities Quality/Product Control Urban Planning

Political Science keywords: Government Accountability Government Regulations

Place keywords

Canada Province

County/Township City

Street Temporal keywords

Day Endemic Flood stage Full moon High flow High tide High water Leaf-off Leaf-on Low flow Low tide Low water New moon

Weekday Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Season Spring Summer Fall Winter


Night Outbreak Post-eruption Post-fire Post-harvest Post-settlement Pre-eruption Pre-fire Pre-harvest Pre-settlement Snow-off Snow-on Year

Month January February March April May June July August September October November December

Sources EIONET GEMET Thesaurus. 24July 2009. European Environment Agency. http://www.eionet.europa.eu/gemet. Grants Development Office. 13 October 2009. University of Minnesota. http://www.morris.umn.edu/grants/FUNDINGdisciplineKEYWORDS.htm. Oregon Geospatial Enterprise Office (GEO). Emmor Nile. 7 October 2007. Oregon Govt. http://gis.oregon.gov/thesaurus.