MapMarker Canada 10.0 Release Notes

Transcription

1 MapMarker Canada 10.0 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 These Release Notes accompany the MapMarker Canada 10.0 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 10.0 User Guide and Developer Guide. To see these Release Notes and related MapMarker documentation, go to the Product Documentation page on the Pitney Bowes Business Insight web site. Navigate to MapMarker & MapMarker USA category and scroll to MapMarker Canada v10.0. Table of Contents New Features and Enhancements Operating Requirements Fixes to Known Issues Known Issues and Clarifications Europe/United Kingdom: Phone: Fax: Technical Support: pbinsight.co.uk 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. September, 2010

2 New Features and Enhancements Following is a summary of the updates that you will see with the MapMarker Canada 10.0 release. Updated Address Dictionary The Address Dictionary has been updated with data generated from several sources. The MapMarker Canada 10.0 Address Dictionary is based on the following data sources: Tele Atlas Multinet Canada Data (March 2010) Canada Post Address Range Data (July 2010) Statistics Canada PCCF (Postal Codes) (July 2009) FSA Boundaries (March 2010) 2006 Census Geographies refresh (December 2009) The total size of the Address Dictionary files for all provinces and territories is approximately 500 MB. Improved Data for Nunavut MapMarker Canada 10.0 provides improved geocoding for the territory of Nunavut. The data has been enhanced with postal centroids and limited street range data. Allow Centerline Offset for Point Candidates If you geocode using a point-based User Dictionary, you can return the candidate at a specified offset from the associated street segment (rather than at the original point). The candidate is returned from the User Dictionary, but a segment dictionary must be present to provide the basis for the centerline offset. If an associated segment Address Dictionary or User Dictionary is not available, the original point candidate is returned. When possible, the coordinates are offset perpendicularly from the associated street segment. 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). A new SC result code indicates that the original point was offset from the nearest segment. The returned candidate has a location precision of CandidateAddress.ADDRESS_POINT_PROJECTED (value of 18). The Desktop application supports the centerline offset feature through new 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). MapMarker Canada 10.0 Release Notes 2

3 Reverse Geocoding The MapMarker Canada 10.0 geocoder supports reverse geocoding. If you provide X/Y (Longitude/Latitude) coordinates, the geocoder returns the closest address for the given X/Y location based on the Address Dictionary. Reverse geocoding is provided in the Developer (Server) edition. The ReverseGeocodeAPI interface includes classes and methods that support reverse geocoding. You can perform reverse geocoding using the Address Dictionary. You cannot use reverse geocoding with a User dictionary. Candidates return R result codes, indicating that records was matched by reverse geocoding. The first three characters of the R result code indicate the type of match found. R geocode results include an additional letter to indicate the dictionary from which the match was made. This is always an A, indicating Address Dictionary. Following are sample geocoding results: Reverse Geocoding Result Codes Sample Georesult Code RS5A RS4A Description Street address match. Candidate returned from Address Dictionary. Street centroid match). Candidate returned from the Address Dictionary. For the following input coordinates, a close match candidate is returned with a result code of RS5A. X: Y: Reverse geocoding is available with the Developer (Server) edition only. Reverse geocoding is not implemented in the Desktop application and is not available with User Dictionaries. Segment IDs are Returned Segment IDs are numeric codes that uniquely identify each interpolated point (S5 result) or street centroid (S4 result) candidate. Segment IDs are also returned for reverse geocoded candidates. See Reverse Geocoding on page 3. Segment IDs are available with the Developer (Server) edition only (not with the Desktop Application). The Java API getsegmentid() method returns the segment ID. Segment IDs are returned in Additional Fields. For example, the returned XML for a candidate displays the result code and unique Segment ID as follows: <AdditionalFields> <KeyValuePair> <Key>RESULT_CODE</Key> <Value>S5HPNTSCZA</Value> </KeyValuePair> <KeyValuePair> <Key>SEGMENT_ID</Key> <Value> </Value> </KeyValuePair> </AdditionalFields> If a street has multiple segment IDs but no house address numbers, the geocoder returns one segment as a close match candidate. Segment IDs are available with the Developer (Server) edition only and is supported in the Sample Application; this feature is not available in the Desktop application. MapMarker Canada 10.0 Release Notes 3

