Spatial Data Management Plan

Department of Defence

Estate and Infrastructure Group

Spatial Data Management Plan

Objective Document Id: BS11709314

Version: 5.0

Status: Final

Dated: 26 June 2020

Produced for: Estate and

Infrastructure Group


Version 5.0 ii 26 June 2020

EXECUTIVE SUMMARY

The Estate and Infrastructure Group (E&IG) Spatial Data Management Plan (SDMP) has

been developed to provide standards and specifications for spatial data management. The

SDMP and Estate Register Information Model (ERIM) make up the Defence Estate

Dictionary (DED), which defines all requirements for information collection, storage and

maintenance for the Defence estate.

The standards and specifications within the SDMP will improve data quality and availability

of information and facilitate spatial information dissemination and sharing within E&IG. With

its use under the E&IG Information Management Framework, E&IG will achieve a

standardised approach to spatial data management that will realise many benefits to both the

organisation and its staff including:

Consistent and more reliable data that will lead to more informed decision making;

Closer integration with E&IG information systems and Defence spatial data users;

Portability of staff skills; and

Greater interoperability with organisations outside of Defence.

The SDMP shall be used by spatial Data Supplier and Business Managers both within

Defence and Defence Contractors, and Information Stewards within E&IG. It is the

responsibility of Data Suppliers and Business Managers to implement the SDMP

Specifications and produce data in accordance with the specifications. Data Suppliers and

Business Mangers shall implement all requirements defined in Section 2, and the specific data

requirements in Sections 3 onwards as determined by the type of data to be created or

updated. Information Stewards will adhere to the standards and requirements set out in

Section 2 and Section 3 when managing data with relationship to spatial data.

The SDMP is made up of three main Sections:

Section 1 provides an introduction to the SDMP, the scope of implementation and other

background information to the document including how this requirement integrates with the

overarching DED.

Section 2 contains the General Data Specification that describes data formats, file naming

conventions, metadata requirements, the approved datum and coordinate systems,

measurement units, accuracy and other E&IG data standards.

Sections 3 onwards contain a set of specific data type specifications that shall be implemented

by all spatial Data Suppliers, Business Managers and Information Stewards. The data

specifications cover the key E&IG data types: the Master Site Plan and the Spaces (Floor)

Plans, in addition to specifications for engineering detail survey, aerial photography, master

planning, environmental data and other data types.

Appendices support the SDMP, providing detail of the E&IG Spatial Data Management

Specifications, the full Metadata Specification and additional appendices to support the core

data specification and data type specifications. Table E-1 summarises the information held

within each Section and Appendix.

This version of the SDMP coincides with the release of geo-enablement functionality in the

Garrison and Estate Management System (GEMS).


Version 5.0 iii 26 June 2020

The opportunity has also been taken to provide clarification of issues identified by SDMP

users in this release.


Version 5.0 iv 26 June 2020

Table E-1 SDMP Sections and Appendices

SDMP

Section Description of Contents

Section 1 Introduction

Section 2 Data Specification

Section 3 Master Site Plan Datasets

Section 4 Spaces Plan Datasets

Section 5 Reference Data

Section 6 Engineering Detail Survey

for Infrastructure and Assets

Section 7 Land Management Data

Section 8 Communications Data

Section 9 Aerial Photography

Section 10 Satellite Imagery

Section 11 Master Planning Datasets

Section 12 Contaminated Sites Data

Section 13 Environmental Data

Section 14 Hazards Data

Section 15 GEMS Geo-enabled Objects

Appendix A Glossary

Appendix B References

Appendix C Contaminated Sites Data Standards - retired

Appendix D Metadata Specification

Appendix E Directory Structure

Appendix F Scale and Accuracy

Appendix G Master Site Plan AutoCAD Standards

Appendix H Space Plan Standards

Appendix I Land Management Data Standards

Appendix J Master Planning CAD Standards

Appendix K Environmental Data Model

Appendix L Space Plan Labelling Standards - retired

Appendix M Hazards Spatial Data Standards

Appendix N GEMS Geo-Enabled Objects

A set of template datasets are provided as part of the SDMP to assist in the implementation of

the SDMP specification. The templates are available on the Defence Estate Quality

Management System (DEQMS) and include example data that has been collected in

accordance with the SDMP specifications.


Version 5.0 v 26 June 2020

TABLE OF CONTENTS

Executive Summary ii

Table of Contents v

Version History xii

1 Introduction 1

1.1 Defence Estate Information ........................................................................... 1

1.2 GEMS and the Defence Estate Dictionary ..................................................... 1

1.3 Purpose of SDMP .......................................................................................... 2

1.4 Spatial Data Definitions ................................................................................. 3

1.5 Intended Audience ......................................................................................... 4

1.6 Structure of SDMP ......................................................................................... 4

1.7 Application of the SDMP ............................................................................... 6

1.8 SDMP Point of Contact ................................................................................. 8

1.9 Linkages with NSIMS.................................................................................... 8

1.10 Spatial Data in the E&IG Information Management Framework .................. 8

2 General Data Specification 12

2.1 Introduction .................................................................................................. 12

2.2 Data Format ................................................................................................. 12

2.3 File Names ................................................................................................... 14

2.4 Directory Structures ..................................................................................... 14

2.5 Spatial Metadata ........................................................................................... 14

2.6 Datum ........................................................................................................... 15

2.7 Coordinate Systems ..................................................................................... 16

2.8 Units of Measurement .................................................................................. 17

2.9 Spatial Accuracy .......................................................................................... 17

2.10 Spatial Scale ................................................................................................. 17

2.11 Data Capture ................................................................................................ 18


Version 5.0 vi 26 June 2020

2.12 Data Viewing ............................................................................................... 18

2.13 Spatial Integrity of Features - Topology ...................................................... 18

2.14 Spatial Integrity of Features – Topology in a CAD Environment ............... 20

2.15 Data Attributes ............................................................................................. 22

2.16 Imagery Management – Image Tiling .......................................................... 22

2.17 Hardcopy Archival ....................................................................................... 23

2.18 Vectorisation of Scanned Information ......................................................... 24

3 Master Site Plan Datasets 28

3.1 Scope of Specification ................................................................................. 28

3.2 Deliverables ................................................................................................. 29

3.3 Deliverable Templates ................................................................................. 29

3.4 Data Deliverable Specification .................................................................... 29

3.5 Specific Data Requirements ......................................................................... 31

4 Spaces Plans 34


4.2 Deliverables ................................................................................................. 35


4.4 Required Inputs ............................................................................................ 35



5 Reference Data 45


5.2 Deliverables ................................................................................................. 45

5.3 Deliverable Specification – General Reference Documentation ................. 45

5.4 Deliverable Specification – Design Drawings ............................................. 46

6 Engineering Detail Survey for Infrastructure and Assets 50



Version 5.0 vii 26 June 2020

6.2 Deliverables ................................................................................................. 50

6.3 Data Inputs ................................................................................................... 50

6.4 Deliverable Specification ............................................................................. 50


7 Land Management Data 54


7.2 Deliverables ................................................................................................. 54



8 Communications Data 58


8.2 Deliverables ................................................................................................. 58


8.4 Required Inputs ............................................................................................ 59


8.6 Field Capture ................................................................................................ 59

8.7 Data Capture ................................................................................................ 59

9 Aerial Photography 66


9.2 Deliverables ................................................................................................. 66

9.3 Acquisition Requirements ............................................................................ 66

9.4 Orthophoto Specifications ........................................................................... 69

9.5 Orthophoto Deliverables .............................................................................. 69


9.7 Quality Assurance Documentation .............................................................. 72

9.8 Specific Metadata Requirements ................................................................. 72

10 Satellite Imagery 74


Version 5.0 viii 26 June 2020


10.2 Background Information .............................................................................. 74

10.3 Deliverables ................................................................................................. 76



11 Master Planning Datasets 80


11.2 Deliverables ................................................................................................. 81



12 Contaminated Sites Data 84


12.2 GEMS: Spatial Data Update and Creation ................................................... 85

12.3 Property Contaminated Site Map Requirements.......................................... 85

12.4 Data Deliverable – Map Template ............................................................... 89


13 Environmental Data 92


13.2 Background Information .............................................................................. 92

13.3 Types of Environmental Spatial Data .......................................................... 92

13.4 Data Deliverable – Templates ...................................................................... 94



13.7 Map Requirements ....................................................................................... 95

13.8 External Environmental Data ..................................................................... 100

14 Hazards Data 102

14.1 Scope of Specification ............................................................................... 102


Version 5.0 ix 26 June 2020

14.2 Schedule 11 Hazardous Chemicals Data and Maps (HAZCHEM) ........... 102

14.3 Hazardous Areas Data ................................................................................ 109

14.4 Unexploded Ordnance (UXO) Data ........................................................... 111

14.5 Training Area Unexploded Ordnance (UXO) Hazard Data and Maps ...... 112

14.6 Asbestos ..................................................................................................... 116

15 GEMS Geo-Enabled Objects (Features) 118

15.1 Scope of Specification ............................................................................... 118

15.2 Approaches for Geo-Enablement of Objects (Features) ............................ 118

15.3 How Geometries are Created or Updated for Geo-enabled Objects (as GIS

features) ...................................................................................................... 118

15.4 Data Deliverable Specification .................................................................. 120

Tables

Table 1-1 SDMP User Groups ................................................................................................... 4

Table 1-2 SDMP Sections and Appendices ............................................................................... 5

Table 1-3 Principles of the E&IG Spatial Data Policy ............................................................... 9

Table 2-1 List of Specialised Data Specifications ................................................................... 12

Table 2-2 E&IG Spatial Data Formats ..................................................................................... 13

Table 2-3 Recommended Tile Sizes ......................................................................................... 22

Table 3-1 Scope of Master Site Plan Data ............................................................................... 28

Table 4-1 Space Area Layers ................................................................................................... 42

Table 4-2 Spaces Plan Block Attributes ................................................................................... 42

Table 4-3 AutoCAD Block Space - Attributes ......................................................................... 43

Table 5-1 Example ASCON File Names ................................................................................. 46

Table 5-2 Design and As-Constructed Title Block Requirements ........................................... 47

Table 5-3 Design and As-Constructed Title Block Optional Information ............................... 47

Table 6-1 Scope of Data Collected using Engineering Detail Survey ..................................... 50

Table 7-1 Land Management data types .................................................................................. 54

Table 7-2 Land Management data type GEMS Record Requirements .................................... 55

Table 8-1 Communication Pit Data .......................................................................................... 61

Table 8-2 Communications Conduit Data ................................................................................ 62

Table 8-3 Communication Cable Data ..................................................................................... 63

Table 8-4 Communications Conduit Cable Link Data ............................................................. 64

Table 9-1 Orthophoto Options for Resolution and Accuracy .................................................. 70

Table 9-2 Orthophoto Technical Specifications ....................................................................... 70

Table 9-3 Orthophoto Quality Assurance Plan ........................................................................ 72

Table 9-4 Aerial Photography Specific Metadata Requirements ............................................. 72

Table 10-1 Satellite Imagery Specific Metadata Requirements ............................................... 77

Table 12-1: Contaminated Datasets ......................................................................................... 84

Table 12-2: Function Codes ..................................................................................................... 85

Table 12-3: Property Contaminated Sites Map Presentation Guidelines ................................. 86


Version 5.0 x 26 June 2020

Table 13-1: Bushfire Operations Map Presentation Guidelines ............................................... 96

Table 13-2: Land Capability Map Presentation Guidelines ..................................................... 98

Table 14-1: Schedule 11 Hazardous Chemicals Workplace Site Map Presentation Guidelines

................................................................................................................................................ 105

Table 15-1: Objects geospatial enabled via attribute association with other GEMS Objects 118

Table 15-2: Methods for Creation of Geometries for Geo-Enabled Objects ......................... 119

Figures

Figure 1-1 Master Site Plan Dataset - example data .................................................................. 3

Figure 1-2 Spaces Plan Dataset - example data ......................................................................... 4

Figure 1-3 Specification Process Flow Diagram ........................................................................ 7

Figure 2-1 Examples of Correct Topological Representation .................................................. 19

Figure 2-2 Examples of Correct Topological Representation .................................................. 20

Figure 2-3 Incorrect Topology - Unconnected line and point features .................................... 21

Figure 2-4 Correct Topology - Connected line and point features .......................................... 21

Figure 3-1 Master Site Plan Dataset - example data ................................................................ 29

Figure 4-1 Spaces Plan Dataset - example data ....................................................................... 34

Figure 4-2 Example external space capture of a covered area ................................................. 37

Figure 4-3 Example wet area and ablutions as a single space ................................................. 38

Figure 4-4 Example multiple wet area and ablutions space capture ........................................ 38

Figure 4-5 Example stairs in a corridor and stairwell space capture ....................................... 38

Figure 4-6 Example 1- workstations or work areas space capture ........................................... 39

Figure 4-7 Example 2 - workstations or work areas space capture .......................................... 39

Figure 4-8 Example fire hose space capture ............................................................................ 40

Figure 4-9 Example electrical switch/substation and communications areas space capture ... 40

Figure 8-1 Communication Pit Labels ..................................................................................... 60

Figure 8-2 Communication Cable Labels ................................................................................ 63

Figure 12-1: Example Property Contaminated Sites map ........................................................ 88

Figure 13-1 Environmental Spatial Data Types ....................................................................... 94

Figure 14-1: Example Workplace Site Map ........................................................................... 104

Figure 14-2: Example Defence Training Area UXO Hazard map ......................................... 114

Appendices

Appendix A Glossary A-1

Appendix B References B-1

Appendix C Contaminated Sites Data Standards - Retired C-1

Appendix D Metadata Specification D-1

Appendix E Directory Structure E-1

Appendix F Scale and Accuracy F-1

Appendix G Master Site Plan AutoCAD Standards G-1

Appendix H Space Plan Data Standards H-1

Appendix I Land Management Data Standards I-1

Appendix J Master Planning CAD Standards J-1

Appendix K Environmental Data Model K-1

Appendix L Space Plan Labelling Standards – Retired L-1

Appendix M Hazards Spatial Data Standards M-1


Version 5.0 xi 26 June 2020

Appendix N GEMS Geo-Enabled Objects N-1


Version 5.0 xii 26 June 2020

VERSION HISTORY

Version

Number Date Amendment Comment Released By

1.0 Feb 06 Draft John Ramsay

DIIE

3.0 31 Oct 06 Published Baseline version for release

Includes name change from CSIG to DSG

John Ramsay

DIIE

3.1 8 May 07 Draft

Updated SDMP Section 5 Spatial Metadata

Specifications v4.4 of 8 May 07. Updated

Section 1 Guiding Principles to numbered

paragraphs and added a Table of Contents

for the each SDMP section.

The Section 1 version number acts as the

overall version number for the entire

SDMP. If any section is updated, Section 1

should also be updated.

John Ramsay

DIIE

3.2 29 Feb 08 Published

Updated SDMP Section 5 Spatial Metadata

Specs v4.5, Section 6 Baseline Spatial Data

Specifications v3.1 and Section 7 Spatial

Data Specifications v3.1.

Berceuse

Bindle DIIE

4.5.1 7 Aug 08 Published Berceuse

Bindle DIIE

4.5.2 21 Dec 11 Draft

Includes name change from DSG to DS.

General restructure and revision of SDMP

to improve currency, ease-of-use and

reduce ambiguity.

Berceuse

Bindle DSIM

4.6.0 01 Mar 15 Draft

Update of Section 12 and Appendix C.

Addition of section 14 and appendix M for

inclusion of Hazards Data

Rod Armstrong

4.6.1 01 Jul 16 Published

Update DSRG to E&IG, Branches and

Directorate names, and references to DEMS

and RDMs. Update Appendix M Table M-7

Field Name Ocean to Medium with

additional values

Victor Bebawi

Lisa Fulgenzi

4.6.2 25 Oct 17 Published Update Space Plan figures to clockwise Lisa Fulgenzi

4.6.3 06 Feb 18 Published Update Spaces plan naming conventions,

Sections 4.6.2.4, 4.6.2.5 and Annex L Lisa Fulgenzi

5.0 26 June 2020 Published Updates to reflect GEMS requirements

Appendices C & L retired. Lois Wake

Spatial Data Management Plan Section 1 Introduction

Version 5.0 1 26 June 2020

Sec

tion 1

- I

ntr

oduct

ion

1 INTRODUCTION

1.1 Defence Estate Information

1.1.1 E&IG has developed and endorsed the E&IG Information Management Framework,

which sets out the how E&IG Information will be governed and managed by the

business.

1.1.2 The Framework sets out seven information management principles to provide a

reference point by which all IM processes, decisions and outcomes can be designed,

implemented and assessed.

1.1.3 The E&IG IM principles are:

Business Led – E&IG information is an enterprise level asset - defined by the

needs of the business, not defined by the technology solution.

Governed – Information assets are governed in a transparent and accountable

manner to ensure its business and authoritative value is maintained.

Managed – Information assets are actively managed and maintained in

accordance with business and technical standards to ensure they are fit for

purpose, usable, and available to the business user.

Organised – Information assets are structured and connected within a trusted

single-source to enable Defence to manage and use the information according to

its business requirements.

Secured – E&IG information is secured against unauthorised access, change,

loss or deletion in order to ensure integrity and protect sensitive information.

Used – E&IG information supports enterprise-wide business processes and

operating models and is accessible to authorised business users enabling

informed business processes and decisions.

Quality – E&IG information assets meet quality standards defined by the

business.

1.1.4 This SDMP is a key element of the management of data within E&IG by defining the

specific requirements by which spatial data is to be managed according to the E&IG

IM Principles.

1.2 GEMS and the Defence Estate Dictionary

1.2.1 The single source of data for Estate and Infrastructure information resides in the

Garrison Estate Management System (GEMS). GEMS has been implemented to

support the effective management of the Defence Estate by Defence and its Base

Services Contractors. Estate data is maintained in GEMS and includes asset data

describing the Defence Estate using spatial and non-spatial means.

1.2.2 GEMS provides timely and reliable information to support the planning and delivery

of estate infrastructure, development of the Defence capability life cycle, the

management of estate risks and environmental compliance and the delivery of estate

support. GEMS also provides real time exchange of electronic information between

Defence and Defence contractors.

1.2.3 GEMS is enhanced with basic geo-enabled functions. Geo-enablement provides users

with an ability to visualise, contextualise and interpret GEMS information, thereby to



Sec

tion 1

- I

ntr

oduct

ion

assure its truth and to better understand the relationships, patterns and trends for

improved Defence estate decision making. GEMS Geo-enablement involves

mandatory application of simple geometry representations that demonstrate existence,

shape and location of all geo-enabled GEMS estate master records and transactions.

Representative geometries are applied at creation of all master and transactional data,

and these are maintained throughout the record lifecycle.

1.2.4 GEMS is both a creator and consumer of spatial data that is created by Defence, its

stakeholders in industry and government and also commercial sources. These data are

visualised, stored, analysed and managed within a GIS information environment that

resides both within and alongside the GEMS system.

1.2.5 GEMS Geo-enablement will manage business GIS layer updates via workflow

tasking, the E&IG GIS will provide the workflow tasking capability (i.e. packaging

and issuing data for updates).

1.2.6 The SDMP spatial data specifications supports GEMS geo-enablement through the

alignment of key spatial dataset with GEMS Estate Business Identifiers (EBI), GEMS

data field values and Estate Register Information Model (ERIM) classes.

1.2.7 While the SDMP articulates the requirements for spatial data, the ERIM specifies SAP

based data requirements. As Defence has Geo enabled its SAP implementation the

data set requirements are integrated. This will eventually be reflected in the creation

of one data dictionary developed consistent with the IM principles.

1.2.8 Refer to Section 15 GEMS Geo-Enabled Objects (features) and Appendix N for

further details.

1.3 Purpose of SDMP

1.3.1 The Estate and Infrastructure Group (E&IG) Spatial Data Management Plan (SDMP)

has been developed to provide standards and specifications for spatial data

management and has been developed with reference to spatial standards both within

Defence and the spatial industry.

1.3.2 The standards and specifications within the SDMP will improve data quality,

availability of information and facilitate spatial information dissemination and sharing

within E&IG and its stakeholders in the broader Commonwealth, State and Local

Government community. With its use, E&IG will achieve a standardised approach to

spatial data management that will realise many benefits to both the organisation and

its staff including:

Consistent and more reliable data that will lead to more informed decision

making;

Closer integration with other E&IG information systems and Defence spatial

data users;

Portability of staff skills; and

Greater interoperability with organisations outside of Defence.

1.3.3 The SDMP provides the Spatial Data Specification for all data stored and managed

within E&IG Estate Information Management Systems including but not limited to;

the GEMS GIS environment



Sec

tion 1

- I

ntr

oduct

ion

the Defence records management system (Objective)

NSIMS

1.3.4 All spatial data shall meet the SDMP Specification to allow data to be accessed

within E&IG Estate Information Management Systems.

1.4 Spatial Data Definitions

1.4.1 Spatial data is information that defines the geographic location and spatial dimension

of natural or constructed features on Earth. Spatial data stores geographic locations in

