MapMarker 22.1 Release Notes

Transcription

1 MapMarker 22.1 Release Notes United States: Phone: Fax: Sales: Government Sales: Technical Support: Technical Support Fax: pbinsight.com Canada: Phone: Fax: Sales: Technical Support: Technical Support Fax: pbinsight.ca Europe/United Kingdom: Phone: Fax: Technical Support: pbinsight.co.uk MapMarker 22.1 unites the newly engineered Pitney Bowes Business Insight geocoding engine (based on the GeoStan geocoding engine) with the interface and API that are familiar to MapMarker customers. These MapMarker 22.1 Release Notes describe the new and improved capabilities, operating requirements, fixes to customer-reported issues, and known issues and clarifications. You also should read the MapMarker 22 Technical Notes, which focus on geocoding, matching, and behavioral changes that experienced MapMarker users may notice when upgrading to MapMarker If you have used previous versions of MapMarker, the information in the Technical Notes document will help you understand these differences. To see these Release Notes, Technical Notes, and other MapMarker documentation, go to the Product Documentation page on the Pitney Bowes Business Insight web site. Navigate to the MapMarker & MapMarker Plus USA category and select MapMarker v22.x. In these release notes: New Features and Enhancements Operating Requirements Fixes to Customer Reported Issues Known Issues and Clarifications Asia Pacific/Australia: Phone: Fax: Technical Support: pbinsight.com.au 2010 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. March 2010

2 New Features and Enhancements MapMarker 22.1 provides many new features and expanded capabilities. See the following topics for a more detailed explanation of new features provided with MapMarker These new features are fully covered in the appropriate sections of the MapMarker 22 User Guide and in the Developer Guide. After you complete the installation, contact Pitney Bowes Business Insight Customer Service at and provide your address. This is necessary to receive future license file updates. This and other contact information also appears in the Quick Reference Card enclosed in the product box. New features are described in the following topics: Certified for CASS Cycle M New Address Dictionaries and Data Updates More Flexible Software and Data Installation Binaries for All Platforms Available with Installer DPV and LACSLink Security Keys Expanded ODBC Support Match Modes Certified for CASS Cycle M MapMarker 22.1 has been fully tested and certified for CASS Cycle M as of January CASS certification is not available with TIGER data. New Address Dictionaries and Data Updates By default, the Tele Atlas Streets address dictionary is included with MapMarker Customers can choose to receive a primary address dictionary based on either NAVTEQ or TIGER data instead of Tele Atlas Streets data. Customers can also purchase supplemental Address Dictionaries that were not previously available with MapMarker. The following Address Dictionaries are available for use with MapMarker 22.1 and can be used within the same core engine: Tele Atlas Street data. In addition to Tele Atlas quarterly updates, you now have the option of receiving monthly updates for Tele Atlas Street data. Updates are referred to by the month name, such as: MapMarker January data update. Tele Atlas Points data January This coincides with the January Tele Atlas street data update and the MapMarker 22.1 software release. NAVTEQ data January Centrus Points data January TIGER data. This offering replaces the MapMarker Standard product. This data will be shipped annually, beginning with the MapMarker 22.1 release. The TIGER data does not provide the same features and capabilities as offered with the other datasets. Also, TIGER data cannot be used in conjunction with any premium dataset. For an understanding of these differences, see MapMarker 22 with TIGER Data on page 12. See the PBBI web site for more detailed information on the U.S Geocoding Data Sets. Contact your sales representative for more information on purchasing additional data sets and updates. Data Expiration For new MapMarker customers, all Address Dictionaries will expire 135 days after the data release month. TIGER data does not expire. The procedure for installing data updates is covered in the Installation chapters of the MapMarker 22 User Guide and in the Developer Guide. For existing MapMarker customers, there is no change in the data expiration policy. That is, the standard Address Dictionary data will not expire for existing customers. CASS data expires at the end of the 105 day cycle. Contact your sales representative for information on CASS data. MapMarker 22.1 Release Notes 2

