Geomatica WebServer Installation Guide.book - UNBC GIS / Remote ...

Geomatica ® WebServer Suite
Installation and Configuration Guide
Version 10.1.1

©2007 PCI Geomatics Enterprises Inc.®. All rights reserved.
COPYRIGHT NOTICE
Software copyrighted © by PCI Geomatics, 50 West Wilmot St., Suite 200, Richmond Hill,
ON CANADA L4B 1M5
Telephone number: (905) 764-0614
RESTRICTED RIGHTS
Canadian Government
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in DSS
9400-18 "General Conditions - Short Form - Licensed Software".
U.S. Government
Use, duplication, or disclosure by the Government is subject to restrictions set forth in
subparagraph (b)(3) of the Rights in Technical Data and Computer Software clause of
DFARS 252.227-7013 or subparagraph (c)(1) and (2) of the Commercial Computer Software-
Restricted Rights clause at 48 CFR 52.227-19 as amended, or any successor regulations
thereto.
PCI, PCI Geomatics, PCI and design (logo), Geomatica, Committed to GeoIntelligence
Solutions, GeoGateway, FLY!, OrthoEngine, RADARSOFT, EASI/PACE, ImageWorks,
GCPWorks, PCI Author, PCI Visual Modeler, and SPANS are registered trademarks of PCI
Geomatics Enterprises, Inc.
Sentinel is a registered® trademark of SafeNet, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
The Geomatica WebServer Suite was developed with the generous support of Natural Resources
Canada GeoConnections program.
http://www.geoconnections.org

Table of Contents
Chapter 1
INTRODUCTION TO GEOMATICA WEBSERVER SUITE
Introducing Geomatica WebServer Suite ..................................................................................................................................................... 7
Intended Audience................................................................................................................................................................................ 7
System Requirements .......................................................................................................................................................................... 7
Contacting PCI Geomatics Support.............................................................................................................................................................. 8
Understanding How the Web Services Work ............................................................................................................................................... 8
Understanding the Geomatica Web Feature Service ........................................................................................................................... 9
Understanding the Geomatica Web Coverage Service...................................................................................................................... 10
Understanding the Geomatica Web Mapping Service........................................................................................................................ 10
Chapter 2
INSTALLING THE SERVLETS
Installing Geomatica ................................................................................................................................................................................... 13
Installing the HTTP Server and Servlets .................................................................................................................................................... 13
Installing the Java SE Development Kit on a Windows System ......................................................................................................... 14
Installing the Tomcat Server on a Windows System .......................................................................................................................... 14
Testing the Tomcat Server ................................................................................................................................................................. 15
Installing .JAR Files .................................................................................................................................................................................... 16
iii

iv
Installing Oracle® .JAR Files ..............................................................................................................................................................16
Installing .WAR Files...................................................................................................................................................................................16
Exploring the WCS Folder...........................................................................................................................................................................16
Exploring the WFS Folder...........................................................................................................................................................................17
Exploring the WMS Folder ..........................................................................................................................................................................17
Stopping and Restarting Tomcat.................................................................................................................................................................18
Troubleshooting Low Memory Error in Tomcat...........................................................................................................................................18
Chapter 3
CONFIGURING THE SERVLET FOR THE WEB FEATURE SERVICE (WFS)
Configuring the WFS Servlet.......................................................................................................................................................................21
Exploring the Web.xml for the WFS ....................................................................................................................................................22
Setting the Initialization Properties......................................................................................................................................................23
Testing the WFS Servlet .....................................................................................................................................................................26
Publishing Your Data on the WFS Servlet ..................................................................................................................................................26
Exploring the Data Source Configuration File .....................................................................................................................................27
Modifying the Data Source Configuration File.....................................................................................................................................27
WFS Troubleshooting Checklist..................................................................................................................................................................28
Chapter 4
CONFIGURING THE SERVLET FOR THE WEB COVERAGE SERVICE (WCS)
Configuring the WCS Servlet ......................................................................................................................................................................31
Exploring the config.xml for the WCS .................................................................................................................................................31
Testing the WCS Servlet.....................................................................................................................................................................34
Publishing Your Data on the WCS Servlet..................................................................................................................................................35
Modifying the WCS Deployment File ..................................................................................................................................................35
WCS Troubleshooting Checklist .................................................................................................................................................................38
Chapter 5
CONFIGURING THE SERVLET FOR THE WEB MAPPING SERVICE (WMS)
Configuring the WMS Servlet......................................................................................................................................................................39
Using the Self-Configured Method ......................................................................................................................................................39

Using the Assisted Method................................................................................................................................................................. 40
Using the Customized Method ........................................................................................................................................................... 40
Creating the Servlet Configuration File....................................................................................................................................................... 41
Exporting the XML Project.................................................................................................................................................................. 41
Exploring the Initialization Parameters ............................................................................................................................................... 41
Setting Parameters in Tomcat ............................................................................................................................................................ 43
Reconfiguring Geomatica Focus Project Using EASI................................................................................................................................. 43
Resetting the Servlet from a Remote Location........................................................................................................................................... 43
Exploring the Syntax of the Servlet’s Configuration File............................................................................................................................. 44
Exploring the Contents of the Servlet’s DTD .............................................................................................................................................. 45
Viewing the MapService-Config DTD ......................................................................................................................................................... 47
Chapter 6
PUBLISHING YOUR MAPS ON THE WMS SERVLET OR A WEB PAGE
Publishing Your Data on the WMS Servlet................................................................................................................................................. 49
Starting the Geomatica WebServer Monitor............................................................................................................................................... 49
Publishing Your Maps in a Web Page ........................................................................................................................................................ 50
Introducing the Templates .......................................................................................................................................................................... 51
Using the Basic Template to Display Your Project ..................................................................................................................................... 52
Using the Templates for Your Web Page ................................................................................................................................................... 52
Creating Your Applet’s XML File......................................................................................................................................................... 52
Creating Your HTML File from an Example........................................................................................................................................ 53
Making Your Own Web Page ..................................................................................................................................................................... 54
Displaying Layers ............................................................................................................................................................................... 55
Creating Queryable Layers................................................................................................................................................................. 55
Adding Buttons ................................................................................................................................................................................... 56
Providing a Tool to Build Query Expressions ..................................................................................................................................... 63
Adding Shortcuts to Saved Queries ................................................................................................................................................... 63
Adding a Tool to Display the Coordinates in the Status Bar............................................................................................................... 64
Displaying an Overview of Your Project ............................................................................................................................................. 64
Chapter 7
CONFIGURING THE WMS MAPVIEWER APPLET
Configuring the MapViewer Applet ............................................................................................................................................................. 67
v

vi
Creating the Applet’s Configuration File......................................................................................................................................................67
Adding Several Map Layers ................................................................................................................................................................68
Defining the “Mapviewer-Config” Root Element..................................................................................................................................69
Using the Viewport Element................................................................................................................................................................69
Using the “Extent” Child Element ........................................................................................................................................................69
Setting the “SRS” Attribute..................................................................................................................................................................69
Using the WMSProvider Element........................................................................................................................................................70
Setting WMSProvider Attributes..........................................................................................................................................................70
Using the “Map” Element ....................................................................................................................................................................71
Using the “Maplayer” Child Element ...................................................................................................................................................71
Determining the Supported-Styles ......................................................................................................................................................72
Changing the Supported-Bbox............................................................................................................................................................72
Setting the “Maplayer” Attributes.........................................................................................................................................................73
Generating a Capabilities File.....................................................................................................................................................................73
Viewing the MapViewer DTD ......................................................................................................................................................................74
Chapter 8
API REFERENCE FOR THE WMS
Class MapViewerApplet..............................................................................................................................................................................77
Class Layer .................................................................................................................................................................................................88
Class LayerInfoFilterConfig.........................................................................................................................................................................97
Class Extent..............................................................................................................................................................................................110
Class Point2d............................................................................................................................................................................................113
Class RectangleDouble.............................................................................................................................................................................118
Index ........................................................................................................................................................................................................131

Introduction to Geomatica WebServer Suite
Introducing Geomatica WebServer Suite
Welcome to Geomatica ® WebServer Suite. Geomatica WebServer
Suite contains three services designed for sharing geospatial
information over the Web.
With the Web Feature Service (WFS) you can open features in
Geomatica Focus from any Web feature service on the Web, and you
can provide others with access to your project’s features through the
Internet.
With the Web Coverage Service (WCS) you can open coverages in
Geomatica Focus from any Web coverage service on the Web, and
you can provide others with access to your coverages through the
Internet.
With the Web Mapping Service (WMS) you can open map layers
in Geomatica Focus from any Web map service on the Web, and you
can make your maps layers available to anyone on the Internet
through the server or your Web page.
C HAPTER
1
Intended Audience
The Geomatica WebServer Suite Guide is intended for those who are
tasked with installing and configuring the components of the Web
servers or designing the Web page. Although most of the guide is
written with the assumption that you have basic knowledge of the
various Web technologies, such as HTML, XML, JavaScript, Web
servers, applets and servlets, some basic concepts are explained. So,
even if you possess only a rudimentary knowledge of the
technologies and basic programming skills, you can install the
Geomatica WebServer Suite and certainly create a Web page.
This guide also assumes that you are familiar with Geomatica, the
software program used to create the projects. For details on how to
use Geomatica Focus, refer to the Geomatica Focus User Guide.
System Requirements
PCI Geomatica software is distributed on ISO9660 format CD-
ROMs. The PCI software requires a valid license; otherwise it will
run in demo mode with limited functionality.
7

Chapter 1 - Introduction to Geomatica WebServer Suite
You must have the following system requirements for the
WebServer Suite:
Microsoft® Windows®
• Windows NT 4.0, Windows 2000, or Windows XP.
• Pentium III 600 MHz processor, or greater.
• CD-ROM drive.
• 800 MB of free hard disk space, plus space for data.
• 512 MB of RAM, or greater.
• 24-bit Windows graphics card or accelerator, running at 1280 x 1024
pixels. The minimum is a 16-bit graphics card or accelerator, running
at 1024 x 768.
• SentinelPro hardware key (included).
HTTP Server
• Servlet 2.2 compliant Web server, such as Tomcat.
• Java version 1.5 or higher
Contacting PCI Geomatics Support
On the Web
• http://www.pcigeomatics.com/services/support_center/
contact_support.php
Call Us
• 1-877-RING-PCI (1-877-746-4724) (North America)
• 905-764-0614 (Direct to our main office in Richmond Hill,
Ontario, Canada)
Write Us
• Fax 1-905-764-9604 (Attention: Support Department)
• Email a Customer Service Request to support@pcigeomatics.com
• Email a Customer License Request to license@pcigeomatics.com
FTP Instructions
1. FTP to ftp.pcigeomatics.com
2. Login: anonymous
3. Password: email address
4. Upload files to "/pub/incoming"
5. E-mail support@pcigeomatics.com with the exact file name (note:
you cannot view the content of "/pub/incoming")
Please include the following information with all your
correspondence with PCI Geomatics technical support:
• your customer number
• the type of operating system you are using
• the version number of the product
• a description of the problem
Understanding How the Web Services
Work
As shown in Figure 1.1, a client is a program on a computer that is
connected to a network which has access to the Web. The client
sends requests for information to a server through the Web using
HTTP. A server is a program that receives the request from the client
and transfers the request to a servlet. The servlet is a small Java
program that runs on the server. The servlet obtains the information
from the data source and then sends the result back to the HTTP
server, which transfers the information back to the client.
8 PCI Geomatics

Understanding How the Web Services Work
Figure 1.1: Understanding Web services
Data
Source
Client
Servlet
HTTP Server
1. The client sends a request to an
HTTP server.
2. The HTTP server passes the
request to the servlet.
3. The servlet obtains the
requested file from the source
and returns it to the HTTP
server.
4. The HTTP server sends the file
back to the client.
Understanding the Geomatica Web Feature Service
A Web feature service provides access to features available on the
Web. As described by the Open GIS Consortium (OGC), a feature
is “a digital representation of a real world entity or an abstraction of
the real world. It has a spatial domain, a temporal domain, or a
spatial/temporal domain as one of its attributes. Examples of
features include almost anything that can be placed in time and
space, including . . . cities, trees, forest stands, ecosystems, . . . ". 1
The Web Feature Service (WFS) available in the Geomatica
WebServer Suite consists of a WFS client and a WFS servlet as
shown in Figure 1.2. The WFS client (1) is accessed through
Geomatica Focus. Using the WFS client, you send a request to any
compatible Web feature service on the Web, it returns the results of
the request to the WFS client, and then the features are displayed as
1. The Open Geospatial Abstract Specification Topic 6: The Coverage Type and
its Subtypes Version 6 Open GIS Consortium. January 2004, http://
www.opengeospatial.org/techno/abstract/00-106.pdf
a layer in Geomatica Focus. With the WFS servlet (2) you can make
your geospatial features available to others through the Web.
Figure 1.2: How the WFS works
Geomatica Focus as
the WFS client
Using the WFS Client
A Web feature service
somewhere on the Web
HTTP Server
A client somewhere
on the Web
WFS servlet
Data sources containing
the features that you want
to publish
The WFS client is accessed through the Remote Data Wizard
dialog box in Geomatica Focus. To open the Remote Data Wizard
dialog box, select File in the main menu, click Open, and click the
Remote Data button. You do not need to configure the WFS client.
For information about how to use the WFS client, refer to the
Geomatica Focus User Guide.
Geomatica WebServer Suite Installation Guide 9

Chapter 1 - Introduction to Geomatica WebServer Suite
Understanding the Geomatica Web Coverage
Service
A Web coverage service provides access to coverages available on
the Web. As described by the Open GIS Consortium (OGC), a
coverage is “a feature that associates positions within a bounded
space (its spatiotemporal domain) to feature attribute values (its
range). GIS coverages (including the special case of Earth images)
are two- (and sometimes higher) dimensional metaphors for
phenomena found on or near a portion of the Earth's surface. A
coverage can consist of a set of features . . .”. 1 Unlike a map, which
is a static two-dimensional representation of geospatial data, a
coverage contains intact geospatial data.
The Web Coverage Service (WCS) available in the Geomatica
WebServer Suite consists of a WCS client and a WCS servlet as
shown in Figure 1.3. The WCS client (1) is accessed through
Geomatica Focus. Using the WCS client, you send a request to any
compatible Web coverage service on the Web, it returns the results
of the request to the WCS client, and then the coverage is displayed
as a layer in the Geomatica Focus. With the WCS servlet (2) you can
make your coverages available to others through the Web.
Using the WCS Client
The WCS client is accessed through the Remote Data Wizard
dialog box in Geomatica Focus. To open the Remote Data Wizard
dialog box, select File in the main menu, click Open, and click the
Remote Data button. You do not need to configure the WCS client.
For information, refer to the Geomatica Focus User Guide.
1. The Open Geospatial Abstract Specification Topic 6: The Coverage Type and
its Subtypes Version 6 Open GIS Consortium. January 2004, http://www.opengeospatial.org/techno/abstract/00-106.pdf
Figure 1.3: How the WCS works
Geomatica Focus as
the WCS client
A Web coverage service
somewhere on the Web
HTTP Server
Data sources containing
the coverages that you
want to publish
A client somewhere
on the Web
WCS servlet
Understanding the Geomatica Web Mapping
Service
A Web mapping service provides access to maps available on the
Web. As described by the Open GIS Consortium (OGC), a map is
“a two-dimensional visual portrayal of geospatial data. A map is not
the data itself.” 2
2. Open GIS Consortium (OGC) Web site, Glossary, January 2004, http://
www.opengeospatial.org/resources/?page=glossary#M
10 PCI Geomatics

Understanding How the Web Services Work
The Web Mapping Service (WMS) available in the Geomatica
WebServer Suite consists of two WMS clients and a WMS servlet as
shown in Figure 1.4. One of the WMS clients is accessed through
Geomatica Focus, and the other is the combination of an applet and
a browser.
Through the WMS client (1) in Geomatica Focus, you send a request
to any compatible Web mapping service on the Web, it returns the
results of the request to the WMS client, and then the map is
displayed as a layer in Geomatica Focus.
With the WMS servlet (2) you can make your maps available to
others through the Web. Instead of placing your maps in a folder,
you create a shortcut to your project which serves the maps to the
servlet.
The other WMS client (3), the applet and browser, displays your map
project in a Web page. You can use one of the Web page templates
provided in Geomatica WebServer Suite or build your own.
Using the WMS Clients
The WMS client in Geomatica Focus is accessed through the
Remote Data Wizard dialog box. To open the Remote Data
Wizard dialog box, select File in the main menu, click Open, and
click the Remote Data button. You do not need to configure
Geomatica Focus’s WMS client. For information about how to use
it, refer to the Geomatica Focus User Guide.
If you want to publish your maps on a Web page, see “Publishing
Your Maps on the WMS Servlet or a Web Page” on page 49.
Figure 1.4: How the WMS works
Geomatica Focus as
the WMS client
The applet and
browser client
displaying the map
project in a Web page
HTTP Server
WMS servlet
Geomatica Focus in server mode
containing the maps that you
want to publish
A Web mapping service
somewhere on the Web
A client somewhere
on the Web
HTTP Server
WMS servlet
Geomatica Focus
in server mode
containing the
maps that you
want to publish
Geomatica WebServer Suite Installation Guide 11

Chapter 1 - Introduction to Geomatica WebServer Suite
12 PCI Geomatics

Installing the Servlets
Installing Geomatica
To install Geomatica, follow the installation instructions in the
Installing PCI Geomatics Software guide.
After you install Geomatica, you must set the Path environment
variable for Geomatica:
To set the Path environment variable for Geomatica:
1. Right-click My Computer and click Properties.
2. Click the Advanced tab.
3. Click Environment Variables.
4. Under System Variables, click Path and click Edit.
5. In the Variable Value box, add the path of the Geomatica exe
folder to the end of the existing data.
For example, %SystemRoot%\system32;%SystemRoot%;
%SystemRoot%\System32\Wbem;C:\Program Files\Common
Files\Adaptec Shared\System;c:\Program Files\PCI
Geomatics\Geomatica_V101\exe.
6. Click OK.
C HAPTER
2
Installing the HTTP Server and Servlets
Several Web server technologies support servlets, such as iPlanet
Web Server, W3C Jigsaw, Tomcat from Apache, JRun from
Macromedia, ServletExec® from New Atlanta Communications,
and Resin® from Caucho Technology.
Note
We recommend the Tomcat Server 5.5 from Apache Software
Foundation as your HTTP server. This manual assumes that you do not
have an HTTP server installed and uses the Tomcat server as an
example. If you are using another server technology, please refer to that
server’s installation instructions for guidance.
13

Chapter 2 - Installing the Servlets
The following steps are required to install the server and
servlets:
1. Install the Java Developer’s Kit :
See “Installing the Java SE Development Kit on a Windows
System” on page 14.
2. Install the Tomcat Server 5.5:
See “Installing the Tomcat Server on a Windows System” on
page 14.
3. Start the Tomcat server 5.5:
See “Testing the Tomcat Server” on page 15.
4. Installing the .jar files:
See “Installing .JAR Files” on page 16.
5. Install the .war file(s):
See “Installing .WAR Files” on page 16.
Installing the Java SE Development Kit on a
Windows System
Because servlets are based on JavaTM technology, you must install
the Java SE Development Kit Standard Edition (JDK) 5.0 or greater
on your HTTP server.
Note
The WCS will not run on versions earlier than 5.0.
To install JDK:
1. Open a Web browser, and enter http://java.sun.com/j2se/1.5/ in the
address bar.
2. Click the Download J2SE 5.0 link.
3. Click the Download button corresponding to JDK 5.0 or higher.
Example: JDK 5.0 Update 12
4. On the Download screen, follow the instructions in the license
agreement section.
5. Scroll down and click the required link.
6. Save the file in a preferred location.
7. Click Close on the Download Complete window.
8. Double-click the saved file and follow the on-screen instructions to
install JDK 5.0.
To set the environment variable for JAVA_HOME:
1. Right-click My Computer and click Properties.
2. Click the Advanced tab.
3. Click Environment Variables.
4. Under User Variables or System Variables, click New.
5. In the Variable Name box, type JAVA_HOME.
6. In the Variable Value box, type the path for the J2SE folder.
Example: C:\jdk-1_5_0_12
7. Click OK.
Installing the Tomcat Server on a Windows System
Once the J2SE is installed on the HTTP server, install the Tomcat
server. If you are using a server technology other than Tomcat,
please refer to its installation manual.
14 PCI Geomatics

Installing the HTTP Server and Servlets
To install Tomcat:
1. Download the current version of Tomcat from http://
jakarta.apache.org/tomcat/. On the Apache Jakarta Project Web page
under Download, click Tomcat 5.x.
2. Under 5.5.xx, click Windows Service Installer.
3. Save the file in a preferred location.
4. Click Close on the Download Complete window.
5. Double-click the saved file and follow the on-screen instructions to
install Tomcat.
Testing the Tomcat Server
When Tomcat is installed, start the Tomcat server and verify that it
is running properly. You can start Tomcat from the command
prompt, if you downloaded a zip or from the Apache Tomcat
Properties window, if you installed Tomcat using the Windows
Service Installer.
To start Tomcat from the command prompt:
1. Open the command prompt.
2. Type the path to the folder where you installed Tomcat.
Example: C:\>cd Program Files\Apache\Tomcat 5.5\bin
3. Press Enter.
4. Type startup.
Example: C:\Program Files\Apache\Tomcat 5.5\bin>startup
To start Tomcat from Apache Tomcat
1. In Windows, click Start > Programs and click Apache Tomcat 5.5.
2. Select Configure Tomcat.
3. On the General tab of the Apache Tomcat Properties window,
click Start.
To verify that Tomcat is running properly:
1. Type the following in the address bar of your browser:
http://[localhost]:[port]
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed. Replace [port] by the number of the
listening port for Tomcat.
2. View the Tomcat HTML page, which should appear similar to Figure
2.1. If Tomcat fails to respond, verify the records in the logs folder,
which is in the folder where you installed Tomcat.
Figure 2.1: Tomcat HTML page
Geomatica WebServer Suite Installation Guide 15

Chapter 2 - Installing the Servlets
Tip
Tomcat uses port 8080 by default, however, the standard HTTP port is
80. To change the HTTP port to 80, change the parameter in the
server.xml file in the conf folder, which is in the folder where you installed
Tomcat. If you do change the HTTP port, you will no longer need to type
the port number when you type the address in the browser.
Installing .JAR Files
The Java Archive (.jar) files contain the class files and auxiliary
resources for the Web Feature Service.
To install the .jar files:
1. Copy the easi.jar, featurequery.jar, ntvcore.jar, and gdbwrapper.jar
files located in \GWS\shared-jars where you installed Geomatica.
2. Paste the .jar files in the \shared\lib folder of your Tomcat
installation.
Installing Oracle® .JAR Files
Oracle .jar files are required if you want to publish Oracle data on
the WCS server. You must first install and set up the Oracle client,
and then transfer the Oracle .jar files to the folder where you
installed Tomcat.
To install Oracle .JAR files:
1. Copy the ojdbc14.jar or classes12.jar located in
\product\$version\client_1\jdbc\lib of your Oracle installation.
2. Paste the .jar file in \shared\lib of your Tomcat installation.
Installing .WAR Files
The Web Archive (.war) files contain the files and configuration
information required for the Geomatica WebServer Suite of
products. Follow the instructions for installing the .war file for each
Web service licensed to you.
The .war file for:
• The Web Feature Service (WFS) is called wfs.war.
• The Web Coverage Service (WCS) is called wcs.war.
• The Web Mapping Service (WMS) is called wms.war.
To install the .war file:
1. Copy the required .war file(s), which are located in the gws folder of
your Geomatica installation.
2. Paste the .war file(s) in the webapps folder of your Tomcat
installation.
3. Start the Tomcat server. If Tomcat is already running, stop and then
restart it (see “Stopping and Restarting Tomcat” on page 18).
When Tomcat starts, it automatically extracts the files from the
.war file and creates its own folder structure.
Exploring the WCS Folder
Once the wcs.war file is copied to the folder where you installed
Tomcat, it contains all of the files that you need for the WCS servlet.
In \webapps\wcs you will find:
images folder: This folder contains the logo of the HTML page used
for testing the WCS servlet (see “Testing the WCS Servlet” on
page 34).
META-INF folder: This folder contains the manifest file, which is
a system file for Web applications and used to define the extension
and package data of the .war file.
16 PCI Geomatics

