Department of Defence. Spatial Data Management Plan. DRMS Document Id: Version: Defence Support and Reform Group R

Transcription

1 Department of Defence Defence Support and Reform Group Spatial Data Management Plan DRMS Document Id: R Version: Status: Draft Dated: 01 March 2015 Produced for: Director SIM

2 EXECUTIVE SUMMARY The Defence Support and Reform Group (DSRG) Spatial Data Management Plan (SDMP) has been developed to provide standards and specifications for spatial data management. The standards and specifications within the SDMP will improve data consistency and availability of information, and facilitate spatial information dissemination and sharing within DSRG. With its use, DSRG 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 DSRG 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 users both within Defence and Defence Contractors, and data managers within DSRG. It is the responsibility of data users to implement the SDMP Specifications and produce data in accordance with the specifications. Data Users 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. 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. 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 DSRG data standards. Sections 3 onwards contain a set of specific data type specifications that shall be implemented by all spatial data users. The data specifications cover the key DSRG 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 DSRG Spatial Data Management Specification, 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. Version ii 01 March 2015

3 Table E-1 SDMP Sections and Appendices SDMP Section Section 1 Section 2 Section 3 Section 4 Section 5 Section 6 Section 7 Section 8 Section 9 Section 10 Section 11 Section 12 Section 13 Section 14 Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I Appendix J Appendix K Appendix L Appendix M Description of Contents Introduction Data Specification Master Site Plan Datasets Spaces Plan Datasets Reference Data Engineering Detail Survey for Infrastructure and Assets Garrison Support Services Data Communications Data Aerial Photography Satellite Imagery Master Planning Datasets Contaminated Sites Data Environmental Data Hazards Data Glossary References Contaminated Sites Data Standards Metadata Specification Directory Structure Scale and Accuracy Master Site Plan AutoCAD Standards Space Plan Standards Garrison Support Services AutoCAD Standards Master Planning CAD Standards Environmental Data Model Space Plan Labelling Standards Hazards Spatial Data Standards 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 and include example data that has been collected in accordance with the SDMP specifications. Version iii 01 March 2015

4 TABLE OF CONTENTS Executive Summary Table of Contents Version History ii iv x 1 Introduction Purpose of SDMP Spatial Data Definitions Intended Audience Structure of SDMP Application of the SDMP SDMP Point of Contact Linkages with NSIMS DSRG Spatial Data Policy Future Changes to Spatial Data Management General Data Specification Introduction Data Format File Names Directory Structures Metadata Datums Coordinate Systems Units of Measurement Spatial Accuracy Spatial Scale Data Capture Data Viewing Version iv 01 March 2015

5 2.13 Spatial Integrity of Features - Topology Spatial Integrity of Features Topology in a CAD Environment Data Attributes Imagery Management Image Tiling Hardcopy Archival Vectorisation of Information Master Site Plan Datasets Scope of Specification Deliverables Deliverable Templates Data Deliverable Specification Specific Data Requirements Topology Specifications For Information Only Topology Guidelines Spaces Plans Scope of Specification Deliverables Deliverable Templates Required Inputs Data Deliverable Specification Specific Data Requirements Reference Data Scope of Specification Deliverables Deliverable Specification General Reference Documentation Deliverable Specification Design Drawings Version v 01 March 2015

6 6 Engineering Detail Survey for Infrastructure and Assets Scope of Specification Deliverables Data Inputs Deliverable Specification Specific Data Requirements Garrison Support Services Data Scope of Specification Status of Specification Deliverables Deliverable Templates Specific Data Requirements Communications Data Scope of Specification Deliverables Deliverable Templates Required Inputs Specific Data Requirements Field Capture Data Capture Aerial Photography Scope of Specification Deliverables Acquisition Requirements Orthophoto Specifications Orthophoto Deliverables Deliverable Specification Version vi 01 March 2015

