MapInfo Spatial Server Web Map Service - Product Documentation ...

MapInfo Spatial Server
Version 1.0
MapInfo Spatial Server Web Map Service

Information in this document is subject to change without notice and does not represent a commitment on the
part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any
form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney
Bowes Software Inc., One Global View, Troy, New York 12180-8399.
© 2012 Pitney Bowes Software Inc. All rights reserved. Pitney Bowes Software Inc. is a wholly-owned subsidiary
of Pitney Bowes Inc. Pitney Bowes, the Corporate logo, MapInfo, Group 1 Software, and MapInfo Professional
are [registered] trademarks of Pitney Bowes Inc. or a subsidiary. All other trademarks are the property of their
respective owners.
United States:
Phone: 518.285.6000
Fax: 518.285.6070
Sales: 800.327.8627
Government Sales: 800.619.2333
Technical Support: 518.285.7283
Technical Support Fax: 518.285.7575
www.pb.com/software
Canada:
Phone: 416.594.5200
Fax: 416.594.5201
Sales: 800.268.3282
Technical Support:.518.285.7283
Technical Support Fax: 518.285.7575
www.pb.com/software
Europe/United Kingdom:
Phone: +44.1753.848.200
Fax: +44.1753.621.140
Technical Support: +44.1753.848.229
www.pitneybowes.co.uk/software
Asia Pacific/Australia:
Phone: +61.2.9437.6255
Fax: +61.2.9439.1773
Technical Support: 1.800.648.899
www.pitneybowes.com.au/software
Contact information for all Pitney Bowes offices is located at: www.pb.com/contact-us.
Products named herein may be trademarks of their respective manufacturers and are hereby recognized.
Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on
the trademark.
30 / 04 / 2012

Contents
Chapter 1: Introduction..............................................................................................5
Overview...............................................................................................................................6
Layers and Styles.............................................................................................................6
WMS Servers...................................................................................................................6
Understanding the WMS Server Functionality.................................................................6
How to Get Information About a WMS Server.................................................................7
How to Retrieve a Map From a WMS Server...................................................................7
How to Use the WMS Server GetFeatureInfo Operations...............................................7
Chapter 2: Managing WMS Resources and Configuration.....................................9
Accessing and Modifying the Configuration File...........................................................10
Accessing the Repository using WebDAV.....................................................................10
Reload the Service Configuration using JMX Console..................................................12
Configuration File Parameters.........................................................................................13
Service Parameters........................................................................................................13
Defining a WMSLayer....................................................................................................14
Creating a WMSLayerTree............................................................................................15
Accessing the Web Map Service From Within MapInfo Professional..........................16
Adding a WMS Server in MapInfo Professional.............................................................16
Chapter 3: Web Map Service Capabilities...............................................................19
Getting Service-level Metadata About a WMS................................................................20
Inputs and Behaviors.....................................................................................................20
Output............................................................................................................................20
Getting Maps......................................................................................................................23
Inputs and Behaviors.....................................................................................................23
Sample Response..........................................................................................................24
Getting Information About Map Features.......................................................................25

4
Inputs and Behaviors.....................................................................................................25
Output............................................................................................................................26
Chapter 4: Web Map Service Fundamentals..........................................................27
WMS Server Technology...................................................................................................28
HTTP GET...........................................................................................................................28
Basic Authentication.........................................................................................................28
Layers and Styles..............................................................................................................29
MapInfo Spatial Server 1.0

Introduction
This guide provides descriptions and examples for the developer who is writing
applications that access the Web Map Service.
The Web Map Service lets an application render layers of geographic data onto
a map image. The OpenGIS Consortium (OGC) Web Map Service standard
(version 1.1.1 and 1.3.0 located at www.opengeospatial.org/specs) defines
how a client can retrieve map images over the Internet or a private intranet by
submitting requests through HTTP. Products that can use results from an OGC
compliant WMS server will work with the MapInfo Spatial Server OGC Web Map
Service, such as MapInfo Professional and MapXtreme or other vendor software.
In this section:
• Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
• Understanding the WMS Server Functionality . . . . . . . . . .6
1

