MapMarker Australia v14 Data v Release Notes

Transcription

1 MapMarker Australia v14 Data v 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 Australia v14 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. This document should be used in conjunction with the MapMarker Australia v14 User Guide and Developer Guide. All of these documents are available at Release Notes are located at the Pitney Bowes Business Insight Product Documentation site: In these Release Notes: New Features and Enhancements Operating Requirements Changes with MapMarker Australia Fixes to Customer-Reported Issues Known Issues 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. March 2010

2 New Features and Enhancements MapMarker Australia v14 includes the following new features and feature enhancements. Following is a summary of the new features that are introduced with MapMarker Australia v14. For a more complete description, see the MapMarker documentation. Address Dictionary Update The Street Range Address Dictionary has been updated with the data generated from several sources. Data vintages for MapMarker Australia v14 are: Street Range Address Dictionary (based on StreetPro data) (October 2009) G-NAF Dictionaries (February 2010) Improved Performance We have optimised performance to improve geocoding speed by 40 to 180 percent, compared to previous versions of MapMarker Australia. This improved performance relies on postcodes in your input data. If your input data is sorted on postcode or locality, you can achieve even faster performance. Performance has also been improved for geocoding with the G-NAF Point Address Dictionary. G-NAF is the authoritative address reference for Australia and the G-NAF Dictionary provides the highest level of geocoding precision. Single Line Address Geocoding MapMarker Australia v14 can geocode input addresses in which address components are entered on a single line. For example: 18 Merivale St, South Brisbane, QLD, This example uses commas as delimiters within the address, but you can use semicolons, colons, or non-delimited single line addresses. Non-delimited or partially delimited single line addresses may take longer to geocode and may not produce the same results as delimited single line input. To optimize single line geocoding, use delimiters between address components (particularly between street name and town/suburb). This is described in the topic Using Single Line Address Geocoding in Chapter 4 (Geocoding with MapMarker Australia) of the MapMarker Australia User Guide. Level Information for G-NAF Addresses MapMarker Australia v14 now returns level information if this information is in the available in the G-NAF data. When using the G-NAF dictionary, Level number is provided for NSW, ACT, VIC, and WA. Level type information (such as G for Ground) is provided for all states. For example, the following input address: U Kavanaugh St, Southbank VIC, 3006 returns: U113 Level 11, 22 Kavanaugh St, Southbank VIC, 3006 Invalid level information in the input address is changed or removed. This is described in the topic G-NAF Level Information Address Matching in Chapter 4 (Geocoding with MapMarker Australia) of the MapMarker Australia User Guide. MapMarker Australia v14 Release Notes 2

3 Accept Only Street Address Matches The Match Restrictions tab of the Geocode dialog includes a selection for Accept Only Street Address Matches. Previously, if Accept Only Street Address Matches was checked, only street level (S5) candidates were returned. MapMarker Australia v14 has been improved so that S5, S7, or S8 candidates are now returned. Additionally, an S4 match is returned if there is a house number match (which could happen for a return from a G-NAF dictionary). This feature is illustrated in the topic Match Restrictions Preference Dialog in Appendix A (MapMarker User Interface Reference) of the MapMarker Australia User Guide. Geocoding to PID When using the G-NAF dictionary, you can find an address based on the unique Persistent Identifier (PID). If the PID is found, a single close match candidate is returned with an S8G result code. G-NAF metadata is also returned for the candidate. This is described in the topic G-NAF PID Geocoding in Chapter 4 (Geocoding with MapMarker Australia) of the MapMarker Australia User Guide. PO Box Geocoding MapMarker Australia v14 now geocodes PO Boxes to the Post Office location where the PO Box is located. A variety of PO Box formats are accepted. For matching purposes, the input address postcode is preferred over the suburb/ locality. This is described in the topic PO Box Geocoding in Chapter 4 (Geocoding with MapMarker Australia) of the MapMarker Australia User Guide. Returning Standard or Frontage G-NAF Coordinates When using the G-NAF dictionary, MapMarker Australia v14 can return the unmoved Standard G-NAF coordinates or coordinates that have been slightly shifted to indicate the frontage of the returned candidate. The Standard coordinates are the most precise, but the Frontage points are generally more suitable for routing purposes. MapMarker Australia v14 provides this functionality via one set of G-NAF dictionaries, whereas it previously required two different G-NAF dictionary sets. This is described in the topic Generating G-NAF Standard Points or Street Frontage Points in Chapter 4 (Geocoding with MapMarker) of the MapMarker Australia User Guide. Returning Original (Untruncated) G-NAF Coordinates MapMarker Australia v14 can optionally return the original G-NAF coordinates, exactly as they appear in the G-NAF source data. These are highly precise coordinates (up to 8 places to the right of the decimal point). In the Desktop application, you can map the appropriate output columns to return the original G-NAF X and Y coordinates. This is described in the topic Original Coordinates in Chapter 5 (Understanding the G-NAF Data) of the MapMarker Australia User Guide. Improved Range Address Geocoding with Segment Data A ranged input address will return a close match candidate based on the first number of the range. For example, input of Meagher St. will return a close match on 20 Meagher St. Previously, this would return a non-close match candidate. This is described in the topic Suffix / Range House Number Geocoding in Chapter 4 (Geocoding with MapMarker) of the MapMarker Australia User Guide. MapMarker Australia v14 Release Notes 3

