DAP Server v 11 Manual - Geosoftupdates.geosoft.com/.../tutorials/pdfs/GeosoftDAPServerManual11.pdf · Configuring the DAP Server to Enable DAP Security 91 Configuring the IDAP_###

DAP Server 11 Installation and Configuration Manual

w w w . g e o s o f t . c o m

Contents

Chapter 1: DAP Server Introduction 1

DAP11 New Features 1

Target Audience 2

Technology Overview 4

DAP Server Architecture 5

Technology Limitations 5

Geosoft DAP Server Licenses 6

Geosoft DAP Server Core Technology 6

Chapter 2: Installing Geosoft DAP Server 8

Package Contents 8

System Requirements 9

Before You Begin 9

Installing Geosoft DAP Server 10

Manually Installing the Geosoft DAP License Key 20

Adding an IDAP Account during the Installation of DAP Server Software 21

Review of Installed DAP Folders and Files 23

Testing the Geosoft DAP Server Installation 24

Starting Internet Information Services 24

Testing Geosoft DAP Servers from a Web Browser 25

Enabling OGC WMS Support 25

Installing and Configuring the Geosoft DAP Administrator 26

Configuring Geosoft DAP Server for the First Time 27

Troubleshooting 28

Chapter 3: Using Geosoft XML 31

XML Document Notation 32

Geosoft XML Reference 32

Request – Response 32

XML Errors 33

Capabilities 34

Configuration 36

Catalog 38

Catalog Hierarchy 41

Catalog Edition 43

Dataset Edition 44

Metadata 44

Image 47

Extract Data 49

Translate Coordinates 56

Translate Bounding Box 58

Default Resolution 60

List Supported Coordinate Systems 61

Coordinate Systems 62

Chapter 4: Creating Web Applications 69

Prerequisites 69

Setting Up an Application Development Environment 69

Directory Structure 69

Chapter 5: Using the GIS Legend Editor 70

SPF Features and Attributes 70

GIS Legend Editor Interface 72

Constant Drawing Attributes 72

Defining Point2D Attributes 73

Setting Text2D Attributes 79

Drawing Attribute Tables 81

Chapter 6: Active Directory Security Model 89

How Thin Clients (such as GeoDAP) Access DAP Servers 89

How Thick Clients Access DAP Servers 90

Enabling DAP Security 90

Creating an IDAP_### Domain Account 91

Configuring the DAP Server to Enable DAP Security 91

Configuring the IDAP_### Account on DAP Server Computer 92

Updating the IIS Security through IIS Manager 92

Applying IDAP_### Security Permissions to DAP Folders 92

Planning and Creating DAP Security Groups 92

Setting DAP Securities to DAP Data Folders/Files 93

Testing DAP Security 93

Chapter 7: DAP Limits 94

Configuration Limits 94

DAP Login Limits 94

Catalog Limits 94

Extraction Limits 95

Render Limits 96

Disclaimer Limits 96

0BChapter 1: DAP Server Introduction 1

Chapter 1: DAP Server Introduction Geosoft DAP™ (Geosoft Data Access Protocol) is a family of Geosoft server and client technologies that enable geoscientists to find spatial and other data for use in their projects. These technologies include three fundamental components:

• Cataloguing of all available spatial and other data resources that might be relevant within an organization. This includes data stored on organized file systems in the many common formats (grids, images, raw data, and file documents), metadata stored in RDBMS systems, spatial data stored in certain RDBMS systems (such as acQuire), and data stored within corporate archiving systems.

• Searching for and evaluating data that may be relevant to a project at hand. This involves spatial and context searches for data by area of interest, data type, and full metadata evaluation to determine the value of each dataset for a particular use. It also involves rapidly previewing the content of selected datasets.

• Retrieval of the selected data, which is windowed to the area of interest, re-projected to an appropriate coordinate system, sampled to an appropriate scale, and transformed into a format that can be used. This also includes simple retrieval of documents and reports that support the data and can be viewed in native formats (such as .doc and .pdf files).

DAP11 New Features DAP now supports the following new data types and data connectors • ESRI LYR files • ArcGIS Map Services • ArcIMS Image Services • ArcIMS Metadata Services • Relational Databases (RDBMS) • Section Grids/Images

Note: ArcSDE and Personal Geodatabase Connectors are no longer supported.

DAP now provides an enhanced and fully integrated metadata solution • Publishing of metadata created in Oasis montaj 7.0 and related applications • Support of FGDC and ISO19139 metadata standards, together 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 – this feature is available in SP1 • Setting coordinate system and extent to datasets in a folder • Support of disclaimer/copyright at dataset level

2 0BChapter 1: DAP Server Introduction

• Auto cataloging for datasets in DAP data folders • Entry of IDAP account parameters during installation of DAP server software New Features in DAP Client Plug-ins • The new Dapple client interface is now available through the ArcGIS 2.0.1 and

MapInfo 7.0.1 Plug-ins

Target Audience This document is intended for Geosoft DAP Administrators who are responsible for the installation and maintenance of the Geosoft DAP Server and spatial data catalogs. A Geosoft DAP Administrator may be:

• A single user who wishes to create a personal DAP server for sharing data among a group of colleagues on an Intranet

• A corporate database administrator responsible for archiving and disseminating large-volume geospatial data across a corporate or organizational Intranet

• A database administrator at a government data distribution centre responsible for making large-volume geospatial data available to the public online

This document may also be used by Web developers for building web servers that integrate Geosoft DAP data distribution technologies into a data discovery and delivery web portal.

You might choose the Geosoft DAP technology to perform your data distribution task because of one or more of the following reasons:

• You have large-volume data, such as large gridded data, airborne geophysical data, large georeferenced point databases or large vector maps, which you need to make available in an efficient way and with minimum data preparation costs. You may also have document files or files of other types that you would like to georeference, catalog, and distribute.

• Your data can be easily organized within a file system as individual data files in a variety of formats. You want to be able to automatically catalog this file system and make the data available to your data consumers.

• You have corporate data stored and managed within an acQuire Data Model on an ODBC-accessible server, and you want to make this data available to clients who need to work with this data.

• Your data-consuming clients are geographically dispersed and connected to central servers only via a WAN, or perhaps even the Internet, and you need an efficient and easy way for them to find and retrieve their own data.

• Your data is georeferenced in known or well-defined coordinate systems and must be converted to a user’s coordinate system as part of the data delivery process.


• Because your datasets are large, and may cover broad geographic areas, your users may only require subsets of the data to suite their purposes. You need technologies that can efficiently subset and resample data to meet your users’ needs.

• A significant number of your data consumers use workstation software such as Oasis montaj, ArcGIS, and MapInfo to access and process data that you provide. You would like these users to be able to access your data directly and efficiently from these environments.

• You may want to provide a web interface to your data so that your data consumers can use a web browser to discover the data you have available, and retrieve this data in a variety of formats in any projected coordinate system.

• Because your datasets are large, and you may have a large number of separate datasets in different formats, you do not want to convert all your data to a single format. Your data models may be too complex to load all your data to a standard database.

The Geosoft DAP Server technology addresses all the above issues (see the Technology Overview section) within certain limitations (see the Technology Limitations section).


Technology Overview Geosoft DAP is a middleware server technology that connects networked users to back-end spatial data stores, which is illustrated in the following diagram.

From the deployment perspective, DAP is installed on a high-performance server at your data centre, where it can be configured to have high-speed access to data stores. A simple deployment would place DAP on a server that directly hosts large disks that store data to be distributed in a file system, and relational databases for storing metadata and geochemistry data. DAP responds to XML and Geosoft TASK requests for data catalogs, data searches, metadata and actual data retrieval. Professionals who need to find and use data will use their preferred applications, such as Oasis montaj, ArcMap, MapInfo, or an acQuire API-enabled application to access data. Data can also be browsed and retrieved via a web interface. Alternatively, other applications can use Geosoft XML to deliver data to their own specific workflows.

A DAP implementation requires a dedicated server in all cases, except possibly for evaluation purposes, or if DAP is deployed on a data professional’s workstation to share data among a small team. For performance reasons, DAP creates and maintains a catalog file that stores certain information about all the cataloged data, and provides for optimal browsing and searching performance.

A DAP Data Administrator manages the DAP catalog through a client workstation connected directly to the DAP Server network. The DAP Data Administrator uses Geosoft Oasis montaj or ArcMap to perform the data QA/QC (Quality Assurance and Quality


Control) and certain data preparation tasks. The DAP Administrator application is used to directly manage the DAP Server and the data catalog.

A typical data management workflow might involve accepting a package of project data and metadata that is to be permanently stored in the corporate data center and made available to a professional team. The DAP Data Administrator first verifies that the data quality standards are met, that coordinate systems are correctly defined, and that data formats meet corporate and DAP standards. The approved data is then placed in the permanent file system, and the DAP Administrator application is used to add this data to the DAP catalog, which makes the data available to all approved users.

DAP Server Architecture

The Geosoft DAP Server: • is a web application, and an ISAPI (Internet Server Application Programming

Interface) extension • uses TASKing and XML protocols to communicate with DAP client applications • provides data and metadata to data consumers, it does not support the uploading of

data and metadata to the server • provides the following services:

− Area of Interest (AOI) and Subject of Interest (SOI) search − Preview of the data − Security services integrated with Active Directory − Preview and download of metadata − Extraction of data

Technology Limitations The Geosoft DAP technologies are evolving to support more and more data types and environments. The following important limitations should be understood and accepted before attempting to implement a Geosoft DAP data distribution solution.

Geosoft DAP takes advantage of the wide variety of data formats supported by Geosoft core technologies. If one of your data formats is not supported, Geosoft DAP can distribute your data as a document of unknown type provided some strategy for georeferencing the data can be established. However, if data windowing and data re-


projection is required, your data must be converted to a Geosoft-supported format, otherwise Geosoft can develop data links to your data as part of your solution.

Geosoft DAP technologies are designed for, and tested in, environments that support up to about 25 concurrent users. Should you require a larger number of concurrent users, Geosoft can work with you to develop usability benchmarks, design data storage, and server scaling strategies to meet your requirements.

Geosoft DAP has been developed using Microsoft technologies and is installed and tested on Microsoft IIS servers. Geosoft DAP has also been tested using the open-source Apache web server running on a Microsoft Windows server. However, such an installation requires the assistance of Geosoft personnel. Geosoft DAP cannot be installed on UNIX servers.

Geosoft DAP is intended as a data cataloguing and data distribution solution, not a data archiving solution. Geosoft DAP can be configured to connect to existing archiving solutions, but such a configuration should be discussed with Geosoft Custom Solutions.