Overview
Overview
The MapInfo Spatial Server Web Map Service (WMS) allows software clients to reference map images
over the Internet or a private intranet. The WMS implementation is based on the WMS 1.1.1 and 1.3.0
OGC specification. Using HTTP requests, the WMS provides georeferenced data to a client that displays
this data as an image. Georeferenced data is information associated with maps that describe the real
world extents of specific features and the projection upon which it is based.
The images can be provided as GIF, JPEG, PNG, and other image formats.
Layers and Styles
The images rendered can be made of layers that are hierarchical—an image can be served that is made
up of a layer that is a collection of other layers. Since WMS renders layers, the characteristics that
modify the view of layers, such as styles and coordinate systems, can also be included in the layers
provided. This lets you customize images because each image can act as a separate layer within the
client that is accessing these images.
WMS Servers
Aside from the servers provided by Pitney Bowes Software Inc. and any service that you provide through
your own organization, there are many public access WMS servers available on the World Wide Web.
There are WMS servers for LandSat data, USGS DOQ photos, bathymetry, weather, and many other
data types. Pitney Bowes Software Inc. maintains a Web Map Server of many of our data products. To
view these products, open the following URI in a WMS client, such as MapInfo Professional:
http://www.mapinfo.com/miwms
If you are accessing maps from different sources, it is not a complicated task to combine the images into
a single coherent image that your users can work with. It is important to keep the spatial information
(bounding box, spatial reference system, height, and width) identical. This ensures that the different images
align with each other properly.
Note:
Not all Web Map Servers adhere to the OGC standards and may or may not be compatible with
your WMS client.
Please refer to the OGC WMS 1.1.1 or 1.3.0 specifications (www.opengeospatial.org/standards/) for
more information about developing a WMS client to the WMS 1.1.1 or 1.3.0 specification.
Understanding the WMS Server Functionality
6
There are three WMS server-specific methods that provide the basis for the server implementation:
• GetCapabilities
• GetMap
• GetFeatureInfo
Each of these methods is discussed below.
MapInfo Spatial Server 1.0

Note:
A basic Web Map Service classifies its georeferenced information holdings into "layers" and offers
a number of predefined "styles" in which to display those layers.
How to Get Information About a WMS Server
When first finding a Web Map Server, it is necessary to find out the names of available layers, styles in
use, spatial information in use, and other information that the server provides, in order to make a request
for an image that is within the parameters of the server.
The GetCapabilities request retrieves service-level metadata over the Internet or intranet, including the
server name, the layer names, abstracts about the data, and valid request parameters, among other
data. The following section highlights potential ways to apply this capability: Getting Service-level
Metadata About a WMS on page 20.
How to Retrieve a Map From a WMS Server
GetMap retrieves the geospatial information, over the Internet or an intranet, based on a specific request
of the data you want and returns it as a raster image. When invoking GetMap a WMS client can specify:
• Layers
• Styles
• A bounding box (the area to be mapped)
• A coordinate reference system (also known as the spatial reference system)
• Output image format (JPEG, GIF, PNG. and others).
• Output size (height and width of the returned image)
• Background transparency and color
The following section highlights potential ways to apply this capability: Getting Maps on page 23.
How to Use the WMS Server GetFeatureInfo Operations
GetFeatureInfo returns request information for a feature at a given point on the map after a GetMap has
been called. This is a search-at-point operation in which, after a GetMap request, the GetFeatureInfo
request supplies the X, Y pixel coordinates of the location about which you want more information. The
following section highlights potential ways to apply this capability: Getting Information About Map
Features on page 25.
MapInfo Spatial Server Web Map Service
Chapter 1: Introduction
7

Managing WMS Resources
and Configuration
This section describes how to configure and add resources to the Web Map
Service. The WMS is installed and pre-configured with the configuration file (named
configuration) located in the repository. WMS uses the standard XML service
configuration similar to the other MapInfo Spatial Server services.
The named WMS configuration file WMSConfiguration is located in the Configuration
directory under the root repository. For example, a default installation
will place the WMS configuration file at http://localhost:8080/RepositoryService/repository/default/Configuration/WMSConfiguration
You can use your standard WebDAV protocol tools (e.g., Windows WebFolders,
DAVExplorer, etc.) to copy the configuration file from the repository, and then
upload the modified configuration file back. Once uploaded, you must use the
MapInfo Spatial Server JMX Console to invoke the new configuration for the
service.
Note:
You must be on the local machine hosting MapInfo Spatial Server to access
and make changes to resources in the repository.
In this section:
• Accessing and Modifying the Configuration File . . . . . .10
• Configuration File Parameters . . . . . . . . . . . . . . . . . . . . . .13
• Accessing the Web Map Service From Within MapInfo Professional
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
2

