DAP Administrator 11.2 User Guide

Transcription

1 DAP Administrator 11.2 User Guide w w w. g e o s o f t. c o m

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: 9/27/2010. Written by, Nancy Whitehead. Please send comments or questions to Copyright 2010 Geosoft Inc. All rights reserved. Geosoft is a registered trademark, and DAP is a 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, photo-copying, 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.ug Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. Geosoft Incorporated Queens Quay Terminal 207 Queens Quay West Suite 810, PO Box 131 Toronto, ON M5J 1A7 Canada Tel: (416) Fax: (416) Web Site: info@geosoft.com

3 Contents Geosoft DAP License Agreement 1 Chapter 1: DAP Administrator 1 DAP Administrator Overview 1 New Features in DAP Administrator DAP added supports for the following data types and data connectors 2 Chapter 2: Install DAP Administrator 4 Installing the DAP Administrator 4 Manually Installing the DAP Administrator License Key 13 Chapter 3: Linking DAP Catalog Data to the DAP Server 15 Setting Up New DAP Server Administrator Configuration 15 Saving DAP Configurations 16 Adding a Data Folder 17 Removing a Data Folder 18 Chapter 4: Preparing Data for Cataloging on DAP Server 19 Setting Data Properties 19 General Properties 20 Security 20 Metadata Properties 21 Image Properties 21 Setting the Coordinate System of Datasets in a Folder 21 Setting Auto Catalog Watch and Update Frequency 23 Creating Data Source Connections to Catalog Various Data Types 24

4 Creating acquire Connection Files 24 Creating an ArcGIS Map Service Connection 27 Creating a RDBMS Data Connection 28 Creating Hyper Datasets 30 Preparing Data Folders 34 Defining Catalog Structure 34 Basic Structure 35 Managing Data Folders 35 Viewing Data Status 35 Refreshing Data 36 Excluding Data from being Cataloged on DAP Server 36 Including Data for Cataloging on DAP Server 36 Chapter 5: Making Data Available in the DAP Catalog 38 Cataloging Data 38 DAP Administrator Scripting 40 Command Line Mode 40 Script Mode 41 Security - Restricting Data Access 41 Restricting Data Permissions 41 Chapter 6: Managing DAP Configurations 46 Editing DAP Configuration 46 Identification and Administrator Pages 47 General Page 48 Environment Page 48

5 Services Page 48 Plug-ins Page 49 Creating DAP Server Usage Reports 49 Managing DAP Server Logs 49 Chapter 7: Integrated Metadata Solution 51 Geosoft Metadata Solution Supports FGDC and ISO Standards 51 Improved Visualization of Metadata 52 Chapter 8: Structured Metadata Query 53 Structured Metadata Query 53 DAP Server 54 How does the Structured Metadata Query work? 54 Appendix 1: Supported Data Types 56 Supported File Types 57 Qualifier 59 Associated File Extensions 60 Associated Directory Extensions 60 Image Size 60 Voxels 60 Georeference Voxel File 60 GIS Data Files 61 Documents 62 acquire Databases 63 Enabling SQL Server Authentication 63 Creating an ODBC Connection 66

6 Hyper Stores 70 Data Visualization 70 Appendix 2: File Mappings 73 View the File Mappings Table 73 Adding New Custom File Mappings 74 Appendix 3: Administrating DAP from a Different Computer 75 Appendix 4: Modify DAP Administrator Settings 76

7 1 Geosoft DAP License Agreement GEOSOFT agrees to supply the Licensed Program(s) as specified in my purchase order. Geosoft shall grant me a license to install and run DAP programs on a single or dual-processor server running a single instance of each DAP program subject to the Terms and Conditions herein contained. Should there be a separate signed agreement between you and Geosoft, or between your company and Geosoft, pertaining to the licensed use of this software, that agreement shall take precedence over the terms of this agreement. 1. DEFINITIONS: In this Agreement: "Licensed Program(s)" means the actual copy of all or any portion of Geosoft s proprietary DAP software technology, computer software code, components, dynamic link libraries (DLLs) licensed through the Geosoft license server, including any modifications, improvements or updates provided by GEOSOFT. Effective Date is the date the Geosoft license is installed. This date is recorded by the Geosoft License server when the Licensed Program(s) is installed. "Services" means the Services described on Section 4. "Termination" means the occurrences contemplated by Section 6 and LICENSE: GEOSOFT grants to me a non-exclusive license to install and run the Licensed Program(s) on a single server with one or two CPUs and with only a single instance of any Licensed Program running at the same time. Title and all intellectual property rights in and to the License Program(s), including, without limitation, copyright, trade secrets and trade marks, shall remain with GEOSOFT. I agree to refrain from raising any objection or challenge to such intellectual property rights, or from assisting or causing or permitting other(s) to do so, during the term of the Agreement and thereafter I may not assign this Agreement or any part thereof or sub-license the rights granted herein, or lend, rent, time-share, sell or lease the software without the prior written consent of GEOSOFT. I may not attempt to reverse engineer, de-compile or disassemble the software. I may not make any attempt to circumvent the License Manager that controls the access to the software use. 3. TERM: The Term of this Agreement shall commence on the Effective Date and shall continue until termination, as described in Section SERVICES: (i) According to the terms of my initial purchase, GEOSOFT shall make available to me, without additional fees such corrections and improvements to the Licensed Program(s) as may be generally incorporated into the Licensed Program(s) by GEOSOFT. (Normally this will be for a period of twelve (12) months). (ii) GEOSOFT has a strong commitment to customer service and product support. GEOSOFT offers me, subject to applicable Service Charge(s), continuing support in the form of or telephone advice and other assistance in problem diagnosis and the correction of errors or faults in the Licensed Program(s) during the life of this License. When a problem occurs which appears to be related to errors or faults in the Licensed Program(s), I may contact GEOSOFT and GEOSOFT will make its best and reasonable effort to solve the problem. However, GEOSOFT cannot guarantee service results or represent or warrant that all errors or program defects will be corrected. Also it is to be noted that each Licensed Program is designed to operate on Windows 2000 Server, Windows 2003 Server, Windows XP Professional, Windows Vista Business (32 or 64 bit), or Windows 7 (32 or 64 bit). (iii) Further, if I request service relating to the modification of the Licensed Program(s) to meet a particular need or to conform with a particular operating environment, GEOSOFT may, at its discretion, modify the Licensed Program(s) to meet these particular needs, subject to applicable Services Charge(s). However, all intellectual property or other rights which may arise from such modifications shall reside with GEOSOFT. 5. PROTECTION AND SECURITY OF LICENSED PROGRAM I agree that all additions, modifications, revisions, updates and extensions to the Licensed Program(s) shall be subject to all of the terms and conditions in this agreement. I acknowledge that all copies of the Licensed Program(s), provided by GEOSOFT or made by me pursuant to this Agreement, including, without limitation, translations, compilations, partial copies, modifications, derivative materials and/or updated materials, are proprietary, and the property of GEOSOFT, and may not be distributed to any other persons, without GEOSOFT s prior written consent.

8 2 I will not provide or otherwise make the Licensed Program(s) available to anyone in any form without GEOSOFT's prior written consent, except to our employees, or to other persons on our premises for purposes specifically related to our authorized use of the Licensed Program(s). 6. TERMINATION: This agreement shall terminate upon the termination date, if any, specified in your purchase agreement with Geosoft. This agreement may be terminated only upon thirty-days prior written notice to GEOSOFT. GEOSOFT may terminate this Agreement upon prior written notice effective immediately if I fail to comply with any of the terms and conditions of this Agreement. This Agreement shall terminate automatically upon the institution, or consenting to the institution of proceedings in insolvency or bankruptcy, or upon a trustee in bankruptcy or receiver being appointed for me/us for all or a substantial portion of my/our assets. 7. EVENTS UPON TERMINATION: I shall forthwith discontinue use of the Licensed Program(s), on the day Termination shall occur and agree not to resume such use in the future without written authorization from GEOSOFT. I shall uninstall and remove all software from my computer. Within thirty days after Termination, I shall destroy all physical and digital copies of the Licensed Program(s). This obligation relates, without limitation, to all copies in any form, including translations, compilations, derivatives and updated materials, whether partial or complete, and whether or not modified or merged into other materials as authorized herein. 8. WARRANTY: GEOSOFT does not warrant that the functions contained in the Licensed Program will meet my requirements or will operate in the combinations which may be selected for use by me, or that the operation of the Licensed Program will be uninterrupted or error free or that all program defects will be corrected. Each Licensed Program shall be furnished to me in accordance with the terms of this Agreement. No warranties, either express or implied, are made to me regarding the Licensed Program. THE FOREGOING WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 9. LIMITATION OF REMEDIES I agree to accept responsibility for the use of the programs to achieve my intended results, and for the results obtained from use of said Program(s). I therefore accept complete responsibility for any decision made based on my use of the aforementioned Licensed Program(s). In no event shall GEOSOFT be liable for any damages arising from performance or non-performance of the Licensed Program(s), or for any lost profits, lost savings or other consequential damages, even if GEOSOFT has been advised of the possibility of such damages, or for any claim against me by any other party. 10. GENERAL: I agree that this Agreement is a complete and exclusive statement of the agreement with GEOSOFT. This Agreement supersedes all previous Agreements with respect to the Licensed Programs, with the exception of a current signed Technical Service Agreements. GEOSOFT is not responsible for failure to fulfill its obligations under the Agreement due to causes beyond its control. Should any part of This Agreement for any reason be declared invalid, such declaration shall not affect the remaining portion which shall remain in full force and effect as if this Agreement had been executed without the invalid portion thereof. The relationship between the parties is that of independent contractors. Nothing contained in this Agreement shall be deemed to constitute or create a partnership, association, joint venture or agency. The provision of this Agreement shall be binding upon me and GEOSOFT and my respective successors and permitted assigns. This Agreement will be governed by the laws of the Province of Ontario and applicable laws of Canada. 11. YEAR 2000: The Licensed Programs have been tested to conform to DISC PD2000 1:1998 Year 2000 Conformity Requirements ( with the exception of clause 3.3.2, paragraph b. Section paragraph b) requires that inferences for two-digit year dates greater than or equal to 50 imply 19xx, and those with a value equal to or less than 50 imply 20xx. The Licensed Programs will recognize all two digit years as 19xx. This is to prevent errors importing historical data that pre-dates All dates that follow 1999 must use four digit dates in the Licensed Programs.

