Release Notes. MapMarker Canada. Version 15. Table of Contents. Location Intelligence Geographic Information Systems

Transcription

1 Location Intelligence Geographic Information Systems MapMarker Canada Version 15 Release Notes This Release Notes document accompanies the MapMarker Canada 15.0 release and describes new features, operating requirements, fixes for known issues, and other issues that may require your attention. You should use it in conjunction with the MapMarker Canada Version 15 User Guide, Developer Guide, and Data Installer Notes, which are available on the MapMarker media and on Pitney Bowes web site under the CANADA heading on the MapMarker Product Documentation page. Table of Contents New Features and Enhancements 2 Operating Requirements 10 Fixes to Known Issues 12 Known Issues and Clarifications 13 UNITED STATES pitneybowes.com Technical Support support.pb.com CANADA pitneybowes.com Technical Support support.pb.com EUROPE/UNITED KINGDOM pitneybowes.com/uk Technical Support pitneybowes.com/uk/support ASIA PACIFIC/AUSTRALIA pitneybowes.com/au Technical Support pitneybowes.com/au/support 2015 Pitney Bowes, Inc.

2 New Features and Enhancements Features and enhancements new to MapMarker Canada 15.0 include: Data Source Code Returned with Candidate Data Availability and Vintages Significance of Dictionary Priority Updated Installer for MapMarker Canada 15.0 Installing with MapMarker Canada 15.0 Point Addressing Data Data Source Code Returned with Candidate Candidates now return a numeric code that identifies the database in which the candidate was found. This is implemented for both the desktop application and the geocoding engine level. MapMarker Canada 15.0 can use the following data sources and display the following data IDs. Data Vendor Codes Data Source Data ID TomTom Streets 2 TomTom Point Addressing 7 NAVTEQ Point Addressing 11 User Defined Dictionary 10 In the desktop application, the data source code is returned in the Data ID field. In the server, the data source code is returned in the StreetDataType key. The following example indicates that the candidate was returned from the TomTom Streets data source: <KeyValuePair> <Key>StreetDataType</Key> <Value>2</Value> </KeyValuePair> MapMarker supports additional numeric codes for other data vendors and sources. The above codes are the only codes that can be returned for MapMarker Canada Pitney Bowes 2 October, 2015

3 Data Availability and Vintages MapMarker Canada 15.0 Release Notes Data availability is determined by your license, which is based on the serial number and unlock code that you receive from Pitney Bowes Customer Service. If you want to upgrade to MapMarker Canada 15.0 with NAVTEQ Point Addressing and/or TomTom Point Addressing data and you did not previously license point addressing data with MapMarker, then you must uninstall and reinstall your MapMarker Canada software. See Installing with MapMarker Canada 15.0 Point Addressing Data on page 9 for details. The data availability and vintages are discussed in the following subsections: TomTom Streets Dictionary TomTom Point Addressing Dictionary NAVTEQ Point Addressing Dictionary MapMarker Canada Data Sources and Vintages TomTom Streets Dictionary The standard TomTom Streets address dictionary has been updated to vintage. The TomTom Streets Address Dictionary Coverage table describes the number of records by province/territory. TomTom Streets Address Dictionary Coverage Province/Territory Total Records Change From Previous Release Alberta (AB) 408,963 5,418 British Columbia (BC) 319,657 10,029 Manitoba (MB) 98,815 3,206 New Brunswick (NB) 83,834 3,362 Newfoundland and Labrador (NL) 37, Nova Scotia (NS) 103,800 1,253 Northwest Territories (NT) 3, Nunavut (NU) 1, Ontario (ON) 796,339 27,157 Pitney Bowes 3 October, 2015