7 9.7 Quality Assurance Documentation Specific Metadata Requirements Satellite Imagery Scope of Specification Background Information Deliverables Deliverable Specification Specific Data Requirements Master Planning Datasets Scope of Specification Deliverables Deliverable Templates Deliverable Specification Contaminated Sites Data Scope of Specification Deliverables Data Deliverable Templates Required Inputs Data Deliverable Specification Environmental Data Scope of Specification Background Information Data Deliverables Data Deliverable Templates Data Deliverable Specification Specific Data Requirements Hazards Data 95 Version vii 01 March 2015

8 14.1 Scope of Specification Schedule 11 Hazardous Chemicals Data and Maps (HAZCHEM) Hazardous Areas Data Unexploded Ordnance (UXO) Data Tables Table 1-1 SDMP User Groups...3 Table 1-2 SDMP Sections and Appendices...4 Table 1-3 Spatial Data Technical Authority...7 Table 1-4 Principles of the DSRG Spatial Data Policy...8 Table 2-1 List of Table 2-2 DSRG Spatial Data Formats Table 2-3 Recommended Tile Sizes Table 3-1 Scope of Master Site Plan Data Table 4-1 DEMS Structure Level Codes Table 4-2 Office Space Area Calculations Table 4-3 Spaces Plan Title Block Table 4-4 Spaces Plan - Optional Attributes Table 4-5 Spaces Plan - Defence Attributes Table 4-6 Spaces Floor Plan XData for Window Attributes Table 4-7 Spaces Floor Plan XData for Wall Attributes Table 5-1 Design and As-Constructed Title Block Requirements Table 5-2 Design and As-Constructed Title Block Optional Information Table 6-1 Scope of Data Collected using Engineering Detail Survey Table 7-1 Garrison Support Service Activities Table 7-2 Garrison Support Grounds Maintenance Grass Cuts Table 8-1 Communication Pit Data Table 8-2 Communications Conduit Data Table 8-3 Communication Cable Data Table 8-4 Communications Conduit Cable Link Data Table 9-1 Orthophoto Options for Resolution and Accuracy Table 9-2 Orthophoto Technical Specifications Table 9-3 Orthophoto Quality Assurance Plan Table 9-4 Aerial Photography Specific Metadata Requirements Table 10-1 Satellite Imagery Specific Metadata Requirements Table 14-1: Schedule 11 Hazardous Chemicals Workplace Site Map Presentation Guidelines Version viii 01 March 2015

9 Figures Figure 1-1 Master Site Plan Dataset - example data...2 Figure 1-2 Spaces Plan Dataset - example data...2 Figure 1-3 Specification Process Flow Diagram...6 Figure 2-1 Examples of Correct Topological Representation Figure 2-2 Examples of Correct Topological Representation Figure 2-3 Incorrect Topology - Unconnected line and point features Figure 2-4 Correct Topology - Connected line and point features Figure 3-1 Master Site Plan Dataset - example data Figure 4-1 Spaces Plan Dataset - example data Figure 8-1 Communication Pit Labels Figure 8-2 Communication Conduit Labels Figure 8-3 Communication Cable Labels Figure 14-1: Example Workplace Site Map Appendices Appendix A Glossary A-1 Appendix B References B-1 Appendix C Contaminated Sites Data Standards 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 Garrison Support Services AutoCAD Standards I-1 Appendix J Master Planning CAD Standards J-1 Appendix K Environmental Data Model K-1 Appendix L Space Plan Labelling Standards L-1 Appendix M Hazards Spatial Data Standards M-1 Version ix 01 March 2015

10 VERSION HISTORY Version Number Date Amendment Comment Released By 1.0 Feb 06 Draft Oct 06 Published May 07 Draft Feb 08 Published Aug 08 Published Dec 11 Draft Mar 15 Draft Baseline version for release Includes name change from CSIG to DSG 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. 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. Includes name change from DSG to DS. General restructure and revision of SDMP to improve currency, ease-ofuse and reduce ambiguity. Update of Section 12 and Appendix C. Addition of section 14 and appendix M for inclusion of Hazards Data John Ramsay DIIE John Ramsay DIIE John Ramsay DIIE Berceuse Bindle DIIE Berceuse Bindle DIIE Berceuse Bindle DSIM Rod Armstrong Version x 01 March 2015

