APPENDIX D METADATA SPECIFICATION...Metadata Application Profile). ADOMAP will develop over time and it is anticipated that this will lead to changes to the DSRG Metadata Specification

Spatial Data Management Plan Appendix D Metadata Specification

Version 4.6.0 D-1 1 March 2015

APPENDIX D METADATA SPECIFICATION

D.1 Introduction 3

1.1 Audience .............................................................................................................. 3

1.2 Scope of Specification .......................................................................................... 3

D.2 Background 3

2.1 Metadata .............................................................................................................. 3

2.2 Spatial Information ............................................................................................... 3

D.3 Creation and Update of Metadata 4

3.1 The DSRG Metadata Entry Tool (MET) ............................................................... 4

D.4 Metadata Standards 4

4.1 Metadata Standards .............................................................................................. 4

D.5 Metadata Definitions 5

5.1 General Definitions .............................................................................................. 5

5.2 Geocoded and Georeferenced Information ............................................................ 5

D.6 Metadata Format 7

6.1 Metadata File Format ........................................................................................... 7

D.7 Structure of the DSRG Spatial Metadata Profile 8

7.1 The DSRG Spatial Metadata Profile ..................................................................... 8

7.2 Metadata Sections ................................................................................................ 8

7.3 Minimum Metadata Elements ............................................................................. 10

7.4 DSRG Geocoded Information Metadata Profile .................................................. 10

7.5 DSRG Georeferenced Information Metadata Profile ........................................... 12

7.6 DSRG Theme Keyword Levels .......................................................................... 15

7.7 DSRG Specific Metadata Elements .................................................................... 16

7.8 DSRG Spatial Metadata Profile Schema Set Location ........................................ 16

7.9 DSRG Spatial Metadata Profile - Table Headings ............................................... 16

D.8 Annex A – DSRG Spatial Metadata Profile 18



D.9 Annex B – DSRG Spatial Metadata Profile Rendered Sample 18

D.10 Annex C – Breakdown Of DSRG Metadata Cardinality 18

D.11 Annex D – List Of Standard DSRG Response Options 18

D.12 Annex E – Entity Relationship Diagram (ERD) 19

D.13 Annex F – DEMS Identifier Assignment Rules 20

D.14 Annex G – Data Set Properties Rules 23

D.15 Annex H – Overview Of Entity Relationships 25

15.1 Data Series ......................................................................................................... 25

15.2 Dataset and nonGeographicDataset .................................................................... 26

Table D5-1 Information type classifications in the DSRG MET ..............................................6 Table D7-1 DSRG Spatial Metadata Profile Sections ..............................................................9 Table D7-2 Minimum Metadata Elements for DSRG Geocoded Information ........................ 10 Table D7-3 Minimum Metadata Elements for DSRG Georeferenced Information ................. 12 Table D7-4 Example DSG Theme Keyword Levels .............................................................. 15 Table D7-5 DSRG Spatial Metadata Profile Section - Table Headings .................................. 16 Figure D 15-1 Required entity relationships with DP_Metadata where metadata HierarchyLevel is equal to ‘series’ ........................................................................................ 25 Figure D 15-2 Sample high level XML nodes where metadataHierarchyLevel is equal to ‘series’.................................................................................................................................. 26 Figure D 15-3 Required entity relationships with DP_Metadata where metadataHierarchyLevel is equal to ‘nonGeographicDataset’ or ‘dataset’ ............................. 27 Figure D 15-4 Sample high level XML nodes where metadataHierarchyLevel is ‘nonGeographicDataset’ ....................................................................................................... 27 Figure D 15-5 Sample high level XML nodes where metadataHierarchyLevel is ‘dataset’ .... 28



D.1 INTRODUCTION

1.1 Audience

This specification contains the full specification for Defence Support and Reform Group (DSRG) Metadata. This specification is written for reference by the DSRG Manager Spatial Systems and Contractors designing Directorate of Strategic Information Management architecture. It is not expected that DSRG Data Creators and Users, or DSRG Data Managers shall be familiar with the contents of the Metadata Specification.

1.2 Scope of Specification

The Metadata Specification is an appendix of the DSRG Spatial Data Management Plan. The Spatial Data Management Plan provides an overview of the DSRG Metadata requirements for Spatial Data that is sufficient for most users of spatial data within DS. The Metadata Specification within this document provides detailed reference information for use by DSRG Manager Spatial Systems and Contractors in refinements to the metadata specification or DSRG Information Systems including the Defence National Spatial Information Management System (NSIMS) or the DSRG Metadata Entry Tool (MET).

