MapMarker. v28.0 RELEASE NOTES

Transcription

1 MapMarker v28.0 RELEASE NOTES

2 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 Inc., One Global View, Troy, New York Pitney Bowes Inc. All rights reserved.pitney Bowes Inc. Pitney Bowes, the Corporate logo, MapInfo, Group 1 Software, and MapXtreme are trademarks of Pitney Bowes Inc. or a subsidiary. All other trademarks are the property of their respective owners. Contact information for all Pitney Bowes Inc. offices is located at:: This product contains SpatiaLite v 3.1.0, which is licensed under GNU Lesser General Public License, Version 2.1, February The license can be downloaded from: The source code for this software is available from and This product contains Feature Data Objects v 3.6.0, which is licensed under GNU Lesser General Public License, Version 2.1, February The license can be downloaded from: The source code for this software is available from This product contains HelpLibraryManagerLauncher.exe v , which is licensed under Microsoft Public License. The license can be downloaded from: The source code for this software is available from April 30, 2015

3 MapMarker USA v28.0 Features and Enhancements Following is a summary of the updates that are you will see with the MapMarker USA v28.0 release. These features are summarized here for convenience and are fully covered in the appropriate sections of the MapMarker USA User Guide and in the MapMarker USA Developer Guide. MapMarker USA v28.0 features are described in the following topics: Matching Improvements Higher Quality Candidates Returned for Input Addresses with Unique ZIP Codes Updated Address Dictionaries License Management Tool The implementation date for CASS Cycle O has been deferred by the United States Postal Service (USPS ) until July 31, The USPS Coding Accuracy Support System (CASS ) Cycle N will be valid through July 31, The USPS reserves the right to modify the "valid through" date in the future if conditions warrant it. The geocoder application shipped with MapMarker USA v28.0 is CASS Certified for Cycle N. Matching Improvements MapMarker USA v28.0 has improved matching of addresses that contain incorrect pre-directionals, oddly formed street type abbreviations, and truncated street names. Reverse geocode matching is improved in rural areas with unranged street segments. Various additional improvements have been made to the matching logic. Higher Quality Candidates Returned for Input Addresses with Unique ZIP Codes A unique ZIP Code is a ZIP Code assigned to a company, agency, or entity with sufficient mail volume to receive its own ZIP Code. CASS rules prohibit altering an input ZIP Code if it matches a unique ZIP Code value. This CASS rule when applied to non-cass match modes resulted in the return of a formatted street address that was not matched to an address range, as well as a lowquality ZIP centroid candidate based solely on the unique ZIP input. For non-cass match modes, no longer apply the special CASS matching rules. We now match the input address against address ranges in the input city, update the ZIP Code and associated address elements based on the matched address, and provide the highest-quality geocode available for the input address. Reverse Geocoding Performance Improvements MapMarker USA v28.0 has across-the-board performance improvements for reverse geocoding. Performance improvements are most significant when using point data sets. MapMarker USA Release Notes

4 Updated Address Dictionaries 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, NAVTEQ Point Addressing data was available for purchase and license. See NAVTEQ Point Address Dictionary Details and Licensing on page 5 for more information on the NAVTEQ Point Addressing 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 v February ( ) 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 v28.0. The following Address Dictionaries are available for use with MapMarker USA v28.0 and can be used within the same core engine. TomTom Street data. This primary address dictionary is installed by default. NAVTEQ NAVSTREETS 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 v28.0 with NAVTEQ NAVSTREETS Street Data TomTom Points data. This is available as a supplemental address dictionary, and is installed using the MapMarker Data Installer. This includes over 90.3 million records, including points from Puerto Rico, Virgin Islands, and Guam. NAVTEQ Point Addressing data. This data source was introduced with MapMarker USA v26 and is available as a supplemental address dictionary. This is installed using the MapMarker Data Installer. This includes over 97 million records. Centrus Points data. This is available as a supplemental address dictionary, and is installed using the MapMarker Data Installer. This includes over 98.1 million points. 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 Point Addressing address dictionaries can be installed in their own data paths. For point datasets, 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. If you install a point address dictionary, the corresponding TomTompoints.xls, NavteqPoints.xls, CentrusPoints.xls, or MasterLocation.xls file is installed in the <install>\mapmarker_usa_v28_data folder. MapMarker USA Release Notes

