MapMarker USA v24.1 Release Notes

Transcription

1 MapMarker USA v24.1 Release Notes United States: Phone: Fax: Sales: Government Sales: Technical Support: Technical Support Fax: pbinsight.com These Release Notes accompany the MapMarker USA v24.1 release. This provides information on new features, behavioral changes in the software, fixes for customer-reported issues, and known issues that may require your attention. These Release Notes and related MapMarker documentation appear on the MapMarker Product Documentation page on the Pitney Bowes Business Insight web site. The USA 24.x documentation appears under the USA heading. Release Notes appear on the web site only. Other documentation is provided on media also. Release Notes may be updated as new information becomes available. Any updated Release Notes will be posted to the web site with an indication of the revision date. Canada: Phone: Fax: Sales: Technical Support: Technical Support Fax: pbinsight.ca Europe/United Kingdom: Phone: Fax: Technical Support: pbinsight.co.uk In these release notes: MapMarker v24.1 Updates MapMarker v24 New Features and Enhancements Operating Requirements Fixes to Known Issues Installation-Related Corrections and Clarifications Known Issues and Clarifications Asia Pacific/Australia: Phone: Fax: Technical Support: pbinsight.com.au These Release Notes are cumulative, and describe features, requirements, and issues related to MapMarker USA v24 and MapMarker USA v 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. October 2011

2 MapMarker v24.1 Updates The v24.1software update includes fixes for the following issues. Under some circumstances, the Desktop Application could hang when you attempted to open a text file in MapMarker USA This issue and fix is described in Desktop hangs when opening text file.when you open a text file that has a line with an unmatched single or double quote, the Desktop Application will hang. For example, the Desktop Application hangs if you open a text file with an address like: Pablo s Pizza, 319 Main St, Grand Junction CO. This has been fixed. on page 13 MapMarker USA v24.1does a better job of handling some non-standard address input. See Handling some types of non-standard address input. on page 13. MapMarker USA v24.1also includes the following data and software changes. TomTom Rebranding New Data Vintage New GeoStan Jar File TomTom Rebranding The Tele Atlas data set has been rebranded as TomTom. The dataset name can appear in several places in the Desktop Application. In MapMarker USA v24 this was identified as Tele Atlas. In v24.1 this has been updated to TomTom. The TomTom rebranding impacts several areas of the Desktop Application: The About MapMarker dialog displays information about the available data sources and vintages. This dialog appears when you click Help > About MapMarker from the Desktop Application. The Quick Find geocoding candidate list includes a column that identifies the data source from which the street geocoded candidate was returned. Anywhere else that the data vendor name appears associated with the name of the Address Dictionary or data source. Note that while the Desktop Application has been updated to reflect the TomTom rebranding, the accompanying documentation and online help has not been updated for this v24.1 point release. New Data Vintage By default, the TomTom Streets address dictionary is included with MapMarker USA v24.1.you can also purchase and license supplemental address dictionaries. The following Address Dictionaries are available for use with MapMarker USA v24.1: TomTom Street data. In addition to Tele Atlas quarterly updates, you have the option of receiving monthly updates for any licensed address dictionary. Updates are referred to by the month name, such as: MapMarker USA v24.1 October, 2011 (2011_10) data update. TomTom Points data (2011_10). Centrus Points data (2011_10). NAVTEQ data (2011_10), available as primary or secondary address dictionary. See the PBBI web site for more detailed information on the U.S Geocoding Data Sets. Standard non-cass data expires six months from the USPS data vintage month. Data with a vintage of October, 2011 (2011_10) expires on April 1, For this release with data vintage 2011_10, the CASS expiration date is February Contact your sales representative for more information on purchasing additional data sets and for establishing a monthly update schedule. MapMarker USA v24.1 Release Notes 2