The Metadata Specification details the standards that the DSRG Metadata Specification is built on, the metadata elements included in the DSRG Metadata Specification and the details associated with relationships between elements, element conditions, cardinality, domains and DSRG specific elements.

D.2 BACKGROUND

2.1 Metadata

Metadata is structured documentation that describes a dataset. Information stored within metadata includes the data currency, accuracy, method of capture, author, and data quality.

Metadata is used with the Defence NSIMS to locate suitable spatial data to meet Defence business purposes. Metadata allows data users within Defence Support to make an informed decision on the suitability of data for a given purpose, to understand how the data was captured and the currency of the data.

Metadata is produced according to the detailed specification in this document to allow NSIMS to store, search and retrieve the metadata in a standardised format. Use of a standardised format that meets International Organization for Standardization (ISO) 19115 “Geographic Information – Metadata” standard, allows metadata to be shared with other organisations.

2.2 Spatial Information

Spatial data is information that defines the geographic location and spatial dimension of natural or constructed features on Earth. Spatial data stores geographic locations as a series of points, lines, and polygons using coordinate systems and topology to record and inform the location of information. Spatial data can be mapped using Computer Aided Design (CAD) or Geographic Information Systems (GIS) software. Defence Support and Reform Group



(DSRG) conducts business with the assistance of spatial data in many forms and for many different purposes.

DSRG relies on two Key or Foundation Spatial Datasets upon which other spatial data is developed and referenced. These Key Spatial Datasets types are:

n Master Site Plan Dataset

n Spaces Plan Dataset Other common spatial data used by DSRG includes:

n Aerial photography and satellite imagery; n Reference documentation including design and as-constructed plans of DSRG

structures, assets and infrastructure, and associated reports; and n Environmental data and information overlays including environmental

monitoring, heritage, contaminated sites data, weed and fire mapping. D.3 CREATION AND UPDATE OF METADATA

3.1 The DSRG Metadata Entry Tool (MET)

Metadata shall be created and edited within Defence Support using the DSRG Metadata Entry Tool (MET). The MET allows users to create, view and edit metadata records within the defined metadata structure. Instructions on installation and use are provided on the DSRG Defence Estate Quality Management System (DEQMS) website

http://www.defence.gov.au/estatemanagement

The MET is simple tool designed for non-specialist users to create metadata that meets the DSRG Metadata Specification. The tool provides an interface that leads a user through dialog steps and options to create a metadata record. Users do not need to be familiar with the DSRG Metadata Specification to create metadata that meets this specification.

All DSRG data shall have a metadata record that accompanies the dataset. A valid metadata record is required to allow data to be loaded into the DSRG NSIMS.

The MET creates a metadata file with the same filename as the data but with an .XML file extension. This metadata file shall remain in the same directory location as the dataset and shall always have the same filename as the data.

D.4 METADATA STANDARDS

4.1 Metadata Standards

Metadata is structured according to an industry specification or standard that allows metadata exchange between users. By adhering to common metadata standards, organisations are able to share data efficiently and search metadata records.

Metadata standards are defined by the official standards organisations, such as the ISO. The ISO spatial metadata standard is referred to as ISO 19115 “Geographic Information – Metadata”.



Australian jurisdictions have agreed to adopt ISO 19115 as the underlying standard for documentation of Spatial Data within Australia and New Zealand. This agreement is managed through the Spatial Information Council (formerly known as the Australian New Zealand Land Information Council - ANZLIC) with the assistance of the Commonwealth Office of Spatial Data Management (OSDM). Additionally Australian jurisdictions have agreed on a profile of ISO 19115 to be known as ANZLIC 3.

The Department of Defence, as a Commonwealth agency, through Defence Imagery and Geospatial Organisation’s (DIGO) participation in ANZLIC has adopted ANZLIC 3 as the basis of a Defence wide profile to be known as ADOMAP (Australian Defence Organisation Metadata Application Profile). ADOMAP will develop over time and it is anticipated that this will lead to changes to the DSRG Metadata Specification.

The DSRG Metadata Profile as described in this specification has been derived from the following standards:

n DIGO Standards;

n Information Management and Commercial Acquisition Directorate (SIMCA) standards;

n Australian Defence Organisation (ADO) Data Management (DM) Metadata Profile (MDP) of ISO 19115:2003 Geographic Information – Metadata (MD– ADO_DM_MDP Version 1.0.4); and

n AS/NZS ISO 19115:2005 Geographic information—Metadata.