vector form as a series of points, lines, polygons and raster images 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. E&IG conducts business with the assistance of spatial data in

many forms and for many different purposes.

1.4.2 E&IG relies on two key or Foundation Spatial Datasets upon which other spatial data

is developed and referenced. These key Spatial Datasets types are:

Master Site Plan Dataset

Spaces Plan Dataset

1.4.3 A Master Site Plan Dataset should exist for all Defence Properties. It contains the

locations of natural and man-made features such as vegetation, water features,

buildings, road, runways, and services. This dataset is used to plan and design new

infrastructure on properties and is used as a basis for the capture of Land Management

data. A sample of data from a Master Site Plan Dataset is shown in Figure 1-1. See


Figure 1-1 Master Site Plan Dataset - example data

1.4.4 A Spaces Plan Dataset (a form of simplified Floor Plan) is created for all buildings to

show the size, shape, layout and identification number of spaces and rooms, door

openings, staircases and fittings. This plan is distinct from an architectural floor plan.

The data captured is used to assist in building management through the allotment of

rooms, cleaning services, management of information technology assets and changes



Sec

tion 1

- I

ntr

oduct

ion

to buildings. A sample of data from a Spaces Plan Dataset is shown in Figure 1-2. See

Section 4 Space Plans

Figure 1-2 Spaces Plan Dataset - example data

1.4.5 Other common spatial data used by E&IG includes:

Aerial photography and satellite imagery;

Reference documentation including design and as-constructed design certified

(ACDC) plans of E&IG structures, assets and infrastructure, and associated

reports; and

Environmental data and information overlays including licensed areas,

environmental monitoring, heritage, contaminated sites data, weed and fire

mapping.

1.5 Intended Audience

1.5.1 The SDMP is intended for use by those creating, using and managing spatial data

within, and on behalf of, the Estate and Infrastructure Group (E&IG).

1.5.2 There are three key SDMP User Groups that are referred to within the SDMP; these

are listed in Table 1-1.

Table 1-1 SDMP User Groups

SDMP User Group Description of Group

Data Suppliers E&IG personnel and contractors who create, use and analyse

spatial data.

Business Managers E&IG personnel and head contractors with a responsibility to

manage and facilitate use of spatial data within their region or

nationally.

Information Stewards E&IG personnel with responsibility to define and manage data

(including and/or related to spatial data) to be made available to

Business Managers and Data Suppliers and users.

1.6 Structure of SDMP

1.6.1 The SDMP contains two types of Standards:



Sec

tion 1

- I

ntr

oduct

ion

The General Data Specification (Section 2).

Specialised Data Specifications (Section 3 onwards).

The General Data Specification (Section 2) contains the Data Specification that

applies to all spatial data. The General Specification prescribes the data formats, file

naming conventions, metadata requirements, the approved datum and coordinate

systems, measurement units, accuracy and other E&IG data standards.

Specialised Data Specifications (Sections 3 onwards) contain a set of specifications

for specific types of spatial datasets. The specifications for the two E&IG Key Spatial

Datasets are detailed, and specifications for other types of Spatial Data.

Appendices provide additional support to the SDMP. The appendices include the

Spatial Data Management Specification, the full Metadata Specification and additional

appendices to support the general data specification and specialised data

specifications.

Table 1-2 summarises the information held within each Section and Appendix.

Table 1-2 SDMP Sections and Appendices

SDMP

Section

Description of Contents Implementation

Responsibility

Section 1 Introduction:

Introduction to the SDMP, the scope of

implementation and background information

All Users

Section 2 General Data Specification

Applicable to all spatial data

All Users

Specialised Data Specifications

Specifications for specific types of spatial datasets

Section 3 Master Site Plan Datasets All users working

with data that falls

within the scope of

the Specification













Section 15 GEMS Geo-Enabled Objects

Appendices

Additional supporting information



Sec

tion 1

- I

ntr

oduct

ion

Appendix A Glossary For Information

Purposes Only

Appendix B References For Information

Purposes Only

Appendix C Contaminated Sites Data Standards - Retired Retired – Refer

Appendix K for

requirements

Appendix D Metadata Specification SDMP Technical

Authority

Appendix E Directory Structure All users

Appendix F Scale and Accuracy For Information

Purposes Only

Appendix G Master Site Plan AutoCAD Standards All users working


within the scope of

the Specification

Appendix H Space Plan Standards

Appendix I Land Management Spatial Data Standards

Appendix J Master Planning CAD Standards

Appendix K Environmental Data Model

Appendix L Space Plan Labelling Standards - Retired Refer Estate &

Infrastructure

Group Defence

Signage And

Labelling Standard

for requirements

Appendix M Hazards Spatial Data Standards All users working


within the scope of

the Specification

Appendix N GEMS Geo-Enabled Objects

Associated Documents

A set of template datasets are provided as part of the SDMP to assist in the implementation

of the SDMP specification. The templates are available on the Defence Estate Quality

Management System (DEQMS) site and include example data that has been collected in

accordance with the SDMP specifications.

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

1.7 Application of the SDMP

1.7.1 The SDMP applies to all E&IG business units and E&IG contractors. All are

responsible for the appropriate application of standards and the implementation of the

SDMP requirement accordingly.

1.7.2 The SDMP specification process flow shall be applied as described below in Figure

1-3.




Sec

tion 1

- I

ntr

oduct

ion

Figure 1-3 Specification Process Flow Diagram



Sec

tion 1

- I

ntr

oduct

ion

1.8 SDMP Point of Contact

General note about data: Queries related to the SDMP should be addressed to the GEMS and

Business Transformation team via email to [email protected]

1.8.1 Constructive feedback at any time on any aspect of the SDMP is welcomed from all

within its user community, Defence and non-Defence users alike. Feedback can be

provided at any time to [email protected].

1.8.2 GEMS has a change request process that covers documentation and system

enhancements. Please contact our user support team in the first instance to discuss

your requirement: [email protected].

1.9 Linkages with NSIMS

1.9.1 Defence has a suite of information systems brought together through GEMS for estate

information. The National Spatial Information Management System (NSIMS) is

currently the repository for Defence staff and contractors to place spatial information.

NSIMS is located within the Defence Restricted Network (DRN) and is access

managed.

1.9.2 NSIMS includes the following components:

A spatial dataset metadata catalogue for searching and locating spatial and non

spatial data;

A gazetteer for defining and performing searches on geographic extents of a

named feature;

A viewing tool that allows spatial datasets to be displayed; and

A tool to allow datasets to be uploaded to, and downloaded from, the system.

1.9.3 All E&IG spatial data shall be stored within NSIMS if the data meets the

specifications of the SDMP.

NSIMS is currently being reviewed for retirement but should continue to be used until

further instructions are released regarding transition to the alternate solution.

1.10 Spatial Data in the E&IG Information Management Framework

1.10.1 E&IG has an Information Management Framework with seven principles to guide

information and data management processes and decisions across E&IG:

Business Led

Governed

Managed

Organised

Secured

Used

Quality

mailto:[email protected]



Sec

tion 1

- I

ntr

oduct

ion

1.10.2 Table 1-3below explains how the principles apply to spatial data. The E&IG

Information Management principles shall be adhered to by all E&IG spatial data user

groups.

1.10.3 Refer to Appendix B for policies that the SDMP applies within.

Table 1-3 Principles of the E&IG Spatial Data Policy

Principle Description User Responsibility

Business Led Data shall be gathered in a

manner that is independent of

specific vendor applications and

readily integrated with other

systems that adhere to this

principle.

To the extent practicable, all spatial data

that is provided in reports, and designed

and produced for Defence shall have the

widest benefit to the broader E&IG

business, and to existing data and

information systems.

Governed DRN users shall have access to

valid, reliable, complete data

they can use with confidence to

support improved decision

making.

NSIMS shall be used to store and access

spatial data to ensure that the most current

and complete spatial data is available to

DRN users.

Managed Spatial Information shall be

valued and protected as a key

Defence asset.

Errors or omissions found in any

dataset shall be rectified prior to

final delivery or reported as soon

as practical to the E&IG business

owner or NSIMS Custodian.

Arrangements shall be in place to protect

E&IG’s information from complete or

partial loss, or destruction.

NSIMS validates spatial dataset against

SDMP requirements prior to upload in

NSIMS.

DRN users should report errors, omissions

and improvement actions via the NSIMS

issue feedback link.

Organised The Standards and Specifications

within the SDMP apply to E&IG

Spatial Data. Specific standards

apply to specific spatial datasets

including the E&IG Key Spatial

Datasets and other spatial data.

Metadata documentation shall be

collected and maintained.

Accurate documentation of

spatial data will ensure data is

stored and can be retrieved

logically and appropriately in

support of E&IG operations and

decision making.

When considering the relevance and

application of the SDMP specification,

spatial data providers and managers

should consider which section of the

SDMP specification shall be applied to

spatial datasets.

The E&IG Metadata Entry Tool (DSG

MET) shall be used to create and edit

metadata to provide documentation of

spatial datasets. The MET can be

downloaded from the DEQMS website

and:

http://intranet.defence.gov.au/estatemanag

ement/support/MET/Default.asp

Secured Management of spatial data shall

include arrangements to preserve

confidentiality, privacy, security

and intellectual property rights

which will protect the rights of

data owners and appropriate

sectors of the Defence

stakeholder community.

The provision of Defence information is

permitted on a “Need to Know” basis.

Defence data shall not be provided to a

third-party without direct approval and the

implementation of a Data License. Data

shall be managed in such a way that

security is maintained at all times.



Sec

tion 1

- I

ntr

oduct

ion

Principle Description User Responsibility

Used Spatial information shall be

made accessible and leveraged

across the Defence Restricted

Network (DRN) to enable

improved decision making and

minimise costs to Defence e.g.

due to duplication.

Data shall be openly available to

all DRN users through the use of

NSIMS to maximise the benefit

of the data to the organisation as

a whole.

NSIMS shall be used to store and access

spatial data to ensure that data is shared

between DRN users. Data gathering

initiatives shall avoid unnecessary

duplication of effort, and the consequent

risks of unnecessary expenditure and

inconsistent data.

Quality Data shall be collected, stored

and disseminated according to

Defence Standards and

specifications.

Data shall be acquired from a

point as close to its (the data’s)

source as possible.

Data shall be entered only once

into Defence systems. There

shall be a single authoritative

source for each data element.

The SDMP identifies the applicability and

scope of minimum spatial data standards

and shall be applied for E&IG Spatial

Data.

E&IG “Contract Documents” may

identify additional specific requirements

that shall be applied.

All finalised spatial and non-spatial data

should be stored within NSIMS to allow

E&IG staff to access a single data source

and minimise the requirement to obtain

multiple versions of data from external

sources.

NSIMS custodian and user roles shall be

used to manage spatial data integrity

within NSIMS.

Spatial Data Management Plan Section 2 General Data Specification


Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

Section 2 General Data Specification



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2 GENERAL DATA SPECIFICATION

2.1 Introduction

2.1.1 This section defines the General Data Specification and standards for spatial data.

Specific or additional requirements are provided within the Specialised Data

Specifications in Sections 3 onwards. The Specialised Data Specification for the type

of data being created or updated must be read in conjunction with the General Data

Specification. See Table 2-1 for a list of the Specialised Data Specifications.

Table 2-1 List of Specialised Data Specifications
















2.1.2 The SDMP applies to all E&IG business units and E&IG contractors. All are

responsible for the appropriate application of standards and the implementation of the

SDMP requirement accordingly.

2.2 Data Format

2.2.1 All E&IG spatial data shall meet the format requirements defined in Table 2-2.



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

Table 2-2 E&IG Spatial Data Formats

Information Type Preferred Format Extension Comments

CAD (Computer

Aided Design) Data

AutoCAD Drawing file DWG Shall be compatible with

AutoCAD Release 2013

GIS Data ESRI Shapefile SHP, SHX

and DBF

Shapefiles shall be supplied

with the three basic file

extensions as a minimum and

content must comply with

relevant SDMP specification

requirements

Geodatabase oracle spatial

SQL server

SAP

ESRI file

geodatabase

It is anticipated that database

extracts would be provided

by E&IG for amendment.

Point Cloud Vendor neutral Point

Cloud data format

LAS

Or

LAZ

For transfer of airborne,

terrestrial and mobile laser

scanned data.

Digital Elevation

Models

Band Interleaved by Line

Band Sequential

TIFF and GeoTIFF

ArcGIS GRID

ERDAS IMAGINE

Comma separated value

BIL

BSQ

TIFF & TIF

Standard

contents of

ArcGIS

GRID

directory

IMG

CSV or TXT

JPG and TIF images shall be

supplied with an associated

‘world file’ containing image

header information (.JFW or

.TFW file)

Data Attribute Tables Dbase IV

Comma separated value

MS Excel 97 (*.xls)

DBF

CSV or TXT

XLS



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2.3 File Names

2.3.1 File names shall succinctly summarise the data to allow users to quickly understand

the content of the data. The file name should include the subject of the data and the

data locality with reference to the Defence Property name and or EBI if appropriate.

2.3.2 Spaces shall not be used in file names, underscores shall be used to separate text.

2.3.3 File naming conventions specific to particular types of data are covered with the

Specialised Data Specification sections of the SDMP. These take precedence over

requirements in Section 2 General Data Specification

2.3.4 Specific file naming requirements for ESRI GIS Elevation Model ‘Grid’ file format:

the ESRI Grid file format stores data within a set of directories that can be easily

confused with standard directory folders in Windows Explorer.

Each ESRI Grid file shall be clearly named to identify the file as a Grid format, and

shall provide a description of the file contents within the filename limit of 13

characters. The following filename format shall be adhered to:

Format: [Short description of file contents]_grd

Example: MBTAelev_grd (elevation grid for Mount Bundy Training Area)

2.4 Directory Structures

2.4.1 Directory structures used for spatial data deliverables shall be intuitive to users.

2.4.2 A recommended directory structure is defined within Appendix E and is available for

download as a ready-defined structure from the following page on the E&IG Defence

Estate Quality Management System (DEQMS) website

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

2.5 Spatial Metadata

2.5.1 Metadata is structured documentation that describes spatial data. Information stored

within metadata includes the data currency, accuracy, method of capture, data author,

and data quality.

2.5.2 Metadata allows data users 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.

2.5.3 All E&IG spatial data shall have a metadata record that accompanies the dataset. A

valid metadata record is required to allow data to be loaded into the E&IG National

Spatial Information Management System (NSIMS).

2.5.4 Spatial metadata shall be created and edited using the E&IG 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

E&IG Defence Estate Quality Management System website:


2.5.5 The MET is a simple tool designed for non-specialist users to create spatial metadata

that meets the E&IG Spatial Metadata Specification. The tool provides an interface





Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

that leads a user through dialog steps and options to create a metadata record. Users

do not need to be familiar with the full E&IG Spatial Metadata Specification

(Appendix D) to create metadata that meets this specification.

2.5.6 The MET creates a metadata file with the same filename as the data but with an .XML

file extension. This metadata file should remain in the same directory location as the

dataset and shall always have the same filename as the data.

2.5.7 Keywords are used to improve efficiency in locating relevant information. A set of

keywords has been developed to align to E&IG’s business structure. Multiple sets of

keywords can be assigned to a dataset to assist users in locating a dataset in the future.

2.5.8 Specific Spatial Metadata Requirements

2.5.8.1 The following metadata requirements shall be stored in metadata records:

Data capture methodology shall be specified in enough detail for the

data capture to be repeated or for the methodology to be reviewed.

Horizontal and vertical accuracy of captured data shall be recorded.

2.5.8.2 The full E&IG Spatial Metadata Specification is provided within Appendix

D. The Metadata Specification is written for reference by the SDMP Technical

Authority and Contractors designing Directorate of Strategic Information

Management (DSIM) architectures. It is not expected that E&IG Data

Suppliers or E&IG Business Managers shall be familiar with the contents of

the Spatial Metadata Specification.

2.6 Datum

2.6.1 A datum is the reference point against which spatial position measurements are taken.

Detailed information on datum can be found on the following website:

www.icsm.gov.au.

2.6.2 Horizontal Datum

2.6.2.1 A Horizontal datum is used to describe the position of a point on the Earth’s

surface in association with a Coordinate System.

2.6.2.2 Defence has adopted the World Geodetic System 1984 (WGS84) as the

standard for all spatially referenced data created for E&IG.

2.6.2.3 Although WGS84 has been adopted across Defence to support Defence

operations, E&IG recognises that industry partners who support the Defence

Estate only have access to GDA and as a consequence will accept the use of

GDA2020 for spatial data used to support the Defence Estate as specified in

the Spatial Data Management. During the transition to GDA2020, GDA94

may be used but must be clearly marked as such.

2.6.3 Vertical Datum

2.6.3.1 A Vertical datum is used to describe a position vertically as the elevation or

depth of a point.



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2.6.3.2 E&IG has adopted Australian Height Datum (AHD) as the standard

vertical datum.

2.6.3.3 Where heights have been derived from GNSS the geoid model used to

derive AHD must be stated.

2.7 Coordinate Systems

2.7.1 A coordinate system divides the Earth’s surface using a set of coordinates to identify

the position of a point.

2.7.2 E&IG has adopted the Geographic Coordinate System and the Map Grid of Australia

(MGA) as the standard coordinate systems.

2.7.3 E&IG will accept data in the MGA coordinate system where data is provided in a

format that does not support the use of Geographic Coordinates. The metadata

accompanying these data must clearly state the datum and coordinate system used.

2.7.4 Geographic Coordinate System

2.7.4.1 The Geographic Coordinate System defines the locations of points on the

surface of the Earth using Latitude and Longitude.

2.7.4.2 Latitude and longitude coordinates shall be recorded in the format Decimal

Degrees and shall be recorded to a minimum of 5 decimal places (approximate

equal to a precision of 1 m).

Example: 31.99235 115.88157

2.7.4.3 Lines of latitude are measured as an angle from the equator (0°) to either

Pole, 90° South and 90° North.

2.7.4.4 Lines of longitude intersect both the North and South poles. They are

numbered using degrees beginning at the Royal Greenwich Observatory in

England, which is designated as 0°, and continue both East and West until they

meet at 180°.

2.7.5 Map Grid of Australia

2.7.5.1 Map Grid of Australia is a projected coordinate system that defines the

locations of points on the surface of the Earth by the measurement of metres

from a point of origin.



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2.8 Units of Measurement

2.8.1 Units of measurement shall be recorded using metric standard scientific (SI) units.

The units of measure shall be defined within the dataset attributes or metadata.

2.8.2 The unit of length measurement shall be metres unless specified within the Data Type

Specifications in Sections 3 onwards.

2.8.3 In ongoing projects, the unit of measurement within the dataset attributes shall be kept

consistent.

2.9 Spatial Accuracy

2.9.1 Spatial accuracy measures how closely a position in a dataset is located to its true

position on the Earth’s surface.

2.9.2 Spatial data shall be captured at an accuracy that is appropriate for the data use. For

example, Master Site Plans and Spaces Plans require a high spatial accuracy for use in

asset and infrastructure management that is specified within the Data Type

Specifications in Sections 3 onwards.

2.9.3 Where a spatial accuracy is not specified within the SDMP the E&IG Project

Manager shall provide guidance on an appropriate level of accuracy.

2.9.4 Spatial accuracy shall be recorded in metadata records for all data capture and derived

data products.

2.9.5 Global Navigation Satellite Systems (e.g. GPS) are used by E&IG in a variety of

business purposes. The right type of GNSS must be used to obtain data of a suitable

accuracy for the business purpose for which it is being collected. Hand-held GPS

cannot collect data at the accuracy required for the Master Site Plan Dataset. An

Engineering Detail Survey using Survey Control Stations must be used for Master

Site Plan Data collection. Differential GNSSS techniques can be used for applications

that require higher accuracy than a hand-held GNSSS, but don’t require the accuracy

of an Engineering Detail Survey.

2.9.6 GNSS receivers record the accuracy (or precision) of the GNSS reading as a Dilution

of Precision (DOP) or Estimated Precision Error (EPE). These values can vary

dependent on the satellite position and signal quality. Where an accuracy of <30m is

required, these readings should be recorded with the attributes of the GNSS positional

data and stored against each record or in the metadata record.

2.10 Spatial Scale

2.10.1 Scale is the ratio of the distance on a hardcopy map or electronic data viewer to the

true distance on the ground (e.g. 1:50,000). Data or maps with smaller scales

(1:250,000) are less accurate and show less detail compared to data or maps at larger

scales (1:25,000).

2.10.2 The accuracy of a dataset or map is equal to ± ½ mm (0.0005m) at map scale. A scale

accuracy table is provided in Appendix F.

Example: ± 0.0005 m at 1:50,000 = ± 25m

± 0.0005 m at 1:10,000 = ± 5m



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2.11 Data Capture

2.11.1 Data products derived from other data sources shall be captured at a scale appropriate

for the data use and where possible defined in Australian industry standards.

2.11.2 Data created from multiple data sources takes on the smallest dataset scale. For

example, if data is combined from 1:250,000 vegetation mapping and 1:100,000

