ADAC-Practical Applications: ADAC XML Data Transfer Implementation in Trimble Business Centre Chris Power

Biography Chris Power is a geospatial applications engineer working for UPG and Sitech on data harmonisation. Chris has a back ground in GIS, Surveying and Remote sensing. He has worked in both public and private sectors in areas including Local Council, Emergency Services, Mining, Civil Construction and Education. Chris is keen to see data harmonisation working in Australia and he is here today to talk about options for ADAC.

Presentation Abstract ADAC can be viewed as part of a merging between Land Surveying and GIS. It brings the discipline and accuracy of Surveying and the Technical capacity of GIS together establishing benefits to both. For example Surveyors benefit from the expanded use of attribute tree structures as a means to rationalise field code lists, while GIS gains smoother, more reliable data flows.  Abstract This paper describes the implementation of The ADAC xml data schema as a data transfer mechanism within the Survey Design and Construction Software application – Trimble Business Center (TBC). ADAC stands for ‘As Designed – As Constructed’ and is designed to standardise the capture and transfer of spatial data relating to public works. The data schema is implemented using XML and stems from the use of spatial data, and GIS in particular, by groups such as Local Councils and Utilities, as the basis for capturing and maintaining asset information. Our work focused on facilitating the use of the ADAC data standard for TBC users. Towards this end we created four items - A feature definition file based on the ADAC data schema, A UI for the entry and storage of ‘header information’, An ADAC data exporter, and an ADAC data importer. Collectively these items are known as the TBC ADAC Utility. The TBC ADAC Utility brings the ADAC data structure into the field via a feature definition file which effectively embeds ADAC into field survey workflows from the outset. The feature definition file also defines the data structure within TBC and provides the basis for mapping features to the ADAC format on export. Similarly it is also used to define ADAC XML features imported and written as native TBC features. ADAC is an attribute rich format which allows users to take advantage of TBC’s native attribution capabilities to create valid ADAC XML as required