9 Chapter 1: DAP Administrator 1 Chapter 1: DAP Administrator The DAP Administrator was designed to provide an easy-to-use tool for administering the DAP Server and managing the DAP catalog. DAP Administrator Overview This document will walk you through the following Chapters: Install DAP Administrator Link Data with DAP Catalog on DAP Server Prepare Data for Cataloging on DAP Server Make Data available in DAP Catalog Manage DAP Configurations Integrated Metadata Solution Structured Metadata Query Also included are four Appendix sections that you may find helpful when you are working with the DAP Administrator: Supported Data Types File Mappings Administrating DAP from a Different Computer Modify DAP Administrator Settings New Features in DAP Administrator 11.2 The DAP 11.2 release focused on simplifying and improving both end user and data administrator workflows. For more detailed information see the Geosoft DAP Server 11.2 release notes available at: Seeker, which replaces the Find Data options with a new workflow driven design that combines capabilities and concepts from DAP Find Data and Dapple to create a simple 3-step workflow. The Seeker data access tool is available in all Geosoft applications and plugins. Structured Metadata Query is now supported in DAP 11.2 Servers, which provides the ability in Seeker to search for data using specific metadata fields in addition to the free-text search based on keywords. JPEG Support has been added for JPEG2000 (*.JP2 and *.J2K), enabling them to be catalogued and retrieved by users through the Seeker data access tool. JPEG2000 supports embedded coordinate system information and it also supports transparency

10 Chapter 1: DAP Administrator 2 which is very useful when sharing images of grids that are not simple rectangular in shape. Multiple File Selection is now supported in the Geosoft Metadata Editor, which is deployed with DAP Server This enables users to enter 'copyable' metadata fields for many files simultaneously. Report for Non-Cataloged Datasets is now included on the Cataloging Batch Tasks List Files Not In Catalog menu. You can now create an interactive report for files that are in the data folders but have not been cataloged. You can catalog selected datasets directly from the report. Support for GDB extraction through Web Clients has been added to the web client interface for DAP Server Improved Automatic Rendering for Shapefiles is included with DAP Server 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, Dapple and web clients. DAP added supports for the following data types and data connectors ESRI LYR files ArcGIS Map Services ArcIMS image Services ArcIMS metadata services Relational Database Management System (RDBMS) Data Connector Section grids/images Note: ArcSDE and Personal Geodatabase Connectors are no longer supported. DAP provides an enhanced and fully integrated metadata solution Publish metadata created in Oasis montaj 7.0 and related applications Support of FGDC and ISO19139 metadata standards along with the introduction of Geosoft metadata schema Graphical viewing of metadata by use of style sheets in Oasis montaj and DAP Administrator Cataloging of metadata in XML files and synchronization of metadata in relational databases and XML files Additional enhancements in DAP Server and DAP Administrator Distributed DAP cataloging processes Setting coordinate system and extent to datasets in a folder Support of disclaimer/copyright at dataset level Auto cataloging for datasets in DAP data folders Entry of IDAP account parameters during installation of DAP server software Features in DAP Client Plug-ins The Dapple client interface is available in ArcGIS Plug-in and MapInfo Plug-in New DAP Administrator Menu Items

11 Chapter 1: DAP Administrator 3 Cataloging Refresh Catalog Component Disclaimers Security Stylesheets Text Search Index Cataloging Attach Data Source ArcGIS Server Map Service ArcIMS Service RDBMS Connection Cataloging Batch Task Sync Metadata from Database List Files in Catalog (v11.2) List Files Not in Catalog (v11.2) Set Coordinate System on Folder Contents Settings Auto Catalog Catalog Service Setup

12 4 Chapter 2: Install DAP Administrator Chapter 2: Install DAP Administrator This section describes the installation of DAP Administrator in a Microsoft IIS environment. The DAP Administrator is a stand-alone client application used to manage and administer your DAP Server. For hardware and software requirements, see the DAP Installation and Configuration Manual (GeosoftDAPServerITManual.pdf). For the first-time installation, we recommend that you install DAP Administrator on the DAP Server computer. This minimizes configuration of file systems that must be accessible from both DAP Server and DAP Administrator. However, any client computer located on the same network as the Geosoft DAP Server computer may be used to administer the server provided that DAP Administrator is installed, and appropriate file shares and permissions are established. For more information, see the Administering DAP from a Different Computer section in the DAP Installation and Configuration Manual. Installing the DAP Administrator 1. Run (double-click) the installation setup.exe file ( ). The installation wizard opens to the Welcome dialog. 2. Click [Next]. The License Agreement dialog is displayed.

13 Chapter 2: Install DAP Administrator 5 3. Select (check) the I accept the terms in the License Agreement option. 4. Click [Next]. The DAP Administrator Install Type dialog is displayed. 5. Select the install type as Dap Administrator or Distributed Cataloging Service. Note: The Distributed Cataloging Service (DCS) enables multiple computers to be used to catalog DAP datasets. The DCS greatly enhances the performance of the cataloging process and increases the cataloging capacity up to 200,000 datasets. Installing the DCS configures the computer to be used for distributed cataloging by the DAP Server. For more information see Distributed Cataloging Service in the Geosoft DAP Server Manual (GeosoftDAPServerManual.pdf). 6. Click [Next].

14 6 Chapter 2: Install DAP Administrator The DAP Administrator Account Information dialog is displayed. 7. In the In the Domain field, type the domain name assigned to your DAP Administrator computer. 8. In the User field, type the name of the DAP Administrator account user. 9. In the Password field, type the password for the DAP Administrator. Note: Use Local System Account only if the datasets are stored locally and the Dap Administrator and DAP Server are installed on the same computer. 10. If you are satisfied with the options selected, click [Next].

15 Chapter 2: Install DAP Administrator 7 The Destination Folder dialog is displayed. 11. The default DAP Administrator installation folder is provided. To choose another location for the DAP Administrator installation; click the [Change] button. 12. When you are satisfied with the install location click [Next].

16 8 Chapter 2: Install DAP Administrator The Working Folder dialog is displayed. 13. Using the [Change] button, select a folder to store the DAP Administrator configurations, metadata template files, and metadata style sheets. Note: It is recommended that the working folder be set outside of the C:\Program Files\Geosoft path to minimize the chance of accidental deletion or removal when reinstalling or reconfiguring DAP Server. 14. Click [Next].

17 Chapter 2: Install DAP Administrator 9 The Temp Folder dialog is displayed. 15. Using the [Change] button, select a folder to store the DAP Administrator temporary files. Note: Temporary file sizes depend on the volume of data you process, and can be very large. It is recommended that a minimum of 1 GB free space be available on the drive that hosts your temporary file folder. 16. When you are satisfied, click [Next].

18 10 Chapter 2: Install DAP Administrator The Ready to install Geosoft DAP Administrator dialog is displayed. 17. To begin the Install process, click the [Install] button. (Note that, 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.)

19 Chapter 2: Install DAP Administrator 11 The DAP Administrator begins the install process. Once the file installation process is complete, the installer prompts you to enter your license key. 18. Do one of the following: If you have your license key and your server is connected to the Internet, enter the key and click [Internet]. The Geosoft License Manager dialog will be displayed. Click [OK]. If you do not have direct Internet access, you must have access from your server. If in doubt, click [Cancel] and establish your license manually. For procedure, see the Manually Installing the DAP Administrator License Key section.