D.5 METADATA DEFINITIONS

5.1 General Definitions

The following definitions are useful in understanding a metadata record:

n Metadata Element – discrete unit of metadata.

n Metadata Entity – set of metadata elements describing the same aspect of data.

n Metadata Section – a collection of related metadata entities and metadata elements.

n Cardinality – Cardinality may define the minimum and maximum number of elements and any conditions required to complete the entity/element.

5.2 Geocoded and Georeferenced Information

DSRG Spatial Information has been classified into two categories; Georeferenced information and Geocoded information.

Georeferenced Information is information has a location established in terms of a coordinate system so it can be viewed, queried, and analysed with other geographic data.



Geocoded Information is the association of an address or other descriptor with a geographic location. This term commonly refers to street address coding, but any type of geographic coding may be used. For example, a DEMS Structure Code can be used to geocode data because the structure has a physical location that can be assigned geographic coordinates. Documents including reports, manuals and drawings that are not georeferenced can be geocoded using the DEMS Structure Code to assign the documents a geographic location.

The file type provides a guide to whether a file is georeferenced or is geocoded information. For example georeferenced files often have the following file extension: *.dwg; *.e00; *.ecw; *img; *.shp; and geodatabases. Geocoded files tend to have the following file extensions: *.bmp, *.doc, *.pdf, *.txt, and *.xls. Image files that are georeferenced will be accompanied with a reference file that provides information that can be used by Spatial Systems to display the image in a georeferenced format.

The DSRG Metadata Entry Tool (MET) has been configured to automatically classify spatial data as Geocoded or Georeferenced. The table below indicates the automatic classifications that will be made in the DSRG MET.

Table D5-1 Information type classifications in the DSRG MET

Information Type Classification

Master Site Plans Georeferenced Garrison Support Services data Georeferenced GIS Data-Vector Georeferenced GIS Data-Grid Georeferenced GIS Data-TIN Georeferenced Imagery Georeferenced ANEF Georeferenced DACR Georeferenced Zone Plan Georeferenced Explosive Ordnance Safety Template

Georeferenced

Precinct Plan Georeferenced Extraneous Lighting DOD and CASA

Georeferenced

Spaces Plans Geocoded Miscellaneous plans Geocoded Photography Geocoded Reports Geocoded MS Excel spreadsheets Geocoded



D.6 METADATA FORMAT

6.1 Metadata File Format

DSRG Spatial Metadata records shall be stored in Extensible Mark-up Language (XML). XML is a specification used to encode documents in format that can be read by software that applies the specification.

The majority of DSRG staff and contractors will not need to be familiar with a raw XML metadata record. The Metadata Entry Tool shall be used to create and update metadata records.



D.7 STRUCTURE OF THE DSRG SPATIAL METADATA PROFILE

7.1 The DSRG Spatial Metadata Profile

The DSRG Spatial Metadata Profile defines what parts of Metadata Standard ISO 19115 are included, excluded and added for use by DSRG.

The Profile defines: n mandatory and conditional metadata sections, metadata entities, and metadata

elements; n the minimum set of metadata elements for any resource in order to conform to the

Profile; n the core metadata for geographic datasets; and n optional metadata elements that allow for a more extensive standard description of

resources.

Annex A sets out the full DSRG Spatial Metadata Profile. The profile and associated documents are provided in Microsoft Excel format to enable the user to sort and filter rows, columns and entries. A rendered example of the Metadata Profile is available from the following location on the Defence Estate Quality Management System http://www.defence.gov.au/estatemanagement

The supplementary documents accompanying this specification are:

n Annex B - Annex B provides a sample of the DSRG Spatial Metadata Profile. n Annex D - Annexes D1 to D26 list the standard DSRG response options applicable

to appropriate elements. n Annex E - Entity Relationship Diagram (ERD). This diagram expresses the

relationship between data entities and elements using Unified Modelling Language (UML).

n Annex F – DEMS identifier assignment rules for encoding within metadata. n Annex G – Data Set Properties: rules for the assemblage of data set properties

keywords by dataset type. n Annex H – Overview of entity relationships for Dataset, DataSeries and

nonGeographicDatasets including example XML.

7.2 Metadata Sections

The DSRG Spatial Metadata Profile is compiled from the Australian / New Zealand Standard ISO 19115:2005. The metadata sections, entities and elements are populated according to the stated cardinality and together combine to form the hierarchical structure of the DSRG Spatial Metadata Profile. Metadata Record Sections are described in Table D7-1.