3 MapMarker Plus 14.x Customers If you choose to upgrade to MapMarker Plus 14.x rather than MapMarker 22.1, you can request Tele Atlas Street data updates until July However, note that MapMarker Plus 14.x is not CASS certified. MapMarker Plus 14.x still provides CASS Mode address matching, but you must use MapMarker 22.1 if you require CASS certification or CASS reports. This option is not available to MapMarker Standard 14 customers, since MapMarker Standard used the TIGER dataset only. More Flexible Software and Data Installation MapMarker 22.1 provides separate software installation and data distribution for the premium datasets (Tele Atlas, Centrus, and NAVTEQ) offered by Pitney Bowes Business Insight. TIGER data is not included in this installation model. See MapMarker 22 with TIGER Data on page 12 for information about the limitations of the TIGER dataset. This separate software and premium dataset installation model has significant advantages. You can install and use Address Dictionaries that were not previously available. There are software and data DVDs for each of the primary street network Address Dictionaries (Tele Atlas Streets, and NAVTEQ). For instructions on installing data updates, see the MapMarker 22 Data Installation Notes. Optionally, you can purchase supplemental Address Dictionaries (such as Centrus Points and Tele Atlas Points). These are provided on separate DVDs and are not part of the software installation. See New Address Dictionaries and Data Updates on page 2 for a description of the available MapMarker Address Dictionaries. A new MapMarker Data Installer is also available. This installer provides a simple and comprehensive procedure for installing and updating MapMarker premium address dictionaries. Instructions for using this new MapMarker Data Installer are posted in the MapMarker USA v22.x category of the PBBI web site. The release numbering system reflects the software version number and the monthly data vintage. For example, this release for the MapMarker U.S. product with the January 2010 data release is named: MapMarker January Software and Data update During installation, the license file is copied into the MapMarker Data folder. The license file remains in that folder after an uninstall. If you get a new license file (for example if you license new data after your initial MapMarker installation) you can simply replace the license file. The MapMarker v22 license file was provided on the media accompanying the MapMarker 22.0 release (July 2009). If you installed MapMarker 22.0, that license file will be used when you update to MapMarker Simply browse to the location of that license file (search for a file named mmusa22*.lic). If you did not install MapMarker 22.0, you can locate the license file on the original MapMarker 22.0 media. If you cannot find your original license file, contact Pitney Bowes Business Insight Customer Service at A new license file will be required for the July 2010 release of the MapMarker USA software and data. Future license files will be distributed via . Please contact Customer Service as soon as possible to verify/update your address, and to avoid disruption in the receipt of future license files. These licensing guidelines are not applicable for TIGER data. Binaries for All Platforms Available with Installer The MapMarker 22.1 installer now provides the binaries for all available platforms. This allows you to more easily install MapMarker 22.1 on one platform but potentially deploy the application on other licensed platforms. If you check Additional Developer Tools from the Choose Install Set dialog when you install MapMarker 22.1 Server, these additional binaries are installed to: <install >\MapMarker_USA_v22\sdk\additional_tools\geostan_libs\. After installation, you will see separate folders for each supported operating platform (for example, linux32). MapMarker 22.1 Release Notes 3