20 12 Chapter 2: Install DAP Administrator The Complete the Geosoft DAP Administrator Setup Wizard dialog is then displayed. 19. To automatically launch DAP Administrator, check the Launch Dap Administrator check box. 20. Click [Finish]. If you did not request automatic launch, you can launch DAP Administrator by navigating to C:\Program Files\Geosoft\DAP Administrator\bin and doubleclicking the DapAdministrator.exe file ( ) or from the Start menu: All Programs Geosoft Dap Administrator Dap Administrator.

21 Chapter 2: Install DAP Administrator 13 If DAP Administrator has been installed successfully, the DAP Administrator window is displayed. Manually Installing the DAP Administrator License Key The typical installation of DAP Administrator configures your DAP license. However, if you were in doubt about your license key or your Internet or access, you may have chosen to cancel the licensing stage. In this case you can use the following procedure to install your DAP Administrator license. TO INSTALL YOUR DAP ADMINISTRATOR LICENSE KEY: 1. If your DAP Administrator computer has a direct Internet connection, or you have an service, from the Microsoft Start menu, select Start Programs Geosoft DAP Administrator License Setup. The Geosoft License Manager dialog is displayed.

22 14 Chapter 2: Install DAP Administrator 2. In the License Key field, type the DAP Administrator License Key provided with your Geosoft DAP CD. 3. Click [Internet] or [ ]. If you chose the option, you will receive an with instructions on how to install your 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 DAP Administrator license on your computer. You receive a confirmation message similar to the one below when the license key is accepted. 4. Your DAP Administrator application becomes licensed and fully functional.

23 Chapter 3: Linking DAP Catalog Data to the DAP Server 15 Chapter 3: Linking DAP Catalog Data to the DAP Server After successfully installing the DAP Administrator certain steps must be taken to prepare the DAP server for active use. Each DAP server managed via DAP Administrator requires its own configuration. Setting Up New DAP Server Administrator Configuration Each DAP server you administer has its own configuration. Note: Later, if you need to integrate a metadata database, you will work with Meta Templates (see the Integrated Metadata Solution chapter). If you intend to restrict data access to certain users and groups, you will define the Security settings (see the Security - Restricting Data Access section). TO CREATE A NEW DAP SERVER CONFIGURATION 1. In the DAP Administrator window, from the File menu, select New Configuration. The New Configuration dialog is displayed. 2. Enter the server URL (or computer name) and password (both were specified during the DAP server installation). For more information see the DAP Server Installation and Configuration Manual (GeosoftDAPServerITManual.pdf). 3. Specify the location of DAP Catalog directory (this was also specified during the DAP server installation, see reference above) by typing a fully qualified path in the Catalog directory field or by browsing to the required directory. 4. You can leave the Browser map field blank and the default browser map will be used in the new configuration. 5. Select the file types to be used in the new configuration. Unless you wish to catalog files of a specific type that is not included in the default list of supported

24 16 Chapter 3: Linking DAP Catalog Data to the DAP Server file types, select Default. To add support for a new file type, you must select Custom and add the new file mapping. For procedure, see the Appendix 2: File Mappings section. 6. Click [Create]. The configuration is created under the name you specified for your DAP server (in this example, DAP Demo ). 7. The configuration contains all the mappings and other information required to manage the data catalog for the selected server. Right-clicking DAP Demo in the DAP Configurations pane opens a pop-up menu that contains options available for working with the selected configuration. Saving DAP Configurations The Save Configuration option is available on the File menu and is enabled when a DAP Configuration is selected (highlighted) in the DAP Configuration pane. TO SAVE A DAP CONFIGURATION 1. Select (highlight) the DAP Configuration to be saved in the DAP Configuration pane. 2. On the File menu, select Save Configuration. The selected Configuration is saved. Note: To save changes made to all configurations, select the Save All option from the File menu.

25 Chapter 3: Linking DAP Catalog Data to the DAP Server 17 Adding a Data Folder Initially, new configurations are not associated with any physical data stores or virtual directories. Virtual directories are folders within which links to multiple file systems can be added and cataloged. As a result, from the perspective of DAP data clients, contents of the various file systems appear to have come from a single physical location. TO ADD A DATA FOLDER: 1. On the DAP Administrator File menu, select Add Data Folder. The Add Data Folder dialog is displayed. 2. To add a virtual directory: a. Select the Virtual data folder option button. b. Type the required folder name. This name will be displayed both internally (in DAP Administrator) and externally (to the DAP clients). 3. To add a physical file store: a. Select the Data folder option button. b. Browse (or type the path) to the required file system folder. In this case, both mappings must be defined. c. If DAP Administrator is installed on a machine other than the DAP server, the mapping to the target file system may differ between the DAP

26 18 Chapter 3: Linking DAP Catalog Data to the DAP Server Administrator and DAP server computers; click the set DAP Server data path hyperlink. The Set Server Path dialog is displayed. d. Define the DAP server mapping to the target file system. Now that you have defined structure for your data catalog, you are ready to add data. Note that the DAP server is not yet publishing any data because nothing has been cataloged. We have only defined the structure within which you will add data. Removing a Data Folder The Remove Data Folder from a DAP Server Configuration is only enabled when a Data Folder is selected in the DAP Configuration tree. TO REMOVE A DATA FOLDER 1. In the DAP Configuration pane select (highlight) the Data Folder to be removed. 2. On the File menu, select Remove Data Folder. The Confirm File System Removal dialog is displayed. 3. Click the [Yes] button and the Data Folder will be removed from the DAP Configuration pane.

27 Chapter 4: Preparing Data for Cataloging on DAP Server 19 Chapter 4: Preparing Data for Cataloging on DAP Server Data preparation for cataloging on a DAP Server is performed in the DAP Cataloging Administrator View. In order to show Data in this window a DAP Configuration must be open. The DAP Cataloging - Administrator View includes two parts, the DAP Catalog tree structure (left) and data properties (right) as shown below: 1.) DAP Catalog tree structure on the left hand side 2.) Data Properties on the right hand side To prepare data to be added to your catalog, copy the appropriate data files to the appropriate directories on your file system. Most data types are cataloged directly, based on the file type identified by the file extension. Some datasets, such as those from acquire or RDBMS databases are cataloged 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 cataloging process. In both cases, the file or connection appears to the data users in the directory where the file or connector is located. How you prepare the data depends on the data type, as does your choice of which catalog options to use when cataloging the data. If you create a database to manage metadata, you must define metadata templates that use the catalog structure and file names to establish metadata links to the metadata database. For more information, see the Integrated Metadata Solution chapter. Setting Data Properties The default property settings can be set/modified using the tabbed Properties window. The four property tabs, General, Security, Metadata, and Image (for Files only) can be found on the right hand side of the DAP Cataloging pane:

28 20 Chapter 4: Preparing Data for Cataloging on DAP Server General Properties The General Properties (Name, Location and File type) are presented as read only, except for individual files, which include exclusive options to override the File type, Qualifier, and Copyright file, as shown in the image below: COPYRIGHT/DISCLAIMER NOTIFICATION The Copyright file option enables you to attach a copyright or disclaimer to a dataset or a folder of datasets. The DAP Server installation creates a new sub-folder named disclaimer in the DAP Catalog folder. 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 save them into the disclaimer folder. All HTML files in the disclaimer folder are automatically added to the Copyright file dropdown list on the General tab. The Copyright file dropdown list also contains [inherit from parent] and [no copyright]. [Inherit from parent] indicates to inherit the settings from its parent folder and [no copyright] means that no copyright/disclaimer is set for the folder/dataset, regardless whether the parent folder has a copyright/disclaimer or not. 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. Security The Security tab enables you to set the security permissions. As DAP Administrator, you can use both local group accounts and users/groups accounts from the Microsoft Windows domain. 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. The Environment Page contains a variety of parameters that control the DAP server environment and presentation to the user. Use this tabbed dialog to select the users or groups to add as your new security group members. Active Directory users and groups, as well as the DAP Security groups themselves can be used as members of DAP Security groups.