Table D7-1 DSRG Spatial Metadata Profile Sections

Metadata Record Sections Description ISO 19115 Lines

Section 01 – Metadata Entity Set Information

The highest level in the hierarchical structure of a metadata record and the parent section for all other sections. Contains attributes that describe the characteristics of the Metadata record.

1-22

Section 02 – Resource Identification Information

Provides the general descriptive information about the data, including an abstract and a categorisation of the data.

23-66.5

Section 03 – Constraint Information Provides specific information on the limitation on use or distribution.

67-77

Section 04 – Data Quality Information

Provides guidance on the accuracy and or completeness of the data. This is a significant element for applications requiring a high level of reliability.

78-141

Section 05 – Maintenance Information

Provides an indication of whether or not the data is part of a planned update process, and if so how regularly.

142-155

Section 06 – Spatial Representation Information

Not used in the DSRG profile 156-185

Section 07 – Reference System Information

Quantifiable information describing the coordinate system the data is stored in.

186-231

Section 08 – Content Information Not used in the DSRG profile 232-267

Section 09 – Portrayal Catalogue Information


Section 10 – Distribution Information

284-286 are used in DSRG profile 270-283,287-302 are not used in DSRG profile

270-302

Section 11 – Metadata Extension Information

Provides the ability to document new elements into the profile to describe information that is deemed necessary for inclusion, but cannot be included under any other element within the profile.

303-319

Section 12 – Application Schema Information


Section 13 – Extent Information Quantification of the geographic extent of the data, usually by coordinates.

334-358



Metadata Record Sections Description ISO 19115 Lines

Section 14 – Citation and Responsible Party Information

Provides the contact details for the responsible organisation and links to additional information.

359-409

7.3 Minimum Metadata Elements

Australian / New Zealand Standard AS/NZS ISO 19115:2005 defines an extensive set of metadata elements; typically only a subset of the full number of elements are used in commonly used metadata profiles based on a set of Core metadata elements defined by ANZLIC. DSRG has identified a set of minimum metadata elements based on ANZLIC’s Core metadata elements that meet the needs of DSRG; these are defined in Sections 7.4 and 7.5.

7.4 DSRG Geocoded Information Metadata Profile

The profile for DSRG geocoded information comprises the elements listed in Table 7-1 The minimum number of keywords for a Geocoded metadata records is three. There must be at least one Theme type keyword, sourced from the Dataset Properties keyword list (within the DSG_gmxTheme codelist). Refer to appendix F for the rules for assembling these. There must be at least one Place Type keyword sourced from the DSG_gmxPlaces codelist of DEMS asset IDs. Additionally there must be at least one or more Theme Type keyword sourced from the DSG Theme keyword list within the DSG_gmxTheme codelist.

All new or updated geocoded spatial information supplied to DSRG is to be accompanied by metadata fully populated in accordance with this specification.

The full technical details for all elements within the scope of the DSRG Spatial Metadata Specification are provided in Annex A of the DSRG Spatial Metadata Specification and should be referred to when reading the following sections.

Table D7-2 Minimum Metadata Elements for DSRG Geocoded Information

ISO 19115 Line No

Name Path Cardinality

2.1 (Metadata) file Identifier

DP_Metadata> DP_Metadata.fileIdentifier

M

3 Language (used in the metadata)

DP_Metadata.language M

6 Hierarchy level DP_Metadata.hierarchyLevel O 9 (Metadata) date

stamp DP_Metadata.dateStamp M

25 Abstract (describing the

data)

DP_Metadata.identificationInfo> DP_DataIdentification.abstract

M

367 Dataset Responsible

Party

DP_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.citedResponsibleParty>

M



ISO 19115 Line No


DP_ResponsibleParty.OrganisationName and DP_ResponsibleParty.positionName and DP_ResponsibleParty.role

32 resourceFormat (Format of the

data)

DP_Metadata.identificationInfo> MD_Identification.ResourceFormat> MD_Format.name

C

53 keyword DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.keyword

M1

54 (keyword) Type DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.type

M1

55 (keyword) Thesaurus

DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.thesaurusName

M

79 Scope DP_Metadata.dataQualityInfo> DQ_DataQuality.scope DQ_Scope.level

M

83 statement

(lineage of the data set)

DP_Metadata.dataQualityInfo> DQ_DataQuality.dataLineage> LI_Lineage.statement

M

360 Title (of the data set)

DP_Metadata.identificationInfo> DP_DataIdentification.citation> CI_Citation.title

M

394 Date (of the data set)

DP_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.date> CI_Date.date