11 Section 1 Introduction 1 INTRODUCTION 1.1 Purpose of SDMP The Defence Support and Reform Group (DSRG) 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 The standards and specifications within the SDMP will improve data consistency and availability of information, and facilitate spatial information dissemination and sharing within DSRG. With its use, DSRG 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 DSRG information systems and Defence spatial data users; Portability of staff skills; and Greater interoperability with organisations outside of Defence The SDMP has been developed as an initiative of the Directorate of Strategic Information Management (at that time known as the Infrastructure Information Environment - IIE) and forms a component of the Strategic Information Management Directorate (SIM) architecture. The SDMP provides the Data Specification for all data stored and managed within the DSRG National Spatial Information Management System (NSIMS). All spatial data shall meet the SDMP Specification to allow data to be accessed within NSIMS and DSRG Enterprise Level Spatial Systems. Section 1 - Introduction 1.2 Spatial Data Definitions Spatial data is information that defines the geographic location and spatial dimension of natural or constructed features on Earth. Spatial data stores geographic locations as a series of points, lines, and polygons using coordinate systems and topology to record and inform the location of information. Spatial data can be mapped using Computer Aided Design (CAD) or Geographic Information Systems (GIS) software. Defence Support (DSRG) conducts business with the assistance of spatial data in many forms and for many different purposes DSRG relies on two Key or Foundation Spatial Datasets upon which other spatial data is developed and referenced. These Key Spatial Datasets types are - Master Site Plan Dataset Spaces Plan Dataset A Master Site Plan Dataset exists for all key Defence Properties and contains the locations of natural and man-made features such as buildings, road, runways, and services. This dataset is used to plan and design new infrastructure on properties, Version March 2015

12 Section 1 Introduction and is used as a basis for the capture of garrison support services data. A sample of data from a Master Site Plan Dataset is shown in Figure 1-1. Section 1 - Introduction Figure 1-1 Master Site Plan Dataset - example data A Spaces Plan Dataset or Floor Plan is created for all key 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 data captured is used to assist in building management through the allotment of rooms, cleaning services, management of information technology assets and changes to buildings. A sample of data from a Spaces Plan Dataset is shown in Figure 1-2. Figure 1-2 Spaces Plan Dataset - example data Version March 2015