29 Chapter 4: Preparing Data for Cataloging on DAP Server 21 Use the Settings Security menu option to create a new security group to be added to the Manage DAP Security Groups window. Note: When changes are made to the existing security levels for one or more datasets, the configuration must be re-cataloged for the changes to take effect. Only the element of the configuration to which the changes are applied must be re-cataloged. If changes are made at the root level of the catalog, the entire catalog must be re-cataloged. Metadata Properties The Metadata tab enables you to select the Meta Stylesheet to be applied and the Meta Template to be used to associate the Supplementary Metadata with the selected configuration, data folder or folder data, in the DAP Cataloging pane. File data includes additional metadata options, such as Create Metadata using the Edit Metadata dialog. The Edit Metadata dialog provides three tabs or pages enabling general, location, and data information to be set. Image Properties The Image tab is exclusively available for file data. The Image tab includes the following options: Preview the image. Click the Refresh Preview button to refresh the preview image. Change the default Highest Resolution of the image. Set image for display instead of the original file. - Provides the DAP administrator path for the image replacement. (If the DAP server uses a different mapping than the DAP administrator, then set DAP Server image path needs to be set as well.) Capability to Set Rendering Attributes is available for following file types: - *.hxyz (only point), *.gdb, line (size and color) or point (symbol, size and color). Setting the Coordinate System of Datasets in a Folder The Set Coordinate System on Folder Contents option found on the Cataloging Batch Tasks menu provides functionality to assign a coordinate system, as well as extents, to datasets residing in a selected folder. It is designed as a batch tool to prepare document datasets, common raster images, and occasionally, grid files. Use this tool with caution. It is advisable to make a copy of the datasets prior to the execution of the tool. Verify the coordinate systems and extents of the datasets in the folder after the process and before cataloging the datasets.

30 22 Chapter 4: Preparing Data for Cataloging on DAP Server The table below shows the data types that this tool is available for and whether the coordinates or extents can be set. Data Types Coordinate System Extents Documents (files) Yes and overwrite Yes and overwrite Grid files, which include all grid types (except for HGD) supported by Geosoft Yes if not set No Voxels Yes if not set No Common image files Yes if not set Yes if extents are not set (origin of 0,0 and pixel size of 1,1) ECW images Yes if not set Yes if extents are not set (origin of 0,0 and pixel size of 1,1) TO SET THE COORDINATE SYSTEM FOR DATASETS IN A FOLDER: 1. Select a folder in the DAP Cataloging Administrator View pane. 2. On the Cataloging menu select Batch Tasks Set Coordinate System on Folder Contents. The Set Coordinate System dialog will be displayed. 3. 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.

31 Chapter 4: Preparing Data for Cataloging on DAP Server 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). Note that Unit and Projection method are disabled when the Geographic coordinate system is selected. 5. Using the dropdown lists, select Unit, Datum and Projection method (required for the Projected coordinate system) and Local Datum (optional). 6. Specify the Minimum and Maximum X and Y Extents (optional). 7. Click [OK] and then [OK] again on the warning dialog to apply the coordinate system and extents to the datasets in the folder. Setting Auto Catalog Watch and Update Frequency The Auto Catalog option enables you to set a watch on your cataloged folders. When the contents of the folder changes as a result of a dataset update or the addition of a new dataset the DAP Administrator will re-catalog the datasets in the background using DAP Administrator scripts. The auto catalog process will begin once the DAP Administrator is closed. The watch utility will be placed in the system tray, and a log file will be saved in the DAP Administrator log folder. TO SET AUTO CATALOG WATCH: 1. From within the DAP Administrator, right-click the selected folder in the DAP Cataloging Administrator View pane. 2. From the popup menu, select Enable Auto Catalog Watch. 3. Click the Disable Auto Catalog Watch to turn off this option. TO SET THE AUTO CATALOG FREQUENCY: 1. From within the DAP Administrator, on the Settings menu, select Auto Catalog. The Auto Catalog Configuration dialog is displayed.

32 24 Chapter 4: Preparing Data for Cataloging on DAP Server 2. Enter the desired auto catalog frequency in the Catalog Frequency box. 3. The parameter is saved in C:\Program files\geosoft\dap Administrator\ini\dap_admin_watch_list.xml. Creating Data Source Connections to Catalog Various Data Types The Attach Data Source options can be accessed from the Cataloging menu. These options will attach data sources to the Data Folder or Folder currently selected in the DAP Cataloging pane. You can use these options to create an acquire Connection, RDBMS Connection, ArcGIS Server Map Service and an ArcIMS Service. For more information on data types, see Appendix 1: Supported Data Types. Creating acquire Connection Files You can create acquire connection files in your DAP data directory. Depending on the data to be published, and on the interfaces required to extract this data, there are two cataloging methods for your acquire databases: 1. Using acquire connections for all data 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 mine planning software. 2. Using acquire connections for drillhole collar and surface sample data cataloged into a widely accessible point format using pre-determined acquire Selection Files (.sel) This method provides a much simpler interface to the point data (including collar locations), enabling access from any DAP-enabled application, such as Oasis montaj, ArcGIS, and MapInfo. CREATING ACQUIRE CONNECTIONS FOR CATALOGING ALL DATA TYPES The acquire database connection provides high-level access to all data types from acquire-enabled applications such as Target or mine planning software. TO CREATE AN ACQUIRE CONNECTIONS FOR ALL DATA TYPES: 1. Select the data folder in the DAP Cataloging pane that you want to create an acquire connection to.

33 Chapter 4: Preparing Data for Cataloging on DAP Server On the Cataloging menu, select Attach Data Source and then select acquire Connection. The Create acquire Connection dialog is displayed. 3. Using the acquire connection type radio buttons, select the acquire database connection and then select the acquire connection settings and the acquire display preferences, as required. 4. Click the [OK] button and the acquire database connection will be attached. CREATING ACQUIRE CONNECTIONS FOR CATALOGING DRILLHOLE AND SURFACE DATA DAP can be used to extract both drillhole collar and surface sample data stored in an acquire database to any DAP client. Since the cataloged dataset is simply built into the Geosoft point technology, any interface (MapInfo, ArcGIS, or Oasis montaj) can be used to interact with the final product. The key to this process is the acquire proprietary

34 26 Chapter 4: Preparing Data for Cataloging on DAP Server selection file, which enables DAP Administrators to define the required fields and data for each dataset. In this case, you create an acquire connection file with extension.dapacquire_selection in your DAP data directory tree. TO CREATE AN ACQUIRE CONNECTION FOR DRILLHOLE AND SURFACE DATA: 1. Select the data folder in the DAP Cataloging pane that you want to create an acquire connection to. 2. On the Cataloging menu, select Attach Data Source and then select acquire Connection. The Create acquire Connection dialog is displayed. 3. Using the acquire connection type radio buttons, select either acquire point display from drillhole collar selection file or acquire point display from surface sample selection file, as required. The system prompts you for the ODBC connection information and for a selection file. 4. From the Selection file drop-down list, select a file (the list contains all selection files located in your current selected folder). 5. In the Dataset name field, type the name to appear in the DAP client for your data users. 6. Click [OK]. The acquire point dataset is now visible to your DAP clients through any interface that supports the point data type.

35 Chapter 4: Preparing Data for Cataloging on DAP Server 27 Note: You can modify the ODBC connection information contained in point datasets using the acquire Point Campaign tab of the Properties window for each dataset. Creating an ArcGIS Map Service Connection The DAP Administrator now includes ArcEngine, therefore prior requirements for the ArcMap license are no longer necessary. To catalog and publish ArcGIS Map Services an instance of ArcGIS Server must be installed on the DAP Server computer and an instance of ArcMap must be installed on the DAP Administrator computer. TO CREATE AN ARCGIS MAP SERVICE CONNECTION 1. To catalog an ArcGIS map service, use the DAP Administrator application to create a connector file. The connector file contains the parameters for connecting to the ArcGIS server and the map service to catalog. 2. Create a sub-folder under the DAP data folder to contain the connector file. The folder name will be shown in the DAP client interface. 3. In DAP Administrator, browse to the folder in the DAP Administrator Administrator View. 4. On the Cataloging menu, select Attach Data Source ArcGIS Server Map Service. The Create ESRI Map Service Connection dialog is displayed. 5. In the Filename text box specify the name of the connector to create. This is also the name of the dataset, or the catalogued ArcGIS Server Map Server, shown in DAP client interfaces. 6. In the ArcGIS Server box specify the name of the server computer or IP address. 7. For Map service, select the name of the Map Service that you would like to catalog. 8. Click the [OK] button to create the connector and optionally catalog the connector immediately. SUPPORT OF ARCGIS MAP SERVICES BY DAP CLIENT APPLICATIONS

36 28 Chapter 4: Preparing Data for Cataloging on DAP Server ArcGIS Server map services, after being cataloged and 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 a map service is done on-the-fly by the DAP Server with the ArcGIS Server. Creating a RDBMS Data Connection RDBMS (Relational Database Management System) Data Connection catalogs and publishes point data in relational databases using ODBC (Open DataBase Connectivity) DSN (Data Source Name) connections. The use of DSN connections enables publishing of point data in virtually any relational database. Point data must be from a database table or a SQL view which contains X, Y and/or Z columns. Data in X and Y columns must be in a geographic or projected coordinate system. The connector uses an ODBC DSN to connect to the database and reads data from it. The DSN must be a system DSN. Both SQL authentication and Windows authentication are supported. For MS Access databases, user name and password are not required as MS Access databases do not need them. TO CREATE A RDBMS DATA CONNECTION: 1. Create a sub-folder under the DAP data folder to contain the connector file. The folder name will be shown in the DAP client interfaces. 2. In DAP Administrator, select a data folder to use for saving the connector file. 3. On the Cataloging menu, select Attach Data Source RDBMS Connection or rightclick the folder and select Attach Data Source RDBMS Connection from the popup menu.