M

395 dateType (e.g

creation, publication…)

MD_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.date> CI_Date.dateType

M

1 The minimum number of keywords for a Geocoded metadata records is three. There must be at least one Theme type keyword, sourced from the Dataset Properties keyword list (within the DSG_gmxTheme codelist). Refer to appendix F for the rules for assembling these. There must be at least one Place Type keyword sourced from the DSG_gmxPlaces codelist of DEMS asset IDs. Additionally there must be at least one or more Theme Type keyword sourced from the DSG Theme keyword list within the DSG_gmxTheme codelist.



7.5 DSRG Georeferenced Information Metadata Profile

The profile for DSRG georeferenced information comprises the elements listed in Table D7-3 Minimum Metadata Elements for DSRG Georeferenced Information

All new or updated georeferenced spatial information supplied to DSRG is to be accompanied by metadata fully populated in accordance with this specification.

The full technical details for all elements within the scope of the DSRG Spatial Metadata Specification are provided in Annex A of the DSRG Spatial Metadata Specification and should be referred to when reading the following sections.

Table D7-3 Minimum Metadata Elements for DSRG Georeferenced Information

ISO 19115 Line No


2.1 (Metadata) file Identifier

DP_Metadata> DP_Metadata.fileIdentifier M

3 Language (used in the metadata)

DP_Metadata.language M

4 CharacterSet (used in the metadata)

DP_Metadata.characterset M

6 Hierarchy level DP_Metadata.hierarchyLevel O

8 (Metadata) Contact

DP_Metadata.contact> CL_ResponsibleParty> DP_ResponsibleParty.organisationName and DP_ResponsibleParty.positionName and DP_ResponsibleParty.role

M

9 (Metadata) date stamp

DP_Metadata.dateStamp M

10 Metadata Standard Name

DP_Metadata.metadataStandardName C

11 Metadata Standard Version

DP_Metadata.metadataStandardVersion O

24 Title (of the data set)

DP_Metadata.identificationInfo> DP_DataIdentification.citation> CI_Citation.title

M

25 Abstract (describing the

data)

DP_Metadata.identificationInfo> DP_DataIdentification.abstract M



ISO 19115 Line No


394 Date (of the data set)

DP_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.date> CI_Date.date

M

395 dateType (e.g creation,

publication…)

DP_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.date> CI_Date.dateType

M

26.1 Defence Purpose

DP_Metadata.identificationInfo> MD_Identification> DP_Identification.defencePurpose

M

367 Dataset Responsible

Party

DP_Metadata.identificationInfo> MD_Identification.citation> CI_Citation.citedResponsibleParty> DP_ResponsibleParty.OrganisationName and DP_ResponsibleParty.positionName and DP_ResponsibleParty.role

M

32 resourceFormat (Format of the

data)

DP_Metadata.identificationInfo> MD_Identification.ResourceFormat> MD_Format.name

C

39 Language (of the dataset)

DP_Metadata.identificationInfo> DP_DataIdentification.language M

40 CharacterSet (of the dataset)

DP_Metadata.identificationInfo> DP_DataIdentification.characterSet C

41 topicCatagory DP_Metadata.identificationInfo> DP_DataIdentification.topicCatagory M

53 Keyword DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.keyword

M1

54 (keyword) Type

DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.type

M1

55 (keyword) Thesaurus

DP_Metadata.identificationInfo> MD_Identification.descriptiveKeywords> MD_Keywords.thesaurusName

M

74.1 Security classification

DP_Metadata.identificationInfo> MD_Identification.resourceConstraints> MD_Constraints> DP_Constraints> MD_SecurityConstraints> DP_SecurityConstraints.classification

M

79 Scope DP_Metadata.dataQualityInfo> DQ_DataQuality.scope DQ_Scope.level

M



ISO 19115 Line No


80 Report DP_Metadata.dataQualityInfo> DQ_DataQuality.report> DQ_Completeness and or DQ_ThematicAccuracy and or DQ_PositionalAccuracy

O

83 statement (lineage of the

data set)

DP_Metadata.dataQualityInfo> DQ_DataQuality.dataLineage> LI_Lineage.statement

M

13.1 Reference System

DP_Metadata.referenceSystemInfo> MD_ReferenceSystem.referenceSystemIdentifier> RS_Identifier

M

37 Spatial Representation

DP_Metadata.identificationInfo> DP_DataIdentification.spatialRespresentationType O

60 or 61

Spatial Resolution