13 Section 1 Introduction Other common spatial data used by DSRG includes: Aerial photography and satellite imagery; Reference documentation including design and as-constructed plans of DSRG structures, assets and infrastructure, and associated reports; and Environmental data and information overlays including environmental monitoring, heritage, contaminated sites data, weed and fire mapping. 1.3 Intended Audience The SDMP is intended for use by those creating, using and managing spatial data within, and on behalf of, the Defence Support and Reform Group (DSRG) There are two key SDMP User Groups that are referred to within the SDMP, these are listed in Table 1-1. Section 1 - Introduction Table 1-1 SDMP User Groups SDMP User Group Data Users Data Managers Description of Group DSRG Project Officers, Directorate of Operations and Training Area Management personnel and Defence Contractors (Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors) that create, use and analyse spatial data. DSRG staff with a responsibility to manage spatial data to facilitate use of spatial data within their region or nationally. These include: Regional Information Officers (RIO); Regional Environmental Officers (REO); staff within the Directorate of Strategic Information Management (DSIM) and staff from the Estate Planning Branch, External Land Planning Directorate. 1.4 Structure of SDMP The SDMP contains two types of Standards: The General Data Specification (Section 2). (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 DSRG data standards. (Sections 3 onwards) contain a set of specifications for specific types of spatial datasets. The specifications for the two Version March 2015

14 Section 1 Introduction DSRG 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 Section 1 Introduction: All Users Introduction to the SDMP, the scope of implementation and background information Section 2 General Data Specification All Users Applicable to all spatial data Specifications for specific types of spatial datasets Section 3 Master Site Plan Datasets All users working Section 4 Spaces Plan Datasets with data that falls Section 5 Reference Data within the scope of the Specification Section 6 Engineering Detail Survey for Infrastructure and Assets Section 7 Garrison Support Services 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 Appendices Additional supporting information Appendix A Glossary For Information Purposes Only Appendix B References For Information Purposes Only Appendix C Contaminated Sites Data Standards All users working with data that falls within the scope of the Specification Appendix D Metadata Specification SDMP Technical Authority Appendix E Directory Structure All users Version March 2015

15 Section 1 Introduction Appendix F Scale and Accuracy For Information Purposes Only Appendix G Master Site Plan AutoCAD Standards All users working Appendix H Space Plan Standards with data that falls Appendix I Garrison Support Services AutoCAD Standards within the scope of the Specification Appendix J Master Planning CAD Standards Appendix K Environmental Data Model Appendix L Space Plan Labelling Standards Appendix M Hazards Spatial Data Standards 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. Section 1 - Introduction 1.5 Application of the SDMP The SDMP shall be applied by DSRG technical and business owners, spatial data managers and their representatives. This includes the Estate Planning Branch, External Land Planning Directorate and Defence Support Operations (DSO) services providers, Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors. All are responsible for the appropriate application of standards and the implementation of the SDMP requirement accordingly The SDMP specification process flow shall be applied as described below in Figure 1-3. Version March 2015

16 Section 1 Introduction Garrison Support Services Data Section 7 Communications Data Section 8 Aerial Photography Section 9 Satellite Imagery Section 10 Master Planning Datasets Section 11 Contaminated Sites Data Section 12 Environmental Data Section 13 Hazards Data Section 14 Section 1 - Introduction Figure 1-3 Specification Process Flow Diagram Version March 2015

17 Section 1 Introduction 1.6 SDMP Point of Contact General Note About Data: The DSRG spatial capability is currently going through a process of transition from file-based data formats to specifications for geodatabases. Through this transition the DSRG Spatial Data Technical Authority will act as the point of contact for questions relating to the SDMP, the data specifications within the SDMP and DSRG Spatial Data. Contact details for the DSRG Spatial Data Technical Authority are provided in Table 1-3. Table 1-3 Spatial Data Technical Authority Position Section: DSRG Spatial Data Technical Authority Manager Spatial Systems Department of Defence Defence Support Chief Operating Officer Division Strategic Planning and Performance Management Branch Directorate of Strategic Information Management Section 1 - Introduction Address: F3-GF-063, Fairbairn Park Offices, Fairbairn, ACT Telephone: Facsimile: Spatial Information Systems group mailbox iie.nsims@defence.gov.au 1.7 Linkages with NSIMS The National Spatial Information Management System (NSIMS) is currently the DSRG repository for all DSRG Spatial Information and is supported by the SDMP. NSIMS is located within the Defence Restricted Network (DRN) and is access managed NSIMS includes the following components: A spatial dataset metadata catalogue for searching and locating spatial and aspatial 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 All DSRG spatial data can be stored within NSIMS if the data meets the specifications of the SDMP. Version March 2015

18 Section 1 Introduction 1.8 DSRG Spatial Data Policy The principles of the DSRG Spatial Data Policy are described in and shall be adhered to by all DSRG spatial data users. Table 1-4 Principles of the DSRG Spatial Data Policy Principle Description User Responsibility Data Standards apply to all DSRG Spatial Data Information is a Defence Asset Security Adherence to Standards Interoperability Access Data from its Point of Truth The Standards and Specifications within the SDMP apply to DSRG Spatial Data. Specific standards apply to specific spatial datasets including the DSRG Key Spatial Datasets and other spatial data. Spatial Information shall be valued and protected as a key Defence asset. 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. Data shall be collected, stored and disseminated according to Defence Standards and specifications. 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. Data shall be acquired from a point as close to its (the data s) source as possible. 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. Arrangements shall be in place to protect DSRG s information assets in the event of its complete or partial loss, or destruction. The provision of Defence information is permitted on a Needs 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. The SDMP identifies the applicability and scope of minimum spatial data standards and shall be applied for DSRG Spatial Data. DSRG Contract Documents may identify additional specific requirements that shall be applied. 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 DSRG business, and to existing data and information systems. All finalised spatial data should be stored within NSIMS to allow DSRG to access a single data source and minimise the requirement to obtain multiple versions of data from external sources. Section 1 - Introduction Version March 2015

19 Section 1 Introduction Principle Description User Responsibility Documented Data shall be Shared Data shall be Collected with Assured Integrity Authoritative Errors and Omissions Metadata documentation shall be collected and maintained. Proper documentation of spatial data will ensure data is stored and can be retrieved logically and appropriately in support of DSRG operations and decision making. 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. Data shall be entered only once into Defence systems. There shall be a single authoritative source for each data element. DRN users shall have access to valid, reliable, complete data they can use with confidence to support improved decision making. Errors or omissions found in any dataset shall be rectified prior to final delivery or reported as soon as practical to the DSRG business owner or NSIMS Custodian. The DSRG Metadata Entry Tool (MET) shall be used to create and edit metadata to provide documentation of spatial datasets. The MET can be downloaded from: gement/default.asp 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. NSIMS custodian and user roles shall be used to manage spatial data integrity within NSIMS. 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. 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. Section 1 - Introduction 1.9 Future Changes to Spatial Data Management The SDMP is currently going through a process of staged revision with the implementation of the National Spatial Information Management System (NSIMS), the Garrison and Estate Management System (GEMS) Data Model and the transition from file-based data formats to specifications for Geodatabases. As part of this revision some of the SDMP data specifications will be revised to meet the requirements of the new systems and data formats. Contact the DSRG Spatial Data Version March 2015

20 Section 1 Introduction Technical Authority for further information regarding the revision schedule and implications for data capture projects Currently a Geodatabase Model is being designed for the Master Site Plan Dataset. It is anticipated that this will be implemented later in A Geodatabase Model for other DSRG Data will be implemented over time. Section 1 - Introduction Version March 2015

21 Section 2 General Data Specification Section 2 General Data Specification Section 2 General Data Specification Version March 2015

22 Section 2 General Data Specification 2 GENERAL DATA SPECIFICATION 2.1 Introduction 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. Table 2-1 List of Section 3 Section 4 Section 5 Section 6 Section 7 Section 8 Section 9 Section 10 Section 11 Section 12 Section 13 Section 14 Master Site Plan Datasets Spaces Plan Datasets Reference Data Engineering Detail Survey for Infrastructure and Assets Garrison Support Services Data Communications Data Aerial Photography Satellite Imagery Master Planning Datasets Contaminated Sites Data Environmental Data Hazards Data Section 2 General Data Specification The SDMP shall be applied by DSRG technical and business owners, spatial data managers and their representatives. This includes Infrastructure Division (ID) and Defence Support Operations (DSO) services providers, Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors. All are responsible for the appropriate application of standards and the implementation of the SDMP requirement accordingly. 2.2 Data Format All DSRG spatial data shall meet the format requirements defined in Table 2-2. Version March 2015

23 Section 2 General Data Specification Table 2-2 DSRG Spatial Data Formats Information Type Preferred Format Extension Comments CAD (Computer Aided Design) Data AutoCAD Drawing file* DWG* Shall be compatible with AutoCAD Release 2007 GIS Data ESRI Shapefile SHP, SHX and DBF Digital Elevation Models Satellite Imagery /Scans Aerial Photography Georeferenced Images Geodatabase Band Interleaved by Line Band Sequential TIFF and GeoTIFF ArcGIS GRID ERDAS IMAGINE Comma separated value Encapsulated Compressed Wavelet TIFF and GeoTIFF JPEG* Band Interleaved by Line Band Sequential ERDAS IMAGINE oracle spatial SQL server SAP ESRI personal geodatabase BIL BSQ TIFF & TIF Standard contents of ArcGIS GRID directory IMG CSV or TXT ECW TIFF & TIF JPG* BIL BSQ IMG Shapefiles shall be supplied with the three basic file extensions as a minimum and content must comply with relevant SDMP specification requirements It is anticipated that database extracts would be provided by DSRG for amendment. JPG and TIF images shall be supplied with an associated world file containing image header information (.JFW or.tfw file) ECWs shall be supplied with an associated ERS file containing the image header information. JPG and TIF images shall be supplied with an associated world file containing image header information (.JFW or.tfw file) Satellite Imagery should preferably be in 16-bit (raw) or 8-bit (pan-sharpened) JPEG2000 is a valid format Section 2 General Data Specification Version March 2015

24 Section 2 General Data Specification Information Type Preferred Format Extension Comments Data Attribute Tables Packaged reference information documents Dbase IV Comma separated value MS Excel 97 (*.xls) Portable Document Format AutoCAD Design Web Format DBF CSV or TXT XLS PDF DWF These data formats shall only be provided in addition to other data deliverables (in formats listed above) * Data format endorsed by the Approved Technology Standards List (ATSL) as a Defence Standard. Section 2 General Data Specification Version March 2015

25 Section 2 General Data Specification 2.3 File Names 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 Spaces shall not be used in file names, underscores shall be used to separate text File naming conventions specific to particular types of data are covered with the Specialised Data Specification sections of the SDMP 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) Section 2 General Data Specification 2.4 Directory Structures Directory structures used for spatial data deliverables shall be intuitive to users 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 DSRG Defence Estate Quality Management System (DEQMS) website Metadata 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 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 All DSRG data shall have a metadata record that accompanies the dataset. A valid metadata record is required to allow data to be loaded into the DSRG National Spatial Information Management System (NSIMS) Metadata shall be created and edited using the DSRG Metadata Entry Tool (MET). The MET allows users to create, view and edit metadata records within the defined metadata structure. Instructions on installation and use are provided on the DSRG Defence Estate Quality Management System website: Version March 2015