37 Chapter 4: Preparing Data for Cataloging on DAP Server 29 The Create RDBMS Connection dialog is displayed. 4. In the Filename box RDBMS.geosoft_rdbms is displayed by default. If a RDBMS connection already exists in the same location, the filename will be appended with a numeric iteration, i.e. RDBMS-2.geosoft_rdbms. The name will be the name of the data shown in DAP client interface. Modify the name to represent the point data in the database. 5. The DSN dropdown list provides all the system DSNs on the computer running DAP Administrator. The default is the first DSN in the list. 6. In the User name box specify the database account name. Leave the box blank for MS Access databases, or if Windows authentication is used for other relational databases. 7. In the Password box provide the password of the database account. Leave the box blank for MS Access databases, or if Windows authentication is used for other relational databases. 8. In the Database Selection section, click [Set] to select a Table or SQL view from the connected database and then select the Columns to be cataloged. 9. In the X, Y, Z columns box, click [Set] to select X, Y and Z columns from the list of columns chosen in the step above. (Z column is optional.) 10. In the Coordinate system box, click [Set] to choose the coordinate system appropriate for the data in the X and Y columns.

38 30 Chapter 4: Preparing Data for Cataloging on DAP Server 11. Click [OK] to create the connector and optionally catalog the point data in the database. The DAP Administrator caches the data as a Geosoft HXYZ file. The connector should be re-cataloged when the content of the database changes, either manually or periodically by using the DAP Administrator scripting tool. Creating Hyper Datasets The Create Hyper Dataset options can be accessed from the Cataloging menu. These options will create Hyper Datasets (i.e. HyperGrids, HyperGrid Mosaic, HyperMap and HyperXYZ) for the Data Folder or Folder currently selected in the DAP Cataloging pane. CREATING A GEOSOFT HYPERGRID FILE: 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. Select the Data Folder or Folder in the DAP Cataloging pane that includes the grid or image that you want to create a Geosoft HyperGrid for. 2. On the Cataloging menu, select Create Hyper Dataset and then select Geosoft HyperGrid. The Create a Geosoft HyperGrid From a Grid dialog will be displayed. 3. Browse to the location of the Input grid/image and then you can accept the default Output filename or specify a new file name. 4. Click the [OK] button and the Geosoft HyperGrid is created in the same folder as the Input grid/image file.

39 Chapter 4: Preparing Data for Cataloging on DAP Server 31 CREATING A GEOSOFT HYPERGRID MOSAIC FILE 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. Select the Data Folder or Folder in the DAP Cataloging pane that includes the grid or image files that you want to use to create a Geosoft HyperGrid Mosaic. 2. On the Cataloging menu, select Create Hyper Dataset and then select Geosoft HyperGrid Mosaic. The Create a Geosoft HyperGrid From a List of Grids dialog will be displayed. 3. Using the [Add] button, select the Input grid/image files to include in the HyperGrid Mosaic, then in the Output filename box, specify a new file name. 4. Click the [Create] button and the Geosoft HyperGrid Mosaic with the specified Output filename is created in the same folder as the Input grid/image files. CREATING A GEOSOFT HYPERMAP FILE 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. Select the Data Folder or Folder in the DAP Cataloging pane that includes the map file that you want to use to create a Geosoft HyperMap. 2. On the Cataloging menu, select Create Hyper Dataset and then select Geosoft HyperMap. The Create a Geosoft HyperMAP From a Map dialog will be displayed.

40 32 Chapter 4: Preparing Data for Cataloging on DAP Server 3. Browse to the location of the Input map and the HyperMap parameters will be enabled. 4. Using the Group dropdown list, select the name of the Group you will be creating the HyperMAP from. 5. In the Output filename 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. Note: 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). Note: 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.

41 Chapter 4: Preparing Data for Cataloging on DAP Server Click the [Create] button and the Geosoft HyperMap with the specified parameters is created in the same folder as the Input map files. CREATING A GEOSOFT HYPERXYZ FILE 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. Select the Data Folder or Folder in the DAP Cataloging pane that includes the database file that you want to use to create as a Geosoft HyperXYZ. 2. On the Cataloging menu, select Create Hyper Dataset and then select Geosoft HyperXYZ. The Create a Geosoft HyperXYZ From a GDB dialog will be displayed. 3. Browse to the location of the Input database and the Channel and Lines parameters will be populated with the selected database information.

42 34 Chapter 4: Preparing Data for Cataloging on DAP Server 4. Use the [Add] and [Remove] buttons to select the Channels and Lines to include in the HyperXYZ file. 5. In the Output filename box, specify the name of the HyperXYZ to create and click the [Create] button. Note that, multiple files are created with the same name and extensions, for example, hxyz,.hxyzd,.hxyzi, etc. They must all be copied together for the HXYZ to work correctly. Preparing Data Folders 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 organized. The hierarchical structure is similar to a file system you are used to working with in Windows Explorer. You map directories from your server file systems directly to the DAP catalog. 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 directories on your file system, or preparing optimizations for certain datasets, and establishing appropriate metadata. Note: 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 on an RDBMS. 5. Cataloging the data, which involves scanning the connected file systems for the data types and connectors that you want to publish, farming the required metadata, setting up the required files (such as data caches), creating visualizations to support visual browsing of your data, and updating the catalog that is exposed to your data clients. 6. Managing your data catalog by adding new data, removing unwanted data, and recataloging certain dynamic data types. Defining Catalog Structure You need to design a logical directory hierarchy in which you want to organize data to be published on your DAP server. DAP can map different file systems to the different directories, so that they appear as part of a single unified directory hierarchy to your data clients. 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.

43 Chapter 4: Preparing Data for Cataloging on DAP Server 35 Basic Structure We would like our data clients to see this data organized in five primary directories : Projects Drilling Geochemistry Geophysics Global Reference We could create a single directory on our DAP server s main disk that has a set of subdirectories with the following names: However, for this example, we plan to share the data load across two separate disks (and thus file systems), either on our DAP server, or on two different servers to which DAP is connected via high-bandwidth backbone. In this case, the server view of the files will look as follows: Managing Data Folders The Manage Data Folders options can be accessed from the Cataloging menu. These options enable you to perform the following data folder management tasks, view Data Status, Refresh Data, Exclude Data from being Cataloged on DAP Server and Include Data for Cataloging on DAP Server. Viewing Data Status When you navigate in your data tree configuration in DAP Administrator, all files that have extensions included in the Appendix 2: File Mappings table are visible to you. The colour of the file name indicates the current status of the file: Black Not yet cataloged, and hence not visible to your data users

44 36 Chapter 4: Preparing Data for Cataloging on DAP Server Green Cataloged and visible to your data users Grey (excluded) Will not be cataloged You can use the Cataloging menu to modify the status of the data files and folders or use the toolbar buttons provided in the DAP Cataloging Administrator View pane, e.g. Exclude ( ), Include ( ) and Catalog ( ). Refreshing Data The user should trigger the Refresh action to make added files or data folders visible in the DAP Cataloging tree structure. The Refresh Data option can be accessed from the Cataloging menu. This option will be applied to the selected Data Folder or Folder in the DAP Cataloging pane. TO REFRESH DATA 1. Select the folder or data folder node in the DAP Cataloging pane and then on the Cataloging menu, select Refresh. The folder or data folder is refreshed for the appropriate node in the DAP Cataloging panel. Excluding Data from being Cataloged on DAP Server The Exclude option enables you to exclude selected data from future cataloging or if the data is already cataloged it will be removed from the DAP Server. The Exclude option can be accessed from the Cataloging menu or from the ( ) button on the Data Cataloging Administrator View toolbar. This option will be applied to the selected Folder or File in the DAP Cataloging pane. Note: Only the catalog entries are removed. The actual data files are not deleted, and can be re-cataloged. TO EXCLUDE DATA FROM BEING CATALOGED 1. Select the file or folder node in the DAP Cataloging pane and then on the Cataloging menu, select Exclude (or click the Exclude ( toolbar in the DAP Cataloging Administrator View pane). The data is marked as excluded (e.g. next time the catalog is updated. Including Data for Cataloging on DAP Server ) button on the ) and will be ignored the The Include option enables you to include selected Data for future cataloging on the DAP Server. The Include option can be accessed from the Cataloging menu or from the ( ) button on the Data Cataloging Administrator View toolbar. This option will be applied to the selected Folder or File in the DAP Cataloging pane.