3 New GeoStan Jar File The installed GeoStan jar file has been updated to reflect the underlying GeoStan engine. This jar file is named geostan jar (compatible with MapMarker USA v24.1). The number is incremented for each software update. The geostan jar file is installed in the following places: <Install_Folder>\Desktop\ <Install_Folder>\sdk\engine\lib\server\ Make sure that your classpath includes a path to this new jar file. MapMarker v24 New Features and Enhancements The following items reflect the features, requirements, and changes that were introduced with MapMarker USA v24. These items were described in the MapMarker USA v24 Release Notes, but are summarized here for convenience. Unless otherwise noted, this information is unchanged from the v24 Release Notes. These features are fully covered in the appropriate sections of the MapMarker v24 User Guide and in the MapMarker v24 Developer Guide. Extended Data Expiration CASS and Suite Link Changes New Search Levels for Finance Area and City Improved Context Menu in Quick Find Dialog New Match Codes and Location Codes Identify the Data Source for Candidates Improved Text File Support Miscellaneous Enhancements Oracle Cartridge Update Improved Description of Match Modes Extended Data Expiration With the release of MapMarker USA v24, the standard data expiration period is extended to six months from the USPS data vintage month. For MapMarker USA v24.1, the data vintage October, 2011 (2011_10) expires on April 1, There is also an improved data expiration message. See Improved error message for data expiration on page 14. For this release with data vintage 2011_10, the CASS expiration date is February 1, Contact your sales representative for information on CASS data. CASS and Suite Link Changes MapMarker USA is certified for USPS CASS Cycle N. The new CASS Cycle N replaces the expiring CASS Cycle M. Suite Link is now required by the USPS for CASS reporting. Previously, you could generate CASS reports without using Suite Link. Note that you can still use CASS Mode with or without Suite Link. Only the CASS reporting feature is subject to the Suite Link USPS requirement. Suite Link is the USPS business name database that provides suite numbers for businesses located in high-rise buildings. This allows delivery sequencing where it would not otherwise be available. MapMarker USA v24.1 Release Notes 3

4 We are continuing to provide Suite Link free of charge, but you must request this data from customer service. This dataset is provided on a separate Centrus SuiteLink media and must be copied from the media into the Data directory (typically <Install>MapMarker_USA_24_Data). To add Suite Link files to your MapMarker USA installation, do the following: 1. Insert the MapMarker SuiteLink Vintage 2011_10 media into your drive. 2. Open the ASCII folder and copy the file in that folder into the MapMarker USA v24 Data directory (typically <install>/mapmarker_usa_24_data). Copy the file only, not the folder. Disregard any other folders on the media. Only the contents of the ASCII folder are required. New Search Levels for Finance Area and City You can specify if you want the search area based on one of three search levels (finance area, city, or search radius). Matched candidates must then be located within the specified area. By default, search level is disabled, but if enabled, the default is city level. See the Finance Area Search Level, City Search Level, and Expanded Search Level for a complete description of these search levels. The Desktop application supports these search levels for automatic geocoding, interactive geocoding and for Quick Find. Finance Area Search Level A Finance Area is an area defined by the U.S. Postal Service from which it collects cost and statistical data. A finance area is a collection of ZIP Codes within a contiguous geographic region and can contain more than one ZIP Code or city. When you specify the finance area search level, MapMarker searches the entire finance area for possible streets. This search level can be used with street address geocoding only (not with postal or geographic geocoding). If you are using CASS mode, the finance area level is enabled by default. For other match modes, city search level is used by default if no other search level is specified. City Search Level When you specify the City search level, MapMarker limits the search to streets within the specified city. Expanded Search Level Expanded search allows MapMarker to expand the search to a given radius (up to 99 miles) from the input address. You can also limit the expanded search to the same state of the input address, regardless of the mile radius. Expanded search helps to find a match when the input address contains limited or inaccurate city or ZIP Code information. Expanded search was already available with previous versions of MapMarker USA. The Finance Area and City search levels are newly introduced with MapMarker USA v24. Desktop Application Support The Desktop application Geocode dialog and Quick Find Settings dialog support the Search Level options of expanded search, finance area search, and city search. API Support You can also enable and control search levels using the setsearchlevel method in the API. This method can have three possible values and can be changed at any time during the session. The table of Search Level Constraints summarizes the API methods. MapMarker USA v24.1 Release Notes 4