4 TomTom Streets Address Dictionary Coverage (continued) Province/Territory Total Records Change From Previous Release Prince Edward Island (PE) 20, Quebec (QC) 541,678 6,210 Saskatchewan (SK) 120, Yukon (YT) 5, Total 2,541,195 57,170 The total size of the TomTom Streets dictionary for all provinces and territories is approximately 685 MB. TomTom Point Addressing Dictionary With the release of MapMarker Canada Version 15, you can now purchase and install the TomTom Point Addressing dictionary in addition to the standard TomTom Streets dictionary. Your license determines which address dictionaries you are authorised to use with MapMarker Canada. The TomTom Point Addressing dictionary is provided on separate media and installed separately using a supplemental data installer. The MapMarker Canada Version 15 Data Installer Notes describe how to install, update, and configure additional address dictionaries. The TomTom Point Addressing dictionary is approximately 444 MB. The TomTom Point Addressing Dictionary Coverage table describes the number of unique address points by province/territory. This includes both address records and point of interest (POI) records. TomTom Point Addressing Dictionary Coverage Province/Territory Total Records Change from Previous Release Alberta (AB) 1,158,123 Not Applicable British Columbia (BC) 1,004,214 Not Applicable Manitoba (MB) 238,017 Not Applicable Pitney Bowes 4 October, 2015

5 TomTom Point Addressing Dictionary Coverage (continued) Province/Territory Total Records Change from Previous Release New Brunswick (NB) 497,070 Not Applicable Newfoundland and Labrador (NL) 71,745 Not Applicable Northwest Territories (NT) 415,001 Not Applicable Nova Scotia (NS) 6,141 Not Applicable Nunavut (NU) 32 Not Applicable Ontario (ON) 3,510,185 Not Applicable Prince Edward Island (PE) 69,275 Not Applicable Quebec (QC) 1,841,170 Not Applicable Saskatchewan (SK) 196,838 Not Applicable Yukon (YT) 8,686 Not Applicable Total 9,016,497 Not Applicable NAVTEQ Point Addressing Dictionary You can purchase and install the NAVTEQ Point Addressing dictionary in addition to the standard TomTom street segment address dictionary. Your license determines which address dictionaries you are authorised to use with MapMarker Canada. The NAVTEQ Point Addressing dictionary is provided on separate media and installed separately using a supplemental data installer. The MapMarker Canada Version 15 Data Installer Notes describe how to install, update, and configure additional address dictionaries. The NAVTEQ Point Addressing dictionary is approximately 294 MB. If you are using the NAVTEQ Point Addressing dictionary, you can geocode to the highest level of accuracy (S8 point geocode matches). NAVTEQ Point Addressing data is licensed for all of Canada, not by individual province. However, during installation you can choose to install selected provinces and territories only. Pitney Bowes 5 October, 2015

6 Your license determines whether you can install TomTom Streets, NAVTEQ Point Addressing dictionary, or both. If you are installing NAVTEQ as your only address dictionary, then you should install software only during the initial installation, then use the MapMarker Data Installer to install the NAVTEQ Point Addressing dictionary. The NAVTEQ Point Addressing Dictionary Coverage table describes the number of unique address points by province/territory. This includes both address records and point of interest (POI) records. NAVTEQ Point Addressing Dictionary Coverage Province/Territory Total Records Change from Previous Release Alberta (AB) 1,102,862 5,585 British Columbia (BC) 854,090 8,603 Manitoba (MB) 232,103 11,278 New Brunswick (NB) 232, Newfoundland and Labrador (NL) 62,038-1 Northwest Territories (NT) 337, Nova Scotia (NS) 5,077 2 Nunavut (NU) 28 0 Ontario (ON) 3,389, ,633 Prince Edward Island (PE) 67,063 3 Quebec (QC) 1,682,671-1,457 Saskatchewan (SK) 146,019 3,420 Yukon (YT) 6,858 1 Total 8,117, ,637 Points of interest in the NAVTEQ data source include a variety of locations such as hospitals, restaurants, shopping locations, hotels, parks, financial institutions, transportation hubs, parking lots, entertainment venues, and other business and community services. Pitney Bowes 6 October, 2015