45 Chapter 4: Preparing Data for Cataloging on DAP Server 37 TO INCLUDE DATA FOR CATALOGING: 1. Select the file or folder in the DAP Cataloging pane and then on the Cataloging menu, select Include (or click the Include ( ) button on the toolbar in the DAP Cataloging Administrator View pane). The selected Data will be included in future Cataloging of the DAP Server and if present, any Data exclusion markers will be removed (e.g. ).

46 38 Chapter 5: Making Data Available in the DAP Catalog Chapter 5: Making Data Available in the DAP Catalog Once data files and connectors have been prepared and placed in the appropriate directories, they need to be cataloged. Catalog Data action can be triggered in four ways: By selecting Catalog on the DAP Administrator Cataloging menu. This action will be applied to the Data selected in the DAP Cataloging Administrator View pane. By right-clicking on the selected Data in the DAP Cataloging Administrator View pane and selecting Catalog from the popup menu. By selecting the Catalog button ( ) in the DAP Cataloging Administrator View pane. (Tooltip: Catalog item on DAP Server) By using the Ctrl + 1 hot key Cataloging Data Catalog data tasks can be performed in the DAP Cataloging - Administrator View pane. All levels of data can be cataloged including, configuration, data folder, folder, and file. TO CATALOG A DATA ITEM (CONFIGURATION, DATA FOLDER, FOLDER, AND FILE): 1. Select the required data item in the DAP Cataloging pane.

47 Chapter 5: Making Data Available in the DAP Catalog On the Cataloging menu, select Catalog. 3. The Data will be catalogued on the DAP Server. The DAP Administrator performs the following tasks for each item it finds: If the item has been Excluded it is ignored. If the item has already been cataloged, the DAP Administrator does a series of checks to see if this item needs to be updated. If the item is a connector, the DAP Administrator re-catalogues the item according to the connection rules (see description per connector type). If the item has not been cataloged, or if it needs to be updated, the DAP Administrator adds the item to the catalog. Depending on the data type, adding an item to the catalog 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

48 40 Chapter 5: Making Data Available in the DAP Catalog If there are any warnings or errors, these are reported in the catalog log file, which can be viewed after the catalog process finishes. If there is a cataloging error, the file or connector is not cataloged. Once the catalog process is complete, the DAP server is notified that the catalog has been updated, and data clients will now see the new catalog. You are presented with a report of the cataloging process. The behaviour of the cataloging process depends on the data type: Note: Only data types defined in the Appendix 2: File Mappings table are recognized. The grid and picture types include a qualifier (in brackets) that tells DAP which DAT interface to use to read that data. Note: Only those qualifiers that appear on the list in the File Mappings window are supported. You cannot add or change qualifiers. 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. Voxels Only georeferenced Geosoft voxels can be cataloged and delivered via the DAP Server. See Appendix 1: Supported Data Types - Voxels for suggestions regarding working with voxels. DAP Administrator Scripting The Dap Administrator Script (dapadministratorscript.exe file) enables the DAP server administrator to perform cataloging functions from a command-line interface. As a result, refreshing a DAP server catalog can be automated as a scheduled task (for example, to be performed following regular updates of the metadata database or DAPData directories). The DAP Administrator Script interface (c:\program files\geosoft\dap administrator\bin\dapadministratorscript.exe) can be executed in two modes: Command-line mode Script mode Command Line Mode This mode is typically used for ad-hoc (non-recurring) catalog updates. All configuration elements must be specified as part of the command line. The syntax for this mode is: dapadministratorscript -configuration=<config> -password=<password> - path=<path> <config> = name of an existing configuration to catalog <password> = DAP Server password <path> = list of comma separated paths to catalog For example:

49 Chapter 5: Making Data Available in the DAP Catalog 41 dapadministratorscript -configuration=geosoft -password=xxx - path=d:\dapdata\canada\,d:\dapdata\arctic The above sample command updates the canada and arctic directories at D:\dapdata for the Geosoft configuration. Script Mode This mode is more useful for regularly recurring or high-frequency catalog updates. It specifies the name of an external configuration file that the DAPAdministratorScript interface uses to obtain its configuration information. The syntax for this mode is: dapadministratorscript.exe -script=<script> where <script> is an XML script containing a configuration and paths to the catalog. For example: dapadministratorscript.exe -script=nightly.xml The above sample updates the canada and arctic directories at D:\dapdata for the Geosoft configuration. The content of the Nightly.xml script is as follows: <geosoft_xml> <configuration name="geosoft" password="pwd"> <node path="d:\dapdata\canada"/> <node path="d:\dapdata\arctic"/> </configuration> </geosoft_xml> Security - Restricting Data Access Through users and groups, the administrator can restrict access to each shared dataset to any of the following four levels: Searching Metadata viewing Data Previewing Extracting Note: The four security levels are sequential, with Searching being the lowest level, Extracting the highest. That is, in order to be able to extract a dataset, the user must have permission at all four levels. DAP Administrator automatically establishes permission for the lower security levels (Metadata viewing, Data previewing, and Searching) when a higher level (Extracting) is explicitly set. Restricting Data Permissions As DAP Administrator, you can use both local group accounts and users/groups accounts from the Microsoft Windows domain. It is highly recommended that security be managed on a group membership basis, rather than by individual user account, to simplify the

50 42 Chapter 5: Making Data Available in the DAP Catalog maintenance of dataset permissions. The Environment Page contains a variety of parameters that control the DAP server environment and presentation to the user. TO CREATE A NEW DAP SECURITY GROUP 1. In the DAP Administrator window, from the Settings menu, select Security. The Manage DAP Security Groups window is displayed. 2. In the Manage DAP Security Groups dialog, on the File menu, select New. The New Group window is displayed. 3. Specify the Group name and optionally add a group Description. Then, click the [Add] button to display the Users/Groups window.

51 Chapter 5: Making Data Available in the DAP Catalog 43 Note: To Remove a member from the group, select the member in the Members list and click the [Remove] button. 4. Use this tabbed dialog to select the users or groups to add as your new security group members. Active Directory users and groups, as well as the DAP Security groups themselves can be used as members of DAP Security groups. Click [OK] to close the dialog and return to the New Group window. 5. Click [Create] to create the new security group that will be added to the Manage DAP Security Groups window. Note: When changes are made to the existing security levels for one or more datasets, the configuration must be re-cataloged for the changes to take effect. Only the element of the configuration to which the changes are applied must be re-cataloged. If changes are made at the root level of the catalog, the entire catalog must be re-cataloged.

52 44 Chapter 5: Making Data Available in the DAP Catalog TO RESTRICT DATA ACCESS: 1. In the DAP Cataloging pane, select the item to restrict access to (file system, folder, or dataset). 2. Select the Security tab. a. To make data access restrictions for the selected item (dataset or folder) identical to those of its immediate parent in the Cataloging tree, check the Inherit Permissions check box. 3. Click [Add].

53 Chapter 5: Making Data Available in the DAP Catalog 45 The Users/Groups dialog is displayed. 4. Select the required user or group. 5. Click [OK]. The Users/Groups dialog closes. The selected user or group appears on the Group or user names list in the Security tab. 6. Select the user or group on the list. 7. In the Permissions for section, define the permissions for the selected user or group. 8. Click [Apply]. Note: To use Active Directory Groups or Active Directory Users, the IDAP account must be a domain account. For help with configuring a DAP Server domain account, please see the DAP Server documentation.

54 46 Chapter 6: Managing DAP Configurations Chapter 6: Managing DAP Configurations The DAP Configuration options for viewing, modifying, backing-up and restoring DAP Configurations created in DAP Administrator can be found on the File menu. Editing DAP Configuration The DAP Configuration can be edited using the Edit Configuration option on the File menu. The DAP Configuration can be found on the left hand side of the DAP Administrator interface. TO EDIT A DAP CONFIGURATION 1. Select (highlight) the configuration in the DAP Configurations pane. 2. On the File menu select Edit Configuration. The Edit Configuration dialog is displayed. 3. Click [Properties].

55 Chapter 6: Managing DAP Configurations 47 The current characteristics of the selected server are displayed in the Configuration dialog. 4. Modify the server characteristics on the tabbed pages of the above dialog as required. (Subsequent sections describe individual pages and the fields they contain.) Identification and Administrator Pages The Identification and Administrator pages identify the server and the Administrator, respectively.