Accessing and Modifying the Configuration File
Accessing and Modifying the Configuration File
The named WMS configuration file WMSConfigurationis located in the Configuration directory
under the root repository. For example, a default installation will place the WMS configuration file at http://localhost:8080/RepositoryService/repository/default/Configuration/WMSConfiguration
To configure the WMS, perform the following:
1. You must be located on the local machine hosting MapInfo Spatial Server and the repository.
2. Use a standard WebDAV protocol tool to access the repository (e.g., Windows WebFolders, DAVExplorer,
etc.) and copy the configuration file from the repository to a directory on your local machine.
The WMS configuration file is located at http://localhost:8080/RepositoryService/repository/default/Configuration/WMSConfiguration
For examples of using standard WebDAV tools, see Accessing the Repository using WebDAV
on page 10
3. Make changes to the local WMSConfiguration file.
4. Upload the modified configuration file back to the same location (and name) in the repository using
your WebDAV tool.
5. Use the MapInfo Spatial Server JMX Console to invoke the new configuration for the service. For
instruction on how to reload the configuration using the JMX Console, see Reload the Service
Configuration using JMX Console on page 12
Accessing the Repository using WebDAV
10
Configuration files are pre-loaded in the repository for each service. These configuration files are located
at http://localhost:8080/RepositoryService/repository/default/Configuration/.
To configure the services, you must use a WebDAV protocol tool to access the JCR repository, copy
the configuration file locally, make changes to the file, copy the configuration file back to the repository,
and reload the configuration using the JMX Console. There are many tools available to accomplish the
WebDAV connection tasks. We have provided two examples:
Using WebFolders to Access the Repository Resources
To add or modify a resource, you must copy the resource to or from the repository using a WebDAV
tool. Using WebFolders is an easy way to access the repository and the resources contained in the repository.
Note:
WebFolders is for Windows machines only. To access the repository, you must be on the same
machine where MapInfo Spatial Server and the repository are installed.
To configure a WebFolder:
1. Using the Windows file explore, for the method appropriate for your version of Windows, select Map
Network Drive...
2. In the pop-up window, click on the link 'sign up for online storage or connect to a
network server' or you may have a link that mentions'Connect to a website...'.
3. Click the Next and select Choose another network location. Click Next.
MapInfo Spatial Server 1.0