5 Search Level Constraints setsearchlevel Method The available SearchLevel constants are in USA_GeocodeConstraints.SearchLevel setsearchlevel Setting Set to Finance_Area to perform street level geocoding within the Finance Area in which the input street is located. See Finance Area Search Level. allowed values for KEY_SEARCH_LEVEL SEARCH_LEVEL_FINANCE_AREA SEARCH_LEVEL_CITY SEARCH_LEVEL_EXPANDED Set to City to perform street level geocoding within the city that the input street is located. See City Search Level. If expanded search is enabled, the following methods can be used. Set to Expanded to perform street level geocoding using expanded search. See Expanded Search Level. setexpandedsearchradiusinmiles (up to 99 miles) setexpandedsearchlimittostate (true/false) Expanded search was introduced with MapMarker USA v23 and was enabled with the setuseexpandedsearch method. The setuseexpandedsearch method has been deprecated in v24 and replaced by the setsearchlevel method with the SEARCH_LEVEL_EXPANDED value. Improved Context Menu in Quick Find Dialog The Desktop application Quick Find context menu provides more flexibility in copying the complete candidate address or just the coordinates. To see the available options, right click on the candidate. You can now choose to copy the X or Y coordinates only and or copy both coordinates, in either order. The coordinates are now copied to your clipboard without parentheses or other punctuation. This makes it more convenient to subsequently paste the coordinates into another application. You can also select Show Status Code Details to display the Status Codes dialog with tabs for GeoResult Code, Match Code, and Location Code. The ability to display Match codes and Location codes in the Desktop application is a new feature for MapMarker USA v24. See New Match Codes and Location Codes. Candidate Copy Options Desktop Candidate Copy Option Show Status Code Details Copy Address Copy Coordinates as LAT/LONG Copy Coordinates as LONG/LAT Copy Latitude Only Description Display the Status Codes dialog. Copy complete address. Copy coordinates in the order Y/X. Copy coordinates in the order X / Y Copy Y coordinate only. MapMarker USA v24.1 Release Notes 5

6 Candidate Copy Options (continued) Desktop Candidate Copy Option Copy Longitude Only Copy All Copy X coordinate only. Description Copy result code, location and match codes, complete address, and coordinates. New Match Codes and Location Codes In addition to the familiar MapMarker result codes, MapMarker USA v24 returns Match codes and Location codes in the Desktop application and in the API. These codes provide a great deal of information on how each candidate was matched and the accuracy of the candidate match. This information can help you evaluate the overall quality of the matched candidates. The underlying geocoding engine returns Match codes and Location codes in MapMarker USA v24. These codes are now fully described and documented. Match codes indicate the parts of the address matched and identify which address elements were changed to achieve the match. Location codes indicate the locational accuracy of the assigned geocode. Note that an accurately placed candidate is not necessarily an ideal candidate. For example, if both the input street name and postal code were changed in order to achieve a match, a candidate with a high locational accuracy may not be desirable. Examine the match codes and result codes in addition to location codes to best evaluate how suitable the candidate is, based on your business application requirements. Match codes and Location codes are described in an appendix of both the MapMarker USA v24 User Guide and the MapMarker USA v24 Developer Guide. These Match Codes and Location Codes are also returned by the Java API. New Status Codes Dialog for Match and Location Codes In the Desktop application, the Quick Find dialog returns Match Codes and Location Codes in separate columns. For table geocoding (automatic or interactive), the codes are returned if the appropriate output address columns are mapped. To display the Status Codes dialog, double-click the candidate s GeoResult, Matchcode, or Locationcode in the geocoded output table. The Status Codes dialog includes corresponding tabs for GeoResult Code, Match Code, and Location Code. The appropriate information appears under each tab. You can also display the Status Codes dialog from the Interactive Geocode dialog by right-clicking a candidate and selecting Show Status Code Details from the context menu. Similarly, from the Quick Find dialog you can right click a candidate from the list and select Show Status Code Details. MapMarker USA v24.1 Release Notes 6

7 The following dialog shows Match Code details for a selected candidate: The following shows the Location Code details for the same candidate: The GeoResult Code tab shows the familiar MapMarker result codes (for example, S8HPNTSCZA for a perfect match from a point dictionary) along with match details for each record. MapMarker USA v24.1 Release Notes 7

