MapMarker Canada Release Notes

Transcription

1 MapMarker Canada Release Notes Canada: Phone: Fax: Sales: Technical Support: Technical Support Fax: United States: Phone: Fax: Sales: Government Sales: Technical Support: Technical Support Fax: Latin America: Phone: Fax: Sales: Technical Support: Latin America Support These Release Notes accompany the MapMarker Canada release. This provides information on new features, operating requirements, fixes for known issues, and other issues that may require your attention. This document should be used in conjunction with the MapMarker Canada v11 User Guide and Developer Guide. These Release Notes are also available on the Pitney Bowes Software web site. Related MapMarker documentation is on the Product Documentation page on the Pitney Bowes Software web site. Scroll to the CANADA heading to see these Release Notes and the MapMarker Canada v11 User Guide and Developer Guide. These Release Notes are cumulative and describe features, requirements, and issues related to MapMarker CAN v11 and subsequent point releases. Table of Contents Updated Installer for MapMarker CAN Data Availability and Vintages Operating Requirements Fixes to Known Issues Known Issues and Clarifications Europe/United Kingdom: Phone: Fax: Technical Support: Asia Pacific/Australia: Phone: Fax: Technical Support: 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. July, 2014

2 Updated Installer for MapMarker CAN The updated installer for MapMarker CAN installs JVM 1.6 by default. The installer also prevents you from selecting a JVM older than 1.6, because JVM 1.5 is no longer supported. See JVM Requirements on page 8. Data Availability and Vintages These Release Notes accompany the MapMarker Canada release. These Release Notes provide information on updated vintages for v These release notes also summarise the features, operating requirements, fixes for known issues, and other issues that were introduced with MapMarker CAN v11 and subsequent point releases. See Fixes to Known Issues on page 9. This document should be used in conjunction with the MapMarker CAN v11 User Guide and in the MapMarker CAN v11 Developer Guide. NAVTEQ Availability and Data Vintages TomTom Streets Dictionary NAVTEQ Point Addressing Dictionary Allow Centerline Offset for Point Address Dictionary Candidates Installing MapMarker CAN with NAVTEQ Data NAVTEQ Availability and Data Vintages NAVTEQ Points data was introduced with MapMarker CAN You can purchase and install the NAVTEQ point address dictionary in addition to the standard TomTom street segment address dictionary. Your license determines which address dictionaries you are authorised to use with MapMarker CAN. NAVTEQ availability is determined by your license, which is based on the serial number and unlock code that you receive from Pitney Bowes Software Customer Service. If you want to upgrade to MapMarker CAN with NAVTEQ Point Addressing data and you did not previously license NAVTEQ data with MapMarker, then you must uninstall and reinstall your MapMarker CAN software. See Installing MapMarker CAN with NAVTEQ Data on page 6 for details. If you have purchased NAVTEQ data, you will also receive a separate customer letter that explains this procedure NAVTEQ Point Addressing is provided on separate media and installed separately using a supplemental Data Installer. The MapMarker Data Installer document describes how to install, update, and configure additional address dictionaries. The MapMarker Data Installer document is available on the Pitney Bowes Software web site. The MapMarker CAN address dictionaries are updated quarterly and are based on data from the following sources. MapMarker CAN Data Sources and Vintages Data Source Vintage TomTom MultiNet Canada Data (March 2014) Canada Post Address Range Data (March 2014) Statistics Canada PCCF (Postal Codes) and FSA Boundaries (September 2013) MapMarker Canada Release Notes 2