4 Fallback During Interactive Geocoding During interactive geocoding, if no close match candidate is found, you can optionally fallback to a postal or geographic centroid match. In the Desktop Application, this option is controlled by new selections on the Interactive Geocoding dialog box. Fallback options are described in the Chapter 4 (Geocoding with MapMarker Australia) of the MapMarker Australia User Guide. Postal Geocoding Changes For Postal geocoding (or fallback to Postal geocoding) the postcode and state is now returned instead of the suburb. This avoids the possibility of confusing a suburb name with the authoritative postcode name. Operating Requirements This section describes the software and hardware requirements for running MapMarker Australia v14. Operating Systems MapMarker runs on the following operating systems: Java API Windows 2000 Advanced Server with SP4 Windows XP Professional with SP2 Windows 2003 Enterprise Edition Windows Vista Ultimate Edition Solaris 2.9, 2.10 HP-UX 11.0 Red Hat Linux kernel version 2.6 SUSE Linux 10x C API Windows 2000 with SP 4 Windows XP Professional with SP2 Windows 2003 Enterprise Edition Solaris 2.9, 2.10 HP-UX 11.0 Desktop Application Windows 2000 with SP4 Windows XP Professional with SP2 Windows 2003 Enterprise Edition Windows Vista Ultimate Edition Java Virtual Machine MapMarker requires a Java Virtual Machine (JVM) to run. The following JVMs are supported: JVM v.1.5 or higher MapMarker Australia v14 ships with: Sun JRE v.1.5.0_09 (for Microsoft Windows and Sun Solaris) MapMarker Australia v14 Release Notes 4

5 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 v.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 Microsoft Data Access Components 2.8 is required to use MapMarker with a SQL database. This component is installed automatically when you install the MapMarker Desktop Application, either on a standalone workstation or on a client machine. The MapMarker Desktop Application installer and the client setup program both install the Jet 4.0 database engine for use with Microsoft Access. The Jet 4.0 package and the MDAC 2.8 installer together install a number of ODBC drivers for use with MapMarker. The following ODBC databases and drivers are supported. In some cases, you must download and install the appropriate driver that suits your needs. SQL Server 2005 SQL Server 2000 Microsoft Access 2007 (Link to download: driver for Microsoft Access 2007) Microsoft Access 2003 MapMarker also supports the following Oracle drivers: Oracle 10G Release 1and 2 Oracle 9i Release 2 You must install the Oracle driver separately. To use the driver, you must have the Oracle 9i client installed. Supported Web Servers The following Web servers are supported: Apache Tomcat 5.5 Oracle 10G Application Server BEA WebLogic 9.1 IBM WebSphere 6.0 Supported MapInfo Products MapMarker Australia v14 can integrate with the following MapInfo products: MapInfo Professional MapInfo AnySite MapInfo Target Pro Envinsa MapMarker products for other countries (New Zealand, USA, etc.) MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server MapMarker Australia v14 Release Notes 5

6 Minimum Hardware and Memory Requirements The minimum system requirements for MapMarker on a full installation of the Desktop Application and Developer Product (SDK) are: 800 Mhz Pentium processor or equivalent 512 MB RAM 2 GB available disk space (including G-NAF data) Recommended Hardware and Memory Requirements For optimal performance of a full installation of both the Desktop Application and Developer Product (SDK) we recommend: 2.5 Ghz processor 1 GB RAM 10 GB available disk space Changes with MapMarker Australia There are additional changes in MapMarker Australia v14 compared to earlier versions of the product. Pitney Bowes Business Insight Branding MapMarker Australia is one of the many location intelligence products offered by Pitney Bowes Business Insight. This newly formed single division of Pitney Bowes Software Inc. unites two industry leaders MapInfo and Group 1 Software to bring the best of both worlds to our customers and partners. Pitney Bowes Business Insight offers a unique combination of location and communication intelligence software, data and services that can be leveraged throughout an organisation. Generating Reports, Log Files, and Updating Tables On Windows Vista systems with UAC enabled., users might not be able to write to the default Programs folder. In that case, users could not generate reports, log files, or update tables when using Windows Vista. To solve this problem, we have standardized the default location where log files, error files, and TAB files are located. The log file and TAB files are in: \My Documents\MapMarker_AUS The error file is in: C:\Documents and Settings\All Users\Application Data\MapInfo\MapMarker\AUS\14.0 Changes in Offset Default Values for Desktop Application For the desktop application, the default street offset value is 10 meters and the default corner offset value is 12 meters. These offset defaults are controlled on the Offset tab of the System Preferences dialog. These changes establish consistent default values for the desktop application and the Java API. MapMarker Australia v14 Release Notes 6