8 Identify the Data Source for Candidates Returned candidates can now identify the datasource from which the candidate was returned. The datasource is identified by a number or a corresponding descriptive string, as shown in the Datasource Numbers and Names table. Datasource Numbers and Names Datasource Number Datasource Name 0 USPS data 1 TIGER data 2 TomTom data 6 NAVTEQ data 7 TomTom point-level data 8 Centrus point data 10 User Dictionary For table geocoding (automatic or interactive), the Datasource type output address column must be mapped if you want that information to be returned. In the Desktop application, the Quick Find and Interactive dialogs return the descriptive DataSource Name (as shown in the Datasource Numbers and Names table). For automatic geocoding (or in the API), the Datasource Number is returned, because the number is more suitable for batch processing and programmatic use. Database source information is returned for street geocode candidates only. Postal and geographic candidates do not return this information. Improved Text File Support The Text File Wizard workflow has been revised to improve usability, eliminate unnecessary warning messages, and allow more flexibility when you change selections in the wizard. Some related text file handling bugs have been fixed. Candidates returned from geocoded text files now include more information: Match Codes and Location Codes (See New Match Codes and Location Codes) DPV NoStat and Vacancy codes SuiteLink code Data source (See Identify the Data Source for Candidates) The Match Codes and Location Codes are returned for candidates from automatic geocoding, interactive geocoding and for Quick Find results. Miscellaneous Enhancements MapMarker USA v24 includes several smaller enhancements that you should be aware of: Quick Find now supports candidate visualization for postal candidates. Previously, candidate visualization in Quick Find was possible only for street geocoded candidates. The County name can now be returned as output for street, postal, or geographic candidates. Previously, only geographic candidates could return the county name. MapMarker USA v24.1 Release Notes 8

9 Oracle Cartridge Update The MapMarker Geocoding Extender Cartridge for Oracle has been updated to support many newer MapMarker features. Among the new features supported by the updated Oracle cartridge are: Match Modes Address Point Interpolation Wide Search Centerline Offset You can request the updated MapMarker Geocoding Extender Cartridge for Oracle from Pitney Bowes Business Insight Customer Service at Oracle 11 is also supported. See Database Support on page 12. Improved Description of Match Modes MapMarker USA v24 provides the following match modes. This information has been updated to provide more detailed and specific descriptions. See the following Match Modes table. Match Modes Desktop Application Mode Equivalent API Mode Description Standard Default This is the default mode, and generally provides the best balance of accurate geocoding, few false matches, and high performance. This requires a close (not necessarily exact) street name match. This is the default geocoding mode when you start MapMarker USA v24. Tight Exact This uses the most strict matching rules and requires an exact street name match. In general, this returns the fewest number of candidates in the fastest processing time. There will be fewer non-close matches than are returned in Standard or Relaxed mode. Tight (Exact in the API) is most suitable when your input addresses are complete, well standardized, and free of spelling errors. Tight mode is not equivalent to selecting Custom matching with all Exact Match criteria selected (House Number, Street Name, City Name, and ZIP Code). MapMarker USA v24.1 Release Notes 9

10 Match Modes (continued) Desktop Application Mode Equivalent API Mode Description Relaxed Relaxed This provides less strict matching rules. In general, Relaxed mode increases your chances of getting a close match but performance (geocoding speed) may not be as good. Relaxed mode: allows the most variation in street name spelling, and therefore may return desirable candidates that are not returned in other modes. is most suitable when your input addresses are not well standardized, incomplete, or may contain spelling errors. is the only mode that does not respect street parity. is more likely to return false positive candidates. may (but does not always) return more candidates than other modes. generally will perform more slowly than other modes. is best used as a second or third geocoding pass. The User Guide describes several multiple pass strategies for optimizing match rate. is best used if you examine the Match codes and Location codes to verify how the address was matched, what address elements were changed to achieve the match, and the locational accuracy of the assigned geocode. Relaxed mode is not equivalent to selecting Custom matching with all Exact Match criteria unselected. CASS CASS This provides strict conformity to USPS CASS regulations for CASS software. Use CASS mode to standardize your input for mailing. If you select CASS Mode, several other options are disabled and their values are overwritten by CASS rules. CASS mode requires a close name match. Unlike other modes, CASS does not match intersection addresses, building name, or street aliases. CASS also does not match based on a user dictionary or any data source that does not have USPS equivalent records. In other modes, a close match candidate may by identified very quickly and this candidate is returned without further processing. However, in CASS mode, the first identified close match may not be the best USPS candidate (for example it could be a building name while the preferred USPS candidate is a business name). A CASS mode search must continue to ensure that the best USPS candidate is returned. For this reason, CASS mode can return more records than in other modes. MapMarker USA v24.1 Release Notes 10