4 ODBC Support for SQL Server 2008 and Oracle 11G The Desktop Application now supports SQL Server 2008 and Oracle 11G ODBC databases. Support Interactive Geocoding of TXT and CSV Files MapMarker Canada 10.0 reads and writes delimited text files, CSV, and TXT files. After opening the input file, you can use a Text File Wizard to set properties for the input file and geocode addresses. Previous versions of MapMarker Canada had some restrictions on interactive geocoding of TXT and CSV files. This functionality has been improved and you can now interactively geocode TXT and CSV files. Intersection Geocoding Allows Additional Tokens MapMarker Canada 10.0 allows new tokens for street intersection input. In addition to the && token. you can use the & symbols to designate a street intersection. You can also use the word and as an intersection separator. For example: Yonge && Wellington; Toronto ON Yonge & Wellington; Toronto ON Wellington; Toronto ON Yonge and Wellington; Toronto ON You can omit spaces between the token and the street name, but the space is required for the and separator. Improved Unformatted (Single-Line) Geocoding Single-line geocoding has been enhanced to allow more flexible input formats. The match rate and performance of single-line geocoding has also been improved. Operating Requirements This section describes the software and hardware requirements for running MapMarker Canada Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the Desktop Application and MapMarker SDK are: 1 Ghz Pentium processor or equivalent 1 GB RAM 5 GB available disk space (including space for CAN 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 MapMarker Canada 10.0 Release Notes 4

5 Microsoft Windows 7 Solaris 2.10 and 11.0 HP-UX 11 Red Hat Linux 4.0 and 5.0 SUSE Linux 10.0 and 11.0 Desktop Application The Desktop Application runs on Microsoft Windows only. 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 requires a Java Virtual Machine (JVM) to run. The following JVMs are supported: JVM v1.5 and 1.6. MapMarker Canada 10.0 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. 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 Canada 10.0 supports the following ODBC databases and drivers. SQL Server 2008 SQL Server 2005 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) Microsoft Access 2003 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 Canada 10.0 ships with: Apache Tomcat 5.5 MapMarker Canada 10.0 Release Notes 5

6 Supported MapInfo Products MapMarker Canada 10.0 can integrate with the following products: MapInfo Professional MapInfo AnySite MapInfo Target Pro MapMarker USA Envinsa version MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server Fixes to Known Issues The following incidents were addressed in MapMarker Canada Cannot Open MapInfo Professional 10 Table When you attempted to open a MapInfo Professional table (TAB file) that used 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 issue. This problem has been fixed for MapMarker Canada You can now open a MapInfo Professional version 10.5 table and all features are available. Input street number written as ordinal sometimes fails to match. For example, the input address of 11 33rd St. did not produce a close match, while the input of 11 Thirty Third St. did produce a close S5 match. Other examples of inconsistent results with numbered/ordinal/ street input: 6644 Tenth Line Rd W Rd vs th Line W Rd. This handling has been improved and numbered/ordinal streets are now interpreted and geocoded more consistently. Input address missing the word The returned wrong candidate. For example, an input address of 155 East Mall did not return the expected close match candidate. Address of 155 The East Mall returns the expected candidate. This has been fixed. Correct candidate is now returned regardless of the article The. Wrong candidate returned when pre directional is separated from street name. For example, if the street name is input as: West Mount Ave. instead of the correct Westmount Ave., a bad close match is returned. This has been fixed and the correct close match is now returned. Address with extra information sometimes returned bad candidate. If an input address had extra information at the end of the MainAddress line, an inaccurate close match candidate was returned. For example, the input: 8 HILL HEIGHTS ROAD 402, Toronto ON returned a bad candidate. If the extraneous 402 was removed, the correct close match was returned. This has been fixed and MapMarker Canada now returns the correct candidate even if extra information appears at the end of the input address. In this example, the input 402 is now returned as a suite number. Wrong candidate returned when post directional is missing. In some cases, an incorrect close match candidate was returned when a post directional was omitted from the input address. For example, 147 Queen St, Toronto ON returned an incorrect close match because the post directional E was omitted from Queen St E. This has been corrected. Selecting Match Mode interferes with selecting Custom match settings. Once a Match Mode has been selected Custom/Exact match settings are not applied. After using Match Mode, you can select Custom/Exact match settings in the Desktop Application, but the settings are ignored and the previously selected Match Mode is still enforced. This has been fixed. Input Place Name was not returned in all cases. If the Place Name (firm name) is omitted from input, the expected place name is not returned. For example, the input address KENT ST OTTAWA ON should return COUR CANADIENNE DE L'IMPOT as the firm name. This has been fixed and the firm name is returned regardless of whether the firm name was input. Empty house number field sometimes produced bad candidate. In some cases, if the input House Number field was empty, an inaccurate candidate was returned. MapMarker Canada 10.0 Release Notes 6