vegetation mapping the resulting dataset will have a scale of 1:250,000.

2.12 Data Viewing

2.12.1 Software functionality enables users to zoom into a dataset and use or print

information at very large scales. Caution shall be taken when using data beyond the

scale at which it was collected as the accuracy of the data remains the same (see

accuracies defined in Appendix F).

2.13 Spatial Integrity of Features - Topology

2.13.1 All data captured or provided for E&IG shall be topologically clean and free of errors.

Data shall be corrected for overshoots and undershoots, polygons shall be closed, and

slivers removed. Figure 2-1 and Figure 2-2 provide examples on how correct topology

shall be applied.

2.13.2 Topologically clean data allows users to link attributes to features more accurately

and to undertake various types of spatial analysis within a Geographical Information

System. For example, analysis can be undertaken to calculate the area or parameter of

a feature automatically, analyse proximity of features to other features, and

automatically quantify change over time.



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

Undershoot in feature

Correct Representation Incorrect Representation

Overshoot in feature

Correct Representation Incorrect Representation

Pseudo-node in contiguous features

Pseudo node

Same feature with identical attribute values.

Broken line in feature

Incorrect Representation

Figure 2-1 Examples of Correct Topological Representation

Correct Representation



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

Artefacts

Correct Intersection Incorrect Intersection Incorrect Intersection

Linear Feature Spike in Linear Feature

Incorrect Representation Correct Representation

Figure 2-2 Examples of Correct Topological Representation

2.14 Spatial Integrity of Features – Topology in a CAD Environment

2.14.1 The following information will assist in maintaining topologically clean data in a

CAD environment.

Poly-lines (polygons) close – their start and end points are the same;

Line features join or snap together – they share endpoints;

Line feature vertices can also join with point features – they share nodes;

Point features provide the vertices for the connecting linework; and

Text is associated with the appropriate polygon, line or point feature.

2.14.2 The capturing/editing of the CAD line work will include:

“Snapping” of line/poly-line nodes to appropriate point features;

“Breaking” utility line work at appropriate point features,

e.g. where a pipe/cable connects to above ground features;

Not “Breaking” utility line work where it does not intersect,

Open Polygon

Slivers



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

e.g. where pipes/cables are at different height levels; and

Point/Symbol features are represented as a ‘block’.

The following examples provide an overview of the requirements for producing topologically

correct Master Site Plan data within a CAD environment.

Figure 2-3 Incorrect Topology - Unconnected line and point features

Figure 2-3 shows CAD line features that intersect a point (symbol) feature but the line

features do not meet at the node within the point feature.

Figure 2-4 Correct Topology - Connected line and point features

The correct topology (Figure 2-4) represents the line features intersecting a point feature by

inserting a new vertex to the line and “snapping” it to the insertion point of the point feature.

It is assumed that the line feature should be split at the point feature and that the relevant end

points of the lines should be at the point feature.



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

2.15 Data Attributes

2.15.1 Data attributes store descriptive information about particular spatial features within a

dataset. Data attributes can include descriptions, dates of capture or update, area,

position coordinates, the value of a measurement taken at the location, or a

classification or category.

2.15.2 Data attributes are described within the SDMP Detailed Data Specifications within

Section 3 onwards for specific types of data.

2.15.3 Where no Specification exists for a data type or where additional attributes are

required, the additional attributes shall be reviewed to confirm that there is a clear

business requirement. Attributes shall be intuitive to users and shall be allocated

intuitive attribute names. Attributes codes and classifications shall follow established

industry standards where possible. A description of the business requirements for the

information, the attributes and attribute classifications shall be provided within the

associated metadata record for the data. If data attributes are provided in an attribute

table that is separate to the spatial data then an Estate Business Identifier (EBI) shall

be included in both the spatial data and the attribute table to enable the spatial features

and attributes to be linked.

2.16 Imagery Management – Image Tiling

2.16.1 Digital ortho imagery and LiDAR data are generally ‘tiled’ (divided into smaller

images) to manage file size.

2.16.2 It is recommended that the tiling process is undertaken by the data provider. It is also

recommended that the data is delivered in both an uncompressed and compressed

format.

2.16.3 The recommended tile size to the pixel resolution or Ground Sample Distance (GSD)

is detailed in Table 2-3, in all cases the uncompressed file size should be under

300Mb.

Table 2-3 Recommended Tile Sizes

Pixel resolution (GSD)

(m)

Tile size

(km)

0.05 0.5 x 0.5

0.1 1 x 1

0.2 2 x 2

0.5 5 x 5

2.16.4 A tile layout dataset or diagram shall be supplied. It is recommended that a layout is

provided in GIS format to allow it to be overlaid with the tiled images.

2.16.5 It is recommended that for most users images are used in compressed formats.

Imagery files in excess of 300mb on standard PCs will result in slow display rates.

There are numerous proprietary software programs available that can be used to tile or

compress data. These include ERDAS Imagine and ERmapper.

2.16.6 Digital imagery file size can be reduced by applying a compression algorithm. The

compression ratio can be varied, however the greater the compression the more the



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

quality of the image will be degraded. There are lossless image compressions

algorithms available, but the amount of compression is limited. In most cases it is

recommended that files are compressed to no more than a 10:1 ratio.

2.16.7 Tile File Names

2.16.7.1 The naming convention for tiles cut from a large data is generally based on

the co-ordinates values of the lower left corner of the tile. This can be

amended, as required, for smaller tiles.

EXAMPLE: Lower left corner: 298000E 6230000N

Tile Name: 2986230

2.16.7.2 If appropriate additional information can be added to the tile name e.g.

M6298623010110 where:

M=MGA

6=Zone 56

298=Easting

6230=Northing

1=0.1m resolution

01=January

10=2010

2.16.7.3 Tile metadata should record the following information in addition to E&IG

Standard Metadata requirements:

Release version;

Area of tile;

Date flown;

Camera/sensor type;

Photo scale;

Image Resolution; and

Digital Elevation Model (DEM) details (if relevant).

2.17 Hardcopy Archival

2.17.1 Where electronic documents do not exist, and hardcopy files are to be scanned for

archival, the following requirements shall apply unless otherwise specified in the

Statement of Work:

The plans shall be scanned at a minimum of 200dpi;

Raster images shall be saved as compressed tiff images (LZW compression);

Any colour plans shall be scanned as 24 bit jpeg images;

Images shall be cropped to minimum plan extents;

Images shall be rotated where necessary;



Sec

tion 2

Gen

eral

Dat

a S

pec

ific

atio

n

Skewed images shall be de-skewed (original dyelines may not be straight); and

Poor quality originals shall be enhanced (de-speckled and/or sharpened).

2.18 Vectorisation of Scanned Information

2.18.1 Vectorisation of hardcopy information and/or electronic images has been undertaken

by Defence in the past to capture vector features relating to Defence Properties.

Vectorisation of information is not recommended due to the low return on the

financial investment and should only be undertaken for a specific business purpose

where the financial value of undertaking the work is greater than the cost of

vectorisation.

Spatial Data Management Plan Specialised Data Specification


Spec

iali

sed

Dat

a S

pec

ific

atio

ns


Spatial Data Management Plan Specialised Data Specification


Spec

iali

sed

Dat

a S

pec

ific

atio

ns

SPECIALISED DATA SPECIFICATION

Specialised Data Specifications have been created to document standards for specific types of

spatial data that have requirements that may differ from, or be additional, to the General Data

Specification in Section 2. The Specialised Data Specifications provide more detailed

information relating to the requirements for specific types of data and how the specification

should be implemented.

The Specialised Data Specifications contained within the SDMP are listed below:

3 Master Site Plan Datasets 28

4 Spaces Plans 34

5 Reference Data 45

6 Engineering Detail Survey for Infrastructure and Assets 50

7 Land Management Data Error! Bookmark not defined.

8 Communications Data 58

9 Aerial Photography 66

10 Satellite Imagery 74

11 Master Planning Datasets 80

12 Contaminated Sites Data 84

13 Environmental Data 92

14 Hazards Data 101

15 GEMS Geo-Enabled Objects 118

https://www.defence.gov.au/estatemanagement/Governance/Policy/SDMP/Docs/Sections/14%20-%20Hazards%20Data.pdf

https://www.defence.gov.au/estatemanagement/Governance/Policy/SDMP/Docs/Sections/14%20-%20Hazards%20Data.pdf

Spatial Data Management Plan Section 3 Master Site Plan Dataset


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et


Section 3 – Master Site Plan Dataset

Not GEMS Geo-enabled

GEMS Geo-enablement Planned

Content GEMS Geo-enabled



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et

3 MASTER SITE PLAN DATASETS

3.1 Scope of Specification

3.1.1 The specification covers the capture and update of the Master Site Plan Dataset that

E&IG collects for Defence Properties, including Training Areas. The Master Site Plan

Dataset stores the position of infrastructure and asset features as listed in Table 3-1

and is a E&IG Key (or Foundation) Spatial Dataset upon which other spatial data is

developed and referenced.

Table 3-1 Scope of Master Site Plan Data

Feature Descriptions

Air Conditioning Services Road Features

Airport Infrastructure Security Services

Compressed Air Services Sewerage Services

Communications Networks Steam Services

Stormwater Drainage Structures

Electricity Services Survey Features

Fire Services Topographic Features

Fuel Services Traffic Features

Gas Services Vegetation

Oxygen Services Water Features

Property Features Water Reticulation

3.1.2 This dataset is used to manage and maintain existing infrastructure, to plan new

infrastructure on properties, and as a basis for the capture of Land Management data.

A sample of data from a Master Site Plan Dataset is shown in Figure 3-1.

Summary of changes with the Introduction of GEMS:

1. New or updated features must be attributed with their Estate Business Identifier

(EBI) via AutoCAD Extended entity data (XData).



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et

Figure 3-1 Master Site Plan Dataset - example data

3.1.3 The Master Site Plan data is collated from as-constructed design certified drawings

and verified through an Engineering Detail Survey and is accurate to ±0.05 m. To

maintain the integrity of the data source the Master Site Plan Dataset must be updated

to remain current and must be collected to the nominated accuracy.

3.2 Deliverables

3.2.1 The following deliverables shall be provided:

A dataset containing Master Site Plan data for all features that have been

created or updated.

A separate dataset shall be provided for each Defence Property.

Metadata record for each Master Site Plan Dataset.

3.3 Deliverable Templates

3.3.1 A dataset template in AutoCAD and an AutoCAD file containing sample data is

available on the Defence Estate Quality Management System at the following

location:


3.4 Data Deliverable Specification

3.4.1 Data Format

3.4.1.1 Data shall be delivered in either:

AutoCAD Drawing format. A detailed data specification is documented

in Appendix G respectively. It is recommended that the deliverable

templates are used as the basis of creating Master Site Plan Data.

An alternate GIS data format is currently being developed. Users

wishing to utilise this data format should contact GEMS & Business

Transformation.

3.4.2 Data Accuracy

3.4.2.1 The Master Site Plan Dataset shall have a horizontal and vertical accuracy

of ±0.05 m.

3.4.3 Engineering Detail Survey – Data Capture Requirements

3.4.3.1 Detail survey shall include all significant infrastructure and asset features

from the building line out.

3.4.3.2 Structures and buildings capture shall include the external walls of the

building, the roofline and the height of the roofline shall be captured.

3.4.3.3 Kerbs capture shall include the kerb profile, top and lip levels at tangent

points, changes of direction and grade, and changes in kerb type shall be




Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et

captured. Maximum 25 m intervals on straights and large radius bends, and at

nominal 5 m intervals on small radius bends.

3.4.3.4 Storm water and sewerage capture shall include manhole surface shape,

perimeter levels and invert levels, and the size and direction of pipes shall be

captured. Any change in direction of the pipes shall be recorded.

3.4.3.5 Underground Cables / Conduits capture shall include a single polyline

which shall be used to delineate the location of the cables and shall include

any change in direction.

3.4.3.6 Concrete lined drains and other surface drainage structures e.g. drop

structures capture shall include detail survey at 25 m intervals for long runs.

3.4.3.7 Road furniture and line-marking capture shall include edge lines to define

existing carriageway widths.

3.4.3.8 Trees with a trunk diameter greater than 0.2 m shall be located and the type,

trunk diameter and the spread defined. The diameter of the trunk shall be

measured 1 m above natural surface level. Trees shall be represented to scale,

with spot heights, diameter, species and height to be shown as text in the

drawing.

3.4.3.9 Readily observed information regarding features and services shall be noted

such as the size/diameter of culverts and lines between power poles.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et

3.5 Specific Data Requirements

3.5.1 Estate Business Identifiers

3.5.1.1 Appendix G – Master Site Plan Dataset AutoCAD Standards contains

specific requirements for attribution of features with Estate Business

Identifiers (EBI) to provide a linkage with SAP and Objective records.

3.5.2 Topology Specifications

3.5.2.1 Data must be captured so that it can be used within a GIS topological model

of points, lines, and polygons that can then be linked to a database.

3.5.2.2 The SDMP specifications were initially designed to meet CAD software

requirements where the data and information is designed to provide a detailed

drawing providing a good picture (rendering) of the data. Although the data

and information in a CAD file consist of symbols, points, lines, and poly-lines

these elements are referred to as simple features and do not have any topology

or link to a database.

3.5.2.3 A topologically structured GIS supports feature (object) relationships which

enables the GIS to perform advanced analysis of the data such as determining

the best route from point A to point B as is commonly performed by in-car

navigation systems. Capturing data using the topology specifications will

support the ability to perform spatial analysis (network analysis) on connecting

or adjacent features such as points, lines and polygons.

3.5.3 Topology Guidelines

3.5.3.1 The following features shall be collected in accordance with the topology

requirements defined within Section 2 of this document.

Polygons:

Buildings

Linework:

Storm Water/Drainage

Sewage pipelines

Water Supply pipelines

Communication cables

Electricity cables

Gas pipeline

Fuel pipelines

Fire water pipelines

Points related to:


Sewage



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 3

– M

aste

r S

ite

Pla

n D

atas

et

Water Supply

Communications

Electricity

Gas

Fuel

Fire water infrastructure

Text related to:


Sewage

Water Supply

Communications

Electricity

Gas

Fuel

Fire water infrastructure

Spatial Data Management Plan Section 4 Spaces Plan Dataset


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et


Section 4 – Spaces Plan Dataset






Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4 SPACES PLANS


4.1.1 The specification outlines the convention E&IG has adopted for the capture of data

for the Spaces Plan Dataset. The Spaces Plan Dataset is created for all Defence

Buildings and is distinct from an architectural floor plan in that it only shows the size,

shape layout and identification number of spaces and rooms within Defence

Buildings, door openings, staircases and fittings. The Spaces Plan Dataset is an E&IG

Key or Foundation Dataset upon which other E&IG data is based.

4.1.2 Where an existing building has a numbering schema in place, that numbering should

be adopted.

4.1.3 The data captured is used to assist building management through the allotment of

rooms, management of information technology assets, cleaning services, and changes

to buildings. A sample of data from a Spaces Plan Dataset is shown in Figure 4-1.

Figure 4-1 Spaces Plan Dataset - example data

4.1.4 The Spaces Plan Dataset is collated from as-constructed drawings, or through

measurement survey, and is accurate to ±0.05 m. This accuracy is required for this

data to be used as a base for the design of new infrastructure or services on Defence

Properties, and to provide data for future calculation to evaluate net return on assets.

To maintain the integrity of the data source the Spaces Plan Dataset must be updated

to remain current and must be collected to the nominated accuracy.

4.1.5 The Spaces Plan Dataset shall be updated, if any space or space number is changed,

within the notice period of change occurring as specified in contracts.

4.1.6 Information stored within each Spaces Plan Dataset includes fixed or static elements

such as external and internal wall outlines, doorways, voids, core areas, wet areas,

corridors, foyers, open spaces and undercrofts. The plans include columns, glazing

Summary of changes with the Introduction of GEMS:

2. Space numbering (of physical assets) is now referred to as Estate Business

Identifier (EBI). The EBI is stored in SAP in the Sort Field.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

and other openings (as a line or outline). Elements that shall be included within the

Spaces Plan Datasets are listed in the Estate Register Information Model (ERIM) at

Estate Class 2 where Estate Class 1 is “Space”.

4.2 Deliverables

4.2.1 A Spaces Plan shall be produced, and be distinct from architectural floor plans, for

each building level. There shall be one Spaces plan per level.

4.2.2 A metadata record for each data file.

4.2.3 Transmittal documentation containing the following information:

Sender’s details;

Date of transmittal;

Media type; and

List of files including the filename and a summary of changes made to the file.


4.3.1 A file template containing all file settings and layer structures, and a file containing

sample data is available on the Defence Estate Quality Management System at the

following location:


4.4 Required Inputs

4.4.1 Relevant space and level data for buildings shall be recorded in accordance with

ERIM requirements in SAP via the GEMS Master Data Process as documented on the

Defence Estate Quality Management System.

4.4.2 The Space Plan Dataset for new buildings will be created using the template that can

be downloaded from the Defence Estate Quality Management System.

4.4.3 Changes to existing buildings must be updated into the existing Space Plan Dataset

for that building. The dataset is stored within NSIMS and shall be supplied by the

E&IG Project Manager.


4.5.1 Data Format

4.5.1.1 Spaces plans shall be delivered as an AutoCAD drawing file (.dwg)

compatible with Release 2013.

4.5.2 File Names

4.5.2.1 The following filename format shall reflect the Floor/Level as follows:

Format: [Level EBI].dwg

Example: 0253-A0012-L02.dwg

4.5.3 Units of Measurement




Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.5.3.1 Data shall be captured in millimetres.

4.5.4 Spatial Accuracy

4.5.4.1 Data shall be produced to a horizontal accuracy of ±0.05 m.


4.6.1 Space Numbering (Space EBI)

4.6.1.1 The consistency of Space numbering is relied upon by many discrete

business areas in Defence including: building maintenance; voice and IT

services; and asset management. The space numbering standards must be

implemented within projects.

4.6.1.2 Building EBIs will be issued via the GEMS Master Data Process.

4.6.1.3 New Level and Space EBIs will be created by the Designer / Project

according to the rules set out on DEQMS.

4.6.1.4 New or updated Space numbering must be approved by the Defence project

point of contact prior to labelling.

4.6.1.5 The Space EBI format is described on DEQMS.

4.6.1.6 The Space and Level EBI shall be consistent with the EBI numbering

format as published on DEQMS, subject to the following considerations:

1. Existing EBI may be maintained to ensure continuity, Except in case of

more than 50% building refurbishment: or

2. Due to fire regulations (e.g. dispensations) and also to preserve building

record history, building refurbishments greater than 50% will require

new space identifier assignments (renumbering).

4.6.1.7 Space numbering shall commence from the first space encountered from the

main entry point of the building and continue in a clockwise and inward

direction. This convention shall apply to all levels of multi-level buildings

with numbering restarting from 001 on subsequent floors.

4.6.1.8 It is important to recognise the impact of space numbering during the

design process, the application of space identification, and the number for door

and window schedules.

4.6.2 Renumbering Spaces Associated with New Works

4.6.2.1 Where an existing space is split into multiple spaces, those new spaces

should be renamed using the existing space number plus consecutive letters of

the alphabet.

EXAMPLE: Space 050 becomes spaces 050A and 050B.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.6.3 Space Labelling

4.6.3.1 The requirements for space labelling are detailed within Estate &

Infrastructure Group Defence Signage And Labelling Standard (SLS) –

refer DEQMS.

4.6.4 Spaces Plan Data Capture

4.6.4.1 Spaces plans are to be expressed as simple, to-scale, diagrams with detail

kept to a minimum.

4.6.4.2 Drawing elements shall include external and internal wall outlines,

doorways, voids, core areas (including lifts and stairways), wet areas

(simplistically identified), corridors, foyers, open spaces and under croft areas.

The Spaces plans shall include columns, glazing and other openings (as a line

or outline).

4.6.4.3 External spaces include external stairs, ramps directly attached to the

building areas, and areas containing air conditioning equipment adjacent to a

building. Verandas and areas with a roof are also included within the

specification, but patios without a roof are not considered spaces in this

context.

Figure 4-2 Example external space capture of a covered area



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.6.4.4 Wet areas and ablutions shall be considered one space unless a door creates

a separate space.

Figure 4-3 Example wet area and ablutions as a single space

Figure 4-4 Example multiple wet area and ablutions space capture

4.6.4.5 Stairs and stairwells shall be considered a separate space except where they

are part of a corridor or a low landing.

Figure 4-5 Example stairs in a corridor and stairwell space capture



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et 4.6.4.6 Where an area comprises workstations or work areas divided by removable

or half height partitions or privacy screen each workstation or work area will

be deemed a space.

Figure 4-6 Example 1- workstations or work areas space capture

Figure 4-7 Example 2 - workstations or work areas space capture



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.6.4.7 Fire Hose reels shall be considered an individual space when contained

within an alcove or cupboard.

Figure 4-8 Example fire hose space capture

4.6.4.8 Electrical switch/substation and communications areas shall be considered

an individual space when contained within an alcove or cupboard or room.