5 Data shipped with MapMarker USA v28.0 is labelled with a common MapMarker product vintage date of The underlying vendor-specific vintages for the data sources are as follows. Data Provider Vintages for MapMarker USA v28.0 Data Vendor Version TomTom Streets (MultiNet) NAVTEQ NAVSTREETS 2015.Q1 TomTom Points (MultiNet) NAVTEQ Point Addressing 2015.Q1 Centrus Points Version TIGER 2014 Depending on your license agreement, you can update data quarterly or monthly (except for TIGER). Beginning with MapMarker USA v28.0, NAVSTREETS can be updated monthly. Previously it was available for quarterly update only. See the Pitney Bowes web site for more detailed information on the U.S Geocoding Data Sets. Since there are no changes to the MapMarker USA v28.0 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 NAVTEQ Point Addressing dictionary gives you the ability to geocode to the highest level of accuracy (S8 point geocode matches). NAVTEQ Point Addressing is licensed for all of United States, not by individual state. As for any point address dictionary, NAVTEQ Point Addressing must be used in conjunction with a standard street address dictionary of the same MapMarker product vintage. The NAVTEQ Point Addressing dictionary includes over 104 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. The NAVTEQ Point Addressing dictionary is separately licensed. See License Management Tool on page 6 for instructions on using the license tool. The NAVTEQ Point Addressing 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 Point Addressing and other supplemental datasets. MapMarker USA Release Notes

6 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. If your Sales Representative provided you with a temporary license, you will need to acquire a permanent one. Pitney Bowes provides the command line License Assistant utility (LicAssist.exe) that enables you to generate a file request for a permanent license. 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 UNIX LicAssist.exe license assistant utility licassist.txt instructions for running License Assistant utility licassist license assistant utility. licassist.txt instructions for running License Assistant utility <root>\licassist\windows\ directory on the software installation media. <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 Pitney Bowes Software Customer Service. The licassist utility generates a txt file that you can to Pitney Bowes without the need to zip the file. After you this file to Pitney Bowes Customer Service at CustomerService- PBS@pb.com, you will receive return with the permanent license file (.lic file) specific to your machine. 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. MapMarker USA Release Notes

7 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. 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). this txt file to Pitney Bowes Customer Service at CustomerService-PBS@pb.com. There is no need to zip the file. In return , you will the receive the permanent license file (.lic file) specific to your machine. When you run the licassist utility, Pitney Bowes 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 v28 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 v28 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. MapMarker USA Release Notes

8 Operating Requirements Operating Requirements This section describes the hardware, memory and other requirements for MapMarker USA v28.0. 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 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 2008 Server (32 and 64-bit) Microsoft Windows 2012 Server (64-bit) Microsoft Windows 7 (64-bit) Microsoft Windows 8 (64-bit) (Windows 8.1 recommended and will be required in subsequent update) Solaris 2.9 and 2.10 (32-bit) Solaris 2.11 (64-bit) SUSE Linux 10 and 11 (64-bit) HP-UX 11.x (64-bit) Red Hat Linux 5.0 (64-bit) Red Hat Linux 6.1 (64-bit) For Red Hat Linux 6.1 you must install all missing 32-bit system libraries, in addition to the default 64-bit libraries. MapMarker USA Release Notes

9 Operating Requirements 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 2008 Server (32-bit and 64-bit) Microsoft Windows 7 (64-bit) JVM Requirements MapMarker v28.0 requires a Java Virtual Machine (JVM). MapMarker USA v28.0 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. Java 1.6 or higher is required to run MapMarker USA v28.0. Java 1.5 is not supported for this release. if you install a 64-bit version of MapMarker USA v28.0 you must also use a 64-bit JVM. Database Support MapMarker USA v28.0 supports the following ODBC databases and drivers. SQL Server 2005 SQL Server 2008 Microsoft Access 2010 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 10G Release 2 Oracle 11 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.6. MapMarker USA v28.0 ships with: Apache Tomcat 6.0 MapMarker USA Release Notes

10 Fixes to Known Issues 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 v28.0 (which uses the Geostan library), run: ldd <install_dir>/sdk/engine/bin/geostanmt.so This will return the MapMarker library dependencies for your UNIX system (Linux, Solaris, or HPUX). For example, if you installed a v28.1 update, the underlying geocoding engine is also updated (for example to ) Supported Pitney Bowes Products MapMarker USA v28.0 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 Fixes to Known Issues The following incident was addressed in MapMarker USA v28.0. Desktop application crashes when opening an displaying SQL Server table with long column names. If a column name in an SQL Server table exceeds 32 characters, the Desktop application crashes when you attempt to display the table in the Desktop Browser. This has been fixed. Column names up to 128 characters are displayed in full and column names longer than that are truncated at 128 characters. Cannot close Desktop application after opening SQL table. Under some circumstances, after opening an SQL table you can be trapped in an error loop and cannot close the Desktop application, unless you kill the program from Task Manager. Opening an empty ODBC table causes the same problem. This has been fixed. Postal fallback does not always work. For some postal codes (point ZIP codes), postal fallback is not working. This has been fixed. MapMarker USA Release Notes