11 Match Modes (continued) Desktop Application Mode Equivalent API Mode Description Custom Custom Custom allows you to select any combination of Exact Match constraints rather than relying on any of the match mode algorithms. This gives you very precise control over the matching. House Number. If selected, a candidate must match the building/house number in order for it to be considered a close match. Street Name. If selected, a candidate must match the street name in order for it to be considered a close match. City Name. If selected, a candidate must match the city name in order for it to be considered a close match. ZIP Code. If selected, a candidate must match the ZIP Code in order for it to be considered a close match. Note that requiring all constraints is not equivalent to Tight mode. Similarly, requiring none of these constraints is not equivalent to Relaxed mode. Operating Requirements This section describes the hardware, memory and other requirements for MapMarker USA v24. These requirements are unchanged from v24. Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the Desktop Application and MapMarker SDK are: 1 GB RAM 5 GB available disk space (including 4GB for entire U.S. Address Dictionary) For optimal performance of a full installation of both the Desktop Application and MapMarker SDK we recommend: Dual Core processor or better 2 or more GB RAM 10 GB available disk space Supported Operating Systems MapMarker runs on the following operating systems: Microsoft Windows XP Professional (32 and 64-bit) Microsoft Windows 2003 Enterprise Edition Microsoft Windows Vista Ultimate Edition (32 and 64-bit) Microsoft Windows 2008 Server Microsoft Windows 7 Solaris 2.9 and 2.10 HP-UX 11 Red Hat Linux 4.0 and 5.0 SUSE Linux 9, 10 and 11 For Unix platforms, MapMarker supports 32-bit systems only. MapMarker USA v24.1 Release Notes 11

12 Desktop Application The Desktop Application runs on Microsoft Windows only. The Desktop is a 32-bit application, but runs on 64-bit Windows providing that 32-bit binaries are used. This works by default, because the installer always configures 32-bit binaries. Microsoft Windows XP Professional (32 and 64-bit) Microsoft Windows 2003 Enterprise Edition Microsoft Windows Vista Ultimate Edition Microsoft Windows 2008 Server Microsoft Windows 7 (64-bit) JVM Requirements MapMarker 24 requires a Java Virtual Machine (JVM). The following JVMs are supported: JVM 1.5 and 1.6 MapMarker USA v24 ships with: Sun JRE 1.5.0_09 (for Microsoft Windows and Sun Solaris) HP JRE _04 (for HP-UX) Sun JRE 1.5.0_11 (for Linux) 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. Note that if you install a 64-bit version of MapMarker USA v24 you must also use a 64-bit JVM. Under high loads, MapMarker server may experience performance degradation with JVM 1.5.0_04 or earlier. For this reason, we recommend that you use JVM 1.5.0_05 or later when high server performance is required. Database Support MapMarker USA v24 supports the following ODBC databases and drivers. SQL Server 2008 SQL Server 2005 SQL Server 2000 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) Microsoft Access 2003 Microsoft Access 2000 MapMarker also supports the following Oracle drivers. Oracle 11 Oracle 10G Release 2 You must install the Oracle driver separately. To use the driver, you must have the Oracle client installed. Supported Web Application Servers The MapMarker server allows you to develop geocoding applications on any Java Platform, Enterprise Edition (Java EE) application server that supports JDK 1.5 or JDK 1.6. MapMarker USA v24 ships with: Apache Tomcat 5.5 MapMarker USA v24.1 Release Notes 12

13 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 (print shared library dependencies) command. For example, to identify the library dependencies for MapMarker USA v24, on a Linux, Solaris, or AIX system, run: ldd libgeostanmt.so The equivalent command on HPUX systems is: ldd libgeostanmt.sl Supported PBBI Products MapMarker USA v24 can integrate with the following products: Other MapMarker country products (Canada, Australia, etc.) MapInfo Professional MapInfo AnySite Envinsa MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server MapXtreme.NET version Fixes to Known Issues The following sections describe incidents and bug fixes for Version v24.1 Issues and for Version 24.0 Issues. Version v24.1 Issues The following incidents were addressed in MapMarker USA v24.1. Desktop hangs when opening text file.when you open a text file that has a line with an unmatched single or double quote, the Desktop Application will hang. For example, the Desktop Application hangs if you open a text file with an address like: Pablo s Pizza, 319 Main St, Grand Junction CO. This has been fixed. Handling some types of non-standard address input. MapMarker USA v24.1 has made improvements in handling some types of non-standard address input. This improves the chances of successfully geocoding some input addresses that are not formatted according to addressing standards. Version 24.0 Issues The following incidents were addressed in MapMarker USA 24.0 and were previously covered in the v24 Release Notes. Unable to switch dictionaries in Desktop application. In the Desktop application, attempting to switch dictionaries using System Preferences dialog has no effect. After entering a different dictionary path, the system reverts to the. original dictionary. This has been fixed. The changed dictionary path is now honored. Changing the Match Mode resets exact match and additional settings. When you change a Match Mode, the user s exact match and additional settings revert to the values they had when the dialog was first opened. This has been fixed. The user settings now persist as they should. MapMarker USA v24.1 Release Notes 13