7 For example, assume that both the NAVTEQ Point Addressing and TomTom Streets dictionaries are available (regardless of dictionary priority order). Consider the following point of interest input with no street address information: Firm: Oyster Boy City: Toronto Province: ON This returns the following close match S8 point candidate from the NAVTEQ Point Addressing dictionary. Firm: OYSTER BOY Street: 872 QUEEN ST W LastLine: TORONTO, ON M6J 1G3 Result Code: S8HPNTSCZA X: Y: In this example, the NAVTEQ and TomTom dictionaries are available (regardless of dictionary priority order) and both firm name and street address are provided on input: Firm: Oyster Boy Address: 872 Queen St W City: Toronto Province: ON This returns a point/parcel S8HPNTSCZA close match candidate. It also returns several non-close matches, including an S5HPNTSCZA street level non-close candidate with the same address. The S8 candidate is from the NAVTEQ Point Addressing dictionary and the S5 candidate is from the standard TomTom Streets dictionary. MapMarker Canada Data Sources and Vintages The MapMarker Canada dictionaries are updated quarterly and are based on data from the following sources. MapMarker Canada Data Sources and Vintages Data Source Vintage TomTom MultiNet Canada Data (June 2015) Canada Post Address Range Data (June 2015) Statistics Canada PCCF (Postal Codes) and FSA Boundaries (March 2015) Pitney Bowes 7 October, 2015

8 MapMarker Canada Data Sources and Vintages (continued) Data Source TomTom Census Data Refresh Vintage (June 2015) based on Canada Census data of 2011 TomTom Point Addressing (June 2015) NAVTEQ Point Addressing 2015.Q3 Unused rural road records have been removed from the Canada Post source data. These rural roads were never used for geocoding but they inflated the size of the address dictionary. Rural addresses are geocoded accurately based on more specific source records. Significance of Dictionary Priority The NAVTEQ and TomTom Point Addressing data sources include points of interest records and address records. The TomTom Streets data source includes address records only. This means that duplicate address records can potentially exist (one from the NAVTEQ dictionary and one each from the TomTom dictionaries). In that case, the priority order of the address dictionaries determines which address candidate is returned as a close match. To control dictionary priority order for the desktop application, use System Preferences (Dictionary tab). To control dictionary priority order for the server, use the CAN_DataManagerSettings.properties file and edit the DICTIONARY_PATH# entries. DICTIONARY_PATH1 has the highest priority. For example, assume that you search: Firm: United Way Address: 26 Wellington St E Unit 200 City: Toronto Province: ON If you have installed the NAVTEQ address dictionary in addition to the standard TomTom address dictionary and the TomTom dictionary has priority, then the S5 close match address candidate is returned from the TomTom dictionary, along with an S8 non-close match. But if the NAVTEQ address dictionary has priority, then the S8 close match is returned from the NAVTEQ source, along with an S5 non-close match. Pitney Bowes 8 October, 2015

9 S8 Candidates do not return census information; census information is associated with the standard TomTom address dictionary only. If a candidate includes census information, it must have been returned from the TomTom address dictionary. You can also use the MapMarker Java API to specify the order of dictionaries and which dictionaries to use in a geocode request. The API settings override preferences set through the desktop application or the DataManagerSettings.properties file. Dictionary preferences are set using the IDictionarySearchOrder object. Use the getsearchorderfordictionary method to return the current dictionary search order and the setsearchorderfordictionary method to change the dictionary search order. See the topic Setting Dictionary Preferences Using MapMarker Java API in the Custom User Dictionaries chapter of the MapMarker Canada Version 15 Developer Guide. Updated Installer for MapMarker Canada 15.0 The updated installer for MapMarker Canada 15.0 installs JVM 1.6 by default, but also supports JVM 1.7 and 1.8. The installer prevents you from selecting versions of JVM older than 1.6, because it no longer supports them. Installing with MapMarker Canada 15.0 Point Addressing Data Generally, there is no special procedure for installing point addressing data. As long as you are licensed for the data, you can install and use the TomTom or NAVTEQ Point Addressing dictionaries in addition to the TomTom Streets dictionary that is available by default. If you are an existing MapMarker Canada customer and are installing either point addressing dictionary for the first time, you must follow these steps to install MapMarker Canada 15.0 with the point addressing dictionaries. Install MapMarker Canada 15.0 Install the Point Addressing Dictionary Install MapMarker Canada 15.0 You can install MapMarker Canada 15.0 using the graphical installer interface or silently without user interaction. Remember, a complete install of MapMarker Canada 15.0 is necessary only if you are installing MapMarker Canada for the first time or if you are upgrading from a previous version of MapMarker Canada and using either TomTom or NAVTEQ Point Addressing Pitney Bowes 9 October, 2015