11 Fixes to Known Issues Result code indicates non match on street even though the street name is exactly matched. The candidate result code indicates a "-" non-match on street name. However, the street name appears to be a perfect match. This has been fixed. Cannot disable an address dictionary for searching. It is not possible to disable searching for an address dictionary with the setdictionaryavailableforsearch method. The setting of false is ignored and therefore the dictionary is still searchable. This has been fixed. User dictionaries return highway and route addresses more accurately. In user dictionaries, numbered highway and route addresses were not returned with complete addresses. For example, State Rt 2 Is returned as "2" without the State Rt part of the address. This has been fixed, and a variety of variety of user dictionary highway name and route number addresses are now returned in a more complete and accurate format. County name is missing from some Desktop application candidates. In the Desktop application, some candidates are missing content from County output column. For Louisiana, county equivalents are called parishes and in Virginia In some cities are counties in their own right. In those cases, the Desktop application returns nothing in the "County" output column. This has been fixed and the county equivalent is now always returned in the Desktop application. Improved Must Match House Number Conformance The Must Match House Number constraint is enforced more consistently. In some cases it was possible for a candidate to return as a close match even though Must Match House Number was specified but the house number differed from the input. Also some user dictionary highway/route address or addresses formatted with an Avenue "pretype" failed to geocode. MapMarker USA v28.0 now handles these types of user dictionary addresses. If your user dictionary has these types of addresses and you want to take advantage of this improvement, you must rebuild that user dictionary. For example, any of the following user dictionary address inputs will return the standardized format of the highway / route as part of the candidate address. Highway 52 Hiway 52 Hwy 52 Returned as: Highway 52 Route 66 Rte 66 Rt 66 Returned as: Route 66 State Hwy 2 St Hwy 2 Returned as: State Highway 2 US Hwy 101 Returned as: US Highway MapMarker USA Release Notes

12 Installation-Related Configuration and Tomcat Integration Cty 142 Cty Rt 142 Returned as: County Route 142 The following types of user dictionary address failed to return any close match candidates. These and similarly formatted user dictionary addresses now return close match candidates as expected Route 5 AND 20 Bloomfield, NY 42 Ave B New York NY Installation-Related Configuration and Tomcat Integration This section provides some additional information regarding installation of MapMarker USA v28.0, including how to configure MapMarker USA v28.0 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_v28\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. You must use a 64-bit JVM to support your 64-bit MapMarker USA 28.0 application. To use MapMarker USA v28.0 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. On 64-bit Unix/Linux systems, make a backup of the file libgeostanmt.so by renaming it libgeostanmt.so.bak. On Windows 64-bit systems, make a backup of all libraries under <geostan_libs>/win64 to <engine>/bin. 4. 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. 5. Modify the startup.bat (or startup.sh) and update the JRE_HOME path to point to the 64-bit JRE that will be used. On some Unix/Linux systems you may need to update the CATALINA_OPTS MapMarker USA Release Notes

13 Installation-Related Configuration and Tomcat Integration entry to increase the maximum memory usage to use the 64-bit Java. Edit the entry as follows: CATALINA_OPTS="-Xmx512m -server -d64" 6. Save and close the startup file. 7. Restart the MapMarker USA server. For Solaris 11 SPARC v9 64-bit machines, see Running on SPARC V9 64-bit Platform on page 18. For Red Hat 6.1 machines, you must install 32-bit system libraries, in addition to the default 64-bit libraries. The FINDAD32.mbx provided with MapMarker USA v28.0 will not work with 64-bit MapInfo Professional. 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 v28.0 and MapMarker Canada v11.14 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 v MapMarker Canada v MapMarker USA Release Notes

14 Installation-Related Configuration and Tomcat Integration Since MapMarker USA v28.0 uses the newer core ( ), 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 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= -xmx512m -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 better 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) Canada (CAN) MapMarker USA Release Notes