14 Abbreviated Saint fails to match. In some cases, when Saint is abbreviated as St on input, no close match is returned. For example: 97 St James Ave, Chicopee, MA does not return a close match. If Saint is used instead of the St abbreviation, the correct candidate is returned. This has been improved and St is now handled properly in most cases. There still may be some instances in which the Saint abbreviation is not handled. Ordinal street name fails to match if data has spelled out street name. n some cases, if a street ordinal is used on input but the data source has the number spelled out, no candidate is returned. For example: 19 1st St, Colchester, VT returns no matches. But 19 First St does return a close match. This has been improved and the ordinal in a street name is now handled correctly in most cases. There still may be some instances in which the ordinal is not handled. Exception thrown with all Must Match options on, Postal fallback, and non-existent ZIP Code. This problem can only happen if all Must Match constraints are true and a non-existent ZIP Code is input. This has been fixed. With both postal and geographic fallback enabled, geographic fallback fails when invalid postal code is input. For example, the input address: 512 Miller Street; Enfield; IL; fails to return a geographic fallback candidate because the postal code does not exist. This has been fixed. Improved error message for data expiration With MapMarker USA v23, standard Address Dictionary data expired 135 days after the 15th of the USPS data vintage month. If your data expired, MapMarker USA would not initialize and the error message did not adequately describe the expiration problem. This has been fixed. If your data has expired, you will now see the message: Unable to initialize. One or more data dictionaries has expired. Note that for MapMarker USA v24, the data expiration period has been increased. See Extended Data Expiration on page 3 for a description of this change. Help About dialog does not properly display all available dictionaries. For example, with three address dictionaries configured, the Help About dialog listed the Centrus Point dictionary (twice) and fails to list the other address dictionaries. This has been fixed. Non-close match candidates are improperly flagged as close match. In some cases with multiple address dictionaries configured, the Desktop application Quick Find dialog mistakenly displays a non-close match as a close match, as indicated by a green check mark in the candidate list. This has been fixed. Only the one correct candidate is now returned as a close match. Data installer incorrectly reports not enough space to install data. The data installer does not look in the correct place to evaluate space availability, and therefore can report inadequate space for data installation. This has been fixed. Duplicate columns in CSV file are not handled. If an input CSV file has duplicate (identically named) columns and you specify First Line Used for Column Titles, MapMarker crashes after step 1 of the Text File Wizard. If the first line of the text file is treated as data, MapMarker fails in step 2 of the wizard. You will now receive a warning message that duplicate column names must be eliminated. User Dictionary Utility is not accurately documented. The previousmapmarker USA Developer Guide does not accurately describe the procedure for creating a user dictionary via the User Dictionary Utility. Also, the procedure for creating a point-based user dictionary was not covered. The MapMarker USA v24 Developer Guide has been updated and corrected. See also Creating a Point User Dictionary with the User Dictionary Utility on page 17 in these Release Notes. Installation-Related Corrections and Clarifications This section corrects some and provides some additional information regarding installation of MapMarker USA v24.1. Unless otherwise noted, this information is unchanged from the v24 Release Notes. License File Location and Use The MapMarker 24 license file is provided on the media accompanying the MapMarker 24 release. The Server license file is named mmusa24.lic and the Desktop application license file is named mmusa24d.lic. Before you begin the installation procedure, copy the appropriate license file to your local hard drive. MapMarker USA v24.1 Release Notes 14

15 During installation, the license file is copied from your local drive into the MapMarker Data folder (MapMarker_USA_24_Data). The license file remains in that folder after an uninstall. If you get a new license file (for example if you acquire new data after your initial MapMarker installation) you can simply replace this file. EWS File Location and Use In previous releases of MapMarker USA, the Early Warning System (EWS) TAB file was included in your installation. With MapMarker USA v24, the TAB file is no longer necessary or shipped. In its place, we are providing a text file named ews.niu and installing it in the Data folder. If you want to use EWS processing, rename this file as ews.txt. Otherwise EWS will not be used. The Desktop application no longer provides the Use EWS file option in the Match Setting dialog. EWS processing is enabled or disabled based solely on the presence or absence of the ews.txt file. 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 v24.1 and MapMarker Canada v11 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. 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 v24.1 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 v24.1 and MapMarker Canada v11 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 Since MapMarker USA v24.1 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 CAN-specific jar files and properties files. By default, the locations are: <MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib <MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\lib Copy the following files from the MapMarker Canada installation into the corresponding USA WEB-INF\lib\ folder: miscp.jar mmj_can.jar MapMarker USA v24.1 Release Notes 15

