DAP Administrator Manual

Transcription

1 DAP Administrator 12.1 Manual

2 The software described in this manual is furnished under license and may only be used or copied in accordance with the terms of the license. Manual release date: 18/04/2012. Please send comments or questions to 2012 Geosoft Inc. All rights reserved. Geosoft is a registered trademark and Oasis montaj is a registered trademark of Geosoft Inc. Other brand and product names mentioned herein are properties of their respective trademark owners. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form, or by any means, electronic, mechanical, photocopying, reading, or otherwise, without prior consent from Geosoft Inc. The software described in this manual is furnished under license and may only be used or copied in accordance with the terms of the license. DAP.m Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. Geosoft Incorporated Queen s Quay Terminal 207 Queen s Quay West Suite 810, PO Box 131 Toronto, Ontario M5J 1A7 Canada Tel: (416) Fax: (416) Web Site: info@geosoft.com

3 Table of Contents Table of Contents ii Chapter 1: DAP Server and DAP Administrator 1 Introduction 1 Features in DAP Seeker 1 Structured Metadata Querying 2 JPEG2000 Support 2 Metadata Editor Multiple File Selection 2 Support for GDB extraction through web clients 2 Improved Automatic Rendering for Shapefiles 2 Web-based DAP Administrator Application 2 SQL Database Catalog 2 Managed Exploration Information Repository 2 Streamlined Data Management 3 Organizational Hierarchy 3 Web-based Metadata Editor 3 Index Map 3 Reports 3 Data Package 3 Simplified Security Model 3 Simplified Architecture 4 Support for Esri10 4 Other Changes in DAP 12 4 Hyper datasets 4 Active Directory User Caching for Secured Servers 4 Technology Overview 4 DAP Server Architecture 6 Technology Limitations 6 Geosoft DAP Server Licenses 7 Security Extension 7 Esri Integration Extension 7 Geosoft DAP Manual ii

4 acquire Integration Extension 7 ECW Extension 7 Max Datasets 8 Chapter 2: Preparing to Install 9 Target Audience 9 Package Contents 10 System Requirements 10 Before You Begin 11 Chapter 3: DAP Catalog SQL Server Database 12 Creating the DAP Catalog SQL Server Database 12 Database Permissions 12 Chapter 4: Installing DAP Administrator 13 Installing the DAP Administrator Web Application and Service 13 Accessing DAP Administrator 21 Chapter 5: Installing Geosoft DAP Server 22 Installing Geosoft DAP Server 22 Manually Installing the Geosoft DAP License Key 31 Adding an IDAP Account during the Installation of DAP Server Software 33 Other changes related to the IDAP account 33 Review of Installed DAP Folders and Files 33 Chapter 6: Testing the Geosoft DAP Server Installation 34 Setting up Internet Information Services 34 Starting Internet Information Services 34 Testing Geosoft DAP Servers from a Web Browser 35 Enabling OGC WMS Support 36 Troubleshooting 36 Installing DAP Server and DAP Administrator on Different Computers 38 Chapter 7: DAP Administrator Settings 39 General Information 39 Security 40 Hierarchy 41 Structured Metadata Query 42 Working with Structured Metadata Query (SMQ) 43 Structured Metadata Query Methodology 43 Disclaimers and Stylesheets 44 Dataset Types 45 Dataset Logic 45 iii Geosoft DAP Manual

5 View the Spatial Dataset Type Table 45 Adding Document Dataset Types 46 Multi-File Documents 48 Update Connectors 48 Chapter 8: DAP Security Model 49 How Web Clients Access DAP Servers 49 How Thick Clients Access DAP Servers 50 Enabling DAP Security 50 Creating an IDAP_### Domain Account 50 Configuring the IDAP_### Account on DAP Server Computer 51 Updating the IIS Security through IIS Manager Applying IDAP_### Security Permissions to DAP Folders 51 Planning and Creating DAP Security Groups 51 Setting DAP Securities to DAP Data Folders/Files 52 Testing DAP Security 52 Active Directory User Caching for Secured Servers 52 Chapter 9: Publishing Data on a DAP Server 53 Defining a Hierarchy 53 User Specified 53 Editing user defined hierarchies 54 From Metadata 55 Editing Metadata 55 Uploading Data 56 DAP Administrator Home 58 List of Datasets 58 Search 59 Advanced Search 60 Dataset Properties 61 General 62 Advanced 63 Metadata 65 Image Preview 66 Security 67 Updating the DAP Server Catalog 68 Publishing and Excluding Datasets 69 Excluding Datasets 69 Publishing Datasets 69 Geosoft DAP Manual iv

6 Updating the DAP Server 69 Setting the Coordinate System of Document Dataset Types 70 Errors 71 Chapter 10: Creating Data Source Connectors 72 Creating an acquire Connection 72 Creating an acquire Connector 73 Creating an acquire Selection Connector 74 Creating an RDBMS Connector 76 Creating an Esri Map Service Connector 78 Support of Esri Map Services by DAP Client Applications 78 Updating Connectors 79 Chapter 11: Advanced Reporting Functions 80 Creating DAP Server Usage Reports 80 Creating an Index Map 82 Creating a DAP Administrator Data Package 83 Chapter 12: Geosoft Integrated Metadata Solution 85 Metadata Best Practices 85 FGDC and ISO Standards 85 Improved Visualization of Metadata 86 Geosoft Metadata Editor 86 Metadata Schema 86 Project Package 86 Integrating a Geosoft Metadata Editor into the DAP Administrator web application 88 Appendix 1: DAP Limits 89 Configuration Limits 89 DAP Login Limits 89 DAP Administrator Configurable Limits 90 Catalog Limits 90 Extraction Limits 90 Render Limits 91 Disclaimer Limits 91 Appendix 2: Supported Dataset Types 92 Supported File Types 93 Associated File Extensions 95 Associated Directory Extensions 95 Voxels 95 Georeference Voxel File 96 v Geosoft DAP Manual

7 GIS Data Files 96 Documents 97 acquire Databases 98 Enabling SQL Server Authentication 98 Creating an ODBC Connection 100 Hyper Stores 103 Data Visualization 104 Appendix 3: DAP12 Migrator 106 Using the DAP12 Migrator 106 Appendix 4: Using Geosoft XML 109 Geosoft XML Reference 109 XML Document Notation 109 Request Response 110 Format 110 Request 111 Response 111 Example 111 XML Errors 111 Error Response 111 Example 112 Capabilities 112 Request 112 Response 112 Example 113 Configuration 114 Request 114 Response 114 Example 115 Catalog 115 Request 116 Response 116 Example 117 Catalog Hierarchy 118 Request 118 Response 119 Example 119 Catalog Edition Geosoft DAP Manual vi

8 Request 120 Response 120 Example 120 Dataset Edition 121 Request 121 Response 121 Example 121 Metadata 121 Request 121 Response 122 Example 123 Image 123 Request 123 Response 125 Example 125 Extract Data 126 Begin Extract Request 126 Begin Extract Response 127 Extract Status Request 128 Extract Status Response 128 Cancel Extraction 129 Extract Data Request 129 Extract Data Response 129 Example 129 Translate Coordinates 132 Request 132 Response 132 Example 133 Translate Bounding Box 133 Request 134 Response 134 Example 135 Default Resolution 136 Request 136 Response 136 Example 136 List Supported Coordinate Systems 137 vii Geosoft DAP Manual

9 Request 137 Response 137 Example 138 Coordinate Systems 138 Examples 140 Projection Transformation Methods 141 Length Units 143 Appendix 5: Creating Hyper Datasets 145 Creating a Geosoft HyperGrid 145 Creating a Geosoft HyperGrid Mosaic 146 Creating a Geosoft HyperMap 146 Creating a Geosoft HyperXYZ 148 Appendix 6: DAP Catalog SQL Server Database Schema 149 Database Schema 149 Full Database Schema 149 Structured Metadata Query and Hierarchy 150 Security 151 Settings 152 Logging 153 Appendix 7: DAP 12 Miscellaneous Information 154 DAP 12.1 Technologies 154 Removed Functionality 154 Storage 154 Glossary and Nomenclature Geosoft DAP Manual viii

10 Chapter 1: DAP Server and DAP Administrator Introduction Geosoft DAP (Geosoft Data Access Protocol) is a family of Geosoft server and client services that enable geoscientists to find spatial and other data for use in their projects. These technologies include three fundamental components: Verifying and publishing of all available spatial and other data resources that might be relevant within an organization. This includes data stored in a managed file system in the many common formats (grids, images, raw data, and documents), data and metadata stored in Relational Database Management Systems (RDBMS), spatial data stored in RDBMS systems (such as acquire), and data stored in corporate archiving systems. Searching for and evaluating data that may be relevant to a project at hand. This involves spatial and context searches for data by area of interest, dataset type, and full metadata evaluation to determine the value of each dataset for a particular use. It also involves quickly previewing the content of selected datasets. Retrieval of the selected data, which may be windowed to the area of interest, re-projected to an appropriate coordinate system, re-sampled to an appropriate scale, and transformed into a format that can be used. This also includes simple retrieval of documents and reports that support the data and can be viewed in native formats (such as DOC and PDF files). Features in DAP 12.1 The DAP 12.1 release focused on simplifying DAP architecture and workflow for data management. The DAP Server evolution to a database catalog and managed exploration data repository is a significant change. This is an improvement that addresses the challenges that DAP Data Managers experience in an application-based DAP Administrator tool as in DAP v11.2. It is also an important change to enable future improvements. For more detailed information see the release notes available at: Seeker Seeker simplifies the data search and retrieval process from DAP Servers and other online data sources. Seeker replaces the Find Data options with a new workflow-driven design that combines capabilities and concepts from DAP Find Data to create a simple 3-step workflow. Enhanced search capabilities including structured metadata queries can be used to refine the search results and selected data is simple to retrieve to your mapping and analysis environment. The Seeker data access tool is available in all Geosoft applications and plug-ins.

11 Chapter 1 Features in DAP 12.1 Structured Metadata Querying DAP Server 12.1 supports the ability in Seeker and Flamingo to search for data using specific metadata fields in addition to the free-text search based on keywords. JPEG2000 Support We have added support for JPEG2000 (JP2 and J2K file extensions), enabling them to be verified, published, and retrieved by users through the Seeker data access tool. Similar to the GeoTIFF format, JPEG2000 supports embedded coordinate system information. In addition, it also supports transparency which is very useful when sharing images of grids that are not simple rectangular in shape. Metadata Editor Multiple File Selection The Geosoft Metadata Editor in DAP Server 12.1 supports multiple file selection. This enables users to enter 'copyable' metadata fields for many datasets simultaneously. Support for GDB extraction through web clients Support for the extraction of Geosoft Databases is available in the web client interface for DAP Server Improved Automatic Rendering for Shapefiles DAP Server 12.1 includes improved default preview rendering for vector data. Specifically, hypermaps are created automatically in the DAP catalog and used for rendering Shapefiles, enabling Shapefiles to appear crisp, not blurry, when viewed in the DAP data access tools including Seeker and web clients. Web-based DAP Administrator Application The DAP Administrator user interface is accessed via a browser-based web application. DAP Data Managers no longer need to install a DAP Administrator application and are not required to login to the DAP Server or to a computer with a high bandwidth connection to the DAP Server to administer the DAP Server. The DAP Data Managers only need to use a supported browser on a computer with standard network access. DAP Data Managers can now more easily manage multiple servers in different regions. SQL Database Catalog The DAP Catalog has been migrated from a proprietary binary index file to a SQL Server relational database. The DAP Catalog and metadata are tightly integrated and managed together in a single SQL database. This not only facilitates reporting on who accesses what datasets, it is also an important direction for future improvements. Managed Exploration Information Repository DAP datasets are stored in a Managed Exploration Information Repository and dataset management is accomplished via the DAP Administrator web application. The physical location of the exploration datasets is always synchronized with the DAP Catalog. This eliminates the need for the DAP Data Manager to directly access the information repository or use other tools such as Windows Explorer that can potentially cause the DAP Catalog and the DAP datasets to become out of sync. 2 Geosoft DAP Manual

12 Features in DAP 12.1 Chapter 1 Streamlined Data Management DAP data management tasks have been significantly updated to streamline many of the tasks involved in verifying and publishing exploration datasets. Datasets are verified immediately when uploaded, before other data administration tasks such as metadata review and publishing. This results in a very fast publishing experience. Other data administration tasks, such as setting properties like security permissions or copyright notices to a dataset or group of datasets, have been dramatically improved from DAP Organizational Hierarchy The folder-based organizational hierarchy that is presented in a treeview to DAP clients is now based on tags or metadata, instead of Windows Explorer directories. DAP Data Managers organize data using a defined "folder structure" or using metadata fields to create a folder-like hierarchy. The DAP Data Managers can easily update the presentation hierarchy without having to un-catalog and re-catalog datasets, or re-organize files. Web-based Metadata Editor Geosoft Metadata Editors can be added to the DAP Administrator web application using the configuration in use within the corporation. The DAP Data Managers can edit metadata of a dataset in the Managed Exploration Information Repository via the DAP Administrator web application. This is critical if metadata is being used for the hierarchy. Index Map The DAP Data Manager can create an Index Map shapefile containing bounding box outlines and structured metadata query fields for all or for a selection of datasets managed within the DAP Server. The SQL Database stores dataset polygon boundaries. These can be used with metadata to create index maps. Index maps showing data coverage are easily created and can be attributed in ArcGIS by any of the pertinent metadata fields. Reports Reports related to the DAP Information Repository and data downloads. The DAP Data Manager can quickly and easily view and track the data that has been uploaded by type, including document dataset types without assigned coordinate system and bounding box, and data download activities. Data Package A selection of the DAP managed data repository can be shared with third party partners via a ZIP file that can be unzipped with the presentation hierarchy as a folder structure. The DAP Data Manager can filter, organize and create a zipped subset of data including the organizational hierarchy as a file structure. This data can then be removed from the managed data repository if required. Project data can be easily shared with other organizations. Simplified Security Model A simplified security model that uses DAP Security Groups. Data access is controlled using a security model based on groups. The DAP Data Managers can create DAP security groups containing Active Directory groups and users. Direct use of Active Directory security groups and users to assign permissions are no longer supported. This design allows other security models to be added in the future. Geosoft DAP Manual 3

13 Chapter 1 Other Changes in DAP 12 Simplified Architecture The DAP Administrator web application and DAP Server simplify the architecture and permissions when compared to DAP Setup and security of the DAP Server has been simplified. The DAP Data Manager can access all settings in one convenient and easy-to-use area. Support for Esri10 DAP Data Managers can publish ArcGIS v10 Layer (.LYR) file and Map Services. Other Changes in DAP 12 Hyper datasets Hyper datasets can no longer be created through the DAP Administrator interface. These datasets must be created in Oasis montaj. Active Directory User Caching for Secured Servers The first time a DAP client user makes a connection, they will be added to a cached user list called guids.cache. All users that have connected are stored in a new cache file. The next time the user connects, in a day, a month, or several months, they will have a faster connection experience. Technology Overview Geosoft DAP is a server technology that connects networked users to back-end spatial data stores, which is illustrated in the following diagram. 4 Geosoft DAP Manual

14 Technology Overview Chapter 1 From the deployment perspective, DAP is installed on a high-performance server at your data centre, where it can be configured to have high-speed access to data stores. A simple deployment would place DAP on a server that directly hosts large disks that store data to be distributed in a file system, and relational databases for storing metadata and geochemistry data. DAP responds to XML and Geosoft TASK requests for data catalogs, data searches, metadata and actual data retrieval. Professionals who need to find and use data will use their preferred applications, such as Oasis montaj, ArcMap, MapInfo, or an acquire API-enabled application to access data. Data can also be browsed and retrieved via a web interface. Alternatively, other applications can use Geosoft XML to deliver data to their own specific workflows. A DAP implementation requires a dedicated server in all cases, except possibly for evaluation purposes, or if DAP is deployed on a data professional s workstation to share data among a small team. For performance reasons, DAP creates and maintains an index file that stores certain information about all the catalogued data, and provides for optimal browsing and searching performance. A DAP Data Manager administers the DAP catalog through a web browser connected to the DAP Server network. The DAP Data Manager uses Oasis montaj or ArcMap to perform data QA/QC (Quality Assurance and Quality Control) and certain data preparation tasks. The DAP Administrator web application is used to directly manage the DAP Server and the data catalog. A typical data management workflow might involve accepting a package of project data and metadata that is to be permanently stored in the corporate data center and made available to a professional team. The DAP Data Manager first verifies that the data quality standards are met, that coordinate systems are correctly defined, and that data formats meet corporate and DAP standards. The approved data are then placed in the incoming folder for data uploading, and the DAP Administrator web application adds this data to the DAP Managed Exploration Information Repository, and they can then be published and made available to all approved users. Geosoft DAP Manual 5

15 Chapter 1 DAP Server Architecture DAP Server Architecture The Geosoft DAP Server: is a web application, and an ISAPI (Internet Server Application Programming Interface) extension uses TASK and XML protocols to communicate with DAP client applications provides data and metadata to data consumers; it does not support the uploading of data and metadata to the server provides the following services: Area of Interest (AOI) and metadata search Preview of the data Security services integrated with Active Directory Preview and download of metadata Extraction of data Technology Limitations The Geosoft DAP technologies are evolving to support more and more dataset types and environments. The following important limitations should be understood and accepted before attempting to implement a Geosoft DAP data distribution solution: 6 Geosoft DAP Manual