15 Known Issues and Clarifications 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 256 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. Known Issues and Clarifications This section covers known issues and behaviors that require further explanation. Installing MapMarker USA v28.0 with NAVTEQ NAVSTREETS 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 v28.0 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 Point Addressing 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. MapMarker USA Release Notes

16 Known Issues and Clarifications To generate a new permanent license, see License Management Tool on page 6. 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_v28.0\MapMarker_USA_v28.0_Data Or for 64-bit machines: C:\Program Files (x86)\mapinfo\mapmarker_usa_v28.0\mapmarker_usa_v28.0_data 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_v28.0\sdk\tomcat\webapps\mapmarker40\WEB- INF\classes Or for 64-bit machines: C:\Program Files (x86)\mapinfo\mapmarker_usa_v28.0\sdk\tomcat\webapps\mapmarker40\web- INF\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_v28\desktop). If you have any difficulty in using the license file, the Pitney Bowes Support group will be prepared to answer your questions and assist you. 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 v28.0 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 v28.0_data) into the user dictionary folder: MapMarker USA Release Notes

17 Known Issues and Clarifications 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. 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. Each client must have a license file (received from your Sales Representative) in order to complete the installation. To perform this client installation, access the <install>mapmarker_usa_v28_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 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 Client Workstation Install topic in the MapMarker USA v28.0 User Guide. This and other MapMarker documentation is located on the Pitney Bowes Product Documentation site. 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. MapMarker USA Release Notes

18 Known Issues and Clarifications 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 USA v28.0 Developer Guide. This and other MapMarker documentation is located on the Pitney Bowes Product Documentation site. 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. 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 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_v28/jre/lib/PA_RISC2.0:/... Edit this to remove the extra colon separator following PATH SHLIB_PATH=$SHLIB_PATH:/data/MapMarker_USA_v28/jre/lib/PA_RISC2.0:/... Running on SPARC V9 64-bit Platform On a Solaris 11 SPARC v9 64-bit platform, add the -d64 property to the CATALINA_OPTS entry of startup.sh: CATALINA_OPTS="-Xmx512m -server -d64" This is required for running the 64-bit geostan libs on SPARC v9 64-bit processors. MapMarker USA Release Notes

19 Known Issues and Clarifications 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 ( / ). Running 64-bit MapInfo Professional The FINDAD32.mbx provided with MapMarker USA v28.0 will not work with 64-bit MapInfo Professional. This is because 64-bit MapInfo Professional cannot load the 32 bit DLL that Findad32.mbx uses. Optimizing ODBC Database Performance The topic of optimizing MapMarker performance when geocoding remote database tables was not accurately covered in the previous documentation. The MapMarker USA v28.0 User Guide has been updated with the following information: When using separate input and output tables, MapMarker performance is faster when the input table is indexed either by State plus City or by ZIP Code. For better performance, the output table should not be indexed. That is true even if the input and output tables are the same. For table row updates, performance is better if columns are not indexed. It is better to drop the column index before processing then create it later if it is needed. Also, the location of the ODBC error log file was not correctly documented. The correct location for ODBCerr.log is:...\progamdata\mapinfo\mapmarker\usa\28.0 Required Files for Installation The Required Files section of the Developer Guide Installation chapter has been updated to list the correct list of files. The following has been removed and are not required: midev-common.jar midev-coordsys-core.jar midev-dataaccess-components-rtree.jar midev-geometry.jar Make sure that your classpath now includes the following required files: midev-core-common onprem.jar midev-core-coordsys-core onprem.jar midev-core-coordsys-utilities onprem.jar midev-core-csw-configuration onprem.jar midev-core-dataaccess-components-rtree onprem.jar midev-core-dataaccess-core onprem.jar midev-core-dataaccess-dataproviders-fdodataprovider onprem.jar MapMarker USA Release Notes

20 Known Issues and Clarifications midev-core-dataaccess-dataproviders-file onprem.jar midev-core-dataaccess-dataproviders-readonlytab onprem.jar midev-core-dataaccess-engine onprem.jar midev-core-dataaccess-language onprem.jar midev-core-dataaccess-table onprem.jar midev-core-dataaccess-tabledepot onprem.jar midev-core-feature onprem.jar midev-core-geometry onprem.jar midev-core-jts onprem.jar midev-core-raster onprem.jar midev-core-style onprem.jar guava-18.0.jar jts-1.11.jar trove jar commons-csv-1.0.jar commons-io-2.4.jar commons-lang-2.5.jar time.jar (This isn't new, but MapMarker USA was not including this previously MapMarker USA Release Notes