Figure 4-9 Example electrical switch/substation and communications

areas space capture

4.6.4.9 All space plans must contain closed polygons for each space and a gross

external area for each floor on the appropriate SP_AREA layer. Refer 4.6.6.4

for the correct layer to use.

4.6.4.10 Each Spaces plan will record the Level EBI, refer 4.6.6.7 below.

4.6.4.11 Each space on the Spaces plan shall record its Space EBI as per 4.6.8

below.

4.6.4.12 Space Plan Datasets for new buildings shall be compiled by survey or from

as-constructed and architectural design plans.

4.6.4.13 Spaces plan data for existing buildings may be obtained from the following

sources:

Field Capture – Field measurement using appropriate electronic measuring

equipment and an audit of each Space. Field capture shall include the

following requirements:

Measurement of external/internal wall thickness, offset external wall,

change layer to internal wall;



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

Measurement of the hallway, main rooms, then all rooms off the

hallways and main rooms;

Doors shall be measured from the door jam and the correct opening

direction shown. The hook point of the door shall be the corner of the

wall (not the centre of the wall);

Only features that are permanently part of the building shall be

collected. No furniture such as tables, workstations or bookshelves shall

be captured unless specified within the Statement of Works.

Electronic CAD files - Existing CAD files may be available from various

sources. Care should be taken to consider their forms, quality, structure and

version.

Hardcopy or Scanned Raster Images – If no other information is

available hardcopy information can be used as a basis to assist in drafting

plans that meet the Data Specification. These shall be used with caution as

they may not be to scale. Note: Building footprints sourced from the

relevant Master Site Plan (Section 3) shall be used as a reference for

scaling.

4.6.4.14 Where existing Spaces plan information is to be used, data verification shall

be undertaken of the area impacted by the project via a site inspection. The site

inspection shall confirm that the Spaces plan is correct, to scale, and that

attribute information including space IDs and areas are correct. Where the

existing spaces layout differs greatly from the supplied plan within the

footprint of the project, the supplied plan shall be updated to reflect spaces

layout (within the footprint of the project). Minor incorrect measurements that

fall within the required accuracy are acceptable for existing data. If the site

inspection reveals differences in the Space Plan outside the project footprint

these should be notified to the Defence project.

4.6.5 Area Calculations

4.6.5.1 Defence has not adopted an agreed method of measurement (such as

BOMA) the following broad methods are outlined for this purpose.

4.6.5.2 It is preferred that Gross External Area and Actual Area (Usage Floor

Space in SAP) shall be calculated according to the following definitions.

Gross External Area – (Applies to a level) Required for estate value and

management calculations. The gross external area is the total external area

of the structure. It is the “footprint” of the structure and the maximum area

covered by it including the spaces.

Actual Area – (Applies to Spaces). This is equivalent to Usage Floor

Space (in SAP). The actual area is the area of a space from the outline

formed from the inside of each wall and not including the wall thickness.

4.6.6 Spaces Plan Presentation

4.6.6.1 Spaces Plans shall be drawn at 1:1 scale with coordinate 0,0 at the bottom

left of the drawing.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.6.6.2 Data shall be drawn square to the AutoCAD World UCS and displayed at

‘Drawing Extents’.

4.6.6.3 All Spaces plans for an individual structure shall be vertically registered

with building outlines coincident between levels to allow spaces plans to be

overlain with each other if required.

4.6.6.4 All spaces plan data shall be assigned to the correct layer structure listed in

Appendix H. No other information shall be included in the Spaces plan.

Table 4-1 shows the layers Gross External and Actual Area will be captured

on.

Table 4-1 Space Area Layers

Area Type Applies to Layer

Gross External Area Level SP_AREA_EXT

Actual Area Space SP_AREA_ACTUAL

4.6.6.5 Drawing borders shall be placed in Paperspace and on Layer “DRGSHT”.

4.6.6.6 A simple scale bar shall be placed with its left-hand end at coordinate 0,0 in

Model Space.

4.6.6.7 The drawing title shall be placed within an AutoCAD Block at the bottom

left hand corner of the drawing centred above the scale bar. The drawing block

attributes are listed in Table 4-2. The only visible attribute shall be the floor

name.

Table 4-2 Spaces Plan Block Attributes

Attribute Example Comments

FLOOR_NAME 0253/A0012/L02 The drawing title shall reflect the file

name of the drawing. This shall be the

only visible attribute.

AREA_AVAILABLE 100 Not required.

4.6.6.8 Annotation text style shall be Arial font and shall be a legible size when

Spaces plans are printed at A3. All text shall be stored within the AR_TEXT

Layer.

4.6.6.9 Space IDs shall be displayed on the plan centred on the Space and shall be

stored in the layer SP_ATTRIBUTE. The use of the attribute block SP_ATTS

is required. The Space ID should be centred within the space polygon and, for

example, not “arrowed” in.

4.6.6.10 Fire Hose reels shall be labelled with the text FH in the AR_TEXT layer.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 4

– S

pac

es P

lan D

atas

et

4.6.6.11 Descriptions of miscellaneous features including counters or display

cabinets shall be placed in the AR_TEXT layer.

4.6.7 Defence Estate Information System Update

4.6.7.1 Relevant space and level data for buildings as specified in ERIM shall be

stored in SAP via the GEMS Master Data Process.

4.6.8 Space Attributes

4.6.8.1 The attributes in Table 4-3 shall be populated within the SP_ATTRIBUTE

layer for each Space and shall be stored in an AutoCAD block.

4.6.8.2 Visibility of attributes on drawings should be discussed with the E&IG

Project Manager prior to commencement.

Table 4-3 AutoCAD Block Space - Attributes

Attribute Example Comments

EBI 1 0249/A0026/GF/001 The full Estate Business Identifier (EBI)

for the Space also known as the Sort

Field.

SPACE 001 Always visible

TYPE Store Refer ERIM Estate Class 2 (where

Estate Class 1 is “Space”).

AREA ACTUAL 10.6 Units = square metres.

FLOOR FINISH Carpet Refer to the ERIM value list ‘Floor

Finish’

Note 1: In existing Spaces data this attribute is called DEMS. Where such plans are

updated any new or updated Space Block Attribute must reflect Table 4-3Table

4-3 AutoCAD Block Space - Attributes. Unaffected Spaces Block Attributes

are not required to be migrated to the attribute structure at Table 4-3.

4.6.9 Optional Data Capture – Fixtures and Fitting

4.6.9.1 Higher detailed fittings such as workstations, toilets, urinals, basins, sinks,

showers and baths may be requested within the Statement of Works for

illustrative purposes but shall be provided as an X-reference to the Space Plan

on an appropriate layer, using a set of standardised blocks

Spatial Data Management Plan Section 5 Reference Data


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 5

– R

efer

ence

Dat

a


Section 5 – Reference Data






Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 5

– R

efer

ence

Dat

a

5 REFERENCE DATA


5.1.1 The specification covers all reports, building operational and maintenance manuals

(O&MM), as-constructed documents (ASCON), defect liability, equipment manuals,

and design manuals. This specification also covers as-constructed Computer Aided

Design (CAD) data relating to Defence Properties including the following:

Architectural plans (Design, etc.);

Engineering plans (Structural, Civil, Communications, Electrical, Hydraulic,

Mechanical etc.);

Landscaping; and

Demolition plans.

5.1.2 These documents are required for reference purposes and it is not expected that all

Section 2 General Specification requirements will be applied to the data. Please refer

to the following specification for details of which standards do apply.

5.2 Deliverables

5.2.1 The design and as-constructed documentation.

5.2.2 Reports, building operational and maintenance manual (O&MM), as-constructed

documentation, defect liability, and equipment manuals.

O&MM information is to be provided in accordance with the Defence

Instructions For Operations And Maintenance Manuals (O&MM) For Defence

Facilities & Infrastructure. Refer DEQMS.

5.2.3 Metadata record for each data file.

5.3 Deliverable Specification – General Reference Documentation

The specification details requirements in addition to those detailed in the Section 2 Data

Specification.

5.3.1 File Names

5.3.1.1 For O&MM’s file naming shall comply with the requirements set out in

Defence Instructions For Operations And Maintenance Manuals (O&MM) For

Defence Facilities & Infrastructure. Refer DEQMS

5.3.1.2 For As Constructed (ASCON) drawings file names must succinctly

summarise the information to allow users to quickly understand the drawing

content. File names must include the subject of information and Defence

Asset/Locality. Under-scores shall be used to separate text (space characters

must not be used).

Building or

Asset ID

File (drawings) name NSIMS name

(Metadata Title)

0703/A0020 0703_A0020_Electrical_Single Line Diagram.dwg 0703 Leeuwin Barracks -

A0020 Contractor Centre –



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 5

– R

efer

ence

Dat

a

Electrical Single Line

diagram,

0089/A0012 CCN_AR_E25_1311_2_0089_A0012_Room Layouts.dwg 0089 HMAS Stirling -

A0012 Squash Courts and

Weight Training Room –

Room Layouts

0767/A5041 0767_A5041_Arch001.dwg 0767 Campbell Barracks –

A5041 Battery Store – Arch

Floor Plan

0967/A0222 0967_A0222_Arch_Elevations.dwg 0967 RAAF Pearce – A0222

Health Centre – Arch

Elevations

Table 5-1 Example ASCON File Names

5.3.1.3 For other document types, accepted industry standards shall be applied.

These typically include elements that suggest, location, discipline, revision etc.

5.3.2 Directory Structure

5.3.2.1 Accepted industry standards shall be applied.

5.3.3 Metadata

5.3.3.1 A SDMP metadata record is required for each document.

5.4 Deliverable Specification – Design Drawings

The specification details requirements in addition to those detailed in the Section 2 Data

Specification.

5.4.1 Data Format

5.4.1.1 Accepted industry standards shall be applied to Design Drawings.

5.4.2 File Names

5.4.2.1 Accepted industry standards shall be applied.


5.4.3.1 Unless otherwise specified in the Statement of Work, drawings are to be

provided within the following Directory Structure:

Format: [PropertyEBI][GEMSPropertyName]\[ProjectName]\[Discipline]\

PropertyName is the name of the relevant property as per the GEMS

Property EBI.

ProjectName is the Project Title, Facility Name, Asset Name or Building

Use.

Discipline is the drawing type. (Architectural, Civil, Electrical, Mechanical

etc).

Example:



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 5

– R

efer

ence

Dat

a

5.4.4 Datum, Coordinate Systems, Spatial Accuracy and Integrity of Features

5.4.4.1 Design drawings are not required to meet the standards defined in Section 2

relating to datum, coordinate systems, accuracy and integrity of features.

5.4.5 Drawing Details

5.4.5.1 The information in Table 5-2 is to be provided in the drawing title block.

The information in Table 5-3 is optional.

5.4.5.2 Any information not shown on the title block may be supplied as a list or

spreadsheet with the transmittal documentation.

Table 5-2 Design and As-Constructed Title Block Requirements

Element Description

TITLE Drawing title e.g. Detail and Level, Site Plan etc.

Do not include the Project title, facility name, or the following

punctuation symbols: semi-colons, colons, forward or backslash, full-

stops.

PROPERTY NO GEMS Property EBI for the Property/Site.

PROJECT Project Title, Facility Name, Asset Name or Building Use

DISCIPLINE Architectural, Structural, Survey, Mechanical, Hydraulics, Electrical,

As-constructed, Environmental etc.

SCALE Plan scale (Plotted scale of plan)

DATE Date of plan

REVISION Revision number

Table 5-3 Design and As-Constructed Title Block Optional Information

Element Description

CONTRACTOR The Principal Contractor

PLAN NO Defence Plan No or Contractors Plan No.

SIZE Plan size (A0, B1 etc.)

XREFs A list of attached plans

5.4.5.3 All x-referenced drawings shall be bound to the parent file and the

individual references shall be deleted.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 5

– R

efer

ence

Dat

a

5.4.5.4 All drawings are to be cleaned up (purged of unused layers and blocks) for

archive purposes.

5.4.5.5 All referenced images are to be supplied with the drawing. Image references

are to be relative (not full path).

5.4.5.6 Where multiple drawings/sheets are stored in a single AutoCAD file, each

drawing shall be referenced in the metadata for that file.

Spatial Data Management Plan Section 6 Engineering Detail Survey for Infrastructure Assets


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 6

- E

ngin

eeri

ng D

etai

l S

urv

ey f

or

Infr

astr

uct

ure

Ass

ets


Section 6 – Engineering Detail Survey

for Infrastructure Assets






Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 6

- E

ngin

eeri

ng D

etai

l S

urv

ey f

or

Infr

astr

uct

ure

Ass

ets

6 ENGINEERING DETAIL SURVEY FOR INFRASTRUCTURE AND ASSETS


6.1.1 The specification covers the capture of infrastructure, asset and topographical features

on Defence Properties using surveying techniques. Engineering detail survey is

predominantly undertaken by E&IG to collect data of high spatial accuracy (±0.05 m)

to create or update E&IG Master Site Plan dataset and in some cases condition

appraisal information.

6.1.2 This specification will be used when a Major or Minor Work or Activity Request has

been issued to undertake an engineering detail survey on a Defence Property.

6.1.3 Features captured using engineering detail surveys are listed in Table 6-1.

Table 6-1 Scope of Data Collected using Engineering Detail Survey

Feature Descriptions

Air Conditioning Services Road Features

Airport Infrastructure Security Services

Compressed Air Services Sewerage Services

Communications Networks Steam Services

Stormwater Drainage Structures

Electricity Services Survey Features

Fire Services Topographic Features

Fuel Services Traffic Features

Gas Services Vegetation

Oxygen Services Water Features

Property Features Water Reticulation

6.2 Deliverables

6.2.1 The deliverables shall be defined in the specific survey brief. The following

deliverables are likely to be included:

A dataset containing collected features. This dataset shall meet the

Specification for Master Site Plan Datasets (Section 3).

A digital triangulated terrain model.

A survey report stating methods applied, accuracy achieved, discrepancies and

including Survey Control diagrams.

A Metadata record for each data file.

Hard copy survey plan(s) at a scale of 1:500 (as required).

6.3 Data Inputs

6.3.1 The existing Master Site Plan Dataset shall be used as the basis to conduct and update

surveys. The existing Master Site Plan Dataset shall be sought from the relevant

E&IG EMOS Contractor.

6.4 Deliverable Specification



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 6

- E

ngin

eeri

ng D

etai

l S

urv

ey f

or

Infr

astr

uct

ure

Ass

ets

6.4.1 Data Format

6.4.1.1 Digital data can be collected in either GIS or AutoCAD format compatible

with the Section 2 Data Specification. AutoCAD files shall be both provided

in both 2D and 3D.

6.4.2 Accuracy

6.4.2.1 All surveys shall have a horizontal and vertical accuracy of ±0.05 m.

6.4.2.2 For the purposes of establishing the coordinated datum for the As-

Constructed survey shall be established using a minimum of 3 control points.

6.4.3 Quality Assurance

6.4.3.1 All As-Constructed detail data shall be reviewed by a senior surveyor. The

surveyor shall certify completeness, and that accuracy standards detailed in

these specifications are achieved.

6.4.3.2 The certification shall include a signed hardcopy plan of the As-Constructed

data and a report detailing the Project number, methodology, discrepancies and

new control marks.


6.5.1 Survey Control Stations

6.5.1.1 Survey Control Stations are physical marks in the ground which are used by

surveyors as a reference location. A Survey Control Station has horizontal co-

ordinates and a vertical height recorded against it.

6.5.1.2 Survey Control Stations, or Defence Facilities Reference Points (DFRP),

stored with WGS-84 and or GDA94/GDA2020 compliant coordinates are

available at most Defence Properties and shall be used as the co-ordinate

origin for all survey work undertaken for and on behalf of E&IG.

6.5.1.3 Where suitable Survey Control Stations are not available in the area to be

surveyed, or there is a possibility that an existing Survey Control Station may

be disturbed/destroyed due to construction, a Survey Control Station shall be

established by the surveyor to the following ICSM Standards:

Horizontal Control shall be established to Class B, equivalent to Order 2; and

Vertical Control shall be established to Class LC, equivalent to Order L3 for

differential levelling and Class C, equivalent to Order 3 for GPS height.

6.5.1.4 Survey Control Stations shall not be located on sandstone walls, tree trunks

or other sensitive areas. Any paint used shall be a removable water based type.

With placement of new Survey Control Station, the surveyor shall take into

account the possibility of disturbance by mowers or other vehicular traffic.

6.5.1.5 New Survey Control Stations shall be listed on a Survey Control diagram

that includes a locality sketch, the type of stabilisation, coordinates of the



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 6

- E

ngin

eeri

ng D

etai

l S

urv

ey f

or

Infr

astr

uct

ure

Ass

ets

control and the Reduced Level (RL). The diagram shall be attached to the

Survey Report.

6.5.1.6 New Survey Control Stations shall be included in an update to the Master

Site Plan Dataset.

6.5.2 Continuously Operating Reference Station (CORS) Networks

6.5.2.1 A CORS is a network of global navigation satellite reference stations that

will provide code range and carrier phase data to users. CORS are managed

across Australian States and Territories by state government and private

organisations.

6.5.2.2 A CORS network within the vicinity of the Defence Property can be used to

collect engineering detail survey.

6.5.3 Topographical Information

6.5.3.1 Ground survey of the natural surface shall be undertaken to a vertical

accuracy of ±0.05 m over the entire site.

6.5.3.2 The grid spacing shall be approximately 25 m. This spacing can be

increased by the surveyor if warranted by the terrain, providing the accuracy

limits are maintained and the changes of grade are surveyed.

6.5.3.3 All topographical features shall be correctly strung to ensure accurate

modelling.

Spatial Data Management Plan Section 7 Land Management Data


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 7

Lan

d M

anag

emen

t D

ata








Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 7

Lan

d M

anag

emen

t D

ata

7 LAND MANAGEMENT DATA


7.1.1 The specification covers the requirements for data depicting the physical location of

Service Activities for Base Services.

7.1.2 The purpose of this specification is to standardise the collection of Land Management

data including GEMS data requirements.

7.1.3 The Land Management activities that require spatial representation are listed in Table

7-1.

Table 7-1 Land Management data types

Land Management

data types

Usage Description

Garden Beds A defined area that supports vegetation growth provided for aesthetic

purposes. May be contained with a garden bed surround.

Maintained Grass A defined area that requires a certain level of attention and care to

maintain a desired look and intention.

Amenity Trees A tree or group of trees is to be recorded if active management is required

such as heritage, environment, safety risk, capability significance or

aesthetic purposes.

Commemorative

Planting

A group of trees or plants that commemorate specific events or people.

Environmental

Improvement

An area set aside for environmental improvement, such as bush/species

regeneration.

Revetment Structure for protection of personnel and facilities from explosion/blast

impacts.

Channel and Open

Drain

Type of drain that collects waste water from a surface area.

7.2 Deliverables

7.2.1 The following deliverables shall be provided:

A spatial dataset containing Land Management data for all features that have

been created or updated.

There shall be a separate spatial dataset for each Defence Property.

There shall be a separate spatial dataset for each Land Management data type.

Metadata record for each Land Management spatial dataset, documented as

GIS Data-Vector.

GEMS data record(s) as specified in section 7.4.2 below.

7.2.2 Spatial data will be captured in Shapefile format in accordance with the requirements

of Section 2 General Data Specification, except where specified otherwise in this

section.

7.2.3 Information to be captured/updated and stored with each feature is described at

Appendix I.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 7

Lan

d M

anag

emen

t D

ata

7.2.4 Filename requirements are provided for each Land Management data type and

Appendix I.

7.2.5 GEMS attribute requirements for GEMS records are described at Appendix I.


7.3.1 A set of template datasets are provided as part of the SDMP to assist in the

implementation of the SDMP specification. The template is available on the Defence

Estate Quality Management System (DEQMS) site.



7.4.1 Data Capture Approach

7.4.1.1 Where available the, now retired, Garrison Support Service Contract

Mapping data can be used as a starting point for any data capture update task.

7.4.1.2 Master Site Plan data shall be used as the primary reference dataset.

7.4.1.3 Land Management dataset features shall align with reference features in

Master Site Plan datasets where appropriate. E.g. a Land Management Garden

Bed polygon must align with the garden bed as shown in the Master Site Plan.

7.4.1.4 Ortho-rectified high resolution imagery may also be used as a reference

dataset in the absence of Master Site Plan dataset and or as a supplement to aid

interpretation.

7.4.1.5 Field verification may be required to confirm Land Management dataset

extents and maintenance standards.

7.4.2 GEMS Data Records

7.4.2.1 The number of GEMS data records to be delivered for each Land

Management data types is specified in Table 7-2 Land Management data type

GEMS Record Requirements below.

Table 7-2 Land Management data type GEMS Record Requirements

Land Management

Data Type

GEMS Record Requirements

Garden Beds To be recorded as a single record for garden beds with the same

maintenance standard attribute for a Property.

For example, if three maintenance standards are required for the

range of garden beds present on a Property, three GEMS records

will be required, one for each maintenance standard.