10 data. If you are upgrading MapMarker Canada with the new vintage of TomTom Streets only, then you will do a simple upgrade installation as you would for any MapMarker point release. See the Installing MapMarker chapter of the MapMarker Canada Version 15 User Guide or MapMarker Canada Version 15 Developer Guide for instructions on performing a complete install of MapMarker Canada. During installation, enter the new serial number and unlock code that is valid for both the standard TomTom Streets dataset and point addressing dataset. The new license is created at install time for the datasets you purchased. Install the Point Addressing Dictionary The TomTom and NAVTEQ Point Addressing dictionaries are each provided on separate media and are installed using a supplemental data installer. Operating Requirements This section describes the software and hardware requirements for running MapMarker Canada Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the desktop application and MapMarker Software Developer Kit are: Dual Core processor or better 4 or more 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 The server application runs on the following operating systems: Microsoft Windows 2008 Server (32 bit and 64 bit) Microsoft Windows 7 (64 bit) Pitney Bowes 10 October, 2015

11 Microsoft Windows 8 (64-bit) Microsoft Windows 2012 Server (64-bit) 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 (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. The desktop application runs on Microsoft Windows only. It is a 32-bit application, but runs on 64-bit Windows provided that 32-bit binaries are used. This works by default, because the installer always configures 32-bit binaries. It runs on the following operating systems: Microsoft Windows 2008 Server (32 bit and 64 bit) Microsoft Windows 7 (64 bit) Microsoft Windows 8 (64 bit) JVM Requirements MapMarker Canada 15.0 requires a Java Virtual Machine (JVM). MapMarker CAN 15.0 ships with JVM 1.6 and also supports JVM 1.7 and 1.8. Database Support MapMarker Canada 15.0 supports the following ODBC databases and drivers. SQL Server 2008 SQL Server 2005 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) MapMarker Canada 15.0 also supports the following Oracle drivers. Oracle 11 Oracle 10G Release 2 Pitney Bowes 11 October, 2015

12 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 or higher. MapMarker Canada 15.0 ships with Apache Tomcat Supported Pitney Bowes Products MapMarker Canada 15.0 is compatible with the following products: Other MapMarker country products (USA, Australia, etc.) MapInfo Professional MapInfo AnySite MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server MapXtreme.NET MapMarker Canada is also the core geocoding component for the Spectrum Technology Platform: Fixes to Known Issues There are several customer-reported bug fixes included with MapMarker Canada Adding/Removing Columns. If you alter a previously mapped output column remove a column, for example the results are no longer written to the next available column. You have to remap to the desired output column. Previously, the results appeared incorrectly in the next available column. Opening a Text File with Duplicate Column Names. Opening a.txt file that contains duplicate column names now displays a message box that indicates a duplicate name is present. Closing the message box displays the Wizard page, from which you can address the issue by changing column names so that there is no duplication. Previously, opening a.txt file with duplicate names terminated the application. Pitney Bowes 12 October, 2015

13 Quebec City Aliases. Quebec, Québec, Quebec City, Québec City, and Ville de Québec are all now included as aliases for both NAVTEQ and TomTom. Previously, using either Quebec City or Québec City as a close match criterion did not yield a close match. However, using Quebec, Québec, or Ville de Québec did. Missing Accent Characters. Missing accent characters in an input address no longer cause a mismatch on street name. Previously, an address with an accent character like ÉDOUARD-MONTPETIT returned an exact street name match when the MustMatchMainAddr preference was true. However, if the accent character was missing and the MustMatchMainAddr preference was selected, the street name did not exactly match. Incorrect Postal Code. Candidates now all have the correct postal codes. Previously, some Toronto addresses returned a candidate with an incorrect postal code. Input Addresses with Postcodes. Input addresses with postcodes now return the most accurate candidates. Previously, in some cases, an input address with a postcode returned a less accurate candidate than an input address that had no postcode. SingleLine Relaxed Verses Custom Match Mode in GeocodeAddressGlobal. The custom match mode setting now returns the same, correct match code as the relaxed match mode setting. Previously, in some instances, the different match modes returned different match codes for the same address. Project File Batch Processing. In the desktop application, a pop-up message no longer interferes with batch processing project files. Previously, you had to click through a popup message during batch processing. Address Point Interpolation. When Address Point Interpolation is on, the geocoder now reviews lastline information from the NAVTEQ Points Address dataset to return the correct match code. Previously, in some instances, it had returned an incorrect code. Avenue prethoroughfaretype. Both formattedstreetaddress and prethoroughfaretype return Avenue as AV. Previously, prethoroughfaretype returned Avenue as AVE. Known Issues and Clarifications Shared Installation Location of Files After the administrator installs the desktop application as a shared application, each client user must then run the client desktop installation (ClientSetup.exe). The client users also must be able to access the shared data. Pitney Bowes 13 October, 2015