7 Fixes to Customer-Reported Issues We have worked to address problems and bugs that have been reported by our customers. Feedback was gathered from customer correspondence sent to This feedback is integral to our continual improvement of our products. The following customer-reported incidents have been fixed in MapMarker Australia v14. The leading numbers are the Incident Numbers that Pitney Bowes Business Insight uses to track these customer issues. In some cases, the description is a consolidation of several related Incident Numbers. T26608: When a numbered street of 12 or higher is spelled out, MapMarker did not return the correct abbreviation. For example, an address like 11 Twelfth St. was returned as 11 12ND St. This has been corrected, and 12TH St. is now returned. T26420: Street intersection geocoding did not always handle misspellings and suburb alias names. For example, a street intersection input address: Meryvale St && Peel St, South Brisbane, 4101, QLD did not return a geocoding match. If the street was correctly spelled as Merivale, the match was made. MapMarker Australia v14 now handles this type of minor misspelling and the correct candidate with an SX result is returned. T25145: Locality information was returned for postal geocoding. However, it is more useful to return suburb information. MapMarker Australia v14 now returns suburb information with postal geocoded addresses. T25032: State information was not returned for postal geocoding. This has been corrected so that state information is returned with postal geocoded records. This behaviour is consistent with street and geographic geocoding results. U11507: The User Dictionary utility could not build a user dictionary based on the G-NAF dictionary. This has been corrected, along with several other user dictionary related issues. T27963: Under some circumstances, MapMarker Australia truncated the street name on output. This has been corrected. T28066: No close matches wee returned if the wrong state was entered. MapMarker Australia v14 can now return a close match when an otherwise valid address has the wrong state. T28363: The abbreviation Cre was not recognised as an alternative for Crescent. MapMarker Australia v14 now recognises Cre and Cres as valid abbreviations for Crescent. Known Issues 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. Microsoft Windows Vista-Related Issues UNIX / Linux-Related Issues Shared Installation Location of Files Log File for Cancelled or Failed Install Console Installation UNIX Unable to Create User Dictionary 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 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, Start the MapMarker Server, or Stop the MapMarker Server. MapMarker Australia v14 Release Notes 7

8 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 Australia 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 Australia 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 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 Australia 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. 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. MapMarker Australia v14 Release Notes 8

9 Shared Installation Location of Files After the administrator installs the Desktop Application as a Shared application, a licensed user can then run the client desktop installation (ClientSetup.exe). Each client user must have a Desktop license and must be able to access to the shared data on the network. By default, the data is installed in the folder: MapMarker_AUS_v14_Data. Under that folder, the DesktopInstaller folder contains the ClientSetup.exe. 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 Australia Developer Guide for more information. Unable to Create User Dictionary You may get the following error when you attempt to create a large user dictionary: A possible work around for this problem is to increase the java heap size in the geojni.cfg file. The default location of the geojni.cfg file is: C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\geojni.cfg The changed setting is noted in bold below: # # geojni.cfg # # This file defines the jni settings and the # MapMarker Java defaults. # +jvmpath=c:\program Files\MapInfo\MapMarker_Australia\14.0\_jvm\jre\bin\server\jvm.dll +numvmoptions=5 -Djava.class.path=C:\Program Files\MapInfo\MapMarker_Australia\s.0\Desktop\;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmjclient.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmjserver.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmj.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\miutil.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\micsys.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmj_aus.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmjclient_aus.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\miscp.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmjjni.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mmjjni_aus.jar;C:\Program MapMarker Australia v14 Release Notes 9

10 Files\MapInfo\MapMarker_Australia\14.0\Desktop\commons-logging.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mxjgeom.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\mijts.jar;C:\Program Files\MapInfo\MapMarker_Australia\14.0\Desktop\jdom.jar -server -Xms128m -Xmx512m # increase java heap size from 256 to 512 MapMarker Australia v14 Release Notes 10