DAP supports access to Metech acQuire databases provided the client applications have implemented the acQuire API that supports DAP connections. Contact Metech directly to discuss the support for this feature (http://www.acquire.com.au/).

Geosoft DAP Server Licenses A new Geosoft DAP Server licensing model has been introduced that provides more flexibility for our clients to license the technology.

Geosoft DAP Server Core Technology

Along with Geosoft’s DAP server core technology, five licensed DAP Server extensions are now available:

Security Extension

Security features include support for Microsoft Active Directory (AD). All data can be secured on a file-by-file basis.

Distributed Cataloging Service Extension

DAP Server can be installed and configured to use one or multiple computers to catalog datasets. This Distributed Cataloging Service (DCS) greatly enhances the performance of the cataloging process.

ESRI Integration Extension

The ESRI Integration extension enhances exploration project workflow by enabling the integration of the following ESRI datasets and services: ESRI LYR files, ArcGIS Map Services, ArcIMS Image Services and ArcIMS metadata services.

acQuire Integration Extension

Data stored in a corporate acQuire database can be cataloged and published to acQuire-enabled client applications using the acQuire API. acQuire SEL files are now supported.

http://www.acquire.com.au/


ECW Extension

The ECW extension is required to support cataloging and publishing of ERMapper ECW image files larger than 500 MB each in size before compression.

8 1BChapter 2: Installing Geosoft DAP Server

Chapter 2: Installing Geosoft DAP Server This chapter describes the installation and setup of a Geosoft DAP Server in a Microsoft Internet Information Services (IIS) environment. If this is the first time you are installing the Geosoft DAP Server, we recommend that you install the server on your personal computer in order to gain familiarity with the system before you attempt to install DAP on a dedicated server.

Geosoft DAP Server comes with the following components:

• Core DAP Server

• The DAP Administrator application, which is a stand-alone client application used to manage and administer your DAP server

• Geosoft public domain datasets that can be installed to test the server application

• If required, your DAP Solution Consultant can enable the ASP.NET sample web server that uses Geosoft XML to interact with the core DAP Server to create a web client data discovery and delivery experience, which can be used as a starting point for a custom web experience.

Thick client applications that use the Geosoft high-performance TASK protocol to directly interact with Geosoft DAP servers are available directly from Geosoft. These include Geosoft Oasis montaj and plug-ins for ArcGIS (through Target for ArcGIS), and MapInfo.

Familiarity with the Microsoft IIS server would be beneficial. If you intend to make your DAP server accessible through the Internet, you should also understand how to secure your IIS server. If you are going to install Geosoft DAP servers on your local computer, or on a corporate Intranet, you can simply run the Geosoft DAP installation program while following the steps described in the installation instructions.

It is important that these steps are followed in the order presented to prevent any setup related errors.

Package Contents The Geosoft DAP Server v11 product is delivered with the following items:

• Geosoft DAP Server Installation CD – Includes directories for the DAP server installation, DAP administrator installation, sample browser maps for a web application, and a starting catalog

• License key for your DAP server installation

1BChapter 2: Installing Geosoft DAP Server 9

System Requirements Hardware and software requirements depend on the intended use of Geosoft DAP Server. There are two installation types supported by the Geosoft DAP system:

1. A personal computer installation that enables your personal computer to act as a server that shares data among a small group of people connected to the same network. Such an installation is limited to one or two concurrent users, and its performance is limited by other applications running on the same computer. Minimal requirements for such a system are:

• Windows XP Professional

• Internet Information Server (IIS) 5.0 or above, or Apache v2.0.44 or above (Note that, IIS 6.0 or above is recommended).

• A minimum of 512 MB RAM

• 200 MB disk space to install the server software and sample datasets

• 500 MB to install Oasis montaj to prepare data and administer DAP Server

• Sufficient disk space to hold data to be served

2. The minimum recommended server configuration for a corporate Intranet or for Internet support:

• Windows 2000/2003 Server Edition

• Internet Information Server (IIS) 65.0 or above

• Dual-Pentium CPU recommended

• 2 - 4 GB RAM

• 50GB SCSI hard drive for operating system and the server software

• 500GB to 1TB hard drive with RAID 5 configuration to store datasets

• 100-500GB hard drive to store DAP temporary files

• 50GB for SQL Server metadata database if needed

Your Geosoft DAP server should be dedicated to providing Geosoft DAP services only.

Note: Geosoft DAP servers can be configured to run in other environments, such as Apache. Contact Geosoft for further information and pricing to install Geosoft DAP on other systems. Geosoft DAP cannot be installed on Unix servers.

Before You Begin Ensure that the following conditions are met:

• You have read through the entire installation process in order to familiarize yourself with the procedure.


• The Microsoft Internet Information Services server (IIS) is installed and running on the machine where Geosoft DAP Server will be installed.

• You are logged in with full administrator privileges to the server computer on which Geosoft DAP Server will be installed.

• You know the computer name of the machine on which you are installing Geosoft DAP Server. If your DAP server will be used on an Intranet for corporate-wide use or for Internet use, you know the name assigned to your DAP Server by your Domain Name Service (DNS) server. Your IT Department establishes this name for you. You can normally verify that you have a valid name by pinging the name and verifying that the IP address returned is indeed the IP address of your server.

• You have at least 250 MB of free disk space for the complete Geosoft DAP Server installation. Note that you will build a file system on your DAP Server to hold all of the data to be catalogued and published, so you will need sufficient disk space to hold all the data that you intend to publish.

• The Geosoft DAP Server installation CD is in the CD drive of the server. You save the Geosoft DAP installation files to a temporary directory on your server if you have received the installation kit via FTP or via the Internet.

• You have the Geosoft DAP Server license key that enables the Geosoft DAP license on your server. The Geosoft DAP Server license key may be printed on the installation CD or supplied to you via an email or other media.

• You are familiar with DAP limits such as the maximum number of characters for short names, descriptive names and passwords, the maximum number of supported custom plugins, the maximum number of large datasets, etc. To view the list of DAP Limits; see the DAP Limits section.

Installing Geosoft DAP Server

TO INSTALL GEOSOFT DAP SERVER

1. Start the IIS service, if it is not started.

Normally, IIS would be running after a clean boot of your system. For instructions on how to check and start IIS, see Starting IIS section.

2. Double-click the installation program .

The Welcome dialog of the installation wizard is displayed.

3. Click [Next].

The License Agreement dialog is displayed.

4. Select the I accept the terms in the License Agreement option and click [Next].

The Destination Folder dialog is displayed.

5. To accept the default location “C:\Program Files\Geosoft\DAP Server\” click [Next].


(Note that to specify a different Geosoft DAP Server installation location, click the [Change] button.)

The Administrator User Information dialog is displayed.

6. In the Name, Email, and Phone Number fields enter contact information for the Geosoft DAP Server Administrator.

This information is stored in the ois.dll file on the Geosoft DAP server, and can be maintained by the Geosoft DAP administrator using the Geosoft DAP administration tools.

7. Click [Next].


The Server Information dialog is displayed.

8. In the Address/URL field, type your server name with the http:// prefix.

If you are installing on a server that has been assigned a specific name through your DNS server, you can change the computer name to that name. You can also use a specific IP address if you know that your server IP will not change, although this is not recommended.

9. In the Password field, type the password that will be required to perform administrative functions on your Geosoft DAP server. In the Confirm Password box re-type the password for confirmation purposes.

10. In the Short Name and Descriptive Name fields, type the names for your Geosoft DAP Server. The short name is used in server lists available to clients that have access to your Geosoft DAP server.

Note: The maximum number of characters for the DAP Short Name is 64 characters and the maximum number of characters for the Descriptive Name is 256 characters. To view the full list of DAP limits, see the DAP Limits section.

11. Click [Next].


The DAP Account Information dialog is displayed.

12. In the Domain field, type the domain name assigned to the user account.

13. In the User field, type the name of the IDAP account user.

14. In the Password field, type the password for the account user.

15. In the Confirm password field, re-type the password for confirmation purposes.

16. Click [Next].


The Data Folder dialog is displayed.

17. The Data Folder should contain the datasets you wish to publish. To enable you to test you initial configuration, some sample datasets will be installed in this folder. You can choose any folder on a local drive to store the Geosoft DAP datasets. If you wish to use a network drive for your dataset folder, you need to set up the network privilege required and used by the DAP server. Note that access to data not on the DAP server will be limited to the access speed of your network, and may not provide the performance required to meet your needs. To change the default folder, click the [Change] button and select a folder to be used to catalog the files to be published by your DAP server.

18. Click [Next].


The DAP Admin Folder dialog is displayed.

19. Using the [Change] button, select a folder for the DAP server catalog files.

20. Click [Next].


The Data Folder dialog is displayed.

21. Using the [Change] button, select a folder for the Geosoft DAP Server to manage temporary files. The temporary disk space required is at least the largest dataset that you envision serving times the number of concurrent users, times 2. For large Geosoft DAP installations, it may be best to reserve an entire disk for the temporary working directory.

22. Click [Next].


The Choose Setup Type dialog is displayed.

23. To install all of the components of the Geosoft DAP Server click the [Complete] button, or to avoid installing the sample datasets you can select the [Custom] option button.


If you selected the [Custom] option in Step 23, the Custom Setup page is displayed.

24. Using the dropdown list, specify if you want to install sample datasets to test your DAP system for the first time. If you have your own data, unselect Sample Datasets. Note that if you do install the sample data, it cannot be removed because the installer ensures that it is maintained and unchanged.

25. Click [Next].


The Ready to Install Geosoft DAP Server dialog is displayed.

26. Click [Install].

Once the file installation process is complete, the installer prompts you to enter your license key:


27. 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].

• If you do not have direct Internet access, you could exchange license information with Geosoft via email. If in doubt, click [Cancel] and establish your license manually. For procedure, see the Installing Geosoft DAP License section.

28. On the next page, click [Finish].

The installer installs the Geosoft DAP Server on your system.

Manually Installing the Geosoft DAP License Key Normal installation of Geosoft DAP Server configures your license. However, if you were in doubt about your license key, Internet access, or e-mail, you may have chosen to cancel the licensing stage. In this case you can use the following procedure to install your Geosoft DAP license.

Note: Always stop and restart the IIS service after installing, setting-up or updating a Geosoft DAP license.

TO INSTALL YOUR GEOSOFT DAP LICENSE

1. If your Geosoft DAP Server computer has a direct Internet connection, or you have an e-mail service, from the Microsoft Start menu, select Start|Programs| Geosoft|DAP Server|License|Setup.

The Geosoft License Manager dialog is displayed.


2. In the License Key field, type the Geosoft DAP Server License Key provided with your Geosoft DAP CD.

3. Click [Internet] or [E-mail].

If you chose the Email option, you will receive an e-mail with instructions on how to install your e-mail license.

If you chose the Internet option, the setup program sends your Geosoft DAP license key to the Geosoft License server, which in turn installs your Geosoft DAP Server license on your server.