3 MapMarker CAN Data Sources and Vintages (continued) TomTom Census Data Refresh Data Source Vintage (March 2014) based on Canada Census data of 2011 NAVTEQ Point Addressing 2014.Q2 The total size of the standard address dictionary for all provinces and territories is approximately 605MB.The NAVTEQ Point Addressing dictionary is approximately 288 MB In size. 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. TomTom Streets Dictionary The standard TomTom MultiNet street segment address dictionary has been updated to vintage. The TomTom Canada Dictionary Coverage table describes the number of records by province/territory. TomTom Canada Dictionary Coverage Province/Territory Total Records Change in Total Records Total Road Length (miles) Change in Total Road Length Alberta (AB) 400, , British Columbia (BC) 307,481-2,617 81, Manitoba (MB) 93, , New Brunswick (NB) 78,852 4,501 26, Newfoundland and Labrador (NL) 35, , Northwest Territories (NT) Nova Scotia (NS) 101,817 8,793 32, Nunavut (NU) Ontario (ON) 764,636 6, , Prince Edward Island (PE) 20,102 1,342-6,853 0 Quebec (QC) 532,211 5, , Saskatchewan (SK) Yukon (YT) Total 246, ,518 31,596 2,148 MapMarker Canada Release Notes 3

4 NAVTEQ Point Addressing Dictionary 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. 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 Canada Point Dictionary Coverage table describes the number of unique address points by province/territory. This includes both address records and Point of Interest (POI) records. The NAVTEQ Point Addressing 2014.Q2 data represents an increase of over 38,000 records compared to the previous data vintage. NAVTEQ Canada Point Dictionary Coverage Province/Territory Total Records Change from Previous Release Alberta (AB) 1,044,709 1,294 British Columbia (BC) Manitoba (MB) 220, New Brunswick (NB) 194, Newfoundland and Labrador (NL) 61, Northwest Territories (NT) 5,071 0 Nova Scotia (NS) 337,794 13,166 Nunavut (NU) 26 1 Ontario (ON) 3,081,370 24,585 Prince Edward Island (PE) 67, Quebec (QC) 1,673, Saskatchewan (SK) 142, Yukon (YT) 6,854 0 Total 7,681,261 38,824 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. For example, assume that both the NAVTEQ and TomTom 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 MapMarker Canada Release Notes 4

5 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 an 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 street segment dictionary. Significance of Dictionary Priority The NAVTEQ Point Addressing data source includes Points of Interest records and address records. The TomTom data source includes address records only. This means that duplicate address records can potentially exist (one from the NAVTEQ dictionary and one from the TomTom dictionary). 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 the Standard (TomTom) address 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. S8 Candidates do not return census information; census information is associated with the 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 overrides 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 CAN v11 Developer Guide. MapMarker Canada Release Notes 5

6 Allow Centerline Offset for Point Address Dictionary Candidates Centerline offset has been available with the NAVTEQ Point Addressing dictionary starting with MapMarker CAN If you geocode using the NAVTEQ Point Addressing dictionary in combination with the TomTom street segment dictionary, you can return the candidate at a specified offset distance from the associated street segment, rather than at the original point. When possible, the coordinates are offset perpendicularly from the associated street segment. If there is no street segment dictionary in addition to the NAVTEQ Point Addressing dictionary, then the original point candidate is returned. In the API, Centerline offset is supported with several GeocodingConstraints methods. The centerline offset capability is disabled by default, but you can enable and control it using the following GeocodeConstraints methods in the API. These methods can be changed at any time during the session. setusecenterlineoffset(boolean) setcenterlineoffset(double offset) setcenterlineoffsetunit(string unit) Set to true to specify that point candidates should be offset from the nearest segment (default is false). Specifies the offset distance from the segment toward the original point. The default value is 7.0. Specifies the offset distance units. The allowable units are: m, f, km, mi, in, yd, cm, and mm. The default value is m (meters). The returned candidate has an SC result code, indicating that the original point was offset from the nearest segment. The location precision is set to CandidateAddress.ADDRESS_POINT_PROJECTED (value of 18). The Desktop application supports the centerline offset feature through Center Line Offset preferences in the System Preferences dialog box. The option is disabled by default but you can check the Use Center Line Offset box to enable this feature and control the offset values and units (by default, the offset is 7 meters). Using Centerline Offset Centerline offset allows you to create points in a more precise and regular pattern that follows street contours. This could be preferable in some cases, such as for routing applications. Installing MapMarker CAN with NAVTEQ Data Generally, there is no special procedure for installing the NAVTEQ Points data. As long as you are licensed for the data, you can install and use NAVTEQ Point Addressing dictionary, in addition to the TomTom street segment address dictionary that is available by default. Similarly, if you already installed NAVTEQ data with a previous MapMarker CAN release, there is no special procedure for installing the NAVTEQ Point Addressing data. If you are an existing MapMarker CAN customer and did not previously install NAVTEQ Point Addressing data with a previous MapMarker CAN release, you must follow these steps to install MapMarker CAN with NAVTEQ Points. Uninstall your current version of MapMarker CAN Install MapMarker CAN Install the NAVTEQ Point Addressing Dictionary Uninstall your current version of MapMarker CAN 1. Begin the uninstall procedure as follows, depending on whether you are uninstalling on Windows or on UNIX/Linux. On Windows, select MapMarker Canada v11 from the Control Panel list of programs and select Uninstall or Change/Remove (depending on your version of Windows). On Solaris, Linux, or HP-UX, Run the shell script from the root of the media using the command: sh /opt/mapinfo/mapmarker_can_v11/uninstall_mapmarker_can_v11 2. In the Uninstall MapMarker Canada dialog, click Next. MapMarker Canada Release Notes 6