16 2. You must also copy several properties and license files. By default, these are in: <MM_CAN_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ <MM_USA_install>\sdk\tomcat\webapps\mapmarker40\WEB-INF\classes\ Copy the following files from the MapMarker Canada installation into the corresponding USA WEB-INF\classes\ folder: CAN_DataManagersettings.properties MMCANLicenseFactory.config MMCANLicenseProvider.config 3. Verify that the Tomcat server allocates at least 512 MB of RAM. Open catalina.bat (or catalina.sh for Solaris) in: <Install>\sdk\tomcat\bin and look for the entry: set CATALINA_OPTS= -mx512m -server The maximum heap size should be at least 512 MB. This should be adequate for most country integrations, such as USA and Canada. A heap size of 1 GB is recommended for optimum performance for a USA and CAN integration. 4. Restart the USA server and re-examine the Java Server Status report as described in Determining the Java Core Engine on page 15. 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 USA and Canada 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 diff the contents of the...\web-inf\lib and...\web-inf\classes folders.) For each country you wish to integrate into an existing Tomcat, copy the country-specific jar, properties, and license files into the Tomcat with the newest MapMarker Java core. Performance of Tomcat integration strategy: Heap size of 512 MB is usually adequate, but 1 GB is recommended for optimum performance for a USA and CAN integration. On 32 bit systems, 1.5 MB is the maximum heap size. Larger heap sizes can be allocated on 64 bit systems. If you move country data: By default, country-specific data is located in directories named MapMarker_CTY_v##_Data (where CTY is the country identifies and v## is the version number). Each CTY_DataManagersettings.properties file (copied in step 2) includes a DICTIONARY_PATH# entry that points to the respective data file location. If you move country data to a different location, you must update the property file to point to the data location. MapMarker USA v24.1 Release Notes 16

17 Known Issues and Clarifications This section covers some known issues and behavioral changes that require further explanation. Unless otherwise noted, these issues are unchanged from the v24 Release Notes, but are summarized here for convenience. Result code does not indicate perfect match. Some perfectly matched addresses return a result code that does not indicate a perfect match. For example, the address: 6201 NE Fourth Plain Blvd; Vancouver, WA; returns a S5HP-TSCZA result code when it should return S5HPNTSCZA (the N indicates perfect street name match). This problem is characteristic of some addresses that include ordinal street names. This issue has been partially fixed, but is not yet fully resolved. See Ordinal street name fails to match if data has spelled out street name. Abbreviated Spanish directionals are not handled properly. When an abbreviated directional is used in a Spanish address, the candidate is not returned. For example, the address: 2035 CAMINITO CIRCULO S; La Jolla, CA does not return a close match candidate. If the directional is spelled as Sur (instead of the abbreviated S), the candidate is returned. With a user dictionary, some city input addresses do not return candidate as expected. For example, input of 5922 Goodwin Ave; Elmendorf AFB, AK does not return a candidate even though Elmendorf AFB is an acceptable city name. If the city is input as Anchorage or if the ZIP Code is input, the correct candidate is returned. This has not been resolved. Abbreviated directionals do not always match. With some abbreviated street directionals, no close match is returned. For example: 4900 Pearl E Cir; Boulder, CO does not return a close match. If East is used instead of the E abbreviation, the correct candidate is returned. Some instances of this problem have been fixed, but not all abbreviated directionals are handled properly. This is not yet fully resolved. Street without house number fails to give S4 match. An address that returns an S5 close match (such as 2 Hutton St; Troy, NY) fails to return an S4 match when the house number is omitted. This has not yet been resolved. Documentation of user dictionary requirements has some inaccuracies. One section of the User Guide still mentions that several address dictionary files are required even if you plan to use a user dictionary exclusively. This is no longer true. You can create and use a user dictionary without referring to any address dictionary components. Creating a Point User Dictionary with the User Dictionary Utility The MapMarker USA v24 User Dictionary Utility can be installed with the MapMarker USA Developer product. This utility simplifies the steps for creating user dictionaries. The utility displays a dialog indicating that point-based user dictionaries are not supported. This dialog is misleading. When you click Next and proceed past that dialog, you will still have the opportunity to create a user dictionary in which each street range contains a single point. To create a point-based user dictionary using the utility, the From Left and To Left columns for each record must have the same house number. You must then map the table input columns appropriately in the Required Columns dialog of the User Dictionary Utility. Required Column Mapping for Point User Dictionary UD Utility Entry Left Starting Address Number Left Ending Address Number Right Starting Address Number Right Ending Address Number Map To Table Column From Left input table column To Left input table column empty column empty column MapMarker USA v24.1 Release Notes 17