4 To ensure that MapMarker 22.1 uses the correct binary, open the USA_DataManagerSettings.properties file and verify that the LIB_PATH entry points to the correct location of the executable. For example: LIB_PATH=C:/Program Files/MapInfo/MapMarker_USA_v22/sdk/additional_tools/geostan_libs/linux32 While 64-bit binaries are provided, the 64-bit versions of MapMarker 22.1 have not undergone rigorous testing and validation. Therefore, Pitney Bowes Business Insight does not support these versions and Technical Support is not available for 64-bit installations at this time. The 64-bit versions will be fully supported in the MapMarker 23.0 release. Also note that if you install a 64-bit version of MapMarker 22.1 you must use a 64-bit JVM. DPV and LACSLink Security Keys To support alternative locations for DPV or LACS Link data, the USA_DataManagerSettings.properties file uses the following entries: DPV_DATA_PATH= DPV_SECURITY_KEY= LACS_SECURITY_KEY= LACS_DATA_PATH= When you install MapMarker 22.1 with DPV or LACS Link data, all of these entries are populated; however the DPV_ and LACS_DATA_PATH entries are commented out. The optional DPV and LACS data path entries are not initially needed because DPV and LACS Link data is installed in the main data path (DICTIONARY_PATH1) by default. If you subsequently move the DPV or LACS Link data, you must uncomment and edit the DATA_PATH configuration entries to point to the new data locations. Do not edit the SECURITY_KEY entries, since they already provide the correct security keys. For example if you move the DPV and LACS Link data, you could locate and authorize the data with the following entries: DPV_DATA_PATH=C:/Program Files/MapInfo/MapMarker_USA_v22/MapMarker_USA_v22_Data/ DPV_Data/ DPV_SECURITY_KEY=ABCD-1234-EFGH-5678 LACS_DATA_PATH=C:/Program Files/MapInfo/MapMarker_USA_v22/MapMarker_USA_v22_Data/ LACS_Data/ LACS_SECURITY_KEY=ABCD-1234-EFGH-5678 If you move your DPV and LACS Link data, you must also move the corresponding security file with it. For DPV, place the following files in the same location as the DPV data. Dpvh.db Xssf.su$ DPV data file) DPV security file) For LACS LinK, place the following file in the same location as the LACS Link data. Llk.db Xssl.su$ These actions ensure that DPV and LACS Link data can be located, authorized, and initialized. Additional details of the Configuring the DataManagerSettings.properties file are described in the Custom User Dictionaries chapter of the MapMarker 22 Developer Guide. DPV is not available with TIGER data. Expanded ODBC Support MapMarker 22.1 now supports SQL Server See Database Requirements on page 7 for a complete list of supported databases and drivers. MapMarker 22.1 Release Notes 4

5 Match Modes MapMarker 22.1 provides the following match modes. Match Modes Mode Description Standard Mode This is the default mode, and generally provides the best combination of accurate geocoding, few false matches, and high performance. Standard Mode is not equivalent to what was previously called Default Mode. Tight Mode This provides strict matching rules. In general, this returns fewer non-close matches than are returned in Standard Mode. Tight Mode is not equivalent to selecting Custom matching with all Exact Match criteria checked (House Number, Street Name, City Name, and ZIP Code). Relaxed Mode This provides less strict matching rules. In general, Relaxed Mode increases your chances of getting a close match but will impact performance (slower geocoding speed). Relaxed Mode is not equivalent to selecting Custom matching with all Exact Match criteria unchecked. CASS Mode Custom Mode This provides strict conformity to USPS CASS rules. CASS Mode activates several other CASS-related and other matching options. Custom Mode allows you to select any combination of Exact Match criteria House Number. If checked, a candidate must match the building/house number in order for it to be considered a close match. Street Name. If checked, a candidate must match the street name in order for it to be considered a close match. City Name. If checked, a candidate must match the city name in order for it to be considered a close match. ZIP Code. If checked, a candidate must match the ZIP Code in order for it to be considered a close match. MapMarker 22.1 Release Notes 5