7 3. Select Complete Uninstall uninstall all of MapMarker CAN, then click Next. The uninstall program runs immediately and MapMarker Canada is completely uninstalled. 4. When the uninstall completes, click Done. Install MapMarker CAN You can install MapMarker CAN using the graphical installer interface or install silently without user interaction. Remember, a complete install of MapMarker CAN is necessary only if you are installing MapMarker CAN for the first time or if you are upgrading from a previous version of MapMarker CAN and using NAVTEQ Point Addressing data. If you are upgrading MapMarker CAN 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 CAN v11 User Guide or Developer Guide for instructions on performing a complete install of MapMarker CAN. During installation, enter the new serial number and unlock code that is valid for both the standard TomTom dataset and NAVTEQ Point Addressing dataset. The new license is created at install time for the datasets that you purchased. Install the NAVTEQ Point Addressing Dictionary The NAVTEQ Point Addressing dictionary is provided on separate media and is installed using the MapMarker Data Installer. The NAVTEQ data, the Data Installer, and PDF file that describes the data installation are included on your NAVTEQ data media. Operating Requirements This section describes the software and hardware requirements for running MapMarker CAN v11. 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 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 MapMarker runs on the following operating systems: Microsoft Windows XP Professional (32 and 64 bit) Microsoft Windows 2008 Server (32 and 64-bit Microsoft Windows 7 (64 bit) 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 4.0 and 5.0 (64-bit) Red Hat Linux 6.1 (64-bit) MapMarker Canada Release Notes 7

8 For Red Hat Linux 6.1 you must install all missing 32-bit system libraries, in addition to the default 64-bit libraries. This is the last release in which Microsoft Windows XP Professional (32-bit and 64-bit) and Red Hat Linux 4.0 will be supported. 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 2008 Server (32 bit and 64 bit) Microsoft Windows 7 (64 bit) Microsoft Windows 8 (64 bit) JVM Requirements MapMarker v11 requires a Java Virtual Machine (JVM). MapMarker CAN 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 CAN Java 1.5 is not supported for this release. For more details, see Choosing the Java VM During Installation on page 11. Database Support MapMarker CAN v11.11 supports the following ODBC databases and drivers. SQL Server 2008 SQL Server 2005 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) 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. MapMarker Canada Release Notes 8