56 48 Chapter 6: Managing DAP Configurations General Page The General page enables you to set the server security configuration, and to define what user events are logged to the server s activity log. The page fields are as follows: Security: Verification True if the user login and verification are required, false otherwise. Everyone user allowed True to allow anyone to log in to the server and see unrestricted data as user Everyone. The Everyone user always exists, and can log in with no password. False to prevent logging in to the server as user Everyone. Log Indicates what activities you would like the server to log. Note that logging image requests and catalog requests can make your log files very large. These requests are typically only logged when you are trying to determine usage patterns, or when you are debugging performance issues, or for other special purposes. Note: When any changes/modifications are made to the General Page - Security option, the Environment Page must also be changed/modified. Environment Page The Environment page contains a variety of parameters that control the DAP server environment and presentation to the user. The page fields are as follows: Area of Interest File A CSV file that contains a list of the areas of interest that you would like to expose in a DAP client interface. The entries provide the user with a rapid way to limit the spatial area of the searched DAP catalog. The file must be in the DAP Catalog directory. See the aoi_region.csv file (in the DAP Catalog directory) as an example of the file formatting. Extension The name of the installed DAP service in IIS. You normally do not change this parameter. Temp Directory DAP creates temporary files while answering data download requests. This is the directory DAP uses for these temporary files. Note: The directory name is as it would appear to the DAP server, and the DAP server must have read/write access to this directory. Structured Query Enter the Server and Database URLs (address and file name) for Structured Query. Path the list of paths that have been set are provided in the Path window. Services Page The Services page identifies the URL location of the servers that perform the basic DAP tasks searching, metadata retrieval/reporting, rendering, and data extraction. All these functions are normally performed by a single server.

57 Chapter 6: Managing DAP Configurations 49 DAP supports connections to different data types through the use of Data Plug-ins. The Services page identifies any plug-ins that have been loaded. Note: When any changes/modifications are made to the Services Page the General Page - Security option must also be changed/modified. Plug-ins Page Plug-ins can be added to support data sources not currently supported by DAP. Creating DAP Server Usage Reports A variety of DAP server usage reports can be created using the Generate Reports option (for example, Extract Summary, Extract Audit File Name, Extract Audit User, Extract Audit IP Address, and Request Summary). New in DAP Administrator 11.2 is the capability to create an interactive report for files that are in the data folders but have not been cataloged. The data administrator can catalog selected datasets directly from the report, quickly adding any datasets that may have been overlooked. TO CREATE A DAP SERVER USAGE REPORT 1. In the Configurations pane, select the DAP server. 2. On File menu, select Generate Reports. The Generate Report dialog is displayed. 3. From the Report drop-down list, select the required report. 4. In the Start date and End date fields, enter the start and end dates for the required report period. 5. Click [Generate]. The requested report is generated and loaded for viewing. Managing DAP Server Logs The DAP Administrator includes the option to manage the DAP server log files for a DAP server configuration. TO MANAGE DAP SERVER LOGS

58 50 Chapter 6: Managing DAP Configurations 1. In the DAP Configuration pane select (highlight) the DAP Configuration to manage. 2. On the File menu, select Manage DAP Server Logs. The Server Log dialog is displayed. 3. Logs for a selected data can be Viewed, Cleared and Filtered with any of the following criteria:

59 Chapter 7: Integrated Metadata Solution 51 Chapter 7: 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. Geosoft Metadata Solution Supports 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 data 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.

60 52 Chapter 7: Integrated Metadata Solution Improved Visualization of Metadata Graphical viewing of metadata is enhanced with the use of style sheets in Oasis montaj, DAP Administrator and DAP client interface. Custom style sheets are required to view the metadata created by custom metadata editors.

61 Chapter 8: Structured Metadata Query 53 Chapter 8: Structured Metadata Query DAP Server 11.2 supports the ability in Seeker to search for data using specific metadata fields in addition to the free-text search based on keywords. This can refine the data search on large corporate data repositories quickly and effectively, realizing their metadata investment. Structured Metadata Query

62 54 Chapter 8: Structured Metadata Query DAP Server 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. Create the SMQ database schema as part of the DAP metadata database. 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. Do not use the metadata fields with yes/no (0 or 1) values. How does the Structured Metadata Query work? 1. Connect to DAP Server.

63 Chapter 8: Structured Metadata Query 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: Data-Project Name!= Arctic Gravity Project <query> <statement operator=!= field= Data-Project Name value= Arctic Gravity Project /> </query> Example 2: Data-Project Name = Arctic and Subject = Geochem <query> <operator value= and > <statement operator= = field= Data-Project Name value= Arctic /> <statement operator= = field= Subject value= Geochem /> </operator> </query> 5. Select the Results step to view the query results.

64 56 Appendix 1: Supported Data Types Appendix 1: Supported Data Types The following table summarizes all the supported data types and the DAP Server v11 and DAP client features available for each type. Refer to the appropriate sections in the Appendix 2: Data Types section for more detailed information on how to handle the different data types. Data Type Grid files, which include all grid types supported by Geosoft Common image files Search, View Metadata, Preview Data Extract Data Download Window Reformat Resample Re-project Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Documents (files) Yes Yes No No No No ECW images Yes Yes Yes Yes Yes Yes Geosoft MAPs Yes Yes Yes No No Yes Geosoft GDB databases Geosoft HyperGrids Geosoft HyperXYZs Geosoft HyperMAPs 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 Grids/images (Section) MapInfo TAB and MIF files Yes Yes Yes Yes Yes No Yes Yes Yes Yes No Yes ESRI Shape files Yes Yes Yes Yes No Yes ESRI LYR files Yes Yes 1,2,4 Yes Yes No Yes ArcGIS Map Services ArcIMS image Services ArcIMS metadata services RDBMS Connector Yes Yes 1,3,4 Yes Yes Yes Yes Yes Yes 1,3,4 Yes Yes Yes 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

65 Appendix 1: Supported Data Types 57 Notes: Not supported in GeoDAP and DAP XML Not supported by MapInfo DAP client tool Image only Supported by Seeker client tool only. 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 ECW images Geosoft MAPs Geosoft GDB databases 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 recognized 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 know are already compressed in their native formats, such a PowerPoint or Word documents, should have the Compressed qualifier added. This will save DAP the unnecessary effort of compressing the data in the transfer stream. 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. (Not supported by GeoDAP web-client)

66 58 Appendix 1: Supported Data Types Geosoft HyperGrid Geosoft HyperXYZ Geosoft HyperMap Voxels Grid/Images (Sections) MapInfo TAB and MIF files HyperGrids are optimized grid files created from any Geosoftsupported 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. HyperGrids can be created in DAP Administrator from the Cataloging menu. 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. HyperXYZ files are created from Geosoft GDB files or from SQL queries on an ODBC link from the Cataloging menu in DAP Administrator. 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. HyperMaps can be created in DAP Administrator from the Cataloging menu. Voxels are 3D grids typically used to represent rock properties or physical parameters in a volume. Through the normal grid connector, DAP 11 introduces the ability to catalog oriented grids and raster images (section grids/images). A section grid maybe a grid (GRD) or image (TIF, JPG, etc). MapInfo TAB and MIF files. For each of these, the catalog process looks for a GIS legend file with a matching root name and with extension geosoft_legend. A legend file contains XML data that describes how to render the GIS points, lines, and polygons found in the native GIS file. Without a legend, DAP uses default characteristics available through the native file type. MapInfo TAB data contains a certain amount of rendering legend information, but ESRI Shape files contain no rendering data. You use the GIS legend editor in Oasis montaj to create GIS file legends.

67 Appendix 1: Supported Data Types 59 ESRI Shape files 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 a ESRI projection string. ESRI LYR files ArcGIS Map Services Connector ArcIMS Image/Meta 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. Layer files do not contain any data, 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 ArcIMS Image/Meta Services Connector provides a dynamic connection to an IMS Service. Note that only Meta Services that are linked to an Image service are cataloged. The Relational Database Management System (RDBMS) Data Connector catalogs and publishes point data in relational databases using ODBC DSN connections. The use of DSN connections allows publishing of point data in virtually any relational database. 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. Qualifier Files of certain types accept a text qualifier that further defines characteristics for connecting and using these files. The use of qualifiers depends on the file type and on how Geosoft works with that file type. Grid and image files, for example, 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 blank, 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).

68 60 Appendix 1: Supported Data Types 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 Shape 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. Image Size When DAP catalogs a dataset, it creates images of the data in a variety of resolutions. These images are stored in the DAP catalog, and are used to respond rapidly to coarse image requests of the data. Image Size is the maximum image size that you would like to prepare for this particular data type. A series of images is created, each half the dimension of the larger image, up to this maximum image size. Some data types can be rendered very rapidly and do not need much, if any, cataloged image. HGD files, for example, are designed specifically to render quickly in DAP, and typically you only need a cataloged image of the minimum 100 x 100 size. Other data types cannot be rendered at all. GIS files, for example, are not rendered on the fly because the process can be extremely slow. For these data types, you may consider rendering the cataloged images to much higher resolutions in order to give your users acceptable visual feedback on the content of the data. 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. 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