14 By default, the data is installed in the folder MapMarker_CAN_v15_Data. Under that folder, the DesktopInstaller folder contains the ClientSetup.exe. After completing the shared installation, the administrator can share the MapMarker_CAN_v15_Data folder (and the subordinate DesktopInstaller folder). Client users will then have access to everything that they need to perform a client installation and access shared data. 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 Configuring Tomcat as a Windows Service in the Deploying Applications chapter of the MapMarker Canada Version 15 Developer Guide. Using ODBC Data source: You must have administrator credentials to create a new ODBC data source. The user also must set up ODBC connections in advance. Reinstall Failure after Improper Uninstall: To properly uninstall MapMarker, you must run the Uninstaller. If you do not run the Uninstaller, but instead delete the MapMarker directories, you will not be able to routinely re-install the product. Contact Pitney Bowes Technical Support at software.support@pb.com for further assistance. UNIX / Linux-Related Issues On UNIX/Linux platforms, there are some installation and startup issues related to administrator rights. Pitney Bowes 14 October, 2015

15 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 will 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. Reinstall Failure after Improper Uninstall: To properly uninstall MapMarker, you must run the Uninstaller. If you do not run the Uninstaller, but instead delete the MapMarker directories, you will not be able to routinely reinstall the product. Contact Pitney Bowes Technical Support at software.support@pb.com for further assistance. 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 on the user's desktop. On UNIX/Linux systems, it is created in the user's home directory or at the root directory ( / ). Console Installation UNIX The MapMarker Developer product does not support console installations for UNIX or Linux operating systems. Run a silent install instead. See the Installation chapter in the MapMarker Canada Version 15 Developer Guide for more information. 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 MapMarker Canada Version 15 Developer Guide also describes this integration strategy. For demonstration purposes, this section describes the integration of MapMarker Canada 15.0 and MapMarker USA 28.0 and assumes 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. Pitney Bowes 15 October, 2015

16 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 CAN 15.0). 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 CAN 15.0 and MapMarker USA 28.0 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 CAN MapMarker USA Since MapMarker Canada 15.0 uses the newer core, it is easier to integrate files from the USA installation into the Canada Tomcat. Now follow these steps: 1. Identify the USA and Canada jar files and properties files. By default, these are in the folders: <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 USA installation into the corresponding CAN WEB-INF\lib\ folder: miscp.jar mmj_can.jar 2. Copy several properties and license files. By default, these are in the folders: <MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ <MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ Copy the following file from the MapMarker USA into the corresponding CAN WEB- INF\classes\ folder: USA_DataManagersettings.properties MMUSALicenseFactory.config Pitney Bowes 16 October, 2015

17 MMUSALicenseProvider.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, such as CAN and USA. A heap size of 1 GB is recommended for optimum performance for a CAN and USA integration. 4. Restart the CAN server and re-examine the Java Server Status report as described in Determining the Java Core Engine. The Product Version Information shows the MapMarker Java Core version (for example, The MapMarker Java Plugin Version Information near the bottom of the status report shows something similar to the following, confirming that both the CAN and USA products are installed in the same Tomcat. Plugin Version United States (USA) Canada (CAN) You can now geocode both American and Canadian addresses within the same Tomcat instance. 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 review the differences between the contents of the...\web-inf\lib and...\web-inf\classes folders.) For each country you wish to integrate into an existing Tomcat instance, 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 CAN and USA integration. On 32 bit systems, 1.5 MB is the maximum heap size. Larger heap sizes can be allocated on 64 bit systems. Pitney Bowes 17 October, 2015

18 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. Pitney Bowes 18 October, 2015