18 Follow these requirements and column mapping guidelines when creating a point-based user dictionary with the User Dictionary Utility. The source TAB file for your user dictionary must have an empty column. You will need this empty column for mapping purposes. To add an empty column to the TAB file, use MapInfo Professional and select Table > Maintenance > Table Structure > Add Field). Add this column before starting the User Dictionary Utility. The User Dictionary Type dialog indicates that point-based user dictionaries are not supported. However when you click Next and proceed past that dialog, you will still have the opportunity to create a user dictionary in which each street range contains one point. Map the Left Starting Address and Left Ending Address fields. The same house number must be in both the left and right fields for each record. Map the Right Starting Address and Right Ending Address to an empty column. 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). By default, the ClientSetup.exe is located under the \Desktop\DesktopInstaller folder. The client users also must be able to access to the shared data. By default, the data is installed in the folder: MapMarker_USA_24_Data. After completing the Shared installation, the administrator can share the MapMarker_USA_24_Data folder (and the \Desktop\DesktopInstaller folder). Client users then have access to everything that they need to perform a client installation and access shared data. The Centrus Points, Tele Atlas Points, and NAVTEQ Address Dictionaries can be installed in their own data paths. Microsoft Windows Administrator-Related Issues This section covers some administrator -related issues that are common to Microsoft Vista, 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. Windows Vista imposes some additional restrictions on installing and running MapMarker. This section provides some background on Microsoft Vista security-related issues and gives specific information on installing and running MapMarker on Windows Vista. Windows Vista uses UAC (User Account Control). When UAC is turned off, the Administrator can install MapMarker USA v24 and run MapMarker programs with no additional requirements. However, when UAC is turned on, you must meet both of the following conditions to install MapMarker USA v24, start the MapMarker Server, or stop the MapMarker Server. You must be an Administrator, and You must run the application with administrator credentials applied. When an administrator launches the installer (setup.exe), UAC asks the user if they want to allow the program to execute. When the user clicks Allow, administrator credentials are automatically applied for the user while the installation executes. For other programs, such as starting or stopping the MapMarker server or installing the server as a Windows Service, administrator credentials must be explicitly applied. 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 v24.1 Release Notes 18

19 Installing and Removing the MapMarker Server as a Windows Service: To install or remove the server as a Windows Service, first open an Administrator Command Prompt. From the Command Prompt, run the commands to install or remove the service, as described in the topic Running the Web Application as a Windows Service in Chapter 2 of the MapMarker Developer Guide. Using ODBC Data source: You must have administrator privilege to create a new ODBC data source. The user also must set up their ODBC connections in advance. Shortcut not Removed on Windows Vista: When uninstalling on Windows Vista, the shortcut may not be removed properly. The program files do uninstall properly, but the shortcut may be left behind. 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_24/jre/lib/PA_RISC2.0:/... Edit this to remove the extra colon separator following PATH SHLIB_PATH=$SHLIB_PATH:/data/MapMarker_USA_24/jre/lib/PA_RISC2.0:/... Log File for Cancelled or Failed Install When the installation fails or is cancelled, a log file is created that provides some insight into what happened. This is useful in the silent install scenarios (install, modify, update, or uninstall), because it directs the user to what must be changed. On Microsoft Windows, the log is created in the user s desktop folder by default. On UNIX/Linux systems, this file is created in the user's home directory or at the root directory ( / ). Verifying Data Vintage To verify the data vintage with MapMarker USA v24 select Help > About MapMarker from the Desktop application. If you are not using the Desktop application, open the dictionarydesc.properties file in any text editor. By default, this is located in: C:/Program Files/MapInfo/MapMarker_USA_24/MapMarker_USA_24_Data/ MapMarker USA v24.1 Release Notes 19