26 Section 2 General Data Specification The MET is a simple tool designed for non-specialist users to create metadata that meets the DSRG Metadata Specification. The tool provides an interface that leads a user through dialog steps and options to create a metadata record. Users do not need to be familiar with the full DSRG Metadata Specification (Appendix D) to create metadata that meets this specification 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 Keywords are used to improve efficiency in locating relevant information. A set of keywords has been developed to align to DSRG s business structure. Multiple sets of keywords can be assigned to a dataset to assist users in locating a dataset in the future Specific Metadata Requirements 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. Section 2 General Data Specification The full DSRG 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 DSRG Data Users or DSRG Data Managers shall be familiar with the contents of the Metadata Specification. 2.6 Datums A datum is the reference point against which spatial position measurements are taken. Detailed information on datums can be found on the following website: Horizontal Datum A Horizontal datum is used to describe the position of a point on the Earth s surface in association with a Coordinate System Defence has adopted the World Geodetic System 1984 (WGS84) as the standard for all spatially referenced data created for DSRG Although WGS84 has been adopted across Defence to support Defence operations, DSRG recognises that industry partners who Version March 2015

27 Section 2 General Data Specification 2.7 Coordinate Systems support the Defence Estate only have access to GDA and as a consequence will accept the use of GDA94 for spatial data used to support the Defence Estate as specified in the Spatial Data Management Vertical Datum A Vertical datum is used to describe a position vertically as the elevation or depth of a point DSRG has adopted Australian Height Datum (AHD) as the standard vertical datum A coordinate system divides the Earth s surface using a set of coordinates to identify the position of a point DSRG has adopted the Geographic Coordinate System and the Map Grid of Australia (MGA) as the standard coordinate systems. MGA requires the use of the GDA94 datum. Section 2 General Data Specification DSRG 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 Geographic Coordinate System The Geographic Coordinate System defines the locations of points on the surface of the Earth using Latitude and Longitude 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: Lines of latitude are measured as an angle from the equator (0 ) to either Pole, 90 South and 90 North 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 Map Grid of Australia 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. Version March 2015