69 Appendix 1: Supported Data Types 61 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: Notes: 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]. 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,ArcIMS Image/Metadata Services, MapInfo TAB files (and associated file sets) and ESRI Shape files (and associated file sets). 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 alterative 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

70 62 Appendix 1: Supported Data Types montaj, ArcMAP, and MapInfo. The process of cataloging TAB and SHP files is the same as that for cataloging other data 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 cataloged. 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 cataloged 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 data 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, Dapple and via web clients. Additional information on the Geosoft GIS Legend Editor is available in Chapter 4: Using the GIS Legend Editor of the Geosoft DAP Server Manual ( For TAB and Shape data, you must place the.tab or.shp files, along with all the associated files, in the directories where you want this data to appear. You can also create a legend for specific data files using GIS Legend Editor, which is accessible from the DAP Prep menu in Oasis montaj. 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

71 Appendix 1: Supported Data Types 63 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. 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. For more information, see the Data Visualization section. 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

72 64 Appendix 1: Supported Data Types database software. We describe the procedure for Microsoft SQL Server, which is the most common technology used to host acquire databases. Note: 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. Note: If the above option is grayed out, you either have not selected the correct SQL Server, or you do 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.

73 Appendix 1: Supported Data Types Select the Security tab. 5. From the Authentication group, select the SQL Server and Windows option button. 6. Click [OK]. The SQL Server Properties (Configure) dialog closes. 7. Under the SQL Server tree, select Security Logins. 8. Select Login ID sa, which is a default public login that is normally set up when SQL Server is installed.

74 66 Appendix 1: Supported Data Types 9. 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 subsequent steps. Note: Note that 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.

75 Appendix 1: Supported Data Types 67 The ODBC Data Source Administrator dialog is displayed. Note: 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. 4. Click Add. 5. 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. 6. 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. 7. Click [Next].

76 68 Appendix 1: Supported Data Types The next dialog asks you how you want to authenticate the Login ID. 8. Choose the SQL Server authentication using a login ID and password entered by the user option. 9. 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. Note: The DAP Server runs under its own user, and this is the only way it can connect to SQL Server. 10. Click [Next].

77 Appendix 1: Supported Data Types 69 The next dialog prompts you to choose the acquire database name within SQL Server as the default database for this connection. 11. Select your database from the drop-down list. In the above example, the selected database is Acquire 1D. 12. Click [Next], and accept the defaults in the next dialog, then click [Finish] button to complete the connection. 13. Test your connection in the last dialog by clicking [Test the data source]. Your data source now appears on the System Data Sources list. 14. Repeat the above process for all acquire databases you want to make available on your DAP server. Note: 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.

78 70 Appendix 1: Supported Data Types 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: 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. Note: 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.

79 Appendix 1: Supported Data Types 71 When the data is cataloged, visualizations at a variety of resolutions are created automatically. All data types have default ways to create visualizations, and different ways to create visualisations at higher resolutions. Typically, all data 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 data type. The following table describes how visualization works for each data type: Type acquiretable acquirepoint Documents Images (ECW, PNG, JPG, TGA, TIF, etc.) Grids (all Geosoft supported types) Hypergrids (HGD) Geosoft databases (GDB) HyperMaps (HMAP) HyperXYZs (HXYZ) GIS Shape and TAB files Voxels 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 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 only 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 data types cannot zoom beyond the minimum resolution in the default snapshots. To improve visualization of these data 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. TO ASSOCIATE AN ALTERNATE VISUALISATION WITH A DATA FILE OR CONNECTOR: 1. Select the file or connector in the DAP Cataloging pane. 2. In the working panel, select the Image tab. 3. Browse to the file you would like DAP to use for rendering purposes. Note: The DAP server system account must have permission to connect to the specified file, and you must provide the path from the DAP server to the destination image. One way to ensure that the DAP Server system account has permission to the target images is to place the visualization support files together with the actual data in the DAP data directories. The visualization

80 72 Appendix 1: Supported Data Types files can then be excluded from the catalog by marking them excluded before cataloging (or re-cataloging the files if excluded afterwards). The IDAP_<servername> user on the DAP server must also have read access to the visualization files. If you choose to place visualization files outside of the DAP data directory, you must ensure that they are accessible from the DAP server, and are readable by the IDAP_<servername> user.

81 Appendix 2: File Mappings 73 Appendix 2: File Mappings The DAP Cataloging pane of the DAP Administrator window displays all the data available in your catalog tree that can be cataloged. Only data with extensions that appear in the File Mappings table is visible. This section shows you how to View the File Mapping Table and how to Add New Custom File Mappings. The list of Supported File Types and the catalog characteristics for each type can be found in Appendix 1: Supported Data Types. View the File Mappings Table TO VIEW THE FILE MAPPINGS TABLE 1. On the DAP Administrator File menu, select Edit Configuration. 2. The Edit Configuration * config_name* dialog is displayed. In the Supported File Types section, click View. The File Mappings window is displayed. The table in the window shows a list of the recognized file types, sorted by extension. The table defines the default DAP Administrator treatment for each of the included file types. However, each individual file type can be configured to behave like another, less complex file type. For example, GIS data files could be configured to behave like documents.

82 74 Appendix 2: File Mappings Adding New Custom File Mappings To enable cataloging of a file type that is not included in DAP Administrator out-of-thebox, you must add a mapping for this file type to the File Mappings table. TO ADD A NEW FILE MAPPING 1. In the DAP Configurations pane select the required configuration. Then, on the File menu select Edit Configuration. The Edit Configuration - *file_name* dialog is displayed. 2. In the Supported File Types section, select Custom. 3. Click [Edit]. 4. The File Mappings window is displayed. On the File menu, select New. The New File Mapping dialog is displayed. 5. In the Extension field, type the file extension for the new file type. 6. From the Type drop-down list, select a data type for the new file type. Note: Typically, you would select Document (see the Type section). 7. Optionally, enter a qualifier and any associated file or directory extensions required for the new file type (see the Qualifier, Associated File Extensions, and Associated Directory Extensions sections). 8. From the Image dimension drop-down list, select an image dimension (in pixels) to be used for generating dataset preview snapshots (see the Image Size section). 9. Click [Create]. The New File Mapping dialog closes. The new file type appears in the File Mappings table.

83 Appendix 3: Administrating DAP from a Different Computer 75 Appendix 3: Administrating DAP from a Different Computer Your DAP server can be administered from any computer on a shared network under the following conditions: DAP Administrator is installed on the computer The Administrator logged in to the computer has read/write access to the DAP Catalog directory The Administrator logged in to the computer has read/write access to all DAP data directories The DAP server has read access to the DAP Catalog directory (which does if installed correctly) The DAP server has read access to the data directories to be published Establishing access to the data directories from the DAP server requires that the data directories be mapped and visible from the DAP Server computer. For example, you have three computers as follows: Tec-DAP Your DAP server Tec-DATA Contains all data to be published Tec-Admin Primary computer for the DAP Administrator When you install Geosoft DAP Server, the DAP Catalog directory can be placed on Tec- DAP, and the DAP Administration work directories can be placed on Tec-Admin. All data should be placed in a directory on Tec-DATA. In this example, all the data is placed in the Tec-DATA\\DAP_DATA directory. The directory permissions should be set up as follows (note that DAP Administrator can log in to all computers as user Tec-Admin, using remote desktop if necessary): On Tec-DAP, share the DAP Catalog directory with user Tec-Admin, giving full control privileges. On Tec-DATA, share the DAP_DATA directory with user Tec-Admin, giving full control privileges. On Tec-DAP, map Tec-DATA//DAP_DATA to a local drive reference. Right-click this reference, select Properties and, on the Security tab of the Properties dialog, add user Tec-DAP/IDAP_Tec-DAP. Give this user read privileges. On Tec-Admin, map Tec-DATA//DAP_DATA to a local drive reference and make sure you have full control privileges. It is also convenient to add the DAP Catalog directory from Tec-DAP as a local drive reference, and use this reference when establishing configuration for the Tec-DAP server. User Tec-Admin can manage all data on Tec-DATA, and administer the DAP server on Tec-DAP directly from their own computer, Tec-Admin.

84 76 Appendix 4: Modify DAP Administrator Settings Appendix 4: Modify DAP Administrator Settings The DAP Administrator general settings, found under the Settings menu, are initial set during the install and should not have to be changed. However, if you move the location of the configuration, meta template or security directory these settings will need to be updated to point to the new location. TO SET DAP ADMINISTRATOR SETTINGS 1. In the DAP Administrator window, from the Settings menu, select DAP Administrator. The DAP Administrator Settings dialog is displayed. 2. Use this dialog to specify the following directories: Configuration directory Meta template directory Security directory 3. Restart the DAP Administrator.