DAP Server 3.0.1
Release Notes
August 1, 2003
Click on the following for further information:
DAP Server 3.0.1
DAP (Data Access Protocol) is a family of server and client technologies developed by Geosoft that provide for the cataloguing and distribution of spatial earth-science data to geoscientists over an Intranet or the Internet. DAP 3.0.1 has been designed to make it easier for organizations to install and administer all the DAP server components and Geosoft’s standard tools and interfaces using an intuitive installation interface.
This release note describes changes and additions that have been made to DAP Server since release 2.9.
What is the DAP Server?
- All five components of the DAP application including latest web server and extraction server
- Use of Oasis montaj and Geosoft Web clients
- Geosoft Public Domain datasets to be used to test the server application
What’s new in DAP Server 3.0.0 and 3.0.1?
- Simplified installation process for DAP applications
- Enhanced server administration tools for loading, removal and disabling of multiple data sets from data servers
- New and enhanced Oasis montaj DAP client interfaces
- New auto loading and cataloguing capabilities
- New DAP monitoring enables administrators to monitor DAP server activities
- New document object to store and retrieve document files
Bugs Fixed in DAP Server 3.0.1
DAP Installation
- Installing Basic option of DAP server software hangs near the end of the installation. This bug exists in DAP 3.0 and has been fixed in 3.0.1
- Fixed the problem with any white spaces in the DAP server path which results in the failure of proper installation of DAP 3.0 server software
- Fixed the problem related to licensing DAP and Oasis montaj installed on one computer
Oasis montaj DAP client
Cancelling data retrieving progress from a DAP server by pressing the Cancel button in the progress bar disables data retrieving function. The bug has been fixed in 3.0.1
DAP Cataloguing Process
- Fixed the bug of failing cataloguing ERS files
- Fixed the bug of failing cataloguing ECW files
- Fixed the abort of using a DAPAdd.gx to add Geosoft database
- Fixed the problem with DAPAdd.gx failing to set spatial reference correctly to document files
- Fixed the abort from DMS server when cataloguing datasets in a (sub-)directory
- Fixed a bug of missing filled polygons in creating HMAP
- Improved capability to generate HXYZ files from large Geosoft databases
DAP Servers
- Fixed the bug of retrieving ERS files and ECW files
- Addressed the problem of using index/reference map which straddles the 180 degree line
- Fixed the bug of using incorrect projection from index/reference map when retrieving point data from the Geosoft public DAP server, which results in location symbols plotted in incorrect positions
What does DAP Server installation do?
Server Install:
- Creates and configures DCS, DDS, DFS and DMS of Geosoft DAP server
- Sets up and configures a working WMS server with a PHP engine and MapServer
- Creates an initial WMS web server for serving up datasets
- Loads default datasets into the DAP server
- Creates a new local user so that the DAP server can run within a secure context
- Sets security permissions on created directories and files used by the DAP server
- Checks for and uses a Geosoft DAP server license key
- Provides all this in a step-by-step, interface driven installation package
What data does DAP Server support?
|
ArcView File Sets |
.SHP, .SHX, .DBF will be catalogued as spatially registered documents. DAP will deliver selected document sets to an Oasis client that will display the data in a Geosoft map. The display of the data will be limited to the capabilities of Oasis montaj. |
|
MapInfo File Sets |
.TAB,.MAP,.ID,.DAT will be catalogued as spatially registered documents. DAP will deliver selected document sets to an Oasis client that will display the data in a Geosoft map. The display of the data will be limited to the capabilities of Oasis montaj. |
|
Geosoft Grid Files |
All supported Geosoft grid types on a project basis. Each grid file must be spatially located within a geographic or projected coordinate system. |
|
Image Files |
All Geosoft supported image file formats. Each image must be spatially located within a geographic or projected coordinate system. |
|
Geosoft Maps |
Geosoft maps will be supported as spatially referenced documents. |
|
Geosoft databases |
Geosoft GDB files will be support full windowing to selected area of interest. GDB files must contain a designated X, Y coordinate channel pair in a defined projected to geographic coordinate system. |
|
Geosoft HyperGrids |
Very large regional grids can be converted to Geosoft HyperMaps for more efficient windowing and delivery by DAP. Administrator tools will be provided to support the creation of HyperGrids. |
|
Geosoft HyperXYZ |
Very large point attribute data (X, Y, attributes…) can be converted to Geosoft HyperXYZ format for efficient windowing and data delivery by DAP. Administrator tools will be provided to support the creation of HyperXYZ data from Geosoft GDB files. . |
|
Geosoft HyperMaps |
Specific large point and line GIS themes, such as drainage, political boundaries, claim boundaries can be converted to Geosoft HyperMaps for efficient windowing and distribution by DAP. Administrator tools will be provided for the creation of HyperMaps from a selected Geosoft map group. |
|
Documents |
All document types can be catalogued with spatial references for delivery of the document files to DAP clients. |
|
AutoCAD drawings |
AutoCAD drawings will not be directly supported. AutoCAD drawings can be converted to Geosoft MAP files or to GIS themes and distributed in these formats. |
|
MS Access Databases |
MS Access databases will not be directly supported except as spatially located documents. Data contained in an MS Access database can be imported into a Geosoft GDB file and converted to Geosoft HyperXYZ file for distribution. |
What system requirements are needed to run DAP Server?
Minimum Requirements:
- Windows 2000/XP (will run on a Workstation and Server Edition)
- IIS 5.0 or above, or Apache v2.0.44 or above
- 128 – 256 MB RAM
- Sufficient amount of physical disk space
Optimal Requirements:
- Windows 2000 Server or Windows 2003 Server (Standard Edition or Enterprise Edition)
- IIS 5.0 or above, or Apache v2.0.44 or above
- 1 – 2 GB RAM
- Dual processor (minimum 1.4 – 2 GHz in speed)
Special Note:
These requirements are only a suggestion. Speed and performance of a DAP server is based on the machine itself. That is, it will run faster with 4 processors than with 2. Also, RAM is the most important defining factor on speed and performance. We suggest that an optimal machine have plenty of RAM.
< back
|