Maintained Grass One record per instance of continuous area of the same ‘cut type’




Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 7

Lan

d M

anag

emen

t D

ata

attribute.

For example, if five cuts types are required for the range of grass

types present on a Property, five GEMS records will be required,

one for each maintenance standard.

Amenity Trees One record per instance (Individual or Group of Trees)

Commemorative

Planting

One record per instance (single planting, group or avenue).

Environmental

Improvement

One record per instance.

Revetment One record per instance.

Channel and Open

Drain

One record per instance (Distinct segment between every

significant change in the channel property, such as shape, lining).

Spatial Data Management Plan Section 8 Communications Data


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a



Pending Review






Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

8 COMMUNICATIONS DATA


8.1.1 The specification encompasses all communications networks on Defence Properties

outside the line of the building, excluding networks within buildings. The

specification includes data relating to telephone, data, fire control and security

networks.


been issued to undertake the creation or update of communications data.

8.1.3 The communication data is used to amend and update existing spatial and textual

databases, assist in maintenance and planning, and provide a permanent record of

development.

8.1.4 Currently communication network data is stored in two formats. Over time these

formats will change through the implementation of geodatabase data formats to store

this information.

A Communications Asset Database known as the Integrated Cable

Management System (ICAMS) stores attributes relating to pits, cables and

conduits. Data attributes relating to communication assets are collected through

field work or from As-Constructed drawings and entered into the database.

The E&IG Master Site Plan Dataset for each Property stores the location of

Pits, Cables and Conduits. Communication features are captured through Field

Survey techniques defined in Section 7 of the SDMP or from As-Constructed

drawings. The features as added to the Master Site Plan Dataset for the Property

as per the specifications provided in Section 3 of the SDMP.

8.2 Deliverables

8.2.1 Updated Communications Database

8.2.2 Updated Master Site Plan Dataset

8.2.3 Photographs of pits

8.2.4 Metadata record for each data file.


8.3.1 A file template containing all file settings and layer structures, and a file containing

sample data is available on the Defence Estate Quality Management System

(DEQMS) at the following location:


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



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

8.4 Required Inputs

8.4.1 E&IG Region Communications Database

8.4.2 E&IG Master Site Plan Dataset


8.5.1 Extended Entity Data (XData)

8.5.1.1 The Integrated Cable Management System (ICAMS) is linked to

Communications Conduits and Pits stored in the Master Site Plan Dataset

using AutoCAD Extended Entity Data (XData). This is required to allow

spatial query functions and thematic mapping of communications cable

networks to be carried out.

8.5.1.2 Extended Entity Data (XData) Specification for Communication Pits

8.5.1.3 The XData shall be added to the Pit feature and the corresponding Pit

Number text in the Master Site Plan.

Registered Application Name: “GFIScomms”

Code 1000, ASCII string: “Compit”

Code 1000, ASCII string: [Pit No] (e.g. P0673)

8.5.1.4 Extended Entity Data (XData) Specification for Conduits

8.5.1.5 The XData shall be added to the Conduit feature in the Master Site Plan.

Registered Application Name: “GFIScomms”

Code 1000, ASCII string: “Conduit”

Code 1000, ASCII string: [AutoCAD Entity Handle of Polyline] (e.g.

2B970)

8.6 Field Capture

8.6.1 Location of the communications network (pits and conduits) shall be captured from

either As-Constructed drawings or through using Field Survey techniques that

comply with the current Survey Specification for Facility Detail.

8.7 Data Capture

8.7.1 Communications Pits

8.7.1.1 All communications pits shall be numbered and clearly labelled. The pit

numbers shall be allocated by the appropriate Information and

Communications Technology Liaison Officer.

8.7.1.2 The labels shall be made of aluminium and engraved with the appropriate

pit number using standard 5mm high number stamps. Pit labels shall display

the pit number, the ‘from pit’ and the ‘to pit’ (Figure 8-1).



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

8.7.1.3 Pit labels shall be attached to the collars of pits with Ramset concrete nails.

DATA/TELECOMMUNICATIONS

CABLE ROUTE /PIT MARKER

FROM PIT TO PIT

PIT NUMBER

Figure 8-1 Communication Pit Labels

8.7.1.4 Each pit number shall be prefixed by the letter “P” and sufficient

characters allocated to allow all pit numbers to be the same length (e.g.

P0001, P1000).

8.7.1.5 Each pit shall be photographed and the image provided .tiff or .jpg format.

The photographs shall be named with the pit number (e.g. Photograph of pit

1000 should be named 1000.jpg).

8.7.1.6 A template shall be displayed within each photograph clearly showing the

base number, date and pit number.

8.7.1.7 A complete condition appraisal shall be carried out and the

communications pit information entered into the Communications Asset

Database ‘Compit’ Table (Table 8-1).



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

Table 8-1 Communication Pit Data

Communications Asset Database Table Name: Compit

Field Name Type Size Description

PITID Long Integer Auto Number

PIT_NO Text 255 Unique pit number

BaseNo Double Defence Property EBI (from

GEMS)

PROJECT Text 50 Project name/number

TYPE Text 100 Material type (concrete, plastic)

LID_MATERIAL Text 50 Lid Material (PVC, Metal,

Concrete)

SIZE Text 50 Size of pit

LOCATION Text 100 Nearest building number or zone

NO_LIDS Integer Number of lids

PADLOCKS Integer Number of Padlocks

KEY_NUMBER Text 50 Key number

SECURITY Text 100 Security status (locked or

unlocked)

CONDITION Text 100 Condition of pit

ACTION Text 255 Remedial action if any required

COMMENTS Text 255 Comment

CONDUITS Integer Number of conduits entering pit

CABLES_info Text 50 Details of Number & Type of

cables in pit

DEPTH Double Depth of pit

GFISx Double X co-ordinate of pit

GFISy Double Y co-ordinate of pit

GFISzoom Double GFIS zoom (default is 30)

Last_Inspection Date/Time Date of inspection

Acadent Text 50 AutoCAD entity handle of block

in dwg file

8.7.2 Conduits

8.7.2.1 All conduits shall be clearly labelled.

8.7.2.2 Labels shall be made of Traffolyte (or another E&IG approved non-

deteriorating material) displaying the conduit number in black letters on a

white background.

8.7.2.3 The label shall be fixed to the communication pit wall in a secure manner

(screws or liquid nails) in the vicinity of the conduit opening and positioned

in such a manner that there is no ambiguity of conduit numbering.

8.7.2.4 The conduit number shall be a four-digit integer that contains preceding 0s

(eg. 0001, 0010).



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

8.7.2.5 The conduit information shall be entered into the Communications Asset

Database ‘Conduit’ Table (Table 8-2).

8.7.2.6 Adjacent conduits that run between pits or buildings shall be represented

by a single polyline within the Master Site Plan. The AutoCAD entity handle

for the polyline shall be added in the ‘Conduit’ table ‘fk_AcadEnt’ field (see

Table 8-2) for all the conduits represented by the polyline. The AutoCAD

entity handle shall be attached to the polyline within the Master Site Plan

using AutoCAD’s Extended Entity Data in for format provided in Section

8.5.1.

Table 8-2 Communications Conduit Data

Communications Asset Database Table Name: Conduit

Name Type Size Description

CONDUITID Long Integer Auto number

CONDUIT Text 50 Unique conduit identifier

BASENO Long Integer GEMS Property EBI Code


TYPE Text 100 Material type

SIZE Double Diameter of conduit

FROM Text 50 Start Pit or building number

TO Text 50 End Pit or building number

CONDITION Text 100 Condition

COMMENT Text 255 Comment

OPENING Text 50 Type of opening (Bell mouth, cut-off)

% FULL

CAPACITY

Double Estimate of % full

SHIELD WIRE Text 3 Yes or No

EARTH STAKE Text 3 Yes or No

PULL ROPE Text 3 Yes or No

DEPTH Double Depth in metres

LENGTH Double Length in metres

fk_AcadEnt Text 50 AutoCAD entity handle of conduit in

dwg file

8.7.3 Cables

8.7.3.1 All cables shall be clearly labelled.

8.7.3.2 The label shall be fixed to the cable in a secure manner, near the top of the

pit if possible and positioned in such a manner that it is clearly visible when

the pit is opened.

8.7.3.3 The method of labelling shall be permanent, durable and easy to identify.

Labels should be made of Traffolyte (or another E&IG approved non-

deteriorating material), with black letters on a white background fixed by

cable ties at either end.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

8.7.3.4 The ‘cable number’, ‘from creation’ and ‘to termination’ must be clearly

printed on the label. Labels shall be placed on cables at start and end, and at

every communications pit in between (Figure 8-2).

Cable Number

From B192 To B199

Cable tie Cable tie

Figure 8-2 Communication Cable Labels

8.7.3.5 The cable numbers shall be a three-digit integer containing proceeding 0s

(eg. 001, 010).

8.7.3.6 Where a cable splits a hierarchal numbering system shall be adopted. This

will enable all cables to be traced from the origin to the termination point.

The hierarchal numbering system shall follow the following convention:

where cable 001 splits into two or more cables the new branches should be

numbered 001-001, 001-002 etc: where cable 001-001 splits the new

branches should be numbered 001-001-001, 001-001-002 etc.

8.7.3.7 The cable information shall be entered into the Communications Asset

Database ‘Cable’ Table (Table 8-3).

Table 8-3 Communication Cable Data

Communications Asset Database Table Name: Cable


CableID Long

Integer

Auto number

CABLE_NO Text 50 Unique cable identifier

BASENO Long

Integer

Defence Property EBI (from GEMS)


TYPE Text 50 Cable type (optic fibre/copper)

SIZE Double Size (mm) or capacity (pairs/cores)

COLOUR Text 50 Cable colour

JOINT

LOCATION

Text 150 Location of joint (Pit No eg P1004)

JOIN TYPE Text 100 Type of joint

CREATED Text 100 Origin of cable (eg Bldg 1001)

TERMINATES Text 100 Termination point (eg Bldg 1002)

COMMENTS Text 255 Comments

SECOND JOIN Text 100 Location of second joint (Pit No eg

P1004)

LENGTH Double Length of cable



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 8

Com

munic

atio

ns

Dat

a

Communications Asset Database Table Name: Cable


OWNER Text 50 Owner of cable (Defence, Telstra)

CONDITION Text 50 Condition

SECURE Yes/No Security status (secure network)( Yes, No)

FROM

CABINET

Text 50 Cabinet No from (if applicable)

TO CABINET Text 50 Cabinet No to from (if applicable)

8.7.4 Conduit/Cable Linking

8.7.4.1 Every conduit that a cable runs through shall be recorded within the

Communications Asset Database. One entry shall be made for each

conduit/cable combination.

8.7.4.2 The conduit cable link information shall be entered into the

Communications Asset Database ‘CondCableLink’ Table (Table 8-4).

Table 8-4 Communications Conduit Cable Link Data

Communications Asset Database Table Name: CondCableLink

Name Type Description

BaseNo Long Integer Defence Property EBI (from GEMS)

Conduit Long Integer Conduit number (ConduitID from Conduit table)

Cable Long Integer Cable number (Cable ID from Cable table)

Order Integer Sequence of conduit/cable section (optional)

Spatial Data Management Plan Section 9 Aerial Photography


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy








Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9 AERIAL PHOTOGRAPHY


9.1.1 This specification applies to the capture and post processing of aerial imagery over

Defence Properties by E&IG Contractors using cameras and digital sensors mounted

on aircraft.

9.1.2 The focus of these specifications is on the delivery of final products that meet E&IG’s

requirement for current and future use in the most cost-effective manner. Within the

foreseeable future, Aerial Photography Acquisition Programs are likely to involve one

of a finite number of digital camera/sensor technologies. For this reason, the imagery

acquisition hardware/software technologies are not specified here. Instead, it is the

responsibility of the contractor to meet the Deliverable Specifications using the most

appropriate technology.

9.2 Deliverables

9.2.1 The primary deliverable from aerial photography is digital imagery which should be

supplied in TIFF and compressed ECW format. In the case of vertical photography,

the imagery must be ortho-rectified and other secondary deliverables may also be

required (see Section 3.3).

9.3 Acquisition Requirements

9.3.1 Platform

9.3.1.1 Aircraft will be required to operate at altitudes from 1,200 feet to 25,000

feet above ground level and have a suitable altitude range for the project. In

exceptional circumstances it may be required to fly at higher altitudes.

9.3.1.2 The Contractor will only deploy aircraft that are maintained in accordance

with manufacturers’ and statutory requirements and have current airworthiness

certification. E&IG will also require written acknowledgement from the

Contractor that all aircraft operations and clearances will be the responsibility

of the Contractor and that they will be undertaken in accordance with

Australian Air Safety Regulations.

9.3.2 Flight Planning

9.3.2.1 It will be the responsibility of the Contractor to plan the photographic sortie

to meet the requirements of the project and the specifications outlined in this

document. This includes managing situations such as obtaining permission to

enter property to survey ground control points, or to place a GPS ground

station.

9.3.2.2 Approval to acquire imagery over Defence installations (especially

Airfields) shall be gained prior to any imagery being flown. The contact

details for the respective approval authorities shall be provided to the

contractor.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9.3.2.3 The contractor shall build a suitable lead time into the flying program to

allow for the approvals.

9.3.3 Special Acquisition Requirements

9.3.3.1 When the photography is required for oblique or pictorial purposes only,

optimum image quality will be sought. When the photography is required for

ortho-rectification the imagery should be sourced using a calibrated metric

camera/sensor system.

9.3.4 Camera

9.3.4.1 Vertical photography will be exposed using a large format metric camera or

sensor. Details of any proposed metric camera to be used for the project must

be submitted to E&IG for approval. For vertical photography the Contractor

will provide a current calibration certificate from the manufacturer or an

approved standardising laboratory for any sensor lens that will be used.

9.3.4.2 Oblique photography may be exposed with smaller format, side mounted

cameras where appropriate and acceptable to E&IG. Specific specifications for

this type of camera may be contained in the project brief and are not contained

in this document.

9.3.5 Image Resolution

9.3.5.1 For vertical photography the image resolution (ground sample distance or

GSD) and the area to be covered will be defined in the project brief. The

Contractor will be required to demonstrate that the defined resolution is

achievable.

9.3.6 Stereo Imagery

9.3.6.1 All vertical aerial photography will be acquired as overlapping (stereo)

frames or swaths.

9.3.6.2 For perspective centre cameras the required forward overlap between

consecutive photographs in each flight strip will be 60% unless otherwise

specified. The deviation range in forward overlap will not exceed +/- 5%.

9.3.6.3 The minimum lateral overlap shall be 25% unless otherwise specified. The

deviation range in lateral overlap will not exceed +/- 5%.

9.3.6.4 For push broom sensors the forward, nadir and back view angles will be

required. The minimum lateral overlap shall be 30% unless otherwise

specified.

9.3.7 Camera Attitude

9.3.7.1 Photography will not be undertaken when atmospheric conditions are likely

to produce excessive tilts in the aerial photographs or deviation from flight

paths.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9.3.7.2 Compensation is to be made for crabbing and drift by rotating the camera

about the vertical axis such that the lateral edges of each frame are parallel to

and not displaced laterally from the intended flight path by more than 5% of

the specified side overlap.

9.3.8 Atmospheric Conditions

9.3.8.1 No cloud or cloud shadow should obscure detail on any area being

photographed. However, if the Contractor considers that conditions on the day

of the flight will not improve once on site, contact will be made with E&IG to

decide whether the photography is to be flown.

9.3.8.2 The photography will not be attempted when smoke, haze or any other

conditions would impair the quality of the photographic image. However, if

the Contractor believes conditions will not improve once on site it is critical

that contact must be made with E&IG to decide the future of the project.

Failure to consult with E&IG before proceeding with the photography under

marginal conditions could lead to rejection of the materials captured.

9.3.9 Solar Altitude

9.3.9.1 Photography over open terrain with low relief will not be attempted when

the solar altitude is less than 25 degrees, or less than 35 degrees over steep or

timbered country.

9.3.9.2 Where water surfaces are extensive over the area being photographed, the

solar altitude will be such that the sun’s reflection does not appear in the

photographs.

9.3.9.3 If a project cannot be completed in one sortie or on the same day every

effort must be made to complete the outstanding runs at the first weather

window of opportunity. If photography is being undertaken to complete a

project or to re-fly rejected frames taken some days, (or weeks) earlier, careful

consideration must be given to the time of day the adjacent runs were

captured. The next additional new run or re-fly must be undertaken as close to

the same time of day as possible.

9.3.10 Tidal Conditions

9.3.10.1 For projects that include the capture of aerial photography over large

coastal water bodies every effort must be made to complete the intertidal zone

in one sortie. If it cannot be completed in one sortie then any appending runs

must be flown at a similar tide height and sun angle if logistically possible. If

only one parameter is possible the similar tide height is most critical.

9.3.11 Coverage

9.3.11.1 Each run will extend outside the specified area by at least one stereoscopic

pair, i.e. two principal points will fall outside of the specified area at the

beginning and end of each run.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9.3.11.2 The first and last runs will have at least 15% of each photograph extending

laterally outside of the boundaries of the specified area.

9.3.12 Airborne DGPS Data

9.3.12.1 The recording of airborne Differential Global Positioning System (DGPS)

data for photo centres and photo metadata is part of the aerial photography

acquisition requirements. The contractor is responsible for ensuring that this

data is recorded for all vertical aerial photography.

9.3.12.2 The contractor is required to supply the photo metadata to E&IG within 7

days of the acquisition of the photography

9.3.13 Image Quality and Colour Balance

9.3.13.1 The contractor will be responsible for the supply of raw metric digital

imagery to the same quality of Colour Balance and Consistency as the

Benchmark imagery samples (where supplied by E&IG). E&IG understands

that due to various climatic and seasonal conditions there will be some

variations to the Benchmark Colour imagery. In this case sample images from

the new photography, representative of the area, should be supplied to E&IG

for acceptance.

9.3.13.2 E&IG may undertake random checks of the digital imagery supplied for

colour balance and extraneous materials appearing on the scans plus other

image degradation (such as steps or banding of scan lines). Results of this

assessment will be made known to the contractor and if considered excessive

remedial action by the contractor will be required.

9.4 Orthophoto Specifications

9.4.1 The focus of these orthophoto specifications is to ensure the final deliverables meet

E&IG’s requirements for current and future use in the most cost-effective manner. For

this reason, the actual imagery acquisition hardware/software technologies and

production methodology to be used are deliberately not specified. In the case of ortho-

rectified imagery E&IG will determine the image resolution required for their project

requirements. It will be the responsibility of the contractor to ensure that the

specifications applicable to the specified resolution are met.

9.5 Orthophoto Deliverables

9.5.1 Deliverables will often be limited to the supply of orthophoto (ortho-rectified image)

tiles (ie the primary deliverable). In some cases, E&IG may also require the supply of

secondary deliverables. This is particularly the case when the raw stereo imagery and

associated data sets are required for photogrammetric mapping.

9.5.2 Primary Deliverables

The primary deliverables are 3 band (RGB) orthophoto tiles.

In some instances there may be a requirement for 4 band (RGB & NIR)

imagery.

A metadata record for each data file.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9.5.3 Secondary Deliverables

Raw (un-rectified) imagery as frames or swathes

Ground control identification sketches and their surveyed coordinates (in terms

of MGA/AHD)

Aero-triangulation report/s

Image support files (interior and exterior orientation data for each frame or

image swathe)

Digital elevation model (DEM)

Key diagram in ESRI shapefile format

DGPS camera centre air station coordinates (in term of MGA/AHD)


9.6.1 Table 9-1 sets out the typical uses for orthophotos at various resolutions and lists their

associated accuracy and tiling requirements. E&IG brief will indicate the appropriate

resolution for each defined area. Table 9-2 defines the orthophoto technical

specifications.

Table 9-1 Orthophoto Options for Resolution and Accuracy

Description/Use Orthophoto

Resolution

(GSD)

Spatial

Accuracy

(RMSE)

Orthophoto

tile size

Very low level photography / Very detailed

engineering and infrastructure design.

5cm 15cm 500m x 500m

Standard resolution for built environment /

Facilities management

10cm 30cm 1km x 1km

Standard resolution for built environment /

Facilities management

15cm 45cm 1km x 1km

Standard resolution for rural environment / Range

management

20cm 60cm 2km x 2km

Standard resolution for rural environment / Range

management

25cm 75cm 2km x 2km

Standard resolution for rural environment / Large

range management

30cm 90cm 2km x 2km

Very high level photography / Regional area

coverage

40cm 120cm 5km x 5km

Very high level photography / Regional area

coverage

50cm 150cm 5km x 5km

Table 9-2 Orthophoto Technical Specifications

General Description

Coverage E&IG will provide a full description to define the extent of the each area



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

Horizontal Datum All survey values/airborne DGPS data will be supplied in terms of

GDA94 and be directly tied in to the local published survey control

network.

Vertical Datum All elevation data must be supplied as heights above/below Australian

Height Datum (AHD) and be directly tied in to the local published

survey control network. Ellipsoid heights must be reduced to AHD

heights using AUSGeoid09 model.

