MapMarker USA v26
Release Notes
These Release Notes accompany the MapMarker USA v26 release. This provides information
on new features, behavioral changes in the software, fixes for customer-reported issues, and
known issues that may require your attention.
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.6080
pbinsight.com
Canada:
Phone: 416.594.5200
Fax: 416.594.5201
Sales: 800.268.3282
Technical Support:.518.285.7283
Technical Support Fax: 518.285.6080
pbinsight.ca
Europe/United Kingdom:
Phone: +44.1753.848.200
Fax: +44.1753.621.140
Technical Support: +44.1753.848.229
pbinsight.co.uk
Asia Pacific/Australia:
Phone: +61.2.9437.6255
Fax: +61.2.9439.1773
Technical Support: 1.800.648.899
pbinsight.com.au
© 2013 Pitney Bowes Software Inc. All
rights reserved. MapInfo, Group 1
Software, and MapMarker are
trademarks of Pitney Bowes Software
Inc. All other marks and trademarks are
property of their respective holders.
May 2013
These Release Notes are also available on the Pitney Bowes Software web site. Related
MapMarker documentation appears on the MapMarker Product Documentation page on the
Pitney Bowes Software web site. The USA v26 documentation appears under the USA heading.
Release Notes may be updated as new information becomes available. Any updated Release
Notes will be posted to the web site with an indication of the revision date.
In these release notes:
Š
Š
Š
Š
Š
MapMarker USA v26 Features and Enhancements . . . . . . . . . . . . 2
Operating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fixes to Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installation-Related Configuration and Tomcat Integration . . . . 12
Known Issues and Clarifications . . . . . . . . . . . . . . . . . . . . . . . . . 15
MapMarker USA v26 Features and Enhancements
Following is a summary of the updates that are you will see with the MapMarker USA v26 release. These features are
summarized here for convenience and are fully covered in the appropriate sections of the MapMarker USA v26 User
Guide and in the MapMarker USA v26 Developer Guide.
MapMarker USA v26 features are described in the following topics:
Š
Š
Š
Š
Š
Š
Š
Updated Dictionaries and New NAVTEQ Points Data
License Management Tool
Single Line Matching Improvements
Reverse Geocoding Enhancements
Improved Matching When a User Dictionary is Present
User Dictionary Builder No Longer Assumes Parity of Both When Odd/Even is Not Specified
Improved Diagnostics Capability
Updated Dictionaries and New NAVTEQ Points Data
By default, the TomTom® Streets address dictionary is installed as the primary address dictionary. Alternatively,
NAVTEQ NAVSTREETS can be installed as the primary address dictionary.
Starting with MapMarker USA v26, you can purchase and license NAVTEQ Points data. This is in addition to the
TomTom and Centrus Points data that were already available. See NAVTEQ Point Address Dictionary Details and
Licensing on page 3 for more information on the newly available NAVTEQ Points dataset.
To use a point-based address dictionary, you must have an accompanying street segment dictionary with the same
MapMarker product data vintage. MapMarker product vintages are referred to by the month name, such as:
MapMarker USA v26 2013 April (2013.04) data update. You can receive quarterly or monthly updates for any licensed
address dictionary (except TIGER). The vintage month corresponds to the month of the MapMarker release. The
underlying data vintages of the data providers may vary. See the table of Data Provider Vintages for
MapMarker USA v26.
The following Address Dictionaries are available for use with MapMarker USA v26 and can be used within the same
core engine.
•
•
•
•
•
•
TomTom® Street data. This primary address dictionary is installed by default.
NAVTEQ® Street data. If licensed, this can be used as a primary address dictionary. However, it must be installed
using the MapMarker Data Installer. See Installing MapMarker USA v26 with NAVTEQ Street Data
TomTom Points data. This is available as a supplemental address dictionary, and is installed using the MapMarker
Data Installer.
NAVTEQ Points data. This is a new data source and is available as a supplemental address dictionary. This is
installed using the MapMarker Data Installer.
Centrus® Points data. This is available as a supplemental address dictionary, and is installed using the MapMarker
Data Installer.
TIGER® data. TIGER data can be used as a primary address dictionary, but it does not provide the same features
and capabilities as offered with the other datasets. Also, TIGER data cannot be used in conjunction with any point
dataset.
The Centrus Points, TomTom Points, NAVSTREETS, and NAVTEQ Points address dictionaries can be installed in their
own data paths.
Data reports for each data vendor are provided as an Excel workbook and distributed on the data media and included
in your installation (and in data downloads). These reports provide detailed state and county statistics for the
point-based address dictionaries. The NavteqPoints.xls and comparable TomTompoints.xls and CentrusPoints.xls files
are installed in the <install>\MapMarker_USA_v26_Data folder.
MapMarker USA 26.0 Release Notes
2
Data shipped with MapMarker USA v26 is labelled with a common MapMarker product vintage date of 2013.04. The
underlying vendor-specific vintages for the data sources are as follows.
Data Provider Vintages for MapMarker USA v26
Data Vendor
Version
TomTom Streets (MultiNet)
2013.03
NAVTEQ® NAVSTREETS
2013Q1
TomTom Points (MultiNet)
2013.03
NAVTEQ Point Addresses
2013Q1
Centrus Points
Version 7.03
TIGER
2013.02
Depending on your license agreement, you can update data quarterly or monthly (except for TIGER). Beginning with
MapMarker USA v26, NAVSTREETS can be updated monthly. Previously it was available for quarterly update only.
See the Pitney Bowes Software web site for more detailed information on the U.S Geocoding Data Sets.
L
Since there are no changes to the MapMarker USA v26 data format, you can install the current version of data
without installing the updated software.
Contact your Sales Representative for more information on purchasing additional data sets and for establishing an
update schedule.
NAVTEQ Point Address Dictionary Details and Licensing
The newly available NAVTEQ point-based address dictionary gives you the ability to geocode to the highest level of
accuracy (S8 point geocode matches). NAVTEQ Points is licensed for all of United States, not by individual state. As
for any point address dictionary, NAVTEQ Points must be used in conjunction with a standard street address dictionary
of the same MapMarker product vintage.
The NAVTEQ Points address dictionary includes over 91.5 million points covering all 50 states and Washington, D.C. It
does not include point data for Puerto Rico, Virgin Islands, or other USA territories.
L
To use the NAVTEQ Points address dictionary, you must acquire a new license. See License Management
Tool on page 4 for instructions on using the license tool.
The NAVTEQ Points address dictionary is provided on separate media and is installed using the MapMarker Data
Installer. See the MapMarker Data Installer document for instructions on installing NAVTEQ Points and other
supplemental datasets.
MapMarker USA 26.0 Release Notes
3
License Management Tool
The key-based license management system was introduced with MapMarker USA v25. Each license file will be
associated with a System ID. Your Sales Representative should provide you with valid license files before you receive
your software media.
Note that reverse geocoding also requires a separate license. See Reverse Geocoding Enhancements on page 7.
L
If your existing MapMarker USA v25 license has not expired and is still contractually valid, you can use your
license for the v26 upgrade. However, if you changed hardware or are licensing different data (such as
NAVTEQ Points), you must acquire a new v26 license file.
If your Sales Representative provided you with a temporary license, you will need to acquire a permanent one. Pitney
Bowes Software provides the command line License Assistant utility (LicAssist.exe) that enables you to generate a file
request for a permanent license.
L
Temporary licenses are good for 30 days. When you do get a permanent license, replace your temporary
license and restart the application in order to activate the new license. If you fail to do so, the software will stop
working when the temporary license expires.
Your media includes both the License Assistant utility (LicAssist.exe) and a LicAssist.txt file that explains how to run
the License Assistant utility. These files are located in the following locations:
License Assistant Utility Location
Platform
File Name and Description
Location
Windows
LicAssist.exe – license assistant utility <root>\licassist\windows\ directory on the software
installation media.
licassist.txt – instructions for running
License Assistant utility
UNIX
licassist – license assistant utility.
licassist.txt – instructions for running
License Assistant utility
<root>/licassist/platform/ directory on the software
installation media, where platform identifies your
UNIX platform. For Solaris platform, the locations
are: <root>/licassist/Solaris/2.9/ and
<root>/licassist/2.10/.
Starting with With MapMarker USA v25.1, the License Assistant utility was improved to enhance usability and facilitate
the transfer of license files between you and the Pitney Bowes Software Customer Service group. The licassist utility
generates a simple .txt file that you can e-mail to Pitney Bowes Software without the need to zip the file. After you
e-mail this file to Pitney Bowes Software Customer Service, you will receive return e-mail with the permanent license
file (.lic file) specific to your machine.
L
The software key implementation does not replace other licensing schemes. Product feature licensing, data
licensing and expiration, CASS, DPV, and LACSLink licensing are not affected by this license management
system.
Running the License Assistant Utility
If you need to run the License Assistant, copy the LicAssist.exe (or licassist for UNIX platforms) from the media to a
writable area on your local machine, for example to your Desktop folder or the root of your C:\ directory for a Windows
platform.
For Windows, navigate to where you copied LicAssist.exe on your local machine. Double-click to launch it.
MapMarker USA 26.0 Release Notes
4
For UNIX systems, open a prompt and navigate to the directory where you copied licassist. Grant execute permissions
to the licassist.exe file, then run the utility.
$ ./licassist
When you run the licassist utility, it generates a license request file (system.MACHINENAME.txt file). E-mail this txt file
to Pitney Bowes Software Customer Service. There is no need to zip the file (as was previously required). In return
e-mail, you will the receive the permanent license file (.lic file) specific to your machine.
When you run the licassist utility, Pitney Bowes Software also collects the following information:
•
•
•
•
•
System Id: machine/host id or MAC address depending on the OS
MAC address
CPU count
Hostname
Machine Info: String describing the OS, such as "Microsoft Windows XP Professional Service Pack 3 (build 2600)"
Your MapMarker USA v26 license file will be named as follows
•
mmusa_<MACHINENAME>.lic
After receiving the permanent license file, you must replace your temporary license. For more specific instructions on
replacing your temporary or expiring license, see Activating a New Permanent License on page 15.
If you are doing a shared Desktop application installation (Windows platform only), each client machine server must
have its own MapMarker license file. See Shared installation – Accessing and Running Client Desktop Installer
on page 17 for more information.
After receiving the permanent license file, you must replace your temporary license. For more specific instructions on
replacing your temporary or expiring license, see Activating a New Permanent License on page 15.
If you do not have a valid v26 license file, the MapMarker Desktop application displays an appropriate error message
when you attempt to install or start the application. See the topic "Troubleshooting License File Errors" in the Installing
MapMarker chapter of the MapMarker USA User Guide for detailed information on the possible error messages.
Single Line Matching Improvements
There are several improvements to matching of single line addresses. The examples represent some single line cases
that previously were not handled correctly, but are now matched as expected.
Better handling of ambiguous street types, street names, city names, and state
Several examples are illustrated below.
In the following single input address, the W could indicate either a street directional or the city of West Newton:
11 Elsworth Rd W Newton MA 02165-1122
The street address 11 Elsworth Rd occurs only in the city of Newton (not West Newton). MapMarker USA v26
recognizes this and returns the close match candidate.
11 ELSWORTH RD.
NEWTON, MA 02465-1122
In the following single line input example, the sequence of South North is ambiguous and the city of North Bloomfield is
not the correct city.
100 Petaluma Blvd South North Bloomfield CA
MapMarker USA v26 recognizes that the correct city is Petaluma and returns the close match candidate.
100 PETALUMA BLVD S
PETALUMA, CA 94952
MapMarker USA 26.0 Release Notes
5
The following single line input address includes an extraneous word and a misspelling of Boulder.
4750 Walnut St WhereIs Zoulder CO 80301
MapMarker USA v26 discards the extraneous word (WhereIs), uses other address elements (ZIP Code) to
determine the correct city name, and returns the close match candidate.
4750 WALNUT ST
BOULDER, CO 80301
In the following single line input address, Warren Heights is the wrong town name.
21122 Aurora Rd Warren Heights OH 44146
MapMarker USA v26 recognizes the correct town name and returns the close match candidate.
21122 AURORA RD
BEDFORD OH
44146-1012
Better handling of ambiguous white space or separators between address elements
In the following single line input address, an unnecessary dash is inserted between the house number and street.
6900-38TH Ave N St Petersburg FL 33710
MapMarker USA v26 eliminates the unnecessary dash, recognizes N as a street directional, and returns the close
match.
6900 38TH AVE N
ST PETERSBURG, FL, 33710-1450
Similarly, other superfluous separators or white space are better interpreted in single line input.
Lastline elements can occur in various combinations and orders
A single line address can include lastline elements formatted in a variety of ways MapMarker USA v26 recognizes
lastline elements in different combinations and orders and returns the close match candidate.
Following are examples of lastline address elements in a variety of formats, all of which will return the correct Boulder,
CO 80301 as part of the candidate.
Boulder CO 80301
Boulder 80301 CO
80301 CO
CO Boulder 80301
CO 80301 Boulder
CO 80301
80301 Boulder
80301 CO
80301
For example, the following single line input address has the ZIP Code is placed before the city rather than the usual
format of ZIP Code as the last element.
4750 Walnut St Boulder 80301 CO
MapMarker USA v26 recognizes the lastline elements and returns the close match candidate.
4750 WALNUT ST
BOULDER CO
80301-2532
MapMarker USA 26.0 Release Notes
6
Reverse Geocoding Enhancements
The MapMarker USA v26 Server improves the configuration, management, and matching of reverse geocoding.
L
Reverse geocoding is available with the Developer (Server) edition only. Reverse geocoding is not
implemented in the Desktop application and is not available with User Dictionaries. Reverse geocoding is also
separately licensed and must be covered in your license agreement.
The ReverseGeocodeAPI interface includes classes and methods that support reverse geocoding. See the Developer
Guide for relevant information on reverse geocoding. The Javadocs includes complete coverage of the reverse
geocoding classes and methods.
Support and configuration for reverse geocoding
Previously, it was necessary to produce a spatial index (gsx files) for the combination of address dictionaries that you
wanted to use for reverse geocoding. This procedure generated a large number of files, and it could potentially take a
long time to generate the files using the batchind program provided with MapMarker USA v25. Also, you had to create
unique gsx folders and files for each combination of address dictionaries that you wanted to configure for reverse
geocoding.
MapMarker USA v26 greatly simplifies reverse geocoding support. MapMarker USA v26 automatically installs two gsx
files for each address dictionary. No special user action is needed to configure reverse geocoding if you are using
MapMarker USA v26 with new data.
L
Because MapMarker USA v26 automatically installs the required gsx files to support reverse geocoding, v26
does not include the batchind utility.
However, new data (and the new gsx file format) is not compatible with old software. If you want to perform reverse
geocoding using new data without upgrading the software, you must create custom, multiple gsx files. In that scenario,
you should also discard the new gsx files that are automatically installed with MapMarker USA v26. See Building
spatial index files with the batchind utility.
Similarly you cannot perform reverse geocoding using old data and new MapMarker USA v26 software.
Building spatial index files with the batchind utility
If you are using MapMarker USA v26 and new data, no additional user actions are needed to support reverse
geocoding on the server. You can therefore ignore this topic.
However, if you upgrade to MapMarker USA v26 data but still want to reverse geocode using older software, you must
create custom, multiple gsx files using your old (MapMarker USA v25) batchind utility. In your MapMarker USA v25
installation, the batchind utility was installed in <install>\sdk\additional_tools\batchind folder. The specific name of the
batchind utility varies slightly for Windows or non-Windows platforms.
Building all the index files takes anywhere from several minutes to several hours, depending on the machine you use
to make the files. If you machine is slow, you may wish to run batchind.exe overnight. The generated GSX files takes
up several hundred megabytes of hard drive space.
Using command line arguments with batchind:
The v25 batchind utility creates a gsx folder and files based on the address dictionaries specified in the searchPath. If
you attempt to reverse geocode using different data dictionaries than were specified with batchind, reverse geocoding
will fail. You must create and use a unique gsx folder and files for each combination of address dictionaries that you
use.
MapMarker USA 26.0 Release Notes
7
You can open a command prompt and run the batchind utility from where it was installed. On UNIX platforms, you must
grant execute permissions to the batchind file before running. Specify your searchPath and outputDir and run batchind
as follows:
batchind <searchPath> <outputDir>
Batchind Syntax
Input
Description
searchPath
The full datapath. That is, the path where the us.gsd and ust.gsd files reside. The Finmbr.dat file
associated with the address dictionary must also be present in this folder. Delimit multiple search
paths with a semi-colon (;). For non-Windows platforms, use a colon (:) as a path delimiter.
outputDir
The full output path (including the gsx folder) where the gsx files will be created. By default, this is
the searchPath/gsx folder.
A space delimits searchPath from outputDir. When running batchind from the command line, you can enclose
searchPath and outputDir in quotes so that a space is not misinterpreted as a delimiter between the paths.
The v25 batchind utility creates a gsx folder and files based on the address dictionaries specified in the searchPath. If
you attempt to reverse geocode using different data dictionaries than were specified with batchind, reverse geocoding
will fail. You must create and use a unique gsx folder and files for each combination of address dictionaries that you
use.
For example, assume that your TomTom Data folder includes the Finmbr file and you have a separate folder for
TomTom Points (TPoints) data. From the <<install>\sdk\additional_tools\batchind folder, run batchind from the
command line as follows:
c:\Program Files\MapInfo\MapMarker_USA_v26\sdk\additional_tools\batchind> batchind
"c:\Program Files\MapInfo\MapMarker_USA_v26\MapMarker_USA_v26_Data\TomTom ";"c:\Program Files\
MapInfo\MapMarker_USA_v26\MapMarker_USA_v26_Data\TPoints" c:\Program Files\
MapInfo\MapMarker_USA_v26\MapMarker_USA_v26_Data\gsx
This creates the gsx files based on the TomTom streets and TomTom Points address dictionaries. the gsx folder is
created if it did not already exist.
If you copy and run batchind from the data folder (for example from: C:\Program Files\MapInfo\
MapMarker_USA_v25\MapMarker_USA_v25_Data, you can simplify the syntax as:
batchind ./ ./gsx
After building the custom gsx files, you should discard the new gsx files that are automatically installed with
MapMarker USA v26.
Using an INI file with batchind:
You can create a batchind.ini file in the directory from which you run batchind. The batchind.ini file should have two
entries to specify the searchPath and outputDir. The searchPath and outputDir are described in Batchind Syntax.
searchPath=<datapath>
outputDir=<output path>
Do not use quotes for INI file search paths.
When you run the batchind executable, it will look for and use the batchind.ini file in the same directory as the
executable. On UNIX platforms, remember to grant execute permissions to the batchind file before running.
A sample file named batchind.txt is installed in the batchind folder. During installation, this sample file is populated with
your searchPath (based on the location of your data) and the outputDir (searchPath/gsx). You can use this sample
batchind.txt file as a model for a batchind.ini file.
MapMarker USA 26.0 Release Notes
8
Improved reverse geocoding results
Reverse geocoded candidates now include the exact latitude / longitude coordinates of the candidate. Along with this,
reverse geocoded candidates also indicate the coordinate system (EPSG code) and the location precision value (a
numeric value of 1, 2, or 16).
See the MapMarker USA v26 Developer Guide for relevant information on reverse geocoding.
Improved Matching When a User Dictionary is Present
Previously, the presence of any user dictionary caused matching problems when abbreviations occurred in input street
names. For example, an input address of 3505 Mount Diablo Blvd matched as expected, but 3505 Mt Diablo Blvd
failed to match because of the "Mt" abbreviation. This could happen if any user dictionary was in the dictionary
searchpath, even if the potential close match candidate was in an address dictionary. Note that this problem did not
occur if CASS mode was used.
Resolution of this issue has produced significant matching improvement when user dictionaries are present. In
particular, abbreviations in street names and street name aliases are now handled better and a number of matching
improvements have been demonstrated with MapMarker USA v26.
User Dictionary Builder No Longer Assumes Parity of Both When Odd/Even is Not Specified
Previously, if you did not specify parity when building a user dictionary, a parity of Both was assumed. Consider an
example in which the left range in the source is 1 – 11, the right range is 2-12, and no parity was specified. Previously,
the User Dictionary builder would have been assigned parity Both. With MapMarker USA v26 the left will be assigned
as Odd and the right will be assigned as Even.
If you built an existing User Dictionary without specifying Odd/Even indicators, you could take advantage of this
improvement by rebuilding existing segment user dictionaries with the new User Dictionary utility.
Improved Diagnostics Capability
Enhancements for more efficient and effective collaboration between Pitney Bowes Software customers and technical
support.
Operating Requirements
This section describes the hardware, memory and other requirements for MapMarker USA v26.
Hardware and Memory Requirements
The minimum system requirements for MapMarker on a full installation of the Desktop Application and MapMarker
SDK are:
•
•
•
Dual Core processor or better
4 GB RAM
10 GB available disk space
MapMarker USA 26.0 Release Notes
9
For optimal performance we recommend more processing power. Many factors can affect performance, including
network speed, hardware, number of concurrent users, number of address/user dictionaries, geocoding preferences,
and quality of input addresses.
Supported Operating Systems
MapMarker USA runs on both 32-bit and 64-bit operating systems. The 32-bit versions will run on any supported 64-bit
machine.
To run as a true 64-bit application, you must use the appropriate Geostan 64-binary file. These binaries are installed
with your software. For information on how to configure MapMarker USA for 64-bit systems, see Running on 64-bit
Operating Systems on page 12.
MapMarker runs on the following operating systems:
•
•
•
•
•
•
•
•
Microsoft Windows XP Professional (32 and 64 bit)
Microsoft Windows 2003 Enterprise Edition (32 bit)
Microsoft Windows 2008 Server (32 and 64 bit)
Microsoft Windows 7 (64 bit)
Solaris 2.9 and 2.10
HP-UX 11x 32 (64 bit only)
Red Hat Linux 4.0 and 5.0 (64 bit only)
SUSE Linux 10.0 and 11.0 (64 bit only)
Desktop Application
The Desktop Application runs on Microsoft Windows only. The Desktop is a 32-bit application, but runs on 64-bit
Windows providing that 32-bit binaries are used. This works by default, because the installer always configures 32-bit
binaries.
•
•
•
•
Microsoft Windows XP Professional (32 and 64-bit)
Microsoft Windows 2003 Enterprise Edition (32 bit)
Microsoft Windows 2008 Server (32 bit and 64 bit)
Microsoft Windows 7 (64-bit)
JVM Requirements
MapMarker v26 requires a Java Virtual Machine (JVM) 1.5 or higher. MapMarker USA v26 ships with:
•
JVM 1.6
During the installation, you will have the option of installing the JVM that ships with MapMarker or using one that you
already have installed on your computer.
For performance reasons, we recommend using the JVM 1.6 that is shipped with your product. However, JVM 1.5 is
still supported. If you choose a JVM 1.5, you will receive a warning message when the installation completes, but you
can ignore this message.
L
Note that if you install a 64-bit version of MapMarker USA v26 you must also use a 64-bit JVM.
Database Support
MapMarker USA v26 supports the following ODBC databases and drivers.
•
•
•
•
SQL Server 2008
SQL Server 2005
SQL Server 2000 (This will not be supported in future releases.)
Microsoft Access 2010
MapMarker USA 26.0 Release Notes
10
•
•
•
Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007)
Microsoft Access 2003 (This will not be supported in future releases.)
Microsoft Access 2000 (This will not be supported in future releases.)
L
Note that SQL Server 2000, Microsoft Access 2000, and Microsoft Access 2003 will not be supported in future
releases.
MapMarker also supports the following Oracle drivers.
•
•
Oracle 11
Oracle 10G Release 2
You must install the Oracle driver separately. To use the driver, you must have the Oracle client installed.
Supported Web Application Servers
The MapMarker server allows you to develop geocoding applications on any Java Platform, Enterprise Edition
(Java EE) application server that supports JVM 1.5 or JVM 1.6.
MapMarker USA v26 ships with:
•
Apache Tomcat 6.0
Tomcat 5.5 is still supported.
System Library Dependencies for UNIX Installations
On UNIX/Linux systems, MapMarker USA requires standard system libraries that are used by the geocoding engine.
While these standard libraries are available with every UNIX platform, they may not be found unless you install with the
appropriate system option.
To determine which system libraries are needed on your UNIX system, run the ldd (list dynamic dependencies)
command, which will print shared library dependencies. For example, to identify the library dependencies for
MapMarker USA v26 (which uses the 26.00 engine), run:
ldd <install_dir>/sdk/engine/bin/geostanMT.so
This will return the MapMarker library dependencies for your UNIX system (Linux, Solaris, or HPUX). If you install the
v26.1 update, the underlying geocoding engine is also updated (for example to 26.01.)
Supported Pitney Bowes Software Products
MapMarker USA v26 can integrate with the following products:
•
Other MapMarker country products (Canada, Australia, etc.)
•
MapInfo Professional®
•
MapInfo AnySite®
•
MapMarker® Geocoding Extender for Oracle
•
MapMarker® Geocoding Extender for SQL Server
•
MapXtreme® .NET version
MapMarker USA 26.0 Release Notes
11
Fixes to Known Issues
The following incidents were addressed in MapMarker USA v26.
Desktop application crashes when geocoding a large table in CASS Mode Under some circumstances,
geocoding a large table (10,000 or more records) in CASS Mode causes the Desktop application to crash. This has
been fixed with more recent DPV/LACSLink data.
User dictionary can return unexpected city name Sometimes different city names are associated with the postal
data and the street segment data for the same address. Previously, MapMarker USA returned the city name
associated with the postal data source. With MapMarker USA v26, the city name associated with the street segment
record is returned. This is more likely to be the correct and expected city name.
Segment user dictionary can return incomplete Census information Candidates from a segment user dictionary
sometimes return state and FIPS code information associated with the ZIP Code rather than the complete Census
Block information. Therefore, the last 10 digits of the Census Field return as zeroes. MapMarker USA v26 fixes this
issue, so that all candidates from segment user dictionaries now return complete 15-digit Census information. This
issue had been resolved for point (but not segment) user dictionaries with MapMarker USA v25.1.
Result code fails to indicate exact street name match Under some circumstances, a close match result code
indicates a mismatch on street name even though an exact street name match was made. For example, the input
address of 5929 W 4500N Rd Kankakee, IL 60901returns a result code of S5HP-TSCZ, with the dash indicating that
street name was not matched. This has been fixed and the correct S5HPNTSCZ result code is consistently returned
for exact matches.
Installation-Related Configuration and Tomcat Integration
This section provides some additional information regarding installation of MapMarker USA v26, including how to
configure MapMarker USA v26 for a supported 64-bit operating system.
Running on 64-bit Operating Systems
Integrating Multiple MapMarker Countries Into One Tomcat Instance
Running on 64-bit Operating Systems
MapMarker USA includes the GeoStan 64-bit binaries but these binaries are not configured by default. Locate the
64-bit binaries in the appropriate Additional Tools > geostan_libs folder or your installation. For example, the linux
64-bit binary is (libgeostanMT.so) is located in:
C:\Program Files (x86)\MapInfo\MapMarker_USA_v26\sdk\additional_tools\geostan_libs\linux64
A comparable 64-bit binary file is located in the aix64 folder. The solaris64 folder has 2.9 and 2.10 subfolders that
contain the corresponding 64-bit binaries. The win64 folder contains libgeostanMT.so.
To use MapMarker USA v26 as a 64-bit application, follow these steps.
1. Stop the MapMarker USA server, if it is running.
2. Install a 64-bit Java JRE if you have not already done so.
3. Make a backup of the file libgeostanMT.so by renaming it libgeostanMT.so.bak. (On Windows 64-bit systems, make
a backup of Geostn64MT.dll.) This file is located in: <install_dir>/sdk/engine/bin/.
4. Locate the file libgeostanMT.so under <Install_dir>/additional_tools/geostan_libs/<platform> (file is named
Geostn64MT.dll. on Windows 64-bit systems). Copy this file to <install_dir>/sdk/engine/bin/.
5. Make a backup copy of the Tomcat startup file in <install_dir>/sdk/tomcat/bin/startup.sh (UNIX systems). For
Windows systems, the file is named startup.bat.
6. Open startup.sh (or startup.bat) in a text editor.
7. Update the path for JRE_HOME to the new 64-bit JRE that will be used.
MapMarker USA 26.0 Release Notes
12
8. If needed, edit the CATALINA_OPTS entry to increase the maximum memory usage. The default is 512m.
MapMarker USA v26 will consume more memory in a 64-bit installation.
9. Save and close the startup file.
10. Restart the MapMarker USA server.
L
You must use a 64-bit JVM to support your 64-bit MapMarker USA 26.0 application.
Integrating Multiple MapMarker Countries Into One Tomcat Instance
You can integrate multiple geocoders into one Tomcat instance. This allows you to use more that one geocoder with a
single URL. The Developer Guide provided on your media also describes this integration strategy. For demonstration
purposes, this section describes the integration of MapMarker USA v26 and MapMarker Canada v11.6 and assume
that both products have been successfully installed. At a minimum, install the MapMarker server component and data
for each country.
The best strategy is to identify which country web application has the newest MapMarker Java core and integrate into
that web application. This strategy will minimize the number of files that you have to copy.
Determining the Java Core Engine To determine the core version, you need to examine the MapMarker Java
Server Status for each country. After starting the MapMarker server, select MapMarker CTY v## Server from the
MapMarker program group (for example, MapMarker USA Server). Then click the link that displays your machine
name.
Select the MapMarker Server Status link in the Administration category. The MapMarker Java Core version appears
near the top of the status report. The country-specific MapMarker Java Plugin Version Information appears in the
Product Specific Information category.
After you examine both the MapMarker USA and MapMarker Canada server reports, you will know the core version
number and build numbers for both products. For example:
MapMarker Country
MapMarker Java Core
Version
MapMarker Java Plugin Version (Build Number)
MapMarker USA v26
4.8.2.71
26.0.0.14
MapMarker Canada v11.6
4.8.2.57
11.6.0.1
Since MapMarker USA v26 uses the newer core (4.8.2.71), it is easier to integrate files from the CAN installation into
the USA Tomcat.
Now follow these steps:
1. Identify the USA and CAN jar files and properties files. By default, the locations are:
<MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib
<MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib
Copy the following files from the MapMarker CAN installation into the corresponding USA WEB-INF\lib\ folder:
miscp.jar
mmj_can.jar
MapMarker USA 26.0 Release Notes
13
2. You must also copy several properties and license files. By default, these are in:
<MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\
<MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\
Copy the following files from the MapMarker CAN installation into the corresponding USA WEB-INF\classes\ folder:
CAN_DataManagersettings.properties
MMCANLicenseFactory.config
MMCANLicenseProvider.config
3. Verify that the Tomcat server allocates at least 512 MB of RAM. Open catalina.bat (or catalina.sh for Solaris) in:
<Install>\sdk\tomcat\bin
and look for the entry:
set CATALINA_OPTS= -mx512m -server
The maximum heap size should be at least 512 MB. This should be adequate for most country integrations, but a
heap size of 1 GB is recommended for optimum performance for a USA and CAN integration.
4. Restart the USA server and re-examine the Java Server Status report for USA as described in Determining the
Java Core Engine on page 13. The Product Version Information shows the MapMarker Java Core version. The
MapMarker Java Plugin Version Information near the bottom of the status report shows something similar to the
following, confirming that both the USA and Canada products are installed in the same Tomcat.
Plugin
Version
United States (USA)
26.0.0.14
Canada (CAN)
11.6.0.1
You can now geocode both American and Canadian addresses within the same Tomcat instance. Both geocoders will
now use the same (USA) port number.
Integrating other MapMarker Server products into a single Tomcat instance: You can use this same strategy to
integrate any number of MapMarker servers into one Tomcat instance. First determine which installed MapMarker has
the most recent core version. Then determine which country-specific files need to be copied into the target web server.
(It may help to diff the contents of the ...\WEB-INF\lib and ...\WEB-INF\classes folders.) For each country you wish to
integrate into an existing Tomcat, copy the country-specific jar, properties, and license files into the Tomcat with the
newest MapMarker Java core.
Performance of Tomcat integration strategy: Heap size of 512 MB is usually adequate, but 1 GB is recommended
for optimum performance for a USA and CAN integration. On 32 bit systems, 1.5 MB is the maximum heap size.
Larger heap sizes can be allocated on 64 bit systems.
If you move country data: By default, country-specific data is located in directories named
MapMarker_CTY_v##_Data (where CTY is the country identifies and v## is the version number). Each
CTY_DataManagersettings.properties file (copied in step 2) includes a DICTIONARY_PATH# entry that points to the
respective data file location. If you move country data to a different location, you must update the property file to point
to the data location.
MapMarker USA 26.0 Release Notes
14
Known Issues and Clarifications
This section covers known issues and behaviors that require further explanation.
Installing MapMarker USA v26 with NAVTEQ Street Data
The procedure for installing NAVTEQ NAVSTREETS as your primary street segment address dictionary was not fully
described in previous documentation.
If you want to use NAVSTREETS as your primary street segment dictionary, install MapMarker USA v26 software
without the default TomTom street data. Using the graphical interface for installation, uncheck the Data box from the
Choose Install Set dialog. The software installation will then proceed without installing the TomTom data.
NAVSTREETS can then be installed by the MapMarker Data Installer. See the MapMarker Data Installer document for
instructions on installing NAVTEQ Points and other supplemental datasets.
Activating a New Permanent License
You may receive a permanent license for several reasons. Most commonly, you will receive a permanent license to
replace a temporary one. You also will receive a new permanent license if you renewed your contract of it there is a
change to your contract agreement (for example, if you licensed additional states or supplemental data that was not
covered by your previous contract). Remember, your MapMarker USA application will stop working when the old
license or data expires.
To generate a new permanent license, see License Management Tool on page 4.
To activate the new license, follow these steps.
1. After receiving your new permanent license file, delete the temporary or old license file from the MapMarker Data
folder and replace it with the new one.
C:\Program Files\MapInfo\MapMarker_USA_v26\MapMarker_USA_v26_Data
Or for 64-bit machines:
C:\Program Files (x86)\MapInfo\MapMarker_USA_v26\MapMarker_USA_v26_Data
L
If you are extending or changing your contract, the new license file may have the same name as your
existing license file. However, because the license has a new contract expiration date (or other changes)
you must still replace the old license file.
2. If you are using the Server product, open the server USA_DataManagerSettings.properties file in a text editor. This
properties file is located in:
C: \Program Files\MapInfo\MapMarker_USA_v26\sdk\tomcat\webapps\mapmarker40\WEBINF\classes
Or for 64-bit machines:
C:\Program Files (x86)\MapInfo\MapMarker_USA_v26\sdk\tomcat\webapps\mapmarker40\WEBINF\classes
Edit the USA_DataManagerSettings.properties file to point to the full pathname of the new the license file.
LICENSE_FILE=
…...NameOfLicense.lic
3. If you had a previous license for the Desktop product, make the comparable edit to the
USA_DataManagerSettings.properties file located in the Desktop folder. (typically C:\Program
Files\MapInfo\MapMarker_USA_v26\desktop).
If you have any difficulty in using the license file, the Pitney Bowes Software Customer Service group will be prepared
to answer your questions and assist you.
MapMarker USA 26.0 Release Notes
15
Creating a Point User Dictionary with the User Dictionary Utility
The MapMarker USA User Dictionary Utility can be installed with the MapMarker USA Developer product. This utility
simplifies the steps for creating user dictionaries. The utility displays a dialog indicating that point-based user
dictionaries are not supported. This dialog is misleading. When you click Next and proceed past that dialog, you will
still have the opportunity to create a user dictionary in which each street range contains a single point.
To create a point-based user dictionary using the utility, the From Left and To Left columns for each record must have
the same house number. You must then map the table input columns appropriately in the Required Columns dialog of
the User Dictionary Utility.
Required Column Mapping for Point User Dictionary
UD Utility Entry
Map To Table Column
Left Starting Address Number
From Left input table column
Left Ending Address Number
To Left input table column
Right Starting Address Number
empty column
Right Ending Address Number
empty column
Follow these requirements and column mapping guidelines when creating a point-based user dictionary with the User
Dictionary Utility.
•
•
•
•
The source TAB file for your user dictionary must have an empty column. You will need this empty column for
mapping purposes. To add an empty column to the TAB file, use MapInfo Professional and select
Table > Maintenance > Table Structure > Add Field). Add this column before starting the User Dictionary Utility.
The User Dictionary Type dialog indicates that point-based user dictionaries are not supported. However when you
click Next and proceed past that dialog, you will still have the opportunity to create a user dictionary in which each
street range contains one point.
Map the Left Starting Address and Left Ending Address fields. The same house number must be in both the left and
right fields for each record.
Map the Right Starting Address and Right Ending Address to an empty column.
Configuring User Dictionary as the Only Dictionary with MapMarker USA Server
With the MapMarker USA Server product, use the USA_DataManagerSettings.properties file to configure address and
user dictionaries and set the priority of these dictionaries. This is described in the MapMarker USA v26 Developer
Guide. However, if you want to configure the Server product with a user dictionary only (without an address dictionary),
you must also copy the following files from the standard address dictionary folder (MapMarker USA v26_Data) into the
user dictionary folder:
•
•
•
ctyst.dir
parse.dir
us.z9
If you do not copy these files, the MapMarker USA Server generates an initialization error when you configure a user
dictionary as the only available dictionary.
With the Desktop product, no special actions are required to configure a user dictionary as the only dictionary.
MapMarker USA 26.0 Release Notes
16
Shared installation – Accessing and Running Client Desktop Installer
After the administrator installs the MapMarker USA Desktop application as a shared application (for Windows platform
only), each MapMarker client user can install the Desktop application on their local machine.
To perform this client installation, access the <install>MapMarker_USA_v26_Data\DesktopInstaller\ folder on the
server machine and locate the following files:
•
•
ClientSetup.exe – client Desktop application installer
Setup.INI – INI file that specifies the data path
L
The administrator must share the Data and DesktopInstaller folders so that client users can access these files.
You can run the ClientSetup.exe to install the Desktop application on your local machine. See the MapMarker USA
v26 User Guide for the Client Workstation Install topic. Each client must have a license file (received from your Sales
Representative) in order to complete the installation.
Microsoft Windows Administrator-Related Issues
This section covers some administrator -related issues that are common to Microsoft Windows 2008 Server, and
Windows 7.
You must always have administrator rights on the target machine to install MapMarker. This is true on all operating
platforms.
Starting and Stopping the MapMarker Server: To start or stop the server using administrator credentials, right-click
the shortcut for the operation that you wish to perform and from the menu that appears, select Run as administrator.
If you did not install shortcuts, run the commands from an Administrator Command Prompt.
To open an Administrator Command Prompt, access the Start Menu and select All Programs > Accessories.
Right-click the shortcut titled "Command Prompt" and from the menu that appears, select Run as administrator. The
command prompt that opens allows commands to be executed with administrator credentials applied.
Installing and Removing the MapMarker Server as a Windows Service: To install or remove the server as a
Windows Service, first open an Administrator Command Prompt. From the Command Prompt, run the commands to
install or remove the service, as described in the topic Running the Web Application as a Windows Service in Chapter
2 of the MapMarker Developer Guide.
Using ODBC Data source: You must have administrator privilege to create a new ODBC data source. The user also
must set up their ODBC connections in advance.
Reinstall Failure after Improper Uninstall: To properly uninstall MapMarker, you must run the Uninstaller. If you did
not run the Uninstaller, but instead deleted the MapMarker directories, you will not be able to routinely re-install the
product.
Administrator Rights for UNIX/Linux Platforms
On UNIX and Linux platforms, administrator rights are required in the following cases.
Administrator Rights Required for Installation: For UNIX and Linux installations, you must have administrator rights
on the target machine to install MapMarker. If you attempt to install on a machine where you do not have administrator
rights, you receive an error message.
Administrator Rights Required to Start Tomcat Server: On UNIX/Linux platforms, the Tomcat server must be
started and stopped by a user with administrator rights.
MapMarker USA 26.0 Release Notes
17
HP-UX Installation Issue
During installation on HP-UX machines, the geoappl application (installed to
$USER_INSTALL_DIR/sdk/additional_tools/geoeng/test/geoappl) may fail to start with error code 1804.
If this happens, examine the file $USER_INSTALL_DIR/sdk/additional_tools/mme.profile and look for double
occurrences of the path separator character ( : ) in the variable assignments. For example, if the path looks like:
SHLIB_PATH=$SHLIB_PATH::/data/MapMarker_USA_v26/jre/lib/PA_RISC2.0:/...
Edit this to remove the extra colon separator following PATH
SHLIB_PATH=$SHLIB_PATH:/data/MapMarker_USA_v26/jre/lib/PA_RISC2.0:/...
Log File for Cancelled or Failed Install
When the installation fails or is cancelled, a log file is created that provides some insight into what happened. This is
useful in the silent install scenarios (install, modify, update, or uninstall), because it directs the user to what must be
changed.
On Microsoft Windows, the log is created in the user’s desktop folder by default. On UNIX/Linux systems, this file is
created in the user's home directory or at the root directory ( / ).
MapMarker USA 26.0 Release Notes
18