Exploring the WFS Folder
schemas folder: This folder contains the OGC-compliant WCS
schemas in XSD format.
WEB-INF folder: This folder contains:
• The config folder: This folder contains the files that help you
configure your WCS server and the system folder that contains cache
management files (see “Exploring the config.xml for the WCS” on
page 31).
• The data folder: This folder contains sample files that you can use to
test and demonstrate the WCS. It can also hold files that you want to
publish through the WCS servlet.
• The lib folder: This folder holds a collection of routines used to run
the WCS servlet.
• The plugins folder: This folder contains the Open Services Gateway
initiative (OSGI) bundles that are part of the WCS implementation.
•The web.xml file: This file is the initialization file for the servlet.
Exploring the WFS Folder
Once the wfs.war file is copied to the folder where you installed
Tomcat, it contains all the files that you need for the WFS servlet. In
\webapps\wfs, you will find:
The conf folder: This folder contains:
• The wfs_init.properties file, which contains a list of parameters
that you can use to customize the WFS servlet (see “Setting the
Initialization Properties” on page 23).
• The wfs_data_sources.xml file, which contains a list of files and
folders that are published on the WFS servlet (see “Exploring the
Data Source Configuration File” on page 27).
demo folder: This folder contains sample files that you can use to
demonstrate the WFS. It can also hold the files that you want to
publish through the WFS servlet.
images folder: This folder contains logos and images for the HTML
page used for testing the WFS servlet (see “Testing the WFS
Servlet” on page 26).
META-INF folder: This folder contains the manifest file used to
define the extension and package data of the .war file.
WEB-INF folder: This folder contains:
•The classes folder, which contains the class files needed to run the
WFS servlet. A servlet is a Java program that runs on a server and
enables WFS servlet to respond to requests quickly and effectively.
•The Lib folder, which holds a collection of routines used to run the
WFS servlet.
•The web.xml file, which is the initialization file for the servlet.
Exploring the WMS Folder
Once the wms.war file is copied to the folder where you installed
Tomcat, it contains all the files that you need for the WMS servlet.
In \webapps\wms you will find:
Application folder: This folder contains the SelectLayer.xslt file
that determines the format for the applet’s configuration page. It
should not be modified.
Config folder: This folder contains the configuration files for the
applet. AllProject.xml configures the applet in
MapViewerTemplate1.html. Layers.xml configures the applets in
the remaining MapViewerTemplates.
DTD folder: This folder contains the Document Type Definition
(DTD) files. A DTD is a document that includes formal definitions
of all the data elements for the Geomatica Web Mapping Service
documents. By consulting the DTD, an XML parser can work with
the markup codes used by WMS documents and validate the syntax
of your configuration files.
Geomatica WebServer Suite Installation Guide 17

Chapter 2 - Installing the Servlets
help folder: This folder contains the help and demo files for the
WMS client that forms a Web page (see “Introducing the Templates”
on page 51).
images folder: This folder contains the library of logos, icons, and
graphics for the Readme and MapViewerTemplate HTML files.
JavaScript folder: This folder contains the JavaScript files that are
used with your HTML files when you are publishing your project in
a Web page. JavaScript adds simple online applications and
functions to your Web page (see “Making Your Own Web Page” on
page 54). Web browsers compatible with JavaScript, such as
Netscape Navigator or Internet Explorer, are required to run
JavaScript code.
META-INF folder: This folder contains the manifest file used to
define the extension and package data of the .war file.
WEB-INF folder: This folder contains:
•The classes folder, which contains the WMSServlet.class,
EasiServlet.class, and AppletConfigServlet.class files. A servlet is a
Java program that runs on a server and enables WMS servlet to
respond to requests quickly and effectively.
•The Lib folder, which holds a collection of routines used to run the
WMS servlet.
•The web.xml file, which contains a list of parameters that you can
use to customize the WMS servlet (see “Changing the Function”
on page 41).
XSLT: This folder contains the Extensible Stylesheet Language for
Transformation (XSLT) files. The XSLT.xslt file determines the
format for the results of the queries that you perform in your Web
page.
MapViewer.jar: This file contains the applet for the WMS client.
An applet is a program that is automatically downloaded over the
Web and run on the recipient's computer. The applet is written in the
Java programming language and runs within the browser software. It
is used to display the map in your Web page.
MapViewerTemplate.html: These HTML files are examples of
Web pages that you can create with Geomatica Web Mapping
Service.
Stopping and Restarting Tomcat
You can stop and restart Tomcat through the command prompt or the
Apache Tomcat Properties window.
If you are using the Web Mapping Service (WMS), you can also stop
and restart Tomcat remotely, see “Resetting the Servlet from a
Remote Location” on page 43.
To stop and restart Tomcat from the command prompt:
1. In the command prompt, where you started Tomcat, type Ctrl+C or
Ctrl+Break to stop Tomcat.
2. Then type startup to restart Tomcat.
Example: C:\Program Files\Apache\Tomcat 5.5\bin>startup
To stop and restart Tomcat from Apache Tomcat
1. In Windows, click Start > Programs > Apache Tomcat 5.5.
2. Select Configure Tomcat.
3. On the General tab of the Apache Tomcat Properties window,
click Stop and then Start.
Troubleshooting Low Memory Error in
Tomcat
In some cases the demands on the servlets exceed the default
memory allocation of Java. The result is a low memory error. You
18 PCI Geomatics

Troubleshooting Low Memory Error in Tomcat
can adjust the allocated memory size through one of the following
methods:
1. Increase the memory size from the Windows command prompt.
2. Increase the memory size in Apache Tomcat.
Determining the memory size to set is an educated guess. You should
take into consideration the size of the data, the number of channels,
and the image type that may be requested, as well as the overhead
being used. Doubling the default amount is recommended as long as
it is smaller than the physical RAM installed on the computer.
To increase the memory size from the Windows command
prompt:
1. Open the command prompt.
2. Type the path to the folder where you installed Tomcat.
3. Press Enter.
4. Then type the following:
startup //TS//Tomcat5 --JvmMx=[size]
Replace [size] with the amount of memory you want to allocate.
For example, if you want to change the size to 512 MB, you can
type JvmMx=512.
To increase the memory size in Apache Tomcat
1. In Windows, click Start > Programs > Apache Tomcat 5.5.
2. Select Configure Tomcat.
3. On the Apache Tomcat Properties window, click the Java tab.
4. Enter a number in the Maximum memory pool.
Example: 512
Geomatica WebServer Suite Installation Guide 19

Chapter 2 - Installing the Servlets
20 PCI Geomatics

C HAPTER
3
Configuring the Servlet for the Web Feature Service (WFS)
Configuring the WFS Servlet
The deployment descriptor for the HTTP server is the web.xml file
found in \webapps\wfs\WEB-INF in the folder where you installed
Tomcat. The web.xml file declares the locations of the WFS servlet, its
Java classes, and its configuration file.
The WFS servlet directly accesses Geomatica Focus executable
routines when retrieving the data as shown in Figure 3.1. Therefore,
WFS servlet and Geomatica Focus must reside on the same computer
or be made directly accessible through the network using the
environment variables.
The initialization file for the WFS servlet is the wfs_init.properties
file found in \webapps\wfs\conf in the folder where you installed
Tomcat. It contains the initialization parameters that control the
servlet. All the parameters must contain values. Each time you
change the parameters, restart Tomcat to unload the servlet from
memory.
Figure 3.1: Understanding the WFS Servlet
HTTP server
WFS servlet
Servlet accesses Geomatica
Focus executable routines
Folders containing
feature data files
21