Map Projection All ortho-rectified imagery must be supplied in terms of the Map Grid of

Australia (MGA) coordinate system.

Data Tiling All Primary data sets should be supplied in predefined tiles specified in

Table 9-1 (tile layout to be based on the MGA coordinate system).

Special Considerations E&IG will provide details of any special considerations applicable to the

project. For example: All coastal data should be acquired at low tide (+/-

2hrs) on any day.

Digital Elevation

Model

The digital elevation data used in the ortho-rectification process should

be of sufficient accuracy to enable to the resulting orthophoto to meet

the accuracy specifications detailed in Section 3.1

File Format 24 bit GeoTIFF and compressed ECW



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 9

Aer

ial

Photo

gra

phy

9.7 Quality Assurance Documentation

9.7.1 Prior to commencement of the aerial photography capture, a quality assurance plan

shall be submitted to E&IG.

9.7.2 It is expected that the documentation will provide detailed information on systems to

be used in the survey, operational information to be captured during the survey (e.g.

mission date, time, flight altitude, forward and side overlap), maps of survey coverage

and boundary overlaps, flight plans and any other pertinent survey information.

Table 9-3 Orthophoto Quality Assurance Plan

QA Deliverables Description

Quality Assurance

Plan

The Contractor shall prepare and submit a Quality Assurance Plan.

The plan must address the organisation and management of the project,

work procedures, environmental considerations, safety and risk control

and test procedures. The Quality Assurance Plan must detail the

procedures to be used to verify that the deliverables meet the required

specification. Approval to commence the aerial survey is contingent on

E&IG’s acceptance of the Quality Assurance Plan.

Pre-Survey Quality

Assurance

Deliverables

Proposed aerial photography flight plan

9.8 Specific Metadata Requirements

9.8.1 A number of additional metadata requirements shall be recorded for all aerial

photography. These requirements are listed in Table 9-4 with the name of the

metadata element in which the information shall be recorded. These elements should

be recorded in the metadata ‘Lineage’ element.

Table 9-4 Aerial Photography Specific Metadata Requirements

Metadata Element

Acquisition Start Date

Acquisition End Date

Sensor type

Focal Length

Flying Height (AGL)

INS/IMU Used

Number of Runs

Number of Frames/Swathes

Output Pixel Size

Description of Aerotriangulation Process Used and Residual Results

Description of Ortho-rectification Process Used

Spatial Accuracy – Horizontal

Spatial Accuracy – Vertical

Limitations of the Data

Spatial Data Management Plan Section 10 Satellite Imagery


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y








Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y

10 SATELLITE IMAGERY


10.1.1 Satellite imagery is collected from sensors mounted on orbiting satellites. The data

collected by the satellites is transmitted to ground stations for processing. Satellite

images often visually resemble an aerial photograph, but the image stores the amount

of electro-magnetic radiation reflected and/or emitted by the Earth's surface. This

information is used to perform data analysis.

10.1.2 E&IG uses satellite imagery in a wide range of analysis including: mapping and

monitoring vegetation; estate planning; erosion or disturbance mapping; and change

detection.

10.1.3 This specification provides guidance to E&IG staff on the acquisition of satellite

imagery.


been issued to undertake the acquisition of satellite imagery.

10.2 Background Information

10.2.1 The most commonly used commercially available satellite imagery for land

management and monitoring include:

ALOS

Aster

Digital Globe

Earth Resource Observation Satellites (EROS)

EO-1

GeoEye

IKONOS

Landsat TM and MSS (pre 1990)

MODIS

NOAA

Rapid Eye

RESOURCESAT-1 (IRS-P6)

SPOT

10.2.2 The selection of an imagery product is dependent on the requirements of the

Statement of Work (SOW). A variety of these products are used within E&IG.

10.2.3 Spectral Resolution

10.2.3.1 Spectral resolution relates to the number and width of spectral wavelength

bands collected by satellite sensors. Different bands are useful for

distinguishing different land cover types. Spectral resolution requirements

shall be carefully considered when designing a satellite image analysis /

remote sensing project.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y

10.2.3.2 The following satellite imagery is available:

Multispectral Images – are suitable for image analysis and remote sensing

data analysis. Multispectral imagery can include data bands in the visible, near

infrared and thermal infrared ranges with the pixel values representing a

reflectance measure within each wavelength band of the sensor.

Three Band or RGB Images – are enhanced satellite images that have been

contrast stretched, colour balanced and/or mosaiced so that they are suitable for

use as a background image in CAD or GIS software. This data is suitable for

image feature classification to extract extents of the manmade features such as

buildings, roads, dams or even general extent of vegetation cover (although it is

not recommended for land cover/land use classifications). This type of imagery

is not recommended for remote sensing image analysis as the pixel values are

modified and do not represent reflectance measures.

Single Band Images (Panchromatic) – These images often have high spatial

resolution and can be used for image feature extraction. These images have

limited applications on their own for remote sensing spectral analysis and should

not be used for such purposes.

Pan-Sharpened Images – a merged product derived from both panchromatic

and multispectral imagery, often from the same sensor. This produces high

resolution colour (natural and/or false colour) images similar to the above and

can be used for image feature extraction. These data should not be used as the

basis of image analysis processing as the pixel values are modified and do not

represent reflectance measures.

10.2.4 Spatial Resolution

10.2.4.1 Spatial resolution is the area on the Earth’s surface that is represented by an

imagery pixel; spatial resolution affects the scale of mapping that can be

obtained from imagery. Satellite imagery is available in a range of spatial

resolutions, from 0.6m panchromatic imagery from Digital Globe to 30m

multispectral imagery from Landsat TM.

Example: Satellite imagery with a resolution of 25m is suitable for mapping

at 1:50,000 or smaller.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y

10.3 Deliverables

10.3.1 The digital imagery shall be delivered as specified in the Scope of Works

10.3.2 A metadata record shall be produced for each data file.


The specification details any additional requirements in addition to those detailed in the

Section 2 Data Specification.

10.4.1 Data Format

10.4.1.1 Data shall be provided in Encapsulated Compressed Wavelet (.ecw) format

with an associated header file (.ers) OR in georeferenced tiff format with

associated world file.

10.4.2 File Names

10.4.2.1 To provide consistency and facilitate data discovery the following filename

format shall be adhered to:

Format: [Short Property Name]_[Other relevant information]_[Satellite

Imagery Sensor]_[Data of Capture in YYYYMMDD format]

Example: GardenIsland_NorthernSection_LandsatTM_20070604

CultanaTA_DigitalGlobe_20070430

10.4.3 Specific Metadata Requirements

10.4.3.1 A number of additional metadata requirements shall be recorded for all

satellite imagery. These requirements are listed in Table 10-1 with the name

of the metadata element in which the information shall be recorded.



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y

Table 10-1 Satellite Imagery Specific Metadata Requirements

Requirements E&IG Metadata Element

Number of rows in imagery Data Quality Information > Lineage

Number of columns in imagery Data Quality Information > Lineage

Cell (pixel) size: these must be square Resource Identification > Resolution >

Sample Distance

Sensor- platform, including version number

(eg. SPOT5, LANDSAT TM7)

Data Quality Information > Lineage

Date of capture Extent Information > Temporal Extent

Time of capture Extent Information > Temporal Extent

NADIR angle: angle of sensor Data Quality Information > Lineage

Sun angle: sun angle at time of image

capture


Spectral bands: number and wavelengths Data Quality Information > Lineage

Sensor resolution: may differ from image

cell size due to resampling


Image processing: detailed description of

image processing undertaken including

details on georeferencing, orthorectification

(RMS errors, source data); resampling

methods



10.5.1 NADIR Angle

10.5.1.1 NADIR angles shall be minimised and should be between 0 and 15 degrees.

The NADIR angle is the pointing angle of the sensor at the time of capture

relative to the area of land being sensed. A number of the satellites are

programmable and can scan the earth at varying angles to increase the

frequency of image capture. However, this can result in high NADIR angles

and significant skewing of the imagery which can be detrimental to the

product quality when mapping land cover.

10.5.2 Cloud

10.5.2.1 Cloud cover shall be minimised and where possible products with 0%-10%

cloud cover should be obtained. Satellite imagery is affected by cloud, haze

and smoke (the exception being radar imagery) as well as the shadows

produced, therefore minimising cloud present in the imagery is important.

Cloudy or hazy conditions can affect the diffuse light penetration and

reflectance (and hence the overall image quality) even if cloud or shadow is

not present within the specific area of interest.

10.5.3 Sensor and Pre-Supply Processing Artefacts

10.5.3.1 Banding, and line or pixel drop outs relating to a mal-functioning sensor

and / or satellite communication can affect usability of imagery. Images with



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

0 S

atel

lite

Im

ager

y

artefacts shall be rejected and must be resupplied with the capture of new or

replacement imagery.

10.5.4 Georeferencing

10.5.4.1 Satellite imagery shall be orthorectified, particularly in areas of high relief.

This shall be undertaken using the best available Digital Terrain Model (DTM)

and ground control data. If this is not being undertaken by the satellite image

provider then an ‘ortho-ready’ product type or unprocessed imagery should be

specified. Satellite image providers pre-process imagery using standard

models, however, the accuracies of these models and the nature of the terrain

in the area of interest should be considered before selecting this option. Where

orthorectification is specified a Route Mean Square (RMS) error of less than

one pixel is required.

10.5.4.2 Georeferencing using ground control coordinate locations is an alternative

to orthorectification. Georeferencing in this manner shall only be undertaken

following consultation with the commissioning E&IG Project Manager and

after an acceptable accuracy is agreed. A Route Mean Square (RMS) error of

less than one pixel is preferred.

10.5.4.3 For change detection, all images shall be co-registered to within one pixel.

10.5.5 Image Compression

10.5.5.1 Owing to the large size of image files (including aerial photography); image

compression is very useful for usability within CAD and GIS systems.

Compressed imagery shall not be used for image analysis and shall not be used

as an input to such processes. Where compressed imagery is requested or

supplied, imagery should also be supplied in an uncompressed ‘lossless’

format.

Spatial Data Management Plan Section 11 Master Planning Datasets


Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

1 M

aste

r P

lannin

g D

atas

ets








Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

1 M

aste

r P

lannin

g D

atas

ets

11 MASTER PLANNING DATASETS


11.1.1 The specification covers the requirements for the production of Master Planning

datasets and mapping outputs. Defence Master Planning is the process by which real

estate is reserved to allow for the optimal long term siting of activities on an

establishment. Master Planning outputs are also used in planning for engineering

infrastructure systems to support existing and emerging Defence capabilities within

regional and environmental constraints. Master planning is a significant element of

Defence capability and estate management.

11.1.2 A master plan is based on a 20-30 year time horizon and permits development of an

establishment to effectively achieve its functional role as identified by Government

policy, Defence capability requirements, and force disposition decisions. Appropriate

areas of serviced land are provided to manage the strategic development of competing

land uses, and thus to ensure ADF capabilities are sustained in a secure operational

environment. Master plans for significant bases are commissioned by the Estate

Planning Branch with plans for other bases being commissioned by regional offices.

11.1.3 Estate Planning Branch use the data to plan the estate; including new buildings,

facilities, capabilities and property disposal.

11.1.4 This specification will be used when a project is initiated by Estate Planning Branch

to support the planning cycle on a particular Defence property.

11.1.5 The Master Planning Datasets store the position of Master Planning Boundaries and is

used as part of the Master Planning process. Master Planning requires three types of

Datasets, these are:

Zone Plans

11.1.5.1 These plans define the spatial reservation of land for prescribed groups of

compatible uses and activities. Compilation of Zone Plans can encompass

Existing and Proposed Zones.

11.1.5.2 Defence has derived a standard set of zones for use in all future Zone Plans:

Operational Zone

Operational Support Zone

Base Support Zone

Domestic Zone

Open Space Zone

Future Development Zone

Open Training Zone

11.1.5.3 Additional zones shall not be added, unless specified by the Estate Planning

Branch.

Precinct Plans



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

1 M

aste

r P

lannin

g D

atas

ets

11.1.5.4 Precincts are derived from issues analysis. Examples of precincts which

may be shown are:

Security Levels (High / Medium / Low)

Heritage

Safety Constrained (Arc/Buffer, etc.)

Environmental Conservation, Offset

Non-Defence Use

Unit or Regimental

Special Projects

Constraints Mapping

11.1.5.5 Constraint maps convey the spatial extent of the following constraints:

DAA – Defence Aviation Areas

The regulations are concerned with providing height restrictions on

man-made structures and vegetation around military airfields.

ANEF – The Australian Noise Exposure Forecast (ANEF) system

ANEF is a scientifically-based computational procedure for determining

aircraft noise exposure levels around airfields. The ANEF maps display

the aerodrome and the surrounding localities, and the noise exposure

contours of ANEF, (the higher the ANEF value, the greater the noise

exposure).

Explosive Ordnance Safety Templates

The criteria defining distances from explosive ordnance and storage

facilities, which controls land uses that may not be desirable or

compatible with the storage of explosive materials.

Extraneous Lighting (DOD) and (CASA) regulations

The criteria defining distances from runways, where the amount of

upward light emitted in specific areas needs to be controlled.

Bird Strikes

The criteria regulating distances away from airfields within which

developments attracting wildlife (birds and bats) need to be controlled.

11.2 Deliverables

11.2.1 A Dataset shall be produced for each plan type.

11.2.2 A Metadata record shall be produced for each Dataset.


11.3.1 A file template containing the data model and a file containing sample data is

available on the Defence Estate Quality Management System (DEQMS) at the

following location:



Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

1 M

aste

r P

lannin

g D

atas

ets



The specification details any additional requirements in addition to those detailed in the


11.4.1 Data Format

11.4.1.1 Digital data can be collected in either GIS or AutoCAD format compatible

with the Section 2 Data Specification. (NOTE – GIS is preferred)

11.4.1.2 Appendix J contains detailed specifications for the provision of AutoCAD

data.

11.4.2 File Names

11.4.2.1 The following filename format shall be adhered to:

Format: [GEMS Property Name]_[Mapping Type]_[Year]_[GEMS

Property EBI]_[Existing or Proposed]

Where:

Mapping Type: Zone / Precinct / DAA / ANEF

Year: Year of map production

Existing of Proposed: Whether the plan is existing (E) or proposed (P)

Example: Amberley_RAAF_Base_Zone_2008_0861_E


11.4.3.1 The main plan dataset shall be in a parent directory with referenced files in

the same directory or at a lower level.


Spatial Data Management Plan Section 12 Contaminated Sites Data


Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata




GEMS Geo-enablement Planned Content GEMS Geo-enabled



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

12 CONTAMINATED SITES DATA


12.1.1 The specification defines the capture of data relating to known or potential

contaminated sites on Defence properties. The purpose of this data is to inform

Defence employees and contractors of contamination issues that may impact base

planning and infrastructure development at the site.

12.1.2 Contaminated Sites data assists the Directorate of Contamination Assessment,

Remediation and Management (DCARM) in the strategic management and tracking

of known or potential contamination issues. While DCARM runs investigation and

remediation programs, including the Regional Contamination Investigation Program

(RCIP), other investigation, remediation and management programs are undertaken by

other Directorates in E&IG.

12.1.3 Contaminated Sites Data shall be collected according to this specification to allow

consistency in management and reporting.

12.1.4 All parties undertaking contamination investigations, remediation, monitoring and

management projects and programs should collect spatial data as part of this work.

Spatial data visually illustrate the outcomes of the project and assist in the improved

management of the contaminated sites. Datasets of contamination have been collated

to produce a “single point of reference” for interrogation of information to identify

whether contamination will impact on planning, development, delivery or evaluation

of an E&IG activity. The data is a valuable management tool for program planning

across the Defence Estate and inform the decontamination provisions liability

assessment.

12.1.5 This specification covers the capture and update of Defence Contaminated Site data

that is collected by any project or program undertaking contamination investigations,

monitoring and/or remediation on the Defence Estate. The Contamination datasets

outline the spatial extent of the contamination. All attribute data in the Contamination

datasets is stored in the GEMS Contamination Module.

12.1.6 The Contaminated Sites Datasets that are included within this specification are as

described in Table 12-1: Contaminated Datasets which also shows how they align

with Environmental Spatial Data types described in Section 13.3 (Environmental

Data).

Table 12-1: Contaminated Datasets

Dataset Description Type of

Environmental

Spatial Data

Contaminated

Sites

This dataset provides detailed information on

areas of known and potential contamination

within Defence properties. The dataset

provides the geometries for GEMS

Environmental Factor Records (EFR).

These data are referred to in Appendix K as

Environmental Factor Spatial Data.

Environmental

Factor Spatial Data



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

Contaminated

Sites Sampling

Locations

This dataset details the location of soil

sampling sites, groundwater sampling sites

and sediment sampling sites.

These data may be used in the process of

determining the presence of contamination

and hence will lead to the creation of one or

more CSR EFRs, but are not themselves

EFRs.

These data are referred to in Appendix K as

Environmental Asset and Survey Spatial Data

Environmental Asset

and Survey Spatial

Data

12.2 GEMS: Spatial Data Update and Creation

12.2.1 As GEMS manages the non-spatial elements of the Defence Contaminated Sites

Register (CSR) it is also the source of all CSR EFR IDs. These are the unique

identifier for each contaminated site documented in the CSR.

12.2.2 Data Update: when a project / activity is updating CSR spatial data any CSR Spatial

data issued by Defence will contain an EFR ID for each site. These must not be

altered in any way.

12.2.3 Data Creation: when a project / activity needs to create new CSR sites, new EFR IDs

must be requested from the CSR Administrator via the NCRP mailbox

([email protected]). These EFR IDs must then be applied to the spatial data

associated with the new site(s).

12.2.4 Function Code: Care must be taken to use the correct Function Code value against

each Contaminated Site polygon appropriate to Update or Creation transactions as per

Table 12-2.

Table 12-2: Function Codes

Transaction Type Allowable Function Code Values

Creation C – Create

Update U – Update

V – Void (use this to delete)

A – Archive

12.3 Property Contaminated Site Map Requirements



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

12.3.1 A map shall be provided at the Property level showing all current Contaminated sites

on the property. The purpose of the map is to support operation and maintenance of

the property as well as planning and compliance activities. The requirements for

these maps are outlined in Table 12-3: Property Contaminated Sites Map Presentation

Guidelines and an example is provided at Figure 12-1: Example Property

Contaminated Sites map.

Table 12-3: Property Contaminated Sites Map Presentation Guidelines

Map Element Guideline

All map elements should be located to avoid obscuring Contaminated Sites and key items of

detail relevant to Contaminated sites on the property.

A title strip along the bottom of the map will accommodate: Title, Legend, Scale bar, Disclaimer,

logo, suppliers reference etc. If sufficient space is not available in the title strip an additional

floating frame may be used.

Map Window Minimum Map content:

1. CSR Data: Thematically mapped polygons representing

contaminated sites, labelled with EFR_ID.

2. Background: Either imagery or topographic map

background as best suited to the property and map scale.

The date of the background map, particularly imagery, will

be shown in the title strip. Preference is top right corner of

the title strip.

3. Back ground labels: Key roads and topographic features

such as water bodies will be labelled. These will be

minimal in number and will not obscure Contaminated

Sites or labels. The number of labels will be sufficient for a

reader to reliably understand the location of Contaminated

Sites on a property,

4. Building/Structure EBI: In order to assist users, interpret

the impact of contamination, buildings and relevant

structures will be shown and labelled with their EBI. The

preferred source of these data is the properties Master Site

Plan (Section 3).

5. A Contaminated Site that has been archived as a

consequence of an investigation or is already denoted for

archiving on GEMS, should not be included on the map.

6. Notes map be used to clarify the status or extent of

Contaminated Sites. The preferred location of notes as at

the bottom left of the map window.

Contaminated Sites

Symbology Contaminated Sites will be thematically mapped by CRAT/ ERAT

Risk Ranking as shown in the GEMS CSR module for each site as

follows:

Risk Description Colour (RGB Values)

Very High R: 255, G: 0, B:0

High R: 255, G: 170, B:0

Medium R: 255, G: 235, B:0

Low R: 0, G: 255, B:0



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata


Defence Property

Boundary Symbology The Defence property boundary will be shown as follows:

Line Style Dual Solid Stroke Layer

Base Line Colour R: 255, G: 255, B:255

Base Line Weight 2.5

Dashed Line Pattern 4 2 4 2 1 2

Dashed Line Colour R: 255, G: 127, B:127

Dash Line Weight 2.5

Map Size and Scale 1. A3 size for all properties.

2. The maps shall be scaled such that the entire property is

contained within the map frame.

3. For large properties or where CSR information is crowded

additional map pages (enlargements) will be created

showing such areas at larger scales so that CSR data,

labelling and background mapping is clearly readable;

4. Where enlargements are employed (as above) a key line

will be shown on the main map indicating the extent of the

enlargement. These key lines shall be labelled with their

Map number. E.g. “Refer Map 2”

5. The Main Map will be Map 1.

6. Where enlargements are employed, they will be numbered

as Map number of the total map count. E.g. Map 2 of 3.