6 Operating Requirements This section describes the hardware, memory and other requirements for MapMarker Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the Desktop Application and MapMarker SDK are: 1 Ghz Pentium processor or equivalent 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 Java API Support The Java API supports the following: Microsoft Windows XP Professional with SP2 or SP3 Microsoft Windows 2003 Enterprise Edition SP3 Microsoft Windows Vista Ultimate Edition Windows 2000 Advanced Server with SP4 Solaris 2.9, 2.10 HP-UX 11.0 Red Hat Linux 4 kernel version 2.6 SUSE Linux 9x For Unix platforms, MapMarker supports 32 bit systems only. C API Support The C API supports the following: Microsoft Windows XP Professional with SP2 or SP3 Microsoft Windows 2003 Enterprise Edition SP3 Desktop Application The Desktop Application runs on Microsoft Windows only. Microsoft Windows XP Professional with SP2 or SP3 Microsoft Windows Vista Ultimate Edition Microsoft Windows 2003 Enterprise Edition SP3 Windows 2000 Advanced Server with SP4 JVM Requirements MapMarker v22 requires a Java Virtual Machine (JVM). The following JVMs are supported: JVM v. 1.5 or 1.6 MapMarker 22.1 Release Notes 6

7 MapMarker 22.1ships with: Sun JRE v _09 (for Microsoft Windows and Sun Solaris) HP JRE _04 (for HP-UX) Sun JRE 1.5.0_11 (for Linux) Note that if you install a 64-bit version of MapMarker 22.1 you must also use a 64-bit JVM. See Binaries for All Platforms Available with Installer on page 3 for information on using binaries for all available platforms, including 64-bit installations of MapMarker Database Requirements MapMarker 22.1 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 2000 MapMarker also supports the following Oracle drivers. Oracle 11 Release 1 Oracle 10G Release 2 You must install the Oracle driver separately. To use the driver, you must have the Oracle client installed. Supported Web Servers The following Web servers are supported: Apache Tomcat 5.5 or 6.0 BEA WebLogic 9.2 IBM WebSphere 6.1 Fixes to Customer Reported Issues Data Initialization Error When no LIC file is specified during install Under some circumstances, it was possible to get a data initialization error when you started MapMarker. This was because the MapMarker 22 license file was not copied to the data drive and therefore the path to the USA_DataManagerSettings.properties file was incorrect. This problem has been fixed for MapMarker 22.1 by requiring the user to specify a valid license file during installation. In the Licensing dialog, accept the default location if you have placed the license file in that area. Otherwise, click Choose and navigate to the location where you have placed your MMUSA22.lic file. During installation, this file is copied to the appropriate data drive. After installation, you can verify that the USA_DataManagerSettings.properties file has a LICENSE_FILE= entry with a complete and correct path. For example: LICENSE_FILE=C:/Program Files/MapInfo/MapMarker_USA_v22/MapMarker_USA_v22_Data/ MMUSA22.lic Opening MapInfo Professional version 10 Table When you attempt to open a MapInfo Professional table (TAB file) that uses MapInfo Professional version 10 features, you received an error message and the table fails to open. Pitney Bowes Business Insight Technical Support provided a workaround for this MapMarker 22 issue. This problem has been fixed for MapMarker You can now open a MapInfo Professional version 10 (or higher) table and all features are avaiable. MapMarker 22.1 Release Notes 7