7 Slight misspelling of input address returned incorrect close match. A minor misspelling of an input address sometimes failed to return the best candidate and returned an incorrect candidate instead. For example, the input address 111 Wellsley Avenue E Toronto, ON should return BUSINESS BUILDING 111 WELLESLEY ST E, TORONTO, ON M4Y 2Y2. This candidate was missed because the input misspelled Wellesley. This has been fixed and MapMarker Canada 10.0 is more tolerant of input spelling variations. Unit number returned even though the returned candidate has no house number. An S4 candidate without a house number sometimes included a unit number. Since there is no house number, there should not be any unit information returned. This has been fixed. MapInfo Professional crashed when MapMarker Server returned an empty coordinate system. If a candidate did not return coordinates (such as an S0 match with a null coordsys string, MapMarker returned an empty coordinate system string (SrsName= ). This caused MapInfo Professional v10 to crash. This has been fixed. If MapMarker returns a candidate address with no coordinates (0, 0 Longitude, Latitude) it now populates the SrsName with a default of epsg:4326. This prevents MapInfo Professional from crashing. Single-line geocoded addresses missing C in result code. For some single-line geocoded addresses, MapMarker returned a result code that did not indicate a match on City name (for example, S5HPNTS ZA). When geocoded with multiline input, the correct S5HPNTSCZA result code was returned. This has been fixed and the complete result code is now returned for both single-line and multiline input. Multiple close matches returned when input has incorrect FSA. When an input address had an incorrect FSA, it was possible to get two close match candidates. This has been fixed and the correct single close match candidate is now returned. Exception when input address has empty field. When an input address had empty address fields (city, province, or postal code field), MapMarker threw an exception. This has been corrected. Intersection address returns a null city if streets are in different cities. If two intersecting streets were in different cities, no city name was returned with the candidate. For example, an input address of HWY 401 EXPY && Yonge Street returned the correct candidate but without the city name. This has been corrected and the candidate will now include one of the two city names. Can t start MapMarker USA RPC server after MapMarker Canada is installed on same PC. If you installed MapMarker Canada v9 on a system where MapMarker USA 22.1 already existed, you could not start the USA RPC server. This was because a MapMarker USA dll was mistakenly overwritten. This has been corrected and you can integrate MapMarker Canada 10.0 and MapMarker USA with no problems. Crash when geocoding CSV file if output file was already open in Excel. When an output CSV file was already open in another application (such as Excel), MapMarker crashed when you attempted to overwrite this file during the last step of the text file geocoding wizard. This has been fixed to avoid a crash. Better messages are also displayed. Multiple geographic candidates returned when city name is an alias for a different city. For geographic geocoding, it was possible to get multiple candidates when the city name is also an alias for a different city. For example, St. John s NL returned the expected close match candidate for St John s but also returned a candidate for Kilbride, NL. This has been corrected, and MapMarker Canada 10.0 returns the St. John s candidate only. Known Issues and Clarifications This section describes provides information specifically related to Windows Vista and UNIX/Linux platforms. This section also provides information and workarounds related to several known issues. MapXtreme Geocoding Requests Fail When Ranges Are Requested When a MapXtreme application requests address ranges, the geocoding operation will fail. To avoid this problem, do not request ranges when issuing a MapXtreme geocoding request. MapMarker Canada 10.0 Release Notes 7

8 Candidate Visualization Does Not Work with Most Recent StreetPro Canada Changes to the MapMarker StreetPro data format and table naming conventions are inconsistent with MapMarker Canada As a result, the candidate visualization feature does not work with StreetPro Canada Use either of these workarounds: You can use and earlier versions of StreetPro Canada (such as StreetPro Canada ). Older versions of StreetPro Canada do support candidate visualization with MapMarker Canada You can rename selected tables (TAB) and associated files from the table names to the equivalent older table names. The StreetPro Canada Product Guide describes these changes in New and Old Layers. Make copies of the original files before renaming them. Contact Technical Support for a more detailed description of this procedure. Microsoft Windows Vista-Related Issues You must always have administrator rights on the target machine to install MapMarker on Microsoft Vista. 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 and run the program with no additional requirements. However, when UAC is turned on, you must meet both of the following conditions to install MapMarker, 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 will ask the user if they want to allow the program to execute. When the user clicks the Allow button, 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. This is described in the topic Starting the MapMarker Server in Chapter 2 of the MapMarker Canada Developer Guide. 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 will allow 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 as described in the Note above. 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 4 of the MapMarker Canada Developer Guide. Generating reports, log files, and updating tables: Reports, log files, and tables (.tab files) must be directed to a writable location. Windows Vista with UAC enabled does not allow users to write to the default Programs folder. If the user cannot write output to the designated directory, the action will fail without notification. To solve this problem, create the log file and other output in a location where the user always has write permissions (such as the user s Desktop or Documents Folder). To set the log file location in the Desktop Application, specify the full path to to a writable location for the log file on the Log File tab of the Geocode dialog box. See the Log File Preferences topic in Chapter 6 of the MapMarker Canada User Guide for additional information. As an additional option, the user can right-click on the Desktop Application shortcut and start the application with administrator credentials by selecting "Run as administrator". With these credentials applied, the user can then create reports, log files, or tables in the default Programs folder or any other location. MapMarker Canada 10.0 Release Notes 8

9 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. UNIX / Linux-Related Issues On UNIX/Linux platforms, there are some installation and startup issues related to administrator rights. 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. Starting the 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 Business Insight Technical Support for further assistance. 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_v10_Data. Under that folder, the DesktopInstaller folder contains the ClientSetup.exe. After completing the Shared installation, the administrator can share the MapMarker_CAN_v10_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. 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\9.0\GEOCODING\RequireProvince MapMarker Canada 10.0 Release Notes 9

10 Loading User Dictionary Only (-udonly Option) The -udonly option (to load user dictionaries only) in MapMarker Server works with MapMarker Canada, but requires modifications to the Windows registry before you can use it. For example, the following command: mm_serve -console -udonly should start MapMarker Server as a console application and load the user dictionary only. However, you must first add two values to the System key for the user dictionary path. CAUTION: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Pitney Bowes Software Inc. cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Make a backup of the registry before you modify it and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, see this article (Description of the Microsoft Windows registry) in the Microsoft Knowledge Base: To add the registry values, do the following: 1. Choose Start > Run, and type regedit in the Open box. 2. In the Registry Editor, open the following key: HKEY_LOCAL_MACHINE\SOFTWARE\MAPMARKER\CAN\10.0.0\SYSTEM 3. Add the following string value: UserDictionaryPath=<path> 4. Add the following DWORD value: UseUserDictionary=1 MapMarker Canada 10.0 Release Notes 10