28 Section 2 General Data Specification 2.8 Units of Measurement 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 The unit of length measurement shall be metres unless specified within the Data Type Specifications in Sections 3 onwards In ongoing projects, the unit of measurement within the dataset attributes shall be kept consistent. 2.9 Spatial Accuracy Spatial accuracy measures how closely a position in a dataset is located to its true position on the Earth s surface 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 Where a spatial accuracy is not specified within the SDMP the DSRG Project Officer shall provide guidance on an appropriate level of accuracy. Section 2 General Data Specification Spatial accuracy shall be recorded in metadata records for all data capture and derived data products Global Positioning Systems (GPS) are used by DSRG in a variety of business purposes. The right type of GPS 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 GPS can be used for applications that require higher accuracy than a hand-held GPS, but don t require the accuracy of an Engineering Detail Survey Global Positioning System (GPS) receivers record accuracy (or precision) of the GPS 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 GPS positional data and stored against each record or in the metadata record Spatial Scale Scale is the ratio of the distance on a hardcopy map or electronic data viewer to the true distance on the ground (eg. 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). Version March 2015

29 Section 2 General Data Specification 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: 2.11 Data Capture ± m at 1:50,000 = ± 25m ± m at 1:10,000 = ± 5m 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 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, Data Viewing 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). Section 2 General Data Specification 2.13 Spatial Integrity of Features - Topology All data captured or provided for DSRG 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 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. Version March 2015