8 Minor misspellings in addresses are not recognized and properly geocoded For example, user input of Beas Creek Lane was not automatically corrected to Bear Creek Lane and therefore a candidate was not returned. In Relaxed mode, MapMarker 22.1 now recognizes this type of spelling mistake and returns close match candidates. As a result of this fix, you will see higher match rates but somewhat reduced performance (slower geocoding speed) in Relaxed mode. We recommend that you use Relaxed Mode in a second (or subsequent) geocoding pass if your data includes poorly spelled or incomplete addresses. DPV does not return ZIP+4 and complete census information for non-close matches With DPV enabled, a single close match candidate returned ZIP+4 and complete census information as expected. However for non-close matches, the complete information was not returned. This has been fixed. For MapMarker 22.1 with DPV enabled, non-close matches now return ZIP+4 and full census information (if that information is available). FIPS and DPV Values not returned for multiple close match candidates With DPV enabled, multiple close match candidates did not return FIPS and DPV information. For MapMarker 22.1 with DPV enabled, multiple close matches now return FIPS values. See Multiple Close Matches and DPV Information on page 9 for an explanation of DPV information with multiple close matches. Improved handling for Queens, NY addresses Some Queens, NY addresses returned inaccurate close match candidates. Some returned candidates were in the wrong part of Queens. This problem has been fixed for MapMarker 22.1, and these false positive results are no longer returned. Java API Left/Right Indicator is null The Java API getleftrightindicator() is null for address ranges. Therefore, when using the Java API a returned range address does not indicate the left/right (odd/even) indicator. This problem has been fixed for MapMarker Multiple close matches returned with Quick Find for Parcel Precision Dictionary When using Quick Find geocoding with both the standard Address Dictionary and ParcelPrecision User Dictionary enabled, multiple close matches are returned when there should be only one close match candidate. This problem has been fixed for MapMarker Units are not always displayed with ranges For Quick Find or Interactive results, units are not displayed with range candidates. This problem has been fixed for MapMarker Place name is also displayed with unit information, when available. Log file not created for batch file When geocoding using a batch file, the log file is not properly created. This problem has been fixed for MapMarker Known Issues and Clarifications This section covers some known issues that require further explanation. Pre-release Customers should Re-install Final Release from Media If you received the DPV pre-release version of MapMarker 22.1, we strongly recommend that you re-install the final release of MapMarker 22.1 from the media. The final release corrected some issues that were not addressed in the pre-release. The issues that were corrected do not affect CASS-certified processing, but can affect other types of processing. DPV pre-release customers received a customer letter (dated 28 January, 2010) that describes these changes in more detail. Software or Data Installation Can Generate Incorrect License File Path Under some circumstances, installing MapMarker 22.1 or installing a data update can overwrite the existing LICENSE_FILE path in the USA_DataManagerSettings.properties files and replace it with an incorrect path. This could happen if you bypassed the Licensing dialog when you initially installed MapMarker 22. This resulted in an invalid license file path that did not point to mmusa22.lic. You had to manually edit the LICENSE_PATH entry to specify a complete and correct path. MapMarker 22.1 Release Notes 8