DP_Metadata.identificationInfo> DP_DataIdentification.spatialResolution> MD_Resolution.equivalentScale or MD_Resolution.distance

C

344, 345, 346 &

347

Geographic Extent (of the

data set)

DP_Metadata.identificationInfo> DP_DataIdentification.extent> EX_Extent.geographicElement> EX_GeographicBoundingBox

M

337 Temporal extent (of the

data set)

DP_Metadata.identificationInfo> DP_DataIdentification.extent> EX_Extent.temporalElement

C

338 Vertical extent (of the data set)

DP_Metadata.identificationInfo> DP_DataIdentification.extent> EX_Extent.verticallElement

C

1The minimum number of keywords for a Georeferenced metadata records is two, there must be at least one Theme type keyword, sourced from the Dataset Properties keyword list within the DSG_gmxTheme codelist. Refer to appendix F for the rules for the assembly of these. Additionally there must be one or more Theme Type keyword sourced from the DSG Theme keyword list within the DSG_gmxTheme codelist. Place Type keywords are optional (sourced from the DSG_gmxPlaces codelist of DEMS asset IDs.)



7.6 DSRG Theme Keyword Levels

Keywords are used to improve efficiency in locating relevant information. A keyword hierarchy (Theme Keywords - Appendix D20) has been developed to align to DSRG’s business structure.

Theme Keywords have been broken up into four level 1 groups: Environment, Infrastructure, Planning and Administration. A fifth level 1 group, DSG Properties, has been reserved to describe the type of information (e.g. Images, GIS Data, etc). Table D7-4 provides an example of DSG Theme Keyword Levels.

Metadata creators and editors should apply as many levels as is necessary to adequately categorise the resource. Any suggested improvements to the list of Theme Keyword descriptors should be directed to the DSRG Manager Spatial Systems.

Within the metadata file Theme Keyword hierarchy levels are delimited using the tilda character (~), for example; Environment~Fauna~Fauna Communities~Fauna Habitats.

Table D7-4 Example DSG Theme Keyword Levels

DSG Theme Level 1

DSG Theme Level 2

DSG Theme Level 3

DSG Theme Level 4

Environment Fauna Fauna Communities Fauna Distribution

Environment Fauna Habitats

Environment Fauna Sightings

Environment Fauna Monitoring

Environment Feral / Overabundant Species

Feral / Overabundant Species Distribution

Environment Feral / Overabundant Species Habitat

Environment Feral / Overabundant Species Sightings

Environment Feral / Overabundant Species Treatment

Environment Feral / Overabundant Species Monitoring



7.7 DSRG Specific Metadata Elements

Metadata elements that have been changed from the Australian / New Zealand metadata standard in relation to changes to cardinality, maximum occurrence or new elements are defined within this document by the Defence Profile (DP) extension. Such inclusions are prefixed with “DP” at the class level. The Defence Profile is based on DIGO’s ADO community implementation.

7.8 DSRG Spatial Metadata Profile Schema Set Location

The DSRG Spatial Metadata schema and referenced DSRG specific code lists can be found at the following URL:

http://intranet.defence.gov.au/im/tools/spatial/main.htm

7.9 DSRG Spatial Metadata Profile - Table Headings

This section provides a description of the DSRG Spatial Metadata Profile and includes examples of appropriate entries for each element.

Annex A describes the specific requirements for each element of a DSRG Metadata record and Annex B provides a well formed example Georeferenced metadata record complying with this specification. Table D7-5 DSRG Spatial Metadata Profile Section - Table Headings outlines the content of each column within Annex A.

Table D7-5 DSRG Spatial Metadata Profile Section - Table Headings

Table Heading Description

Section The metadata section to which the entity/element belongs.

ISO 19115 Line No The ISO 19115 standard line number of the entity/element. This number provides a reference to the ISO 19115 and the DIGO metadata profile, and is an identifier to reference elements.

Name/Role Name The long name of the entity/element.

Short Name The short name of the entity/element.

Definition A short explanation of the purpose of the element.

Geocoded Minimum

Identifies those elements that must be present and completed for the documentation of DSRG Geocoded data.

Georeference Minimum

Identifies those elements that must be present and completed for the documentation of DSRG Georeferenced data.



Table Heading Description

Cardinality The cardinality is the obligation to complete the entity/element. An element may be: Mandatory (M), Conditional (C) or Optional (O).

Mandatory means the element must be completed.

Conditional means completion of the element may become mandatory if a parent element within the hierarchy is completed or will be mandatory based on the characteristics of the subject data. The case when conditional elements are applied are detailed within the ‘Condition’ column.