4. In the Internet or network addressfield add the repository URL http://localhost:8080/RepositoryService/repository/default/.
Click Next.
5. If you are asked for cridentials, use the username and password Admin/Admin
6. Give this connection a name. For example, Spatial Server Repository. Click Next.
Once finished, you will have a folder connection to the contents of the repository under your network
places.
The WebFolder connection to the repository can be used like any other windows explorer folder, where
files can be copied from the repository, modified, and copied back to the same location in the repository.
Using DAVExplorer to Access the Repository Resources
To add or modify a resource, you must copy the resource to or from the repository using a WebDAV
tool. Using DavExplorer is an easy way to access the repository and the resources contained in the repository.
DAVExplorer is a freely available WebDAV client application. This software is available from
http://www.davexplorer.org.
Note:
DavExplorer is for Windows machines only. To access the repository, you must be on the same
machine where MapInfo Spatial Server and the repository are installed.
To get or add resources from the repository using DAVExplorer, use the following instructions:
Getting Resources From the Repository Using DAVExplorer
Use the following steps to get resources from the repository using DAV Explorer:
1. Open DAVExplorer.
2. In DAVExplorer, enter the URL of the MapInfo Spatial Server repository and click the Connect button.
For example, enter localhost:8080/RepositoryService/repository/default/. (Note
that DAVExplorer prepends http:// automatically.)
If prompted, enter the admin/admin login name and password required to connect to the repository.
Once you are connected to the repository, a node for the repository appears in the treeview pane
on the left.
3. In the treeview pane on the left, expand the nodes under the repository node until you see the node
that contains the type of resource you want to get.
For example, if the named resource you want to get is a configuration, expand the repository nodes
until you see the Configuration node. Click on the node to select it. The named configuration resources
in the repository are then listed in the right pane.
4. In the right pane, click on the resource you want to get.
You may click on any of the fields of the named resource to select it.
5. On the File menu, select Get File.
The Save As dialog box opens.
6. In the Save As dialog box, enter a name for the named resource definition file and select the directory
in which you want to save it, then click the Save button.
The selected named resource definition file is saved to the selected file location.
MapInfo Spatial Server Web Map Service
Chapter 2: Managing WMS Resources and Configuration
11

Reload the Service Configuration using JMX Console
Note:
You should always save the resource as the same name as it appears in the repository. By
using this technique, you will never have a conflict when adding the resource back to the repository.
Adding Resources to the Repository Using DAVExplorer
Use the following steps to add resources to the repository using DAVExplorer:
1. Open DAVExplorer.
2. In DAVExplorer, enter the URL of the MapInfo Spatial Server repository and click the Connect button.
For example, enter localhost:8080/RepositoryService/repository/default/. (Note
that DAVExplorer prepends http:// automatically.)
If prompted, enter the admin/admin login name and password required to connect to the repository.
Once you are connected to the repository, a node for the repository appears in the treeview pane
on the left.
3. In the treeview pane on the left, expand the nodes under the repository node until you see the node
that corresponds to the type of resource you are adding.
For example, if you are adding a configuration resource, expand the repository nodes until you see
the Configuration node. Click on the node to select it.
4. On the File menu, select Write File.
The Write File dialog box opens.
5. In the Write File dialog box, select the definition file of the resource you want to add to the repository,
then click the Open button.
The selected resource is added to the repository.
Reload the Service Configuration using JMX Console
12
Once you have modified a service configuration, you must reload the configuration in the repository using
the JMX Console. The JMX console allows you to reload and administer a service, without having to
restart the application container.
To reload the service configuration:
1. Access the JMX Console using the following URL: http://localhost:8080/jmx-console/
2. Under the Domain: EnterpriseMapping section, select the administration link for the service.
For example, EnterpriseMapping:name=Administration,type=WMS Service.
3. Click the Invoke button for the reloadConfiguration operation.
You will get a message on the status of the invocation.
MapInfo Spatial Server 1.0

Configuration File Parameters
The named WMS configuration file is pre-configured in the repository. See the following sections for
detailed descriptions of the configuration parameters and how to specify layers accessed by the WMS:
Service Parameters
The service parameters define the base WMS configuration.
Parameter
Title
Abstract
OnlineResource
ResourceRoot
DisableGetFeature-
Info
MIMETypes
Description
Human-readable name for your WMS service. Edit the Title to add your WMS
name.
Descriptive introduction to your WMS service. Edit the Abstract to describe what
type of features or content your WMS service provides.
Top level HTTP URL for your WMS Service. Edit the OnlineResource hostname
and port number with your services WMS top level URL.
Defines the location of your local repository where resources are stored that are
accessed by the WMS service. Edit the ResourceRoot hostname and port number
to match your WMS service container. This URL should point to the Repository
Service rmi.
Determines if the GetFeatureInfo operation is enabled. Default is set to false. If
you would like to disable the GetFeatureInfo operation for the service set this
parameter to true.
List of supported image MIME types the user can use to return maps.
PBBI WMS Server
Provides WMS-compliant services.
http://localhost:8080/WMSService/WMS
false
image/gif
image/jpg
image/jpeg
image/png
image/tiff
http://localhost:8080/RepositoryService/rmi
MapInfo Spatial Server Web Map Service
Chapter 2: Managing WMS Resources and Configuration
13

Defining a WMSLayer
Defining a WMSLayer
14
Since you can have multiple configurations, the layer list and layer tree has been separated to allow for
configuration merging. The WMSLayerList has the list of all available layers that can be provided by the
service.
The WMSLayer parameters define the individual layer configurations.
Parameter
Name
Title
Abstract
Queryable
KeywordList
SRSList
NamedResourceList
NamedStyleList
LatLonBounding-
Box
Description
Example of how to define a layer:
The name of your Layer. This is the name of your named layer. The name specified
in the Name element is the name used in the Title element when defining the
WMSLayerTree.
Human-readable name for your layer. Edit the Title to add your layer name.
Descriptive introduction to your layer. Edit the Abstract to describe what type of
features or content the layer provides.
Boolean that indicates whether the server supports the GetFeatureInfo operation
on that Layer.
Contains elements to aid in catalog searches.
List of the Spatial Reference Systems used by the layer.
The absolute path of the NamedLayer within the repository root. All ResourcePaths
must start with a slash (/) character.
List of available styles for this layer. Any number of styles may be defined for a
Layer. Each style must have a Name, Title, and ResourcePath element. The ResourcePath
is the absolute path of the NamedStyle within the repository root. All
ResourcePaths must start with a slash (/) character.
Describes the bounding box for the Layer. The information specified for the
LatLonBoundingBox will be returned in a GetFeatureInfo request.
World
World
The entire world base map
World
true
EPSG:4326
/NamedLayers/LayerWithTable
PointStylePin
PointStylePin
MapInfo Spatial Server 1.0

NamedStyles/PointStylePin
-180, -90, 180, 90
Once you have defined your Layers, the WMSLayerTree defines both what layers the server's GetCapabilities
response will contain, and what layers can be used by the service. By doing this, it allows for a
central default configuration to be defined for all layers, and then for a specific instance of the server,
these default layers can be exposed or hidden using the WMSLayerTree, or existing layers can be redefined,
or new layer definitions can be added.
Creating a WMSLayerTree
The WMSLayerTree defines the layers that are exposed through the WMS and also defines the structure
of how these layers are organized. Only the layers defined in the WMSLayerTree are returned in a
GetCapabilites response, and can be defined and returned in a GetMap or GetFeatureInfo query.
WMSLayerTree Rules
The following rules apply when creating a WMSLayerTree:
• The Title element of the layer defined in the WMSLayerTree must match the Name element defined
in the WMSLayerList.
• Each Title element must be wrapped in a WMSLayerTree element.
• Each WMSLayerTree element can contain one or more WMSLayerTree elements.
• There can be only one WMSLayerTree at the root. That root layer can have any number of children,
as can any of those children.
• If more than one root WMSLayerTree is defined in a configuration file, only the first WMSLayerTree
will be exposed through the service.
• If multiple configuration files have WMSLayerTrees defined, the last configuration file listed in the
beans.xml file that has a WMSLayerTree will be the one exposed through the service.
In the following example, the World layer contains the North America layer. The North America layer
contains both the Canada and United States layers.
World
North America
Canada
United States
MapInfo Spatial Server Web Map Service
Chapter 2: Managing WMS Resources and Configuration
15

Accessing the Web Map Service From Within MapInfo Professional
Accessing the Web Map Service From Within
MapInfo Professional
You can access the MapInfo Spatial Server Web Map Service from within MapInfo Professional. For
more information, refer to the topic entitled Enhancing Map Data Using a Web Map Service in the MapInfo
Professional online help.
Adding a WMS Server in MapInfo Professional
16
Before you can access a WMS server, you must first add it to the list of available servers.
To add a WMS server:
1. On the Options menu, select Preferences > Web Services.
2. In the Web Services Preferences dialog box, select the WMS tab.
3. Click Servers to open the WMS Servers List dialog box.
4. Click Add to open the WMS Server Information dialog box.
In the WMS Server Information dialog box you can add the new web server address and description
in the fields provided.
5. Enter the WMS server's URL in the Server URL field.
Click Test URL to ensure that MapInfo Professional can locate the server.
Click Get Description to get the server-provided description, or enter your own description.
6. If you know that the connect times, send times, or receive times for this server are particularly long
or unusually short, you may want to override the default values for this server.
To establish specific overrides for this server, select the Override Default Values check box and
enter new values, as appropriate, in the following fields:
Field
Connect Timeout
Send Timeout
Receive Timeout
Description
Indicates the amount of time (in seconds) allowed to establish an Internet
connection request to a Web Map server. If the request takes longer than
this value, a timeout occurs. The default connect timeout is 60 seconds.
Indicates the amount of time (in seconds) allowed to send an Internet request
to a Web Map server. If the request takes longer than this value, a timeout
occurs. The default send timeout is 60 seconds.
Indicates the amount of time (in seconds) allowed to begin to receive a response
from a request from a Web Map server. The download can take longer
than the timeout, but the response has to occur within the timeout setting.
The default receive timeout is 300 seconds.
7. If you want to limit the amount of time it takes to retrieve a map or if your map does not require a
great deal of detail, you may want to override the standard number of pixels that are retrieved.
MapInfo Spatial Server 1.0

To establish specific GetMap Pixel limits, select the Override Default Values check box and enter
new values, as appropriate, in the following fields:
Field
Max Width
Max Height
Description
Specifies the maximum number of pixels for a GetMap request in the
X direction.
Specifies the maximum number of pixels for a GetMap request in the
Y direction.
8. Click OK to save your server settings and close the WMS Server Information dialog box.
9. In the WMS Servers List dialog box, click Set Default to select a default server.
The default server will be selected the next time you open the Open WMS Table dialog box. When
you set a default WMS server, a check mark appears beside it. If you do not select a default server,
MapInfo Professional displays the first server in the list when you begin your WMS Server session.
MapInfo Spatial Server Web Map Service
Chapter 2: Managing WMS Resources and Configuration
17

Web Map Service
Capabilities
The MapInfo Spatial Server Web Map Service supports three capabilities which
are described in detail in this section.
In accordance with the Open GIS Consortium's Web Map Service Implementation
Specification, the MapInfo Spatial Server WMS provides the following operations:
GetCapabilities – This capability retrieves service-level metadata including the
server name, the layer names, abstracts about the data, and the valid request
parameters.
GetMap – This capability is used to request a map image using well-defined
geospatial and dimensional parameters containing layers, styles, boundaries,
and the spatial reference system (coordinate system of the data being retrieved).
You can also specify the image format (JPEG, GIF, PNG, and others) and styles.
GetFeatureInfo – This capability is used to request information for a feature at
a given point on the map after a GetMap has been called.
All of these request types are case-sensitive.
In this section:
• Getting Service-level Metadata About a WMS . . . . . . . . .20
• Getting Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
• Getting Information About Map Features . . . . . . . . . . . . .25
3

Getting Service-level Metadata About a WMS
Getting Service-level Metadata About a WMS
Before obtaining a map from a WMS server, it is important to determine the names of available layers,
their contents, their SRS (spatial reference system, or coordinate system) settings, and other information
about the data. Use the GetCapabilities request to obtain this information from a server.
The GetCapabilities request returns service-level metadata in XML format. This metadata is a description
of the information content and valid request parameters of the service.
Inputs and Behaviors
The following table lists the possible request inputs:
Input
Output
20
VERSION=version
SERVICE=WMS
REQUEST=GetCapabilities
Required
No
Yes
Yes
Description
Request version. Currently versions 1.1.1 and 1.3.0 are supported.
Service type. The SERVICE attribute is always set to WMS.
Request name
The request parameters are always sent as an HTTP query string. The following is a sample GetCapabilities
request:
http://localhost:8080/rest/EnterpriseMapping/WMS?VERSION=1.3.0&SERVICE=WMS&RE-
QUEST=GetCapabilities
After a successful GetCapabilities request, the service returns a GetCapabilities response which is a
descriptive XML file. The GetCapabilities.xml file contains the information on the services metadata,
capabilities, and layers.
General Service Metadata
The first part of a GetCapabilities response contains the name of the Web service (always OGC:WMS),
the title of the Web service, and the URL of the service.
Note:
The Name is usually a single word read by a machine, while the Title is designed to be humanreadable.
The following code illustrates an example of this section:
MapInfo Spatial Server 1.0

OGC:WMS
Pitney Bowes Software Inc. Web Map Server
Capabilities
This section names the actual operations that are supported by the service, the output formats offered
by these operations, and the URL prefix for each operation. For most WMS services this section has
three parts, one for GetCapabilities, one for GetMap, and one for GetFeatureInfo. The following example
illustrates the GetMap section:
image/gif
image/jpeg
image/jpg
image/png
Layers
Within the Capabilities is a Layer element for each map that can be provided by the service. WMS also
allows layers to be made up of layers so some nesting of layers can also be seen in these elements.
Each Layer element includes the following:
• Title – a name of the layer that is readable by the user.
• Name – a name of the layer that is used to reference the layer in requests.
• Style – a predefined style that can be used with this particular layer.
• SRS – the spatial reference system(s) that applies to this layer. If more than one SRS can be used
on the layer, each one can be listed.
• LatLonBoundingBox – a set of attributes that state the minimum bounding rectangle of the map data
in the default coordinate system (EPSG:4326). These numbers are expressed in decimal degrees
These values are important when making a GetMap request, as that request requires the correct values
that are specific to each individual Web Map service.
MapInfo Spatial Server Web Map Service
Chapter 3: Web Map Service Capabilities
21

Output
22
When layers are nested, the values set for a parent layer cascade down to subsidiary elements unless
specifically set differently in the child layers. The example below shows portions of the layer element to
illustrate the different settings.
Pitney Bowes MapInfo Web Map Server
BigRedStar
BigRedStar
POITextStyle
POITextStyle
PositionStyle
PositionStyle
RouteEndPointStyle
RouteEndPointStyle
FeatureLayers
EPSG:4201
EPSG:4205
...
PUBLIC
uscity
US Cities
WorldCountries
WorldCountries
...
MapInfo Spatial Server 1.0

Getting Maps
The primary reason to use or establish a Web Map Server is to obtain or serve maps. Use the GetMap
request to obtain images from a WMS server. GetMap requests are always sent as HTTP strings and
the response is a map image with well-defined geospatial and dimensional parameters in the image
format specified in the request.
Inputs and Behaviors
When invoking GetMap a WMS query can specify:
Input
VERSION=version
SERVICE=WMS
REQUEST=GetMap
LAYERS=layer_list
STYLES=style_list
SRS=namespace:identifier
CRS=namespace:identifier
Required
Yes
Yes
Yes
Yes
Yes
Yes for
1.1.1
Yes for
1.3.0
MapInfo Spatial Server Web Map Service
Description
Request version. MapInfo Spatial Server WMS supports both
version 1.1.1 and 1.3.0 of the OGC specification.
Service type. This is always WMS.
Request name. For a GetMap request this is always GetMap.
The layer or layers to be included in the map image. Each
layer should be separated by a comma. For example:
LAYERS=Layer1,Layer2,Layer3
Comma-separated list of one rendering style per requested
layer. A style is required for each layer requested. If no style
is requested, the attribute must be present but without a value.
If requesting multiple layers, the styles listed should be in the
same order as the layers. For example:
STYLES=Style1,,Style3
Chapter 3: Web Map Service Capabilities
In the above example the second style (for the second layer
requested) is left blank, allowing the default style defined for
the layer to be used.
The spatial reference system used in the map (numeric representation
of the projection of the map, also known as the
coordinate reference system). This parameter is only used
for 1.1.1 versions of the OGC specification. If this is not specified,
the default spatial reference system, as defined in the
default style of the layer, is used.
The coordinate reference system used in the map (numeric
representation of the projection of the map, also known as
the spatial reference system). This parameter is only used
for 1.1.1 versions of the OGC specification. If this is not specified,
the default coordinate reference system, as defined in
the default style of the layer, is used.
23

Sample Response
Input
BBOX=minx,miny,maxx,maxy
WIDTH=output_width
HEIGHT=output_height
FORMAT=output_format
TRANSPARENT=TRUE|FALSE
BGCOLOR=color_value
EXCEPTIONS=exception_format
Required
Yes
Yes
Yes
Yes
No
No
No
Description
The area to be mapped. the bounding box is specified as the
four coordinates of the corners of the box that bounds the
map area to be included in the image. The BBOX coordinates
are always expressed in the units of the SRS.
Width in pixels of map picture.
Height in pixels of map picture.
The format in which the map image is to be returned.
The transparency and color of the background of the image.
If nothing is specified, the value is FALSE.
Hexadecimal red-green-blue color value for the background
color (default=0xFFFFFF).
The format in which exceptions are to be reported by the
WMS (default=SE_XML).
The request parameters are always sent as an HTTP query string. The following are sample GetMap
requests:
WMS version 1.3:
http://localhost:8080/rest/EnterpriseMapping/WMS?VERSION=1.3.0&SERVICE=WMS&RE-
QUEST=GetMap
&CRS=EPSG:4326&BBOX=-100,0,90,100&WIDTH=400&HEIGHT=300&Layers=World&STYLES=AreaStyle
&FORMAT=image/png
WMS version 1.1.1:
http://localhost:8080/rest/EnterpriseMapping/WMS?VERSION=1.1.1&SERVICE=WMS&RE-
QUEST=GetMap
&SRS=EPSG:4326&BBOX=-100,0,90,100&WIDTH=400&HEIGHT=300&Layers=World&STYLES=AreaStyle
&FORMAT=image/png
Note:
Sample Response
24
The code above should all be on a single line with no breaks. Due to space limitations, we cannot
display the request in such a way in this document.
After a successful GetMap request, the service returns a GetMap response that is an image of the map
specified by the parameters in the request. The following is the response to the above request:
MapInfo Spatial Server 1.0

Getting Information About Map Features
Once a GetMap request has been successfully completed the user may want further information about
the features included in the map. Use the GetFeatureInfo request to get this further information from a
server. A GetFeatureInfo request returns information regarding the layers in the map and the queryable
attributes of each layer. This operation is optional. If GetFeatureInfo is employed, it must be issued after
a GetMap request is sent, as the X/Y pixel coordinate of a point on that map is a required input of a
GetFeatureInfo request. Refer to the Web Mapping Service OGC Specification for more information
about this capability (http://www.opengeospatial.org/standards/).
Inputs and Behaviors
The following table lists the possible GetFeatureInfo request inputs.
Input
VERSION=version
REQUEST=GetFeatureInfo
QUERY_LAYERS=layer_list
Required
Yes
Yes
Yes
Yes
MapInfo Spatial Server Web Map Service
Description
Chapter 3: Web Map Service Capabilities
Request version. MapInfo Spatial Server WMS supports both
version 1.1.1 and 1.3.0 of the OGC specification.
Request name. For a GetFeatureInfo request this is always
GetFeatureInfo.
Partial copy of the GetMap request parameters that generated
the map for which information is desired. The spatial reference
system, bounding box, width, height, and layers of the GetMap
request are required parameters. See the sample request
below.
Comma-separated list of one or more layers to be queried.
You do not need to include every layer included in the initial
GetMap request.
25

Output
Input
INFO_FORMAT=output_format
FEATURE_COUNT=number
X=pixel_column
Y=pixel_row
I=pixel_column
J=pixel_row
Required
No
No
Yes for
1.1.1
Yes for
1.1.1
Yes for
1.3.0
Yes for
1.3.0
Description
Return format of feature information (MIME type).
The maximum number of features about which to return information.
X-coordinate in pixels of feature (measured from the upper
left corner which is 0).This parameter is only used for 1.1.1
versions of the OGC specification.
Y-coordinate in pixels of feature (measured from the upper
left corner which is 0).This parameter is only used for 1.1.1
versions of the OGC specification.
I-coordinate in pixels of feature (measured from the upper left
corner which is 0).This parameter is only used for 1.3.0 versions
of the OGC specification.
J-coordinate in pixels of feature (measured from the upper
left corner which is 0).This parameter is only used for 1.3.0
versions of the OGC specification.
The request parameters are always sent as an HTTP query string. The following are sample GetFeature-
Info requests:
WMS version 1.3:
http://localhost:8080/rest/EnterpriseMapping/WMS/?VERSION=1.1.1&SERVICE=WMS&RE-
QUEST=GetFeatureInfo
&SRS=EPSG:4326&BBOX=-100,0,90,100&WIDTH=400&HEIGHT=300&LAYERS=World&QUERY_LAY-
ERS=World&X=1&Y=1
WMS version 1.1.1:
http://localhost:8080/rest/EnterpriseMapping/WMS/?VERSION=1.3.0&SERVICE=WMS&RE-
QUEST=GetFeatureInfo
&CRS=EPSG:4326&BBOX=-100,0,90,100&WIDTH=400&HEIGHT=300&LAYERS=World&QUERY_LAY-
ERS=World&I=1&J=1
Note:
Output
26
The code above should all be on a single line with no breaks. Due to space limitations, we cannot
display the request in such a way in this document.
After a successful GetFeatureInfo request, the service returns a GetFeatureInfo response. A GetFeature-
Info response is an XML file. The returned file includes information about the layers in the map, the
queryable attributes of those layers, and the bounding box and SRS information of the map.
MapInfo Spatial Server 1.0

Web Map Service
Fundamentals
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed,
collaborative, hypermedia information systems. The Web Map Service uses
HTTP for the transfer of information. Specifically two methods are used. They are
described in detail in this section.
In this section:
• WMS Server Technology . . . . . . . . . . . . . . . . . . . . . . . . . .28
• HTTP GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
• Basic Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
• Layers and Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
4

WMS Server Technology
WMS Server Technology
The WMS server functions using the HTTP GET method. For a full discussion of HTTP and its methods,
refer to the Internet Engineering Task Force HTTP specification (www.ietf.org).
HTTP GET
The GET method retrieves whatever information (in the form of an entity) is identified by the Request-
URI. If the Request-URI refers to a data-producing process, it is the produced data that is returned as
the entity in the response and not the source text of the process, unless that text happens to be the
output of the process.
For the Web Map Service, the GET method is used to retrieve entire images from whatever server is
being accessed.
Basic Authentication
28
Usually a Web Map Service is open to the general public and needs no authentication. From time to
time, a server may limit access to only authorized users. MapInfo Spatial Server allows you to access
WMS servers that use HTTP Basic Authentication. When defining a WMS layer, you can add a username
and password to your Connection URL. The format of the HTTP URL is:
wms:http://:@
For example:
wms:http://admin:admin@localhost:8008/rest/EnterpriseMapping/WMS?
If you do not want to include IDs or passwords in a WMS request query, you have the option to set authentication
in your client by including additional information in the HTTP header on the Web page. The
following is a sample HTTP header that includes basic authorization information:
GET /rest/EnterpriseMapping/WMS?SERVICE=WMS&REQUEST=GetCapabilities HTTP/1.1
Authorization: BASIC YWRtaW46aDdhU1ZEd2o3RVd5a1gzRUhNbW5Pdz09
User-Agent: Java/1.4.1
Host: 127.0.0.1:8080
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
MapInfo Spatial Server 1.0

Layers and Styles
The images rendered can be made of layers that are hierarchical—an image can be served that is made
up of a layer that is a collection of other layers. Since WMS renders layers, the characteristics that
modify the view of layers, such as styles and coordinate systems, can also be included in the layers
provided. This lets you customize images because each image can act as a separate layer within the
client that is accessing these images.
You can find out what map layers are available from a WMS server by submitting a GetCapabilities request
and examining the GetCapabilities.xml file returned in the response. (Refer to Getting Servicelevel
Metadata About a WMS on page 20 for more information.)
MapInfo Spatial Server Web Map Service
Chapter 4: Web Map Service Fundamentals
29