You receive a confirmation message similar to the one below if the license key is accepted.

4. Stop and restart the IIS service on the Geosoft DAP Server computer.

Your Geosoft DAP Server becomes licensed and fully functional.

Adding an IDAP Account during the Installation of DAP Server Software

To increase the security of the services that DAP server provides over the Intranet or Internet, the DAP server executes within its own account. The previous version of DAP server installers created a local IDAP account on the computer, which could then be manually replaced by a domain account.

To simplify the installation process, the DAP server installer will continue to create a local IDAP account, but the account can now be switched to a domain account during the installation.

Other changes related to the IDAP account:

• IDAP account information is no longer stored in DAP Server ois.xml file, nor is it editable through the Configuration dialog in DAP Administrator.

• IDAP account no longer needs to be in the ‘log on as a batch job’ policy group under the User Rights Assignment.


• IDAP account is used directly in IIS for anonymous access to the DAP virtual folder so that the DAP server process is run under the IDAP account. To verify the setup of the IDAP account in IIS, first browse to the DAP virtual folder to view its properties via, “Start|Control Panel|Administrative Tools|Internet Information Services”, and the Internet Information Services dialog will be displayed.

Select the Properties for the DAP virtual folder. On the DAP Properties dialog select the Directory Security tab and then in the Anonymous access and authentication control section, click the [Edit] button and the Authentication Methods dialog will be displayed, as shown below.


• Other virtual folders, including GeoDAP, WMS, and GEODAP_images will, by default, continue to use the local IUSR account or the account inherited from the web site.

• For more information on active directory security see Chapter 5: Active Directory Security Model.

Review of Installed DAP Folders and Files

1. Software folders: • DAP Server: C:\Program files\Geosoft\DAP Server • DAP Administrator: C:\Program files\Geosoft\DAP Administrator

2. DAP Server configuration: • C:\Program files\Geosoft\DAP Server\DAP\Config\ois.xml

Note: IDAP account parameters are no longer saved in ois.xml file. 3. New folders and files in DAP 11:

• Disclaimer folder and disclaimer files in HTML format • Style sheet folder and style sheet file in XLST format

4. Abort and Log folders: • DAP Server (abort): C:\Program files\Geosoft\DAP Server\dap\aborts • DAP Server (log): C:\Program files\Geosoft\DAP Server\dap\log


Testing the Geosoft DAP Server Installation

Testing the Geosoft DAP Server installation involves the following:

1. Starting IIS on the server after reboot, if it is not already running (see the Starting Internet Information Services section).

2. Testing Geosoft DAP Server from a web browser (see the Testing Geosoft DAP Servers from a Web Browser section).

3. Installing and configuring the DAP Administrator (see the Installing and Configuring the Geosoft DAP Administrator section).

Starting Internet Information Services

The Internet Information Services (IIS) server must be running before you can connect to Geosoft DAP Server. IIS is normally running after rebooting the system.

TO ENSURE THAT IIS IS RUNNING CORRECTLY

1. From the Start menu, select Settings|Control Panel|Administrative Tools|Internet Information Services.

The Internet Information Services administration console is displayed.

2. To stop and restart the service, do one of the following:


• On the toolbar, click the Start Item, Stop Item or Pause Item buttons, or

• From the Action menu of the IIS Configuration select the Start, Stop or Pause menu items or

• Enter the IISRESET command in the command prompt window.

Testing Geosoft DAP Servers from a Web Browser

You can verify that your Geosoft DAP Server is running correctly from a standard web browser such as Microsoft Internet Explorer.

TO TEST GEOSOFT DAP SERVER FROM INTERNET EXPLORER

1. Open Internet Explorer.

2. Enter the URL for your Geosoft DAP Server as shown in the following figure.

Note that the URL must have “/dap/ois.dll” as the last characters in the name. The above example uses an explicit IP address. You can use a computer name instead.

If you see the window as it appears in the above picture, perhaps with a different version, your Geosoft DAP Server is installed correctly.

Enabling OGC WMS Support