Optional means the element may be left blank.

See paragraphs 7.4 and 7.5 for more information regarding cardinality.

Max Occ Maximum occurrence defines the number of times that an element may be repeated. The value of the element is either an integer or ‘N’ which represents ‘many’.

Type Describes the data type for an entity/element. Values include: Character String, Class, and Boolean.

Domain The Domain details the type of response option, whether free text can be entered for the element or whether a selection must be made from a defined domain list. Annex A provides details of all domains.

Comment The Comment includes additional information that may assist metadata readers and authors.

Condition Defines the case when conditional elements are applied.



Annexes A to D are stored within Appendix D Annexes A to D.xls (v4.6.0 1 March 2015).

D.8 Annex A – DSRG Spatial Metadata Profile

D.9 Annex B – DSRG Spatial Metadata Profile Rendered Sample

D.10 Annex C – Breakdown Of DSRG Metadata Cardinality

This Section has been removed.

D.11 Annex D – List Of Standard DSRG Response Options

Spatial Data Management Plan Section 5 Spatial Metadata Specifications


D.12 Annex E – Entity Relationship Diagram (ERD)



D.13 Annex F – DEMS Identifier Assignment Rules

Background Geocoded datasets, that are stored and managed within NSIMS, require a spatial reference embedded in metadata records. Geocoded datasets are required to be spatially referenced using Defence Estate Management System (DEMS) asset identifiers.

Geo-referenced datasets require geographic coordinate extents to be stored in metadata records.

Metadata records will be created using the MET and NSIMS, stored within NSIMS, and updated as data is edited within NSIMS.

The DEMS asset identifier is stored as a single string in the ‘keyword’ element (23) for Region, Property, Site, Structure, Floor and Space. The string is populated left to right, elements to the right may be null in the string if that level is not required.

The required format for the metadata will be:

Region~Property~Site~Structure~Floor~Space

For example, a Defence Structure (eg. a building) must contain the keywords for Region, Property, Site, and Structure but the Floor and Space keywords are not required. The tilde separators for Floor and Space remain in place.

A number of examples are provided below to illustrate the operation of the standard:

Example 1:

Description DEMS Identifiers Space A037 on the ground floor (GF) of building 0089/A0136 within Site 0089/A of Property 0089 (HMAS Stirling) in Western Australia.

Region ID: WA Property ID: 0089 Site ID: 0089/A Structure ID: 0089/A0136 Floor ID: GF Space ID: A037

Metadata Encoded String:

WA~0089~0089/A~0089/A0136~GF~A37



Example 2:

Description DEMS Identifiers Married Quarters “Jezzine House” Jezzine Barracks – Townsville in Queensland

Region ID: NQ Property ID: 0230 Site ID: 0230 Structure ID: 0230/MQ01 Floor ID: Space ID:


NQ~0230~0230~0230/MQ01~~

Example 3:

Description DEMS Identifiers The Fresh Water bore Site, Area B Exmouth, at Exmouth Area B – Admin & HF Transmitter property in Western Australia.

Region ID: WA Property ID: 0082 Site ID: 0082/F Structure ID: Floor ID: Space ID:


WA~0082~0082/F~~~

Example 4:

Description DEMS Identifiers Property HMAS Cairns in the DSRG region North Queensland

Region ID NQ Property ID: 0009 Site ID: Structure ID: Floor ID: Space ID:


NQ~0009~~~~



Example 5:

Description DEMS Identifiers Sydney West South region Region ID SWS

Property ID: Site ID: Structure ID: Floor ID: Space ID:


SWS~~~~~

Region Codes will be standardised as:

Code Name

ACTSN ACT and Southern NSW

CNN Central and Northern NSW

NQ North Queensland

NTK Northern Territory and Kimberly

RMV Riverina and Murray Valley

SV Southern Victoria

SA South Australia

SQ South Queensland

SC Sydney Central

SWS Sydney West South

TAS Tasmania

WA Western Australia



D.14 Annex G – Data Set Properties Rules

Info type value Hierarchy level value in MET Explorer

If selected number of entries present at ‘keyword’ where ‘thesaurusName’ value = ‘Dataset Properties’

Required value in ‘keyword’ where ‘thesaurusName’ value = ‘Dataset Properties’

Master Site Plan dataset 1 Dataset Properties~Master Site Plan Garrison Support Plan

dataset 1 Dataset Properties~Garrison Support Plan

Spaces Structure Plan

nonGeographicDataset

1 Dataset Properties~Spaces Structure Plan