9 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 CAN v11.11 ships with: Apache Tomcat 6.0 Tomcat 5.5 is still supported. Supported Pitney Bowes Software Products MapMarker CAN v11.11 can integrate 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 CAN is also the core geocoding component for the Spectrum Technology Platform: Fixes to Known Issues There are several software fixes for MapMarker CAN There were also a number of enhancements or fixes were made in previous point releases of MapMarker CAN v11. These earlier software fixes are included in this document to provide cumulative Release Note coverage for all MapMarker CAN post 11.0 releases. Changes for MapMarker CAN v11.11 Single line address with country code at end of line returns no candidates. An address like Ave Calgary AB CAN fails to return a candidate. If the CAN country code is omitted, the correct candidate returns as expected. This has been fixed, and the country code on single line input no longer interferes with correct geocoding. MMPC-583 Single line address with street directional fails to geocode An address like st W Prince Albert SK fails return a candidate. The is related to the missing space between 16 and st. This has been fixed, and addresses like this are now recognized regardless of whether there is a space following the numbered street. MMPC-587 Street number is returned as close match even though number was not specified on input. An address like Quebec St, Toronto, ON, M6K3C3 returns a close match to 70 QUEBEC ST, TORONTO, ON, M6K 3C3 with an S8 result code. However, the address 70 was not specified and there are many other address numbers on the same street. This has been fixed and this return is now an S4 candidate. MMPC-584 One close match returned when several other good candidates are discarded. For example, the input address 21 BYNG AVE, Toronto, ON returns one close match candidate when there are several other equally close matches in Scarborough, Etobicoke & North York (which have all been consolidated into Toronto). This happens when no postal code is specified on input. This has been fixed. The candidate from the preferred dictionary is returned as the first close match, but candidates from the second (non-preferred) address dictionary are now also returned. MMPC-585 Changes for MapMarker CAN 11.6 Improved reverse geocoding results. Reverse geocoded candidates now return the exact latitude / longitude coordinates of the candidate, not just the input coordinates. Along with this, the coordinate system (EPSG code) and the location precision value (a numeric value of 1, 2, or 16) are also returned for reverse geocoded candidates. MapMarker CAN 11.6 was the first release to reflect the updated 2011 Canadian census information. MapMarker Canada Release Notes 9

10 Changes for MapMarker CAN 11.4 Reverse geocode candidates do not return city and postcode. when reverse geocoding returns an RS4 candidate, the city and postcode are not returned with the candidate. This has been fixed and the complete candidate information is now returned. Reverse geocode returns two candidates when it should return only one. Under some circumstances, a reverse geocode returns two candidates when only one is expected. This has been fixed and only the single correct candidate is now returned. Changes for MapMarker CAN 11.3 NAVTEQ Points Data Introduced. The NAVTEQ Point Addressing dictionary was introduced. NAVTEQ data for Canada is separately licensed. Upgrade install problem with Solaris. On the Solaris platform, upgrade installations (such as from v11.0 to 11.1) produced an error when you attempted to start the server. This has been resolved with the v11.11 installer and no workaround is required. Addresses with two street types do not return close match. Some addresses with two possible street type were not geocoded correctly. For the address 3035 Boulevard le Carrefour, Laval, QC H7T 1C7, both Boulevard and Carrefour can be street types. In this example Carrefour was misinterpreted as the street type and the close match was missed. Similarly, 1 Promenade Circle Thornhill, ON L4J4P8 was missed as a close match. This has been resolved. Incorrect unit value returned when input has #unit-housenumber format. When the input address has the specific format of #unit-housenumber, the returned unit value is not correct. For example, the input address # Steeles Ave East Willowdale ON M2H3P1 returns a candidate with a unit value of , rather than the correct unit value of 520. This was a rare occurrence, but has been fixed. Changes for MapMarker CAN 11.0 Wrong candidate returned when suite number is omitted from input. For the address: 20 Bay Street, Toronto ON, M5J 2NL a close match is returned but with the wrong LDU. If the suite number is included, a candidate with the correct 2NL LDU is returned. The correct LDU candidate should be returned whether or not the suite number is included on input. This has been corrected. Unit type NO does not return candidates. An address like: Ave NW NO 304 does not return the expected close match candidate. This has been fixed and the NO unit type is now handled properly Silent installation fails to install some province data. The silent installer fails to install licensed data for several provinces. This has been fixed. Close match not returned when an invalid postcode format is supplied. If an otherwise valid address is input with an invalid postcode format, no candidate is returned. For example, the address: 2080 United Blvd, BC, 00V3K fails to geocode. But if the postcode is input as V3K, the expected candidate is returned. This has been fixed and the expected close match candidate is now returned. False positive candidate returned for some addresses. In some cases, a non-existent address returns a close match. For example, the address 1045 East Ave, Toronto, ON returns a false positive match. This and some related cases of false positive returns have been resolved. Address like 15 La Rose Ave. returns wrong candidate. The La is not properly recognised as part of the street address., so a candidate on Rose Ave (instead of La Rose Ave) is returned. This has been fixed and an address like this is now handled correctly. Best candidate is missed when input street directional is wrong. For the address: 19 Woodlawn Rd W Guelph, ON, N1H 7B1, the top returned candidate has an LDU of N1H 1G8. A better candidate is 19 WOODLAWN RD E Guelph, ON N1H 7B1. Even though the street directional is different, the matching FSA/LDU is a better close match candidate. This has been fixed and the matching LDU candidate is returned as a close match. MapMarker Canada Release Notes 10