Chapter 3 - Configuring the Servlet for the Web Feature Service (WFS)
Exploring the Web.xml for the WFS
Using an example is the best way to understand the configuration
files. The web.xml for the WFS is found in \webapps\wfs\WEB-INF
in the folder where you installed Tomcat. It communicates to the HTTP
server the WFS servlet’s name, its location, and the location of its
configuration file called wfs_init.properties.
PCI WFS (Web Feature Server) Servlet
WFSServlet
com.pcigeomatics.servlets.wfs.WFSServlet
properties.filename
/conf/wfs_init.properties
WFSServlet
/wfs/*
The first line in the web.xml file indicates that the document is based
on XML version 1.0 and the encoding is ISO-8859-1, which is the
character encoding commonly used in North and South America,
Western Europe, Australia, and most of Africa.
The DOCTYPE declaration states that the file is an XML document,
and includes the DTD published by Sun Microsystems, Inc. that
validates the web.xml:
The “web-app” element is the root element of the XML file, which
contains all the other elements in the web.xml file.
. . .
The “display-name” element determines the name that will appear
on the GUI tools and server configuration tools.
PCI WFS (Web Feature Server) Servlet
The “servlet” element contains the elements used to identify the
servlet. The “servlet-name” element declares the name of the servlet
used with the WFS. The “servlet-class” element declares the relative
path and filename of the servlet, which is in \webapps\wfs\WEB-
INF\classes\com\pcigeomatics\servlets\wfs in the folder where you
installed Tomcat.
WFSServlet
com.pcigeomatics.servlets.wfs.WFSServlet
22 PCI Geomatics

Configuring the WFS Servlet
The “init-param” element contains the name/value pair initialization
parameters for the WFS servlet. The “param-name” element declares
the name of the parameter. The “param-value” element declares the
value of the parameter. It provides the location of the configuration
file for the servlet, which is the wfs_init.properties file in
\webapps\wfs\conf in the folder where you installed Tomcat.
properties.filename
/conf/wfs_init.properties
The “servlet-mapping” element contains the name/value pair that
controls how you access a servlet through the Web. The “servletname”
element declares the name of the servlet, which corresponds
to the name declared in the “servlet” element. The “url-pattern”
element declares the relative path of the URL after http://host:port/
war filename.
WFSServlet
/wfs/*
Setting the Initialization Properties
The initialization properties are a list of parameters that you can use
to change how the WFS servlet functions or to determine the values
returned by the Capabilities file. The file containing the initialization
properties for the WFS, the wfs_init.properties file, is found in
\webapps\wfs\conf in the folder where you installed Tomcat.
The only property that MUST be set is the
wfs.capabilities.service.online.resource, which is described on
page 25.
To change the defaults:
1. Delete the pound sign (#) in front of the property that you want to
change.
2. Select the value and type the new value.
3. Save the file.
4. Restart Tomcat to unload the servlet from memory.
Table 1 contains the configuration and initialization properties for
the WFS servlet.
Table 1: Properties for Configuration and Initialization
Property Description and Default Values
wfs.data.sources.
filename
The wfs.data.sources.filename property
declares the name of the file that lists the
files and layers (data sources) that can
be published on your WFS servlet. You
can set the value to a relative or absolute
path.
By default the value is set to conf/
wfs_data_sources.xml in the folder
where you installed Tomcat.
Geomatica WebServer Suite Installation Guide 23

Chapter 3 - Configuring the Servlet for the Web Feature Service (WFS)
Table 1: Properties for Configuration and Initialization
Property Description and Default Values
wfs.matching.
layer.name.action
wfs.invalid.characters.
action
The
wfs.share.matching.layer.name.action
determines the result when the WFS
servlet detects identically named layers
in the data sources. When the servlet
detects duplicate names, the options are:
exception: It produces an error
message.
ignore: It publishes the first layer and
ignores the remaining layers with
identical names.
mangle: It appends sequential numbers
to duplicate names starting with number
1.
The default is mangle.
The wfs.invalid.characters.action
property determines the result when the
servlet encounters a name that contains
characters that are incompatible with
GML such as spaces, tabs, and
punctuation marks. When the servlet
detects an incompatibility, the options
are:
exception: It produces an error message
and prevents the servlet from starting.
This option is useful to identify names
that do not follow the GML naming
convention.
ignore: It creates GML with XML tag
names and attributes that are not valid
nor well formed.
mangle: It converts the name into one
that is compatible with GML.
The default is mangle.
Table 1: Properties for Configuration and Initialization
Property Description and Default Values
wfs.bad.file.action
wfs.transaction.allow
The wfs.bad.file.action property
determines the result when the servlet
encounters a file that cannot be read
such as when the file is corrupted or uses
a file format that is not compatible with
Geomatica.
exception: It produces an error message
and prevents the servlet from starting. If
a user tries to access this WFS via an
HTTP request, the server produces an
exception message stating that an
unusable file was detected.
ignore: The unusable file is not
published.
The default is ignore.
The wfs.transaction.allow property
defines the read/write property of the
publishable files on the WFS servlet. The
files remain read-only in the Geomatica
WFS client even if this property is set to
“true”.
false: files are read-only
true: files are read/write enabled
The default is false.
24 PCI Geomatics

Configuring the WFS Servlet
Table 1: Properties for Configuration and Initialization
Property Description and Default Values
wfs.transaction.timeout
The wfs.transaction.timeout property
determines the number of seconds
before a time-out error occurs. A time-out
results when a request is blocked due to
another transaction being processed by
the servlet. A transaction blocks all
others from access to the servlet until its
process terminates. A time-out error
results if the blocked request is unable to
access the servlet before time expires.
The default is 120.
Since Geomatica Web Feature Service (WFS) is compliant with the
Open Geospatial Web Feature Service Implementation
Specification, it can respond to the Get Capabilities request. Table 2
contains the properties that you can use to describe the capabilities
available on the WFS servlet. These properties should be changed to
reflect your service.
Table 2: Properties for Get Capabilities
Property Description and Default Values
wfs.capabilities.service
.online.resource
wfs.capabilities.service
.name
wfs.capabilities.service
.title
wfs.capabilities.service
.abstract
The
wfs.capabilities.service.online.resource
property declares the value for the
“OnlineResource” element that appears
in the Capabilities document returned by
the WFS. It contains a URL that provides
more description about the WFS servlet.
If you installed the servlet using the
defaults, replace “localhost” by the name
of the computer or IP address where
Tomcat is installed. If you changed the
directory structure or port number, make
sure the value points to the correct path
for your installation.
The default is http://localhost:8080/wfs/
wfs.
The wfs.capabilities.service.name
property declares the official name of the
servlet as it will appear in the Capabilities
document returned by the WFS.
The default is WFS.
The wfs.capabilities.service.title property
declares the value for the “service-title”
element that appears in the Capabilities
document returned by the WFS.
The default is Web Feature Service.
The wfs.capabilities.service.abstract
property declares the “service-abstract”
element that appears in the Capabilities
document returned by the WFS.
The default is Web Feature Service
implemented by PCI Geomatics Inc.
Geomatica WebServer Suite Installation Guide 25

Chapter 3 - Configuring the Servlet for the Web Feature Service (WFS)
Table 3 contains the properties used to define the namespace for the
WFS servlet. A namespace is used to differentiate your WFS servlet
from others on the Web.
Table 3: Properties for XML Schema Namespaces
Property Description and Default Values
wfs.application.schema
.namespace.prefix
wfs.application.schema
.namespace.url
Testing the WFS Servlet
You can test the installation before you begin adding your own data
after you have:
• Copied the wfs.war file to the folder where you installed Tomcat.
• Started Tomcat.
• Set the wfs.capabilities.service.online.resource property.
To test if the WFS servlet was installed properly, you can use the
following Web page, which is designed to run with the demo files
called wfs_california.pix and wfs_irvine.pix.
To test the WFS servlet:
1. Start the Tomcat server.
The wfs.application.schema.namespace.
prefix property declares the value used to
denote the namespace of the WFS
servlet.
The default value is: pci
The
wfs.application.schema.namespace.url
property declares the URI of the
namespace for the WFS servlet.
The default value is pci:wfsapplication-schema.
2. Open a browser window and type the following address:
http://[hostname]:8080/wfs/index.html
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
3. Click the links under Request. These requests should return xml
documents describing the files in the demo folder.
If an error occurs, it can mean that:
• The environment variable for Geomatica is not set properly (see
“Installing Geomatica” on page 13).
• The environment variable for JAVA_HOME is not set properly (see
“Installing the Java SE Development Kit on a Windows System” on
page 14).
• The .war file is missing (see “Installing .WAR Files” on page 16).
• The .jar files are missing (see “Installing .JAR Files” on page 16).
• Tomcat is not running (see “Exploring the WCS Folder” on page 16).
• The wfs.capabilities.service.online.resource property is not set
properly (see “Setting the Initialization Properties” on page 23).
Publishing Your Data on the WFS
Servlet
After you have installed and configured the WFS servlet, you can
make your geospatial features available to others through the Web.
To add your data to the WFS, you can simply paste your vector files
into the demo folder in \webapps\wfs where Tomcat is installed. By
default the WFS is configured to publish the data stored in the demo
folder.
The WFS can publish georeferenced vector (feature) data with
attributes, except topological layers, in the following formats
supported by PCI Geomatics’s Generic Database (GDB)
Technology: PIX, DXF, DVC, SPC, SPL, SQD, DGN, DWG, IFF,
VEH, E00, NTX, vtx, DBF, SHP, TBA, txt, HDR, MIF, PLT, NET,
OBJ, GIA, GTE, mpp, mps, grf, mpa, tbt, tbb, NTF, DDF, TAB, VQ,
MDB, XLS, lvc, , DVOF, DVD, CGM, LOL, adf, GML, wth, out,
26 PCI Geomatics

Publishing Your Data on the WFS Servlet
and las. For more information about GDB, see http://
www.pcigeomatics.com/products/gdb.html#gdb_info.
If you want to configure the WFS to serve data from other data
sources, you can edit the data source configuration file to add
relative or absolute paths to specific files or entire folders. For more
information, see “Modifying the Data Source Configuration File” on
page 27.
You can edit the data source configuration file or you can create your
own. If you create you own file, you must declare it as the
wfs.data.sources.filename property in the wfs_init.properties file
(see “Setting the Initialization Properties” on page 23).
Exploring the Data Source Configuration File
Using an example is the best way to understand the configuration
file. The default data source configuration file for the WFS, the
wfs_data_sources.xml file, is found in \webapps\wfs\conf where you
installed Tomcat:
demo
The first line in the example indicates that the document is based on
XML version 1.0 and the encoding is UTF-8:
The “Sources” element is the root element of the XML file, which
contains all the other elements in the wfs_data_sources.xml file.
The “Source” element identifies the type and location of the data
source. If you have the data saved in several places, each place must
be identified in a separate “Source” element. The “Source” element
has a “base” attribute, which indicates that the data source is a file or
a folder.
demo
The “Filter” element is used with the “base” attribute. It identifies
the files that you will make available on the servlet. The “Filter”
element always uses the “type” attribute and it is always set to “file”.
By default the “Filter” element is set to “demo”, which is a relative
path to the demo folder in \webapps\wfs in the folder where Tomcat
is installed.
Modifying the Data Source Configuration File
By default the WFS is configured to publish all the data stored in the
demo folder. If you want to configure the WFS to serve data from
other data sources, you can edit the data source configuration file to
add relative or absolute paths to specific files or entire folders.
The data source configuration file is called wfs_data_sources.xml,
and it is in \webapps\wfs\conf where Tomcat is installed. All of the
different data sources can be included in one data source
Geomatica WebServer Suite Installation Guide 27

Chapter 3 - Configuring the Servlet for the Web Feature Service (WFS)
configuration file. You identify each source of data by stating its
location and format using a “Source” element.
The following is an example of a wfs_data_sources.xml file
containing the various methods for adding data sources to the WFS:
demo
*.pix
*.tif
The first data source declared in the file is:
demo
When the “Source” element does not contain an attribute, it defaults
to the “base” attribute with a relative path to \webapps\wfs in the
folder where Tomcat is installed. The “Filter” element is used only
with the “base” attribute. It identifies the files that you will make
available on the WFS. The “Filter” element always uses the “type”
attribute and it is always set to “file”. In the example, the “Filter”
element is set to “demo”, which indicates the demo folder in
\webapps\wfs in the folder where Tomcat is installed.
You can add an absolute path to another folder. In the following
example, you use the “base” attribute to indicate the path to a folder
named demo1. Using this method, all the files in the demo1 folder
are made available on the WFS.
You can limit which files are available on the WFS by using the
“Filter” element. You can use the “Filter” element several times
within one “Source” element. In the following example, only the
PCIDSK files (.pix) and TIFF files (.tif) are made available on the
WFS.
*.pix
*.tif
WFS Troubleshooting Checklist
If the WFS is not functioning properly, one of the settings or
parameters may be set incorrectly. To troubleshoot the installation
and configuration, double-check using the following list:
Step Check
1. Install Geomatica.
See “Installing Geomatica” on page 13
1. Set the Path environment variable for Geomatica.
See “Installing Geomatica” on page 13
2. Install the Java Developer’s Kit and set the environment
variable for JAVA_HOME.
See “Installing the Java SE Development Kit on a
Windows System” on page 14.
28 PCI Geomatics

WFS Troubleshooting Checklist
Step Check
3. Install the Tomcat Server.
See “Installing the Tomcat Server on a Windows
System” on page 14.
4. Copy the .jar files from \gws\shared-jars where you
installed Geomatica and paste it in \shared\lib where you
installed Tomcat.
See “Installing .JAR Files” on page 16.
5. Copy the wfs.war file from the gws folder where you
installed Geomatica and paste it in the webapps folder
where you installed Tomcat.
See “Installing .WAR Files” on page 16.
6. Start the Tomcat server.
See “Exploring the WCS Folder” on page 16.
7. Set the wfs.capabilities.service.online.resource property in
the wfs_init.properties file found in \webapps\wfs\conf in
the folder where you installed Tomcat.
See “Setting the Initialization Properties” on page 23.
8. Place your files into the demo folder in \webapps\wfs or
modify the wfs_data_sources.xml in \webapps\wfs\conf.
Both are found in the folder where Tomcat is installed.
See “Modifying the Data Source Configuration File” on
page 27.
9. Stop and restart the Tomcat server.
See “Exploring the WCS Folder” on page 16.
Geomatica WebServer Suite Installation Guide 29

Chapter 3 - Configuring the Servlet for the Web Feature Service (WFS)
30 PCI Geomatics

C HAPTER
4
Configuring the Servlet for the Web Coverage Service (WCS)
Configuring the WCS Servlet
The WCS servlet directly accesses your Geomatica installation when
retrieving the data as shown in Figure 4.1. Therefore, the HTTP
server, WCS servlet and Geomatica should reside on the same
computer. The configuration descriptor for the HTTP server is the
config.xml file found in the \webapps\wcs\WEB-INF\config folder
where you installed Tomcat. The config.xml file contains the elements
that the servlet will use to configure itself.
Once the installation is complete, the WCS servlet can function
using default or automatically generated configuration parameters.
You can change these parameters to fit your needs.
Figure 4.1: Understanding the WCS Servlet
HTTP server
WCS servlet
Servlet accesses Geomatica
Exploring the config.xml for the WCS
The default config.xml for the WCS is located at \webapps\wcs\WEB-
INF\config where you installed Tomcat. It communicates to the HTTP
server the WCS name, its directory path, and the directory path of its
configuration files. You can edit this file as required.
The config.xml file has the following sections:
Folders containing
coverage data files
31

Chapter 4 - Configuring the Servlet for the Web Coverage Service (WCS)
• Service information
• Contact information
• Fees and access constraints
• Online resource parameter
• Temporary directory
• Deployment parameters
• Metadata configuration
• System properties
Service information
This section allows you to specify a label and description of the
service. For example, the label can contain the name of the
organization that is providing the coverage. The description can
contain some details about the coverage, such as, the area name,
coordinates, and geological information.
This section also allows you to add keywords that would quickly
connect users to the coverage. The label, description, and keywords
are all displayed in the XML document that appears at a
getCapabilities request.
Contact information
This section allows you to specify the contact information you want
displayed in the XML document that appears at a getCapabilities
request.
Fees and access constraints
This section allows you to specify any fees or constraints that users
must pay or adhere to before accessing the coverage.
Online resource parameter
This section allows you to specify the online resource parameter.
Because the system automatically detects the online resource for
you, we recommend that you keep the default setting commented
out.
Temporary directory
This section allows you to specify a directory path that is to hold
temporary files that the system creates when processing Web
coverage requests. These files are deleted by the system upon
completion of the requests, or upon shutdown.
If the path you specify exists, ensure that it is writable, otherwise, the
system generates an error. If the path you specify does not exist, the
system automatically creates the path as long as the path is writable.
If you do not specify a path for the temporary files, the system can
create the path upon start up at: ${servlet}/WEB-INF/tmp. An error
is generated, however, if the path is not writable.
32 PCI Geomatics
Note
Do not set the directory in the same location as the metadata directory as
this may cause processing errors.
Deployment parameters
This section has parameters that allow you to specify a custom
deployment file and set monitoring options for a custom or the
default deployment file. A custom TXT file containing EPSG codes
can also be specified. The parameters are described in Table 4.

Configuring the WCS Servlet
Table 4: Deployment parameters and their descriptions
Deployment
Parameters
deployment-
file
monitordeploymentfile
monitordeploymentfiledelay
monitordeploymentcontent
Settings Description
deploy.xml
file or custom.xml
file
An XML file that is validated against
deploy1_0_0.xsd in
webapps\wcs\WEB-INF\config\system
where Tomcat is installed. The
default, deploy.xml, can be modified
or replaced with another XML file.
This file is located at
webapps\wcs\WEB-INF\config
where Tomcat is installed, and for
more information, see “Modifying
the WCS Deployment File” on
page 35.
true Enables monitoring of the deployment
file. When monitoring, applies
any changes made in the file to the
WCS without restarting the server.
false Disables monitoring of the deployment
file.
every
60,000 ms
(per
minute)
(default)
Waits for the specified time before
checking for changes in the deployment
file.
true Enables monitoring of the deployed
coverage files. Updates the WCS
with any changes to the coverage
files without restarting the server.
May use a lot of server resources,
therefore, it can overload the server
if there is a lot of imagery.
false Disables monitoring of the deployed
coverage files.
Table 4: Deployment parameters and their descriptions
Deployment
Parameters
monitordeploymentcontentdelay
supported-crs-
list-file
every
30,000 ms
(per ½
minute)
(default)
Metadata configuration
Settings Description
supported_
crs.txt or
custom.txt
file
Waits for the specified time before
checking for changes in the coverage
files.
Specifies a file that must be in TXT
format. The default,
supported_crs.txt, contains a list of
European Petroleum Survey Group
(EPSG) codes that are published on
the WCS. This file allows you to list
the EPSG codes that you want published.
Only the supported codes of
the coverage are listed in the XML
document that appears at a
describeCoverage request.
This section has parameters that allow you to specify the way in
which you want the system to generate and manage metadata. The
parameters are described in Table 5.
Geomatica WebServer Suite Installation Guide 33

Chapter 4 - Configuring the Servlet for the Web Coverage Service (WCS)
Table 5: Metadata parameters and their descriptions
Metadata
Parameters
metadata-directory
Settings Description
Directs where to create and store
the metadata files. The files are
created by the PACE program
GDBMETA and are stored in
XML format.
If you do not specify a path, the
system creates a location at:
${temporary-directory}/metadata.
If you specify a path that exists,
ensure that the path is writable,
otherwise, the system generates
an error.
If you specify a path that does not
exist, the system automatically
creates the path as long as the
path is writable.
Do not set the directory in the
same location as the temporary
directory as this may cause
processing errors.
You can enter an absolute path
for the metadata files.
Example:
\webapps\wcs\metadata
\webapps\wcs\data
Example:
C:\temp\gdbmeta
Table 5: Metadata parameters and their descriptions
Metadata
Parameters
delete-metadataon-shutdown
System properties
This section allows you to specify the cache management files:
cache.ccf (see http://jakarta.apache.org/jcs) and log4j.xml (see
http://jakarta.apache.org/log4j/).
Testing the WCS Servlet
Before you start adding your own data, you must test the WCS
servlet after you have:
• copied the wcs.war file to the folder where you installed Tomcat and
• started Tomcat.
The test Web page, which is index.html, is designed to run with the
demo files specified in the default deploy.xml file in
\webapps\wcs\WEB_INF\config where you installed Tomcat.
To test the WCS servlet:
1. Start the Tomcat server.
Settings Description
true Deletes metadata files and their
directory during a server shutdown.
false Does not delete metadata files
during a server shutdown.
This is the recommended setting.
2. Open a browser window and type the following address:
http://[hostname]:[port]/wcs/index.html
34 PCI Geomatics

Publishing Your Data on the WCS Servlet
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed. Replace [port] by the number of the
listening port for Tomcat.
3. Click the links under Request. These requests should return
documents describing the files in the data folder in
\webapps\wcs\WEB_INF\data where you installed Tomcat.
If an error occurs, it can mean that:
• The environment variable for Geomatica is not set properly (see
“Installing Geomatica” on page 13).
• The environment variable for JAVA_HOME is not set properly (see
“Installing the Java SE Development Kit on a Windows System” on
page 14).
• The .war file is missing (see “Installing .WAR Files” on page 16).
• Tomcat is not running (see “Exploring the WCS Folder” on page 16).
Publishing Your Data on the WCS
Servlet
After you have installed and configured the WCS servlet, you can
make your coverages available to others through the Web. To add
your data to the WCS, you can paste your files into the data folder in
\webapps\wcs\WEB_INF where you installed Tomcat.
By default, the WCS is configured to publish all of the georeferenced
raster data stored in the data folder if it is compatible with the PCI
Geomatics Generic Database (GDB) technology. For more
information about GDB, see
http://www.pcigeomatics.com/products/gdb.html#gdb_info.
If you want to configure the WCS to serve data from other data
sources, you can edit the deployment file to add specific files and
entire folders. In addition, you can set options for the title and
descriptions of the coverages. For more information, see “Modifying
the WCS Deployment File” on page 35.
Geomatica WebServer Suite Installation Guide 35
Note
In some cases the demands on the WCS servlet will exceed the default
memory allocation of Java. The result is a low memory error. To adjust
the allocated memory size, see “Troubleshooting Low Memory Error in
Tomcat” on page 18.
Modifying the WCS Deployment File
The default WCS deployment file is called deploy.xml, and is used
to deploy coverages to the Web. The file is located in
webapps\wcs\WEB-INF\config where Tomcat is installed and is
validated against deploy1_0_0.xsd.
Figure 4.2 displays the hierarchical structure of the elements used in
the deploy.xml file. These elements manage the display of coverages
on your WCS and provide options that optimize your WCS service.
Serving mosaics
Serving mosaics is a key feature of the WCS. To serve mosaics, you
must:
• set the “coverage-type” parameter to “mosaic” in the Group element
Param, and
• specify the Include path of the images you want included in the
mosaic.
When a request for mosaics is submitted to the WCS, the WCS
creates and serves the mosaics based on the images specified in the
Include paths of the deployment file.

Chapter 4 - Configuring the Servlet for the Web Coverage Service (WCS)
Figure 4.2: Hierarchy of elements within the deploy.xml file
The tables below describe the use of the elements in deploy.xml.
Table 6: Deploy elements and their descriptions
Deploy Element Description
RootPath
Group
Provides the directory path the system must
use to trace through and find the folder(s) or
file(s) specified in the Group\Include. The directory
path can be absolute or relative and can be
overridden by the path specified in Group\Root-
Path. System rules for this override are illustrated
in Table 9, “System trace routes based
on Deploy and Group RootPaths,” on page 38.
Helps you categorize documents. For example,
you can group all of the images for a particular
geographic area. You can have multiple
groups.
Table 7: Group elements and their descriptions
Group Element Description
36 PCI Geomatics
Title
Description
Param
Channels
Allows you to specify a title for the group.
Example: A title for a group of files used
to produce a mosaic.
Allows you to specify a brief description
for the group.
Example: Details of the mosaic coverage.
Specifies the mosaicking of a group of
images. If the “coverage-type” attribute is
set to “mosaic”, the system produces a
virtual mosaic from the specified files in
the group.
If the “coverage-type” attribute is set to
“basic”, each file then becomes an individual
coverage.
If this parameter is commented out, the
system defaults to “basic”.
Allows you to specify the image channels
you want published. The channel numbers
must be integers separated by
spaces.
Examples: 1 2 3
If the Include path specifies a folder, the
specified channels are published for the
folder.
To display different channels for each file,
create separate Include paths. The Group
element can have multiple Include paths.
If the channels are not specified, all of the
channel numbers are published.

Publishing Your Data on the WCS Servlet
Table 7: Group elements and their descriptions
Group Element Description
RootPath
Include
Provides the directory path the system
must use to trace through and find the
folder(s) or file(s) specified in
Group\Include. The directory path can be
absolute or relative and can override the
path specified in Deploy\RootPath. System
rules for this override are illustrated in
Table 9 on page 38.
Only one RootPath can exist for every
Group element.
Allows you to specify directory paths or
names of files you want published on the
WCS.
This element has two attributes:
• “path” allows a relative or absolute URI,
including Oracle connection strings. If
the relative URI is a folder, then the
entire folder is selected.
• “id” allows the tagging of each file
specified in the “path” with a unique
identifier.
You can have multiple Include paths and
use wildcards to specify particular folders
or files. The wildcard: “*” matches zero or
more characters, and the wildcard: “?”
matches only one character.
The system follows a set of rules to trace
the “path”. For more information, see
Table 9 on page 38.
Table 8: Include elements and their descriptions
Include Element Description
Geomatica WebServer Suite Installation Guide 37
Title
Description
Param
Channels
This element is reserved for use in a
future release.
This element is reserved for use in a
future release.
Allows you to monitor the path specified
in Include. Monitors the path for changes,
deletions, and additions with the “monitor”
attribute set to true.
The “monitor” settings (true or false) override
the setting for the config.xml\monitordeployment-content
parameter. Only
when the “monitor” attribute is commented
out or not listed, the system uses
the monitor-deployment-content setting.
Allows you to specify the image channels
you want published. The channel numbers
must be integers separated by
spaces.
Examples: 1 2 3
If the Include path specifies a folder, the
specified channels are published for the
folder.
To display different channels for each file,
create separate Include paths. The Group
element can have multiple Include paths.
If the channels are not specified, all of the
channel numbers are published.
This setting is overridden by the setting in
Group\Channels element.

Chapter 4 - Configuring the Servlet for the Web Coverage Service (WCS)
Table 9: System trace routes based on Deploy and Group
RootPaths
Include
Path
Deploy/
RootPath
data\*.pix Absolute:
c:\maps
data\*.pix Absolute:
c:\maps
data\*.pix Absolute:
c:\maps
data\*.pix Relative:
“maps”
data\*.pix Not
specified
data\*.pix Relative:
“maps”
Group/
RootPath
Absolute:
c:\images
Relative:
“ottawa”
Not
specified
Relative:
“ottawa”
Not
specified
Not
specified
System Trace Route
c:\images\data\*.pix
c:\maps\ottawa\data\*.pix
c:\maps\data\*.pix
c:\program
files\tomcat\webapps\wcs\
web-inf\config\maps\
ottawa\data\*.pix
c:\program
files\tomcat\webapps\wcs\we
b-inf\config\data\*.pix
c:\program
files\tomcat\webapps\wcs\
web-inf\config\maps\
data\*.pix
Note: “ottawa” is not included.
WCS Troubleshooting Checklist
If the WCS is not functioning properly, one of the settings or
parameters may be set incorrectly. To troubleshoot the installation
and configuration, double-check using the following list:
Step Check
1. Install Geomatica.
See “Installing Geomatica” on page 13
Step Check
2. Set the Path environment variable for Geomatica.
See “Installing Geomatica” on page 13
3. Install the Java SE Development Kit Standard Edition
(JDK) 5.0 and set the environment variable for
JAVA_HOME.
See “Installing the Java SE Development Kit on a
Windows System” on page 14.
4. Install the Tomcat Server.
See “Installing the Tomcat Server on a Windows
System” on page 14.
5. Copy the Oracle .jar file, if required, from
\product\$version\client_1\jdbc\lib of your Oracle
installation and paste it in the \shared\lib path of your
Tomcat installation.
See “Installing Oracle® .JAR Files” on page 16.
6. Copy the wcs.war file from the gws folder where you
installed Geomatica and paste it in the webapps folder
where you installed Tomcat.
See “Installing .WAR Files” on page 16.
7. Start the Tomcat server.
See “Exploring the WCS Folder” on page 16.
8. Place your files in the data folder located at
\webapps\wcs\WEB_INF where Tomcat is installed.
See “Modifying the WCS Deployment File” on
page 35.
9. Stop and restart the Tomcat server.
See “Stopping and Restarting Tomcat” on page 18.
38 PCI Geomatics

C HAPTER
5
Configuring the Servlet for the Web Mapping Service (WMS)
Configuring the WMS Servlet
This chapter explains the WMS servlet’s configuration file and its
associated DTD file so you can build, modify and/or manage the
configuration file. The information in this chapter is intended for
users with comprehensive knowledge of HTML, JavaScript, Web
servers, applets and servlets.
The WMS servlet is different from the WFS or WCS servlets.
Instead of accessing data from a folder, the WMS servlet
communicates with the Geomatica WebServer Monitor, which is
Geomatica Focus in server mode. For more information about the
Geomatica WebServer Monitor, see “Starting the Geomatica
WebServer Monitor” on page 49.
The WMS servlet can use one of three methods to retrieve a
configuration file from the Geomatica WebServer Monitor: the Self-
Configured method, the Assisted method, or the Customized
method.
Using the Self-Configured Method
When the WMS servlet is not given a configuration file, it
automatically seeks the Geomatica WebServer Monitor and requests
its configuration file. The Geomatica WebServer Monitor then
responds by sending its default configuration file (see Figure 5.1).
For this scenario to work, Geomatica Focus must be installed on the
same computer as the WMS servlet, and the Geomatica WebServer
Monitor must be running on port 1450 on the same computer as the
WMS servlet.
39

Chapter 5 - Configuring the Servlet for the Web Mapping Service (WMS)
Figure 5.1: Example of a Self-Configured system
HTTP server
WMS servlet
Using the Assisted Method
The WMS servlet automatically
sends a request through port 1450
to the Geomatica WebServer
Monitor for its Capabilities file.
The Geomatica WebServer Monitor
returns its default configuration file (such
as host name, port, layers, etc.).
When the WMS servlet is configured with a location for the
Geomatica WebServer Monitor, it automatically gets the
configuration file from the specified Geomatica WebServer
Monitor. By using the Assisted method, one WMS servlet can
retrieve the configuration file from a specific Geomatica WebServer
Monitor running on any computer in the network (see Figure 5.2).
Two parameters are used to specify the location of the Geomatica
WebServer Monitor: “Focus_HostName” and “Focus_Port”. The
“Focus_ HostName” parameter specifies either the IP address or the
host name where the Geomatica WebServer Monitor is running.
“Focus_Port” specifies which port the Geomatica WebServer
Monitor is using. The method used to set the “Focus_HostName”
and “Focus_Port” parameters for the WMS servlet depends on the
HTTP server technology that you are using (see “Setting Parameters
in Tomcat” on page 43).
If you are using a different port and/or a different host name, use the
Focus_Port and/or Focus_HostName parameters to declare them in
the web.xml file, which is in \webapps\wms\WEB-INF in the folder
where you installed Tomcat. The WMS will get the Capabilities file
from the Monitor using the port and/or host name specified in the
web.xml.
Figure 5.2: Example of an Assisted system
HTTP server
WMS servlet
WMS servlet
You can have several WMS servlets installed on a server with each
assigned to its own Geomatica WebServer Monitor running its own
project. Each WMS servlet retrieves the configuration file from its
assigned Geomatica WebServer Monitor.
Using the Customized Method
You can also create your own configuration file and program the
WMS servlet to retrieve it from a specific location. By creating your
own configuration file, you can program the WMS servlet to gain
access to several projects running on different computers and even
retrieve information from other sources (see Figure 5.3). This
method requires comprehensive knowledge of XML programming.
The MapService_Configuration parameter specifies the path and the
file name of the XML file that the WMS servlet requires to configure
itself. If you create a new configuration file for the WMS, use the
MapService_Configuration parameter to declare its path and
filename in the web.xml, which is in \webapps\wms\WEB-INF in the
folder where you installed Tomcat. The WMS will get your
configuration file from the location declared in the web.xml.
“Creating the Servlet Configuration File” on page 41 provides a
description of the valid tags allowed in the XML file, including the
WMS servlet’s Document Type Definition (DTD) file.
40 PCI Geomatics

Creating the Servlet Configuration File
Figure 5.3: Example of a customized system
HTTP server
WMS servlet
Creating the Servlet Configuration File
You can create your own configuration file or you can export one
from your Geomatica project.
Exporting the XML Project
From your project in Geomatica Focus, you can create an XML file
that you can modify for use as a configuration file. By default
Geomatica will use port 1450 and the name of the computer
currently running the Geomatica project as the host name.
To export the XML file:
1. Open your Geomatica project.
The WMS servlet
retrieves your
configuration file that
enables it to access
information from any
source that you specify.
2. In the File menu, click Utility, and then click Export XML Project.
3. Save the XML file in \webapps\wms in the folder where you
installed Tomcat.
You can edit the XML file to include the correct host name and port
number, combine it with other projects’ exported XML files, or
modify it to suit your needs. After the configuration file for the
WMS servlet is complete, specify the path and the file name of the
configuration file by using the MapService_ Configuration
parameter in the web.xml file (see “Setting Parameters in Tomcat”
on page 43).
Exploring the Initialization Parameters
Two sets of parameters change how the WMS servlet reacts. One set
affects how it functions and the other control what values appear in
the Capabilities file. Refer to “Setting Parameters in Tomcat” on
page 43 for an example of how to set these parameters. Setting the
servlet’s parameters depends on your HTTP server technology. If
you are using a server other than Tomcat, please refer to that server’s
documentation for details.
Changing the Function
The web.xml contains a list of parameters that are commented out by
default, but you can use them to customize the servlet. The first set
of parameters determines how the WMS servlet functions (see
Table 10). Each time you change the parameters, restart Tomcat to
unload the servlet from memory.
To be compliant with the WMS specification, all the layers
published in the capabilities document must have a bounding box
measured using latitude and longitude (Lat/Long) coordinates.
When the parameter is set to true, the servlet runs in
OGC_Compliancy_Mode. In OGC_Compliancy_Mode only the
georeferenced layers from which a Lat/Long bounding box can be
derived are published. When the parameter is set to false, all the
layers in the project are published in the capabilities document
whether a Lat/Long bounding box can be derived or not.
Geomatica WebServer Suite Installation Guide 41

Chapter 5 - Configuring the Servlet for the Web Mapping Service (WMS)
Table 10: Change the Function
Service_Debug
OGC_Compliancy_Mode
Capabilities_DTD_URL
Focus_Port
Focus_HostName
MapService_Configuration
Changing the Values
Service_Debug helps you to debug
the WMS servlet during installation
and development. By default, Service_
Debug parameter is not activated.
OGC_Compliancy_Mode specifies
whether the WMS servlet is running in
OGC compliancy mode or not. By
default, the OGC_Compliancy_Mode
parameter is set to false.
Capabilities_DTD_URL specifies the
HTTP address of the Capabilities’s
DTD (capabilities_1_0_0.dtd) that is in
\webapps\wms\DTD in the folder
where you installed Tomcat. By
default the address is http://
[localhost]:8080/wms/DTD/
capabilities_1_0_0.dtd.
Focus_Port is a number that specifies
which port the Geomatica WebServer
Monitor is using (see “Using the
Assisted Method” on page 40).
Focus_HostName specifies either the
IP address or the host name where
Geomatica WebServer Monitor is
running (see “Using the Assisted
Method” on page 40).
MapService_Configuration specifies
the path and file name of the XML file
that the WMS servlet requires to
configure itself (see “Using the
Customized Method” on page 40).
Since Geomatica WebServer is compliant with the Open Geospatial
Web Map Server Interface Implementation Specification, it can
provide a Capabilities file. The web.xml contains a list of parameters
that are commented out by default, but you can use them to
customize the servlet. The second set of parameters (see Table 11
and Table 12) determines the values returned in the Capabilities file.
To comply with the Open Geospatial Web Map Server Interface
Implementation Specification, you must enter values corresponding
to your project. By default unspecified values are given the default
value of “none”, except the parameter Service_Name which is
“GetMap” by default. Each time you change the parameters, restart
Tomcat to unload the servlet from memory.
Table 11: Change the Capabilities Values
(compatible with version 1.0.0 and higher)
Service_Name
Service_Title
Service_Abstract
Service_KeyWord
Service_OnlineResource
Service_Fees
The Service_Name parameter is
defined as “GetMap” within the Web
Mapping Specification namespace.
The Service_Title parameter contains
a title to identify the server to the user.
The Service_Abstract parameter is a
descriptive statement about the
server.
The Service_KeyWord parameter
provides a register of short words to
help with catalogue searching.
Currently, no controlled vocabulary is
defined.
The Service_OnlineResource
parameter declares the top-level
HTTP URL or home page for your
service.
The Service_Fees parameter
indicates the fees imposed on the
user. The reserved keyword “none”
indicates that no fees exists.
42 PCI Geomatics

Reconfiguring Geomatica Focus Project Using EASI
Table 11: Change the Capabilities Values
(compatible with version 1.0.0 and higher)
Service_AccessConstraint
Table 12: Change the Capabilities Values
(compatible with version 1.1.1 and higher)
Path_Contact_Information
Setting Parameters in Tomcat
The Service_AccessConstraint
parameter indicates the access
constraints imposed on the user. The
reserved keyword “none” indicates
that no constraint exists.
The Path_Contact_Information
parameter declares the file containing
the contact or support information for
your service.
If you are using Tomcat as your HTTP server, the parameters are set
in the web.xml file found in \webapps\wms\WEB-INF in the folder
where you installed Tomcat. Each time you change the parameters,
restart Tomcat to unload the servlet from memory. For example, the
code below sets the MapService_Configuration parameter in the
web.xml file:
MapService_Configuration
C:\configuration.xml
Reconfiguring Geomatica Focus Project
Using EASI
EASI is a scripting language that you can use for querying,
specifying parameter values, and executing tasks. You can build an
EASI script to automatically compute more complex or timeconsuming
results. With EASI you can access and manipulate raster
imagery, vector data, projection information, general binary files,
and text files.
To open the EASI Servlet:
1. Make sure that Tomcat is running and the Geomatica WebServer
Monitor is running with a Geomatica Focus project.
2. Type the following in the address bar of your browser:
http://[localhost]:8080/wms/EasiServlet
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
3. In the EASI Editor box, type the EASI script that you want to use.
For example, to open a Geomatica Focus project from a remote
location, you can type:
Call ReadJOLTProjectFile ("C:\\Program
Files\\Geomatica_V100\\demo\\newport.gpr")
4. Click Process EASI.
5. Restart Tomcat. You can also restart Tomcat from a remote location,
see “Resetting the Servlet from a Remote Location” on page 43.
Resetting the Servlet from a Remote
Location
When you make changes in your Geomatica Focus project, you must
update the MapService with the new map data set. To do this,
normally you stop and restart Tomcat through the command prompt
(see “Exploring the WCS Folder” on page 16). If you are at a remote
location from the servlet, you can used the MapService Reset Button
to stop and restart it.
To reset the MapService:
1. Make sure that Tomcat is running and the Geomatica WebServer
Monitor is running with a Geomatica Focus project.
Geomatica WebServer Suite Installation Guide 43

Chapter 5 - Configuring the Servlet for the Web Mapping Service (WMS)
2. Type the following in the address bar of your browser:
http://[localhost]:8080/wms/Reset.html
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
Exploring the Syntax of the Servlet’s
Configuration File
Using an example is the simplest way to describe the syntax of the
WMS servlet’s configuration file. By consulting the MapService-
Config.dtd, you can validate any modifications that you make to the
file.
The following configuration file contains a layer from Geomatica
WebServer Monitor running on the computer “Host” using port
1455:
image
FocusConnector
1455
Host
Default
The first line in the example indicates that the document is based on
XML version 1.0 and the encoding is UTF-8:
The “mapservice-config” element is the root of the XML file where
you declare all the map layers.
. . .
Within the “mapservice-config” element, the next lines shown in the
example state the “map” element with a style sheet and the map
layer. The stylesheet determines the format for the results of the
queries that you perform.
Each “maplayer” is identified by a unique “layerid”. The layer ID
corresponds to the names of the layers in the Capabilities, which is
“Boundaries” in this example:
The “queryable” attribute in the “maplayer” element indicates
whether the layer can be queried about layer attributes or not. If the
value is “true”, queries are possible. If the value is “false”, queries
are not possible.
The “layertype” element defines the type of layer, which is “image”
in the following line from the example:
image
44 PCI Geomatics

Exploring the Contents of the Servlet’s DTD
The “mapprovider” element indicates where the layer is retrieved.
When “mapprovider” element is FocusConnector, you require the
“port” tag and the “hostname” tag as shown in the following
example. The “port” tag determines which port Geomatica
WebServer Monitor is using to communicate with the WMS servlet.
The “hostname” tag determines the IP address or the computer where
Geomatica WebServer Monitor is running.
FocusConnector
1455
Host
The “bbox” element declares the Spatial Reference System used and
the bounding box value of the image, as shown in the following
example. Requests about the layer are sent only if the values returned
fall within the specified bounding box. For example:
The “style” element determines the number of styles supported by
the map layer. For example:
Default
You can use other elements to further describe the layers. As shown
in the following example, the “title” element provides users with a
title for the layer and the “abstract” element provides a description
of the layer. For example:
Overview of the project
The Boundaries map layer defines the outline
of the incorporated cities.
Exploring the Contents of the Servlet’s
DTD
The mapService-Config.dtd is a DTD that contains the formal
definitions for all the data elements used in the WMS servlet’s
configuration file. By consulting the mapService-Config.dtd, you
can validate any modifications that you make to the file.
The mapService-Config.dtd is an XML file using XML version 1.0
and encoding UTF-8:
The “mapservice-config” element is the root of the WMS servlet’s
configuration file:
The “map” element is a container for one to several map layers. It is
defined in the DTD as follows:
The “maplayer” element is a child of the “map” element. It
represents a map layer that is identified by its layer ID in the
Capabilities. The “maplayer” element contains title, layertype,
hostname, port, mapprovider, bbox, style, urladdress, and abstract
child elements and the layerid and queryable attributes. The
“maplayer” child element is defined in the DTD as follows:
The “title” element is optional, however, it provides more
description than the “layerid” attribute. Usually, the “layerid”
attribute cannot be read by users so use the “title” element to
Geomatica WebServer Suite Installation Guide 45

Chapter 5 - Configuring the Servlet for the Web Mapping Service (WMS)
describe the layer. The “title” element is defined in the DTD as
follows:
The “layertype” element is required to identify the type of layer,
such as an image, a feature, and so on. The “layertype” element is
defined in the DTD as follows:
The “hostname” element is required when the map provider is
FocusConnector. The host name is the name of the computer where
Geomatica WebServer Monitor is installed. The “hostname” element
is defined in the DTD as follows:
The “port” element is also required when the map provider is
FocusConnector. The “port” element indicates the path where
Geomatica WebServer can locate an image in a Geomatica project
and send it to the applet. The “port” element is defined in the DTD
as follows:
The “mapprovider” element is required to indicate the type of
provider needed to provide the layer. Two kinds of map providers
exist, FocusConnector and URLConnector.
FocusConnector: The FocusConnector can retrieve the images from
Geomatica WebServer Monitor.
URLConnector: The URLConnector retrieves images from an
address on the Internet (URL). For example, the URLConnector can
access an image from a map provider.
The “mapprovider” element is defined in the DTD as follows:
The “bbox” or bounding box element is required for each layer. The
“bbox” element indicates the edge of the bounding box in the units
of the specified Spatial Reference System (SRS). The “bbox”
element is defined in the DTD as follows:
The “style” element is required to define the style supported by the
layer. The “style” element is defined in the DTD as follows:
The “urladdress” element is required when the map provider is
URLConnector. It indicates the Internet address where the map is
located. The “urladdress” element is defined in the DTD as follows:
The “abstract” element provides more information about the layer.
The “abstract” element is defined in the DTD as follows:
The “stylesheets” element declares the style sheet used to format the
results of the queries. The “id” attribute defines the filename of the
style sheet. The “path” attribute defines the path where the file is
found. These are defined in the DTD as follows:
46 PCI Geomatics

Viewing the MapService-Config DTD
Viewing the MapService-Config DTD
The following is the mapService-Config.dtd in its original form:

Chapter 5 - Configuring the Servlet for the Web Mapping Service (WMS)
The style element defines the style supported by the
layer.
-->
48 PCI Geomatics

C HAPTER
6
Publishing Your Maps on the WMS Servlet or a Web Page
Publishing Your Data on the WMS
Servlet
With the WMS servlet you can make your maps available to others
through the Web. After you have installed and configured the WMS
servlet, start the WebServer Monitor with you maps project (see
“Starting the Geomatica WebServer Monitor” on page 49). The
WebServer Monitor provides access to your data to others on the
Web. You can also display your project in a Web page (see
“Publishing Your Maps in a Web Page” on page 50).
When you are building a project, remember the following:
1. Separate your project into layers with similar items together on one
layer. For example, put the highways on one layer and the railroads
on a separate layer.
2. Identify each layer with a clear, concise, and unique name that
represents what appears on the layer. For example, you can name the
highway layer HIGHWAYS.
3. Avoid using spaces and commas from the layer names. When the
Geomatica WebServer Monitor prepares the project for the Web,
spaces and commas are removed, which may cause errors to occur.
To avoid problems, label your layers using only the letters of the
alphabet, numbers, and the underscore “_”. Other characters may
produce unwanted results or errors.
Tip
When the Shortcut to Focus.exe is used for the Geomatica WebServer
Monitor, you can start Geomatica Focus from the Windows Start button
or create a new shortcut.
Starting the Geomatica WebServer
Monitor
The Geomatica WebServer Monitor is Geomatica Focus in server
mode. As explained in Figure 6.2 on page 51, it provides the WMS
servlet with a communication port to the map project that you want
to publish and to the Geomatica Focus executable routines so it can
process the requests made by the WMS client. The Geomatica
WebServer Monitor and the WMS servlet can run on separate
computers as long as they can communicate over the network.
49

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
To start the Geomatica WebServer Monitor:
1. Create a shortcut to Geomatica Focus on your desktop.
2. Right-click the shortcut.
3. Click Properties.
4. In Target box on the Shortcut tab, add “ -webserver”, the port
number and the path for the project. The synopsis of the command is:
-webserver [port] projectfile
As an example, use one of the existing projects in Geomatica’s
demo folder to start the Geomatica WebServer Monitor. The path
in Target box on the Shortcut tab should appear something like
this:
“C:\Geomatica_V100\exe\Focus.exe” -webserver 1450
“C:\Program Files\Geomatica_V100\demo\newport.gpr”
Note
Verify that port 1450 is available.
5. Click OK.
6. Double-click the Shortcut to focus.exe on your desktop.
Geomatica Focus then opens the Geomatica WebServer Monitor,
as shown in Figure 6.1. If the Geomatica WebServer stops
responding, the earth graphic stops moving.
Figure 6.1: Example of the Geomatica WebServer Monitor
Publishing Your Maps in a Web Page
You can also publish your maps on a Web page. Geomatica
WebServer Suite provides you with the WMS servlet, a WMS client
(applet and browser combination), assorted HTML templates, a
library of button icons, and JavaScripts for adding functions to your
Web page. Even if you possess only rudimentary programming
skills, you can easily publish your project on the Web by using one
of the templates.
To publish your maps on a Web page:
1. Create a map project in Geomatica Focus.
2. Install the WMS servlet as explained in “Installing the HTTP Server
and Servlets” on page 13.
3. Create a Web page. You can start with “Using the Basic Template to
Display Your Project” on page 52, which shows you how to use one
of the HTML templates to publish your project on the Web.
50 PCI Geomatics

Introducing the Templates
Figure 6.2: Interactions between the components
Introducing the Templates
Geomatica WebServer includes six templates that you can use to
publish your project on the Web. Each template showcases different
features that you may want for your own Web page. When you have
Tomcat and the Geomatica WebServer Monitor running, you can
view the templates using one of the demo projects provided in the
Demo folder located in the Geomatica folder.
To view the templates:
The applet and browser work
together as a WMS client. As
you perform functions on the
map in the applet, it sends
requests to the HTTP server.
The WMS servlet uses Geomatica
WebServer Monitor to access
Geomatica Focus and the map project.
The HTTP server sends the requests to the
WMS servlet which communicates with
the Geomatica WebServer Monitor.
HTTP server
WMS servlet
1. Make sure Tomcat is running and the Geomatica WebServer
Monitor is started with the newport.gpr project from the Demo
folder.
2. Type the following in the address bar of your browser:
http://[localhost]:8080/wms/Readme.html
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
3. Click the Geomatica Web Server folder.
4. Click Demonstrations.
5. Click Templates.
Geomatica WebServer includes six templates:
•Click Tool Reference to view the descriptions and use of all the tools
available in the templates.
•Click MapViewerTemplate1.html: this basic template includes the
map window and the Pan and Zoom features.
•Click MapViewerTemplate2.html: this template includes the map
window, Pan, Recenter, Overview, Progressive Zoom, Zoom In,
Zoom Out, Zoom Window, Zoom and Pan, and check boxes to select
layers.
•Click MapViewerTemplate3.html: this template includes all the
features available in MapViewerTemplate2.html plus check boxes to
select layers for queries, a General Query button, and an Overview
window.
•Click MapViewerTemplate4.html: this template includes all the
features available in MapViewerTemplate2.html plus check boxes to
select layers for queries, a Query Select Point button, a Length tool,
Area tool, Circle tool, and an Overview window.
•Click MapViewerTemplate5.html: this template includes all the
features available in MapViewerTemplate3.html plus a Line tool,
Polygon tool, a Line Query tool, a Polygon Query tool, and a Saved
Query button.
•Click MapViewerTemplate6.html: this template includes all the
features available in MapViewerTemplate3.html plus the Query
Form button.
Geomatica WebServer Suite Installation Guide 51

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
Using the Basic Template to Display
Your Project
MapViewerTemplate1.html is a very basic model for a Web page.
Web users will only be able to pan and zoom using their left and right
mouse buttons. To create a more interesting Web page, see “Using
the Templates for Your Web Page” on page 52 or “Making Your
Own Web Page” on page 54.
To use MapViewerTemplate1 for your Web page:
1. Start the Geomatica WebServer Monitor with your project in the
Target box (see “Starting the Geomatica WebServer Monitor” on
page 49). For example: in Target box on the Shortcut tab, type:
C:\Geomatica_V100\exe\Focus.exe -webserver 1450
C:\YourProject\projectX.gpr
2. Restart the HTTP server (see “Exploring the WCS Folder” on
page 16).
3. Open your browser window. In the address bar type
http:\\[localhost]:8080\wms\MapViewerTemplate1.html
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
4. Press ENTER.
Using the Templates for Your Web Page
As described in “Introducing the Templates” on page 51, Geomatica
WebServer offers you six different templates that you can use as is
or modify to suit your needs. Of course, if you are at ease with
HTML, you can create your own Web page.
To create a Web page for your project, you must:
1. Create an applet configuration file using Extensible Markup
Language (XML).
2. Create a Hypertext Markup Language (HTML) file.
Creating Your Applet’s XML File
The XML file contains the names of the layers in the project and
other data required to form the HTML file. Since Geomatica
WebServer is compliant with the Open Geospatial® Web Map
Server Interface Implementation Specification, Revision 1.1.1, you
can generate a capabilities document from your project and use it to
create your project’s XML file. A Capabilities document is an XML
file that conforms to the Capabilities Interface DTD. The XML file
can list the interfaces that the Map Server supports, the layers the
map contains, and what formats it can use.
To create your XML file:
1. Start the Tomcat server.
2. Start the Geomatica WebServer Monitor with your project.
3. In your browser type:
http://[localhost]:8080/wms/AppletConfigServlet
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
4. Press ENTER.
5. On the Web page in the Address box, type
http://[localhost]:8080/wms/WMSServlet
Replace [localhost] by the name of the computer or IP address
where Tomcat is installed.
6. Click Connect.
7. Under LayerID, select the layers that you want to include in your
Web page.
8. Under Queryable, select the layers that will support queries.
52 PCI Geomatics

Using the Templates for Your Web Page
9. Under Format, select the graphics file format that you want to use.
10. Click Save As.
11. Click Save to download the file to your computer, and save the
XML file in \webapps\wms\Config in the folder where you installed
Tomcat.
Matching the Coordinate System Between Your Project and
Web Page
The measurement tools and any button that you program to display
the coordinates in the status bar will display the coordinates in paper
units (EPSG:NONE) by default. You can change the default to the
EPSG (European Petroleum Survey Group) coordinate system used
in your project.
Table 13: EPSG codes
Code Unit
none millimeters
4000 to 5000 degrees
All others meters
To use the same coordinate system as your project:
1. Start Tomcat and Geomatica WebServer Monitor with your project.
2. Type the following in the address bar of your browser:
http://[localhost]:8080/wms/
WMSServlet?wmtver=1.0.0&request=capabilities
Replace [localhost] by the name of the server where your project is
located.
3. Locate the EPSG code used for your layers. For example, the
“Lakes” layer in the Newport project is SRS="EPSG:26711".
4. Open the applet’s XML file that you created in a text editor, such as
Wordpad.
5. Above the map element, type the viewport element with the EPSG
code.
6. Save the XML file.
Below is an example of how the layers.xml file from
\webapps\wms\Config in the folder where you installed Tomcat would
look like with the viewport element:
Creating Your HTML File from an Example
The HTML file contains the data required for browsers to display
your Web page. You can use one of the MapViewerTemplate.html
Geomatica WebServer Suite Installation Guide 53

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
files located in \webapps\wms in the folder where you installed Tomcat
as an example.
To create your HTML file using one of the templates:
1. Make a copy of a MapViewerTemplate.html file in \webapps\wms in
the folder where you installed Tomcat (copy and paste into wms).
For a description of the differences between the templates, refer to
“Introducing the Templates” on page 51.
2. Rename the copy of the MapViewerTemplate according to your
project so it will be easier to identify later.
For example, change Copy of MapViewerTemplate3.html to
MyProject.html.
3. Open the HTML file in a text editor, such as Notepad.
4. Locate the applet in the HTML file and replace the XML file in the
applet with your project’s XML file. The XML file and the applet
must be on the same computer. For example, below is the applet
declared in the MapViewerTemplate3.html. You would replace
“layers.xml” by “MyProjectLayers.xml”.
5. Replace ALL of the other project’s layer names by the ones in your
project making sure to type them exactly as they appear in the
project. For example, below is the code for the Lakes layer in the
MapViewerTemplate3.html. You would replace “Lakes” by the your
layer names:
Lakes
6. Delete any unneeded sections. The layers that are queryable contain
an index to describe the order of the layers so make sure that the
numbering is in sequence. For example, the number “3” in the
example from step 5 indicates that this layer is the third in the HTML
file:
ONCLICK="javascript:LayerQueryableSimple(3,'vue')"
7. Save the HTML file.
8. Start the Geomatica WebServer Monitor with your project in the
Target box (see “Starting the Geomatica WebServer Monitor” on
page 49).
9. Restart Tomcat (see “Exploring the WCS Folder” on page 16).
10. Open your browser window.
11. In the address bar type
http://[localhost]:8080/wms/MyProject.html
Replace [localhost] by the name of the computer where your
project is located and replace MyProject.html by the HTML file
that you created for your project.
12. Press ENTER.
Making Your Own Web Page
You can modify the templates to customize the look and
functionality of your Web page or create your own from scratch. To
54 PCI Geomatics

Making Your Own Web Page
create a Web page you need a layout containing the applet and
various functions that you can apply to the applet, such as zoom, pan,
and query functions.
In the HTML file you design how the Web page is going to look. The
JSMapViewer.js, Query.js, and Measurement.js files are the source
files for the JavaScripts that can be used in your Web page. These
files are in \webapps\wms\JavaScript in the folder where you installed
Tomcat.
HTML uses the JavaScript to load functions from the MapViewer.jar
file. The MapViewer.jar file contains the class files and auxiliary
resources for the applet and its applications. It is in \webapps\wms
in the folder where you installed Tomcat.
For the HTML, JavaScript and MapViewer.jar files to function
together, the applet name must remain consistent throughout the
HTML file. For example, the MapViewerTemplate4.html uses the
name “vue” as the applet name:
and it contains the following for the Pan button:
The browser will use the “javascript:Pan('vue')” to find the
Pan function in the JSMapViewer.js file, and then the
JSMapViewer.js file refers to the MapViewer.jar file for the Pan
function.
Displaying Layers
Most of the MapViewerTemplates display rows of check boxes. The
row labeled “View” enables the users to select the layers they want
to see.
The “checkForm” check boxes are designed to show or hide layers
in a project. For example, the MapViewerTemplate2.html contains
the following code used to display a check box for the user to select
a layer and the code for an APPLY button. The APPLY button
enables users to select several layers before performing the function.
Lakes
The MapViewerTemplate2.html uses the name “vue” as the applet
name. The browser will use the “javascript:LayerOnOff('vue')”
to find the LayerOnOff function in the JSMapViewer.js file.
Normally, you will have several layers selectable so you would
create a loop to verify which layers are selected, retrieve the selected
layers, and refresh the applet, as was done for the LayerOnOff
function in the JSMapViewer.js file.
Creating Queryable Layers
Most of the MapViewerTemplates display rows of check boxes. The
row labeled “Query” enables the users to select the layers for a
query. The query boxes are used in conjunction with a query button
of some kind. The response to the query is displayed in a new
browser window.
The “checkFormQuery” check boxes are designed to prepare layers
for queries on the map layer’s attributes. For example, the
Geomatica WebServer Suite Installation Guide 55

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
MapViewerTemplate3.html contains the following code for the
query box for the Lakes layer:
The MapViewerTemplate3.html uses the name “vue” as the applet
name. The browser will use the “javascript:LayerQueryable
Simple(3,'vue')” to find the LayerQueryableSimple function in
the JSMapViewer.js file.
Note
Remember to declare your layers as queryable in the applet’s
configuration file.
Adding Buttons
The MapViewerTemplate HTML files, except
MapViewerTemplate1.html, display a number of default buttons.
You may want to remove some of the buttons, change their style or
use the buttons in your own Web page. The buttons that appear in the
various MapViewerTemplates are shown and explained in the
Readme.html Web page (see “Introducing the Templates” on
page 51) in Reference for Tool Buttons. All the graphics for the
buttons, including some not seen in the MapViewerTemplates, are
located in \webapps\wms\images in the folder where you installed
Tomcat.
Each graphic in the images folder has an “on” version and an “off”
version. The HTML files, except MapViewerTemplate1.html,
include a variable called ArrayButtonName that controls the
appearance of the buttons as they are clicked. To change the graphics
used for the buttons, you can replace the file names of graphics with
those in the images folder. For example, the following HTML
element displays the ArrayButtonName variable shown in
MapViewerTemplate2.html:
After the appearance of the button is programmed, you must
program the functionality of the button. The functionality of the
button is controlled by JavaScript from the JSMapViewer.js,
Query.js, or Measurement.js files. For example, the following is the
HTML element for the pan button as shown in
MapViewerTemplate2.html:
• The SRC attribute declares the path for the graphic used with the
tool.
• The NAME attribute identifies the button in the ArrayButtonName
variable.
• The BORDER attribute determines the width of the button’s outline.
56 PCI Geomatics

Making Your Own Web Page
• The WIDTH and HEIGHT attributes determine the size of the button
in pixels.
• The ALT attribute contains the text string that you want to use if the
graphic is not supperted by the browser, which may also function as a
ToolTip on some browsers.
• The ONMOUSEDOWN attribute determines the actions taken when
you click the button. For example, the browser uses
“javascript:Pan(‘vue’)” to find the Pan function in the
JSMapViewer.js file. The browser uses
“toggleAllButton('pan',ArrayButtonName,8)” to find the
toggleAllButton function in the JSMapViewer.js file. The
toggleAllButton function finds the graphics used in the
ArrayButtonName variable so the pan button can appear on and off
when clicked. The “8” represents the total number of buttons in the
ArrayButtonName variable.
Changing Zoom Values
The JSMapViewer.js file includes several JavaScripts for zoom
functions. The Zoom Functions in Table 14 are programmed with
default values. As explained in “Adding Buttons” on page 56, you
can create buttons with selectable zoom values by changing the
JavaScript used in the ONMOUSEDOWN attribute to one described
in Table 15.
Table 14: Fixed Zoom Functions
JavaScript Function Button Description
ZoomInDefault
(Appletname)
ZoomOutDefault
(Appletname)
ZoomInPercentDefault
(Appletname)
Zoom In
Used to increase the
magnification by a factor of 2.
Zoom Out
Used to decrease the
magnification by a factor of 2.
Zoom In Percent
Used to increase the
magnification by 25 percent.
Table 14: Fixed Zoom Functions
JavaScript Function Button Description
ZoomOutPercentDefaul
t
(Appletname)
ZoomWindow
(Appletname)
ZoomZoom
(Appletname)
PanAndZoom
(Appletname)
Table 15: Programmable Zoom Functions
JavaScript Function Description
ZoomIn(Appletname)
ZoomOut(Appletname)
ZoomInPercent(Appletname)
Zoom Out Percent
Used to decrease the
magnification by 25 percent.
Zoom Window
Used to increase the
magnification within a frame
drawn in the applet.
Progressive Zoom
Used to decrease or increase the
magnification as you drag the
mouse up or down in the applet.
Zoom and Pan
Used to assign the function Pan
to the left mouse button, and the
ZoomZoom to the right mouse
button.
Used in combination with a dropdown
combo box to increase the
scale by a list of values.
Used in combination with a dropdown
combo box to decrease the
scale by a list of values.
Used in combination with a dropdown
combo box to increase the
magnification by a list of percent
values.
Geomatica WebServer Suite Installation Guide 57

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
Table 15: Programmable Zoom Functions
JavaScript Function Description
ZoomOutPercent(Appletname)
Creating a Combo Box
By using the ZoomIn(Appletname) and ZoomOut(Appletname)
JavaScripts and inserting a drop-down combo box named “Factor”
in the HTML file, you can offer a range of values for the users to
select instead of relying on the default factor of 2. For example, the
following HTML code displays the drop-down combo box with a list
of factors as shown in Figure 6.3:
Zoom Factor :
2
3
4
5
Figure 6.3: Factor Combo Box
Used in combination with a dropdown
combo box to decrease the
magnification by a list of percent
values.
By using ZoomInPercent(Appletname) and
ZoomOutPercent(Appletname) and inserting a drop-down combo
box named “ZoomPercentForm” in the HTML file, you can offer a
range of percent values for the users to select instead of relying on
the default factor of 25 percent. For example, the following HTML
code displays a drop-down combo box with a list of percent values
as shown in Figure 6.4:
Zoom Percent :
10
25
50
75
Figure 6.4: ZoomPercentForm Combo Box
Adding Measurement Tools
The Measurement.js file contains three measurement tools that you
can use in your Web page. The JavaScript in the Measurement.js file
is the link between the HTML file and the Mapviewer.jar file. The
HTML uses the JavaScript to load functions from the MapViewer.jar
file.
By default the status bar uses EPSG NONE, which results in the
applet displaying in paper units (mm). If you want the status bar to
display the units in the georeferencing from your project, see
“Matching the Coordinate System Between Your Project and Web
Page” on page 53.
58 PCI Geomatics

Making Your Own Web Page
All three measurement tools appear in MapViewerTemplate4.html.
They are designed to display specific values in the status bar as you
use the tool in the applet. Each tool is described in Table 16 on
page 59. To add the measurement tools to your Web page, you need
to:
• Include the Measurement.js and JSMapViewer.js files in the HTML
file under “Call JavaScript library”
• Include the graphics for the buttons in the ArrayButtonName code
(see “Adding Buttons” on page 56)
• Program the button’s functionality
For example, the MapViewerTemplate4.html contains the following
examples in the ArrayButtonName code:
Table 16: Measurement Tools
JavaScript Function Button Description
lengthMeasure
(Appletname)
areaMeasure
(Appletname)
circleMeasure
(Appletname)
Adding Query Buttons
Line Tool
Used to display in the status bar
the values for the x and y
coordinates of the cursor, the
length of the line, the unit of
measurement, and the length of
the last line segment.
Area Tool
Used to display in the status bar
the values for the x and y
coordinates of the cursor, the
perimeter and area of the shape,
and the unit of measurement.
Circle Tool
Used to display in the status bar
the values for the x and y
coordinates of the cursor, the
coordinates of the center of the
circle, the radius, the perimeter,
and area of the circle, and the
unit of measurement.
The query tools are designed to retrieve and display the requested
attributes from your project. The MapViewerTemplates contain
several query tools: query buttons, saved queries, and query
expressions. This section explains the query buttons. For
information about the saved queries, see “Adding Shortcuts to Saved
Queries” on page 63. For information about the query expressions,
see “Providing a Tool to Build Query Expressions” on page 63.
Geomatica WebServer Suite Installation Guide 59

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
The Query.js file contains the JavaScript that you need to add the
query buttons to your Web page. The JavaScript in the Query.js and
JSMapViewer.js files are the link between the HTML file and the
Mapviewer.jar file. The HTML uses the JavaScript to load functions
from the MapViewer.jar file.
General Query Button
The General Query button appears in MapViewerTemplate3.html,
MapViewerTemplate5.html, and MapViewerTemplate6.html. It
retrieves and displays all the attributes from the selected layers.
Adding the General Query button to your Web page is similar to
adding the measurement tools (see “Adding Measurement Tools” on
page 58) to your Web page. You need to include the JSMapViewer.js
and the Query.js files in the HTML file under “Call JavaScript
library”, and you need to include the graphics for the buttons in the
ArrayButtonName variable (see “Adding Buttons” on page 56).
In addition to the ArrayButtonName variable, you also need to add
code to automatically return the button to its original state after the
query is performed, otherwise the button will appear “on” even
though the query is complete. For example, the following code
appears below the ArrayButtonName variable in
MapViewerTemplate5.html:
function toggleInfoQuery()
{
document.images['query'].src='images/off_car_info.gif';
}
After the appearance of the button is programmed, you must
program the functionality of the button. The functionality of the
button is controlled by JavaScript from the JSMapViewer.js and the
Query.js files. For example, the following is the HTML element for
the General Query button as shown in MapViewerTemplate5.html:
ONMOUSEDOWN="javascript:LayerQueryable('vue');
DisplayFeatureInfo('vue','xslt.xslt');
toggleAllButton('query',ArrayButtonName,13);
setTimeout('toggleInfoQuery()',2500)"
The SRC, NAME, BORDER, WIDTH, HEIGHT, and ALT
attributes are described in “Adding Buttons” on page 56. The
ONMOUSEDOWN attribute determines the actions taken when you
click the General Query button. For example, the browser uses:
•“javascript:LayerQueryable(‘vue’)” to find the
LayerQueryable function in the JSMapViewer.js file, which verifies
which layers were selected for the query.
•“DisplayFeatureInfo('vue','xslt.xslt')” to find the
DisplayFeatureInfo function in the Query.js file, which retrieves and
displays the attributes from the selected layers using the layout
described in the xslt.xslt file. XSLT is a style sheet language which
governs how the data retrieved from the project is presented.
•“toggleAllButton('query',ArrayButtonName,13)” to find the
toggleAllButton function in the JSMapViewer.js file, which finds the
graphics used in the ArrayButtonName variable so the button can
appear on and off when clicked. The “13” represents the total number
of buttons in the ArrayButtonName variable.
•“setTimeout('toggleInfoQuery()',2500)” to automatically
return the button to its original status after a specified delay. The
toggleInfoQuery function, which appears in the HTML file below the
ArrayButtonName variable, defines the appearance of the button, and
the “2500” defines the delay in milliseconds.
Table 17: General Query Button
JavaScript Function Button Description
DisplayFeatureInfo
(AppletName,xsltFile)
General Query
Used to retrieve and display all
the attributes from the selected
layers.
60 PCI Geomatics

Making Your Own Web Page
Spatial Query Buttons
The Spatial Query buttons retrieve and display in a separate window
the attributes from specified areas on the selected layers. The Query
Select Point button appears in MapViewerTemplate4.html. The Line
Tool, Line Query, Polygon Tool, and Polygon Query buttons appear
in MapViewerTemplate5.html. To perform the query, the user makes
a layer available for queries (see “Creating Queryable Layers” on
page 55) and then chooses the query button according to the results
they desire.
Query Select Point button: Adding the Query Select Point button
to your Web page is the same as adding the General Query button to
your Web page (see “General Query Button” on page 60), except the
graphics used in the ArrayButtonName variable and
toggleInfoQuery function are different, and the JavaScript for the
ONMOUSEDOWN is different as shown in
MapviewerTemplate4.html:
var ArrayButtonName =
[['query','images/off_car_inf_point.gif','images/
on_car_inf_point.gif']
function toggleInfoQuery()
{
document.images['query'].src='images/off_car_inf_
point.gif';
}
The ONMOUSEDOWN attribute for the Query Select Point button
uses “javascript:QueryPointMode('vue','QueryResults')” to
find the QueryPointMode function in the Query.js file.
Tip
If you are familiar with creating HTML files with frames, the JavaScript for
Query Select Point contains the windowName parameter, which you can
use to display the query result in a frame in your Web page instead of in
separate window.
Line Query and Polygon Query buttons: Adding the other Spatial
Query buttons to your Web page is similar to adding the General
Query button (see “General Query Button” on page 60), except they
each need an additional button to work. The Line Query and Polygon
Query buttons need the Line and Polygon tools respectively to
identify the specific location in the applet to query. Therefore, you
need to:
• Include the JSMapViewer.js and the Query.js files in the HTML file
under “Call JavaScript library”.
• Include the graphics for the spatial query buttons and their
corresponding tools in the ArrayButtonName variable (see “Adding
Buttons” on page 56). For example, the following is in
MapViewerTemplate5.html:
var ArrayButtonName =
['line','images/off_car_crt_line.gif','images/
on_car_crt_line.gif'],
['polygon','images/off_car_crt_poly.gif','images/
on_car_crt_poly.gif'],
['lineQuery','images/off_car_inf_line.gif','images/
on_car_inf_line.gif'],
['polygonQuery','images/
off_car_inf_poly.gif','images/
on_car_inf_poly.gif']];
• Add code to automatically return each query button to its original
state after the query is performed, otherwise the spatial query buttons
will appear “on” even though the query is complete. For example, the
code to do this appears below the ArrayButtonName variable in
MapViewerTemplate5.html:
function toggleInfoQueryLine()
{
Geomatica WebServer Suite Installation Guide 61

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
document.images['lineQuery'].src = 'images/off_car_
inf_line.gif';
}
function toggleInfoQueryPoly()
{
document.images['polygonQuery'].src = 'images/off_car_
inf_poly.gif';
}
• Program the functionality of the buttons. The functionality of a
button is controlled by JavaScript from the JSMapViewer.js and the
Query.js files. For example, the following are the HTML elements
for the Line tool, Polygon Tool, Line Query and Polygon Query in
MapViewerTemplate5.html:
The SRC, NAME, BORDER, WIDTH, HEIGHT, and ALT
attributes are described in “Adding Buttons” on page 56. The
LayerQueryable, toggleAllButton and setTimeout attributes are
described in “General Query Button” on page 60. The
ONMOUSEDOWN attribute determines the actions taken when you
click the buttons. For example, the browser uses:
•“javascript:Line(‘vue’)” from the Line Tool to find the Line
function in the Query.js file. You use the Line Tool to draw a line in
the applet to identify the location that you want to query.
•“javascript:Polygon(‘vue’)” from the Polygon Tool to find the
Polygon function in the Query.js file. You use the Polygon Tool to
draw a polygon in the applet to identify the area that you want to
query.
•“SendQuery('vue','HTML','Intersect')” from the Line Query
and Polygon Query buttons to find the SendQuery function in the
Query.js file. The SendQuery function retrieves and displays the
attributes from the selected layers for the area identified by the line or
polygon. The “vue” is the applet’s name. The “HTML” declares that
the attributes will be displayed in HTML using the layout described
in the xslt.xslt file. You can also replace “HTML” with “XML”. The
“Intersect” spatial filter defines which attributes are retrieved. For
polygons, you can replace “Intersect” with Crosses, Overlap, or
Within. More explanations for the Spatial Queries appear in the
Readme.html Web page (see “Introducing the Templates” on
page 51) in the Query folder in Spatial Query.
Table 18: Spatial Query Tools
JavaScript Function Button Description
QueryPointMode('vue',
'QueryResults')
Line(‘vue’)
Query Select Point
Used to request attributes from
features in your project by
selecting a point in the applet.
Line Tool
Used to draw a line in the applet.
62 PCI Geomatics

Making Your Own Web Page
Table 18: Spatial Query Tools
JavaScript Function Button Description
SendQuery('vue',
'HTML','Intersect')
Polygon(‘vue’)
SendQuery('vue',
'HTML','Intersect')
Providing a Tool to Build Query Expressions
A query expression is a combination of operators, functions,
constants, and variables that you use to retrieve specific attributes
from a layer. To provide query expressions from your Web page, you
need to program a button to open a new window that you can use to
build query expressions. The WMS provides a form, called
Post.html, that contains several options you can use to create the
window for the query expressions. Post.html is in \webapps\wms in
the folder where you installed Tomcat.
For example, the following appears before the ArrayButtonName
variable and below the Overview applet in
MapViewerTemplate6.html:
function redirectWindow()
{
window.open("Post.html");
}
Line Query
Used to request attributes from
the features from the selected
layers in your project. The
features are identified by the line
drawn in the applet.
Polygon Tool
Used to draw a polygon in the
applet.
Polygon Query
Used to request attributes from
the features from the selected
layers in your project. The
features are identified by the
polygon drawn in the applet.
The ONCLICK attribute uses “javascript:redirectWindow()” to
find the redirectWindow function in the HTML file. The
“redirectWindow()” function opens a new browser window using
Post.html. The Post.html is a form that the user completes. When the
user clicks Send Request, it retrieves and displays the attributes from
the selected layer .
Adding Shortcuts to Saved Queries
Saved queries are useful when you have to repeatedly perform a
query. Saved queries retain the expression, not the results.
Therefore, you can avoid recreating the query expression every time
that you need to perform the query. You can add as many saved
queries to your Web page as you require.
To add a saved query to your Web page, you can simply create and
program a button, such as:
The browser will use the
“javascript:PropertyQuery('vue','length>0.6',
'RoadNetwork')” to find the PropertyQuery function in the
Query.js file. The PropertyQuery function retrieves and displays the
attributes that results from the query expression. The “vue” is the
applet’s name. The “length> 0.6” is the query expression. You can
build the expression using any of the operators available in
GDBQuery explained at www.pcigeomatics.com/cgi-bin/pcihlp/
gdbquery. The results are displayed by default in HTML using the
layout described in the xslt.xslt file. The “RoadNetwork” identifies
the layer to be queried.
Geomatica WebServer Suite Installation Guide 63

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
However, you can make the saved query more evident by providing
a concise description of the query with the button, such as the
example that appears in MapViewerTemplate5.html, which is nested
in a table:
SAVED QUERY
Hydrological channels with a length greater than 10 km:
Adding a Tool to Display the Coordinates in the
Status Bar
You can design a tool to retrieve the coordinates on-the-fly and
display them in the status bar. You can assign this functionality to
the cursor itself or to a button.
To change the cursor so it displays the coordinates, you
need to:
• Assign the function to the cursor. For example:
function displayCoordinate()
{
document.applets['vue'].cursorTool();
}
• Activate the function when the page opens. For example:
To add a button to your Web page with the
displayCoordinate function, you need to:
• Include the JSMapViewer.js file in the HTML file under “Call
JavaScript library”.
• Include the graphics for the buttons in the ArrayButtonName code
(see “Adding Buttons” on page 56). For example:
var ArrayButtonName =
['Point','images/off_car_xy.gif','images/
on_car_xy.gif'],
• Program the button’s functionality. For example:
The SRC, NAME, BORDER, WIDTH, HEIGHT, and ALT
attributes are described in “Adding Buttons” on page 56. The
toggleAllButton attribute is described in “General Query Button” on
page 60. The ONMOUSEDOWN attribute uses
“javascript:displayCoordinate('vue')” to find the
displayCoordinate function in the JSMapViewer.js file.
By default the status bar displays in paper units (mm). If you want
the status bar to display the units using the projection from your
project, see “Matching the Coordinate System Between Your Project
and Web Page” on page 53.
Displaying an Overview of Your Project
The Overview is a small viewer that displays your entire project.
When you zoom in, a frame appears in the Overview to highlight the
64 PCI Geomatics

Making Your Own Web Page
location that you are currently displaying in the applet. To include
the Overview in your Web page, add the Overview HTML code to
your HTML file. For example, the following HTML code displays
the Overview shown in MapViewerTemplate3.html:
Geomatica WebServer Suite Installation Guide 65

Chapter 6 - Publishing Your Maps on the WMS Servlet or a Web Page
66 PCI Geomatics

Configuring the WMS MapViewer Applet
Configuring the MapViewer Applet
To display your project in a Web page, you need the WMS servlet
and the WMS client that consists of the applet and browser. The
WMS servlet is explained in “Configuring the Servlet for the Web
Mapping Service (WMS)” on page 39. The HTML file is explained
in “Publishing Your Maps on the WMS Servlet or a Web Page” on
page 49. The MapViewer Applet is inserted into the HTML file
containing the data required for browsers to display your Web page.
For example, the following is the MapViewer Applet declared in the
MapViewerTemplate3.html:
The “Config” parameter specifies the file name of the configuration
file (XML file) that the MapViewer Applet requires. The default
C HAPTER
7
configuration file for MapViewerTemplate1.html is AllProject.xml
and for the rest of the MapViewerTemplates it is layers.xml.
Creating the Applet’s Configuration File
The configuration file provides the MapViewer Applet with
instructions to connect to the WMS servlet, the name of the server
where the project data is located, the name of the layers that it can
display, and other information concerning how to display the data.
The MapViewer Applet’s configuration file can be as simple as the
AllProject.xml or the layers.xml files (provided in \webapps\wms
in the folder where you installed Tomcat ) or as complex as you want
to make it.
The MapViewer.dtd is a DTD that contains the formal definitions of
all of the data elements the MapViewer Applet’s configuration file.
By consulting the MapViewer.dtd, you can validate any
modifications that you make to the file. You can create a
configuration file for the MapViewer Applet by using one of these
methods:
• Modify the AllProject.xml or layers.xml files.
67

Chapter 7 - Configuring the WMS MapViewer Applet
• Create your own by using a text editor or an XML editor (or any
programming language, such as Java, Javascript, Python, or C/C++).
Using the AllProject.xml file as an example is the simplest way to
describe the syntax of the MapViewer Applet’s configuration file.
AllProject.xml is an XML file generated by Geomatica Focus that
merges all the project’s map layers into one layer.
The first line in the example indicates that the document is based on
XML version 1.0 and the encoding is UTF-8:
The AllProject.xml file uses a DTD so the second line is a
DOCTYPE definition. The DOCTYPE definition declares what type
of document the XML file is and which DTD it follows. In the
AllProject.xml example, the DOCTYPE declares that the file is a
“mapviewer-config” document and it follows the DTD file
“MapViewer.dtd”:
The DOCTYPE definition must appear after the XML declaration,
but before the first element in the configuration file. The next line
following the DOCTYPE definition in the AllProject.xml example
states the root element (see “Defining the “Mapviewer-Config” Root
Element” on page 69):
The next line in the example provides information about the
connection and protocol used to get the map information from a Web
mapping server (WMS) compliant with the Open Geospatial®
Consortium (OGC) using the protocol WMS version 1.0.0 or 1.1.1.
You can expand this element using several attributes explained in
“Using the WMSProvider Element” on page 70.
The next lines shown in the example state the “map” element with a
“maplayer” identified by a unique “layerid”. The “map” element
does not include a layer ID, because it is a container for map layers
and it cannot be requested from the WMS (see “Using the “Map”
Element” on page 71). The layer ID corresponds to the name of the
layer in the Capabilities file, which is “AllProject” in the example:
The “” is also equivalent to:
When this element is parsed, the MapViewer Applet verifies if the
layer with the indicated layer ID is available on the server (see
“Using the “Maplayer” Child Element” on page 71). If the layer is
found, it is initialized with information coming from the Capabilities
file, such as title and description. By using additional attributes and
children elements, you can control the map information retrieved
from the Capabilities file to customize the map layer information or
and support for different languages.
Adding Several Map Layers
You can also retrieve more than one map layer with the
configuration file. By adding “maplayer” elements within the “map”
68 PCI Geomatics

Creating the Applet’s Configuration File
element, you can display more than one map layer. The following
example includes two map layers:
You can retrieve the names of the layers in your project by opening
the project in Geomatica or by generating the Capabilities file (see
“Generating a Capabilities File” on page 73).
Defining the “Mapviewer-Config” Root Element
The “mapviewer-config” element is the root of the MapViewer
applet’s configuration file. The MapViewer applet is only able to
connect to an OGC Web Mapping Service using the WMS protocol
version 1.0.0 or 1.1.1 (see www.opengeospatial.org for more
details). The mapviewer-config element is defined in the DTD as
follows:
Using the Viewport Element
The “viewport” element determines the extent of the initial view.
When the viewer starts, it displays an overview of the map by
default. You can modify the bounding box and the Spatial Reference
System (SRS) as required. To configure the initial bounding box,
add the “viewport” element immediately after the root element. By
default the “viewport” element is EPSG:NONE. The “viewport”
element is defined in the DTD as follows:
Using the “Extent” Child Element
The “extent” element is a child of the “viewport” element. It
indicates the values to specify the bounds of a map layer. The
“extent” child element contains the “minx”, “miny”, “maxx”, and
“maxy” attributes. The “extent” child element is defined in the DTD
as follows:
Geomatica WebServer Suite Installation Guide 69

Chapter 7 - Configuring the WMS MapViewer Applet

Creating the Applet’s Configuration File
type: The “type” attribute identifies where the map information is
coming from. Geomatica’s Web Mapping Service currently only
supports the OGC Web mapping Server, which is why the value of
the attributes is fixed to "OGC-WMT".
version: The “version” attribute indicates the version of the WMS
protocol used by the WMS. Currently, Geomatica Web Mapping
Service supports versions 1.0.0 and 1.1.1.
Using the “Map” Element
The “map” element is a container for one to several map layers. The
“map” element includes five child elements (title, description,
metadata, supported-bbox, and maplayer) and the visible attribute.
The “map” element is defined in the DTD as follows:
The “maplayer” child element also contains the title, description,
metadata, and supported-box child elements and the visible attribute.
Therefore, refer to “Using the “Maplayer” Child Element” on
page 71 for the description of the child elements and the visible
attribute.
Using the “Maplayer” Child Element
The “maplayer” element is a child of the “map” element. It
represents a map layer that is identified by its layer ID in the
Capabilities file. The “maplayer” element contains the title,
description, metadata, supported-styles, and supported-bbox child
elements and the layerid, default-style, visible, and queryable
attributes. The “maplayer” child element is defined in the DTD as
follows (see “Setting the “Maplayer” Attributes” on page 73 for the
attributes):
Replacing the Title
The “title” element is an optional child element of both the “map”
element and “maplayer” child element. Although the Capabilities
file contains a title for the map layer, you can use the “title” child
element to replace the published title with a more practical label. If
it is not used, the viewer uses the title from the Capabilities file. The
“title” child element is defined in the DTD as follows:
Replacing the Description
The “description” element is an optional child element of both the
“map” element and “maplayer” child element. Although the
Capabilities file contains a description for the map layer, you can use
the “description” child element to replace the published description
with your own version. If it is not used, the viewer uses the
description provided in the Capabilities file. The “description” child
element is defined in the DTD as follows:
Replacing the Metadata
The “metadata” element is an optional child element of both the
“map” element and “maplayer” child element. The Capabilities file
may contain metadata for the map layer, however, you may want to
include more information or replace the published information. The
“metadata” child element is defined in the DTD as follows:
By using the “metadata” child element, you can add metadata
information for each map layer as key or value string pairs. For
example:
Geomatica WebServer Suite Installation Guide 71

Chapter 7 - Configuring the WMS MapViewer Applet
Map of Lake Superior
The largest of the Great Lakes located between the
north-central United States and southern Ontario, Canada
You can access the metadata from the API of the map layer provided
with the applet (see “API Reference for the WMS” on page 77).
Determining the Supported-Styles
The “supported-styles” element is a child element of the “maplayer”
child element only. The “supported-styles” child element is defined
in the DTD as follows:
By default the layer supports all the styles provided by the
Capabilities file. You can restrict the list of styles supported by a
layer to those specified in the “supported-styles” child element.
The “supported-styles” child element can include a list of styles as
children using the “style” child element. The “style” child element
provides the name of the style you want to support. Each name in the
list must be published in the Capabilities file.
Changing the Supported-Bbox
The “supported-bbox” child element is an optional child element of
both the “map” element and “maplayer” child element. By default
the map layer supports all the bounding boxes published by the
Capabilities file. You can restrict the list and extent of the bounding
boxes by using the “supported-bbox” child element. The “supportedbbox”
child element is defined in the DTD as follows:
The “supported-bbox” child element overrides any bounding boxes
provided by the Capabilities file. For example, the following shows
a layer that supports only two SRS with limited bounding boxes:
srs="EPSG:26711"
minx="411814.576577"
miny="3724207.746876"
maxx="433946.398012"
maxy="3732255.880432"/>
The “maplayer” child element and its descendants can inherit
bounding boxes from the “map” element. If the bounding box from
the “maplayer” child element or its descendants conflicts with the
bounding box using the same SRS inherited from the “map” element,
the viewer disregards the inherited bounding box. However, all the
supported bounding boxes must be of an SRS supported by the
Capabilities file.
72 PCI Geomatics
Note
The extent must be within the extent published in the Capabilities file.

Generating a Capabilities File
Setting the “Maplayer” Attributes
The attributes for the “maplayer” child element are defined in the
DTD as follows:
layerid: The “layerid” attribute identifies the map layer published in
the Capabilities file. If the WMS does not contain the map layer, the
viewer will disregard the map layer and the request will not be sent
to the WMS. The “map” element does not include a layer ID,
because it is a container for map layers and it cannot be requested
from the WMS.
default style: The “default-style” attribute is an optional attribute of
the “maplayer” child element. The Default Style must be one of
styles in the Capabilities file supported by the map layer. For
example:
When a layer does not support styles, such as a layer containing an
image, the request sent to the WMS uses the name "default" for the
style ID. If the “default-style” attribute is disregarded, the viewer
uses the first style published in the Capabilities file as the default.
visible: The “visible” attribute is an optional attribute of the “map”
element and the “maplayer” child element. It indicates whether the
map or map layer is visible or not when the viewer is started. The
attribute contains only two values, “true” or “false”. By default the
value is “true”. The value “true” means that the map or map layer is
visible. The value “false” means that the map or map layer is not
visible.
The “visible” attribute of the “map” element has priority over the
“visible” attribute of the “maplayer” child element or its
descendants. If the “map” element is visible (“true”), you can set the
attribute to “true” or “false” for the map layers. If the “map” element
is not visible (“false”), the map layer cannot be visible, regardless of
how its attribute is set.
For example, the “visible” attribute of the following map layers is
“true”, but the “visible” attribute of the “map” element is “false”.
Therefore, the map layers are not visible.

Chapter 7 - Configuring the WMS MapViewer Applet
Replace [localhost] by the name of the server where the project is
located.
2. Identify the exact layer names in the XML file. For example, the
layer “Lakes” in the Capabilities file generated from the demo
project Newport.gpr.
Lakes
Lakes
Default
Default
none
Viewing the MapViewer DTD
The following is the MapViewer.dtd is its original form:
74 PCI Geomatics

Viewing the MapViewer DTD

Chapter 7 - Configuring the WMS MapViewer Applet
only a clip of the full bounding box must be used or only
a subset of SRS is used. If the tag is not used the list
of bounding boxes published by the WMS capabilities is
used.
-->
76 PCI Geomatics

API Reference for the WMS
C HAPTER
8
This chapter contains the API of the MapViewer applet, the Layer object, and the Layer Information Requests using the style used by Java. This
chapter is intended for advanced or expert users with comprehensive knowledge of HTML, Java, and JavaScript. You can use the application
programming interface (API) reference to expand Geomatica WebServer Suite functionality. You can use the information provided in the API to
control the behaviour of the MapViewer applet and to enhance the content of your Web page.
Class MapViewerApplet
This applet is a map viewer for OGC Web Mapping Server. It runs with Java 1.4 JVM and provides tool to manipulate the view and map drawing.
Field Summary
Fields inherited from class java.awt.Component
BOTTOM_ALIGNMENT, CENTER_ALIGNMENT, LEFT_ALIGNMENT, RIGHT_ALIGNMENT, TOP_ALIGNMENT
Fields inherited from interface java.awt.image.ImageObserver
ABORT, ALLBITS, ERROR, FRAMEBITS, HEIGHT, PROPERTIES, SOMEBITS, WIDTH
Constructor Summary
77

Chapter 8 - API Reference for the WMS
MapViewerApplet()
Method Summary
void
void
void
Extent
LayerInfoFilterConfig
LinearRing
LineString
Point2D
Rectangle
SimplePolygon
void
void
Extent
Extent
Layer
Layer
areaMeasurementTool()
Activate a area measurement tool.
centerTool()
Activate a Recenter tool.
circleMeasurementTool()
Activate a area measurement tool.
createExtent(double ulx, double uly, double width, double height)
Create an instance of Extent
createLayerInfoFilterConfig()
Create a new LayerInfoFilterConfig allowing property and spatial filtering on the layers and customized presentation using XSLT.
createLinearRing(java.lang.String coordinates)
Create a LinearRing geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
createLineString(java.lang.String coordinates)
Create a LineString geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
createPoint2D(java.lang.String coordinate)
Create a Point2D geometry from a coordinate string in the following format: 3,2
createRectangle(java.lang.String coordinates)
Create a Rectangle geometry from a list of two coordinates along a diagonal in the following format: 3,2 3,4.
createSimplePolygon(java.lang.String coordinates)
Create a SimplePolygon geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
cursorTool()
Activate a area measurement tool.
flush()
Flush the cache of the drawing view.
getExtent()
Get the current extent of the DrawingView.
getFullExtent()
Get the full extent of the view (overview).
getLayer(java.lang.String layerID)
Get the Layer identified by the layerID.
getRoot()
Returns the root of the map composition displayed in the applet.
78 PCI Geomatics

double
GeometryIF
void
void
void
void
void
void
void
void
void
void
void
void
void
void
Point2d
void
Class MapViewerApplet
getScale()
Get the current scale of the view (scale is number of points of the device per user space unit.
getSelectedGeometry()
Get the current selected GeometryIF in the view.This Geometry is created typically by a Query tool such as QueryPolygonTool,
QueryPointTool or QueryLineStringTool.
init()
Opens the window and initializes its contents.
lengthMeasurementTool()
Activate a length measurement tool.
loadMapViewConfiguration(java.lang.String urladdress)
Load a map configuration file from the URL address.
overview()
Set the extent of the view to full extent (overview of the Drawing) by using the best fit for the drawing extent in the view.
pan()
This method activates the pan tool.
panAndZoom()
Activate a pan and zoom tool.
refresh()
Refresh the screen.
setCenterAt(double X, double Y)
Center the view at the specified user space point.
setExtent(double x, double y, double width, double height)
Set the extent for the view.
setQueryLineTool()
Set the query line string tool.
setQueryPointTool(java.lang.String windowName)
This method allows you to select a point with the mouse.
setQueryPointTool(java.lang.String windowName, int featureCountNum)
This method allows you to select a point with the mouse.
setQueryPolygonTool()
Set the query polygon tool.
start()
This method is called after the applet is loaded.
toDevicePoint(double x, double y)
Converts a point in user space coordinate to device space coordinate in sub-pixel precision.
toolDone()
Informs the editor that a tool has finished its interaction.
Geomatica WebServer Suite Installation Guide 79

Chapter 8 - API Reference for the WMS
Point2d
void
void
void
void
toUserPoint(int xdevice, int ydevice)
Converts a point in device space coordinate to user space coordinate in double precision.
zoom()
The zoom is performed by dragging the mouse up and down.
zoom(double scale)
Zoom at the specified scale.
zoomFactor(double factor)
This method activates a tool to zoom by a fixed factor set in the view.
zoomWindow()
Activates a Zoom Window tool: used to magnify the portiom of the map contained within the selected area.
Methods inherited from class java.applet.Applet
destroy, getAccessibleContext, getAppletContext, getAppletInfo, getAudioClip, getAudioClip, getCodeBase, getDocumentBase,
getImage, getImage, getLocale, getParameter, getParameterInfo, isActive, newAudioClip, play, play, resize, resize,
setStub, showStatus, stop
Methods inherited from class java.awt.Panel
addNotify
Methods inherited from class java.awt.Container
add, add, add, add, add, addContainerListener, addImpl, addPropertyChangeListener, addPropertyChangeListener,
applyComponentOrientation, areFocusTraversalKeysSet, countComponents, deliverEvent, doLayout, findComponentAt,
findComponentAt, getAlignmentX, getAlignmentY, getComponent, getComponentAt, getComponentAt, getComponentCount,
getComponents, getContainerListeners, getFocusTraversalKeys, getFocusTraversalPolicy, getInsets, getLayout, getListeners,
getMaximumSize, getMinimumSize, getPreferredSize, insets, invalidate, isAncestorOf, isFocusCycleRoot, isFocusCycleRoot,
isFocusTraversalPolicySet, layout, list, list, locate, minimumSize, paint, paintComponents, paramString, preferredSize,
print, printComponents, processContainerEvent, processEvent, remove, remove, removeAll, removeContainerListener,
removeNotify, setFocusCycleRoot, setFocusTraversalKeys, setFocusTraversalPolicy, setFont, setLayout,
transferFocusBackward, transferFocusDownCycle, update, validate, validateTree
80 PCI Geomatics

Methods inherited from class java.awt.Component
MapViewerApplet
public MapViewerApplet()
Class MapViewerApplet
action, add, addComponentListener, addFocusListener, addHierarchyBoundsListener, addHierarchyListener,
addInputMethodListener, addKeyListener, addMouseListener, addMouseMotionListener, addMouseWheelListener, bounds,
checkImage, checkImage, coalesceEvents, contains, contains, createImage, createImage, createVolatileImage,
createVolatileImage, disable, disableEvents, dispatchEvent, enable, enable, enableEvents, enableInputMethods,
firePropertyChange, firePropertyChange, firePropertyChange, getBackground, getBounds, getBounds, getColorModel,
getComponentListeners, getComponentOrientation, getCursor, getDropTarget, getFocusCycleRootAncestor, getFocusListeners,
getFocusTraversalKeysEnabled, getFont, getFontMetrics, getForeground, getGraphics, getGraphicsConfiguration, getHeight,
getHierarchyBoundsListeners, getHierarchyListeners, getIgnoreRepaint, getInputContext, getInputMethodListeners,
getInputMethodRequests, getKeyListeners, getLocation, getLocation, getLocationOnScreen, getMouseListeners,
getMouseMotionListeners, getMouseWheelListeners, getName, getParent, getPeer, getPropertyChangeListeners,
getPropertyChangeListeners, getSize, getSize, getToolkit, getTreeLock, getWidth, getX, getY, gotFocus, handleEvent,
hasFocus, hide, imageUpdate, inside, isBackgroundSet, isCursorSet, isDisplayable, isDoubleBuffered, isEnabled,
isFocusable, isFocusOwner, isFocusTraversable, isFontSet, isForegroundSet, isLightweight, isOpaque, isShowing, isValid,
isVisible, keyDown, keyUp, list, list, list, location, lostFocus, mouseDown, mouseDrag, mouseEnter, mouseExit, mouseMove,
mouseUp, move, nextFocus, paintAll, postEvent, prepareImage, prepareImage, printAll, processComponentEvent,
processFocusEvent, processHierarchyBoundsEvent, processHierarchyEvent, processInputMethodEvent, processKeyEvent,
processMouseEvent, processMouseMotionEvent, processMouseWheelEvent, remove, removeComponentListener, removeFocusListener,
removeHierarchyBoundsListener, removeHierarchyListener, removeInputMethodListener, removeKeyListener, removeMouseListener,
removeMouseMotionListener, removeMouseWheelListener, removePropertyChangeListener, removePropertyChangeListener, repaint,
repaint, repaint, repaint, requestFocus, requestFocus, requestFocusInWindow, requestFocusInWindow, reshape, setBackground,
setBounds, setBounds, setComponentOrientation, setCursor, setDropTarget, setEnabled, setFocusable,
setFocusTraversalKeysEnabled, setForeground, setIgnoreRepaint, setLocale, setLocation, setLocation, setName, setSize,
setSize, setVisible, show, show, size, toString, transferFocus, transferFocusUpCycle
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Constructor Detail
Geomatica WebServer Suite Installation Guide 81

Chapter 8 - API Reference for the WMS
Method Detail
init
public void init()
Opens the window and initializes its contents.
Overrides:
init in class java.applet.Applet
start
public void start()
This method is called after the applet is loaded.
Overrides:
start in class java.applet.Applet
loadMapViewConfiguration
public void loadMapViewConfiguration(java.lang.String urladdress)
Load a map configuration file from the URL address.
Parameters:
urladdress - URL address of the config file
getRoot
public Layer getRoot()
Returns the root of the map composition displayed in the applet. The layer can be a simple Layer without any children.
Returns:
the root of the map composition that is displayed in the applet.
getLayer
public Layer getLayer(java.lang.String layerID)
Get the Layer identified by the layerID.
Parameters:
layerID - identifier of the GeoMap
Returns:
Layer instance corresponding to the layerID,null if not found
getExtent
public Extent getExtent()
Get the current extent of the DrawingView.
82 PCI Geomatics

Returns:
Rectangle representing the Extent of the DrawingView.
getFullExtent
public Extent getFullExtent()
Get the full extent of the view (overview).
Returns:
Extent corresponding to the full extent
Class MapViewerApplet
setExtent
public void setExtent(double x,
double y,
double width,
double height)
Set the extent for the view. This method computes the best fit of the given extent in the current DrawingView. A uniform scale is computed in both
directions. Extent is expressed in map space.
Parameters:
x - upper left x coordinate in map space
y - upper left x coordinate in map space
width - width of the extent in map space
height - height of the extent in map space
getScale
public double getScale()
Get the current scale of the view (scale is number of points of the device per user space unit.
Returns:
current scale of the view
pan
public void pan()
This method activates the pan tool. The user needs to click the left button and drag the mouse to pan the image.
zoomFactor
public void zoomFactor(double factor)
This method activates a tool to zoom by a fixed factor set in the view. The zoom is done by keeping the center of the view fixed.
zoomWindow
public void zoomWindow()
Activates a Zoom Window tool: used to magnify the portiom of the map contained within the selected area. Area is selected by dragging the left mouse
button to create a window.
Geomatica WebServer Suite Installation Guide 83

Chapter 8 - API Reference for the WMS
centerTool
public void centerTool()
Activate a Recenter tool. The user needs to click the left button. The view is centered at the position clicked.
cursorTool
public void cursorTool()
Activate a area measurement tool.
lengthMeasurementTool
public void lengthMeasurementTool()
Activate a length measurement tool.
areaMeasurementTool
public void areaMeasurementTool()
Activate a area measurement tool.
circleMeasurementTool
public void circleMeasurementTool()
Activate a area measurement tool.
setCenterAt
public void setCenterAt(double X,
double Y)
Center the view at the specified user space point.
Parameters:
X - user space X coordinate of the center
Y - user space Y coordinate of the center
overview
public void overview()
Set the extent of the view to full extent (overview of the Drawing) by using the best fit for the drawing extent in the view.
zoom
public void zoom()
The zoom is performed by dragging the mouse up and down. Move up zoom out, move down zoom in.
zoom
public void zoom(double scale)
Zoom at the specified scale. The center point of the view remains fixed. The scale is expressed as number of device unit per user unit.
84 PCI Geomatics

Parameters:
scale - scale to use to zoom
Class MapViewerApplet
panAndZoom
public void panAndZoom()
Activate a pan and zoom tool. To zoom click the right mouse button and drag up and down. Moving up zooms out, moving down zooms in. To pan click
and drag the left mouse button.
toolDone
public void toolDone()
Informs the editor that a tool has finished its interaction. This method can be used to switch back to the default tool.
flush
public void flush()
Flush the cache of the drawing view.
refresh
public void refresh()
Refresh the screen.
setQueryPointTool
public void setQueryPointTool(java.lang.String windowName,
int featureCountNum)
This method allows you to select a point with the mouse.
setQueryPointTool
public void setQueryPointTool(java.lang.String windowName)
This method allows you to select a point with the mouse.
setQueryPolygonTool
public void setQueryPolygonTool()
Set the query polygon tool.
setQueryLineTool
public void setQueryLineTool()
Set the query line string tool.
createLayerInfoFilterConfig
public LayerInfoFilterConfig createLayerInfoFilterConfig()
Create a new LayerInfoFilterConfig allowing property and spatial filtering on the layers and customized presentation using XSLT.
Geomatica WebServer Suite Installation Guide 85

Chapter 8 - API Reference for the WMS
Returns:
Instance of LayerInfoFilterConfig.
createSimplePolygon
public SimplePolygon createSimplePolygon(java.lang.String coordinates)
Create a SimplePolygon geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
Parameters:
coordinates - list of coordinates
Returns:
SimplePolygon geometry, null if coordinates invalid.
createLineString
public LineString createLineString(java.lang.String coordinates)
Create a LineString geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
Parameters:
coordinates - list of coordinates
Returns:
LineString geometry, null if coordinates invalid.
createRectangle
public Rectangle createRectangle(java.lang.String coordinates)
Create a Rectangle geometry from a list of two coordinates along a diagonal in the following format: 3,2 3,4.
Parameters:
coordinates - Two opposite points along a diagonal
Returns:
com.pcigeomatics.spatial.geometry.Rectangle geometry, null if coordinates invalid.
createLinearRing
public LinearRing createLinearRing(java.lang.String coordinates)
Create a LinearRing geometry from a list of coordinates in the following format: 3,2 3,4 4,5.
Parameters:
coordinates - list of coordinates
Returns:
LinearRing geometry, null if coordinates invalid.
createPoint2D
public Point2D createPoint2D(java.lang.String coordinate)
Create a Point2D geometry from a coordinate string in the following format: 3,2
86 PCI Geomatics

Parameters:
coordinate - of the point
Returns:
Point2D geometry, null if coordinate invalid.
Class MapViewerApplet
getSelectedGeometry
public GeometryIF getSelectedGeometry()
Get the current selected GeometryIF in the view.This Geometry is created typically by a Query tool such as QueryPolygonTool, QueryPointTool or
QueryLineStringTool. It could also be the result if a selection in a layer (not supported in this version) The current version returns only atomic Geometry,
not collection
Returns:
Geometry geometry currently selected, null if none is found.
createExtent
public Extent createExtent(double ulx,
double uly,
double width,
double height)
Create an instance of Extent
Parameters:
ulx - upper left x coordinate
uly - upper left x coordinate
width - width of the extent
height - height of the extent
toDevicePoint
public Point2d toDevicePoint(double x,
double y)
Converts a point in user space coordinate to device space coordinate in sub-pixel precision.
Parameters:
x - X coordinate of point in user space
y - Y coordinate of point in user space
Returns:
Point2d in device space coordinate (in sub pixel)
toUserPoint
public Point2d toUserPoint(int xdevice,
int ydevice)
Converts a point in device space coordinate to user space coordinate in double precision.
Geomatica WebServer Suite Installation Guide 87

Chapter 8 - API Reference for the WMS
Returns:
Point2d in device space coordinate (in sub pixel)
Class Layer
public class Layer
extends java.lang.Object
A layer is a visual representation of geodata commonly known as a "map". It is not the data itself. A layer is generally rendered in a pictorial format
such as PNG, GIF or JPEG, or occasionally as vector-based graphical elements in Scalable Vector Graphics (SVG).
This class provides methods to provide layer attributes information and to modify display properties.
Constructor Summary
Layer(GeoMap geomap)
Constructor
Method Summary
void
clearScales()
Clears the existing scale limitations, allowing the layer to be drawn at all scales.
boolean
getAllowsChildren()
Returns true if this Layer is allowed to have children.
Extent
getExtent()
Get the current Extent of the Layer.
Extent
getLatLongExtent()
Get the LongLat Extent of the Layer.
java.lang.String getLayerID()
Get the identifier of the Layer.
java.lang.String getLayerLeafIDs()
A breath first traversal starts looking at the root node, then goes to its children, in ascending index order.
java.lang.String getLayerLeafNames()
A breath first traversal starts looking at the root node, then goes to its children, in ascending index order.
double
getMaxScale()
Gets the maximum scale at which this layer is displayed.
88 PCI Geomatics

getMetadata(java.lang.String name)
java.lang.Object
Returns the value of a metadata.
getMetadataNames(int index)
java.lang.String
Returns the metadata name represented by a specific index.
getMetadataNamesCount()
int
Returns the number of metadata names that are declared in a Layer.
getMinScale()
double
Gets the minimum scale at which this layer is displayed.
java.lang.String getName()
Get the name of the geodataset (title).
com.pcigeomatics
.map.geodataset.
geomap.Layer
com.pcigeomatics
.map.geodataset.
geomap.Layer
getParent()
Gets the parent container of this layer.
getRoot()
Returns the root of the composition that contains the Layer.
java.lang.String getSRS()
Gets the spatial reference system used by the layer.
Style
getStyle()
Gets the current Style.
Style
getStyle(java.lang.String styleID)
Gets the Style object from its StyleID.
int
getSubLayerCount()
Returns the current number of sub layers in the Layer.
com.pcigeomatics
.map.geodataset.
geomap.Layer
java.lang.String
int
Style
int
boolean
getSubLayers(int index)
Returns the Layer represented by a specific index.
getSupportedSRS(int index)
Returns the SRS String represented by a specific index.
getSupportedSRSCount()
Returns the number of SRS supported that are declared in a Layer
getSupportedStyles(int index)
Returns the Style represented by a specific index.
getSupportedStylesCount()
Returns the number of Styles supported in a layer.
isLeaf()
Returns true if this Layer has no children.
Class Layer
Geomatica WebServer Suite Installation Guide 89

Chapter 8 - API Reference for the WMS
boolean
boolean
boolean
boolean
boolean
void
void
void
void
void
void
void
void
Layer
public Layer(GeoMap geomap)
Constructor
isQueryable()
Indicates if the layer is queryable.
isRoot()
Returns true if this Layer is the root of the composition.
isSelected()
Indicates if the layer is selected.
isVisible()
Indicates if the layer is visible or if it is hidden.
move(int startIndex, int endIndex, int toIndex)
Moves one or more sublayers starting at startIndex to endIndexin the model to the toIndex.
setMaxScale(double maxScale)
Sets the maximum scale at which this layer is displayed.
setMinScale(double minScale)
Sets the minimum scale at which this layer is displayed.
setSelected(java.lang.String selected)
Selects the layer by using "true" or "false" strings.
setSelectedByInt(int visible)
Selects the layer by using integer 0 or 1.
setSRS(java.lang.String srsName)
Sets the spatial reference system used by the Layer.
setStyle(java.lang.String styleID)
Sets the current Style.
setVisible(java.lang.String visible)
Sets the layer visibility by using "true" or "false" strings.
setVisibleByInt(int visible)
Sets the layer visibility by using integer 0 or 1.
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Constructor Detail
90 PCI Geomatics

Method Detail
getLayerID
public java.lang.String getLayerID()
Get the identifier of the Layer. If not set, it returns null, The layer cannot be requested.
Returns:
Identifier of the Layer.null if not set.
getName
public java.lang.String getName()
Get the name of the geodataset (title).
Returns:
name of the geodataset
getMetadataNames
public java.lang.String getMetadataNames(int index)
Returns the metadata name represented by a specific index.
Parameters:
index - of the metadata name requested
Returns:
metadata name String at a specific index
getMetadataNamesCount
public int getMetadataNamesCount()
Returns the number of metadata names that are declared in a Layer.
Returns:
int that indicate the number of metadata names declared
getMetadata
public java.lang.Object getMetadata(java.lang.String name)
Returns the value of a metadata. If the metadata name is not recognized, null is returned
Parameters:
name - the name of the metadata, as a String.
Returns:
the value of the metadata, as an Object or null if not defined
Class Layer
Geomatica WebServer Suite Installation Guide 91

Chapter 8 - API Reference for the WMS
getLatLongExtent
public Extent getLatLongExtent()
Get the LongLat Extent of the Layer. If not set for this layer, the parent one is used. If not set in ancestors, returns null
Returns:
Extent LongLat Extent
getExtent
public Extent getExtent()
Get the current Extent of the Layer. If not set for this layer, the closest ancestor's one is used. If not set in the ancestor, returns null
Returns:
Extent current Extent
getSRS
public java.lang.String getSRS()
Gets the spatial reference system used by the layer. If not set for this layer, the closest ancestor's one is used. If not set in ancestor's, returns null.
Returns:
spatial reference system used by the geospatial dataset
setSRS
public void setSRS(java.lang.String srsName)
Sets the spatial reference system used by the Layer. The SRS is set only if it is supported by the Layer.
getSupportedSRS
public java.lang.String getSupportedSRS(int index)
Returns the SRS String represented by a specific index.
Parameters:
index - of SRS
Returns:
String that represents the SRS value at a specific index
getSupportedSRSCount
public int getSupportedSRSCount()
Returns the number of SRS supported that are declared in a Layer
Returns:
int number of SRS supported in the Layer
getStyle
public Style getStyle()
Gets the current Style. If no style is available, it returns null. A default one needs to be used in the request.
92 PCI Geomatics

Returns:
current Style to use
setStyle
public void setStyle(java.lang.String styleID)
Sets the current Style.
getStyle
public Style getStyle(java.lang.String styleID)
Gets the Style object from its StyleID. If the style is not available, it returns null.
Parameters:
styleID - style identifier to use to retrieve the Style object
Returns:
Style object having the given StyleID, null if not found.
getSupportedStyles
public Style getSupportedStyles(int index)
Returns the Style represented by a specific index.
Parameters:
index -
Returns:
style supported for a specific index in this layer
getSupportedStylesCount
public int getSupportedStylesCount()
Returns the number of Styles supported in a layer.
Returns:
int the number of styles supported
isVisible
public boolean isVisible()
Indicates if the layer is visible or if it is hidden.
Returns:
true if the layer is visible, false if the layer is hidden.
setVisible
public void setVisible(java.lang.String visible)
Sets the layer visibility by using "true" or "false" strings. If the string is not valid, the method does nothing.
Class Layer
Geomatica WebServer Suite Installation Guide 93

Chapter 8 - API Reference for the WMS
setVisibleByInt
public void setVisibleByInt(int visible)
Sets the layer visibility by using integer 0 or 1. If the integer is not valid, the method does nothing.
Parameters:
visible - 1 if layer is visible, 0 otherwise not visible
getMaxScale
public double getMaxScale()
Gets the maximum scale at which this layer is displayed. If the current scale is greater than the maximum scale, the layer will not be displayed. If no
maximum scale has been set, the method returns NO_MAXSCALE. If not set, it is inherited from parent.
Returns:
the maximum scale this layer can be displayed
setMaxScale
public void setMaxScale(double maxScale)
Sets the maximum scale at which this layer is displayed. If the current scale is greater than the maximum scale, the layer will not be displayed. This is
a bound property, so report of any change is done to all registered listeners.
Parameters:
maxScale - the maximum scale this layer can be displayed
getMinScale
public double getMinScale()
Gets the minimum scale at which this layer is displayed. If the current scale is less than the minimum scale, the layer will not be displayed. If not set, it
is inherited from parent.
Returns:
the minimum scale this layer can be displayed. If no minimum scale has been set, the method returns NO_MINSCALE;
setMinScale
public void setMinScale(double minScale)
Sets the minimum scale at which this layer is displayed. If the current scale is less than the minimum scale, the layer will not be displayed. This is a
bound property, so report of any change is done to all registered listeners.
Parameters:
minScale - the minimum scale this layer can be displayed.
clearScales
public void clearScales()
Clears the existing scale limitations, allowing the layer to be drawn at all scales. This is a bound property, so report of any change is done to all registered
listeners.
94 PCI Geomatics

setSelected
public void setSelected(java.lang.String selected)
Selects the layer by using "true" or "false" strings. If the string is not valid, the method does nothing.
Parameters:
selected - "true" if layer is selected, "false" otherwise.
setSelectedByInt
public void setSelectedByInt(int visible)
Selects the layer by using integer 0 or 1. If the integer is not valid, the method does nothing.
Parameters:
visible - 1 if layer is selected, 0 otherwise not selected.
isSelected
public boolean isSelected()
Indicates if the layer is selected.
Returns:
true if the Geomap is selected, false otherwise.
isQueryable
public boolean isQueryable()
Indicates if the layer is queryable.
Returns:
true if query can be done on the map, false otherwise
getParent
public com.pcigeomatics.map.geodataset.geomap.Layer getParent()
Gets the parent container of this layer.
Returns:
Layer parent of this Layer, null if no parent.
getAllowsChildren
public boolean getAllowsChildren()
Returns true if this Layer is allowed to have children. A Layer that can contain children is a composition.
Returns:
true if this Layer allows children, else false.
Class Layer
isLeaf
public boolean isLeaf()
Returns true if this Layer has no children. To distinguish between Layers that have no children and Layer that cannot have children, use this method in
Geomatica WebServer Suite Installation Guide 95

Chapter 8 - API Reference for the WMS
conjunction with getAllowsChildren.
Returns:
true if this layer has no children.
getSubLayerCount
public int getSubLayerCount()
Returns the current number of sub layers in the Layer. Note that a Layer composition is considered as one layer. Its sublayers are not counted individually.
Returns:
number of sub layers (siblings) in this Layer.
getSubLayers
public com.pcigeomatics.map.geodataset.geomap.Layer getSubLayers(int index)
Returns the Layer represented by a specific index.
Parameters:
index -
Returns:
Layer at a specific index
getLayerLeafNames
public java.lang.String getLayerLeafNames()
A breath first traversal starts looking at the root node, then goes to its children, in ascending index order. After each child has been looked at, the traversal
moves on to the children of the root's first child and so on. A breath=first traversal might be good to find the item near the top of the tree.
Returns:
String of layers of GeoMap objects using a breath-first traversal algorithm.
getLayerLeafIDs
public java.lang.String getLayerLeafIDs()
A breath first traversal starts looking at the root node, then goes to its children, in ascending index order. After each child has been looked at, the traversal
moves on to the children of the root's first child and so on. A breath=first traversal might be good to find the item near the top of the tree.
Returns:
String of layers of GeoMap objects using a breath-first traversal algorithm.
getRoot
public com.pcigeomatics.map.geodataset.geomap.Layer getRoot()
Returns the root of the composition that contains the Layer. The root is the ancestor with a null parent.
Returns:
the root of the composition that contains this Layer.
96 PCI Geomatics

Class LayerInfoFilterConfig
isRoot
public boolean isRoot()
Returns true if this Layer is the root of the composition. The root is the only Layer in the composition with a null parent; every composition has exactly
one root.
Returns:
true if this Layer is the root of its tree
move
public boolean move(int startIndex,
int endIndex,
int toIndex)
Moves one or more sublayers starting at startIndex to endIndexin the model to the toIndex.
Examples of moves:
1. move(1,3,5);
a|B|C|D|e|f|g|h|i|j|k - before
a|e|f|B|C|D|g|h|i|j|k - after
2. move(6,7,1);
a|b|c|d|e|f|G|H|i|j|k - before
a|G|H|b|c|d|e|f|i|j|k - after
Parameters:
startIndex - the starting sublayer index to be moved
endIndex - the ending sublayer index to be moved
toIndex - the destination of the sublayers to be moved
Returns:
true if move has been successfull false if any of the indices are out of range or if endIndex is less than startIndex or no children to move.
Class LayerInfoFilterConfig
public class LayerInfoFilterConfig
extends java.lang.Object
This class is used for configuring the layer information request sent by the applet. The object can be accessed through the applet method
createLayerInfoConfig().
Geomatica WebServer Suite Installation Guide 97

Chapter 8 - API Reference for the WMS
Constructor Summary
LayerInfoFilterConfig(GeoMap geomapCurrent, java.applet.Applet applet)
Constructor
Method Summary
void
createBBoxOp(GeometryIF geometry)
Create an BBox spatial operator
void
createCrossesOp(GeometryIF geometry)
Create an Crosses spatial operator
void
createIntersectOp(GeometryIF geometry)
Create an intersects spatial operator
Join
createJoin()
Create a Join instance
void
createNearestOp(GeometryIF geometry)
Create an Nearest spatial operator
void
createOverlapOp(GeometryIF geometry)
Create an Overlap spatial operator
void
createWithinDistanceOp(GeometryIF geometry, double distance)
Create an WithinDistance spatial operator
void
createWithinOp(GeometryIF geometry)
Create an Within spatial operator
void
displayLayerInfoResult()
Send the layer info query and display the result in the browser window identified by windowName.
int
getBeginRecord(java.lang.String layerID)
Get the beginning record number in the resulting request for the specified layer.
getFeatureIDs(java.lang.String layerID)
java.lang.String Get the list of feature identifier to return in the query for the specific layer identified by layerID.The list is encoded as a string
with a "|" delimiter.
java.lang.String getID()
Get the identifier of the layerInfoFilter.
Join
getJoin(java.lang.String layerID)
Get the join information for the specific layer identified by layerID.
java.lang.String getLayerInfoFilterURL()
Get the URL corresponding to the query based on HTTP Get
98 PCI Geomatics

int
int
Class LayerInfoFilterConfig
getMaxFeature()
Get the maximum number of features returned for all layers
getMaxFeatures(java.lang.String layerID)
Set the maximum of features returned in the response for the specific layer identified by layerId.If not set the value is -1.
int
getNumXSLTInfoParam()
Get the parameter number
java.lang.String getOutputFormat()
Get the output format name used to retrieve the result
getPropertyFilter(java.lang.String layerID)
java.lang.String
Get the property filter using the GDB syntax for the specific layer identified by layerID
getResponseFilter(java.lang.String layerID)
java.lang.String
Get the response filter, i.e the list of property names to returns in the query.
SpatialFilter
getSpatialFilter()
Get the spatial filter applied for all the layers
SpatialFilter
getSpatialFilter(java.lang.String layerID)
Get the spatial filter applied for the specific layer identified by layerID.
java.lang.String getXMLLayerInfoFilter()
Get the XML encoding of the layer info filter.
XSLTInfo
getXSLTInfo()
Get the XSLTInfo for the request used to transform the result set.
getXSLTInfoParam(java.lang.String key)
java.lang.String
Get the parameter for the xslt
boolean
hasEnvelope(java.lang.String layerID)
Indicates if the response should indicate the envelope for each returned features
boolean
hasFullEnvelope(java.lang.String layerID)
Indicates if the response indicates the full envelope for all returned features of the layer or not.
boolean
isDirectOutput()
Indicate if the output needs to be sent directly or accessed indirectly via a URL or file
void
setBeginRecord(java.lang.String layerID, java.lang.String beginIndex)
Set the beginning record number in the resulting request for the specified layer
void
setDirectOutput(boolean directOutput)
Indicatea if the output needs to be sent directly or accessed indirectly via a URL or file
void
setEnvelope(java.lang.String layerID, java.lang.String bEnvelope)
Set whether the response should indicate the envelope for each returned features or not.
void
setEnvelopeByInt(java.lang.String layerID, int bEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not.
Geomatica WebServer Suite Installation Guide 99

Chapter 8 - API Reference for the WMS
void
void
void
void
void
void
void
void
void
void
void
void
void
void
setFeatureIDs(java.lang.String layerID, java.lang.String ids)
Set the list of feature identifier to return in the query for the specific layer identified by layerID.The list is of identifiers is delimited
by the character '|'.
setFullEnvelope(java.lang.String layerID, java.lang.String bFullEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not.
setFullEnvelopeByInt(java.lang.String layerID, int bFullEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not.
setID(java.lang.String ID)
Set the identifier of the layerInfoFilter.
setJoin(java.lang.String layerID, Join join)
Set the join information for the specific layer identified by layerID.
setMaxFeature(java.lang.String layerID, java.lang.String maxFeature)
Set the maximum number of features returned for all layers
setMaxFeatures(java.lang.String layerID, java.lang.String maxFeatures)
Set the maximum of features returned in the response for the specific layer identified by layerId.
setOutputFormat(java.lang.String outputFormat)
Set the output format name used to retrieve the result
setPropertyFilter(java.lang.String layerID, java.lang.String propertyFilter)
Set the property filter using the GDB syntax for the specific layer identified by layerID
setResponseFilter(java.lang.String layerID, java.lang.String propertyNames)
Get the response filter, i.e the list of property names to returns in the query.
setSpatialFilter()
Set the spatial filter applied for all the layers
setSpatialFilter(java.lang.String layerID, SpatialFilter filter)
Set the spatial filter applied for the specific layer identified by layerID.
setXSLTInfo(java.lang.String path)
Set the XSLTInfo for the request used to transform the result set.
setXSLTInfoParam(java.lang.String key, java.lang.String value)
Set the parameter for the xslt
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
100 PCI Geomatics

Constructor Detail
LayerInfoFilterConfig
public LayerInfoFilterConfig(GeoMap geomapCurrent,
java.applet.Applet applet)
Constructor
Method Detail
createJoin
public Join createJoin()
Create a Join instance
Returns:
Join instance
setPropertyFilter
public void setPropertyFilter(java.lang.String layerID,
java.lang.String propertyFilter)
Set the property filter using the GDB syntax for the specific layer identified by layerID
Parameters:
layerID - identifier of the layer
propertyFilter - property filter using GDB syntax
getPropertyFilter
public java.lang.String getPropertyFilter(java.lang.String layerID)
Get the property filter using the GDB syntax for the specific layer identified by layerID
Parameters:
layerID - identifier of the layer
Returns:
property filter using GDB syntax
getResponseFilter
public java.lang.String getResponseFilter(java.lang.String layerID)
Get the response filter, i.e the list of property names to returns in the query. The list is encoded as a string with a "|" delimiter.
Parameters:
layerID - identifier of the layer
Class LayerInfoFilterConfig
Geomatica WebServer Suite Installation Guide 101

Chapter 8 - API Reference for the WMS
Returns:
list of property names encoded as a string with a "|" delimiter.
setResponseFilter
public void setResponseFilter(java.lang.String layerID,
java.lang.String propertyNames)
Get the response filter, i.e the list of property names to returns in the query.
Parameters:
layerID - identifier of the layer
Returns:
array of property names
setMaxFeatures
public void setMaxFeatures(java.lang.String layerID,
java.lang.String maxFeatures)
Set the maximum of features returned in the response for the specific layer identified by layerId.
Parameters:
layerID - identifier of the layer
maxFeatures - maximum number of features
getMaxFeatures
public int getMaxFeatures(java.lang.String layerID)
Set the maximum of features returned in the response for the specific layer identified by layerId.If not set the value is -1.
Parameters:
layerID - identifier of the layer
Returns:
maximum number of features
getBeginRecord
public int getBeginRecord(java.lang.String layerID)
Get the beginning record number in the resulting request for the specified layer. If not set the value is -1.
Parameters:
layerID - identifier of the layer
Returns:
beginning record number in the resulting request
102 PCI Geomatics

setBeginRecord
public void setBeginRecord(java.lang.String layerID,
java.lang.String beginIndex)
Set the beginning record number in the resulting request for the specified layer
Parameters:
layerID - identifier of the layer
beginIndex - beginning record number in the resulting request
Class LayerInfoFilterConfig
getFeatureIDs
public java.lang.String getFeatureIDs(java.lang.String layerID)
Get the list of feature identifier to return in the query for the specific layer identified by layerID.The list is encoded as a string with a "|" delimiter.
Parameters:
layerID - identifier of the layer
Returns:
list of feature identifiers encoded as a string with a "|" delimiter.
setFeatureIDs
public void setFeatureIDs(java.lang.String layerID,
java.lang.String ids)
Set the list of feature identifier to return in the query for the specific layer identified by layerID.The list is of identifiers is delimited by the character
'|'. Example "1|3|4|34".
Parameters:
layerID - identifier of the layer
createIntersectOp
public void createIntersectOp(GeometryIF geometry)
Create an intersects spatial operator
Parameters:
geometry - Geometry used by the operator. Only SimplePolygon is supported.
Returns:
Instance of IntersectOp. null if geometry is is not supported.
createWithinDistanceOp
public void createWithinDistanceOp(GeometryIF geometry,
double distance)
Create an WithinDistance spatial operator
Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Geomatica WebServer Suite Installation Guide 103

Chapter 8 - API Reference for the WMS
Returns:
Instance of WithinDistanceOp. null if geometry is is not supported.
createNearestOp
public void createNearestOp(GeometryIF geometry)
Create an Nearest spatial operator
Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Returns:
Instance of NearestOp. null if geometry is is not supported.
createCrossesOp
public void createCrossesOp(GeometryIF geometry)
Create an Crosses spatial operator
Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Returns:
Instance of CrossesOp. null if geometry is is not supported.
createOverlapOp
public void createOverlapOp(GeometryIF geometry)
Create an Overlap spatial operator
Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Returns:
Instance of OverlapOp. null if geometry is is not supported.
createBBoxOp
public void createBBoxOp(GeometryIF geometry)
Create an BBox spatial operator
Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Returns:
Instance of BBoxOp. null if geometry is is not supported.
createWithinOp
public void createWithinOp(GeometryIF geometry)
Create an Within spatial operator
104 PCI Geomatics

Parameters:
geometry - Geometry used by the operator. Only Point2D is supported.
Returns:
Instance of WithinOp. null if geometry is is not supported.
getSpatialFilter
public SpatialFilter getSpatialFilter(java.lang.String layerID)
Get the spatial filter applied for the specific layer identified by layerID.
Parameters:
layerID - identifier of the layer
Returns:
SpatialFilter spatial filter applied to this layer
setSpatialFilter
public void setSpatialFilter(java.lang.String layerID,
SpatialFilter filter)
Set the spatial filter applied for the specific layer identified by layerID.
Parameters:
layerID - identifier of the layer
filter - SpatialFilter spatial filter applied to this layer
getSpatialFilter
public SpatialFilter getSpatialFilter()
Get the spatial filter applied for all the layers
Returns:
SpatialFilterIF instance
setSpatialFilter
public void setSpatialFilter()
Set the spatial filter applied for all the layers
getJoin
public Join getJoin(java.lang.String layerID)
Get the join information for the specific layer identified by layerID.
Parameters:
layerID - identifier of the layer
Returns:
Instance of Join
Class LayerInfoFilterConfig
Geomatica WebServer Suite Installation Guide 105

Chapter 8 - API Reference for the WMS
setJoin
public void setJoin(java.lang.String layerID,
Join join)
Set the join information for the specific layer identified by layerID.
Parameters:
layerID - identifier of the layer
join - Instance of Join
setFullEnvelope
public void setFullEnvelope(java.lang.String layerID,
java.lang.String bFullEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not. Use "true" if the response indicates the envelope,"false"
otherwise
Parameters:
layerID - identifier of the layer
bFullEnvelope - "true" if the response indicates the envelope,"false" otherwise
setFullEnvelopeByInt
public void setFullEnvelopeByInt(java.lang.String layerID,
int bFullEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not. Use 1 if the response indicates the envelope,0
otherwise.
Parameters:
layerID - identifier of the layer
bFullEnvelope - 1 if the response indicates the envelope,0 otherwise
hasFullEnvelope
public boolean hasFullEnvelope(java.lang.String layerID)
Indicates if the response indicates the full envelope for all returned features of the layer or not.
Parameters:
layerID - identifier of the layer
Returns:
true if the response indicates the envelope, false otherwise
setEnvelope
public void setEnvelope(java.lang.String layerID,
java.lang.String bEnvelope)
Set whether the response should indicate the envelope for each returned features or not. Use "true" if the response indicates the envelope,"false" otherwise.
106 PCI Geomatics

Parameters:
layerID - identifier of the layer
bEnvelope - "true" if the response indicates the envelope for each feature,"false" otherwise
Class LayerInfoFilterConfig
setEnvelopeByInt
public void setEnvelopeByInt(java.lang.String layerID,
int bEnvelope)
Set whether the response should indicate the full envelope for all returned features of the layer or not. Use 1 if the response indicates the envelope for
each feature,0 otherwise.
Parameters:
layerID - identifier of the layer
bEnvelope - 1 if the response indicates the envelope,0 otherwise
hasEnvelope
public boolean hasEnvelope(java.lang.String layerID)
Indicates if the response should indicate the envelope for each returned features
Parameters:
layerID - identifier of the layer
Returns:
true if the response indicates the envelope, false otherwise
getXSLTInfo
public XSLTInfo getXSLTInfo()
Get the XSLTInfo for the request used to transform the result set.
Returns:
XSLTInfo associated with the request
setXSLTInfo
public void setXSLTInfo(java.lang.String path)
Set the XSLTInfo for the request used to transform the result set.
getXSLTInfoParam
public java.lang.String getXSLTInfoParam(java.lang.String key)
Get the parameter for the xslt
setXSLTInfoParam
public void setXSLTInfoParam(java.lang.String key,
java.lang.String value)
Set the parameter for the xslt
Geomatica WebServer Suite Installation Guide 107

Chapter 8 - API Reference for the WMS
getNumXSLTInfoParam
public int getNumXSLTInfoParam()
Get the parameter number
Returns:
int the number of parameters
getMaxFeature
public int getMaxFeature()
Get the maximum number of features returned for all layers
Returns:
maximum number of features returned for all layers
setMaxFeature
public void setMaxFeature(java.lang.String layerID,
java.lang.String maxFeature)
Set the maximum number of features returned for all layers
Parameters:
maxFeature - maximum number of features returned for all layers
getOutputFormat
public java.lang.String getOutputFormat()
Get the output format name used to retrieve the result
Returns:
output format name
setOutputFormat
public void setOutputFormat(java.lang.String outputFormat)
Set the output format name used to retrieve the result
getID
public java.lang.String getID()
Get the identifier of the layerInfoFilter. Typically set for asynchrounous communication or stored queries
Returns:
identifier of the LayerInfoFilter
setID
public void setID(java.lang.String ID)
Set the identifier of the layerInfoFilter. Typically set for asynchrounous communication or stored queries
108 PCI Geomatics

Parameters:
ID - identifier of the LayerInfoFilter
isDirectOutput
public boolean isDirectOutput()
Indicate if the output needs to be sent directly or accessed indirectly via a URL or file
Returns:
true if the rensponse is returned directly, false otherwise
setDirectOutput
public void setDirectOutput(boolean directOutput)
Indicatea if the output needs to be sent directly or accessed indirectly via a URL or file
Parameters:
directOutput - true if the rensponse is returned directly, false otherwise
getXMLLayerInfoFilter
public java.lang.String getXMLLayerInfoFilter()
Get the XML encoding of the layer info filter. This could be used in Javascript to send directly the query from a browser.
Returns:
XML encoding of the filter. null if any problem is found. Encoded specifically for HTTP Get.
getLayerInfoFilterURL
public java.lang.String getLayerInfoFilterURL()
Get the URL corresponding to the query based on HTTP Get
Returns:
URI of the request
displayLayerInfoResult
public void displayLayerInfoResult()
Send the layer info query and display the result in the browser window identified by windowName.
Class LayerInfoFilterConfig
Geomatica WebServer Suite Installation Guide 109

Chapter 8 - API Reference for the WMS
Class Extent
This class represents an extent of a figure or drawing. It is written to replace the Rectangle2D.Double that is only available Java 1.2. This class will
ensure that the class is portable among different JVM.
Field Summary
Fields inherited from class com.pcigeomatics.drawing.geom.RectangleDouble
height, width, x, y
Constructor Summary
Extent()
This default constructor builds an extent where the upper left corner is set to (0,0) and the width and height are both set to 0.0.
Extent(double x, double y)
Constructs and initializes a Extent at the specified origin in user-space.
Extent(double x, double y, double width, double height)
Constructs and initializes an Extent with the specified origin in user-space, width, and height.
Extent(Point2d point)
Constructs and initializes a RectangleDouble at the specified origin in user-space.
Extent(RectangleDouble r)
Constructor taking a RectangleDouble as parameter.
Method Summary
java.lang.Object
Extent
Extent
java.lang.String
java.lang.String
clone( )
Makes a copy of of an Extent object.
createIntersection(Extent extent)
Returns a new Extent object representing the intersection of this Extent with the specified Extent extent.
createUnion(Extent extent)
Returns a new Extent object representing the union of this Extent with the specified extent.
returnStringBBOX( )
Get a string representing the Extent.
String( )
Get a string representing the Extent.
110 PCI Geomatics

Methods inherited from class com.pcigeomatics.drawing.geom.RectangleDouble
Extent
public Extent()
This default constructor builds an extent where the upper left corner is set to (0,0) and the width and height are both set to 0.0.
Extent
public Extent(double x,
double y,
double width,
double height)
Constructs and initializes an Extent with the specified origin in user-space, width, and height.
Parameters:
x - upper left x coordinate
y - upper left y coordinate
width - width of the extent
height - height of the extent
Extent
public Extent(double x,
double y)
Constructs and initializes a Extent at the specified origin in user-space. The width and height are both set to 0.0.
Parameters:
x - the X ordinate of the upper left corner of the newly constructed Extent
y - the Y ordinate of the upper left corner of the newly constructed Extent
Extent
public Extent(Point2d point)
Constructs and initializes a RectangleDouble at the specified origin in user-space. The width and height are both set to 0.0.
Class Extent
add, add, add, buffer, contains, contains, createIntersection, createUnion, equals, getCenter, getHeight, getMaxX,
getMaxY, getMinX, getMinY, getWidth, hashCode, intersect, intersects, intersects, isEmpty, main, moveBy, setFromDiagonal,
setFromDiagonal, setRectangle, setRectangle, union
Methods inherited from class java.lang.Object
equals, finalize, getClass, notify, notifyAll, wait, wait, wait
Constructor Detail
Geomatica WebServer Suite Installation Guide 111

Chapter 8 - API Reference for the WMS
Parameters:
point - Point2d origin of the rectangle
Extent
public Extent(RectangleDouble r)
Constructor taking a RectangleDouble as parameter.
Parameters:
r - RectangleDouble used to initialize the Extent
Method Detail
createIntersection
public Extent createIntersection(Extent extent)
Returns a new Extent object representing the intersection of this Extent with the specified Extent extent.
Parameters:
extent - the Extent to be intersected with this Extent
Returns:
the largest Extent contained in both the specified extent and in this Extent
createUnion
public Extent createUnion(Extent extent)
Returns a new Extent object representing the union of this Extent with the specified extent.
Parameters:
extent - the Extent to be combined with this Extent
Returns:
the smallest Extent containing both the specified extent and this Extent.
clone
public java.lang.Object clone()
Makes a copy of of an Extent object. The ULC, width, and height will have the exact same values.
Overrides:
clone in class RectangleDouble
Returns:
the Clone of the Extent.
112 PCI Geomatics

toString
public java.lang.String toString()
Get a string representing the Extent. The format of the String is "Extent : ULX = #x#, ULY = #y#, width = #w#, height = #h#", where:
• #x# is the upper left X value
• #y# is the upper left Y value
• #w# is the width
• #h# is the height
This is often used for debugging purposes.
Overrides:
toString in class RectangleDouble
Returns:
a String in the given.
returnStringBBOX
public java.lang.String returnStringBBOX()
Get a string representing the Extent. The format of the String is "lx, by, rx, ty", where:
• lx is the left most X value
• by is the bottom most Y value (equal to: ty-height)
• rx is the right most X value (equal to: lx + width)
• ty is the top most Y value
Returns:
a String in the given format.
Class Point2d
java.lang.Object
com.pcigeomatics.drawing.geom.Point2d
All Implemented Interfaces:
java.lang.Cloneable
public class Point2d
extends java.lang.Object
implements java.lang.Cloneable
Class Point2d
Geomatica WebServer Suite Installation Guide 113

Chapter 8 - API Reference for the WMS
Point2D represents a 2 dimensional point with coordinates in double precision. This class is provided as a replacement of Point2D.Double (Java2) for Java
1.1.
Since:
09/03/2001
Field Summary
double x
The X coordinate of this Point2d.
double y
The Y coordinate of this Point2d.
Constructor Summary
Point2d()
Constructs and initializes a Point2d with coordinates (0,0).
Point2d(double x, double y)
Constructs and initializes a Point2d with the specified coordinates.
Method Summary
static Point2d
add(Point2d p1, Point2d p2)
Add coordinates p1 to p2 to create new point
java.lang.Object clone()
Creates a new object of the same class and with the same contents as this object.
double
static double
double
double
static Point2d
distance(double PX, double PY)
Returns the distance from this Point2d to a specified point.
distance(double X1, double Y1, double X2, double Y2)
Returns the distance between two points.
getX()
getY()
Returns the X ordinate of this Point2d in double precision.
Returns the Y ordinate of this Point2d in double precision.
scale(Point2d p1, double scale)
Scale coordinates p1 by factor scale
114 PCI Geomatics

void
static Point2d
x
public double x
The X coordinate of this Point2d.
y
public double y
The Y coordinate of this Point2d.
Point2d
public Point2d()
setLocation(double x, double y)
Sets the location of this Point2d to the specified double coordinates.
substract(Point2d p1, Point2d p2)
Subtract coordinates p2 from p1 to create new point
java.lang.String toString()
Returns a String that represents the value of this Point2d.
Methods inherited from class java.lang.Object
equals, getClass, hashCode, notify, notifyAll, wait, wait, wait
Field Detail
Constructor Detail
Constructs and initializes a Point2d with coordinates (0,0).
Point2d
public Point2d(double x,
double y)
Constructs and initializes a Point2d with the specified coordinates.
Parameters:
x - the X ordinate of the point
y - the Y ordinate of the point
Method Detail
Class Point2d
Geomatica WebServer Suite Installation Guide 115

Chapter 8 - API Reference for the WMS
getX
public double getX()
Returns the X ordinate of this Point2d in double precision.
Returns:
the X ordinate of this Point2d.
getY
public double getY()
Returns the Y ordinate of this Point2d in double precision.
Returns:
the Y ordinate of this Point2d.
setLocation
public void setLocation(double x,
double y)
Sets the location of this Point2d to the specified double coordinates.
Parameters:
x - the X ordinate of the point
y - the Y ordinate of the point
distance
public double distance(double PX,
double PY)
Returns the distance from this Point2d to a specified point.
Parameters:
PX - the X ordinate of the first point
PY - the Y ordinate of the first point
Returns:
the distance between this Point2d and a specified point.
distance
public static double distance(double X1,
double Y1,
double X2,
double Y2)
Returns the distance between two points.
Parameters:
X1 - the X ordinate of the first point
116 PCI Geomatics

Y1 - the Y ordinate of the first point
X2 - the X ordinate of the second point
Y2 - the Y ordinate of the second point
Returns:
the distance between the two sets of specified coordinates.
add
public static Point2d add(Point2d p1,
Point2d p2)
Add coordinates p1 to p2 to create new point
Parameters:
p1 - first point
p2 - second point
Returns:
new point (p1+p2)
substract
public static Point2d substract(Point2d p1,
Point2d p2)
Subtract coordinates p2 from p1 to create new point
Parameters:
p1 - first point
p2 - second point
Returns:
new point (p1-p2)
scale
public static Point2d scale(Point2d p1,
double scale)
Scale coordinates p1 by factor scale
Parameters:
p1 - first point
scale - scale to apply to point
Returns:
new point scale * p1
toString
public java.lang.String toString()
Class Point2d
Geomatica WebServer Suite Installation Guide 117

Chapter 8 - API Reference for the WMS
Returns a String that represents the value of this Point2d.
Overrides:
toString in class java.lang.Object
Returns:
a string representation of this Point2D.
clone
public java.lang.Object clone()
Creates a new object of the same class and with the same contents as this object.
Overrides:
clone in class java.lang.Object
Returns:
a clone of this instance.
Throws:
java.lang.OutOfMemoryError - if there is not enough memory.
See Also:
Cloneable
Class RectangleDouble
java.lang.Object
com.pcigeomatics.drawing.geom.RectangleDouble
All Implemented Interfaces:
java.io.Serializable, java.lang.Cloneable
Direct Known Subclasses:
Extent
public class RectangleDouble
extends java.lang.Object
implements java.lang.Cloneable, java.io.Serializable
The RectangleDouble class defines a rectangle specified in double precision coordinates. It was created to be JDK1.0 compatible.
118 PCI Geomatics

See Also:
Serialized Form
Field Summary
double
double
double
double
Constructor Summary
height
The height of this RectangleDouble.
width
The width of this RectangleDouble.
x
The x coordinate of the upper left corner of this RectangleDouble.
y
The y coordinate of the upper left corner of this RectangleDouble.
RectangleDouble()
Constructs a new RectangleDouble.
RectangleDouble(double initX, double initY)
Constructs and initializes a RectangleDouble at the specified origin in user-space.
RectangleDouble(double initX, double initY, double initWidth, double initHeight)
Constructs and initializes a RectangleDouble object from the specified coordinates.
RectangleDouble(Point2d initPoint)
Constructs and initializes a RectangleDouble at the specified origin in user-space.
Method Summary
void
add(double newx, double newy)
Adds a point, specified by the double precision arguments newx and newy, to this RectangleDouble.
void
add(Point2d p)
Adds a point, specified by the double precision arguments newx and newy, to this RectangleDouble.
void
add(RectangleDouble r)
Adds a RectangleDouble object to this RectangleDouble.
void
buffer(double distanceX, double distanceY)
Increase the size of the rectangle by the amounts given.
java.lang.Object clone()
Clone the rectangle
boolean
contains(double xIn, double yIn)
Tests if a specified coordinate is inside the boundary of this RectangleDouble.
Class RectangleDouble
Geomatica WebServer Suite Installation Guide 119

Chapter 8 - API Reference for the WMS
boolean
RectangleDouble
RectangleDouble
boolean
Point2d
double
double
double
double
double
double
int
static void
boolean
boolean
boolean
void
void
contains(double xIn, double yIn, double wIn, double hIn)
Tests if the interior of this RectangleDouble entirely contains the specified set of rectangular coordinates.
createIntersection(RectangleDouble r)
Returns a new RectangleDouble object representing the intersection of this RectangleDouble with the specified RectangleDouble.
createUnion(RectangleDouble r)
Returns a new RectangleDouble object representing the union of this RectangleDouble with the specified RectangleDouble r.
equals(RectangleDouble anotherRectangle)
This method checks if two RectangleDoubles are similar, i.e same coordinates.
getCenter()
Get the center of the rectangle
getHeight()
Get the height of the rectangle.
getMaxX()
Get the maximum X coordinate of the rectangle.
getMaxY()
Get the maximum Y coordinate of the rectangle.
getMinX()
Get the minimum X coordinate of the rectangle.
getMinY()
Get the minimum Y coordinate of the rectangle.
getWidth()
Get the width of the rectangle.
hashCode()
Returns the hashcode for this RectangleDouble.
intersect(RectangleDouble src1, RectangleDouble src2, RectangleDouble dest)
Intersects the pair of specified source RectangleDouble objects and puts the result into the specified destination RectangleDouble
object.\
intersects(double xIn, double yIn, double wIn, double hIn)
Tests if the interior of this RectangleDouble intersects the interior of a specified set of rectangular coordinates.
intersects(RectangleDouble r)
Tests if the interior of this RectangleDouble intersects the interior of a specified RectangleDouble
isEmpty()
Determines whether or not this RectangleDouble is empty.
moveBy(double dx, double dy)
Move the rectangle by the offset (dx,dy).
setFromDiagonal(double x1, double y1, double x2, double y2)
Sets the diagonal of the rectangle based on the two specified coordinates.
120 PCI Geomatics

x
public double x
The x coordinate of the upper left corner of this RectangleDouble. It can also be considered the minimum X coordinate.
y
public double y
The y coordinate of the upper left corner of this RectangleDouble. It can also be considered the maximum Y coordinate.
width
public double width
The width of this RectangleDouble.
height
public double height
The height of this RectangleDouble.
RectangleDouble
public RectangleDouble()
Constructs a new RectangleDouble. The location and size (width and height) are all initialized to 0.
Class RectangleDouble
void
setFromDiagonal(Point2d p1, Point2d p2)
Sets the diagonal of the rectangle based on the two specified point in double precision.
void
setRectangle(double newX, double newY, double newWidth, double newHeight)
Sets the location and size of this RectangleDouble to the specified double values.
void
setRectangle(RectangleDouble sourceRectangle)
Copy the settings of the specified RectangleDouble, sourceRectangle, to thisRectangleDouble.
java.lang.String toString()
Returns the String representation of this RectangleDouble.
static void
union(RectangleDouble src1, RectangleDouble src2, RectangleDouble dest)
Unions the pair of source RectangleDouble objects and puts the result into the specified destination RectangleDouble dest object.
Methods inherited from class java.lang.Object
equals, getClass, notify, notifyAll, wait, wait, wait
Field Detail
Constructor Detail
Geomatica WebServer Suite Installation Guide 121

Chapter 8 - API Reference for the WMS
Location ( x = 0.0, y = 0.0 )
ize ( width = 0.0, height = 0.0 )
RectangleDouble
public RectangleDouble(double initX,
double initY,
double initWidth,
double initHeight)
Constructs and initializes a RectangleDouble object from the specified coordinates.
Parameters:
initX - initial X ordinate of the upper left corner of the newly constructed RectangleDouble.
initY - initial Y ordinate of the upper left corner of the newly constructed RectangleDouble.
initWidth - initial width of the newly constructed RectangleDouble.
initHeight - initial height of the newly constructed RectangleDouble.
RectangleDouble
public RectangleDouble(double initX,
double initY)
Constructs and initializes a RectangleDouble at the specified origin in user-space. The width and height are set to 0.
Parameters:
initX - initial X ordinate of the upper left corner of the newly constructed RectangleDouble.
initY - initial Y ordinate of the upper left corner of the newly constructed RectangleDouble.
RectangleDouble
public RectangleDouble(Point2d initPoint)
Constructs and initializes a RectangleDouble at the specified origin in user-space. The width and height are set to 0.
Parameters:
initPoint - Point2d origin of the rectangle
Method Detail
getMinX
public double getMinX()
Get the minimum X coordinate of the rectangle.
Returns:
minimum X coordinate of the rectangle.
122 PCI Geomatics

getMaxX
public double getMaxX()
Get the maximum X coordinate of the rectangle. This is equivalent to getMinX() + getWidth().
Returns:
maximum X coordinate of the rectangle.
getMinY
public double getMinY()
Get the minimum Y coordinate of the rectangle. This is equivalent to getMaxY() - getHeight().
Returns:
minimum Y coordinate of the rectangle.
getMaxY
public double getMaxY()
Get the maximum Y coordinate of the rectangle.
Returns:
maximum Y coordinate of the rectangle.
getWidth
public double getWidth()
Get the width of the rectangle.
Returns:
width of the rectangle.
getHeight
public double getHeight()
Get the height of the rectangle.
Returns:
height of the rectangle.
setRectangle
public void setRectangle(double newX,
double newY,
double newWidth,
double newHeight)
Sets the location and size of this RectangleDouble to the specified double values.
Parameters:
Class RectangleDouble
Geomatica WebServer Suite Installation Guide 123

Chapter 8 - API Reference for the WMS
newX - the new X ordinate of the upper left corner of this rectangle.
newY - the new Y ordinate of the upper left corner of this rectangle.
newWidth - the new width of this rectangle.
newHeight - the new height of this rectangle.
setRectangle
public void setRectangle(RectangleDouble sourceRectangle)
Copy the settings of the specified RectangleDouble, sourceRectangle, to thisRectangleDouble.
Parameters:
sourceRectangle - the RectangleDouble to copy.
setFromDiagonal
public void setFromDiagonal(double x1,
double y1,
double x2,
double y2)
Sets the diagonal of the rectangle based on the two specified coordinates. This method takes care of determining the minimum and maximum values of
the x and y coordinates of each point. It will perform a swap if needed.
Parameters:
x1 - the first specified X coordinate
y1 - the first specified Y coordinate
x2 - the second specified X coordinate
y2 - the second specified Y coordinate
setFromDiagonal
public void setFromDiagonal(Point2d p1,
Point2d p2)
Sets the diagonal of the rectangle based on the two specified point in double precision. This method takes care of determining the minimum and maximum
values of the x and y coordinates of each point. It will perform a swap if needed.
Parameters:
p1 - the first specified point.
p2 - the second specified point.
equals
public boolean equals(RectangleDouble anotherRectangle)
This method checks if two RectangleDoubles are similar, i.e same coordinates.
Returns:
true if the two rectangles are similar false if the two rectangles are different
124 PCI Geomatics

isEmpty
public boolean isEmpty()
Class RectangleDouble
Determines whether or not this RectangleDouble is empty. An RectangleDouble is considered as empty if width or height are less or equal 0.0.
Returns:
true if this RectangleDouble is empty; false otherwise.
createIntersection
public RectangleDouble createIntersection(RectangleDouble r)
Returns a new RectangleDouble object representing the intersection of this RectangleDouble with the specified RectangleDouble.
Parameters:
r - the RectangleDouble to be intersected with this RectangleDouble
Returns:
the largest RectangleDouble contained in both the specified RectangleDouble and in this RectangleDouble
createUnion
public RectangleDouble createUnion(RectangleDouble r)
Returns a new RectangleDouble object representing the union of this RectangleDouble with the specified RectangleDouble r.
Parameters:
r - the RectangleDouble to be combined with this RectangleDouble
Returns:
the smallest RectangleDouble containing both the specified RectangleDouble r and this RectangleDouble.
add
public void add(double newx,
double newy)
Adds a point, specified by the double precision arguments newx and newy, to this RectangleDouble. The resulting RectangleDouble is the smallest RectangleDouble
that contains both the original RectangleDouble and the specified point.
After adding a point, a call to contains with the added point as an argument does not necessarily return true. The contains method does not return true
for points on the right or bottom edges of a rectangle. Therefore, if the added point falls on the left or bottom edge of the enlarged rectangle, contains
returns false for that point.
Parameters:
newx - the X coordinates of the new point.
newy - the Y coordinates of the new point
add
public void add(Point2d p)
Adds a point, specified by the double precision arguments newx and newy, to this RectangleDouble. The resulting RectangleDouble is the smallest RectangleDouble
that contains both the original RectangleDouble and the specified point.
Geomatica WebServer Suite Installation Guide 125

Chapter 8 - API Reference for the WMS
After adding a point, a call to contains with the added point as an argument does not necessarily return true. The contains method does not return true
for points on the right or bottom edges of a rectangle. Therefore, if the added point falls on the left or bottom edge of the enlarged rectangle, contains
returns false for that point.
Parameters:
p - Point2d the new point to add in the extent
add
public void add(RectangleDouble r)
Adds a RectangleDouble object to this RectangleDouble. The resulting RectangleDouble is the union of the two RectangleDouble objects.
Parameters:
r - the RectangleDouble to add to this RectangleDouble.
contains
public boolean contains(double xIn,
double yIn)
Tests if a specified coordinate is inside the boundary of this RectangleDouble.
Parameters:
xIn - the x coordinates to test.
yIn - the y corrdinates to test.
Returns:
true if the specified coordinates are inside the boundary of this RectangleDouble; false otherwise.
contains
public boolean contains(double xIn,
double yIn,
double wIn,
double hIn)
Tests if the interior of this RectangleDouble entirely contains the specified set of rectangular coordinates.
Parameters:
xIn - the X ordinates of the upper left corner of the specified set of rectangular coordinates
yIn - the Y ordinates of the upper left corner of the specified set of rectangular coordinates
wIn - the width of the specified set of rectangular coordinates
hIn - the height of the specified set of rectangular coordinates
Returns:
true if this RectangleDouble entirely contains specified set of rectangular coordinates; false otherwise.
intersect
public static void intersect(RectangleDouble src1,
126 PCI Geomatics

Class RectangleDouble
RectangleDouble src2,
RectangleDouble dest)
Intersects the pair of specified source RectangleDouble objects and puts the result into the specified destination RectangleDouble object.\
Parameters:
src1 - the first of a pair of RectangleDouble objects to be intersected with each other
src2 - the second of a pair of RectangleDouble objects to be intersected with each other
dest - the RectangleDouble that holds the results of the intersection of src1 and src2
intersects
public boolean intersects(double xIn,
double yIn,
double wIn,
double hIn)
Tests if the interior of this RectangleDouble intersects the interior of a specified set of rectangular coordinates.
Parameters:
xIn - the X ordinates of the upper left corner of the specified set of rectangular coordinates
yIn - the Y ordinates of the upper left corner of the specified set of rectangular coordinates
wIn - the width of the specified set of rectangular coordinates
hIn - the height of the specified set of rectangular coordinates
Returns:
true if this RectangleDouble intersects the interior of a specified set of rectangular coordinates; false otherwise.
intersects
public boolean intersects(RectangleDouble r)
Tests if the interior of this RectangleDouble intersects the interior of a specified RectangleDouble
Parameters:
r - the of RectangleDouble object to be intersected with this one.
Returns:
true if this RectangleDouble intersects the interior of r; false otherwise.
union
public static void union(RectangleDouble src1,
RectangleDouble src2,
RectangleDouble dest)
Unions the pair of source RectangleDouble objects and puts the result into the specified destination RectangleDouble dest object.
Parameters:
src1 - the first of a pair of RectangleDouble objects to be combined with each other
src2 - the second of a pair of RectangleDouble objects to be combined with each other
Geomatica WebServer Suite Installation Guide 127

Chapter 8 - API Reference for the WMS
dest - the RectangleDouble that holds the results of the union of src1 and src2
moveBy
public void moveBy(double dx,
double dy)
Move the rectangle by the offset (dx,dy).
Parameters:
dx - offset in X in user space
dy - offset in Y in user space
buffer
public void buffer(double distanceX,
double distanceY)
Increase the size of the rectangle by the amounts given.
Parameters:
distanceX - is the amount to add on each side (left and right) of the retangle.
distanceY - is the amount to add on each top and the bottom of the retangle.
getCenter
public Point2d getCenter()
Get the center of the rectangle
Returns:
Point2D center of the rectangle in user-space coordinate
clone
public java.lang.Object clone()
Clone the rectangle
Overrides:
clone in class java.lang.Object
Returns:
Clone of the rectangle
hashCode
public int hashCode()
Returns the hashcode for this RectangleDouble.
Overrides:
hashCode in class java.lang.Object
128 PCI Geomatics

Returns:
the hashcode for this RectangleDouble.
toString
public java.lang.String toString()
Returns the String representation of this RectangleDouble.
Overrides:
toString in class java.lang.Object
Returns:
a String representing this rectangle.
Class RectangleDouble
Geomatica WebServer Suite Installation Guide 129

Chapter 8 - API Reference for the WMS
130 PCI Geomatics

Index
A
Abstract Parameter 42
AccessConstraint Parameter 43
Add Several Map Layers 68
adding
buttons 56
elements 54
measurement tools 58
Query Buttons 59
AllProject.xml 67
ALT attribute 57
Alter Zoom Values 57
API 77
applet 55
AllProject.xml 67
configuration files 17
create configuration file 67
layers.xml 67
MapViewer configuration 67
applet and browser 11
Applet DTD 74
Application Programming Interface 77
APPLY button 55
ArrayButtonName variable 56
Assisted Configuration 40
Attribute
alt 57
base 27, 28
border 56
default-style 73
exception-format 70
height 57
info-format 70
layerid 45, 73
map-format 70
mapService-Config.dtd 47
MapViewer.dtd 74
maxx 69
maxy 69
minx 69
miny 69
name 56
onmousedown 57
queryable 44, 73
src 56
srs 69
131

type 27, 28, 71
url 70
version 71
visible 71, 73
width 57
Automatic Configuration
See Self-Configured
B
basic model 52
Bbox Element 46
BORDER attribute 56
Bounding Box 46, 72
browser 11
Build Query Expressions 63
Buttons 56
C
Capabilities 25, 42, 52, 70, 73
Capabilities_DTD_URL parameter 42
Change the Supported-Bbox 72
check boxes 55
CheckForm 55
CheckFormQuery 55
class
Extent 109
Layer 88
LayerInfoFilterConfig 97
MapViewerApplet 77
Point2d 113
RectangleDouble 118
client
WCS 10
WFS 9
WMS 11
WMS applet 11
Combo Box 58
Config Parameter 67
config.xml
contact information 32
deployment parameters 32
fees and constraints 32
file contents 31
metadata configuration 33
online resource parameter 32
service information 32
system properties 34
temporary directory section 32
WCS 31
Configuration File
Config Folder 17
MapViewer Applet 67
Servlet 39
web.xml (WFS) 21
wfs_init.properties 21
Configure the MapViewer Applet 67
Contact_Information 43
coordinate display 53
coverage, definition of 10
Create your HTML file 54
Create Your XML File 52
CRS file
EPSG codes 32
Customized Configuration 40
D
data source configuration file (WFS) 27
Debug 42
default configuration 39
Default Style Attribute 73
deploy.xml file
deploy elements and descriptions 36
hierarchical structure of elements 35
hierarchy of deploy and group paths 38
location in WCS 35
Description Element 71
Determine the Supported-Styles 72
display coordinates 64
display overview 64
132 PCI Geomatics

display the coordinates 53
DisplayFeatureInfo 60
DOCTYPE Definition 68
Document Type Definition file (DTD) 17
Drop-down Combo Box 58
DTD 45
GeoWSServlet Servlet 39, 45
MapViewer 74
E
EASI Servlet 43
Element
abstract 45, 46
bbox 45, 46
description 71
extent 69
Filter 27, 28
hostname 46
layerid 68
layertype 44, 46
map 44, 45, 68, 71
maplayer 44, 45, 71
mapprovider 45, 46
mapservice-config 44, 45
mapService-Config.dtd 47
MapViewer.dtd 74
mapviewer-config 68, 69
metadata 71
port 46
Source 27, 28
Sources 27, 28
style 45, 46
supported-bbox 72
supported-styles 72
title 45, 71
urladdress 46
viewport 69
WMSProvider 68, 70
Environment Variables
JAVA_HOME 14
EPSG codes
CRS text file 32
publishing to the WMS 53
SRS attribute 69
Error in Tomcat (low memory) 18
Exception-format Attribute 70
Export the XML Project 41
Extensible Stylesheet Language for Transformation (XSLT) 18
Extent Element 69
F
Factor 58
Feature_info 70
features, definition of 9
Fees Parameter 42
Focus
using WCS client 10
using WFS client 9
using WMS client 11
Focus_HostName 40, 42
Focus_Port 40, 42
FocusConnector 46
G
GDBQuery 63
generate Capabilities file 73
Geomatica
installation 13
Geomatica Focus
using WCS client 10
using WFS client 9
using WMS client 11
Geomatica WebServer Monitor 49
GeoWSServlet Servlet 39
GetMap 42
GIFs 70
graphics 18
Geomatica WebServer Suite Installation Guide 133

H
HEIGHT attribute 57
HostName 42
Hostname Element 46
HTML files 53
HTTP port 16
HTTP Server 13
I
icons 18
Info-format Attribute 70
initialization properties (parameters)
WFS 23
WMS 41
Installation
Geomatica 13
Java Developer’s Kit (SDK) for Windows 14
Tomcat server on Windows 14
WAR file 16
Intended Audience 7
J
Java
install on Windows 14
JavaScript 57
adding buttons 56
areaMeasure 59
browserCheck 64
circleMeasure 59
cursorTool 64
displayCoordinate 64
DisplayFeatureInfo 60
LayerOnOff 55
LayerQueryableSimple 56
lengthMeasure 59
Line 62
PanAndZoom 57
Polygon 62, 63
PropertyQuery 63
QueryPointMode 61, 62
redirectWindow 63
SendQuery 63
setTimeout 60
toggleInfoQuery 60
toggleInfoQueryLine 61
toggleInfoQueryPoly 62
zoom factor 58
ZoomIn 57
ZoomInDefault 57
ZoomInPercent 57
ZoomInPercentDefault 57
ZoomOut 57
ZoomOutDefault 57
ZoomOutPercent 58
ZoomOutPercentDefault 57
ZoomPercentForm 58
ZoomWindow 57
ZoomZoom 57
JPEGs 70
JSMapViewer.js file 55, 57
K
KeyWord Parameter 42
L
Layerid Attribute 68, 73
LayerOnOff function 55
LayerQueryable 60
LayerQueryableSimple 56
layers.xml 67
Layertype Tag 46
logos 18
Loop 55
Low Memory Error 18
M
Manual Configuration
See Customized
134 PCI Geomatics

Map 70
Map Element 68, 71
Map Request 70
map, definition of 10
Map-format Attribute 70
Maplayer Element 45, 68, 71
Mapprovider Tag 46
MapService_Configuration 40, 42
MapService-Config DTD 47
Mapservice-config Element 45
MapViewer Applet 67
MapViewer DTD 67, 74
Mapviewer-config Element 68, 69
MapViewerTemplate1.html 52
MapViewerTemplates 51
Maxx 69
Maxy 69
Measurement.js 58
Metadata Element 71
Microsoft Windows - recommended 8
MIME 70
Minx 69
Miny 69
Modify the Templates 52
Monitor 50
mosaics
about 35
setting 36
Multipurpose Internet Mail Extensions 70
N
NAME attribute 56
Name Parameter 42
new window 63
O
OGC Web Mapping Server 71
OGC_Compliancy_Mode 42
OGC-WMT 71
OnlineResource Parameter
configuring the WFS 25
configuring the WMS 42
ONMOUSEDOWN attribute 57
Open Geospatial 25, 42, 52
open new page 63
Overview 64
P
Parameter
Capabilities_DTD_URL 42
Focus_HostName 40, 42
Focus_Port 40, 42
fs.application.schema.namespace.url 26
Initialization 41
MapService_Configuration 40, 41, 42
Path_Contact_Information 43
Service_Abstract 42
Service_AccessConstraint 43
Service_Debug 42
Service_Fees 42
Service_KeyWord 42
Service_Name 42
Service_OnlineResource 42
Service_Title 42
setting in WMS 43
wfs.application.schema.namespace. prefix 26
wfs.bad.file.action 24
wfs.capabilities.service.abstract 25
wfs.capabilities.service.name 25
wfs.capabilities.service.online.resource 25
wfs.capabilities.service.title 25
wfs.data.sources.filename 23
wfs.invalid.characters.action 24
wfs.share.matching.layer.name.action 24
wfs.transaction.allow 24
wfs.transaction.timeout 25
Parameters 41
Path_Contact_Information 43
Percent Values 58
Geomatica WebServer Suite Installation Guide 135

Port 42
Port Tag 46
Post.html 63
Prevent corrupted or blank images 70
PropertyQuery 63
Publishing Your Data
features 26
maps 49
maps in a Web page 50
Q
Query 55
query tools 59
display coordinate 64
GDBQuery 63
General Query button 60
Line Query button 61
Polygon Query button 61
Query Select Point button 61
saved queries 63
Spatial Query buttons 61
Query.js 60
Queryable Attribute 73
R
reconfigure Geomatica Focus with EASI 43
redirectWindow 63
remote Tomcat reset 43
Replace the Description 71
Replace the Metadata 71
Replace the Title 71
reset the MapService 43
Reset.html 44
Restart Tomcat 18
S
Saved queries 63
scripting, EASI, query tools
EASI servlet 43
section 32
Self-Configured Configuration 39
Semi-Automatic Configuration
See Assisted
SendQuery 62
Service_Abstract 42
Service_AccessConstraint 43
Service_Debug 42
Service_Fees 42
Service_KeyWord 42
Service_Name 42
Service_OnlineResource 42
Service_Title 42
servlet
WCS 10
WFS 9
WMS 11
Servlet Configuration File 39
Export from Geomatica Focus 41
Servlet DTD 39
Set the Maplayer Attributes 73
setTimeout 60
show coordinates 64
Solaris 8
Spatial Reference System (SRS) 45, 46, 69
SRC attribute 56
SRS Attribute 69
standard HTTP port 16
Start Geomatica WebServer Monitor 50
Stop Tomcat 18
Style 46
Supported-bbox Child Element 72
Supported-styles Element 72
Syntax
GeoWSServlet Servlet 44
MapViewer Applet 68
Syntax of Servlet Configuration File 45
System Requirements 7
136 PCI Geomatics

T
Templates 51, 52
Title Element 45, 71
Title Parameter 42
toggleAllButton 57
toggleInfoQuery 60
Tomcat
install on Windows 14
low memory error 18
remote reset 43
restart 18
stop 18
testing the server 15
Type Attribute 71
U
URL Address 70
URL Attribute 70
URLConnector 46
V
Validate XML File 45
Version Attribute 71
View 55
viewer 64
Viewport Element 69
Visible Attribute 73
Visible Layers 55
vue 55
W
WCS 7
configuring the servlet 31
deployment file 35
publishing your coverages 35
testing the servlet 34
troubleshooting 38
WCS folder 16
WCS images folder 16
WCS META-INF folder 16
WCS schemas folder 17
WCS WEB-INF folder 17
Web Archive (WAR) file 16
web.xml
WFS 21, 22
WMS 43
WFS 7
configuring the servlet 21
data source configuration file 27
publishing your feature data 26
testing the servlet 26
troubleshooting 28
wfs.application.schema.namespace. 26
wfs.application.schema.namespace.url 26
wfs.bad.file.action 24
wfs.capabilities.service.abstract 25
wfs.capabilities.service.name 25
wfs.capabilities.service.online.resource 25
wfs.capabilities.service.title 25
wfs.data.sources.filename 23
wfs.invalid.characters.action 24
wfs.share.matching.layer.name.action 24
wfs.transaction.allow 24
wfs.transaction.timeout 25
wfs_init.properties 21
WFS conf folder 17
WFS demo folder 17
WFS folder 17
WFS images folder 17
WFS META-INF folder 17
WFS WEB-INF folder 17
WIDTH attribute 57
WMS 7
WMS Application folder 17
WMS Config Folder 17
WMS DTD Folder 17
WMS folder 17
WMS help folder 18
Geomatica WebServer Suite Installation Guide 137

WMS images folder 18
WMS JavaScript Folder 18
WMS MapViewer.jar file 18
WMS MapViewerTemplate.html file 18
WMS META-INF folder 18
WMS WEB-INF folder 18
WMS XSLT folder 18
WMSProvider Element 70
WMT_XML 70
X
XML files
Applet Configuration 52, 67
Export from Geomatica Focus 41
Servlet Configuration 41
Z
Zoom 57
Zoom Factor 58
Zoom Functions 57
ZoomIn() 58
ZoomInPercent() 58
ZoomOut() 58
ZoomOutPercent() 58
ZoomPercentForm 58
138 PCI Geomatics