Miscellaneous Plan nonGeographicDataset

One or many of the following: n ‘Dataset Properties~Miscellaneous

Plan~Architectural’ n ‘Dataset Properties~Miscellaneous

Plan~Civil’ n ‘Dataset Properties~Miscellaneous

Plan~Communications’ n ‘Dataset Properties~Miscellaneous

Plan~Hydraulic’ n ‘Dataset Properties~Miscellaneous

Plan~Mechanical’ n ‘Dataset Properties~Miscellaneous

Plan~Power/Electrical’ n ‘Dataset Properties~Miscellaneous

Plan~Security’ n ‘Dataset Properties~Miscellaneous

Plan~Structural’ n ‘Dataset Properties~Miscellaneous

Plan~Unknown’ One or many of the following: n ‘Dataset Properties~Miscellaneous

Plan Sub Type~Details’ n ‘Dataset Properties~Miscellaneous

Plan Sub Type~Elevations’ n ‘Dataset Properties~Miscellaneous

Plan Sub Type~Sections’ n ‘Dataset Properties~Miscellaneous

Plan Sub Type~Plans’ n ‘Dataset Properties~Miscellaneous

Plan Sub Type~Unknown’ One of the following: n ‘Dataset Properties~Miscellaneous

Plan Phase~As Built/As Constructed’

n ‘Dataset Properties~Miscellaneous Plan Phase~Design’



Info type value Hierarchy level value in MET Explorer

If selected number of entries present at ‘keyword’ where ‘thesaurusName’ value = ‘Dataset Properties’

Required value in ‘keyword’ where ‘thesaurusName’ value = ‘Dataset Properties’

n ‘Dataset Properties~Miscellaneous Plan Phase~Unknown’

Photography nonGeographicDataset

1 Dataset Properties~Photography

Reports nonGeographicDataset

1 Dataset Properties~Reports

MS Excel Spreadsheets

nonGeographicDataset

1 Dataset Properties~MS Excel Spreadsheets

GIS Data-Vector dataset 1 Dataset Properties~GIS Data-Vector GIS Data-Grid dataset 1 Dataset Properties~GIS Data-Grid GIS Data TIN dataset 1 Dataset Properties~GIS Data TIN ANEF dataset 1 Dataset Properties~ANEF DACR dataset 1 Dataset Properties~DACR Zone Plan dataset 1 Dataset Properties~Zone Plan Explosive Ordnance Safety Template

dataset 1 Dataset Properties~Explosive Ordnance Safety Template

Precinct plan dataset 1 Dataset Properties~Precinct plan Extraneous Lighting DOD and CASA

dataset 1 Dataset Properties~Extraneous Lighting DOD and CASA

Bird Strikes dataset 1 Dataset Properties~Bird Strikes Imagery dataset One of the following:

‘Dataset Properties~Imagery~Aerial’ ‘Dataset Properties~Imagery~Satellite’

series Not required

Spatial Data Management Plan Appendix B References


D.15 Annex H – Overview Of Entity Relationships

The section provides definition of the entity relationships relating to DP_Metadata (ISO ID 1.1) for the three values: ‘dataset’; ‘nonGeographicDataset’; and ‘series’ that are applied to metadataHierarchyLevel (ISO ID 6). Sample XML displaying high level XML nodes for each value are also provided.

15.1 Data Series

Figure D15-1 provides an overview of required entity relationships with DP_Metadata where metadataHierarchyLevel is equal to ‘series’.

Figure D 15-1 Required entity relationships with DP_Metadata where metadata HierarchyLevel is equal to ‘series’



Figure D 15-2 Sample high level XML nodes where metadataHierarchyLevel is equal to ‘series’

15.2 Dataset and nonGeographicDataset

Figure D2 provides an overview of required entity relationships with DP_Metadata where metadataHierarchyLevel is equal to ‘nonGeographicDataset’ or ‘dataset’.

Tables D-2 and D-3 provide sample high level XML nodes for metadata records documenting ‘dataset’ and ‘nonGeographicDataset’; where the metadataHierarchyLevel element is set to ‘dataset’ or ‘nonGeographicDataset’ respectively.



Figure D 15-3 Required entity relationships with DP_Metadata where metadataHierarchyLevel is equal to ‘nonGeographicDataset’ or ‘dataset’

Figure D 15-4 Sample high level XML nodes where metadataHierarchyLevel is ‘nonGeographicDataset’



Figure D 15-5 Sample high level XML nodes where metadataHierarchyLevel is ‘dataset’