11 Rural route number is sometimes returned as unit number. For example, for the input address 4090 GUELPH LINE RR #1, the number 1 is returned as a unit number rather than rural route number. This has been corrected and a valid rural route number is now recognised and returned with the matching candidate. If the rural route number is not valid for the address, then the RR number is discarded. Street and Rue thoroughfare types handling. ST and RUE are now considered equivalent and MapMarker CAN can return a close match regardless of whether Street or Rue is input as a prethoroughfaretype or postthoroughfaretype. For example, if the user enters 1 rue Main but the official Canada Post address is 1 Main St, MapMarker CAN v11 returns the official 1 Main St as a close match. This is true even if the Must Match Street constraint is selected. Similarly, AVE/AV and BLVD/BOUL are considered equivalent as a pre or postthoroughfaretype. For example, input of either 3 Main Ave or 3 Ave Main returns the official address of 3 Ave Main. Note that BD is not the correct abbreviation for Boulevard and will be corrected to BLVD. NAVTEQ data vintage information in desktop. Starting with the MapMarker CAN v11 Desktop application, the Help > About MapMarker dialog displays data source and vintage information. Known Issues and Clarifications This section describes provides information specifically related to Windows and UNIX/Linux platforms. This section also provides information and workarounds related to several known issues. Choosing the Java VM During Installation When installing MapMarker CAN 11.11, the default action allows you to select a valid JVM that already resides on your system. The installer prevents you from selecting an unsupported JVM 1.5 or older version. You can also select the option to install the JVM 1.6 that is packaged with your product. 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 to the shared data. By default, the data is installed in the folder: MapMarker_CAN_v11_Data. Under that folder, the DesktopInstaller folder contains the ClientSetup.exe. After completing the Shared installation, the administrator can share the MapMarker_CAN_v11_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. MapMarker Canada Release Notes 11

12 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 Developer Guide. Using ODBC Data source: You must have administrator credentials 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. Contact Pitney Bowes Software 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. 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 did not run the Uninstaller, but instead deleted the MapMarker directories, you will not be able to routinely reinstall the product. Contact Pitney Bowes Software Technical Support 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 will be 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 Developer Guide for more information. Silent Uninstall on Windows XP Silent uninstall on Windows XP does not clean up all folders and registry keys. After the uninstall is completed, you must manually remove the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Mapinfo\MapMarker\CAN\11\GEOCODING\RequireProvince 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 CAN and MapMarker USA v26 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. MapMarker Canada Release Notes 12

13 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 11.11). 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 and MapMarker Canada v11.11 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 v Since MapMarker CAN uses the newer core, it is easier to integrate files from the USA installation into the CAN tomcat. Now follow these steps: 1. Identify the USA and CAN 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. You must also 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 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. MapMarker Canada Release Notes 13

14 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 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 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. 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 Canada Release Notes 14