9 When you subsequently install MapMarker 22.1 or perform a data update, the originally incorrect LICENSE_FILE path may re-appear instead of the corrected path. You will then receive an unable to initialize data manager error when you attempt to start MapMarker You must manually re-edit the LICENSE_PATH entry to specify a complete and correct path. See Data Initialization Error When no LIC file is specified during install for a description how to fix the license file path. Multiple Close Matches and DPV Information With DPV enabled, multiple close match candidates do not return DPV information. After investigation, it was determined that this behavior is correct. Returning DPV information for multiple close match candidates would violate the current USPS DPV licensing agreement. Some Intersection Addresses Return Incomplete Candidates When multiple candidates are returned from an intersection search, some of the candidates are incomplete and are not proper intersection results. For example, Willow & Cumberland Cowan, TN returns an incomplete candidate. This issue has not yet been resolved. False Positive Candidates for Address with Invalid House Number With all constraints relaxed (including Must Match House No.), an input address with an invalid house number can return false positive candidates. For example, input of 164 Flores Way, Brentwood CA (there is no house number 164) returns false positive close match candidates in Los Angeles. The preferred Brentwood addresses are returned as non-close candidates. This issue has not yet been resolved. 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_v22_Data. After completing the Shared installation, the administrator can share the MapMarker_USA_v22_Data folder (and the subordinate 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 or into the MapMarker data path (typically <install>/mapmarker_usa_v22/mapmarker_usa_v22_data). Microsoft Windows Vista-Related Issues 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 22.1 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 22.1, start the MapMarker Server, or stop the MapMarker Server. You must be an Administrator, and You must run the application with administrator credentials applied. MapMarker 22.1 Release Notes 9

10 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. 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_v22/jre/lib/PA_RISC2.0:/... Edit this to remove the extra colon separator following PATH SHLIB_PATH=$SHLIB_PATH:/data/MapMarker_USA_v22/jre/lib/PA_RISC2.0:/... Permissions on Geoappl Testing Application (HP and Solaris) The geoappl application is a C-based test program that can geocode a sample input file. This is included with the Developer SDK on HP and Solaris systems, and is installed in the sdk/additional_tools/geoeng/test directory. You can run the program as follows: geoappl [infile] [outfile] [mapmarker data path] However, on HP UNIX machines, the geoappl program does not run unless you do both of the following: MapMarker 22.1 Release Notes 10

11 assign execute permissions to the geoappl program and the libraries located in the sdk/additional_tools/geoeng/lib directory ensure that the user can write to the directory specified for the output file (outfile in the above syntax) Installing MapMarker Canada 9.x with Existing MapMarker 22.1 (Windows) If you install MapMarker 22.1 and then install MapMarker Canada 9.x on the same computer, the RPC server will not run. This is because a specific DLL is overwritten by the MapMarker Canada installer. If you experience this, contact Technical Support to receive a replacement DLL that will solve this problem. 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 A simple way to verify the data vintage installed with MapMarker 22.1 is to open the dictionarydesc.properties file in any text editor. By default, this is located in: C:/Program Files/MapInfo/MapMarker_USA_v22/MapMarker_USA_v22_Data Documentation Corrections The MapMarker 22.1 User Guide included on your media does not accurately describe the Match Mode behaviors. See Match Modes on page 5 of these Release Notes for a better description of Standard, Tight, and Relaxed Modes. The MapMarker 22.1 Developer Guide included on your media does not accurately describe the relationships between API Match Mode Constants and the Desktop Application Match Modes. See the topic on Match Mode Relationships in Desktop and API in the MapMarker 22 Technical Notes for updated information. Those Technical Notes and other documents are published on the MapMarker Product Documentation page on the Pitney Bowes Business Insight web site. MapMarker 22.1 Release Notes 11

12 MapMarker 22 with TIGER Data MapMarker 22 with TIGER data replaces the MapMarker Standard product. TIGER data will be shipped annually, beginning with the MapMarker 22.1 release. The following table indicates the MapMarker features and capabilities available with TIGER data versus other datasets. t TIGER Data Limitations Feature TIGER Dataset TIGER Dataset Compared to Other Datasets Data Source Based on the US Census Bureau TIGER dataset. This is a digital database of streets, addresses, geographic features, census boundaries, legal boundaries, and latitude/longitude. Other datasets cannot be combined with TIGER. Update Frequency Annually Several premium datasets are available from Pitney Bowes Business Insight. Contact your sales representative for more information. Note that TIGER data cannot be used in conjunction with any premium dataset. Expiration TIGER data does not expire. For new customers, premium datasets expire 135 days after the data release month. Geocoding Precision CASS (Coding Accuracy Support System) DPV (Delivery Point Validation) LACS Link Best available TIGER geocoding precision is single match at street address position (S5 result code) or single match at ZIP centroid (S6 result code). CASS certification is not available with TIGER data. DPV is not available with TIGER data. LACS Link is not available with TIGER data Premium datasets offer a much greater level of precision, including interpolated points on the street segment (S7 result code) or a single parcel/point (S8 result code). CASS is available with Tele Atlas and NAVTEQ datasets. DPV is available with Tele Atlas and NAVTEQ datasets. LACS Link is available with Tele Atlas and NAVTEQ datasets. Since there is only one core MapMarker USA software product (MapMarker 22), you can purchase the dataset (or datasets) that best serve your needs without upgrading software. So if you initially had MapMarker 22 with TIGER data, you could subsequently acquire a premium dataset that offers more precise geocoding and better address cleansing and verification. You would not have to make any software upgrades to implement the new data. Before you upgrade from TIGER to a premium dataset, you must uninstall TIGER first. The TIGER data is not compatible with the premium datasets from Tele Atlas, Centrus, or NAVTEQ. MapMarker 22.1 Release Notes 12