30 Section 2 General Data Specification Undershoot in feature Correct Representation Incorrect Representation Overshoot in feature Correct Representation Incorrect Representation Section 2 General Data Specification Pseudo-node in contiguous features Pseudo node Same feature with identical attribute values. Broken line in feature Correct Representation Incorrect Representation Figure 2-1 Examples of Correct Topological Representation Version March 2015

31 Section 2 General Data Specification Artefacts Correct Intersection Incorrect Intersection Incorrect Intersection Linear Feature Spike in Linear Feature Open Polygon Section 2 General Data Specification Slivers Incorrect Representation Correct Representation Figure 2-2 Examples of Correct Topological Representation 2.14 Spatial Integrity of Features Topology in a CAD Environment 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. The capturing/editing of the CAD line work will include: Snapping of line/poly-line nodes to appropriate point features; Version March 2015

32 Section 2 General Data Specification 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, 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. Section 2 General Data Specification 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 Version March 2015

33 Section 2 General Data Specification 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 Data Attributes 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 Data attributes are described within the SDMP Detailed Data Specifications within Section 3 onwards for specific types of data 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 a Unique Identifier shall be included in both the spatial data and the attribute table to enable the spatial features and attributes to be linked. Section 2 General Data Specification 2.16 Imagery Management Image Tiling Digital ortho imagery and LiDAR data are generally tiled (divided into smaller images) to manage file size 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 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) x x x x 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. Version March 2015

34 Section 2 General Data Specification 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 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 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 Tile File Names 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: E N Tile Name: If appropriate additional information can be added to the tile name e.g. M where: Section 2 General Data Specification M=MGA 6=Zone =Easting 6230=Northing 1=0.1m resolution 01=January 10= Tile metadata should record the following information in addition to DSRG 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). Version March 2015

35 Section 2 General Data Specification 2.17 Hardcopy Archival 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; Skewed images shall be de-skewed (original dyelines may not be straight); and Poor quality originals shall be enhanced (de-speckled and/or sharpened) Vectorisation of Information 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. Section 2 General Data Specification Version March 2015