Digital Mapping for
Business & Government

Java Platform - Written in Java for platform independence.

Servlet Based - Handles concurrent routing requests and can be optimized for shortest time or distance with accompanying drive time estimates and distance traveled. Developers can also select a default setting or set the functionality as a user-defined parameter.

Configurable System Parameters - To simplify development, a sample configuration file is provided with the installation.

Routing Strings - Descriptions of calculated driving directions may also be customized by editing route and turn angle strings. For example, a negative turn angle of minus 171 to 180 degrees is described as 'make a sharp right.' If a different description is preferred, a developer may simply alter this string or the string describing any of the ten-degree increments in which turns are returned.

Data Security - Maintain complete control over sensitive, proprietary business data. As everything is maintained on your web site, you can make modifications quickly and easily with confidence in their accuracy.

XML API Interface - With Extensible Markup Language, the Routing J Server meets OGC standards.  The client can now communicate with the server in XML - no conversion needed.

Driving Analysis Tools - Extended API - For drive-time polygons: return the boundary of travel within X miles (isodistance) or X minutes (isochrone) of a given point. Multi-point routing: great for determining optimal route when dispatching drivers to multiple destinations.

Dynamic Data Access - With Routing J Server you can dynamically update routing network data. You can select a road segment and modify its attributes, or change speeds to match real world conditions.

Relative Route Chart - Displays routes using easy to follow caricatures. This option is included in a sample application which ships with the product.

Include/Exclude - The Routing J Server API has been extended to enable users to identify segments that should explicitly be part of a route or not part of a route. Users can identify those segments using a unique segment ID or X, Y coordinates. If the later are used, the engine will determine the closest segment to those coordinates and route accordingly. This feature is not yet available through the COM client.

Add Time As A Component - Specify a start time OR end time for the route (both cannot be specified), and a duration for each intermediate point in a MultiPoint route.

Choose Road Types - The user is given four levels of desirability - high, medium, low, avoid.

Focused Route Descriptions - Create a focused route, or a subset of the whole route that concentrates on either the beginning or end of the route. A route focused at the start will route the user from their origin to (and including) the first major highway. A route focused at the end will route the user from the last major highway in the route (including that highway) to the destination. This assumes user is familiar with much of the route and only needs assistance for part of it.

Terse Driving Directions - Tell the server to provide concise driving directions instead of just the standard directions. This is valuable for a wireless application where there is limited room for directions thus requiring shorter directions strings.

Multiple Mode Preference - Users may stipulate walking or driving directions. This feature is handled via the deployment of two instances of RJS, each utilizing its own transportation network.

Matrix Routing - Users may specify a block of routes to be calculated (n by n) with one call. Time and distance for each combination will be returned. No driving directions are included.

Architecture:
The MapInfo Routing J Server calculates routes and provides driving directions for applications built on MapXtreme^® Java and NT editions.  Communication between the MapInfo Routing J Server and MapInfo's Internet Mapping products such as MapXtreme^®, can be handled easily at the Application Server level. Any application that has the ability to speak with a Java object can speak with the Routing J Server and in-turn MapXtreme^® Java Edition or MapXtreme^® NT.

Servlets:

• Classic -This sample application assumes the user has MapMarker^® J Server as well as MapXtreme^® Java installed. It provides the ability to geocode an address and display the route, plus driving directions.
• Isochrone - Extends the Classic sample to demonstrate the generation of drive time polygons (isochrones).
• Multipoint - Extends the Classic sample to demonstrate the generation of multi-point routes.

• Include/Exclude - For those interested in developing routing 'applications' rather than 'servlets,' this sample demonstrates how to request regular routes, isochrones and multi-point routes as a Java application.

• RoutingAdmin - This is a sample administrative program that demonstrates the functionality available to control the server, retrieve statistics, change or view preferences and shutdown the server.
• TestXML - For those interested in accessing the routing engine directly via XML instead of via the Java or COM client, this sample demonstrates how routing functionality can be achieved.
• RoutingClientGUI – This sample application does not rely upon MapXtreme^® Java. The user may enter latitude/longitude coordinates and access the engine directly.

Data Updates:
To ensure the most up-to-date data and accurate route calculation, the Routing J Server utilizes GDT's Dynamap 2002 Transportation database for the U.S. and is updated quarterly. 

Tele Atlas' MultiNet navigational database is used for Europe and is updated on a twice yearly basis.