16 Geosoft DAP Server Licenses Chapter 1 Geosoft DAP takes advantage of the wide variety of data formats supported by Geosoft core technologies. If one of your data formats is not supported, Geosoft DAP can distribute your data as a document of unknown type, provided a strategy for georeferencing the data can be established. However, if data windowing and data re-projection is required, your data must be converted to a Geosoft-supported format, otherwise Geosoft can develop data links to your data as part of your solution. Geosoft DAP technologies are designed for, and tested in, environments that support up to 25 concurrent users. Should you require a larger number of concurrent users, Geosoft can work with you to develop usability benchmarks, design data storage, and server scaling strategies to meet your requirements. Geosoft DAP has been developed using Microsoft technologies and is installed and tested on Microsoft IIS servers. Geosoft DAP cannot be installed on UNIX servers. Geosoft DAP is intended as a data cataloguing and data distribution solution; not a data archiving solution. Geosoft DAP can be configured to connect to existing archiving solutions, but such a configuration should be discussed with Geosoft Professional Services. DAP supports access to acquire databases provided the client applications have implemented the acquire API that supports DAP connections. Contact ATS directly to discuss the support for this feature ( Geosoft DAP Server Licenses Along with Geosoft s DAP Server core technology, five licensed DAP Server extensions are now available: Security Extension Security features include support for Microsoft Active Directory (AD). All data can be secured on a dataset-by-dataset basis. Esri Integration Extension The Esri Integration extension enhances exploration project workflow by enabling the integration of the following Esri datasets and services: Esri LYR files, ArcGIS Map Services, ArcIMS Image Services and ArcIMS metadata services. ArcEngine (or ArcMap or ArcGIS Server) is not installed with the DAP Server. Either ArcEngine 9.3 or ArcEngine 10 can be installed separately and is optionally licensed through the DAP Server. ArcEngine v10 is required for version 10 LYR files. acquire Integration Extension Data stored in a corporate acquire database can be verified and published to acquire-enabled client applications using the acquire API. acquire SEL files are supported for point or collar datasets. ECW Extension The ECW extension is required to support extraction of ERMapper ECW image files larger than 500 MB each in size before compression. Geosoft DAP Manual 7

17 Chapter 1 Geosoft DAP Server Licenses JPEG2000 uses the same ECW Compression Algorithm licence. This means JPEG2000 images larger than 500 MB require the ECW compression license component. Max Datasets Supports a catalog of up to 220,000 datasets. 8 Geosoft DAP Manual

18 Chapter 2: Preparing to Install Target Audience This document is intended for Geosoft DAP Data Managers who are responsible for the installation and maintenance of the Geosoft DAP Server and spatial data catalog. A DAP Data Manager may be: A single user who wishes to create a personal DAP server for sharing data among a group of colleagues on an Intranet A corporate database administrator responsible for archiving and disseminating large-volume geospatial data across a corporate or organizational Intranet A database administrator at a government data distribution centre responsible for making largevolume geospatial data available to the public online This document may also be used by web developers for building web servers that integrate Geosoft DAP data distribution technologies into a data discovery and delivery web portal. You might choose the Geosoft DAP technology to perform your data distribution task because of one or more of the following reasons: You have large-volume data, such as large gridded data, airborne geophysical data, large georeferenced point databases or large vector maps, which you need to make available in an efficient way and with minimum data preparation costs. You may also have document files or files of other types that you would like to georeference, catalog, and distribute. Your data can be easily organized within a file system or similar hierarchy as individual datasets in a variety of formats. You want to be able to catalog this file system and make the data available to your data consumers. You have corporate data stored and managed within an acquire Data Model on an ODBC-accessible server, and you want to make these data available to clients who need to work with them. Your data-consuming clients are geographically dispersed and connected to central servers only via a WAN, or perhaps even the Internet, and you need an efficient and easy way for them to find and retrieve their own data. Your data is georeferenced in known or well-defined coordinate systems and must be converted to a user s coordinate system as part of the data delivery process. Because your datasets are large, and may cover broad geographic areas, your users may only require subsets of the data to suit their purposes. You need technologies that can efficiently subset and resample data to meet your users needs. A significant number of your data consumers use workstation software such as Oasis montaj, ArcGIS, and MapInfo to access and process data that you provide. You would like these users to be

19 Chapter 2 Package Contents able to access your data directly and efficiently from these environments. You want to provide a web interface to your data so that your data consumers can use a web browser to discover the data you have available, and retrieve this data in a variety of formats in a projected coordinate system. Because your datasets are large, and you may have a large number of separate datasets in different formats, you do not want to convert all your data to a single format. Your data models may be too complex to load all your data to a standard database. The Geosoft DAP Server technology addresses all the above scenarios within certain limitations. Package Contents The Geosoft DAP 12.1 is delivered with the following items: Geosoft DAP Server Installation DVD Includes the DAP Server installation, DAP Administrator installation, sample browser maps, and a SQL script to create a starting DAP catalog SQL database License key for your DAP Server System Requirements Geosoft DAP is a multi-threaded server application that will take maximum advantage of multiple processors and available memory. The more processors and memory on the server, the better the performance will be. The requirements listed below are guidelines. Speed and performance of a DAP server will be dependent on the hardware configuration and the data serving demands of your site. Hardware and software requirements depend on the intended use of Geosoft DAP Server. The minimum recommended DAP server configuration for a corporate DAP solution is: Operating System Microsoft Windows Server 2008 R2 Standard Web Server Microsoft IIS 7.5 Database Memory CPU Disk Space 1 Microsoft SQL Server 2008 Standard with SP1 or R2 Standard Recommended: 8 GB RAM (Minimum: 4 GB RAM) Recommended: Dual processor (Minimum: 2.0 GHz in Speed) 50GB for operating system 500GB to 1TB for datasets Physical disk space for DAP temporary files Third Party Support ArcGIS 10 with SP1 acquire API Browser 2 Microsoft Internet Explorer 8.0 or higher 3 Mozilla Firefox 3.6 or higher 10 Geosoft DAP Manual

20 Before You Begin Chapter 2 Google Chrome 8.0 or higher 1 2 Actual required physical disk space for datasets and temporary files is dependent on unique client configuration and data serving needs Applies to DAP Administrator For more detailed information on Geosoft DAP System Requirements, visit: Before You Begin Ensure that the following conditions are met: You have read through the entire installation process in order to familiarize yourself with the procedure. The Microsoft Internet Information Services server (IIS) and other required features are installed and running on the machine where Geosoft DAP Server will be installed. You are logged in with full administrator privileges to the server computer on which Geosoft DAP Server will be installed. You know the computer name of the machine on which you are installing Geosoft DAP Server. If your DAP server will be used on an Intranet for corporate-wide use or for Internet use, you know the name assigned to your DAP Server by your Domain Name Service (DNS) server. Your IT department establishes this name for you. You can normally verify that you have a valid name by pinging the name and verifying that the IP address returned is indeed the IP address of your server. You have at least 350 MB of free disk space for the complete Geosoft DAP Server installation. Note that you will build a file system on your DAP server to hold all of the data to be verified and published, so you will need sufficient disk space to hold all the data that you intend to publish. The Geosoft DAP Server installation DVD is in the DVD drive of the server. Save the Geosoft DAP installation files to a temporary directory on your server if you have received the installation kit via FTP or via the Internet. You have the Geosoft DAP Server license key that enables the Geosoft DAP license on your server. The Geosoft DAP Server license key may be printed on the installation DVD or supplied to you via an or other media. You are familiar with DAP limits. To view the list of DAP limits, See "DAP Limits" on page 89. It is important that the steps for installing the DAP Administrator and DAP Server are followed in the order presented to prevent any setup-related errors. Geosoft DAP Manual 11

21 Chapter 3: DAP Catalog SQL Server Database In DAP 12.1, the DAP Catalog is contained in a SQL Server database rather than in a proprietary binary file as used by DAP v11.2. Also, DAP datasets and metadata use a single database. Metadata is tightly tied to the dataset record. Creating the DAP Catalog SQL Server Database A SQL script is included with the DAP Server installation package. Run the script to create your DAP Catalog SQL Server database that is referenced in the DAP Server and DAP Administrator installations. There are also SQL scripts for creating a new DAP Catalog SQL Server database or modify an existing database to become the DAP Catalog SQL Server database. The DAP Catalog SQL Server database is required before the installation of the DAP Administrator. You should ensure that the database is part of your regular backup processes. Database Permissions Both the IDAP account and the Active Directory user that runs the Geosoft DAP Administrator service (may be the same) require read and write permission on the DAP Catalog SQL Server database. If the DAP Server is un-installed and re-installed, the IDAP account needs to be remapped to the DAP database.

22 Chapter 4: Installing DAP Administrator For first-time installation, we recommend that you install DAP Administrator and DAP Server on the same server computer. This minimizes configuration of file systems that must be accessible from both DAP Server and DAP Administrator. The DAP Server and DAP Administrator must be installed on the same network. The DAP Administrator web application and service can be installed on any computer located on the same network as the DAP Server computer provided that appropriate file sharing settings and permissions are established. For more information, See "Installing DAP Server and DAP Administrator on Different Computers" on page 38. You may consider installing the DAP Server and DAP Administrator on separate machines if you plan to publish a lot of data and you have many concurrent users. For example, the Geosoft Public DAP Server hosts the DAP Server and the DAP Administrator on the same machine, because data changes are quite rare, so there are only moderate publishing and updating requirements. Any computer may be used to administer the DAP Server provided that privileges allow access to the DAP Administrator web application. For hardware and software requirements, see Installing the DAP Administrator Web Application and Service 1. Run (double-click) the installation setup.exe file. The installation wizard opens to the Welcome dialog.

23 Chapter 4 Installing the DAP Administrator Web Application and Service 2. Click Next. DAP Administrator application files by default are installed in C:\Program Files (x86)\geosoft. This is not configurable during installation. If the installation is required to be located in a drive or folder other than the system drive, then the installation folder can be specified via the command line: setup.exe INSTALLDIR="d:\my install location". The License Agreement dialog is displayed. Select (check) the I accept the terms in the License Agreement option. 3. Click Next. The Data Folder dialog is displayed. 14 Geosoft DAP Manual

24 Installing the DAP Administrator Web Application and Service Chapter 4 The default DAP Data Folder is provided. To choose another location for the DAP Data Folder, click the Change... button. The Geosoft DAP Data Folder creates the following sub-folders: Incoming - The folder where new data will be uploaded, either by file transfer (FTP) or via the MDE (the upload folder). Outgoing - The folder where Data Packages are created. Storage - The data are stored here. This is the folder where the managed datasets will reside. Several other files used by the DAP Server are also stored here. 4. Click Next. Quarantine - The folder where datasets with errors will be stored. Replacement - The folder where replacement files can be uploaded. The Port Assignment dialog is displayed. Geosoft DAP Manual 15

25 Chapter 4 Installing the DAP Administrator Web Application and Service 5. Click Next. The Database Connection Settings dialog is displayed. 16 Geosoft DAP Manual

26 Installing the DAP Administrator Web Application and Service Chapter 4 Enter the SQL Server Host, DAP Catalog SQL Server database Name, SQL Server Username and Password for the database connection. The SQL Server user must have read and write privileges on the database. The SQL Server user account is used by the DAP Administrator service to read data from and write data to the DAP Catalog SQL Server database. 6. Click Next. The DAP Server Connection Settings dialog is displayed. Enter the DAP Server URL and password. 7. Click Next. The Administrator Settings dialog is displayed. Geosoft DAP Manual 17

27 Chapter 4 Installing the DAP Administrator Web Application and Service Enter the network domain and Active Directory security group name for the users that will have access to log in to the DAP Administrator web application. You will need LDAP settings for the LDAP domain and LDAP group. For example: LDAP domain: geosoft.com Administrator LDAP group name: Dap Admin Portal Users DAP can support users from different domains as long as the users can be authenticated across domains. Use the domain that contains the AD security group as the LDAP domain in the Administrator Settings. 8. Click Next. The Secure HTTP Configuration dialog is displayed. 18 Geosoft DAP Manual

28 Installing the DAP Administrator Web Application and Service Chapter 4 Enter the path and names for the HTTPS certificate and key files. 9. Click Next. HTTPS certificate and key files are required because the DAP Data Manager will type a network password into a web page when logging in to the DAP Administrator web application. The Ready to install Geosoft DAP Administration Portal dialog is displayed. Geosoft DAP Manual 19

29 Chapter 4 Installing the DAP Administrator Web Application and Service 10. To begin the install process, click the Install button. You can click the Back button to review or change any of your installation settings or click the Cancel button to cancel the installation process and exit the wizard. The DAP Administrator install process begins. 11. If DAP Administrator has been installed successfully, the Completed the Geosoft DAP Administration Portal Setup Wizard window is displayed. 20 Geosoft DAP Manual

30 Accessing DAP Administrator Chapter Click Finish. Note: If the datasets are not stored locally or the DAP Administrator and DAP Server are not installed on the same machine, then the Service can be changed to a Network account after the installation is complete since, by default, the Service is now installed as a Local System Account.. Accessing DAP Administrator You can access the DAP Administrator web application by browsing to where 9000 is the portal port assigned in step 5. The DAP Administrator service can be accessed under Control Panel > Administrative Tools > Services > Geosoft DAP Administration Portal. The DAP Administrator service uses the Windows\temp folder for temporary swap space. As some modules - such as Security - are licensed by the DAP Server, the DAP Administrator service will need to be restarted after the DAP Server installation has been completed. Geosoft DAP Manual 21

31 Chapter 5: Installing Geosoft DAP Server This chapter describes the installation and setup of a Geosoft DAP Server in a Microsoft Internet Information Services (IIS) environment. If this is the first time you are installing the Geosoft DAP Server, we recommend that you install the server on your personal computer in order to gain familiarity with the system before you attempt to install DAP on a dedicated server. Geosoft DAP Server comes with the following components: Core DAP Server If required, your DAP Solution Consultant can enable the ASP.NET sample web server that uses Geosoft XML to interact with the core DAP Server, to create a web client data discovery and delivery experience. This can be used as a starting point for a custom web experience. Thick client applications that use the Geosoft high-performance TASK protocol to directly interact with Geosoft DAP servers are available directly from Geosoft. These include Geosoft Oasis montaj and plugins for ArcGIS (through Target for ArcGIS), and MapInfo. Familiarity with Microsoft IIS is beneficial. If you intend to make your DAP Server accessible through the Internet, you should also understand how to secure your IIS server. If you are going to install Geosoft DAP servers on your local computer, or on a corporate Intranet, you can simply run the Geosoft DAP installation program while following the steps described in the installation instructions. Installing Geosoft DAP Server To install Geosoft DAP Server: 1. Start the IIS service, if it is not started. Normally, IIS would be running after a clean boot of your system. 2. Double-click the installation program. The Welcome dialog of the installation wizard is displayed.

32 Chapter 5 Installing Geosoft DAP Server 3. Click Next. The License Agreement dialog is displayed. 4. Select (check) the I accept the terms in the License Agreement option and click Next. The Destination Folder dialog is displayed. 23 Geosoft DAP Manual

33 Installing Geosoft DAP Server Chapter 5 5. To accept the default location, C:\Program Files (x86)\geosoft\dap Server\, click Next. To specify a different Geosoft DAP Server installation location, click the Change... button. The Administrator User Information dialog is displayed. Geosoft DAP Manual 24

34 Chapter 5 Installing Geosoft DAP Server 6. In the Full name, , and Phone number fields, enter contact information for the Geosoft DAP Data Manager. This information is stored in the ois.xml file on the Geosoft DAP Server, and can be maintained by the Geosoft DAP Administrator. 7. Click Next. The DAP Server Information dialog is displayed. 25 Geosoft DAP Manual

35 Installing Geosoft DAP Server Chapter 5 8. In the Address/URL field, type your server name with the prefix. If you are installing on a server that has been assigned a specific name through your DNS server, you can change the computer name to that name. You can also use a specific IP address if you know that your server IP will not change, although this is not recommended. 9. In the Password field, type the password that will be required to perform administrative functions on your Geosoft DAP Server. In the Confirm password field, re-type the password for confirmation purposes. 10. In the DAP Server name field, type the name of your Geosoft DAP Server. The name is used in server lists available to clients that have access to your Geosoft DAP Server. 11. Click Next. The maximum number of characters for the DAP Server Name is 64 characters. To view the full list of DAP limits, See "DAP Limits" on page 89. The Database Information dialog is displayed. Geosoft DAP Manual 26

36 Chapter 5 Installing Geosoft DAP Server 12. Enter the SQL Server name and Database name for the DAP Catalog SQL Server database. This information is required. 13. Click Next. 27 Geosoft DAP Manual

37 Installing Geosoft DAP Server Chapter 5 The DAP Account Information dialog is displayed. 14. In the Domain field, type the domain name assigned to the user account. 15. In the User field, type the name of the IDAP account user. 16. In the Password field, type the password for the account user. 17. In the Confirm password field, re-type the password for confirmation purposes. 18. Click Next. The Storage Folder dialog is displayed. The Storage folder will contain all datasets managed by DAP. This is the subfolder created during the setup of the DAP Administration Portal. If you wish to use a network drive for your dataset folder, you need to set up the network privileges required and used by the DAP Server. Note that access to data not on the DAP Server will be limited to the access speed of your network, and may not provide the performance required to meet your needs. To change the default folder, click the Change button and select a folder to be used for the Storage Folder. 19. Click Next. This folder must exist. It was created during the DAP Administrator installation The Temporary Folder dialog is displayed. Geosoft DAP Manual 28

38 Chapter 5 Installing Geosoft DAP Server 20. Using the Change button, select a folder for the Geosoft DAP Server to manage temporary files. The temporary disk space required is at least twice as large as the largest dataset that you envision serving times the number of concurrent users. For large Geosoft DAP installations, it may be best to reserve an entire disk for the temporary working directory. 21. Click Next. The Ready to Install Geosoft DAP Server dialog is displayed. 29 Geosoft DAP Manual

39 Installing Geosoft DAP Server Chapter Click Install. Once the file installation process is complete, the installer prompts you to enter your license key: This dialog may be hidden behind the installation dialog. 23. Do one of the following: Geosoft DAP Manual 30

40 Chapter 5 Manually Installing the Geosoft DAP License Key If you have your license key and your server is connected to the Internet, enter the key and click Internet. If you do not have direct Internet access, you can exchange license information with Geosoft via . If in doubt, click Cancel and establish your license manually. For procedure, See "Manually Installing the Geosoft DAP License Key" on page On the next page, click Finish. Manually Installing the Geosoft DAP License Key Normal installation of Geosoft DAP Server configures your license. However, if you were in doubt about your license key, Internet access, or , you may have chosen to cancel the licensing stage. In this case, you can use the following procedure to install your Geosoft DAP license. Always stop and restart the IIS service after installing, setting up or updating a Geosoft DAP license. To install your Geosoft DAP license: 1. If your Geosoft DAP Server computer has a direct Internet connection, or you have an service, from the Microsoft Start menu, select Start Programs Geosoft DAP Server License Setup. The Geosoft License Manager dialog is displayed. 31 Geosoft DAP Manual

41 Manually Installing the Geosoft DAP License Key Chapter 5 2. In the License Key field, type the Geosoft DAP Server License Key provided with your Geosoft DAP DVD. 3. Click Internet or . If you chose the option, you will receive an with instructions on how to install your e- mail license. If you chose the Internet option, the setup program sends your Geosoft DAP license key to the Geosoft License server, which in turn installs your Geosoft DAP Server license on your server. You receive a confirmation message similar to the one below if the license key is accepted. 4. Stop and restart the IIS service on the Geosoft DAP Server computer. Your Geosoft DAP Server becomes licensed and fully functional. Geosoft DAP Manual 32

42 Chapter 5 Adding an IDAP Account during the Installation of DAP Server Software Adding an IDAP Account during the Installation of DAP Server Software To increase the security of the services that DAP Server provides over the Intranet or Internet, the DAP Server executes within its own account. The previous version of DAP Server installers created a local IDAP account on the computer, which could then be manually replaced by a domain account. To simplify the installation process, the DAP Server installer will continue to create a local IDAP account, but the account can now be switched to a domain account during the installation. Other changes related to the IDAP account IDAP account no longer needs to be in the log on as a batch job policy group under the User Rights Assignment. IDAP account is used directly in IIS for anonymous access to the DAP virtual folder so that the DAP Server process is run under the IDAP account. Review of Installed DAP Folders and Files 1. Software folders: DAP Server: C:\Program Files (x86)\geosoft\dap Server (on a 64-bit operating system) DAP Server: C:\Program Files\Geosoft\DAP Server (on a 32-bit operating system) 2. DAP Server configuration: C:\Program files\geosoft\dap Server\DAP\Config\ois.xml. 3. Abort and Log folders: DAP Server (abort): C:\Program files\geosoft\dap Server\dap\aborts DAP Server (log): C:\Program files\geosoft\dap Server\dap\log The web site will be added to the default application pool. This needs to be in the 32-bit application pool. 33 Geosoft DAP Manual

43 Chapter 6: Testing the Geosoft DAP Server Installation Testing the Geosoft DAP Server installation involves the following: 1. Starting IIS on the server after reboot, if it is not already. 2. Testing Geosoft DAP Server from a web browser. Setting up Internet Information Services It is recommended that a new Application Pool is created for the DAP Server. This Application Pool should have the following configurations: Use Basic Authentication Use.NET Framework v4.0 On a 64-bit system, set Enable 32-bit Applications to True Managed Pipeline Mode to True Set the Application Pool identity to the domain IDAP account (add the IDAP account to the IIS_ IUSRS group to give it the required rights) Ping Enabled is True Rapid Fail Protection Enabled is False Uncheck all options in the Application Pool Recycling Settings Starting Internet Information Services The Internet Information Services (IIS) server must be running before you can connect to Geosoft DAP Server. IIS is normally running after a clean reboot of the system. To ensure that IIS is running correctly: 1. From the Start menu, select Settings Control Panel Administrative Tools Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager console is displayed.

44 Chapter 6 Testing Geosoft DAP Servers from a Web Browser 2. To stop and restart the DAP Server, select the DAP site and do one of the following: Right click on the site and select Manage Web Site, and select Restart Item, or Stop and Start, or From the Actions area, select the Restart, or Stop and Start items or Enter the IISRESET command in the command prompt window. Testing Geosoft DAP Servers from a Web Browser You can verify that your Geosoft DAP Server is running correctly from a standard web browser such as Internet Explorer. To test Geosoft DAP Server from Internet Explorer: 1. Open Internet Explorer. 2. Enter the URL for your Geosoft DAP Server, 35 Geosoft DAP Manual

45 Enabling OGC WMS Support Chapter 6 The DAP Data Folder storage folder must exist. The URL must have /dap/ois.dll as the last characters in the name. The above example uses "localhost". You can use a computer name instead. If you see the window as it appears in the above picture - or a variation thereof - your Geosoft DAP Server is installed correctly. Enabling OGC WMS Support Your Geosoft DAP Server can be configured to behave as an Open GIS Consortium (OGC) Web Map Service (WMS) server (see A WMS server responds to WMS requests to provide a catalog of the server contents and draw specific entries to an image for display in a webbased application. To make your DAP server provide WMS services: 1. On DAP Server, open web.config at C:\Program Files\Geosoft\DAP Server\wms. 2. Change the DAP_URL line <add key="dap_url" value=" /> to reflect the name of the DAP WMS server. So for the Geosoft Public DAP Server, the line becomes: <add key="dap_url" value=" />. This is the only line changed in the web.config file. 3. Enter the IISRESET command in the command prompt window. Troubleshooting If you encounter an error, or if your DAP Server does not seem to respond, you may need to troubleshoot your server. Geosoft DAP Manual 36

46 Chapter 6 Troubleshooting To troubleshoot your DAP Server: 1. Check that you have properly installed your Geosoft DAP Server license. To do this, from the Start menu, select All Programs Geosoft DAP Server License View. Your license should look similar to the following: If it does not, try to install your license again by selecting the Setup option from the License menu. Remember to always stop and restart the IIS service after installing, setting up or updating a DAP license. 2. Examine the most recent files in the following directories: C:/Program Files/Geosoft/DAP Server/DAP/Aborts Stores fatal errors reported by the server. C:/Program Files/Geosoft/DAP Server/DAP/Log directory Contains an information log of all 37 Geosoft DAP Manual

47 Installing DAP Server and DAP Administrator on Different Computers Chapter 6 transactions processed by the DAP server. Unlike the Aborts directory, where the presence of any files indicates a potentially serious problem, the Log directory usually contains files that are not necessarily indicative of any configuration or operational errors. 3. If there are files in the Aborts directory, contact Geosoft with the information in the files to determine a course of action. 4. Restart IIS (either by rebooting the server or by using the procedure to handle potential conflicts between IIS and other installed services). For more information, See "Starting Internet Information Services" on page 34. Installing DAP Server and DAP Administrator on Different Computers Your DAP Server can be administered from any computer on a shared network under the following conditions: The IDAP account under which DAP Server runs has read and write access to the DAP Data Folder The user account under which the DAP Administrator service runs has read and write access to the DAP Data folder The DAP Server and DAP Administrator are both able to connect to the DAP Catalog SQL Server database The DAP Administrator can communicate with the DAP Server through HTTP The DAP Server has read access to the DAP Data folder Establishing access to the Data folder from the DAP Server requires that the DAP Data folder be accessible from the DAP Server computer via UNC path. Geosoft DAP Manual 38

48 Chapter 7: DAP Administrator Settings After successfully installing the DAP Administrator web application and service, certain steps must be taken to prepare the DAP Server for active use. Each DAP Server managed via DAP Administrator requires its own configuration. 1. Log in to the DAP Administrator web application. 2. Click on Settings. 3. Change the settings as required. Settings are described below. Most Settings are modified during implementation. Some Settings may be modified later on, as required. Settings are grouped into the following categories: General Information Security Hierarchy Structured Metadata Query Disclaimers and Stylesheets Dataset Types General Information General Information includes the contact information for the DAP Server. The Server Name is published to the DAP clients. This is configured during implementation. Contact Information includes Name, Phone number, and . This is configured during the DAP Server installation. It may be updated at any time. These settings can be modified and updated as required by the DAP Data Manager.

49 Chapter 7 Security The following should be set for a DAP Server. Name: This is the name of the DAP Server as viewed in DAP client applications. Browser map: The Geosoft Map file that will be used as the Browser Map in DAP client applications. The extents and coordinate system of the browser map should be sufficient to cover the extents of all datasets that will be published by the DAP Server. If the map includes raster groups, such as a Geosoft Grid, then the map must be a packed map file. In DAP 12.1, there is an option to use Bing Maps aerial imagery as the Seeker browser map. The checkbox, Use Bing, will put an entry in the DefaultSettings table, browsermapbing True. This is supported by the Oasis montaj 7,5, Target 7.5, and Extensions for ArcGIS 3.5 Seeker client. The user will be required to sign in. The DAP server will then read this value and send it back in the configuration to the client which will then display the Bing Map if the user is signed in. If the user is not signed in, they will get the default Oasis montaj browser map. As well, a supported license is required, otherwise the user will get the default browser map. If the checkbox is checked, the DAP Data Manager should still provide a browser map. This will be used by pre-7.5 clients and to specify the DAP Server extents. The packed map will still set the AOI and the region list will still be used. The Compatibility for this feature has the same requirements as Oasis montaj. A high-speed internet connection is ideal, but not required. There is no browser requirement in Seeker except for the requirements for viewing metadata. Region list: The Region List is displayed in DAP client applications. It is loaded from a CSV file and stored in a table in the DAP Catalog SQL Server database. The aoi.csv that may be observed in the Managed Exploration Information Repository is a cached output from the aoi [RegionList] table in the database. This cache is regenerated every time the DAP Server is started. You can add a region in the table instead of reloading the CSV, if desired. Security The Security tab will appear if the DAP Server is licensed for this module. 40 Geosoft DAP Manual

50 Hierarchy Chapter 7 User verification: If selected, this option means that user login and verification are required for data access. Flamingo users will be required to enter their Active Directory name and password. The DAP Server must be licensed for this feature to be used. Security groups: The DAP Data Manager can create DAP Security Groups and include Active Directory groups or users. These groups can be applied to single or multiple datasets. User verification must be selected to enable this. See "DAP Security Model" on page 49 for more details. Hierarchy Hierarchy is the virtual folders used to display datasets in a tree or list view in a DAP client application. These folder names are based on hierarchy tags which can be defined on individual or groups of datasets in the Dataset Properties. From metadata: The folder structure presented in the DAP client application is created from metadata fields that have been added to the Structured Metadata Query list. User specified: The folder structure presented in the DAP client application is created from the folders used in the uploading of the data, from the Metadata Editor upload process or alternative methods.the folder level may be renamed to something more descriptive. Geosoft DAP Manual 41

51 Chapter 7 Structured Metadata Query During the implementation process, the hierarchy is set to use either "From metadata" or "User specified". Extreme care should be taken when considering switching between these two options. Structured Metadata Query DAP Server supports the ability in Seeker or Flamingo to search for data using specific metadata fields in addition to the free-text search. This can refine the data search on large corporate data repositories quickly and effectively, realizing the metadata investment. Specify the tags that will be used to populate the Structured Metadata Query with values from designated metadata fields that will populate the list of values in the DAP client Advanced Search options. These fields and values are also available to be used for the Metadata Hierarchy. Only string fields can be used in the Metadata Hierarchy. 42 Geosoft DAP Manual

52 Structured Metadata Query Chapter 7 The Structured Metadata Query fields should be configured before data is added to the Data Folder. In DAP 12.1, new Structured Metadata Query fields for published datasets are not updated automatically by the DAP Administrator service. Working with Structured Metadata Query (SMQ) The following list of best practices has been provided to assist in ensuring that your structured metadata queries provide the most optimum results: Use the keywords type of metadata fields with pick lists, such as subject, category, project name, data creator, creation date and data formats. Keep the list of metadata fields short; no more than a dozen. Do not use the title, description/abstract fields. The list of titles equals to the number of datasets on the DAP Server, which could be very large to be displayed in Seeker or web browser. Do not use continent, country and province/state metadata fields. They work in the similar way as AOI. The list of datasets returned in Seeker shows the datasets in a ranked order: the algorithm used by DAP Server ranks the datasets by how closely the dataset area matches your AOI. Datasets that are closest to your AOI are returned first. These fields are still available via the free text search. Do not use the metadata fields with yes/no (0 or 1) values. Structured Metadata Query Methodology 1. Connect to the DAP Server. 2. Server is queried for list of SMQ fields. 3. Server is queried for list of operators for selected field and Server is queried for list of distinct values for selected field. 4. Expression is transformed into xml parse tree. Example 1: Geosoft DAP Manual 43

53 Chapter 7 Disclaimers and Stylesheets Project Name = Arctic Gravity Project <query> <statement operator= = field='project Name value= Arctic Gravity Project /> </query> Example 2: Project Name Contains Arctic and Subject = Geochemistry <query> <operator value= and > <statement operator="contains" field= Project Name value= Arctic /> <statement operator= = field= Subject value= Geochemistry /> </operator> </query> 5. Select the Results step to view the query results. Structured queries formed in the Advanced panel in Seeker are applied to all servers that share the metadata schema. Disclaimers and Stylesheets The DAP Data Manager can add (and remove) Metadata Stylesheets and Dataset Disclaimers, and also designate the default stylesheet and disclaimer that will be used in the Dataset Properties unless otherwise specified. The 'default' stylesheet or disclaimer is the active entry that is displayed in the Settings list. (Use default) in the Dataset Properties means that the DAP Data Administrator does not need to individually change the stylesheet or disclaimer when the stylesheet or the disclaimer content are updated. 44 Geosoft DAP Manual

54 Dataset Types Chapter 7 Dataset Types Only datasets with extensions that appear in the Spatial Dataset Types and Document Dataset Types tables will be verified from the incoming folder. This section shows you how to view supported Spatial Dataset Types and how to add new Document Dataset Types. See "Supported Dataset Types" on page 92 for the list of supported file types and the characteristics for each type. The DAP Data Manager can review the list of DAP-supported Spatial Dataset Types. Supported DAP Spatial Dataset Types cannot be removed in the Settings page. The Dataset Type is a property of the dataset and can only be edited in the database. This property should not generally be modified except in specific circumstances. DAP Data Managers should contact DAP Support before modifying this property. For example, the Dataset Type may be changed to Document for non-georeferenced Picture types such as a digital photograph in JPG format that is being treated as a document and is not georeferenced. Dataset Logic The DAP Dataset logic has been updated in DAP In DAP 12, if the recognized dataset was verified with other files in the same folder with the same root name, they were treated as a single dataset. This meant that two datasets with the same name could get their associated files mixed up, resulting in an error and a tedious unravelling process. However, in DAP 12.1, a dataset file extension must first match the file extension in the Dataset Types list. Then, other files with the same root name and extensions that are listed as associated are included with the dataset. This is also the case for when the second extension matches dataset extension, e.g..grd.gi. If there are other file(s) with the same root name as the dataset, it will not be included with the dataset if: it has its own xml file, e.g. if file.map.xml exists, then the file.map will not be associated with a file.tab. it is listed as its own primary extension, e.g. file.tif will not be associated with file.gdb. it is an associated extension of another dataset, e.g..dat is associated with a.tab file. it has double extension equal to another primary extension, e.g. file.jpg.gi will not be associated with file.grd. In addition, DAP 12.1 has also added the ability to add a * at the end of an associated extension, e.g. <associated_file ext=".hgd*" /> in the Dataset Types list of associated files. This is expected to dramatically improve the incorrect file associations on verification for folders that contain multiple datasets with the same root file name. View the Spatial Dataset Type Table To view the Spatial Dataset Types table: 1. In the DAP Administrator web application, click on the Settings page, then select Dataset Types. The Dataset Types section is displayed. Geosoft DAP Manual 45

55 Chapter 7 Dataset Types 2. Under Spatial Dataset Types, click View Default. The Spatial Dataset Types window is displayed. The table in the window shows a list of the supported spatial dataset types. Adding Document Dataset Types To enable cataloging of a file type that is not included in supported Spatial Dataset Types, you must add a mapping for this dataset type to the Document Dataset Types table. To add a new Document Dataset Type: 1. In the DAP Administrator web application, click on the Settings page. The Document Dataset Types table is displayed. 46 Geosoft DAP Manual

56 Dataset Types Chapter 7 2. Click Add. The Add Document Dataset Type window is displayed. 3. In the Name field, enter a name for the new Document Dataset Type. 4. In the Extension field, enter the file extension for the new Document Dataset Type. 5. Optionally, enter a Qualifier and in the Associated Extension and Associated Directories fields, add any associated file or directory extensions, respectively, required for the new dataset type. 6. Click Add. Geosoft DAP Manual 47

57 Chapter 7 Dataset Types The Add Document Dataset Type window closes. The new Document Dataset Type appears in the Document Dataset Type table. 7. Select a Document Dataset Type in order to Edit or Remove it. Multi-File Documents Multi-file Documents are also supported. A 'multi-file' document is a document file type which includes associated extensions. When a user retrieves the dataset via their DAP client application (such as Seeker or Flamingo), they will download a zip file containing all of the associated files. Update Connectors For information on the Connector Updates options, See "Creating Data Source Connectors" on page Geosoft DAP Manual

58 Chapter 8: DAP Security Model The architecture of the DAP Security Model is illustrated below: The DAP Server must be licensed for DAP Security in order to use this functionality. How Web Clients Access DAP Servers Flamingo is the Geosoft DAP web client.

59 Chapter 8 Enabling DAP Security 1. A user connects to Flamingo from a web browser and enters login credentials. The user is logged into the same domain as the IIS server. 2. Flamingo verifies login credentials. The cached user list and / or Active Directory is queried by DAP server. 3. The DAP Server determines the list of datasets that the user is allowed to access by querying against the Active Directory ID of the user. The DAP Server also indicates the actions the user can perform on the datasets: view the metadata, preview the dataset and extract data from the selected dataset. The DAP server sends the results to Flamingo. 4. Flamingo builds a results web page and sends an HTTP response to the user via IIS. 5. The Active Directory ID of the user is used for all subsequent queries of and requests to the DAP Server. How Thick Clients Access DAP Servers 1. A domain user launches a DAP client software application (Oasis montaj, ArcMap, or MapInfo). 2. Inside the client application, the Seek Data > Seeker command launches the DAP client plugin. The plugin sends the Active Directory ID of the logon user to the connected DAP Server to query the datasets available to the user. 3. The DAP Server returns - as a HTTP response via IIS - the list of datasets available to the user, along with the actions the user can perform on the datasets: view the metadata, preview the dataset and extract data from the selected dataset. Enabling DAP Security To enable the DAP security, do the following in the order listed: 1. Create an IDAP_### domain account. 2. Configure the IDAP_### account on the DAP Server computer. 3. Update IIS security through IIS Manager. 4. Apply the IDAP_### appropriate security permissions to all DAP related folders in Windows Explorer. 5. Plan and create DAP security groups in DAP Administrator. 6. Assign user permissions to DAP datasets in DAP Administrator. Publish the datasets; if the datasets are already published, refresh the security by running Update DAP Server in DAP Administrator. 7. Enable DAP security for Flamingo, if used. 8. Test the secured DAP Server in a DAP thick client (Seeker) and Flamingo. Creating an IDAP_### Domain Account DAP Server installation program creates an IDAP_### account on the local computer. To enable the DAP security, a domain IDAP_### in the internal network system needs to be created. Use a meaningful name to replace ###. 50 Geosoft DAP Manual

60 Enabling DAP Security Chapter 8 Set up the domain IDAP_### account to No logon to limit its security permissions and to Password never expire. Configuring the IDAP_### Account on DAP Server Computer On the DAP Server computer, use the Control Panel Administrative Tools Computer Management System Tools Local User and Groups Groups and add the IDAP_### domain account to the Users group. Updating the IIS Security through IIS Manager Open the Internet Information Services Manager and select <Server_Name>\Web Sites\Default Web Site\DAP. 2. Right-click on the DAP website and from the popup menu, select Properties. 3. On the DAP Properties dialog, select the Directory Security tab. 4. Click the Edit button under Authentication and access control. 5. Ensure that Enable anonymous access is enabled. Enter the following information: User Name: IDAP_#### (use the Browse button to find the domain IDAP account) Password: Password for the IDAP_#### account 6. Your Application Pool should also be set to run as your IDAP_#### account. Save the changes and close all the dialogs. 7. Recycle the Application Pool or open a Command Prompt window and type the following at the DOS prompt: IISRESET Applying IDAP_### Security Permissions to DAP Folders 1. On the DAP server computer, grant the IDAP_### domain account the same permission as the local IDAP_DAPServer account created by the DAP server setup program. It is important that you traverse the DAP software directory and its sub-directories to complete this process. The following permissions are required on the DAP server computer and should be applied recursively. a...\program Files (x86)\geosoft\dap Server\dap (modify) b...\dap\storage (read, write) c...\daptemp (modify) Planning and Creating DAP Security Groups Use DAP data security groups. The DAP security groups created should be easy to manage and make sense to your company s workflow and business operations. One model to create DAP security groups is based on exploration projects. Use the DAP Administrator web application Security Settings to create DAP security groups. Geosoft DAP Manual 51

61 Chapter 8 Enabling DAP Security Setting DAP Securities to DAP Data Folders/Files In DAP Administrator, select a dataset(s), assign Security under Dataset Properties, and Update DAP Server to update access permissions. Testing DAP Security Use the Seeker client to test the change of access permissions. Active Directory User Caching for Secured Servers The first time a DAP client user makes a connection, they will be added to a cached user list called guids.cache. All users that have connected are stored in a new cache file. The next time the user connects, in a day, a month, or several months, they will have a faster connection experience. The SID cache is stored in the root of the Managed Exploration Data Repository / Data Folder. It contains a list of active users. The DAP12.1 Server keeps an extra thread that watches the in-memory cache and automatically refreshes the list. The list is updated with new users when they connect to the DAP Server. The file is an ASCII file, so new users can be added manually. There is no fixed limit on the number of users in the cache file. The in memory cache will be rebuilt if IISRESET is run. The combination of deleting the guids file and running IISRESET would delete the cache completely. 52 Geosoft DAP Manual

62 Chapter 9: Publishing Data on a DAP Server The DAP Administrator enables you to manage data to be published on your DAP Server. This includes the following: 1. Designing a hierarchical structure within which your data will be presented. The hierarchical structure is similar to a file system in Windows Explorer. 2. Establishing rules for managing metadata and relating metadata entries to the published data files (if you maintain metadata in an external RDBMS). 3. Preparing data to be published, this may be as simple as copying the data to the incoming folder, or preparing optimizations for certain datasets and establishing appropriate metadata. This task depends on the objectives you have for your DAP server, and on the characteristics of specific datasets you publish. 4. Creating connectors to certain datasets, such as acquire data stored in a relational database (RDBMS). 5. Publishing the data, which may involve the file systems for the dataset types and connectors that you want to publish, farming the required metadata, setting up the required files, creating visualizations to support visual browsing of your data, and updating the DAP Server that is exposed to your data clients. 6. Managing your data catalog by adding new data, removing unwanted data, and updating certain dynamic dataset types. Defining a Hierarchy You need to design a logical hierarchy in which you want to present data to be published on your DAP Server. We will use a typical, fairly simple example to illustrate the various points as we work through this section. In our example, we want to publish the archived historic project data, drilling and geochemistry data stored in a corporate acquire database, regional geophysical data, and global reference data. If you would like DAP clients to see data organized in a tree of primary and sub folders, this can be done using Metadata or using User Specified tags. User Specified If Hierarchy is set to use "User specified", then we could create a single directory on our DAP Server s incoming folder that has a set of subdirectories with these names. The folder names from the incoming folder will be set to the Hierarchy level "tags".

63 Chapter 9 Defining a Hierarchy The Hierarchy Settings needs to have enough tags to support the number of folder levels used in the incoming folder. We recommended limiting the hierarchy to 4 to 6 tags. Editing user defined hierarchies When the User Specified hierarchy setting is applied, the hierarchy that will be presented through the DAP client is shown in the Advanced Dataset Properties for a single dataset or for multiple selected datasets with the same hierarchy values. To make changes to the hierarchy for the select dataset(s), click Edit. The Edit Hierarchy dialog will display with the number of levels specified in the DAP Administrator Settings. You can select existing values from the pick list: Using the Add/Edit button, you can modify existing values by selecting an existing value and entering a new value, 54 Geosoft DAP Manual

64 Defining a Hierarchy Chapter 9 or add new values simply by entering a new value. From Metadata Select values from the Structured Metadata Query list. See Structured Metadata Query Settings. Editing Metadata If your Geosoft Metadata Editor has been configured in the DAP Administrator web application, then the Edit button will be active when a single dataset is selected. The Metadata Editor will open. After making the required updates, click OK to save the changes. Geosoft DAP Manual 55

65 Chapter 9 Uploading Data Uploading Data Datasets in the incoming folder are verified and uploaded into the Managed Exploration Information Repository. Data may be added to the incoming folder via the Metadata Editor upload, or manually via a file transfer such as FTP. The incoming folder is monitored by the DAP Portal for new files. When a dataset is added to the incoming folder, the DAP Administrator service checks the datasets for changes every 5 minutes to ensure that the complete dataset with all associated files has been completely uploaded. Associated files have the same name as the key dataset file and are in the same folder (e.g. mag.grd may have an associated file in the same folder called mag.grd.gi). If there are changes, the system checks again in another five minutes. After two checks, where no changes have occurred, the system will upload the dataset. The 5 minute delay is configurable. 56 Geosoft DAP Manual

66 Uploading Data Chapter 9 Only dataset types defined in the Settings: Dataset Types table are recognized. The picture file types are always rendered and delivered in an image format. The SPF (SHP) and SPF (TAB) file sets are read using the SPF (Spatial Feature) DAP interface, which can deliver the GIS-type data to clients that accept the GIS data. Only georeferenced Geosoft voxels can be cataloged and delivered via the DAP Server. See "Voxels" on page 95 for suggestions regarding working with voxels. The dataset must have a valid coordinate system that can be reprojected into WGS84 Depending on the dataset type, verifying a dataset may involve the following procedures: Extracting the required metadata Checking for the required information such as titles and coordinate systems, either directly in the datasets or in the supplementary metadata database Preparing fast-view images in the coordinate system of the browser map Preparing work files (such as a data cache) that may be required When the dataset is verified successfully, it is uploaded into the Managed Exploration Information Repository storage folder, and a record is added to the DAP Catalog SQL Server database. If there are any warnings or errors, these are reported in the log file. If there is an error, the file or connector is not verified. If the dataset fails the verification process, then it is moved to the quarantine folder and will appear in the Error tab. A number of supporting files may be created for verified datasets including:.cache folder - A cache folder is automatically created for TAB files and warped images.custom_info - The custom_info file contains information for some datasets that cannot be stored in the SQL database catalog..image_info - The image_info contains information used for the snapshot Geosoft DAP Manual 57

67 Chapter 9 DAP Administrator Home.snap_shot - A single 1600x1600 snapshot is used for dataset preview.properties - The properties file contains internal metadata object information and is used for extraction for some dataset types..spatial_image - The spatial_image is a 128x256 bitmap used for large datasets with a dimension of > 7 degrees longitude Then the datasets are available for further preparation and publishing. DAP Administrator Home Administering datasets for publishing on a DAP Server is performed in the DAP Administrator web application Home page. The Home page includes several tabs. The All tab is shown below: List of Datasets The List of Datasets contains five tabs: All, Verified, Published, Excluded, and Error. The All tab shows all datasets in the DAP Catalog database. Other tabs in the List of Datasets organize the datasets according to the status of the dataset. 58 Geosoft DAP Manual

68 Search Chapter 9 All - All datasets that exist in the DAP system can be listed here. Verified - New datasets that have been uploaded and passed the verification process. These datasets can be published or excluded as part of the data management process/workflow. Verified datasets meet the following criteria: The dataset is one of the supported spatial dataset types. The dataset can be opened. If spatial, the dataset must have a coordinate system, and can be reprojected into WGS84. Published - Datasets that have been published to the DAP Server. Excluded- Datasets that have been verified, but are not published and have been excluded by the DAP Data Manager. Error - Supported spatial dataset types that exhibit errors during the verification process will appear in the Errors tab. By default, datasets are sorted by the date in the Modified column. The List of Datasets can be re-sorted in ascending or descending order by clicking on the field header. Even the Selection is sortable by clicking next to the Select All checkbox. Each tab reports a number of datasets in the tab name. Within each tab, only lists up to 500 datasets can be displayed. The Number of Datasets in the list can be changed by the DAP Data Manager with the Number of Datasets selection. If more than 500 datasets are displayed, a grouped dataset is displayed. Fewer datasets can be displayed by using the Search options. This is described below in the Search and Advanced Search sections. Search The Search tools are used to filter the List of Datasets to a smaller subset of the DAP Catalog. A Google-like search option searches the dataset name. The Search by dataset name option above the List of Datasets provides an easy way to find a specific dataset that requires modifications to dataset properties or status. The Search by dataset name box allows a free text search of all dataset names. The dataset name as set in the metadata may be different from the physical file name. To search, simply enter the text and click on the button. Wildcards are not required. A search for "bath" will return all datasets with "bath" anywhere in the dataset name. Wildcard characters are not supported. The counts for the full List of Datasets and for each tab will be updated. Geosoft DAP Manual 59

69 Chapter 9 Search Use the Clear Search button to show all datasets. This will remove criteria in the Search by dataset name field and the Advanced Search options. Advanced Search In addition to searching by Dataset name, several other options for identifying datasets for selection are available in the Advanced Search options, including: Date - Search by modified date for recently uploaded datasets, or datasets modified within a specific date range. The Modified date will be updated if all or one of the files in the dataset are replaced or if the preview image is updated. In the case of dataset connectors, the Modified date also reflects when the dataset is refreshed from the data source. Spatial Dataset Type - Default supported spatial dataset types and custom added document dataset types are listed here. Use Ctrl to select and de-select items. Security group - Datasets can be identified according to what Security groups have permissions to those datasets. Changes can be easily made and published. Hierarchy Levels - Using hierarchy levels allows datasets to be identified according to the dataset organization presented in a DAP client. Whether using User Specified Hierarchy or Metadata Hierarchy, these selections allow the DAP Data Manager to identify all datasets that appear to the end user in a given folder structure. These options are also useful for a batch exclude action. The Hierarchy search filters tags according to the hierarchy associations. For example, if there is a Level 1 hierarchy for Canada, Nebraska will not appear in the Level 2 list of available selections. 60 Geosoft DAP Manual

70 Dataset Properties Chapter 9 Use the Clear All button to remove all search filters. This will remove criteria in the Search by dataset name field and the Advanced Search options. Dataset Properties The default property settings for a selected dataset can be viewed and modified in the Dataset Properties area to the right of the List of Datasets. Select a dataset by clicking on the selection box on the left side of the List of Datasets. Select multiple datasets in the same way. To unselect, click the selection box again. Geosoft DAP Manual 61

71 Chapter 9 Dataset Properties General The General properties (Name, Size, Loaded, Modified, and Status) are presented as read only. Name: This is the Name of the dataset from the dataset or from the metadata, if applicable. Size: The size of the dataset including associated files. Loaded: The date and time that the dataset was uploaded to the Managed Exploration Information Repository. Modified: Date and time a dataset was modified. Datasets are modified if part of the dataset is replaced. Status: Status may be Verified, Published, Excluded, or Error. If multiple datasets are selected in the List of Datasets, the General area will include a count of the number of datasets in the multiple selection. Other Dataset Properties will be populated depending on the common properties of the datasets that are selected. The Size uses the list of associated files to calculate the size. However, it does not examine and include datasets for all the data connections. 62 Geosoft DAP Manual

72 Dataset Properties Chapter 9 If more than 500 datasets are listed in any tab, a single record representing all datasets will be displayed. Selecting this record is the same as selecting multiple items. The Copy Managed Path button can be used to reference the physical location of the dataset in the Managed Exploration Data Repository. This is useful if the dataset needs to be added to an Esri Map Service. Advanced The Advanced section includes Qualifier, Hierarchy, and Disclaimer settings. Qualifier: Some datasets have a Qualifier that is related to the dataset type. The grid and picture types include a qualifier that tells DAP which DAT interface to use to read that data. On occasion, this may be modified for certain circumstances. Files of certain types accept a text qualifier that further defines characteristics for connecting to and using these datasets. The use of qualifiers depends on the file type and on how Geosoft works with that file type. Grid and image files use qualifiers to define the format of the grid or image file, which can be different than implied by the actual file extension. For example, white colour in a TIFF file is interpreted as a blank, and would appear transparent when visualized through DAP. If you would like a different colour to be nulled, you can use qualifier TIFF;dummy=0,0,0, which will make the transparent colour black (dummy=red,green,blue, each in the range 0 to 255). Convert to Document: In DAP 12.1, spatial dataset types have an option to Convert to Document. Geosoft DAP Manual 63

73 Chapter 9 Dataset Properties The Type will continue to display the original dataset type, but the icon will appear as the document type. The inherent coordinate system, if one exists, will not apply to the new document status, but the extents specified in the metadata will be used. This functionality is useful for publishing images, such as photos, that are not georeferenced, have local coordinate systems and fail verification. The dataset can also be reverted back to its original dataset type. Hierarchy: If the Hierarchy Setting is User specified, then the presentation hierarchy that is presented through DAP clients is shown here. If the hierarchy path is too long for the screen, the DAP Data Manager can preview the full path via a tool tip. Click Edit to review or modify the hierarchy values. If multiple datasets with common values are selected then the hierarchy for all selected datasets can be viewed or modified. 64 Geosoft DAP Manual

74 Dataset Properties Chapter 9 If Hierarchy is set to come From metadata, then the hierarchy cannot be viewed or edited here. Disclaimer: A disclaimer or copyright notice that users can review through DAP clients and must acknowledge if retrieving a dataset, can be set for a single dataset or multiple datasets. Selecting (Use default) will apply the Disclaimer that is selected in the Settings. The disclaimer html file can also be previewed using the Preview button. The Disclaimer option enables you to attach a copyright or disclaimer to a dataset or a selection of datasets. The DAP Administrator installation creates a folder named disclaimer in the root folder of the Managed Exploration Information Repository. The disclaimer folder includes a sample copyright/disclaimer file (default_disclaimer.html) in HTML format. You can create your own copyright/disclaimer HTML documents and upload them into the disclaimer folder via the DAP Administrator Settings. HTML disclaimer files are added to the Disclaimer file dropdown list on the Dataset Properties on the Home page, along with the option for None where no disclaimer is applied. DAP Client plug-ins in Oasis montaj, ArcMap and MapInfo display the copyright/disclaimer information associated with the dataset to be downloaded. However, older DAP client plug-ins ignore the disclaimer documents. If multiple datasets are selected, common Advanced properties will be displayed. Properties that are not common to the selected datasets will be blank. Metadata The Metadata section enables you to select a metadata stylesheet to be applied to a single dataset or a selection of datasets. Geosoft DAP Manual 65

75 Chapter 9 Dataset Properties Stylesheet: The stylesheet that will be used to display the XML metadata through DAP clients is selected here. Selecting (Use default) will apply the Disclaimer that is selected in the Settings. The metadata can also be previewed using the selected stylesheet using the Preview button. The Edit option is only available when a Geosoft Metadata Editor has been configured. Image Preview The Image Preview section is available for file datasets. Click Preview to see the snapshot image that will be presented to users via DAP client applications. Rendering attributes are available for HXYZ (point with symbol, size and colour) and GDB (line with size and colour, or point with symbol, size and colour). 66 Geosoft DAP Manual

76 Security Chapter 9 Set Redirect allows the DAP Data Manager to specify another dataset with the same hierarchy that will be used as the preview image for a Published dataset. The dataset that is going to be used as a redirect image must pass the verification process. The status of the redirect dataset can be Verified, Published, or Excluded. Set Coordinates is used to set the extents for document dataset types. Security The Security section enables the DAP Data Manager to set the security permissions for a single dataset or selection of datasets. Geosoft DAP Manual 67

77 Chapter 9 Updating the DAP Server Catalog The DAP Data Manager can create DAP Security Groups including user and group accounts from the Microsoft Windows domain in the Settings page. It is highly recommended that security be managed on a group membership basis, rather than by individual user accounts, to simplify the maintenance of dataset permissions. Use the Settings Security options to create a new security group to be added to the DAP Security Groups window. There are now two options when editing security: Set Security - appends additional security groups to the security groups that are already set on the dataset(s). Clear Security - removes all security groups from the datasets so that you can have a clean slate and add a new group or group(s). When changes are made to the existing security levels for one or more datasets, the DAP Server must be updated for the changes to take effect. Updating the DAP Server Catalog On startup, the DAP Server will read the DAP Catalog SQL Server database and create a cache or index. Before logging out of the DAP Administrator web application, or as needed, the green Update DAP Server button will reload the DAP Catalog SQL Server database changes to the DAP Server. The DAP Data Manager will be reminded to perform this action if they logout. The DAP Server will take ~ one minute to re-generate the DAP Server catalog cache. The datasetinformation.cache and spatialimages.cache (not the DAP Server 11.2 geosoft_obj_database file) are stored in the Storage folder. 68 Geosoft DAP Manual

78 Publishing and Excluding Datasets Chapter 9 Publishing and Excluding Datasets Using the Publish and Exclude buttons at the top of the Dataset Properties, recently verified datasets can be Published or Excluded, published datasets can be Excluded, and excluded dataset can be Published. Excluding Datasets The Exclude option enables you to exclude selected data from future publishing or if the data is already published, it will be removed from the DAP Server. Only the catalog entries are removed. The actual data files are not deleted, and can be re-published. To Exclude datasets from the DAP Catalog: 1. Select the dataset(s) in the List of Datasets and then in the Dataset Properties, click Exclude. The dataset status is changed to Excluded and the dataset will appear in the Excluded tab. It will be removed from the catalog, or ignored, the next time the DAP Server is updated. Publishing Datasets Before publishing datasets, it is expected that the Dataset Properties will be reviewed and modified as required. The Dataset Properties includes areas for General, Advanced, Metadata, Image Preview, and Security. To publish a dataset: 1. Select the dataset(s) in the List of Datasets. 2. In the Dataset Properties, click Publish. The dataset status is changed to Published and the dataset will appear in the Published tab. It will be added, or updated, the next time the DAP Server is updated. Updating the DAP Server Once data files and connectors have been prepared and placed in the appropriate directories, they need to be published. The user should trigger the Update DAP Server action to make published datasets visible in the DAP clients. If the item has not been published, or if it needs to be updated, the DAP Administrator adds the item to the DAP Server index. If the item has already been published, the DAP Server does a series of checks to see if this item needs to be updated. If the item is a connector, the DAP Server re-catalogs the item according to the connection rules (see description per connector type). If the item has been Excluded, it is ignored. Once the updating process is complete, the DAP Server is notified that the catalog has been updated, and data clients will now see the new catalog. Geosoft DAP Manual 69

79 Chapter 9 Setting the Coordinate System of Document Dataset Types Setting the Coordinate System of Document Dataset Types The Set Coordinates options provide functionality to assign a coordinate system and extents to document datasets. This tool cannot be applied to grid or image dataset types in DAP To set the coordinate system for datasets: 1. Select a dataset(s) in the List of Datasets. 2. In the Image Preview section, click Set Coordinates. The Set Coordinate System dialog will be displayed. This dialog provides two methods to set coordinate system parameters and extents either manually by entering the parameters or by copying the parameters from an existing dataset. 3. Click Copy from to define the coordinate system and extents from an existing dataset when possible. If manual entry is necessary, first define the type of coordinate system, Geographic (long, lat) or Projected (x,y). Unit and Projection method are disabled when the Geographic coordinate system is selected. 70 Geosoft DAP Manual

80 Errors Chapter 9 4. Using the dropdown lists, select Unit, Datum and Projection method (required for the Projected coordinate system) and Local Datum (optional). 5. Specify the Minimum and Maximum X and Y Extents. 6. Click OK to apply the coordinate system and extents to the selected datasets. Errors Datasets that fail the verification process are listed in the Error tab. The Dataset Properties area displays a message related to the cause of the error. The DAP Data Manager can correct datasets with errors using Delete, Download, and Replace options. Delete: The delete button deletes the dataset and all related information from the DAP Catalog SQL Server database and the DAP Data Folder. A confirmation message will appear. Multiple datasets can be selected in any tab (All, Verified, Published, or Excluded) and deleted. When many datasets are selected, the delete task may take several minutes. Download: The Download button will create a zip file of a complete dataset for downloading to the DAP Data Manager's local computer. The dataset can then be opened in an application such as Oasis montaj or ArcGIS, and modified to rectify the error. Replace: The Replace button allows the replacement of a dataset or associated file with a new file that has been uploaded to the "replacement" folder in the DAP Data Folder. A DAP Data Manager may decide to download a dataset for modification and then replace it, or delete and re-upload the entire dataset as a new record. After a dataset is repaired, it may take several minutes for the changes to be observed in the DAP Administrator web application as the repaired dataset is verified. Geosoft DAP Manual 71

81 Chapter 10: Creating Data Source Connectors Some datasets, such as those from acquire or RDBMS databases, are created with the use of a Connector. A Connector is a file that provides the connection information that enables DAP to connect to an external data source, or perform special actions as part of the publishing process. Four types of Connectors can be added: acquire - For a connection to an acquire database, including Project and Prospect information if desired, using the acquire Direct API. acquire Selection - For a connection to a point or collar dataset defined by an acquire Selection file. RDBMS - For a generic connection to a table or view in a relational database, including Oracle databases. Esri Map Service - For a connection to an ArcGIS Server Map Service. Connectors can be added from below the List of Datasets on the Home page, except when viewing the Error tab. Click the Add Connector button to select one of these connection types: For more information on dataset types, See "Supported Dataset Types" on page 92. Creating an acquire Connection You can create acquire connection files in your DAP Data folder. Depending on the data to be published, and on the interfaces required to extract this data, there are two methods for connecting to and publishing data in your acquire databases: 1. Using acquire connections for all dataset types including drillhole collar and surface sample data organized into logical project or prospect directories This method provides high-level acquire API access to the data from acquire-enabled applications, such as Geosoft Target or Target for ArcGIS. 2. Using acquire connections for drillhole collar and surface sample data published in a widely

82 Chapter 10 Creating an acquire Connection accessible point format using pre-configured acquire Selection Files (.sel) This method provides a much simpler interface to the point data (including collar locations), enabling access from any DAP client, including Oasis montaj, ArcGIS, and MapInfo. acquire connectors use an ODBC DSN to connect to the database. The DSN must be a System DSN. Both Windows authentication and SQL authentication are supported. Windows authentication uses the user account that the Geosoft DAP Administrator Portal service is running under. The IDAP account also requires permissions on the database for data extraction from DAP clients using the acquire Direct API. Creating an acquire Connector The acquire database connector provides high-level access to all drillhole and campaign data from acquire-enabled applications such as Geosoft Target or Target for ArcGIS. To create an acquire Connector: 1. From below the List of Datasets on the Home page, click the Add Connector button. 2. Select acquire from the Add Connector menu. The Add acquire Connector dialog is displayed. 3. In the Dataset name field, type the names to appear in the DAP client for your data users. Enter the required values for the acquire Connection Settings including the DSN from the server that is hosting the DAP Administrator application, and the User name and Password in the acquire SQL Server database. 73 Geosoft DAP Manual

83 Creating an acquire Connection Chapter 10 Select the acquire Display Preferences as required. User name, Password, and Display Preferences can be modified by editing the connector. Dataset name cannot be modified. To change the Dataset Name, create a new connector, or edit the metadata Dataset Title. 4. Click Add and the acquire database connection will be created and verified. Once the connector is verified, it will appear in the Verified tab. Modify the Dataset Properties, including Hierarchy, Disclaimer, Metadata, and Stylesheet options. You can then publish the dataset. The acquire datasets will be visible to your DAP clients through a point dataset type. Bounding boxes representing the datasets defined in the Display Preferences can be previewed in the DAP client. Users that select these datasets will use the acquire Direct API to extract the data directly from the acquire database. The bounding boxes can be updated as more data is added to the project in acquire. Creating an acquire Selection Connector DAP can be used to extract both drillhole collar and surface sample data stored in an acquire database to any DAP client where the users cannot or do not need to access the full acquire Direct API. The key to this process is the acquire Selection (*.SEL) file, which enables DAP Data Managers to define the required fields and data for each point dataset. To create an acquire Selection Connector for drillhole collar and point campaign surface data: 1. From below the List of Datasets on the Home page, click the Add Connector button. 2. Select acquire Selection from the Add Connector menu. The Add acquire Selection Connector dialog is displayed. Geosoft DAP Manual 74

84 Chapter 10 Creating an acquire Connection 3. In the Dataset name field, type the name to appear in the DAP client for your data users. Enter the required values for the acquire Connection Settings including the DSN from the server that is hosting the DAP Administrator application, and the User name and Password in the acquire SQL Server database. User name and Password can be modified by editing the connector. Dataset name cannot be modified. To change the Dataset Name, create a new connector, or edit the metadata Dataset Title. 4. Select Point display from drillhole collar or Point display from surface sample, depending on the type of acquire Selection (*.SEL) file that is being used. 5. Browse for the Selection file on your local machine. 6. Click Add and the acquire database connection will be created and verified. Once the connector is verified, it will appear in the Verified tab. Modify the Dataset Properties, including Hierarchy, Disclaimer, Metadata, and Stylesheet options. You can then publish the dataset. The acquire point dataset will be visible to your DAP clients through as a point dataset type. You can edit the connection information contained in point datasets via the Edit button in the Dataset Properties panel for each dataset. Points can be previewed in the DAP Administrator web application and will be available in DAP clients as well. 75 Geosoft DAP Manual

85 Creating an RDBMS Connector Chapter 10 DAP Administrator caches the data as a Geosoft HXYZ file. The connector should be updated as more samples or holes are added to the selected projects in acquire, either manually using the Update Connector button, or regularly using the Update connector automatically option. Creating an RDBMS Connector RDBMS (Relational Database Management System) Connector publishes point data stored in relational databases using ODBC (Open DataBase Connectivity) DSN (Data Source Name) connections. The use of DSN connections enables publishing of point data from relational databases. The RDBMS Connector has been tested with Access, SQL Server, and Oracle. Point data must be from a database table or a SQL view which contains X, Y (and optionally Z) columns. Data in X and Y columns must be in a single geographic or projected coordinate system. The connector uses an ODBC DSN to connect to the database. The DSN must be a System DSN. For connections to a SQL databsae, both Windows authentication and SQL Server authentication are supported. Windows authentication uses the user account that the DAP Administrator service is running under. For MS Access databases, user name and password are not required as MS Access databases do not need them. Oracle does not support Windows authentication - this connector uses a Username and Password. Geosoft DAP Manual 76

86 Chapter 10 Creating an RDBMS Connector To Create an RDBMS Connector: 1. From below the List of Datasets on the Home page, click the Add Connector button. 2. Select RDBMS from the Add Connector menu. 3. The Add RDBMS Connector dialog is displayed. 4. Enter a Dataset name to represent the point data in the RDBMS database. This is the name that will be displayed in the DAP client interface. 5. In Database Settings, select a DSN Name. The DSN list provides all the System DSNs on the computer running DAP Administrator web application. 6. Select a Table or SQL View from the connected database. Move fields to be published from the Available Columns list to the Selected Columns list. Selected Columns can also be re-ordered. 7. In the X, Y, Z columns fields, select X, Y and Z columns from the list of columns chosen above. (Z column is optional.) 8. In the Coordinate system section, select the coordinate system appropriate for the data in the X 77 Geosoft DAP Manual

87 Creating an Esri Map Service Connector Chapter 10 and Y columns. 9. Click Add and the RDBMS connector will be created and verified. User name, Password, Table, columns and column order, and coordinate system can all be modified by editing the connector. Dataset name cannot be modified. To change the Dataset Name, create a new connector, or edit the metadata Dataset Title. DAP Administrator caches the data as a Geosoft HXYZ file. The connector should be updated when the content of the database changes, either manually using the Update Connector button, or regularly using the Update connector automatically option. See Updating Connectors for details. Creating an Esri Map Service Connector To publish Esri Map Services, the DAP Server requires an Esri License component. The Esri Map Service connector contains the parameters for connecting to the ArcGIS Server and the Map Service. To Create an Esri Map Service Connector: 1. From below the List of Datasets on the Home page, click the Add Connector button. 2. Select Esri Map Service from the Add Connector menu. 3. The Add Esri Map Service Connector dialog is displayed. 4. In the Dataset name field specify the name of the connector to create. This is also the name of the dataset shown in DAP client interfaces. 5. In the Server box specify the name of the ArcGIS Server computer or IP address. 6. Click Retrieve List to see a list of Map Services hosted by the ArcGIS Server. Select the name of the Map Service that you would like to publish. 7. Click Add to create the connector. Support of Esri Map Services by DAP Client Applications Esri Server Map Services - after being published through a DAP Server - can be searched, viewed and downloaded in all DAP client interfaces. The native data published by an ArcGIS Server Map Service is not downloadable; instead, a raster image showing the presentation of the data is extracted and saved to DAP client computers. The raster image is normally a GeoTIFF, and can be reprojected, reformatted and resampled. Preview of an Esri Map Service is done on-the-fly by the DAP Server with the ArcGIS Server. Geosoft DAP Manual 78

88 Chapter 10 Updating Connectors Updating Connectors Connectors, especially connectors that cache point data, need to be updated as more data are added to the external data sources. This can be done in two ways. 1. Manually as required, using the Update Connector button in the Dataset Properties panel. 2. Regularly using the Update connector automatically option in the Dataset Properties panel according to the update frequency (daily or weekly) specified in Settings page under Dataset Types. 79 Geosoft DAP Manual

89 Chapter 11: Advanced Reporting Functions Creating DAP Server Usage Reports A variety of DAP Server usage reports can be viewed in the Reports page of the DAP Administrator web application. A collection of reports is provided including reports on uploaded data and download activity: Recent Activities - Loaded datasets are reported by last 60 days, 30 days, last week and current day Dataset Status Summary - Datasets are reported by status and count Spatial Dataset Type Summary - Datasets are reported by type and count Documents without Specified Extents - All documents with global extents (without specified extents) are listed Download Summary by Datasets - Downloaded datasets are reported by spatial dataset type Download Summary by User - Downloaded datasets are reported by "who downloaded" Extraction Profile - Downloaded datasets are displayed as a profile based on extraction date Request Type Summary - Summary of server requests types Request Profile - Requests on datasets are displayed as a profile To create a DAP Server report: 1. In the DAP Administrator web application, select the Reports page. 2. From the Reports dropdown list, select the required report.

90 Chapter 11 Creating DAP Server Usage Reports 3. From the Date Range dropdown list, select the required timeframe. 4. The requested report is generated and displayed. 81 Geosoft DAP Manual

91 Creating an Index Map Chapter If needed, export a CSV of the report details. The DAP Administrator 11.2 capability to create an interactive report for files that are in the data folders but have not been cataloged, has been replaced by the Verify tab in the List of Datasets. The DAP Data Manager can publish selected datasets directly from the Verify tab. DAP Server 12.1 log files are unchanged from DAP Creating an Index Map An index map is a query-able set of survey or dataset outlines with attributes. This function will create a shapefile of the selected datasets in the List of Datasets, as filtered by the Search options. 1. Use the Advanced Search to specify a subset of datasets. 2. Select the datasets to be included in the Index Map. 3. Click Index Map. 4. Specify a local location to save the shapefile. Geosoft DAP Manual 82

92 Chapter 11 Creating a DAP Administrator Data Package The Index Map shapefile includes a polygon of the dataset bounding box and attributes defined by the metadata fields specified as part of the Structured Metadata Query. The creation of an Index Map is a DAP Administrator task that is accessible only to the DAP Data Manager. The Index Map is not available to the end users through the DAP clients unless it is published as a DAP dataset. Creating a DAP Administrator Data Package Package is a DAP Administrator tool that can be used by the DAP Data Manager to create a usable subset of the catalogued data which can be shared with a 3rd party or archived like a traditional file system. 1. Use the Advanced Search to specify the subset of datasets. 2. Select the datasets to be included in the Index Map. 3. Click Package. A separate process will create a new file named "Package_yyyy-mm-dd_#.zip" in the outgoing folder of the DAP Data folder. 83 Geosoft DAP Manual

93 Creating a DAP Administrator Data Package Chapter 11 The files in the Data Package zip file will unzip based on the presentation hierarchy that an end user of a DAP client would see. Geosoft DAP Manual 84

94 Chapter 12: Geosoft Integrated Metadata Solution Metadata is data that describes data. With the release of Oasis montaj 7.0 and Geosoft DAP 11, Geosoft introduced a fully integrated metadata solution from metadata creation to publishing. In DAP 12.1, metadata has been integrated into the DAP Catalog SQL Server database. This means that there is one metadata database per DAP Server. Metadata Best Practices Care should be taken to avoid special characters such as /, %, & and ' (single quote) in dataset names and metadata picklists. For a complete list of invalid characters, See "Configuration Limits" on page 89 The Geosoft Metadata Editor allows users to submit data and DAP Data Managers to upload datasets with the metadata in XML format. Datasets are uploaded to the folder structure in the "incoming" folder, and the DAP Administrator web application uses the incoming folders to create the hierarchy. Alternatively, the metadata can be used to determine the hierarchy as specified by the Hierarchy option in the DAP Settings. FGDC and ISO Standards Geosoft integrated metadata solution is flexible and configurable, and supports FGDC and ISO metadata standards. It can also be expanded to support the metadata and terminology that is unique to the exploration industry. Geosoft introduces their XML metadata schema in Oasis montaj. The schema is the base used to create the built-in metadata editor in Oasis montaj. Geosoft metadata schema is also extensible. Geosoft Metadata Editor includes: Support for multiple file selection; this enables users to enter copyable metadata fields for many files simultaneously. Support the newly released ISO standard and the new Geosoft metadata schema. Support the new DAP dataset types such as Esri LYR files. Simplify the process of submitting and uploading the data packages. Synchronize metadata in a SQL Server metadata database and XML files.

95 Chapter 12 Improved Visualization of Metadata Improved Visualization of Metadata Graphical viewing of metadata is enhanced with the use of stylesheets in Oasis montaj, DAP Administrator and DAP client interface. Custom stylesheets are required to view the metadata created by custom metadata editors. Geosoft Metadata Editor Metadata Schema DAP 12 introduces a change to the metadata schema. Several columns now reside in a new table called Dataset. This table name is fixed. In the Dataset table, the StatusID column cannot be null. The Metadata Editor must fill in a value in this column for each dataset. By default, the value is 7 (from the DatasetStatus table) for 'MDE Upload'. Project Package The Project Package is new in DAP 12. The purpose of the Project Package is to facilitate the upload of a project of data, such as a Geosoft Project File and associated datasets or a similar folder of data used by another data processing application. 86 Geosoft DAP Manual

96 Geosoft Metadata Editor Chapter 12 To create a project package: 1. In the Geosoft Metadata Editor, select New Project Package Select the folder of data to package. In this step, select the folder that will be zipped up and made into the project package. The project package then gets placed beside this folder. 3. Select a GeoTIFF to use as the Preview Image and to set the extents and coordinate system for the package. It is recommended that the GeoTIFF image selected is outside of the package folder. 4. Edit the metadata as required. 5. Save and submit the Project Package. Creating Project Package will create a *.geosoft_project_zip file. This can be uploaded to the DAP Server and will be published like a document dataset type with a preview image and the extents defined by that image. Geosoft DAP Manual 87

97 Chapter 12 Geosoft Metadata Editor Integrating a Geosoft Metadata Editor into the DAP Administrator web application The Geosoft Metadata Editor can be integrated into the DAP Administrator web application. This allows metadata to be directly edited and updated through the DAP Administrator web application. 88 Geosoft DAP Manual

98 Appendix 1: DAP Limits DAP limits are provided to assist you when installing, setting up and running the Geosoft DAP Server and DAP Administrator. Unless otherwise stated, these are maximum limits and should always be maintained. Configuration Limits Invalid Characters \ / : *? < > Invalid characters are not permitted in any folder or file name in the DAP system. Name Maximum 64 Characters Purpose Maximum 1024 Characters (only available when editing the ois.xml file) Admin Password Maximum 16 Characters Admin Name Maximum 64 Characters Admin Number Maximum 32 Characters Admin Maximum 64 Characters Number of Services (Meta, Extract, Image, Catalog) Maximum 16 Service Name Maximum 32 Characters Service URL Maximum 256 Characters Number of Plugins Maximum 16 DAP plugins enable 3 rd party companies to write a set of DLLs to catalog and publish data sources/types that are not supported by the core DAP technology. In total, up to 16 custom plugins are supported by a DAP server. Plugin Namespace Maximum 32 Characters DAP Login Limits User Name Maximum 64 Characters User Password Maximum 64 Characters Domain Maximum 256 Characters

99 Appendix 1 DAP Administrator Configurable Limits DAP Administrator Configurable Limits Number of datasets in the List of Datasets 500 (configurable) Incoming queue delay 5 minutes (configurable) Catalog Limits Number of DAP groups Maximum 64 Number of snapshots Maximum 6 Number of large datasets Maximum 65,536 To determine if a dataset is considered large, the DAP Administrator applies two criteria; spatial extent and image density. To apply these criteria, the DAP Administrator program first renders the dataset as an image of 128 rows * 256 columns. Then, the first criteria - spatial extent - requires that the dataset has a spatial extent that is over 8 degrees in longitude or latitude. If the dataset does meet these criteria, then it is considered a large dataset; if it does not meet the first criteria, then the second criteria - image density - is applied. If less than 95% of the pixels in the rendered image has a value (not dummy), then this is considered a large dataset. Examples of large datasets are global coastlines and global DEM. Area of interest (AOI) search uses dataset extents only for small datasets. For large dataset, AOI search first checks for dataset extents and then pixel values in the image file. Number of hierarchy depth Maximum 256 This number refers to the number of folder levels, including virtual folders, that are allowed in a DAP catalog. However, we recommend no more than 5 or 6 levels of subfolders. Catalog results Maximum 5000 This is the maximum number of datasets returned from a DAP search. DAP returns the datasets in a folder that is clicked in a DAP client application, and does not include any datasets outside of the folder. Hence, this limit is physically the maximum number of datasets in a Windows file folder. This is a reasonable limit and balance between users data and DAP performance. For example, a folder with 5000 DAP datasets could have, depending on the data file types, up to 20,000 files. Extraction Limits Number of extraction threads Maximum 128 Number of extractions remembered in history Maximum 1024 Number of hours extraction history saved Maximum 24 hours Size of Extraction memory Maximum 512 MB Minimum image size Width > 10 and Height > Geosoft DAP Manual

100 Render Limits Appendix 1 No data is returned if the raster image is less than 10 * 10 (in pixels). Minimum ECW size Width > 128 and Height > 128 This depends on whether ECW license is enabled on the DAP Server. Re-project memory Maximum 128 MB Render Limits Number of datasets to render in one request Maximum 32 This refers to the number of datasets that will be rendered for previewing in a browser map Disclaimer Limits Number of datasets to return disclaimers for Maximum 32 This is more a limitation in DAP client API. No direct impact to end users. Geosoft DAP Manual 91

101 Appendix 2: Supported Dataset Types The following table summarizes all the supported dataset types and the DAP Server and DAP client features available for each type. Dataset Type Search, View Metadata, Preview Data Extract Data Download Window Reformat Resample Reproject Grid files, which include all grid types supported by Geosoft Common image files Documents (files) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No ECW images Yes Yes Yes Yes Yes Yes Geosoft MAPs Geosoft GDB databases Geosoft HyperGrids Geosoft HyperXYZs Geosoft HyperMAPs Yes Yes Yes No No Yes Yes Yes 1 Yes 1 No No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Voxels Yes Yes 2 Yes No Yes Yes

102 Appendix 2 Supported File Types Grids/images (Section) MapInfo TAB and MIF files Esri Shape files Esri LYR files ArcGIS Map Services RDBMS Connector Yes Yes Yes Yes Yes No Yes Yes Yes Yes No Yes Yes Yes Yes Yes No Yes Yes Yes 1,2,4 Yes Yes No Yes Yes Yes 1,3,4 Yes Yes Yes Yes Yes Yes Yes Yes No Yes acquire data Yes Yes 1,2 Yes Yes No Yes acquire point Yes Yes Yes Yes No Yes Notes: 1 Not supported in Flamingo and DAP XML 2 Not supported by MapInfo DAP client tool 3 Image only 4 Supported by Seeker client tool only. Flamingo and GeoDAP not supported Supported File Types The following table lists the supported file types, along with the catalog characteristics for each type: Grid files, which include all grid types supported by Geosoft Common Image Files Document files Grid files contain gridded data, in whatever format Geosoft supports. The Qualifier field must be used to specify any grid types other than Geosoft-format grids. Picture files include most image format files that display as a picture (such as ECW, JPG, BMP, etc). Such files normally require specification of a qualifier that tells DAP exactly which format converter to use when it works with the file. The qualifier table that follows documents recognizes qualifiers. Documents are files of any type that you would like to publish and expose through DAP. Documents can have metadata, and they can be geographically located by defining a location in the metadata. However, DAP has no knowledge of a document s content or format. When a document is requested by a DAP data client, the entire file is transferred to the requesting client. DAP compresses files as they are streamed over the network. Documents that you 93 Geosoft DAP Manual

103 Supported File Types Appendix 2 know are already compressed in their native formats, such as PDF documents, should have the Compressed qualifier added. This will save DAP the unnecessary effort of compressing the data in the transfer stream. ECW images Geosoft MAPs Geosoft GDB databases Geosoft HyperGrid Geosoft HyperXYZ Geosoft HyperMap Voxels Grid/Images (Sections) MapInfo TAB and MIF files Esri Shape files ECW (Enhanced Compression Wavelet) is an open standard wavelet compression image format developed by Earth Resource Mapping. The file format is optimized for aerial and satellite imagery, and efficiently compresses very large images with fine, alternating contrast. A Geosoft map can contain many views and groups. Normally a map has a base view and data view. The coordinate system and extent of the data view is the coordinate system and extent of the map. Geosoft GDB files are Geosoft databases that may contain point or line data for extremely large datasets (10s or even 100s of gigabytes). You typically pare down raw survey datasets to contain only the fields and columns that you wish to publish. DAP can optimally extract and window such large datasets. HyperGrids are optimized grid files created from any Geosoft-supported grid or image files. You use a HyperGrid when you have very large grid or image files that are frequently accessed, and are expected to be windowed and re-sampled when extracted. HyperGrids are naturally de-aliased, so that they appear correctly at any scale and resolution, and provide the fastest possible DAP extraction and viewing performance. HyperXYZs are optimized tables of located data values and attributes for very large datasets that are expected to be windowed when extracted. These are ideal for regional datasets of point locations, such as regional geochemistry datasets, or regional gravity datasets. HyperMaps are optimized vector map drawings created from a Geosoft map group. They are intended for very large and frequently accessed vector datasets to be extracted at a variety of scales and windowed to smaller areas. HyperMaps are naturally de-aliased, and provide optimum DAP performance in these cases. A regional, but detailed drainage map is a good example of a vector layer that is ideal for a HyperMap. Voxels are 3D grids typically used to represent rock properties or physical parameters in a volume. DAP 12.1 introduces the ability to catalog oriented grids and raster images (section grids/images). A section grid may be a grid (GRD) or image (TIF, JPG, etc). MapInfo TAB files contain vector data or point to raster images. Vector MapInfo TAB files contain rendering information. Esri Shape files contain vector data: points, lines and polygons. Shape files do not contain symbology for rendering the vectors. Coordinate systems of Shape files are saved in PRJ files. Each PRJ file contains an Esri projection string. You use the GIS legend editor in Oasis montaj to create GIS file legends. Geosoft DAP Manual 94

104 Appendix 2 Associated File Extensions Esri LYR files ArcGIS Map Services Connector RDBMS Data Connector acquire data acquire point ArcGIS layer file (.LYR) is a binary file that depending on the types of data sources, contains the following: Pointers to data sources physical locations, Symbology, Display settings (such as transparency), Scale dependent display properties, Joined table/related table information, Definition query, Labeling properties for feature layers, and Annotation display properties for annotation layers. ArcGIS Map Services Connector provides a dynamic connection to a GIS Map Service to display data stored in ArcGIS Server The Relational Database Management System (RDBMS) Data Connector catalogs and publishes point data in relational databases using ODBC DSN connections. acquiretables are connectors to acquire databases. These connectors expose the full acquire API to data clients that support acquire directly. These connectors are intended for advanced acquire data users utilizing acquire-based applications. They enable any acquire data consumer connected over the network to efficiently access acquire data without the need for a direct ODBC connection. acquire databases can be exposed as simple point/attribute tables, which are defined by creating point acquire selection files. Point connectors can be used by any data consumer that can work with point data, such as GIS applications. Associated File Extensions Certain file types can represent a group of files, each with the same name as the primary file but with a different extension. For example, Esri Shapefile data come in a set of files that relate to the primary file with extension.shp. Associated Directory Extensions Some file types may have an associated directory or folder that is used to hold associated files. In some cases, DAP Administrator creates a.cache folder that is used to maintain cached copies of certain parts of the data in order to enhance the DAP performance. Associated folders must be located in a sub-folder accessed from the same location as the data file. The associated directory must have the same name as the data file. Multiple Associated Directories should be entered as a ";" separated string (DAP Portal). Retrieve extracts the dataset as a.zip containing the dataset files (catalogued) and associated directory (directories). Voxels Voxels represent volumes of the earth. They use a three-dimensional grid structure stored in a Geosoft Voxel file. In order to share voxel model data using DAP, voxel must be converted to the Geosoft voxel format, georeferenced to real-world coordinates, and displayed in Oasis montaj to assign default viewing characteristics to the voxel. To create a Geosoft voxel file in Oasis montaj, you select the Copy or Convert option from the Voxel menu. 95 Geosoft DAP Manual

105 GIS Data Files Appendix 2 Currently, Oasis montaj enables you to create voxels from files of GoCAD, UBC, Datamine, Geosoft GDB, and ASCII XYZ formats. When converting Geosoft GDB and XYZ data, the data must be already organized in a regular X,Y,Z mesh (just as it would be if exported from a voxel to these formats). Oasis montaj also enables you to create voxels by gridding 3D data stored in Geosoft GDB files. Georeference Voxel File In many of the above formats, voxel data is typically not georeferenced. More commonly, voxel models are defined in a local coordinate system, which is tied to a true projected coordinate system at some location on Earth. Before a voxel can be cataloged by DAP, it must be georeferenced to a projected coordinate system. To georeference a voxel, you must know: Reference datum and coordinate system Location of the top or bottom X,Y origin of the voxel model in the reference system Orientation of the voxel relative to the X, Y, and Z axes of the reference coordinate system To georeference a voxel: 1. In Oasis montaj, from the Voxel menu, select Voxel Grid Info. Basic information about the voxel is displayed. 2. Click Modify. 3. Enter the details in the displayed dialog. 4. To view descriptions of the various parameters, click Help. Notes: Geographic (Latitude, Longitude) coordinate systems are not supported for voxels. The voxel must be defined in real length units relative to a known or definable projected coordinate system, such as UTM. Non-uniform point separations in a voxel are supported, and can be defined by listing the point separations along each axis. For details, see the Oasis montaj Help system. When voxels are windowed and transferred to a data client over DAP, the voxels are located in the target projected coordinate system by locating the origin defined in the georeference information, re-projecting this to the target coordinate system, and correcting for any rotational difference between the original and target systems. This means that any small distortions due to scale differences, and the differences in projection method, are lost. Typically, this is not an issue on the scale used for most voxels, but it does imply that voxel consumers would get the most accurate georeference results if they use the voxels in the same coordinate system as they are defined. GIS Data Files DAP can catalog GIS data contained in Esri LYR files, ArcGIS Map Services, MapInfo TAB files (and associated file sets) and Esri Shape files (and associated file sets). Geosoft DAP Manual 96

106 Appendix 2 Documents Esri shape files do not contain any rendering information. Therefore, a secondary file is required in order to properly display the features within a shape file. We highly recommend using Esri LYR files, to define the rendering attributes of SHP files. However, as an alternative, Geosoft has created the geosoft_ legend file to store all the rendering information for a shape file, so that it can be identically displayed in Oasis montaj, ArcMAP, and MapInfo. The process of cataloging TAB and SHP files is the same as that for cataloging other dataset types. You must first place the data (including all associated files) in a directory in the DAP data tree. However, before the data can be published, you can create a legend for displaying the data. This can be done using Esri LYR files or alternatively using the GIS Legend Editor, which is accessible from the DAP Prep menu in Oasis montaj. The Legend Editor enables you to create a display legend that controls all display attributes, which can be defined based on tables of actual GIS data contained in the files, or attribute fields found in the GIS data, or set to constants. For MapInfo TAB files, the GIS data already contains rendering information, and a default legend is automatically created when the data is verified. However, the legend uses the field lookup technique and all the drawing attribute information is placed in separate fields of the attribute database. This technique does not utilize the ability of a legend to use a table lookup based on the value of a particular attribute. For example, a geological map would contain many polygons and an attribute table that indicates the rock name (such as Granite or Felsic volcanic ). In the field lookup method, each Granite polygon will have a Colour field that might be R128G64B64 for pink. Using a table lookup, you can construct a table that simply lists Granite and the colour pink so that all polygons with the Granite rock type will be coloured pink. Esri shape files, on the other hand, contain no rendering information at all and, if published without a legend, all entities would appear in black in Oasis montaj or some default rendering color in ArcMap. Legends for shape files are created with the use of GIS Legend Editor. For many GIS dataset types, you would want to create tables that control the way the GIS data is displayed. The preview display of shapefiles has been improved with the release of 11.2, which includes improvements for the default preview rendering of vector data. Specifically, hypermaps are created automatically in the DAP catalog and used for rendering shapefiles. This means that the shapefile will appear crisp, not blurry, when viewed in the DAP data access tools including: Seeker and via web clients. Documents Documents are files of any type that you want to make available for distribution in their native format. DAP does not need to know the file format it simply delivers the file as it is to a data client. However, DAP does need to have certain metadata to enable users to browse for the data. In particular, establishing a location or spatial extent enables the document to respond to spatial queries. Without spatial extent, the document would appear in all spatial queries. In DAP Administrator, you can add basic metadata and special information to a document. Metadata are stored in a file named after the document file with the.geosoftmeta extension. If all documents within a directory share the same spatial and contextual information, you can create a single metadata file named Common.GeosoftMeta. Any documents in the directory that do not have their own metadata will use metadata from the common metadata file. 97 Geosoft DAP Manual

107 acquire Databases Appendix 2 Documents (except MAP files) cannot be rendered in a browser. You may choose to use another file as a representative of the data for rendering purposes. For example, a survey directory may contain many documents, but all of them could be represented by a single grid or image. In this case, you may choose to use the grid file to represent visualization of the documents. acquire Databases Data clients can use Geosoft DAP to browse and extract exploration data directly from an acquire database. Many organizations store certain exploration data (typically, drilling and point geochemical data) in acquire databases. Without DAP, geoscientists would access this data by making a direct ODBC link to the data and using the acquire tools embedded in their applications. For example, an ArcGIS user might extract data directly into ArcGIS for processing with the Geosoft Target for ArcGIS system, or a mine geologist might extract data directly into MineSight for further mine planning activities. Such applications require a very high-speed connection to the database server and complex procedures used to establish and maintain direct ODBC database links on the client systems. When a DAP server is used to extract the data, only that server is directly connected to the acquire database. DAP is responsible for windowing and re-projecting the data to meet the client needs, and for passing that data to the client using the DAP high-speed compression and streaming technology. This approach simplifies the client desktop configuration and enables accessing acquire data over slower connections, such as a WAN, or remotely, using VPN over the Internet. If you have an existing acquire database hosted on Microsoft SQL Server, there are three steps required to connect and catalog the contents of the database through DAP: 1. Enable SQL Server authentication Establish a SQL Server database Login ID and Password for your database. 2. Create an ODBC system Data Source Name (DSN) on the DAP server and DAP Administrator computer. 3. Create a DAP acquire connection file in your DAP data directory tree to be used to catalog the acquire database on the DAP server. Enabling SQL Server Authentication The SQL Server Login ID and password are used to authenticate an ODBC connection to your database. The procedure used for setting up these parameters depends on your database software. We describe the procedure for Microsoft SQL Server, which is the most common technology used to host acquire databases. To set up Login ID and password for SQL Server, you must set authentication on SQL Server to support SQL Server and Windows (by default, the SQL Server installation process sets authentication to Windows only ). To enable SQL Server authentication: 1. Start SQL Server Enterprise Manager. 2. Open the Console Root tree, and select your SQL Server. 3. Select Tools SQL Server Configuration Properties. 4. If the above option is grayed out, you either have not selected the correct SQL Server, or you do Geosoft DAP Manual 98

108 Appendix 2 acquire Databases not have administrative privileges on the selected server. You must have administrative access to SQL Server with your User ID in order to proceed. The SQL Server Properties (Configure) dialog is displayed. 5. Select the Security tab. 6. From the Authentication group, select the SQL Server and Windows option button. 7. Click OK. 8. Under the SQL Server tree, select Security Logins. 9. Select Login ID sa, which is a default public login that is normally set up when SQL Server is installed. 10. If sa is not found, create a new Login ID. It should have the SQL Server Authentication selected, and you should either know the password or set a new one. Make a note of the password as you will need it in subsequent steps. 99 Geosoft DAP Manual

109 acquire Databases Appendix 2 Other users of this SQL Server may be using the sa Login ID, so you should not change the password unless you know that this will not cause problems. Creating an ODBC Connection To create an ODBC connection to an acquire server: 1. Log in to the system that hosts the DAP server with administrator privileges. 2. Launch Control Panel and select Administrative Tools. 3. Select the Data Sources (ODBC) tool to add a new System DSN. The ODBC Data Source Administrator dialog is displayed. Geosoft DAP Manual 100

110 Appendix 2 acquire Databases The connection must be a System DSN because the DAP server will access this connection using a different User ID, created specifically for the DAP server when it was installed. 5. Click Add. 6. In the next dialog, select the SQL Server driver to access your acquire database, and click on Finish. The system prompts you for a name for your data connection (this is the DSN name that you will need later), and a description. 7. Choose a meaningful name and description, and select the server computer that hosts the database. Make a note of the DSN name as you will use it in subsequent steps. 8. Click Next. The next dialog asks you how you want to authenticate the Login ID. 101 Geosoft DAP Manual

111 acquire Databases Appendix 2 9. Choose the SQL Server authentication using a login ID and password entered by the user option. 10. Enter the SQL Server Login ID and password set in the Enabling SQL Server Authentication section. The DAP server will also use these parameters to connect to your data. The DAP Server runs under its own user, and this is the only way it can connect to SQL Server. 11. Click Next. The next dialog prompts you to choose the acquire database name within SQL Server as the default database for this connection. Geosoft DAP Manual 102

112 Appendix 2 Hyper Stores 12. Select your database from the drop-down list. In the above example, the selected database is Acquire 1D. 13. Click Next and accept the defaults in the next dialog, then click Finish button to complete the connection. 14. Test your connection in the last dialog by clicking Test the data source. Your data source now appears on the System Data Sources list. 15. Repeat the above process for all acquire databases you want to make available on your DAP server. If you are managing your DAP server from a different computer on your network (which is the typical configuration), you must also establish an ODBC System DSN connection from your administration computer to the same acquire database. This connection will be used by DAP Administrator to manage the DAP catalog on the administration computer. You must use exactly the same DSN, Login ID, and password. Once the catalog is created, the DAP server will access the acquire database through its own ODBC connection. Hyper Stores You may choose to publish certain performance-sensitive data as a hyper-store, which is optimized to support high-performance windowing and extraction for very large datasets. A good example of such a dataset is the global SRTM topography data hosted on Geosoft DAP Server. This is an extremely large dataset sampled on a 3 second interval, which results in more than 60,000,000,000 points. This data is stored in the Geosoft DAP hyper-grid (hyper-store for grids and images), which makes browsing the world in the Geosoft web portal appear almost instantaneous. Geosoft DAP supports three types of hyper-stores: 103 Geosoft DAP Manual

113 Data Visualization Appendix 2 HyperGrid (HGD) Optimized read-only grid format for the Geosoft DAP servers that supports compression and extremely fast windowing and multithreading. We recommend that very large grids or images that require frequent windowing to support client requests be provided to Geosoft DAP servers in the HyperGrid format. HyperGrids can be created from single grids or images, or from a mosaic constructed from a set of grids or images. HyperXYZ (HXYZ) Optimized point-data format used to store very large table datasets, such as point geochemistry or mineral occurrence data. The data is stored in a quad-tree search structure to support very fast windowing of small sets of data from a very large database. HyperXYZ files can be created from Geosoft GDB files or from any database using SQL queries. HyperMAP (HMAP) Vector drawing format for very large vector data to be windowed and rendered at a wide range of scales. The vector data is stored at multiple resolutions in a quad-tree search structure, which enables this data to be efficiently retrieved for any map scale. For example, a drainage vector layer is an ideal candidate to be stored as a HyperMAP. To create a HyperMAP, you can draw the data in a Geosoft map group the way you would like the data to appear in a client application. The DAP Administrator can convert the selected map group into a HyperMAP. The Geosoft line data stored in large GDB files is already optimized for efficient windowing and extraction. Such data can be cataloged in its native GDB format. All Hyper-formats should be created in the coordinate system of the browser map to achieve optimum performance. Data Visualization An important capability of DAP is the visualisation of cataloged data in the context of data browsing. Data users often need to see what the data looks like before it is downloaded. DAP also supports simple data visualization through OpenGIS WMS and Geosoft XML, which enables any web application to add data visualization from the DAP catalogs. When the data is cataloged, visualizations at a variety of resolutions are created automatically. All dataset types have default ways to create visualizations, and different ways to create visualisations at higher resolutions. Typically, all dataset types create coarse resolution snapshots in the coordinate system of the browser map. The snapshots are used for rapid display at very large viewing scales, which is common when browsing large catalogs. As the visualization scale is reduced, for example, by zooming into an area of interest, more refined visualizations may be rendered directly from the data sources, depending on the source dataset type. The following table describes how visualization works for each dataset type: Type acquiretable acquirepoint Documents Images (ECW, PNG, JPG, TGA, TIF, etc.) Default Visualization Box outline of extent with a title Image of point locations as simple symbols Box outline of extent with a title Snapshot image plus high-resolution refinement, which may be slow for large images Geosoft DAP Manual 104

114 Appendix 2 Data Visualization Grids (all Geosoft supported types) Hypergrids (HGD) Geosoft databases (GDB) HyperMaps (HMAP) HyperXYZs (HXYZ) GIS Shape and TAB files Voxels Snapshot image plus high resolution refinement, which may be slow for large grids Snapshot image plus high-performance refinement at all resolutions Database line traces as image snapshot Vector snapshot plus high-performance vector drawing at all resolutions Image of point locations as simple symbols Image snapshots plus high performance refinement at high resolutions Voxel rendered as it would look if viewed from directly above the Voxel in 3D Note that some visualization is very limited. A box with a title does not provide much information except the data location. Also, some dataset types cannot zoom beyond the minimum resolution in the default snapshots. To improve visualization of these dataset types, you can choose to create a HyperGrid image or HyperMap of the data that presents what you would like data browsers to see. Both HyperGrid images and HyperMaps render very fast at all resolutions. 105 Geosoft DAP Manual

115 Appendix 3: DAP12 Migrator The DAP12 Migrator can be used to migrate a DAP 11.2 catalog object file to a DAP 12.1 Catalog in a SQL database. The DAP 11 file system is also migrated to a Managed Exploration Information Repository in this process. The migration is faster than using the upload via the incoming folder, because the datasets in DAP 11 have already been catalogued and therefore have passed the verification process. The migration process will make a copy of the v11.2 file system in the DAP Data Folder, so double the anticipated volume of free space is required. Data may be accessed from other drives. As some of the DAP information that was stored in the v11.2 catalog is now stored in the file system, extra space for these supporting files should also be accounted for. In DAP12, Esri images that require a de-warped cache version are processed with ArcEngine 10 options to set compression type and ratios. This makes rectified Esri raster images much smaller compared to DAP Using the DAP12 Migrator The migrator is included with the DAP Administrator application installation; it is an executable named Geosoft.DAP.DapServerMigrator.exe and can be found in the DAP Administrator program: C:\Program Files (x86)\geosoft\dap Portal\service\bin. To run the DAP Server Migrator: 1. Locate and run (double click) the Geosoft.DAP.DapServerMigrator.exe application. 2. Browse and enter parameters for the DAP11.2 catalog file and the DAP12 config.

116 Appendix 3 Using the DAP12 Migrator A message will display when the catalog migration is complete. The Dap Server Migrator produces two log files in C:\Program Files (x86)\geosoft\dap Portal\service\Log. The application requires permission to write to this folder. This may require the application to be "Run as Administrator". C:\Program Files (x86)\geosoft\dap Portal\service\Log\DapMigration_History.log contains a list of datasets that were successfully migrated. C:\Program Files (x86)\geosoft\dap Portal\service\Log\DapMigration_Log.log contains more details on success and failures For example, this error: Error HRESULT E_FAIL has been returned from a call to a COM component. occurred because a LYR file did not have a data source file geodatabase. In the DAP Administrator web application, datasets are automatically published. Some properties of the DAP v11.2 catalog are not migrated including 107 Geosoft DAP Manual

117 Using the DAP12 Migrator Appendix 3 Browser Map Custom redirect images Preview sizes Structured Metadata Query Text search index Stylesheets and Disclaimer are applied in Dataset Properties, but the XLST and HTML files must be uploaded first. Click Cancel or the x button in the top right corner to close the Dap Server Migrator. Take care not to run the migration process twice by clicking on OK again. Geosoft DAP Manual 108

118 Appendix 4: Using Geosoft XML Geosoft XML Reference This chapter is a reference manual for developers wishing to communicate with a Geosoft DAP server using XML. A fundamental level of knowledge of XML and DAP Server technology is assumed. For more information on XML, consult the online resources found at Geosoft XML is an XML-compliant protocol used to communicate with a data access protocol (DAP) server. Basic XML services include support for catalog information, metadata information, imaging, coordinate translation, and extraction services. The communication process between a client and a DAP server through Geosoft XML is illustrated by the following simple example. In this example, the client retrieves a catalog of all the datasets stored on the DAP server. XML Document Notation Various techniques are used to guide the user through the different syntax elements present in Geosoft XML. Some of these elements are listed below: ()* 0 or more elements contained within the braces may be present ()+ 1 or more elements contained within the braces may be present [] The content is optional (a b) Either a or b is required but both cannot be present

119 Appendix 4 Request Response Step 1: A get_catalog request is sent to the Geosoft DAP DMS server. Step 2: The request is received and processed by the server. Step 3: The server sends an XML response containing all the datasets it has stored. In this example, it has one dataset called MyDataset in the directory MyDirectory. Step 4: The catalog response is received by the client and displayed to the user. Request Response The geosoft_xml tag is the first tag in any request or response. It informs the client or server of the version of Geosoft XML to use. Format <geosoft_xml version=... > </geosoft_xml> version The version of the protocol the following elements are encoded with. It has the Major_ Version.Minor_Version format. Each request is enclosed by a start and end request tag, and each response is also enclosed with its own start and end tag. 110 Geosoft DAP Manual

120 XML Errors Appendix 4 Request <request namespace= > </request> namespace Optional parameter used to direct an XML request to DAP server plug-in. Response <response> </response> Example The following is a request for the catalog: <geosoft_xml version= 1.0 > <request> <catalog/> </request> </geosoft_xml> The DAP server sends the following response: <geosoft_xml version= 1.0 > <response> <catalog> (the catalog information is returned here) </catalog> </response> </geosoft_xml> XML Errors If an error occurs, an error tag is sent back instead of the expected response tag. The error tag notifies the client that an error occurred while processing a particular request. The client matches the error to the request by the handle attribute in the request. The error is reported in the format described below. Error Response <error handle= code= > Geosoft DAP Manual 111

121 Appendix 4 Capabilities <![CDATA[ ]]> </error> handle code Optional client-defined string used by the client to keep track of request and response pairs. An integer specifying the particular error that occurred. Example <geosoft_xml version= 1.0 > <error code= 502 > <![CDATA[Error processing EXTRACT_DATA request, operation not supported by this server.]]> </error> </geosoft_xml> Capabilities Gets capabilities of a server. Request <capabilities handle= > </ capabilities > handle Optional client-defined string used by the client to keep track of request and response pairs. Response The response provides information about what is allowed for each supported dataset type. <capabilities handle= > (<dataset_type name= > <commands> (<command name= > (<parameter name= > (<attribute name= > (<value name= >)* </attribute>)* </parameter>)* </command>)* 112 Geosoft DAP Manual

122 Example Appendix 4 </commands> </dataset_type>)* </capabilities> handle DATASET_ TYPE name COMMAND name PARAMETER name ATTRIBUTE name VALUE name Optional client-defined string used by the client to keep track of request and response pairs. The spatial dataset type supported by DAP. The name of the spatial dataset type. The command that can be executed on a dataset of this type The name of the command that maps to the corresponding XML tag. The child tag within a command that is further restricted by the following child nodes. The name of the parameter, which maps to a corresponding XML tag that is a child node of the specified command. The attribute of the parameter node that is restricted to the given list of values. The name of the attribute within the parameter tag. The value that the attribute is allowed to have. The value of the attribute. First, the response outlines each command that is valid for the spatial dataset type. Only datasetspecific commands are listed. These include: dataset_edition, metadata, image, extract, extract_status, extract_cancel, extract_data and default_resolution. All other commands catalog, catalog_edition, translate_coordinates, translate_bounding_box, and coordinate_system_list are independent of the spatial dataset type, and are not included in the list of supported commands for a spatial dataset type. Second, the response lists constraints for particular values that attributes can have in a request. Normally, all child nodes of a request are supported for all spatial dataset types. However, the response may return a list of allowable values for a particular attribute of a given tag. For instance, the image request has a format child with the type attribute. This attribute specifies the format of the image to return. The response can use the parameter, attribute, and value tags to restrict the allowable values for the type attribute. The following sample response limits the allowable values for the type attribute within the format tag to image/jpeg and image/png. Example <geosoft_xml version= 1.0 > <request> <capabilities/> Geosoft DAP Manual 113

123 Appendix 4 Configuration </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <capabilities> <dataset_type name= Grid > <commands> <command name= IMAGE > <parameter name= format > <attribute> <value name= image/jpg /> <value name= image/png /> </attribute> </parameter> </command> </commands> </dataset_type> </capabilities> </response> </geosoft_xml> Configuration Gets the configuration details of a DAP server. Request <configuration handle= /> handle Optional client-defined string used by the client to keep track of request and response pairs. Response <configuration handle= > <meta> <class name= > 114 Geosoft DAP Manual

124 Catalog Appendix 4 </meta> </configuration> handle META Optional client-defined string used by the client to keep track of request and response pairs. See the Metadata section. Example <geosoft_xml version= 1.0 > <request> <configuration/> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <configuration> <meta> <class name=\"geosoft\"> <class name=\"core\"> <class name=\"dap\"> <class name=\"configuration\"> </class> </class> </class> </class> </meta> </configuration> </response> </geosoft_xml> Catalog Gets the list of datasets currently stored on a DAP server. Geosoft DAP Manual 115

125 Appendix 4 Catalog Request <catalog handle= index = max_results= keywords= count= true false > <bounding_box maxx= maxy= minx= miny= > <coordinate_system datum= protection= units= /> </bounding_box> <filter path=... depth= /> </catalog> handle index max_results keywords count Optional client-defined string used by the client to keep track of request and response pairs. Optional; the number of datasets to skip before starting to return the catalog content. Optional; the maximum number of results to return governed by an in-order tree traversal. Optional; a search string. Optional; if True, only the number of datasets that matchs the query is returned. FILTER (Optional) path depth A folder path variable that can be used to filter the list of datasets returned (in addition to the spatial and/or keyword criteria). Optional; the number of levels to return beginning at the path location. Examples:/Global/ returns all datasets under the Global directory. /Global/@Global_Coastlines.hmap returns the specific dataset, Global_ Coastlines.hmap, if it exists. BOUNDING_ BOX (optional) maxx maxy minx miny COORDINATE_ SYSTEM The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. See the Coordinate Systems section. Response < catalog handle= > <collection name= > 116 Geosoft DAP Manual

126 Catalog Appendix 4 (<item name= title= type= edition= > <bounding_box maxx= maxy= minx= miny= /> </item>)+ (<collection name= > </collection>)* </collection> <count value= /> </catalog> <configuration version= /> handle COLLECTION name ITEM name title type edition Optional client-defined string used by the client to keep track of request and response pairs. A directory containing datasets and/or other directories. The name of the directory. A dataset. A unique name for the dataset used by the DAP server. It is used to specify a particular dataset in any request that has a dataset parameter. User-defined name for the dataset. Type of the dataset, which corresponds to one of the spatial dataset types returned by the capabilities response. E.g., image, grid, or document. The current edition of the dataset. BOUNDING BOX The bounding box for the dataset, always returned in WGS 84. maxx maxy minx miny COUNT value CONFIGURATION version The maximum x coordinate. The maximum y coordinate. The minimum x coordinate. The minimum y coordinate. Present if the catalog request only asked for a dataset count. The number of datasets that match the search criteria. The current version of the server. Used to invalidate the client cache. The version of the server. Example <geosoft_xml version= 1.0 > Geosoft DAP Manual 117

127 Appendix 4 Catalog Hierarchy <request> <catalog/> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <catalog edition= dog > <collection name= Global > <item name= Global_coastlines.hmap title= World Costlines type= Image > <bounding_box maxx= 180 maxy= 90 minx= -180 miny= -90 /> </item> </collection> </catalog> </response> </geosoft_xml> Catalog Hierarchy Gets the list of folders that have datasets currently stored on a DAP server. Request <catalog_hierarchy handle= keywords= > <bounding_box maxx= maxy= minx= miny= > <coordinate_system datum= protection= units= /> </bounding_box> </catalog_hierarchy> handle keywords Optional client-defined string used by the client to keep track of request and response pairs. Optional search string. BOUNDING_BOX (optional) maxx The maximum X coordinate. 118 Geosoft DAP Manual

128 Catalog Hierarchy Appendix 4 maxy minx miny COORDINATE_ SYSTEM The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. See the Coordinate Systems section. Response < catalog_hierarchy handle= > <collection name= > (<collection name= > </collection>)* </collection> </catalog_hierarchy> <configuration version= /> handle COLLECTION name CONFIGURATION version Optional client-defined string used by the client to keep track of request and response pairs. A directory containing datasets and/or other directories. The name of the directory. The current version of the server. Used to invalidate the client cache. The version of the server. Example <geosoft_xml version= 1.0 > <request> <catalog_hierarchy/> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <catalog edition= dog > <collection name= Global > </collection> </catalog> Geosoft DAP Manual 119

129 Appendix 4 Catalog Edition </response> </geosoft_xml> Catalog Edition Gets the current catalog edition. Request <catalog_edition handle= /> handle Optional client-defined string used by the client to keep track of request and response pairs. Response <configuration version= /> <catalog_edition handle= edition= /> handle edition CONFIGURATION version Optional client-defined string used by the client to keep track of request and response pairs. The current edition of the catalog. The current version of the server. Used to invalidate the client cache. The version of the server. Example <geosoft_xml version= 1.0 > <request> <catalog_edition/> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <configuration version= 432 /> <catalog_edition edition= dog /> </response> </geosoft_xml> 120 Geosoft DAP Manual

130 Dataset Edition Appendix 4 Dataset Edition Gets the edition of a dataset. Request <dataset_edition handle= name= /> handle name Optional client-defined string used by the client to keep track of request and response pairs. The name of the dataset as given by the name attribute in the item tag of a catalog response. Response <dataset_edition handle= edition= /> handle edition Optional client-defined string used by the client to keep track of request and response pairs. The current edition of the requested dataset. Example <geosoft_xml version= 1.0 > <request> <dataset_edition name= global_coastlines.hmap /> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <dataset_edition edition= dog /> </response> </geosoft_xml> Metadata Retrieves metadata for a dataset. Request <metadata handle= name= > Geosoft DAP Manual 121

131 Appendix 4 Metadata </metadata> handle name Optional client-defined string used by the client to keep track of request and response pairs. The name of the dataset for which to retrieve metadata, as given by the name attribute in the item tag of a catalog response. Response <meta handle= > <class name= type= > (<attribute name= type= value= />)* (<table> (<item name= X > (<attribute name= type= value= />)* </item>)* </table>)* (<class name= type= >)* </class> </meta> handle CLASS name type ATTRIBUTE name type value TABLE ITEM name Optional client-defined string used by the client to keep track of request and response pairs. Class containing a collection of attributes, tables, and/or other classes. The name of the class. The type of the class An attribute of the class. The name of the attribute. The type of the attribute. The value of the attribute. A collection of attributes in table format. A row of attributes in the table. The name of the row. 122 Geosoft DAP Manual

132 Image Appendix 4 Example <geosoft_xml version= 1.0 > <request> <metadata name= Global_coastlines.hmap /> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <metadata> <class name="geosoft"> <attribute name="referenceurl" type="/predefined/types/string" value=" <attribute name="description" type="/predefined/types/string" value="geosoft metadata objects"/> <class name="data"> <attribute name="centrey" type="/predefined/types/r8" value=" "/> <attribute name="centrex" type="/predefined/types/r8" value="0" /> </class> </class> </metadata> </response> </geosoft_xml> Image Renders a series of datasets into a layered picture. Request <image handle= > <format type= transparent= (true false) background= /> <bounding_box maxx= maxy= minx= miny= > Geosoft DAP Manual 123

133 Appendix 4 Image <coordinate_system datum= protection= units= /> </bounding_box> <resolution height= width= /> <layers base_map= index_map= > (<dataset name= >)+ </layers> </image> handle Optional client-defined string used by the client to keep track of request and response pairs. FORMAT type transparent Background The requested image type. The valid types are defined in the capabilities response. An optional True or False value; specifies whether the image should be transparent. Optional background colour for the image, specified in RGB (0xRRGGBB). BOUNDING_ BOX maxx maxy minx miny COORDINATE_ SYSTEM The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. See the Coordinate Systems section. RESOLUTION height width The height of the picture in pixels. The width of the picture in pixels. LAYERS base_map index_map An optional True or False value; specifies whether to draw the base map as a layer. An optional True or False value; specifies whether to draw the index map as a layer. DATASET name The name of the dataset to draw as one of the layers of the image, as given by the name attribute in the item tag of a catalog response. 124 Geosoft DAP Manual

134 Image Appendix 4 Response <image handle= > <picture> </picture> </image> handle PICTURE Optional client-defined string used by the client to keep track of request and response pairs. The picture encoded in base64. Example <geosoft_xml version= 1.0 > <request> <image> <format type= image/jpeg /> <bounding_box maxx= 180 maxy= 90 minx= -180 miny= -90 > <coordinate_system datum= WGS 84 /> </bounding_box> <resolution height= 300 width= 600 /> <layers> <dataset name= Global_coastlines.hmap /> <dataset name= Global_rivers.hmap /> </layers> </image> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> < image> <picture> abcdefgdvafldafhfdkvczkhfdsafdaj# Geosoft DAP Manual 125

135 Appendix 4 Extract Data </picture> </ image> </response> </geosoft_xml> Extract Data Retrieves data for a dataset. Because the data extraction process may take time, extracting data involves first requesting the server to begin the extraction process. The process is then checked periodically to determine its status. This enables an application to provide periodic status information. Once the process is completed, the data can be requested. Begin Extract Request This section details the extraction process for a particular dataset. <?xml version="1.0" encoding="utf-8"?> <geosoft_xml version="1.1"> <request> <extract> <bounding_box minx="-180" miny="-56" maxx="180" maxy="60"> <coordinate_system datum="wgs 84" /> </bounding_box> <datasets> <dataset name= 16 format="geosoft/uncompressed" resolution="1.44" /> </datasets> </extract> </request> </geosoft_xml> BOUNDING_ BOX maxx maxy minx miny COORDINATE_ SYSTEM The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. See the Coordinate Systems section. 126 Geosoft DAP Manual

136 Extract Data Appendix 4 DATASET name The name of the dataset to extract, as given by the name attribute in the item tag of a catalog response. FORMAT type The requested image type. The type valid types are given in the capabilities response and depend on the type of the dataset. RESOLUTION value The resolution to extract the data at. Begin Extract Response The parameters returned represent the actual parameters that the extracted data conforms to. These may differ from the requested parameters due to the format of the raw data. <extract handle= > <key name= /> <dataset name= /> <format type= /> <bounding_box maxx= maxy= minx= miny= > <coordinate_system datum= projection= units= local_datum= /> </bounding_box> <resolution value= /> </extract> handle Optional client-defined string used by the client to keep track of request and response pairs. KEY name A unique identifier of the extraction process. DATASET name The name of the dataset that is being extracted. FORMAT type The format the data is being extracted to. One of the formats listed in the capabilities response for this spatial dataset type. BOUNDING_ BOX Geosoft DAP Manual 127

137 Appendix 4 Extract Data maxx maxy minx miny COORDINATE_ SYSTEM The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. See the Coordinate Systems section. RESOLUTION value The actual data extraction resolution. Extract Status Request Gets the status of an extraction process. <extract_status handle= key= > </extract_status> handle key Optional client-defined string used by the client to keep track of request and response pairs. The key given to the client on an extract response that specifies the particular data extraction process. Extract Status Response Returns the status of an extraction process. <extract_status handle= key= > <status value= progress= status= /> </extract_status> handle key Optional client-defined string used by the client to keep track of request and response pairs. The key given to the client on an extract response that specifies the particular data extraction process. STATUS value progress status The current state of the extraction process: CANCELLED, IN_PROGRESS, or COMPLETED. The completion percentage of the extraction process The current task the extraction process is working on. 128 Geosoft DAP Manual

138 Extract Data Appendix 4 Cancel Extraction Cancels an extraction process. <extract_cancel handle= key= > </extract_cancel> handle key Optional client-defined string used by the client to keep track of request and response pairs. The key given to the client on an extract response that specifies the particular data extraction process. The response to the extract_cancel request is an extract_status response with status=cancelled. Extract Data Request Gets the data from an extraction process that has completed. <extract_data handle= key= > </extract_data> handle key Optional client-defined string used by the client to keep track of request and response pairs. The key given to the client on an extract response that specifies the particular data extraction process. Extract Data Response Gets the data from an extraction process that has completed. The data is returned encoded in base64. <extract_data handle= key= > </extract_data> handle key Optional client-defined string used by the client to keep track of request and response pairs. The key given to the client on an extract response that specifies the particular data extraction process. The data is encoded in base64. Example Begin extraction: <geosoft_xml version= 1.0 > <request> Geosoft DAP Manual 129

139 Appendix 4 Extract Data <extract> <format type= geosoft/compressed /> <bounding_box maxx= 180 maxy= 90 minx= -180 miny= -90 > <coordinate_system datum= WGS 84 /> </bounding_box> <resolution value= 0.01 /> <dataset name= Global_globeDEM.hgd /> </extract> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <extract> <key name= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas /> <dataset name= Global_globeDEM.hgd /> <format type= geosoft/compressed /> <bounding_box maxx= -100 maxy= 35 minx= -96 miny= 32 > <coordinate_system datum= WGS 84 /> </bounding_box> <resolution value= 0.01 /> </extract> </response> </geosoft_xml> Periodically check the status of the extraction using the key returned by the extract request: <geosoft_xml version= 1.0 > <request> <extract_status key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas /> </request> </geosoft_xml> <geosoft_xml version= 1.0 > 130 Geosoft DAP Manual

140 Extract Data Appendix 4 <response> <extract_status key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas > <status value= IN_PROGRESS progess= 20 /> </extract_status> </response> </geosoft_xml> After the extract_status response returns 100 as the progress, you can begin the actual data extraction. The data is returned as a ZIP file using base64 encoding: <geosoft_xml version= 1.0 > <request> <extract_data key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas /> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <extract_data key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas > fdaklfjdafhrueanklfzhsdfahdfkl;sfjafsafkl;hafd </extract_data> </response> </geosoft_xml> The extraction process can be stopped at any time by sending an extract_cancel request: <geosoft_xml version= 1.0 > <request> <extract_cancel key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas /> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <extract_status key= hafdsfsdnzjhfdsafldhvbzjnfdsahfdas > <status value= CANCELLED /> </extract_status> Geosoft DAP Manual 131

141 Appendix 4 Translate Coordinates </response> </geosoft_xml> Translate Coordinates Translates a series of coordinates from one projection to another. Request <translate_coordinates handle= > <input> <coordinate_system datum= projection= units= /> </ input > <output> <coordinate_system datum= projection= units= /> </ output > (<point x= y= z= />)* </translate_coordinates> handle INPUT OUTPUT COORDINATE_ SYSTEM Optional client-defined string used by the client to keep track of request and response pairs. The input coordinate system. The output coordinate system See the Coordinate Systems section. POINT x y z The x coordinate to translate. The y coordinate to translate. The optional z coordinate to translate. Response <translate_coordinates handle= > (<point x= y= z= />)* </translate_coordinates> 132 Geosoft DAP Manual

142 Translate Bounding Box Appendix 4 handle Optional client-defined string used by the client to keep track of request and response pairs. POINT x y z The x coordinate to translate. The y coordinate to translate. The optional z coordinate to translate. Example <geosoft_xml version= 1.0 > <request> <translate_coordinates> <input> <coordinate_system datum= NAD83 /> </input> <output> <coordinate_system datum= [NAD27] MEAN CONUS /> </output> <point x= y= /> <point x = y= /> </translate_coordinates> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <translate_coordinates> <point x= y= /> <point x = y= /> </translate_coordinates> </response> </geosoft_xml> Translate Bounding Box Translates a bounding box from one projection to another. Geosoft DAP Manual 133

143 Appendix 4 Translate Bounding Box Request <translate_bounding_box handle= > <bounding_box maxx= maxy= minx= miny= > <coordinate_system datum= projection= units= /> </bounding_box> <coordinate_system datum= projection= units= /> <resolution value= /> </translate_bounding_box> handle COORDINATE_ SYSTEM Optional client-defined string used by the client to keep track of request and response pairs. The first coordinate system (the one nested under the translate_bounding_box tag) is the coordinate system of the bounding box. The second coordinate system is the coordinate system required for the returned bounding box. See the Coordinate Systems section for more information on how to describe a coordinate system. BOUNDING_ BOX maxx maxy minx miny The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. RESOLUTION (optional) value This distance in the input coordinate system is converted to an equivalent distance in the output coordinate system based on the scale difference at the centre of the bounding box. Response <translate_bounding_box handle= > <bounding_box maxx= maxy= minx= miny= /> <resolution value= /> </ translate_bounding_box> 134 Geosoft DAP Manual

144 Translate Bounding Box Appendix 4 handle Optional client-defined string used by the client to keep track of request and response pairs. BOUNDING_ BOX maxx maxy minx miny RESOLUTION value The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. Optionally returned when a resolution was supplied in the input request. The new resolution for the new bounding box. Example <geosoft_xml version= 1.0 > <request> <translate_bounding_box> <bounding_box maxx= -101 maxy= 49 minx= -96 miny= 45 > <coordinate_system datum= NAD83 to WGS 84 (4) /></bounding_box> <coordinate_system datum= [NAD27] MEAN CONUS /> <resolution value= 0.01 /> </translate_bounding_box> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <request> <translate_bounding_box> <bounding_box maxx= maxy= minx= miny= /> <resolution value= 0.01 /> </translate_bounding_box> </request> </geosoft_xml> Geosoft DAP Manual 135

145 Appendix 4 Default Resolution Default Resolution Gets the default resolution for a given datatype and bounding box. Request <default_resolution handle= type= > <bounding_box maxx= maxy= minx= miny= /> </default_resolution> handle type Optional client-defined string used by the client to keep track of request and response pairs. The type of data contained within the bounding box: Grid, Image, Data, or Map. BOUNDING_ BOX maxx maxy minx miny The maximum X coordinate. The maximum Y coordinate. The minimum X coordinate. The minimum Y coordinate. Response <default_resolution handle= > <resolution value= /> </default_resolution> handle Optional client-defined string used by the client to keep track of request and response pairs. RESOLUTION value The default resolution to extract the data at. Example <geosoft_xml version= 1.0 > <request> <default_resolution type= Map > <bounding_box maxx= -101 maxy= 49 minx= -96 miny= 45 /> 136 Geosoft DAP Manual

146 List Supported Coordinate Systems Appendix 4 </default_resolution> </request> </geosoft_xml> <geosoft_xml version= 1.0 > <request> <default_resolution> <resolution value= 0.01 /> </default_resolution> </request> </geosoft_xml> List Supported Coordinate Systems Gets a list of the supported coordinate systems. Request <coordinate_system_list handle= list_type= datum= > </coordinate_system_list> handle list_ type datum Optional client-defined string used by the client to keep track of request and response pairs. The type of list to return; one of: datum local datum description local datum name projection units Optional; specifies a datum to narrow down the list to the supported projections, units, or local datums for the particular datum. If a local datum description or local datum name is specified as list_type, a datum must be provided. Response <coordinate_system_list handle= > (<item name= X />)* </coordinate_system_list> handle Optional client-defined string used by the client to keep track of request and response pairs. Geosoft DAP Manual 137

147 Appendix 4 Coordinate Systems ITEM name The name of a list item. Example <geosoft_xml version= 1.0 > <request> <coordinate_system_list list_type= datum / > </request> </geosoft_xml> <geosoft_xml version= 1.0 > <response> <coordinate_system_list> <item name= WGS 84 /> <item name= NAD27 /> <item name= NAD83 /> </coordinate_system_list> </response> </geosoft_xml> Coordinate Systems Any Geosoft XML request that includes a coordinate (such as a bounding_box), also includes a coordinate_system definition. You can describe coordinate systems in one of two ways: <coordinate_system datum= projection= units= /> OR <coordinate_system esri= /> Coordinate systems can be either geographic or projected. Geographic coordinate systems use longitude, latitude coordinates in degrees, and only require the datum to be defined. Projected coordinates use a map projection to define map coordinates in certain units of length on a datum. For example, the UTM Zone 15N projection defines coordinates in metres using a specific Transverse Mercator projection. The coordinate system description in Geosoft XML enables you to define systems by name, by EPSG code, or explicitly by specifying all parameters on the projection. Supported names for the various coordinate systems can be found in the projection CSV tables in your Oasis montaj/csv directory. 138 Geosoft DAP Manual

148 Coordinate Systems Appendix 4 The above tables may also be found in the /csv directory of each of the installed DAP servers. The projection.csv tables on all DAP servers should be identical. datum Specifies the datum of the coordinate system in one of the following three ways: By datum name, which can be any name returned for list_ type= datum, list_type= local datum description, or list_type= local datum name in response to a COORDINAT_SYSTEM_LIST request. By an EPSG code number for the datum or for a local datum transform (refer to By the name and parameters specified for a datum as follows: Datum=name,major_axis,flattening,prime_meridian The major axis must be defined in metres, and the prime meridian is in degrees relative to Greenwich. Note that if you expect the/a transformation to take place between datums, you must use the first option with local datum description or local datum name, or the second option using a local datum transform code. This will fully describe the local datum transform information required to translate coordinates between datums. projection Specifies the projection of the coordinate system. This is only required for projected coordinate systems. The projection can be defined in one of the following three ways: By projection name, which can be any name returned for list_ type= projection in response to a COORDINAT_SYSTEM_LIST request. By an EPSG code number for the projection (refer to By the name and parameters specified for a projection as follows: Projection=name,method,length_units, P1,P2,P3,P4,P5,P6,P7,P8 where name is your projection name, method is one of the methods listed in the Projection Transformation Methods table, length_units is one of the length units listed in the Length Units table, and the parameters P1 through P8 are the method-specific parameters listed for each method the Projection Transformation Methods table. A method may have fewer than 8 parameters, in which case the parameters must be provided in the order listed in the Projection Transformation Methods table. Distance references must be specified in length_unit. Geographic references (latitudes and longitudes) are specified in degrees. Longitudes in the Western hemisphere are negative. Latitudes in the Southern hemisphere are negative. Longitudes are relative to the prime meridian of the datum. units Optional coordinate system units of length, if different from length_unit Geosoft DAP Manual 139

149 Appendix 4 Coordinate Systems defined by Projection. The unit name can be any name returned for list_ type= units in response to a COORDINAT_SYSTEM_LIST request. Length units may also be defined in the form: units= name,factor where name is your length unit name and factor is the multiplication factor that converts your length unit to metres. esri The coordinate system may be described using an Esri coordinate system string as defined for ArcGIS version 8 or later. Refer to the Esri documentation for information on how to describe an Esri coordinate system. Note that the Esri coordinate system descriptions do not explicitly describe a preferred local datum transform method; although a local datum transform can be inferred from many datum names. If you intend your data to be transformed across datums, you should test to ensure that your results are as you expect. Examples The following describes geographic coordinates on the ARC 1960 datum, which is widely used in Africa: <coordinate_system datum="arc 1960"/> The following describes a projected coordinate system on the same datum: <coordinate_system datum="arc 1960" projection="utm zone 37S"/> Although the definition of units is redundant, the following two examples also define units, first by name only, and then by name and conversion factor: <coordinate_system datum="arc 1960" projection="utm zone 37S" units="m"/> <coordinate_system datum="arc 1960" projection="utm zone 37S" units="m,1.0"/> This example explicitly defines the ARC 1960 spheroid parameters: <coordinate_system datum="arc 1960, , ,0.0" projection="utm zone 37S"/> This example explicitly defines the UTM zone 37S projection parameters: <coordinate_system datum="arc 1960" projection="utm zone 37S,Transverse Mercator,m,0,39,,,0.9996,500000, "/> All previous examples are appropriate only for coordinate translations on the same datum (ARC 1960). If the coordinates require a datum change, a local datum transformation method must be defined for the datum. The following two examples show the same local datum transform description. The first uses the area descriptive string (from ldatum.csv), and the second uses the EPSG standard name (from datumtrf.csv): 140 Geosoft DAP Manual

150 Coordinate Systems Appendix 4 <coordinate_system datum="arc 1960 to WGS 84 (3)" projection="utm zone 37S"/> <coordinate_system datum="[arc 1960] Tanzania" projection="utm zone 37S"/> The following examples use the EPSG code number to describe the coordinate systems. The first example describes the datum only, and the second example describes the local datum transform: <coordinate_system datum=4210 projection=16137/> <coordinate_system datum=1285 projection=16137/> The following is an Esri string example that describes geographic coordinates on the ARC 1960 datum: <coordinate_system esri=geogcs["arc_1960", DATUM["Arc_1960", SPHEROID["Clarke_1880_(RGS)", , ]], PRIMEM["Greenwich",0], UNIT["Degree", ]]/> The following is an Esri string example that describes a projected coordinate system using UTM zone 37S: <coordinate_system esri=projcs["arc_1960_utm_zone_37s", GEOGCS["Arc_1960", DATUM["Arc_1960", SPHEROID["Clarke_1880_(RGS)", , ]], PRIMEM["Greenwich",0], UNIT["Degree", ]], PROJECTION["Transverse_Mercator"], PARAMETER["False_Easting",500000], PARAMETER["False_Northing", ], PARAMETER["Central_Meridian",39], PARAMETER["Scale_Factor",0.9996], PARAMETER["Latitude_Of_Origin",0], UNIT["Meter",1]]/> Projection Transformation Methods Projection Method Hotine Oblique Mercator Laborde Oblique Mercator Required Parameters Latitude of projection centre Longitude of projection centre Azimuth of initial line Angle from Rectified to Skew Grid Scale factor on initial line False Easting False Northing Latitude of projection centre Geosoft DAP Manual 141

151 Appendix 4 Coordinate Systems Longitude of projection centre Azimuth of initial line Scale factor on initial line False Easting False Northing Lambert Conic Conformal (1SP) Lambert Conic Conformal (2SP) Lambert Conformal (2SP Belgium) Mercator (1SP) Mercator (2SP) New Zealand Map Grid Oblique Stereographic Polar Stereographic Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing Latitude of first standard parallel Longitude of natural origin False Easting False Northing Latitude of natural origin Longitude of natural origin False Easting False Northing Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing Latitude of natural origin Longitude of natural origin Scale factor at natural origin 142 Geosoft DAP Manual

152 Coordinate Systems Appendix 4 False Easting False Northing Swiss Oblique Cylindrical Transverse Mercator Transverse Mercator (South Oriented) *Albers Conic *Equidistant Conic *Polyconic Latitude of projection centre Longitude of projection centre Easting at projection centre Northing at projection centre Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin Latitude of false origin Longitude of false origin Scale factor at natural origin Easting at false origin Northing at false origin Length Units Unit Description Factor to Metres m Metre 1.0 ft Foot ftus US survey foot ftma Modified American foot Geosoft DAP Manual 143

153 Appendix 4 Coordinate Systems ftcla Clarke's foot ftind Indian foot (Clarke) ftse foot (Sears) lkcla link (Clarke) lkben link (Benoit) lkse link (Sears) chben chain (Benoit) chse chain (Sears) ydse yard (Sears) ydind Indian yard fathom Fathom nautmi nautical mile mger German legal metre dega degrees (angular) n/a 144 Geosoft DAP Manual

154 Appendix 5: Creating Hyper Datasets The Create Hyper Dataset options can be accessed in Oasis montaj. These options will create Hyper Datasets (HyperGrids, HyperGrid Mosaic, HyperMap and HyperXYZ). Hyper Datasets are often used for redirected Image Preview, and serving very large point or raster datasets. Creating a Geosoft HyperGrid The Geosoft HyperGrid option enables you to create a Geosoft HyperGrid (*.hgd) from a grid or image file. A Geosoft HyperGrid is an optimized read-only grid format for DAP servers and supports compression, extremely fast windowing and multithreading. We recommend that very large grids or images that require frequent windowing to support client requests be provided to a DAP server in HyperGrid format. The actual HyperGrid is made up of a set of compressed files as follows: (*.hgd) the base grid index file. (*.hgd.gi) contains the georeferencing information. (*.hgd#) where # is 0, 1, 2, 3, etc. These are individual compressed grids of the original data at resolutions that are factors of two different in size. To Create a Geosoft Hyper Grid file: 1. Open Oasis montaj. 2. In the DAP Prep menu, select Prepare Hyper Dataset HGD from Single Grid... The Create an HGD (HyperGrid) from a grid dialog will be displayed. 3. Click the button and browse to the location of the input Grid/image file. A hypergrid with this same name will be automatically created in the same folder as the input grid or image. 4. Upload the hypergrid dataset to the incoming folder.

155 Appendix 5 Creating a Geosoft HyperGrid Mosaic Creating a Geosoft HyperGrid Mosaic The Geosoft HyperGrid Mosaic option enables you to create a Geosoft HyperGrid file (*.hgd) from a set of grid or image files that together make up a mosaic of a larger area. To Create a Geosoft HyperGrid Mosaic file: 1. Open Oasis montaj. 2. On the DAP Prep menu, select Prepare Hyper Dataset HGD from Multiple Grid Mosaic. The Create a HyperGrid from a grid mosaic dialog will be displayed. 3. Click the button and use the Ctrl key to select the Input Grids to include in the HyperGrid Mosaic, then in the Output HyperGrid box, specify a new file name. 4. Click OK and the Geosoft HyperGrid Mosaic with the specified Output filename is created in the same folder as the Input grids. Creating a Geosoft HyperMap The Geosoft HyperMap option enables you to create a Geosoft HyperMap file (*.hmap) from a map file. HyperMaps are optimized vector map drawings created from a Geosoft map group. They are intended for very large and frequently accessed vector datasets to be extracted at a variety of scales and windowed to smaller areas. HyperMaps are naturally de-aliased, and provide optimum DAP performance in these cases. A regional, but detailed drainage map is a good example of a vector layer that is ideal for a HyperMap. To Create a Geosoft HyperMap file: 1. Open Oasis montaj. 2. On the DAP Prep menu, select Prepare Hyper Dataset HMAP from Geosoft Map groups. The Create an HMAP from a map group dialog will be displayed. 146 Geosoft DAP Manual

156 Creating a Geosoft HyperMap Appendix 5 3. Click the button and browse to the location of the input Map file and click Next >. 4. Using the Group dropdown list, select the name of the Group you will be creating the HyperMAP from. 5. In the Output HyperMAP box, specify the name of the HyperMap to create. All the data for this store will be in a single file with the (*.hmap) extension. 6. In the Min Resolution box, specify the minimum resolution to store the HyperMap file. The HyperMAP will always store all entities in their initial resolution. The dataset will be processed and thinned to a specific resolution. This parameter specifies the resolution for the first thinning operation. This resolution will then be doubled and the process will be done again until a standard cut-off resolution is reached. It is important to specify a resolution that is an approximation of the actual resolution of the dataset. 7. Using the Data storage dropdown list, select Multiple or Single storage. This parameter enables you to choose between smaller HyperMAP files and better performance during the extraction process. You can configure multiple data stores, one for each rendering level or a single shared data store. The performance penalties occur with large HyperMAPs when the higher level layers are used. 8. Using the Entity Order dropdown list, select Tree optimized order (fast) or Original render order (slow). The Entity Order parameter controls the ordering of entities in the HyperMAP. If the HyperMAP contain filled entities (polygons) and the order of the rendering is important then the "Original Render Order" should be chosen. This will decrease performance but will ensure that the render order of the entities does not change. If the HyperMAP is primarily composed of line entities or the render order is not important then choosing "Tree Optimized Order" will result in more efficient extraction. 9. the OK and the Geosoft HyperMap with the specified parameters is created in the same folder as the Input map files. Geosoft DAP Manual 147

157 Appendix 5 Creating a Geosoft HyperXYZ Creating a Geosoft HyperXYZ The Geosoft HyperXYZ option enables you to create a Geosoft HyperXYZ file (*.hxyz) from a Geosoft random point database (*.gdb) file. This point format was designed as an optimized read-only format for DAP servers and supports compression, fast windowing and multithreading. It is recommended that all point data stored on a DAP server use this format to ensure the server functions efficiently. To Create a Geosoft HyperXYZ file: 1. Open Oasis montaj. 2. On the DAP Prep menu, select Prepare Hyper Dataset HXYZ from GDB... The Export database to HXYZ (HyperXYZ) dialog will be displayed. 3. Enter a name or click the button to browse to the location for the Output HXYZ file. The current GDB will be used, or a prompt to open a GDB will appear. The Channel to save and Lines to save parameters will be populated with the selected database information. 4. Click OK. Note that, multiple files are created with the same name and extensions, for example, hxyz,.hxyzd,.hxyzi, etc. They must all be uploaded together for the HXYZ to work correctly. 148 Geosoft DAP Manual

158 Appendix 6: DAP Catalog SQL Server Database Schema Database Schema The schema for the DAP Catalog SQL Server database is shown below. The Dataset table is the main table. The tables should not be edited directly except by or under the guidance of a Geosoft Solution Analyst. Full Database Schema The main tables are highlighted in blue. DatasetProperties are set by the DAP Data Manager through the DAP Administrator web application.

159 Appendix 6 Database Schema A new column was added to the DatasetInformation table in DAP 12.1: ServerQualifier: nvarchar(50) NULL The column allows us to download rectified images that are of a different type then the original one. Structured Metadata Query and Hierarchy In DAP 12.1, there is one metadata database per DAP Server. The datasetid and path fields in the Dataset table are used by the DAP Administrator service and connect to the metadata tables. 150 Geosoft DAP Manual

160 Database Schema Appendix 6 Security The SecurityGroup table contains the DAP security groups. Geosoft DAP Manual 151

161 Appendix 6 Database Schema Settings 152 Geosoft DAP Manual

162 Database Schema Appendix 6 Logging The tables on the left are used in DAP Server logging. The tables on the right are error logs for the DAP Administrator service. Geosoft DAP Manual 153