Your Geosoft DAP Server can be configured to behave as an Open GIS Consortium (OGC) Web Map Service (WMS) server (see http://www.opengeospatial.org). A WMS server responds to WMS requests to provide a catalog of the server contents and draw specific entries to an image for display in a web-based application.

http://www.opengeospatial.org/


TO MAKE YOUR DAP SERVER PROVIDE WMS SERVICES:

1. On DAP Server, open “web.config“ at C:\Program Files\Geosoft\DAP Server\wms.

2. Change the DAP_URL line <add key="DAP_URL" value="http://localhost" /> to reflect the name of the DAP WMS server. So for the Geosoft Public DAP Server the line becomes: <add key="DAP_URL" value="http://dap.geosoft.com" />. This is the ONLY line changed in the web.config file.

3. Enter the IISRESET command in the command prompt window.

TO TEST YOUR DAP (WMS SERVICES) SERVER FROM AN OASIS MONTAJ DAP CLIENT:

1. Open Oasis montaj.

2. On the DAP menu, select Find Data with Dapple. The Dapple interface is displayed.

3. On the Servers menu, select Add WMS Server.

The Add a WMS Server dialog is displayed.

4. Type the following in the text box provided: dap.geosoft.com/wms/wms.aspx.

Note: WMS is a powerful and open protocol that enables many WMS-compatible applications to discover data on your DAP server, and to display that data through a simple image rendering. However, WMS does not scale well for large DAP catalogs. We do not recommend the use of WMS for publishing catalogs larger than a few hundred datasets.

Installing and Configuring the Geosoft DAP Administrator

For first-time installation, we would recommend that you install DAP Administrator on the Geosoft 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 sharing settings and permissions are established. For more information, see the “Administering DAP from a Different Computer” section in the DAP Administrator Guide v11.


For instruction on installing the DAP Administrator, see the DAP Administrator Guide v11 (http://www.geosoft.com/resources/tutorials/).

Configuring Geosoft DAP Server for the First Time After successfully installing the DAP Server and DAP Administrator applications, certain steps must be taken to prepare the DAP server for active use. Each DAP server managed via DAP Administrator requires its own configuration.

TO CREATE A NEW CONFIGURATION

1. In the DAP Administrator window, from the File menu, select New Configuration.

The New Configuration dialog is displayed.

2. Specify the URL of the DAP server, along with the administrator password and DAP Catalog directory (defined during the installation of Geosoft DAP Server).

Note: To view the properties of the DAP Server click the Properties button and the Configuration dialog will be displayed.

3. Click [Create].

http://www.geosoft.com/resources/tutorials/


4. A configuration named after the short name of your DAP server (DAP Demo) is created. For instructions on how to publish data on your DAP server, see the DAP Administrator Guide v11 (http://www.geosoft.com/resources/tutorials/).

Troubleshooting If you encounter an error, or if your DAP server does not seem to respond, troubleshoot your server.

TO TROUBLESHOOT YOUR DAP SERVER

1. Check that you have properly installed your Geosoft DAP Server license. To do this, from the Start menu, select All Programs|Geosoft|DAP Server|License|View.



Your license should look similar to the following:

2. If it does not try to install your license again by selecting the Setup option from the License menu. Remember to always stop and restart the IIS service after installing, setting-up or updating a DAP license.

3. Examine the most recent files in the following directories: • C:/program files/geosoft/DAP Server/DAP/Aborts – Stores fatal errors

reported by the server. • C:/program files/geosoft/DAP Server/DAP/Log directory – Contains an

information log of all transactions processed by the DAP server. Unlike the Aborts directory, where the presence of any files indicates a potentially serious problem, the Log directory usually contains files that are not necessarily indicative of any configuration or operational errors.


4. If there are files in the Aborts directory, contact Geosoft with the information in the files to determine a course of action.

5. Restart IIS (either by rebooting the server or by using the procedure described in the Starting IIS section) to handle potential conflicts between IIS and other installed services.

6. If everything else fails, uninstall and reinstall Geosoft DAP Server.

2BChapter 3: Using Geosoft XML 31

Chapter 3: Using Geosoft XML This chapter is a reference manual for developers wishing to communicate with a Geosoft DAP server using XML. A fundamental level of knowledge of XML and DAP Server technology is assumed. For more information on XML, consult the online resources found at www.w3.org/XML.

Geosoft XML is an XML-compliant protocol used to communicate with a data access protocol (DAP) server. Basic XML services include support for catalog information, metadata information, imaging, coordinate translation, and extraction services.

The communication process between a client and a DAP server through Geosoft XML is illustrated by the following simple example. In this example, the client retrieves a catalog of all the datasets stored on the DAP server.

Step 1: A “get_catalog” request is sent to the Geosoft DAP DMS server.

Step 2: The request is received and processed by the server.

Step 3: The server sends an XML response containing all the datasets it has stored. In this example, it has one dataset called “MyDataset” in the directory “MyDirectory”.

Step 4: The catalog response is received by the client and displayed to the user.

http://www.w3.org/XML

32 2BChapter 3: Using Geosoft XML

XML Document Notation Various techniques are used to guide the user through the different syntax elements present in Geosoft XML. Some of these elements are listed below:

• ()* – 0 or more elements contained within the braces may be present

• ()+ – 1 or more elements contained within the braces may be present

• [] – The content is optional

• (a|b) – Either a or b is required but both cannot be present

Geosoft XML Reference

Request – Response

The geosoft_xml tag is the first tag in any request or response. It informs the client or server of the version of Geosoft XML to use.

FORMAT

<geosoft_xml version=”...”> </geosoft_xml>

version The version of the protocol the following elements are encoded with. It has the Major_Version.Minor_Version format.

Each request is enclosed by a start and end request tag, and each response is also enclosed with its own start and end tag.

Request tag: <request namespace=”…”> </request>

namespace Optional parameter used to direct an XML request to DAP server plug-in.

Response tag: <response>

</response>


EXAMPLE

The following is a request for the catalog: <geosoft_xml version=”1.0”> <request> <catalog/> </request> </geosoft_xml>

The DAP server sends the following response: <geosoft_xml version=”1.0”>

<response>

<catalog> (the catalog information is returned here)

</catalog>

</response>

</geosoft_xml>

XML Errors

If an error occurs, an error tag is sent back instead of the expected response tag. The error tag notifies the client that an error occurred while processing a particular request. The client matches the error to the request by the handle attribute in the request. The error is reported in the format described below.

ERROR RESPONSE

<error handle=”…” code=”…”>

<![CDATA[…]]>

</error>

handle Optional client-defined string used by the client to keep track of request and response pairs.

code An integer specifying the particular error that occurred.


EXAMPLE

<geosoft_xml version=”1.0”>

<error code=”502”>

<![CDATA[Error processing EXTRACT_DATA request, operation not supported by this server.]]>

</error>

</geosoft_xml>

Capabilities

Gets capabilities of a server.

REQUEST

<capabilities handle=”…”>

</ capabilities >


RESPONSE

The response provides information about what is allowed for each supported data type. <capabilities handle=”…”>

(<dataset_type name=”…”>

<commands>

(<command name=”…”>

(<parameter name=”…”>

(<attribute name=”…”>

(<value name=”…”>)*

</attribute>)*

</parameter>)*

</command>)*

</commands>

</dataset_type>)*

</capabilities>


DATASET_TYPE The dataset type supported by DAP.


name The name of the dataset type.

COMMAND The command that can be executed on a dataset of this type

name The name of the command that maps to the corresponding XML tag.

PARAMETER The child tag within a command that is further restricted by the following child nodes.

name The name of the parameter, which maps to a corresponding XML tag that is a child node of the specified command.

ATTRIBUTE The attribute of the parameter node that is restricted to the given list of values.

name The name of the attribute within the parameter tag.

VALUE The value that the attribute is allowed to have.

name The value of the attribute.

First, the response outlines each command that is valid for the dataset type. Only dataset-specific commands are listed. These include: dataset_edition, metadata, image, extract, extract_status, extract_cancel, extract_data and default_resolution. All other commands – catalog, catalog_edition, translate_coordinates, translate_bounding_box, and coordinate_system_list – are independent of the dataset type, and are not included in the list of supported commands for a dataset type.

Second, the response lists constraints for particular values that attributes can have in a request. Normally, all child nodes of a request are supported for all dataset types. However, the response may return a list of allowable values for a particular attribute of a given tag. For instance, the “image” request has a “format” child with the “type” attribute. This attribute specifies the format of the image to return. The response can use the “parameter”, “attribute”, and “value” tags to restrict the allowable values for the “type” attribute. The following sample response limits the allowable values for the “type” attribute within the “format” tag to “image/jpeg” and “image/png”.


EXAMPLE


<request>

<capabilities/>

</request>

</geosoft_xml>


<response>

<capabilities>

<dataset_type name=”Grid”>

<commands>

<command name=”IMAGE”>

<parameter name=”format”>

<attribute>

<value name=”image/jpg”/>

<value name=”image/png”/>

</attribute>

</parameter>

</command>

</commands>

</dataset_type>

</capabilities>

</response>

</geosoft_xml>

Configuration

Gets the configuration details of a DAP server.

REQUEST

<configuration handle=”…” />



RESPONSE

<configuration handle=”…”>

<meta>

<class name=”…”>

…

</meta>

</configuration>


META See the Metadata section.

EXAMPLE


<request>

<configuration/>

</request>

</geosoft_xml>



<response>

<configuration>

<meta>

<class name=\"Geosoft\">

<class name=\"Core\">

<class name=\"DAP\">

<class name=\"Configuration\">

…

</class>

</class>

</class>

</class>

</meta>

</configuration>

</response>

</geosoft_xml>

Catalog

Gets the list of datasets currently stored on a DAP server.

REQUEST

<catalog handle=”…” index =”…” max_results=”…” keywords=”…” count=”true|false”> <bounding_box maxX=”…” maxY=”…” minX=”…” minY=”…”> <coordinate_system datum=”…” protection=”…” units=”…”/> </bounding_box> <filter path=”...” depth=”…”/> </catalog>


index Optional; the number of datasets to skip before starting to return the catalog content.

max_results Optional; the maximum number of results to return governed by an in-order tree traversal.

keywords Optional; a search string.

count Optional; if True, only the number of datasets that matchs the query is returned.


FILTER (Optional)

path A folder path variable that can be used to filter the list of datasets returned (in addition to the spatial and/or keyword criteria).

depth Optional; the number of levels to return beginning at the path location.

Examples: /Global/ – returns all datasets under the Global directory. /Global/@Global_Coastlines.hmap – returns the specific dataset, Global_Coastlines.hmap, if it exists.

BOUNDING_BOX (optional)

maxX The maximum X coordinate.

maxY The maximum Y coordinate.

minX The minimum X coordinate.

minY The minimum Y coordinate.

COORDINATE_SYSTEM

For information, see the Coordinate Systems section.

RESPONSE

< catalog handle=”…”>

<collection name=”…”>

(<item name=”…” title=”…” type=”…” edition=”…”>

<bounding_box maxX=”…” maxY=”…” minX=”…” minY=”…”/>

</item>)+

(<collection name=”…”>…</collection>)*

</collection>

<count value=”…”/>

</catalog>

<configuration version=”…”/>


COLLECTION A directory containing datasets and/or other directories.

name The name of the directory.

ITEM A dataset.

mailto:/Global/@Global_Coastlines.hmap


name A unique name for the dataset used by the DAP server. It is used to specify a particular dataset in any request that has a dataset parameter.

title User-defined name for the dataset.

type Type of the dataset, which corresponds to one of the dataset types returned by the capabilities response. E.g., image, grid, or document.

edition The current edition of the dataset.

BOUNDING BOX The bounding box for the dataset, always returned in WGS 84.

maxX The maximum x coordinate.

maxY The maximum y coordinate.

minX The minimum x coordinate.

minY The minimum y coordinate.

COUNT Present if the catalog request only asked for a dataset count.

value The number of datasets that match the search criteria.

CONFIGURATION

The current version of the server. Used to invalidate the client cache.

version The version of the server.

EXAMPLE


<request>

<catalog/>

</request>

</geosoft_xml>



<response>

<catalog edition=”dog”>

<collection name=”Global”>

<item name=”Global_coastlines.hmap” title=”World Costlines” type=”Image”>

<bounding_box maxX=”180” maxY=”90” minX=”-180” minY=”-90”/>

</item>

</collection>

</catalog>

</response>

</geosoft_xml>

Catalog Hierarchy

Gets the list of folders that have datasets currently stored on a DAP server.

REQUEST

<catalog_hierarchy handle=”…” keywords=”…”> <bounding_box maxX=”…” maxY=”…” minX=”…” minY=”…”> <coordinate_system datum=”…” protection=”…” units=”…”/> </bounding_box> </catalog_hierarchy>


keywords Optional search string.

BOUNDING_BOX (optional)





COORDINATE_SYSTEM

For information, see the Coordinate Systems section.


RESPONSE

< catalog_hierarchy handle=”…”>

<collection name=”…”>

(<collection name=”…”>…</collection>)*

</collection>

</catalog_hierarchy>



COLLECTION A directory containing datasets and/or other directories.

name The name of the directory.

CONFIGURATION



EXAMPLE


<request>

<catalog_hierarchy/>

</request>

</geosoft_xml>


<response>

<catalog edition=”dog”>

<collection name=”Global”>

</collection>

</catalog>

</response>

</geosoft_xml>


Catalog Edition

Gets the current catalog edition.

REQUEST

<catalog_edition handle=”…”/>


RESPONSE


<catalog_edition handle=”…” edition=”…” />


edition The current edition of the catalog.

CONFIGURATION



EXAMPLE


<request>

<catalog_edition/>

</request>

</geosoft_xml>


<response>

<configuration version=”432”/>

<catalog_edition edition=”dog”/>

</response>

</geosoft_xml>


Dataset Edition

Gets the edition of a dataset.

REQUEST

<dataset_edition handle=”…” name=”…”/>


name The name of the dataset as given by the name attribute in the item tag of a catalog response.

RESPONSE

<dataset_edition handle=”…” edition=”…” />


edition The current edition of the requested dataset.

EXAMPLE


<request>

<dataset_edition name=”global_coastlines.hmap”/>

</request>

</geosoft_xml>


<response>

<dataset_edition edition=”dog”/>

</response>

</geosoft_xml>

Metadata

Retrieves metadata for a dataset.

REQUEST

<metadata handle=”…” name=”…”>

</metadata>



name The name of the dataset for which to retrieve metadata, as given by the name attribute in the item tag of a catalog response.

RESPONSE

<meta handle=”…”>

<class name=”…” type=”…”>

(<attribute name=”…” type=”…” value=”…”/>)*

(<table>

(<item name=”X”>

(<attribute name=”…” type=”…” value=”…”/>)*

</item>)*

</table>)*

(<class name=”…” type=”…”>)*

</class>

</meta>


CLASS Class containing a collection of attributes, tables, and/or other classes.

name The name of the class.

type The type of the class

ATTRIBUTE An attribute of the class.

name The name of the attribute.

type The type of the attribute.

value The value of the attribute.

TABLE A collection of attributes in table format.

ITEM A row of attributes in the table.

name The name of the row.


EXAMPLE


<request>

<metadata name=”Global_coastlines.hmap”/>

</request>

</geosoft_xml>


<response>

<metadata>

<class name="Geosoft">

<attribute name="ReferenceURL" type="/Predefined/Types/String" value="www.geosoft.com/schemas/geosoft.schema"/>

<attribute name="Description" type="/Predefined/Types/String" value="GEOSOFT metadata objects"/>

<class name="Data">

<attribute name="CentreY" type="/Predefined/Types/R8" value="2.531514"/>

<attribute name="CentreX" type="/Predefined/Types/R8" value="0" />

</class>

</class>

</metadata>

</response>

</geosoft_xml>


Image

Renders a series of datasets into a layered picture.

REQUEST

<image handle=”…”>

<format type=”…” transparent=”(true|false)” background=”…”/>

<bounding_box maxX=”…” maxY=”…” minX=”…” minY=”…”>

<coordinate_system datum=”…” protection=”…” units=”…”/>

</bounding_box>

<resolution height=”…” width=”…”/>

<layers base_map=”…” index_map=”…”>

(<dataset name=”…”>)+

</layers>

</image>


FORMAT

type The requested image type. The valid types are defined in the capabilities response.

transparent An optional True or False value; specifies whether the image should be transparent.

Background Optional background colour for the image, specified in RGB (0xRRGGBB).

BOUNDING_BOX





COORDINATE_SYSTEM For information, see the Coordinate Systems section.

RESOLUTION

height The height of the picture in pixels.


width The width of the picture in pixels.

LAYERS

base_map An optional True or False value; specifies whether to draw the base map as a layer.

index_map An optional True or False value; specifies whether to draw the index map as a layer.

DATASET

name The name of the dataset to draw as one of the layers of the image, as given by the name attribute in the item tag of a catalog response.

RESPONSE

<image handle=”…”>

<picture>

…

</picture>

</image>


PICTURE The picture encoded in base64.


EXAMPLE


<request>

<image>

<format type=”image/jpeg”/>

<bounding_box maxX=”180” maxY=”90” minX=”-180” minY=”-90”>

<coordinate_system datum=”WGS 84”/>

</bounding_box>

<resolution height=”300” width=”600”/>

<layers>

<dataset name=”Global_coastlines.hmap”/>

<dataset name=”Global_rivers.hmap”/>

</layers>

</image>

</request>

</geosoft_xml>


<response>

< image>

<picture>

abcdefgdvafldafhfdkvczkhfdsafdaj#

</picture>

</ image>

</response>

</geosoft_xml>

Extract Data

Retrieves data for a dataset. Because the data extraction process may take time, extracting data involves first requesting the server to begin the extraction process. The process is then checked periodically to determine its status. This enables an application to provide periodic status information. Once the process is completed, the data can be requested.

BEGIN EXTRACT REQUEST

Starts the extraction process for a particular dataset.


<extract handle=”…” user_name=”…” password=”…”>

<dataset name=”…”/>

<format type=”…”/>


<coordinate_system datum=”…” projection=”…” units=”…”/>

</bounding_box>

<resolution value=”…”/>

</extract>


user_name Optional user name of the client.

password Optional password for the user.

DATASET

name The name of the dataset to extract, as given by the name attribute in the item tag of a catalog response.

FORMAT

type The requested image type. The type valid types are given in the capabilities response and depend on the type of the dataset.

BOUNDING_BOX






RESOLUTION

value The resolution to extract the data at.

BEGIN EXTRACT RESPONSE

The parameters returned represent the actual parameters that the extracted data conforms to. These may differ from the requested parameters due to the format of the raw data.


<extract handle=”…”>

<key name=”…”/>

<dataset name=”…”/>

<format type=”…”/>


<coordinate_system datum=”…” projection=”…” units=”…” local_datum=”…”/>

</bounding_box>


</extract>


KEY

name A unique identifier of the extraction process.

DATASET

name The name of the dataset that is being extracted.

FORMAT

type The format the data is being extracted to. One of the formats listed in the capabilities response for this dataset type.

BOUNDING_BOX






RESOLUTION

value The actual data extraction resolution.


EXTRACT STATUS REQUEST

Gets the status of an extraction process. <extract_status handle=”…” key=”…”>

</extract_status>


key The key given to the client on an extract response that specifies the particular data extraction process.

EXTRACT STATUS RESPONSE

Returns the status of an extraction process. <extract_status handle=”…” key=”…”>

<status value=”…” progress=”…” status=”…”/>

</extract_status>



STATUS

value The current state of the extraction process: CANCELLED, IN_PROGRESS, or COMPLETED.

progress The completion percentage of the extraction process

status The current task the extraction process is working on.

CANCEL EXTRACTION

Cancels an extraction process. <extract_cancel handle=”…” key=”…”>

</extract_cancel>



The response to the extract_cancel request is an extract_status response with status=CANCELLED.

EXTRACT DATA REQUEST


Gets the data from an extraction process that has completed. <extract_data handle=”…” key=”…”>

</extract_data>



EXTRACT DATA RESPONSE

Gets the data from an extraction process that has completed. The data is returned encoded in base64.

<extract_data handle=”…” key=”…”>

…

</extract_data>



Note: The data is encoded in base64.

EXAMPLE

Begin extraction: <geosoft_xml version=”1.0”>

<request>

<extract>

<format type=”geosoft/compressed”/>

<bounding_box maxX=”180” maxY=”90” minX=”-180” minY=”-90”>


</bounding_box>

<resolution value=”0.01”/>

<dataset name=”Global_globeDEM.hgd”/>

</extract>

</request>

</geosoft_xml>



<response>

<extract>

<key name=” hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”/>

<dataset name=”Global_globeDEM.hgd”/>

<format type=”geosoft/compressed”/>

<bounding_box maxX=”-100” maxY=”35” minX=”-96” minY=”32”>


</bounding_box>

<resolution value=”0.01”/> </extract>

</response>

</geosoft_xml>


Periodically check the status of the extraction using the key returned by the extract request:


<request>

<extract_status key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”/>

</request>

</geosoft_xml>


<response>

<extract_status key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”>

<status value=”IN_PROGRESS” progess=”20”/>

</extract_status>

</response>

</geosoft_xml>

After the extract_status response returns “100” as the progress, you can begin the actual data extraction. The data is returned as a ZIP file using base64 encoding:


<request>

<extract_data key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”/>

</request>

</geosoft_xml>


<response>

<extract_data key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”>

fdaklfjdafhrueanklfzhsdfahdfkl;sfjafsafkl;hafd

</extract_data>

</response>

</geosoft_xml>


The extraction process can be stopped at any time by sending an extract_cancel request: <geosoft_xml version=”1.0”>

<request>

<extract_cancel key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”/>

</request>

</geosoft_xml>


<response>

<extract_status key=”hafdsfsdnzjhfdsafldhvbzjnfdsahfdas”>

<status value=”CANCELLED”/>

</extract_status>

</response>

</geosoft_xml>

Translate Coordinates

Translates a series of coordinates from one projection to another.

REQUEST

<translate_coordinates handle=”…”>

<input>

<coordinate_system datum=”…” projection=”…” units=”…” />

</ input >

<output>


</ output >

(<point x=”…” y=”…” z=”…”/>)*

</translate_coordinates>


INPUT The input coordinate system.

OUTPUT The output coordinate system



POINT

x The x coordinate to translate.

y The y coordinate to translate.

z The optional z coordinate to translate.

RESPONSE

<translate_coordinates handle=”…”>

(<point x=”…” y=”…” z=”…”/>)*



POINT

x The translated x coordinate.

y The translated y coordinate.

z The optional translated z coordinate.

EXAMPLE


<request>

<translate_coordinates>

<input>

<coordinate_system datum=”NAD83”/>

</input>

<output>

<coordinate_system datum=”[NAD27] MEAN CONUS”/>

</output>

<point x=”-100.5” y=”36.122”/>

<point x =”-100.5” y=”36.233”/>


</request>

</geosoft_xml>



<response>

<translate_coordinates>

<point x=”-100.5000123” y=”36.1219884”/>

<point x =”-100.5000121” y=”-36.2329882”/>


</response>

</geosoft_xml>

Translate Bounding Box

Translates a bounding box from one projection to another.

REQUEST

<translate_bounding_box handle=”…”>



</bounding_box> <coordinate_system datum=”…” projection=”…” units=”…”/>


</translate_bounding_box>


COORDINATE_SYSTEM

The first coordinate system (the one nested under the translate_bounding_box tag) is the coordinate system of the bounding box.

The second coordinate system is the coordinate system required for the returned bounding box.

See the Coordinate Systems section for more information on how to describe a coordinate system.

BOUNDING_BOX





RESOLUTION (optional)


value This distance in the input coordinate system is converted to an equivalent distance in the output coordinate system based on the scale difference at the centre of the bounding box.

RESPONSE

<translate_bounding_box handle=”…”>



</ translate_bounding_box>


BOUNDING_BOX





RESOLUTION Optionally returned when a resolution was supplied in the input request.

value The new resolution for the new bounding box.

EXAMPLE


<request>

<translate_bounding_box>

<bounding_box maxX=”-101” maxY=”49” minX=”-96” minY=”45”>

<coordinate_system datum=” NAD83 to WGS 84 (4)”/> </bounding_box>

<coordinate_system datum=”[NAD27] MEAN CONUS”/>



</request>

</geosoft_xml>



<request>

<translate_bounding_box>

<bounding_box maxX=”-101.00023” maxY=”49.00014” minX=”-96.000192” minY=”45.000133”/>



</request>

</geosoft_xml>

Default Resolution

Gets the default resolution for a given datatype and bounding box.

REQUEST

<default_resolution handle=”…” type=”…”>


</default_resolution>


type The type of data contained within the bounding box: Grid, Image, Data, or Map.

BOUNDING_BOX





RESPONSE

<default_resolution handle=”…”>




RESOLUTION

value The default resolution to extract the data at.


EXAMPLE


<request>

<default_resolution type=”Map”>

<bounding_box maxX=”-101” maxY=”49” minX=”-96” minY=”45”/>


</request>

</geosoft_xml>


<request>

<default_resolution>



</request>

</geosoft_xml>

List Supported Coordinate Systems

Gets a list of the supported coordinate systems.

REQUEST

<coordinate_system_list handle=”…” list_type=”…” datum=”…”>

</coordinate_system_list>


list_type The type of list to return; one of: “datum” “local datum description” “local datum name” “projection” “units”

datum Optional; specifies a datum to narrow down the list to the supported projections, units, or local datums for the particular datum. If a local datum description or local datum name is specified as list_type, a datum must be provided.


RESPONSE

<coordinate_system_list handle=”…” >

(<item name=”X”/>)*



ITEM

name The name of a list item.

EXAMPLE


<request>

<coordinate_system_list list_type=”datum”/ >

</request>

</geosoft_xml>


<response>

<coordinate_system_list>

<item name=”WGS 84”/>

<item name=”NAD27”/>

<item name=”NAD83”/>


</response>

</geosoft_xml>

Coordinate Systems Any Geosoft XML request that includes a coordinate (such as a bounding_box), also includes a coordinate_system definition. You can describe coordinate systems in one of two ways:

<coordinate_system datum=”…” projection=”…” units=”…”/>

OR <coordinate_system esri=”…”/>

Coordinate systems can be either geographic or projected. Geographic coordinate systems use longitude, latitude coordinates in degrees, and only require the datum to be defined.


Projected coordinates use a map projection to define map coordinates in certain units of length on a datum. For example, the “UTM Zone 15N” projection defines coordinates in metres using a specific Transverse Mercator projection.

The coordinate system description in Geosoft XML enables you to define systems by name, by EPSG code, or explicitly by specifying all parameters on the projection. Supported names for the various coordinate systems can be found in the projection CSV tables in your “Oasis montaj/csv” directory.

Note: The above tables may also be found in the “…/csv” directory of each of the installed DAP servers. The projection.csv tables on all DAP servers should be identical.

datum Specifies the datum of the coordinate system in one of the following three ways:

By datum name, which can be any name returned for list_type=“datum”, list_type=“local datum description”, or list_type=“local datum name” in response to a COORDINAT_SYSTEM_LIST request.

By an EPSG code number for the datum or for a local datum transform (refer to http://www.epsg.org/).

By the name and parameters specified for a datum as follows: ”Datum=name,major_axis,flattening,prime_meridian” The major axis must be defined in metres, and the prime meridian is in degrees relative to Greenwich.

Note that if you expect the/a transformation to take place between datums, you must use the first option with local datum description or local datum name, or the second option using a local datum transform code. This will fully describe the local datum transform information required to translate coordinates between datums.

projection Specifies the projection of the coordinate system. This is only required for projected coordinate systems. The projection can be defined in one of the following three ways:

By projection name, which can be any name returned for list_type=“projection” in response to a COORDINAT_SYSTEM_LIST request.

By an EPSG code number for the projection (refer to http://www.epsg.org/).

By the name and parameters specified for a projection as follows: Projection=name,method,length_units, P1,P2,P3,P4,P5,P6,P7,P8 where name is your projection name, method is one of the methods listed in the Projection Transformation Methods table, length_units is one of the length units listed in the Length Units table, and the

http://www.epsg.org/

http://www.epsg.org/


parameters P1 through P8 are the method-specific parameters listed for each method the Projection Transformation Methods table. A method may have fewer than 8 parameters, in which case the parameters must be provided in the order listed in the Projection Transformation Methods table.

Notes:

• Distance references must be specified in length_unit.

• Geographic references (latitudes and longitudes) are specified in degrees.

• Longitudes in the Western hemisphere are negative.

• Latitudes in the Southern hemisphere are negative.

• Longitudes are relative to the prime meridian of the datum.

units Optional coordinate system units of length, if different from length_unit defined by Projection. The unit name can be any name returned for list_type=”units” in response to a COORDINAT_SYSTEM_LIST request. Length units may also be defined in the form: units=“name,factor” where name is your length unit name and factor is the multiplication factor that converts your length unit to metres.

esri The coordinate system may be described using an ESRI coordinate system string as defined for ArcGIS version 8 or later. Refer to the ESRI documentation for information on how to describe an ESRI coordinate system. Note that the ESRI coordinate system descriptions do not explicitly describe a preferred local datum transform method; although a local datum transform can be inferred from many datum names. If you intend your data to be transformed across datums, you should test to ensure that your results are as you expect.

EXAMPLES

The following describes geographic coordinates on the “ARC 1960” datum, which is widely used in Africa:

<coordinate_system datum="Arc 1960"/>

The following describes a projected coordinate system on the same datum: <coordinate_system datum="Arc 1960" projection="UTM zone 37S"/>

Although the definition of units is redundant, the following two examples also define units, first by name only, and then by name and conversion factor:

<coordinate_system datum="Arc 1960" projection="UTM zone 37S" units="m"/> <coordinate_system datum="Arc 1960" projection="UTM zone 37S" units="m,1.0"/>

This example explicitly defines the “ARC 1960” spheroid parameters:


<coordinate_system datum="Arc 1960,6378249.145000,293.465,0.0" projection="UTM zone 37S"/>

This example explicitly defines the UTM zone 37S projection parameters: <coordinate_system datum="Arc 1960" projection="UTM zone 37S,Transverse Mercator,m,0,39,,,0.9996,500000,10000000"/>

All previous examples are appropriate only for coordinate translations on the same datum (ARC 1960). If the coordinates require a datum change, a local datum transformation method must be defined for the datum. The following two examples show the same local datum transform description. The first uses the area descriptive string (from ldatum.csv), and the second uses the EPSG standard name (from datumtrf.csv):

<coordinate_system datum="Arc 1960 to WGS 84 (3)" projection="UTM zone 37S"/>

<coordinate_system datum="[Arc 1960] Tanzania" projection="UTM zone 37S"/>

The following examples use the EPSG code number to describe the coordinate systems. The first example describes the datum only, and the second example describes the local datum transform:

<coordinate_system datum=4210 projection=16137/>

<coordinate_system datum=1285 projection=16137/>


The following is an ESRI string example that describes geographic coordinates on the ARC 1960 datum:

<coordinate_system esri=GEOGCS["Arc_1960", DATUM["Arc_1960", SPHEROID["Clarke_1880_(RGS)",6378249.145,293.4650000298]], PRIMEM["Greenwich",0], UNIT["Degree",0.0174532925199432955]]/>

The following is an ESRI string example that describes a projected coordinate system using UTM zone 37S:

<coordinate_system esri=PROJCS["Arc_1960_UTM_zone_37S", GEOGCS["Arc_1960", DATUM["Arc_1960", SPHEROID["Clarke_1880_(RGS)",6378249.145,293.4650000298]], PRIMEM["Greenwich",0], UNIT["Degree",0.0174532925199432955]], PROJECTION["Transverse_Mercator"], PARAMETER["False_Easting",500000], PARAMETER["False_Northing",10000000], PARAMETER["Central_Meridian",39], PARAMETER["Scale_Factor",0.9996], PARAMETER["Latitude_Of_Origin",0], UNIT["Meter",1]]/>

PROJECTION TRANSFORMATION METHODS

Projection Method Required Parameters Hotine Oblique Mercator Latitude of projection centre

Longitude of projection centre Azimuth of initial line Angle from Rectified to Skew Grid Scale factor on initial line False Easting False Northing

Laborde Oblique Mercator Latitude of projection centre Longitude of projection centre Azimuth of initial line Scale factor on initial line False Easting False Northing

Lambert Conic Conformal (1SP) Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

Lambert Conic Conformal (2SP) Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin


Projection Method Required Parameters Lambert Conformal (2SP Belgium) Latitude of first standard parallel

Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin

Mercator (1SP) Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

Mercator (2SP) Latitude of first standard parallel Longitude of natural origin False Easting False Northing

New Zealand Map Grid Latitude of natural origin Longitude of natural origin False Easting False Northing

Oblique Stereographic Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

Polar Stereographic Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

Swiss Oblique Cylindrical Latitude of projection centre Longitude of projection centre Easting at projection centre Northing at projection centre

Transverse Mercator Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

Transverse Mercator (South Oriented) Latitude of natural origin Longitude of natural origin Scale factor at natural origin False Easting False Northing

*Albers Conic Latitude of first standard parallel Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin


Projection Method Required Parameters *Equidistant Conic Latitude of first standard parallel

Latitude of second standard parallel Latitude of false origin Longitude of false origin Easting at false origin Northing at false origin

*Polyconic Latitude of false origin Longitude of false origin Scale factor at natural origin Easting at false origin Northing at false origin

LENGTH UNITS

Unit Description Factor to Metres

m Metre 1.0 ft Foot 0.3048 ftUS US survey foot 0.3048006096012 ftMA Modified American foot 0.3048122529845 ftCla Clarke's foot 0.3047972651151 ftInd Indian foot (Clarke) 0.3047995102481 ftSe foot (Sears) 0.3047994715387 lkCla link (Clarke) 0.201166194976 lkBen link (Benoit) 0.2011678249438 lkSe link (Sears) 0.2011676512155 chBen chain (Benoit) 20.1167824943759 chSe chain (Sears) 20.1167651215526 ydSe yard (Sears) 0.914398414616 ydInd Indian yard 0.9143985539701 fathom Fathom 1.8288 nautmi nautical mile 1852.0 mGer German legal metre 1.0000135965 dega degrees (angular) n/a

3BChapter 4: Creating Web Applications 69

Chapter 4: Creating Web Applications Geosoft DAP catalogs and delivers data in support of “thick” clients such as Oasis montaj, ArcGIS, and MapInfo. Through WMS and Geosoft XML, Geosoft DAP servers also support the development of web applications for the discovery and downloading of data using a web browser. This chapter explains how to build web applications using Geosoft XML. It is assumed that you have a working knowledge of IIS, Microsoft VisualStudio.NET, ASP.NET, and C#.

Prerequisites • Internet Information Server (IIS) 5.0 or above, or Apache v2.0.44 or above (Note

that, IIS 6.0 or above is recommended).

Setting Up an Application Development Environment

TO SET UP A DEVELOPMENT ENVIRONMENT

1. In a text editor open geodap.csproj, this file can be found in the \geosoft\DAP Server\geodap\ directory.

Set PreBuildEvent = “” on line 19.

2. Save and close geodap.csproj.

3. In Microsoft Visual Studio.NET 2003 open geodap.sln, this file can be found in the \geosoft\DAP Server\geodap\ directory.

Remove the dapxmlclient and geonet references.

4. Add new references to dapxmlclient.dll and geonet.dll. The .dll files can be found in the \geodap\bin directory.

Directory Structure Controls User controls used to create HTML for the user interface.

Home The main page of the website, used to control the workflow.

Resources Hold string tables and other resources for multi-language support.

Scripts Javascript scripts used to drive the website.

src Collection of C# code.

Style sheets Hold the style sheets used to control the user interface.

User_controls User controls used to hold web controls inside the datagrid cells.

70 4BChapter 5: Using the GIS Legend Editor

Chapter 5: Using the GIS Legend Editor 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 montaj, ArcMAP, and MapInfo.

The legend files are created using Geosoft GIS Legend Editor. This application provides a simplified interface to assist you in setting the display attributes for shape files.

This chapter walks you through the process of creating a GIS legend file for an ESRI shape file containing drill hole location data.

The dataset, Drillholes.shp, can be found in your C:\Program Files\Geosoft\Oasis montaj\data\various directory if you chose to install the samples during the setup of Oasis montaj.

SPF Features and Attributes DAP supports the following SPF features:

• Point2D – Two-dimensional point data

• Text2D – Text rendered at two-dimensional point locations

• Line2D – Two-dimensional line data

• Polygon – Two-dimensional polygon data Note: Additional SPF features will be added to the system in future releases.

Each of the features has a set of display attributes listed in the following table. Point2D

Font String Name of the character set to use

Font Style Enum Regular, Bold, Italic, Underline, or Strikethrough

Symbol Integer Character index to display at each point

Symbol Angle Double Rotation of the symbol

Symbol Color Color Color of the symbol

Symbol Color Transparency Integer 100 – Opaque, 0 – Transparent

Symbol Fill Color Color Color to fill the symbol with

Symbol Fill Color Transparency

Integer 100 – Opaque, 0 – Transparent

Symbol Size Double Size of symbol in millimetres

Text2D

4BChapter 5: Using the GIS Legend Editor 71

Font String Name of the character set to use

Font Angle Double Rotation of the text

Font Background Color Color Color to fill in the background of the text

Font Background Color Transparency

Integer 100 – Opaque, 0 – Transparent

Font Color Color Color of the text

Font Color Transparency Integer 100 – Opaque, 0 – Transparent

Font Reference Enum Bottom Left, Right, Center

Middle Left, Right, Center

Top Left, Right Center

Font Size Double Size of the font in millimetres

Font Style Enum Regular, Bold, Italic, Underline, or Strikethrough

Value String Text string to display at each point

Line2D

Line Color Color Color of the line

Line Color Transparency Integer 100 – Opaque, 0 – Transparent

Line Pitch Double Size of gaps in the line pattern

Line Style Enum List of available line styles

Line Thickness Double Thickness of the line in millimetres

Polygon

Line Color Color Color of the line

Line Color Transparency Integer 100 – Opaque, 0 – Transparent

Line Pitch Double Size of gaps in the line pattern in millimetres

Line Style Enum List of available line styles

Line Thickness Double Thickness of the line in millimetres

Fill Color Color Color to fill in the polygon

Fill Color Transparency Integer 100 – Opaque, 0 – Transparent

Fill Pattern Enum List of the available fill patterns

Fill Pattern Angle Double Rotation of the fill pattern

Fill Pattern Line Thickness Double Thickness of the lines within the pattern as a percentage of the tile size

Fill Pattern Style Enum Controls the tiling of the pattern: Rectangle, Random, Diagonal and Triangular (only valid in Oasis montaj)


Fill Pattern Tile Density Double Density of the fill pattern

Fill Pattern Tile Size Double Tile size in millimetres

GIS Legend Editor Interface The Geosoft Legend Editor interface is displayed below:

The window contains two menus:

• File – Enables you to open an ESRI shape file to create/edit drawing attributes, save the attribute changes, and close the window.

• View – Helps you (re)display the Legend Explorer pane.

The window contains two main panes:

• Legend Explorer on the left – Manages SPF features (for which drawing attributes are defined) and lookup attribute tables.

• Workspace on the right – Displays the attributes created for the SPF features and lookup tables.

Constant Drawing Attributes This section walks you trough sample procedures used to define the following attributes:

• Point2D

• Text2D


Defining Point2D Attributes

TO SET CONSTANTS FOR EACH DRAWING ATTRIBUTE

1. Start Oasis montaj and add the DAP menu by loading the dapprep.omn file.

2. Create a new subdirectory under your DAP data root called Legends.

3. Copy C:\Program Files\Geosoft\Oasis montaj\various\data\Drillholes.shp and all the associated files (Drillholes.dbf, Drillholes.prj, Drillholes.shp.GeosoftMeta, Drillholes.shx) to the newly created Legends subdirectory.

4. From the DAP Menu, select GIS Legend Editor.

The Geosoft Legend Editor window is displayed.

5. From the File menu, select Open.

The Open dialog is displayed.

6. Using the [Browse] button, locate the Drillholes.shp file in the Legends directory and click [Open].

The Drillholes.shp file is displayed in the Legend Explorer pane.

The Legend Explorer pane enables you to navigate through the different parts of a legend file.

7. Click the “Drillholes.shp” node in the Legend Explorer pane to expand the tree, and then click the “Sections” node to display the “SPF” node.

8. Right-click the “SPF” node.


9. From the Add Feature pop-up menu, select Point2D to create drawing attributes required to render the point locations in the Drillholes.shp file.

The “Point2D” node is added under the “SPF” node in the Legend Explorer pane.

10. Double-click the “Point2D” node

The drawing attributes are displayed in the Workspace pane.

Note: The Point2D SPF feature was selected because the Drillholes.shp file contains only two-dimensional point data. For GIS files with two-dimensional point data, you can also define Text2D attributes (see the Text2D Attributes section).

Note: By default, none of the drawing attributes are defined. 11. To specify a symbol font, select the row containing the Font attribute and click the

browse button ( ).


The Font dialog is displayed.

12. In the Enter Value field, type “ESRI Geometric Symbols”. Note: You must enter double quotes to include the font name. The current version

requires you to manually enter the name of the font to use. Note: If one of the fields in the shape file contains the symbol font names to render

the locations, you can select the Field option button, and then select the field name from the Select Field dropdown list. This enables you to draw the point locations using symbols from the different fonts as defined in the selected field.

13. Click [OK].


The Font dialog closes.

14. To specify a symbol, select the row containing the Symbol attribute and click the browse button ( ).

The Symbol dialog is displayed.

15. In the Enter Value field, type “37”. “37” corresponds to a solid square in the chosen ESRI font.

16. Click [OK].


The Symbol dialog closes.

17. To specify a symbol colour, select the row containing the SymbolColor attribute and click the browse button ( ).

The Color dialog is displayed.

18. In the Value section, click [Select Color] and select a color from the color palette.

19. Click [OK] to save the change.

20. To specify a symbol size (in millimetres), follow the same procedure as for the symbol color.


Note: You can leave all other attributes undefined. Default values are used for attributes that are not set explicitly in the GIS legend file. For example, the default value for SymbolAngle is 0.

Note: Some of the drawing attributes may be ignored even if defined, depending on the type of the DAP client application used. For example, SymbolFillColor may not be used when drawing symbols in ArcMap because this client application uses the same color to draw the edge and fill the symbol.

The resulting attribute definitions should look as follows:

21. From the File menu, select Save.

The legend file is stored in XML format. It has the same name as the shape file it is defined for, with the “geosoft_legend” extension. The legend file is saved in the same directory as the shape file.

22. From the File menu, select Exit.

The Geosoft Legend Editor window closes.

23. Use any text editor to view the content of the XML file you created: <geosoft_xml> <legends> <legend name="SPF"> <feature name="Point2D"> <attribute expression="geosoft_symbol=37" /> <attribute expression="geosoft_symbol_size=8" /> <attribute expression="geosoft_symbol_color="R255G0B0"" /> <attribute expression="geosoft_font="ESRI Geometric Symbols"" /> </feature> </legend>


<tables /> </legends> </geosoft_xml>

Note: You can manually edit the content of the XML legend file after you become more familiar with the format and schema of the GIS legend file.

24. To view the drawing attributes in any DAP client application, catalog the sample shape file, and then retrieve the points from the DAP server to a client application.

The following Geosoft map shows the data points downloaded from the shape file.

Setting Text2D Attributes

This section describes the procedure used to post the data (text strings) contained in the Elements field of the Drillholes.shp file, in addition to the symbols rendered at each point location.

TO DEFINE THE TEXT2D ATTRIBUTES

1. In the Geosoft Legend Editor window, open the …\Legends\Drillholes.shp file.

2. In the Legend Explorer pane, browse from the root of the tree to the “SPF” node.

3. Right-click the “SPF” node.

4. From the menu that pops up, select Text2D.

5. Double-click the “Text2D” node in the Legend Explorer pane to display the Text2D attributes in the Workspace pane, where you can set the text font, font color, size, and other attributes. You can use the steps described in the Point2D Attributes section to set those attributes to constant values.

6. Select the Value attribute and click the browse button ( ).


The Text dialog is displayed.

7. Select the Field option button.

8. From the Select Field drop-down list, select Elements.

9. Click [OK]. Note: If you enter a constant text string in the Enter Value field, for example, Label,

the text string Label will be drawn at all point locations in the Drillholes.shp file.

The drawing attributes you defined for the Text2D feature should be similar to the following:


10. From the File menu in the Geosoft Legend Editor window, select Save.

11. Open the XML file again is a text editor.

The following new section appears in the file: <feature name="Text2D"> <attribute expression="geosoft_text=ELEMENTS" /> <attribute expression="geosoft_font="Arial"" /> <attribute expression="geosoft_font_style=2" /> <attribute expression="geosoft_font_size=2" /> <attribute expression="geosoft_font_color="R0G0B0"" /> </feature>

12. Retrieve the data from the Drillholes.shp file using the Get DAP Data window within Oasis montaj.

The new Geosoft map should look similar to the following:

Note: You do not need to re-catalog the shape file after modifying the XML legend file. The new attributes will automatically become available once the modified legend file is saved.

Drawing Attribute Tables You can use lookup attribute tables to define drawing attributes for GIS datasets. This section explains the procedure using the Drillholes.shp file as an example.

Note: Backup Drillholes.shp.geosoft_legend file if you would like to keep the current version.

TO DEFINE AND APPLY DRAWING ATTRIBUTE TABLES

1. In the Geosoft Legend Editor window, open the …\Legends\Drillholes.shp file.

2. In the Legend Explorer pane, browse from the root of the tree to the “Tables” node.

3. Right-click the “Tables” node.

4. From the menu that pops up, select Add Table.


The Add Table dialog is displayed.

5. To create a lookup table containing a list of colors: a. In the Name field, type “Color”. b. From the Type drop-down list, select Name Lookup. c. From the Value Type drop-down list, select Color. d. From the Field drop-down list, select Elements. (The Field drop-down list

displays all the fields found in the Drillholes.shp file.) e. Click [OK].

The Add Table dialog closes.

6. Expand the “Tables” node to display the new table you created.

7. Double-click the “Color” node to display the Color definition in the Workspace pane.

The Color definition has two columns:

• Name – Displays a list of unique entries in the Elements field of Drillholes.shp file

• Value – Defaults all colors to black


8. Modify the Color attributes by selecting the required colors from the Color drop-down lists. The resulting colors should be similar to those shown in the picture above.

Note: You can widen the Name column in the Color definition pane by dragging the vertical separation line between the Name and Value columns. You may find that the ( ) buttons disappear after resizing the columns. When this happens, resize the entire dialog slightly to redraw the buttons.

9. To create a lookup table of symbol sizes: a. Repeat steps 2 – 4. b. Enter the parameter values as shown in the figure below.

c. Click [OK]. 10. Double-click on the “Size” node to display the Size definitions in the Workspace

pane.

As with the Color lookup table, the Size lookup table also contains two columns:

• Name – Contains a list of unique entries in the Elements field

• Value – Initially blank


11. Type the required sizes (in millimetres) in the Value fields. The resulting sizes should be similar to those shown in the picture above.

12. To add a Symbol (or symbol number) lookup table: a. Repeat the procedure you used for Color and Size tables. b. In the Add Table dialog, enter the parameter values as shown below.

13. Double-click the “Symbol” node to display the Symbol definition in the Workspace pane.

14. Enter the symbol numbers in the Value fields as shown in the following figure.

Note: Symbol numbers used must match with the symbol font. In the above example, the ESRI Geometric Symbols symbol font was selected. The same font is used in this example.

You have created all three lookup tables you need for this example. Now you can use the created lookup tables to replace the constant values used in the procedure described in the Constant Drawing Attributes section.

15. Expand the tree from the root to the “Point2D” node (create a Point2D feature if one does not exist).

16. Double-click the node to display the Point2D definition in the Workspace pane.


17. Select the Symbol attribute and click the browse button ( ).

The Symbol dialog is displayed.

18. Select the Table option button.

19. From the Select Table Lookup group of option buttons, select Name.

20. From the Select Table dropdown list, select Symbol (the only entry in the list).

21. From the Select Field dropdown list, select ELEMENTS. (The Select Field drop-down list displays all the fields found in the Drillholes.shp file.)

22. Click [OK].


23. Repeat steps 17 – 22 for SymbolColor and SymbolSize attributes.

The resulting Point2D definition should look as follows:

24. From the File menu, select Save, then select Exit.

25. Open the resulting legend file in a text editor. <geosoft_xml> <legends> <legend name="SPF"> <feature name="Point2D"> <attribute expression="geosoft_symbol=TableLookup("Symbol","value",FindRow("Symbol","name",ELEMENTS))" /> <attribute expression="geosoft_symbol_size=TableLookup("Size","value",FindRow("Size","name",ELEMENTS))" /> <attribute expression="geosoft_symbol_color=TableLookup("Color","value",FindRow("Color","name",ELEMENTS))" /> <attribute expression="geosoft_font="ESRI Geometric Symbols"" /> </feature> </legend> <tables> <table name="Color" value_type="Color" table_type="Name_Lookup"> <row name="No values reported." value="R0G0B0" /> <row name="Presence of Gold: Between 500 and 3000 ppb" value="R255" /> <row name="Presence of copper: At least 0.1%" value="R0G0B0" /> <row name="Presence of zinc: At least 0.25%" value="R0G0B0" /> <row name="Presence of nickel: At least 0.1%" value="G255B255" />


</table> <table name="Size" value_type="SymbolSize" table_type="Name_Lookup"> <row name="No values reported." value="3" /> <row name="Presence of Gold: Between 500 and 3000 ppb" value="8" /> <row name="Presence of copper: At least 0.1%" value="6" /> <row name="Presence of zinc: At least 0.25%" value="3" /> <row name="Presence of nickel: At least 0.1%" value="6" /> </table> <table name="Symbol" value_type="Symbol" table_type="Name_Lookup"> <row name="No values reported." value="33" /> <row name="Presence of Gold: Between 500 and 3000 ppb" value="36" /> <row name="Presence of copper: At least 0.1%" value="38" /> <row name="Presence of zinc: At least 0.25%" value="35" /> <row name="Presence of nickel: At least 0.1%" value="178" /> </table> </tables> </legends> </geosoft_xml>

26. Test your new legend file in Oasis montaj, ArcMap, or MapInfo.


If you use ArcMap and start the process with an empty ArcGIS map, the map should be similar to the following:

5BChapter 6: Active Directory Security Model 89

Chapter 6: Active Directory Security Model The architecture of the DAP Active Directory Security Model is illustrated below:

How Thin Clients (such as GeoDAP) Access DAP Servers

1. Connects to GeoDAP from a web browser and enters login credentials. The user is logged into the same domain as the IIS server.

2. GeoDAP uses a DCOM Server process, running under the domain IDAP account, to verify login credentials. Active Directory is queried in the process.

3. GeoDAP determines the list of datasets that the user is allowed to access by querying the DAP server against the Active Directory ID of the user. The DAP server also indicates the actions the user can perform on the datasets: view the metadata, preview the dataset and extract data from the selected dataset.

90 5BChapter 6: Active Directory Security Model

4. GeoDAP builds a results web page and sends an HTTP response to the user via IIS.

5. The Active Directory ID of the user is used for all subsequent queries of and requests to the DAP server.

How Thick Clients Access DAP Servers

1. A domain user launches a DAP client software application (Oasis montaj, ArcMap, or MapInfo).

2. Inside the client application, run ‘Find Data’ or ‘Find Data with Dapple’ command to launch the DAP client plugin. The plugin sends the Active Directory ID of the logon user to the connected DAP server to query the datasets available to the user.

3. The DAP server returns, as an HTTP response via IIS, the list of datasets available to the user, together the actions the user can perform on the datasets: view the metadata, preview the dataset and extract data from the selected dataset.

4. The Active Directory ID of the user is used for all subsequent queries of and requests to the DAP server.

Enabling DAP Security To enable the DAP security, do the following in the order listed:

1. Create an IDAP_### domain account

2. Configure the DAP Server to turn the DAP security on in DAP Administrator. Disable Everyone user if appropriate

3. Configure the IDAP_### account on the DAP Server computer

4. Update IIS security through IIS Manager

5. Apply the IDAP_### appropriate security permissions to all DAP related folders in Windows Explorer

6. Plan and create DAP security groups in DAP Administrator

7. Assign user permissions to DAP data folders and data files in DAP Administrator. Catalog/Re-catalog the affected folders/files. If the datasets are already cataloged, refresh the security by running Cataloging |Refresh Catalog Component|Security in DAP Administrator

8. Enable DAP security for GeoDAP, if used

9. Test the secured DAP server in a DAP thick client (Dapple and/or classic Get DAP Data dialog) and GeoDAP.

The sections below describe each of those items in more details.


Creating an IDAP_### Domain Account

DAP server installation program creates an IDAP_### account on the local computer. To enable the DAP security, a domain IDAP_### in the internal network system needs to be created. Use a meaningful name to replace ###.

Set up the domain IDAP_### account to ‘No logon’ to limit its security permissions and to ‘Password never expire’.

Configuring the DAP Server to Enable DAP Security

1. In DAP Administrator, select the General tab on the DAP server Configuration dialog.

2. In the Security section, use the Verification dropdown list to select True. Then, using the Everyone User Allowed dropdown list, select False.

Tip: Check ( ) all the Log options, as shown in the screen capture above.

3. Click [OK] to save all the changes and close the dialog.

4. Close DAP Administrator.

92 5BChapter 6: Active Directory Security Model

Configuring the IDAP_### Account on DAP Server Computer

1. On the DAP server computer, use the Control Panel|Administrative Tools|Computer Management|System Tools|Local User and Groups|Groups, add the IDAP_### domain account to the Administrators group.

Note: Adding the account to the Users group will be sufficient if GeoDAP is not part of the DAP solution.

Updating the IIS Security through IIS Manager

1. Open the Internet Information Services Manager and select <Server_Name>\Web Sites\Default Web Site\DAP.

2. Right-click on the DAP website and from the popup menu select Properties.

3. On the DAP Properties dialog, select the Directory Security tab.

Click the [Edit] button under Authentication and access control.

4. Ensure that “Enable anonymous access” is enabled. Enter the following information: • User Name: IDAP_#### (use the Browse button to find the domain IDAP

account) • Password: Password for the IDAP_#### account

5. Save the changes and close all the dialogs.

6. Open a Command Prompt window and type the following at the DOS prompt: IISRESET

Applying IDAP_### Security Permissions to DAP Folders

1. On the DAP server computer, grant the IDAP_### domain account the same permission as the local IDAP_DAPServer account created by the DAP server setup program. It is important that you traverse the DAP software directory and its sub-directories to complete this process. The following permissions are required on the DAP server computer and should be applied recursively.

1. ..\program files\geosoft\dap server\dap (modify)

2. ..\dapdata (read)

3. ..\dap catalog (read, write)

4. ..\daptemp (modify)

5. ..\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files (read, write). Required if GeoDAP is enabled.

Planning and Creating DAP Security Groups

While it is permitted to assign DAP data access permissions to Active Directory security users individually, we recommend that DAP data access/security groups are used instead.


The DAP security groups created should be easy to manage and make sense to your company’s workflow and business operations. One model to create DAP security groups is based on exploration projects. Use the tool inside DAP Administrator to create DAP security groups.

Setting DAP Securities to DAP Data Folders/Files

In DAP Administrator, click Cataloging|Refresh Catalog Component|Security to update access permissions after setting securities to folders/files. Note: Refer to the Security - Restricting Data Access section in the Geosoft DAP

Administrator User Guide (http://www.geosoft.com/resources/tutorials/).

Testing DAP Security

Use GeoDAP, classic Get DAP Data and Dapple client applications to test the change of access permissions.


94 6BChapter 7: DAP Limits

Chapter 7: DAP Limits The following lists of DAP Limits are provided to assist you when installing, setting up and running the Geosoft DAP Server and DAP Administrator. Unless otherwise stated, these are maximum limits and should always be maintained.

Configuration Limits

Invalid Characters – \ / : * ? “ < > |

• Note, invalid characters are not permitted in any folder or file name in the DAP system.

Short Name – Maximum 64 Characters

Descriptive Name – Maximum 256 Characters

Purpose – Maximum 1024 Characters (only available when editing the ois.xml file)

Admin Password – Maximum 16 Characters

Admin Name – Maximum 64 Characters

Admin Number – Maximum 32 Characters

Admin Email – Maximum 64 Characters

Number of Services (Meta, Extract, Image, Catalog) – Maximum 16

Service Name – Maximum 32 Characters

Service URL– Maximum 256 Characters

Number of Plugins – Maximum 16

• Note, DAP plugins enable 3rd party companies to write a set of DLLs to catalog and publish data sources/types that are not supported by the core DAP technology. In total, up to 16 custom plugins are supported by a DAP server.

Plugin Namespace – Maximum 32 Characters

DAP Login Limits

User Name – Maximum 64 Characters

User Password – Maximum 64 Characters

Domain – Maximum 256 Characters

Catalog Limits

Number of DAP groups – Maximum 64

• Note, this includes all groups and all users assigned in catalog, including the Everyone user.

Number of snapshots – Maximum 6

6BChapter 7: DAP Limits 95

Number of large datasets – Maximum 65,536

• Note, to determine if a dataset is considered ‘large’ the DAP Administrator applies two criteria; spatial extent and image density. To apply these criteria the DAP Administrator program first renders the dataset as an image of 128 rows * 256 columns. Then, the first criteria, spatial extent, require that the dataset have a spatial extent that is over 8 degrees in longitude or latitude. If the dataset does meet this criteria then it is considered a large dataset, if it does not meet the first criteria then the second criteria, image density, is applied. If less than 95% of the pixels in the rendered image has a value (not dummy) then this is considered a large dataset. Examples of large datasets are global coastlines and global DEM. Area of interest (AOI) search uses dataset extents only for small datasets. For large dataset, AOI search first checks for dataset extents and then pixel values in the image file.

Number of hierarchy depth – Maximum 256

• Note, this number refers to the number of folder levels, including virtual folders, that are allowed in a DAP catalog. However, we recommend no more than 5 or 6 levels of subfolders.

Catalog results – Maximum 5000

• Note, this is the maximum number of datasets returned from a DAP search. DAP returns the datasets in a folder that is clicked in a DAP client application, and does not include any datasets outside of the folder. Hence, this limit is physically the maximum number of datasets in a Windows file folder. This is a reasonable limit and balance between users’ data and DAP performance. For example, a folder with 5000 DAP datasets could have, depending on the data file types, up to 20,000 files.

Extraction Limits

Number of extraction threads – Maximum 128

Number of extractions remembered in history – Maximum 1024

Number of hours extraction history saved – Maximum 24 hours

Size of Extraction memory – Maximum 512 MB

Minimum image size – Width > 10 and Height > 10

• Note, no data is returned if the raster image is less than 10 * 10 (in pixels).

Minimum ECW size – Width > 128 and Height > 128

• Note, this depends on whether ECW license is enabled on the DAP Server.

Re-project memory – Maximum 128 MB

96 6BChapter 7: DAP Limits

Render Limits

Number of datasets to render in one request – Maximum 32

• Note, this refers to the number of datasets that will be rendered for previewing in a browser map

Disclaimer Limits

Number of datasets to return disclaimers for – Maximum 32

• Note, this is more a limitation in DAP client API. No direct impact to end users.

DAP Server v 11 Manual - Geosoftupdates.geosoft.com/.../tutorials/pdfs/GeosoftDAPServerManual11.pdf · Configuring the DAP Server to Enable DAP Security 91 Configuring the IDAP_###

Documents