Title The map title shall follow the following schema:

[PropertyEBI] – [Property Name], [State/Territory Abbreviation]

Contaminated Sites.

A subscript will follow stating which Defence entity has issued the

map.

e.g. “Map issued by DCARM”

Legend The map legend shall show symbols as per Contaminated Sites and

Defence Property Boundary Symbology as above.

North point Where ever possible the map must be oriented so that north is up

the page. The preferred position of the north point is at the top left

of the Window. It may be pre-positioned if the preferred location

detracts from the information content of the map. E.g. it covers a

contaminated site.

Creation and Revision

dates

1. The date of the map’s creation must be shown.

2. Revision number must be shown.

3. The date of the map revision must be shown.

PDF delivery (fonts) Care must be taken to ensure all fonts are embedded to ensure maps

render accurately on end users computers.



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

Figure 12-1: Example Property Contaminated Sites map



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

12.4 Data Deliverable – Map Template

12.4.1 A file template containing all file settings, features, symbology, attributes and layer

structures, is available on the Defence Estate Quality Management System (DEQMS)

at the following location.


A file containing sample data is also available.


12.5.1 The specification details any additional requirements in addition to those detailed in

the Section 2 General Data Specification.

12.5.2 The deliverables required for a given scope of work will be defined by the work

scope. These will be one or more of the following:

Contaminated Sites CSR EFR spatial data records – See Appendix K –

Environmental Data Model

Contaminated Sites Sampling Locations records – See Appendix K –

Environmental Data Model

12.5.3 All datasets created or updated in association with these specific datasets shall form

part of the project deliverables. Datasets may include groundwater mapping or

contours, soil salinity or associated outputs.

12.5.4 An SDMP compliant metadata record shall be produced for each dataset.

12.5.5 Property Contaminated Sites Map must be provided as self-contained soft copy (e.g.

PDF) and in editable form (NOTE – ESRI ArcGIS.mxd map documents are

preferred). Where a map product unavoidably includes licensed reference data (e.g.

background imagery), a clear description of the data Defence will need to re-source to

allow the map to be updated must accompany the map.

12.5.6 Data Format

12.5.6.1 Data shall be provided in an ESRI Shapefile.

12.5.7 File Names

12.5.7.1 The contaminated sites datasets shall be named as follows:

Contaminated Sites

Refer to Appendix K – Environmental Data Model.

Sampling Locations

Refer to Appendix K – Environmental Data Model.

Property Contaminated Sites map

Files shall be names as per the following schema:

CSR_[GEMS Property EBI][GEMS Property short




Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

2 C

onta

min

ated

Sit

es D

ata

name]_YYYYMMDD

Example: CSR_1426Laverton_20200207.pdf

12.5.8 Spatial Accuracy

12.5.8.1 Boundaries for Contaminated Sites will collected by reference to the best

available spatial data relevant to the contamination issue or by GNSS

techniques to an accuracy of ± 2m or better.

12.5.8.2 Sampling locations shall be captured using a GNSS technique to an

accuracy of ±2m.

Spatial Data Management Plan Section 13 Environmental Data


Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata








Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

13 ENVIRONMENTAL DATA


13.1.1 The specification covers data collected for environmental management purposes. The

specification provides guidance on the minimum data requirements for Environmental

Data.

13.2 Background Information

13.2.1 Environmental data shall be collected in formats suitable for use with a Geographical

Information System (GIS) to allow Data Users to collect data attributes against spatial

features and to undertake spatial analysis on the data.

13.2.2 The data model details a General Context to each dataset and the following

information:

File names;

Dataset description;

Feature types; and

Specific data collection or attribute requirements.

13.2.3 The Data Model provides an Attribute Table detailing minimum data collection

specifications for core environmental datasets. Additional attributes shall be captured

as required. The data model details the following attribute information:

Field names;

Description of the field;

Field data types and size;

Units; and/or example values.

13.3 Types of Environmental Spatial Data

13.3.1 Environmental Factor Spatial Data: These data are required to support enablement

of Environmental Factor Records (EFR) in GEMS. That is, they provide the

geometries for GEMS EFR records. The following EFR types are included:

Contaminated Site Register (CSR), Heritage, Bushfire and Soils.

13.3.2 Environmental Asset and Survey Spatial Data: These data are collected or

complied for Defence Estate Management purposes. They include data that has been

created by Defence projects for the purposes of generating an Environmental Factor

Spatial Data set but are not EFRs. Contaminated sites sampling locations are an

example. These data may be used in the process of determining the presence of

contamination and hence will lead to the creation of one or more CSR EFRs, but are

not themselves EFRs.

13.3.2.1 These data include reference data, sourced from a third-party data provider

for the purposes of creating Environmental Factor Spatial Data and for

providing context to mapping products.

13.3.2.2 Data specifically created for Defence purposes for which there is an

accepted State/Territory standard shall be created according to that standard.

Creators of such data must be aware that, where Defence believes the created



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

data will modify/contribute to State/Territory data, Defence will contribute

these data to the relevant States/Territories.

13.3.2.3 Where spatially enabled environmental data is sourced from State, Territory

and other Commonwealth agencies these must adhere to nationally accepted

standards for the environmental data type represented. Such data will extend

but not duplicate the Defence requirement set out in the SDMP.

13.3.3 Environmental Monitoringand Transactional Spatial Data: These data include

monitoring and transactional data involving dynamic/time dependant spatial data

relating to management of the Defence Estate. Examples include:

Footprints of weed treatments,

Raster data modelling weed density that can be used to plan treatments, and

Fire history raster data modelling time since last fire that used to plan burn

programs against reference fire return interval raster



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

Envi

ron

men

tal M

onit

orin

g

& T

ran

sact

iona

l Sp

atia

l Dat

aEn

viro

nm

enta

l Fac

tor

Spat

ial D

ata

Envi

ron

men

tal A

sset

&

Surv

ey S

pati

al D

ata

Sampling locations

State/Territory contamination

Gully erosion mapping

Soil EFRpolygon

State/Territory soil mapping

Heritage EFR polygon

Historical ruins

State/Territory heritage community

Assessment / Decision Making Processes

Contamination modelling

...

Weed density

raster

2016

2018

Erosion monitoring

Burn raster

2019

2020

Figure 13-1 Environmental Spatial Data Types

13.4 Data Deliverable – Templates

13.4.1 A set of file templates containing the data model requirements are available on the

Defence Estate Quality Management System (DEQMS) at the following location



13.5.1 The specification details any additional requirements in addition to those detailed in

the Section 2 General Data Specification.

13.5.2 Data Format




Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

13.5.2.1 Data shall be provided in a GIS data format, Shapefile format is the

preferred format.

13.5.3 File Names

13.5.3.1 File names shall be as specified in Appendix K or as detailed in the

Section 2 General Data Specifications.

13.5.4 Data Attributes

13.5.4.1 Data attributes shall be as specified in Appendix K or as detailed in the

Section 2 General Data Specifications.

13.5.5 Metadata

13.5.5.1 A new or updated metadata file shall be provided with each data delivery

file as detailed in Appendix D.


13.6.1 Specific data requirements are specified in Appendix K.

13.7 Map Requirements

13.7.1 Bushfire Operations Map Presentation

13.7.1.1 The purpose of this map is to provide a ready reference to external bushfire

responders attending the site. Content must therefore be UNCLASSIFIED.

Following data labelling and content unclassified Training Area (TA) special

maps will provide a useful benchmark of appropriate content for reference

layers. Specific requirements are listed in Table 13-1: Bushfire Operations

Map Presentation Guidelines.

13.7.1.2 Map must be provided as self-contained soft copy (e.g. PDF) and in editable

form (NOTE – ESRI ArcGIS.mxd map documents are preferred). Where a

map product unavoidably includes licensed reference data (e.g. background

imagery), a clear description of the data Defence will need to re-source to


13.7.1.3 Any hard or soft copy mapping produced for Bushfire mapping shall adopt

the Emergency Management Spatial Information Network Australia

(EMSINA) standards for map symbology where appropriate to the product.

Refer www.emsina.org.

13.7.1.4 Relevant matters represented on a map must be drawn from the EFR spatial

data.

13.7.1.5 Bush Fire Operations map files shall be named as per the following schema:

[Establishment]_Bushfire_Ops_Map_Rev[Number]_YYYYMMDD.pdf / .mxd

http://www.emsina.org/



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

Example: MTA_Bushfire_Ops_Map_Rev0_20201022.pdf

Table 13-1: Bushfire Operations Map Presentation Guidelines


All map elements should be located to avoid obscuring any part of the property. Depending on

the shape of the property, any of the required elements can be placed as floating frames within

the main map frame. Scale bars, north arrow and reference maps for vegetation and UXO are

most suitable for such placement.

A consolidated strip along the bottom of the map will generally accommodate most elements,

and if sufficient space is not available in a bottom strip and floating frames, adopt a side strip on

the left hand side of the map.

Property map (main

map frame)

Minimum Map content:

1. Background: Either satellite imagery or topographic map

background as best suited to the property.

2. General reference layers: Defence boundary, general

roads tracks and trails, buildings, Defence facilities and

ranges, staging points, safe zones, entry/exit points,

emergency exit routes, neighbouring residential,

commercial and environmental assets, gates (locked and

unlocked) and access points, turnaround points, secure

areas, restricted areas, explosive storage risk areas, other

known risks, any significant landscape or built features

(creeks, ridges, powerlines)

3. Reference layers derived from BMP EFR data layers:

Strategic fire trail network represented to local standard

(e.g. Cat 1, Cat 7 etc), firebreaks including trafficability

(where relevant), APZs, SFAZ, water points, fire sensitive

assets (Natural, Cultural, Built), refuges of last resort.

4. Any area of Extreme explosive hazard in UXO mapping

must be labelled as “Extreme UXO risk- no firefighting

operations”.

Unexploded Ordnance

map frame

A small reference frame showing current UXO mapping for entire

property. The frame shall include:

1. A title “Unexploded Ordnance Risk”

2. A statement “Refer to guidelines for Firefighting in UXO

Affected Areas from Defence Unexploded Ordnance

Management Manual for likely restrictions imposed by

UXO”.

3. A legend showing each UXO risk category.

4. No scale, north arrow or grid are required.

Vegetation Classes map

frame

A small reference frame or single A3 sheet map showing NVIS

major vegetation groups. The frame shall include:

1. A title “Vegetation groups”

2. A legend showing each included group.

3. No scale, north arrow or grid are required



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata


Map Size and Scale 1. Map scale shall be such that the map is readable.

2. The preferred scale range is 1:5,000 – 1:50,000, with a

maximum of 1:100,000.

3. Minimum A3 size for smaller properties.

4. Maximum A1 size for larger properties.

5. Multiple A3 maps are more appropriate for very large

properties and should be provided in a map book (see

below).

6. Additionally, for very large properties where large areas

will not be subject to external fire response, A3 maps may

be selectively provided of operational areas showing

infrastructure and roading. These must be accompanied by

a key map showing areas covered by the operational maps.

The key map shall show areas not covered by operations

maps shaded in grey.

7. Where map book treatment is required a large format (e.g.

A1) whole of property map shall be provided. Appropriate

cartographic license will be applied to ensure the map is

readable and also conveys key BMP, UXO and vegetation

information.

A3 Map Books Where A3 map books are provided the map content shall be as per

Property map (main map frame) requirement. However,

individual frontal sheets shall be used for:

1. Legends;

2. Key map of the property showing the location of each

numbered A3 map page;

3. Reference maps; and

4. Key legend elements relevant to an unusual/specialist

feature on a particular page (e.g. Extreme UXO risk areas,

restricted areas) should also be shown either as annotation

or a simple legend.


[Establishment Name] Bushfire Operations Map

Legend The map legend shall show symbols as per Emergency

Management Spatial Information Network Australia (EMSINA)

standards for map symbology where appropriate and will include

only these symbols included in the map.


the page.

Grid 1. The main map frame should have a grid overlay relevant to

the map scale.

2. For 1:2,5000 – 1:100000 maps a 1x1 kilometre grid should

be used.

3. The map projection and datum will be quoted in the map

title area. Refer Section 2 for projection and datum

requirements.


dates

1. The date of the map’s creation must be shown.

2. Revision number must be shown.


Softcopy map delivery Where maps are delivered in softcopy form (adobe PDF format)

care must be taken to ensure all fonts are embedded to ensure maps




Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

13.7.2 Land Capability Mapping

13.7.2.1 Map must be provided as self-contained soft copy (e.g. PDF) and in editable

form (NOTE – ESRI ArcGIS .mxd map documents are preferred). Where a

map product unavoidably includes licensed reference data (e.g. background

imagery), a clear description of the data Defence will need to re-source to


13.7.2.2 The purpose of this map is to provide a ready reference on the capacity of a

Defence property to support different activity classes based on topography,

soil, vegetation, climate and hydrology. Specific requirements are listed in

Table 13-2: Land Capability Map Presentation Guidelines.

13.7.2.3 Land Capability map files shall be named as per the following schema:

[Establishment]_Land_Cap_Map_Rev[Number]_YYYYMMDD.pdf / .mxd

Example : MTA_Land_Cap_Map_Rev0_20201022.pdf

Table 13-2: Land Capability Map Presentation Guidelines


All map elements should be located to avoid obscuring any part of the property. Depending on

the shape of the property, any of the required elements can be placed as floating frames within

the main map frame. Scale bars, north arrow and reference maps are most suitable for such

placement. Additional reference maps could include vegetation and UXO.

A consolidated strip along the bottom of the map will generally accommodate most elements,

and if sufficient space is not available in a bottom strip and floating frames, adopt a side strip on

the left-hand side of the map.

Property map (main

map frame)

Minimum Map content:

1. Minimum Topographic Information: Displayed with

standard symbology:

a) Contours with 10m ASL contours,

b) Water bodies and water courses,

c) Shore line,

d) Areas subject to inundation/swamps,

e) Spot height for key topographic features,

f) Key infrastructure (e.g. roads, railways, power lines

etc.),

g) Assets and urban areas,

h) Defence boundary, and

i) Defence facilities and ranges.

2. Capability Mapping layers:

a) Cross country trafficability as black and white hatched

polygons.

b) Sensitive areas; green hatching for classes of



Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata


environmental sensitivity, red hatching for

physiographic constraints to movement.

c) Ground cover as different shades of green.

Unexploded Ordnance

map frame (optional)

A small reference frame showing current UXO mapping for entire

property. The frame shall include:

1. A title “Unexploded Ordnance Risk”

2. A statement “Refer to guidelines for Firefighting in UXO

Affected Areas from Defence Unexploded Ordnance

Management Manual for likely restrictions imposed by

UXO”.

3. A legend showing each UXO risk category (refer Appendix

M).

4. No scale, north arrow or grid are required.

Vegetation Classes map

frame (optional)

A small reference frame or single A3 sheet map showing NVIS

major vegetation groups. The frame shall include:

1. A title “Vegetation groups”

2. A legend showing each included group.

3. No scale, north arrow or grid are required

Map Size and Scale 1. Map scale should match the Defence Training Area special

map.


[Establishment Name] Land Capability Map

Legend The map legend shall show symbols and will include only these

features included in the map.

North Point A North Point shall be shown and wherever possible the map must

be oriented so that north is up the page.

Grid 1. The main map frame should have a grid overlay relevant to

the map scale.

2. For 1:25000 – 1:100000 maps a 1x1 kilometre grid should

be used.

3. The map projection and datum will be quoted in the map

title area. Refer Section 2 for projection and datum

requirements.


dates

1. The date of the maps creation must be shown.

2. The revision number






Version 5.0 100 26 June 2020

Spec

iali

sed

Dat

a S

pec

ific

atio

ns

Sec

tion 1

3 E

nvir

onm

enta

l D

ata

13.8 External Environmental Data

13.8.1 Where spatially enabled environmental data is sourced from State, Territory and other

Commonwealth agencies these must adhere to nationally accepted standards for the

environmental data type represented. Such data will extend but no duplicate the

Defence requirement set out in the SDMP.

Spatial Data Management Plan Section 14 Hazards Data

Version 5.0 101 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a







Version 5.0 102 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14 HAZARDS DATA


14.1.1 The specification defines the capture and presentation of data relating to known or

potential Hazards on Defence properties. The purpose of this data is to inform

Defence employees and contractors of hazards that may impact safe operation of the

site, base planning and infrastructure development at the site.

14.2 Schedule 11 Hazardous Chemicals Data and Maps (HAZCHEM)

14.2.1 Background

14.2.1.1 Work Health and Safety Regulations (Cth) 2011 (WHS Regs), Regulation

(Reg) 347 requires a person conducting a business or undertaking (PCBU) at a

workplace must, if the quantity of a Schedule 11 hazardous chemical or group

of Schedule 11 hazardous chemicals used, handled or stored at the workplace

exceeds the manifest quantity for the Schedule 11 hazardous chemical or

group of Schedule 11 hazardous chemicals to:

1. prepare a manifest of Schedule 11 hazardous chemicals, including site

plans (maps) prepared in accordance with Schedule 12 of the WHS

Regs; and

2. ensure that the Regulator (Comcare) is given written notice where

manifest quantities are used, handled or stored, at a workplace in

accordance with Reg 348.

14.2.1.2 In accordance with point (a) above this specification outlines the

requirements for spatial data representing areas within workplaces on the

Defence Estate where Schedule 11 hazardous chemicals are used, handled or

stored. The specification also outlines the requirements for the required site

maps showing these same areas in hard or soft copy form.

14.2.1.3 The audience for these maps includes Emergency Services, Comcare and all

Defence (including contractors) site personnel.

14.2.2 Map Requirements

14.2.2.1 WHS Regulations, Schedule 12, Clause 7 and Defence WHS Manual, Vol

3, Part 3A, Chapter 1, Procedure HC:03-15 Notification of Hazardous

Chemicals Manifest Quantities, Pipelines and Abandoned Tanks specifies the

minimum detail which must be shown on workplace site plans (maps):

1. Show the location of containers and other storage of hazardous

chemicals in bulk and provide their identification details (e.g. DGT 3);

2. Show the location of storage areas for packaged hazardous chemicals

and IBCs and provide their identification details (e.g. PS3);

3. Show the location where hazardous chemicals are manufactured or

generated and provide their identification details (eg MA 2);


Version 5.0 103 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

4. Show on the map areas which have been designated for chemicals that

are ‘in transit’ (eg ITA 1);

5. A legend describing what the map symbols represent;

6. Show the location of the main entrance (gate) to the Property (and other

points of entry) and clearly show the access route to the workplace from

the main entrance of the property;

7. Show on the map entry and exit points to/from the workplace;

8. Show on the site map any essential site services, including fire services

and isolation points for fuel and power;

9. Show on the site map all drainage systems;

10. Show on the site map where the manifest is located;

11. Show and provide a description of adjoining workplaces, occupancies or

sites (e.g. car repair shop and furniture factory);

12. Show on the site map the location of all other buildings, amenities,

fences, car parks and storage areas;

13. Include a north point symbol indicating the direction of true north;

14. Ensure the site name and address details are recorded on the site map

along with the date it was prepared / revised; and

15. Include a description of the activities carried out in adjoining sites or

premises.

Note: The completed workplace map (plan) must match the information

in HCM002 Notification Form and Manifest document.

14.2.2.2 Refer to Appendix M for the symbology requirements to be used for all

Defence Schedule 11 Hazardous Chemical site maps.

14.2.2.3 The Comcare approved map template must be used for all Defence

workplace site maps as shown in Figure 14-1: Example Workplace Site Map.

Refer 14.2.7 for available pre-prepared template.


Version 5.0 104 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

Figure 14-1: Example Workplace Site Map


Version 5.0 105 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.2.2.4 Workplace site maps will use the current Master Site Plans (Section 3) and

or current imagery as their base map. Layers selected from Master Site Plans

should be selected so as to show the general above ground configuration of the

site and any below ground infrastructure into which escaped material may

drain.

Refer to Appendix M for the recommended list of Master Site Plan layers to

be used in Workplace site maps.

14.2.2.5 Table 14-1 provides map presentation guidelines that must be adhered to.

Table 14-1: Schedule 11 Hazardous Chemicals Workplace Site Map Presentation

Guidelines


Title The map title shall include the Defence property number, property

name, State/Territory and the name of the workplace as per the

Defence Notification.

Locality map The locality map extent must be such that the Property entrance and

workplace are included.

Legend The map legend shall show symbols as per Appendix M and will

include only these features included in the map.

Scale 1. Map scale will be such that the map is readable. The preferred

scale range is 1:500 – 1:1250.

2. Where a single notification includes widely separated sites that

would lead to map features being unreadable, multiple map sheets

should be used.


the page.

Regional reference The reference number that identifies the workplace documented by

the Manifest. The reference number conforms to the following

schema:

PPPP-AAAA

Where PPPP is the Property EBI of the property.

AAAA is the GEMS Asset number of the tank, container, storage

area or compound that is used to store, handle or generate the

hazardous chemicals. Where no such feature is present or there are

multiple tanks, containers etc. the GEMS asset number of a building

or structure in close proximity may be used, if it is shown on the

map, as the Regional reference.

Comcare reference The workplace number assigned by Comcare must be shown in the

legend panel (if known)

Workplace address The legend panel shall include the address of the workplace, as per

the Defence Notification.

Tanks Tanks will be labelled with a DGT number, and detail sourced from

the Defence Notification including:

1. Volume (maximum capacity in Litres/Kilograms).

2. Contents (with the appropriate GHS or ADG code and

description).

3. Any local identification number or code.

4. The tanks Defence Asset number (GEMS).


Version 5.0 106 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

5. Where individual labelling of tanks is impractical tanks may be

labelled with the DGT number and cross referenced to a table

listing the above details, e.g. DGT 001.

Abandoned tanks Any tank that has not been formerly de-commissioned, whether in

use or not, must be shown. Those that are not in use may be shown

as Abandoned.

Below manifest quantities Where a workplace contains other quantities of Hazardous

Chemicals that are below manifest thresholds, which may be

relevant in the event of an incident, their presence may be noted and

labelled.

Site access A line or lines showing the access route from the Properties main

gate to the workplace exit and entry points may be substituted for a

written description of the access route.

Manifest The location of the Manifest must be shown in the body of the map.

A note must also be shown below the locality map describing the

location(s) of the Manifest.

Where it is not practical to hold the manifest at the workplace (i.e.

with the manifest quantity) the location where the Manifest is held

must be shown in the locality map and described in the note below

the locality map (e.g. Bulk LPG Bullet).

Assembly Area The assembly area(s) for the site must be shown. If inclusion

within the map would impact readability (reduction of the scale)

then a symbol(s) may be placed at the map margin with an arrow

pointing in the direction of the actual location with the name of that

location and the distance in metres.

Base map labelling The base map must include, where relevant:

1. Road names.

2. Building/Structure EBI (GEMS).

3. Building/Structure names.

4. Names/Descriptions of yards, compounds etc..

Hydrants, extinguishers,

First Aid, Spill Kits, Eye

Wash, Emergency

Showers.

1. These features must be shown in the immediate vicinity of the

workplace where outside buildings or structures.

2. These features may be shown when inside buildings only when

they would be accessible and relevant in the event of an incident.


dates

1. The date of the maps creation must be shown.





14.2.3 Review Procedure

14.2.3.1 Prior to finalisation workplace site maps must be provided to the relevant

contacts at the property for review and confirmation purposes. A checklist is

provided at Appendix M to guide and support this process.

14.2.4 Dependences

14.2.4.1 Workplace site maps are supporting documentation for Notifications made

by Defence to the Commonwealth WHS Regulator, Comcare. As such, the

details shown on workplace site maps must be sourced from and match the

details in the Notification and Manifest documents

14.2.5 Spatial Data Requirements


Version 5.0 107 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.2.5.1 Areas representing the locations where Schedule 11 Hazardous Chemicals

are stored, handled, manufactured and or generated will be captured as

polygons. The representation may be:

1. A polygon representing the individual container/tank the material is held

within; or

2. A polygon that represents an area (e.g. yard, compound etc) where

materials are held; or

3. A polygon that represents the extent of

containers/tanks/yards/compounds etc. when no base data representing

these individually is available.

14.2.5.2 The location of infrastructure and equipment used to respond to incidents

related to the subject Schedule 11 Hazardous Chemicals will be represented as

point features.

1. Only infrastructure and equipment that is not within the scope of Master

Site Plans (Section 3) are to be included in this dataset. Appendix M

provides a list of features that may be included in this dataset.

14.2.5.3 Spatial data will be captured in Shapefile format in accordance with the

requirements of Section 2 General Data Specification, except where specified

otherwise in this section.

14.2.5.4 Attribute information to be captured and stored with Polygon and Point

features is described at Appendix M

14.2.6 Deliverables

14.2.6.1 The following are the minimum expected deliverables where a workplace

site map is updated or a new one is created:

1. Workplace Site map(s), conforming to 14.2.2 in PDF format;

2. New and or updated HAZCHEM spatial data conforming to 14.2.5 in

shapefile format.

3. There shall be one polygon and one point HAZCHEM spatial dataset for

each Property;

4. New and or updated metadata record for each HAZCHEM spatial data

set; and

5. New and or updated map documents where ESRI ArcGIS is used to

prepare workplace site map(s). Refer 14.2.9.1.

14.2.7 Deliverable Templates

14.2.7.1 A file template containing the data model and a file containing sample

HAZCHEM data is available on the Defence Estate Quality management

System (DEQMS) at the following location:




Version 5.0 108 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.2.8 Deliverable Specification

14.2.8.1 This sub-section details any additional requirements to those detailed in


14.2.9 Data Format

14.2.9.1 Workplace site maps can be prepared in any application supporting data

formats compatible with the Section 2 Data Specification. (NOTE – ESRI

ArcGIS .mxd map documents are preferred)

14.2.9.2 Appendix M contains detailed specifications for the provision of workplace

site maps and HAZCHEM spatial data.

14.2.10 File Names

14.2.10.1 The following filename schema for workplace site maps shall be adhered to:

[Property EBI]-HAZCHEM Map-[Regional reference]

Refer Table 14-1 for definition of the Regional reference.

Example: 0089-HAZCHEM Map-B0116.pdf

14.2.10.2 The following filename schema for workplace HAZCHEM spatial data

shall be adhered to:

Defence_HAZCHEM_[Property EBI]

Example: Defence_HAZCHEM_0089.shp

14.2.10.3 The following filename schema for infrastructure and equipment used to

respond to incidents shall be adhered to:

Defence_HAZCHEM_PT_[Property EBI]

Example: Defence_HAZCHEM_PT_0089.shp

14.2.10.4 The following filename schema for workplace HAZCHEM map documents

prepared using ESRI ArcGIS shall be adhered to:

Workplace_[Regional reference]

The Regional reference will aligned with that chosen for the workplace site

maps. Refer Table 14-1 for definition of the Regional reference.

Example: Workplace_B0116.mxd

14.2.10.5 Where a HAZCHEM map document (e.g. .mxd files) reference other data,

the map document and referenced data may be packaged into compressed data

archive (.zip).


Version 5.0 109 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a


14.2.11.1 Workplace HAZCHEM spatial data are to be documented as GIS Data-

Vector.

14.2.11.2 Workplace HAZCHEM map documents (eg .mxd files) or compressed data

archive shall be included within the scope of the HAZCHEM spatial data

metadata.

14.2.12 References

14.2.12.1 The requirements for these data and maps are informed by the following:

14.2.12.2 Defence WHS Manual, Vol 3, Part 3A, Chapter 1, Procedure HC:03-15

Notification of Hazardous Chemicals Manifest Quantities, Pipelines and

Abandoned Tanks


(Reg) 347 and schedule 12, Clause 7.

14.3 Hazardous Areas Data

14.3.1 Background

14.3.1.1 In order to properly discharge the applicable safety duties under the WHS

Act, Defence needs to identify the safety hazards and risks arising from its

operations. Accordingly, it is required to identify all hazardous areas on the

Defence Estate

14.3.1.2 Hazardous areas are areas where a flammable atmosphere may be expected

to be present owing to the presence of flammable gases, vapours, liquids, or

combustible dusts, fibres or flyings may occur in dangerous quantities and

where explosives materials/substances are exposed to the atmosphere.

14.3.1.3 For further information on identification of hazardous areas refer also to the

WHS Code of Practice - Managing Risks of Hazardous Chemicals in the

Workplace - July 2012 - Appendix I - Fire and Explosion Risks


14.3.2.1 Areas delineating the location and extent of hazardous areas will be

represented as polygons. Each polygon will represent the individual

structure/room/cabinet/yard/etc each hazardous area is contained within. That

is there must be one polygon for each hazardous area.





Version 5.0 110 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.3.2.3 Attribute information to be captured and stored with each polygon is

described at Appendix M

14.3.3 Deliverables

14.3.3.1 The following are the minimum expected deliverables:

1. New and or updated Hazardous Areas spatial data

2. There shall be one Hazardous Areas spatial dataset for each Property;

and

3. New and or updated metadata record for each Hazardous Areas spatial

data set;


14.3.4.1 A file template containing the data model, and a file containing sample

Hazardous Areas spatial data is available on the Defence Estate Quality

management System (DEQMS) at the following location:



14.3.5.1 This sub-section details any additional requirements to those detailed in


14.3.5.2 File Names

14.3.5.3 The following filename schema for Workplace Hazardous Areas spatial

data shall be adhered to:

Defence_Hazardous_Areas_[Property EBI]

Example: Defence_Hazardous_Areas_0089.shp


14.3.6.1 Hazardous Areas spatial data are to be documented as GIS Data-Vector.

14.3.7 References

14.3.7.1 The requirements for these data are informed by the following:

14.3.7.2 WHS Code of Practice - Managing Risks of Hazardous Chemicals in the

Workplace - July 2012 - Appendix I - Fire and Explosion Risks


(Reg) 347.



Version 5.0 111 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.4 Unexploded Ordnance (UXO) Data

14.4.1 Background

14.4.1.1 The Department of Defence is required to maintain a comprehensive record

of sites confirmed as, or suspected of being contaminated by unexploded

ordnance (UXO).

14.4.1.2 A primary purpose of these records is for protection of members of the

public from the hazards associated with UXO, and to increase public

awareness of these hazards.

14.4.1.3 The records are made available to the general public, planning authorities,

utility companies, and industry in order to influence local land use planning

and development activities.

14.4.1.4 Defence owns and maintains spatial data delineating areas that have

potential for the presence of UXO in order to support the above requirements.

14.4.1.5 The spatial data covers land:

1. Occupied by the Commonwealth;

2. Divested by the Commonwealth of a legal interest in the land; and

3. Land the Commonwealth has never had a legal interest in.


14.4.2.1 Areas delineating the location and extent of areas that have potential for the

presence of UXO will be represented as polygons. Each polygon will

encompass a region determined to have an equal level of UXO potential.

There must be one polygon for each UXO area.






14.4.3 Deliverables


1. New and or updated UXO spatial data

2. There shall be one UXO spatial dataset for the entire geographic scope

of services; and

3. New and or updated metadata record for new or updated UXO spatial

data set;


Version 5.0 112 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a



UXO spatial data is available on the Defence Estate Quality Management


http://www.defence.gov.au/estatemanagement/support/Default.asp


14.4.5.1 This sub-section details any requirements in addition to those detailed in


14.4.5.2 File Names

14.4.5.3 Where a project is contributing new UXO spatial data the following

filename schema shall be adhered to:

UXO_[Project Number]

Example: UXO_SN0089.shp

14.4.5.4 Where a project is updating existing UXO spatial data the existing filename

will be preserved.


14.4.6.1 UXO spatial data are to be documented as GIS Data-Vector.

14.4.7 References

14.4.7.1 The requirements for these data are informed by the following:

Commonwealth Policy on the Management of Land Affected by

Unexploded Ordnance, 1 February 2018

14.5 Training Area Unexploded Ordnance (UXO) Hazard Data and Maps

14.5.1 Background

14.5.1.1 The Department of Defence is required to maintain a comprehensive record

of sites confirmed as, or suspected of being contaminated by unexploded

ordnance (UXO) on and around Defence Training Areas.

14.5.1.2 A primary purpose of these records is for protection of Defence personnel

and others (with authority to access a Defence Training Area) from the hazards

associated with UXO, and to increase Training Area user’s awareness of these

hazards.

http://www.defence.gov.au/estatemanagement/support/Default.asp


Version 5.0 113 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.5.1.3 The primary audience is Defence personnel, authorised Defence Contractors

and Emergency services.

14.5.1.4 Defences owns and maintains spatial data delineating areas that have

potential for the presence of UXO in order to support the above requirements.

14.5.1.5 The spatial data and maps cover the following types of land:

1. Occupied by the Commonwealth;

2. Land the Commonwealth has a legal interest (e.g. leased) in.

14.5.2 Map Requirements

14.5.2.1 Training Area UXO Hazard maps must show at a minimum the following:

1. The Training Area name;

2. Date the map was prepared / revised,

3. Revision number,

4. UXO Hazard Areas – see Appendix M for the symbology requirements

to be used for all Defence Training Area UXO Hazard maps;

5. Relevant boundaries including: Property Boundary, Range Boundary

Impact Areas, Camp or Admin Areas, Special Use/Restricted Areas,

Sector Boundaries;

6. Labels of precincts within the training area including: Sectors, Impact

Areas, Ranges, Administration Areas, Accommodation areas and

restricted use/access areas;

7. A scale bar. Scale is not to be shown as a ratio or fraction e.g. 1:10,000

or 1/10,000;

8. A legend describing what the map symbols represent;

9. A north point symbol indicating the direction of true north;

14.5.2.2 Defence Training Area UXO Hazard maps will show only one Training

Area;

14.5.2.3 Defence Training Area UXO Hazard maps are to show the entire Training

Area on a single sheet, unless agreed with the Defence point of contact;

14.5.2.4 The preferred page size for Defence Training Area UXO Hazard maps is A3

and must be legible at A4;

14.5.2.5 The Defence map template must be used for all Defence Training Area

UXO Hazard maps as shown in Figure 14.2. A template containing the data

model and a file containing sample data is available on the Defence Estate

Quality Management System (DEQMS).


Version 5.0 114 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

Figure 14-2: Example Defence Training Area UXO Hazard map


Version 5.0 115 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a


14.5.3.1 Areas delineating the location and extent of areas that have potential for the

presence of UXO will be represented as polygons. Each polygon will

encompass a region determined to have an equal level of UXO potential.

There must be one polygon for each UXO area.






14.5.4 Deliverables


1. New and or updated Training Area UXO Hazard spatial data

2. There shall be one Training Area UXO Hazard spatial dataset for the

entire geographic scope of services; and

3. New and or updated metadata record for new or updated Training Area

UXO Hazard spatial data set;

4. If requested, Defence Training Area UXO Hazard map(s) in PDF

format.



UXO spatial data is available on the Defence Estate Quality Management




14.5.6.1 This sub-section details any requirements in addition to those detailed in


14.5.6.2 File Names:

Where a project is contributing new Training Area UXO Hazard spatial data

the following filename schema shall be adhered to:

TA_UXO_HAZ_[Project Number]

Example: TA_UXO_HAZ_SN0089.shp

Where a project is updating existing Training Area UXO Hazard spatial

data the existing filename will be preserved.



Version 5.0 116 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

4 H

azar

ds

Dat

a

14.5.6.3 Where a project is contributing new Training Area UXO Hazard map the

following filename schema shall be adhered to:

[Property Name]-TA UXO Hazard Map-[Revision number].pdf

Example: Greenbank Military-TA UXO Hazard Map-Rev7.pdf


14.5.7.1 UXO spatial data are to be documented as GIS Data-Vector.

14.5.8 References

14.5.8.1 The requirements for Defence to maintain these data are mandated by the

following:

Commonwealth Policy on the Management of Land Affected by

Unexploded Ordnance, 1 February 2018.

14.6 Asbestos

14.6.1 Background

14.6.1.1 The Department of Defence utilises GEMS to store information on

instances of Asbestos across the Defence Estate. GEMS manages these data

within the following modules:

o GEMS asbestos module.

o GEMS Contaminated Site Register (CSR) – see Section 12 for specific

requirements.


14.6.2.1 Spatial data requirements for the Contaminated Site Register (CSR) are

provided in Section 12 – Contaminated Sites Data

14.6.2.2 Specific geometries for records managed via the GEMS asbestos module

are not required. GEMS asbestos module records are geo-enabled by

“geocoding” to another GEMS object that is geo-enabled. Refer Appendix N

– GEMS Geo-Enabled Objects.

Spatial Data Management Plan Section 15 GEMS Geo-Enabled Objects

Version 5.0 117 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

5 G

EM

S G

eo-E

nab

led O

bje

cts







Version 5.0 118 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

5 G

EM

S G

eo-E

nab

led O

bje

cts

15 GEMS GEO-ENABLED OBJECTS (FEATURES)


15.1.1 This specification outlines the elements of the Defence Estate that are represented in

GEMS and how they are spatially enabled. It also describes the requirements for

providing geometries (spatial data) representing these elements for use in GEMS.

15.1.2 This specification provides requirements for GEMS Objects for which there is no

specific SDMP specification. Where the SDMP provides specific specifications, these

take precedent (e.g. Section 13 - Environmental Data)

15.2 Approaches for Geo-Enablement of Objects (Features)

15.2.1 GEMS Objects are geo-enabled by:

relying on a “link” only to an existing GEMS geo-enabled object’s geometry

(i.e. linked only records have no additional geometry to maintain), or

receiving a “copy” of the geometry held by a linked GEMS geo-enabled object

(i.e. the record acquires its own copy of this object’s geometry which is able to

be maintained separately. or

A geometry directly associated with them.

15.2.2 Table 15-1 lists the “geocoded” GEMS Object types that in and of themselves are not

required to be provided with a spatial representation of their location and extent.

These objects are geo-enabled by linked reference with another GEMS object

geometry.

Table 15-1: Objects geospatial enabled via attribute association with other GEMS

Objects

Object Type Referenced to

Real Estate Contracts Related Architectural Objects. E.g. Property or Building

Equipment Related Functional Locations

Notifications Related Functional Locations

Work Orders Related Functional Locations

15.2.3 Appendix N list the types of objects that are geo-enabled in GEMS with a directly

associated geometry and the required feature types (point, line polygon). (for

awareness).

15.3 How Geometries are Created or Updated for Geo-enabled Objects (as GIS

features)

15.3.1 There are two methods available for creation of geometries that will directly represent

objects in GEMS, as follows:

GEMS:

via GEMS GEO.e tab [Geo-explorer “Local View”] in “edit mode” within the

GEMS record transaction, (else automatically created via system “default

assignment” of its parent GEMS object geometry).


Version 5.0 119 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

5 G

EM

S G

eo-E

nab

led O

bje

cts

Beyond GEMS:

via GEMS Master Data create or update processing supplemented with the

GEMS geo-enablement Refinement Work Flow processing (pending /TBA)

15.3.2 Currently, GEMS geo-enablement geometries, relating to GDL /HOTO and GEMS

Master Data processing do NOT require any change to current data provider

responsibilities (i.e. such as the current requirement to upload to NSIMS).

15.3.2.1 Data Providers should advise GEMS Master Data management after

properly completing NSIMS spatial datasets uploads where related to GDL

processing.

Table 15-2: Methods for Creation of Geometries for Geo-Enabled Objects

Method Context Requirements

GEMS User

Interface -

manually

Available to DRN

users with

relevant GEMS

edit access

or automatically

assigned a

[temporary]

parent record

geometry

At the beginning of the life cycle of an Object

and in order to confirm the validity of the new

record created, the system mandates the

requirement that a simple geometry be added,

representing the location and shape of the object.

(Note that a GEMS geo-enabled record cannot

be saved without a geometry)

If required, GEMS geometry may be further

maintained; edited directly or else refined via

work flows.

GEMS Master

Data Creation

process

MDM Team and

Off-line:

Available to

Defence

Contractors

Contractors lodging GEMS Data Loading

(GDL) tools must also continue to upload spatial

datasets and geospatial plans into NSIMS per

SDMP requirements as usual.

IMPORTANT: Contractors should confirm that

they have completed NSIMS uploads to the

GEMS Master Data team to assist the

completion of GDL processing.

15.3.3 An [interim] process will extract geometries for GEMS records from datasets

uploaded into NSIMS by the Contractor. Therefore, it is critical that Contractors

ensure that when supplying and uploading spatial data that the correct EBI is assigned

where applicable. (Refer to Sections 3 and 4)

NOTE: Estate Business Identifiers (EBIs), the physical asset identifier, are E&IG

systems “geocodes” (meaning their respective actual geo locations are pre-established

within geospatial systems) and should not be modified without approval. These

geocodes enable the correct association of information to the estate representation,

and thereby achieve the critical geospatial association with the correct GEMS asset

record.


Version 5.0 120 26 June 2020

Spec

iali

sed D

ata

Spec

ific

atio

ns

Sec

tion 1

5 G

EM

S G

eo-E

nab

led O

bje

cts

15.3.4 To assist new GEMS record creation, where a specific geometry cannot be generated

for an object, a “Stand-In” geometry is assigned by default, in which case the

geometry of the parent object is used to ensure the correct asset record context is

maintained. For example, if a geometry cannot be created for a Building the geometry

representing its [parent] Property will be applied by Defence.


15.4.1 Geospatial data submitted for GEMS must continue to conform with the requirements

of Section 2 General Data Specification, particularly with regard Spatial Integrity of

features.

15.4.2 Data Format

15.4.2.1 Data shall be provided in ESRI Shapefile format.

15.4.3 Required Attributes

15.4.3.1 So that geometries are able to be attached to their GEMS record, they must

be attributed with the EBI appropriate to the Object Type. See Appendix N

– GEMS Geo-Enabled Objects for attribution requirements.

15.4.4 File Names

Files shall be names as per the following schema:

GEO_[Object Type]_[Pt, Line, Poly]_YYYYMMDD.shp

Example: EST_Poly_20200207.shp