MapMarker Plus 13.0 Release Notes

Transcription

1 MapMarker Plus 13.0 Release Notes These Release Notes accompany the MapMarker Plus 13.0 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 13.0 User Guide and Developer Guide. All of these documents are available at: Corporate Headquarters: Phone: Fax: Sales: Government Sales: Technical Support: Pitney Bowes MapInfo Corporation. All rights reserved. MapInfo and the MapInfo logo are trademarks of Pitney Bowes MapInfo Corporation and/ or its affiliates. August 2007 Table of Contents New Features Operating Requirements Changes with MapMarker Plus Fixes to Customer-Reported Issues Known Issues and Clarifications Geocoding Changes Implemented with MapMarker 11 or Later. 9 1

2 New Features MapMarker Plus 13.0 includes the following new features and feature enhancements. This section provides brief descriptions of these feature. For a more complete description, see the MapMarker Plus 13.0 documentation Single line address geocoding. MapMarker can now geocode input addresses in which address components are entered on a single line. For example: "1 Global View, Troy, NY". This is described in chapter 3 of the MapMarker 13.0 User Guide in the topic "Using Single Line Addresses in Geocoding". Address range geocoding: Some business locations are identified by address ranges. For example, a shopping plaza could be addressed as Front St. MapMarker now can geocode these types of address ranges. This is described in chapter 3 of the MapMarker 13.0 User Guide in the topic Address Range Geocoding. Geographic geocoding (city, county, state): If the input address consists of a valid combination of city, county, and state (but no further address information), you can still geocode to the city, county, or state centroid. This is described in chapter 3 of the MapMarker 13.0 Desktop User Guide in the topic Geographic Geocoding. Geographic Fallback Preferences: If MapMarker cannot match a record to the level or precision you have requested (such as street level), it can now fallback to City, County, or State. These new preferences are described in chapter 3 of the MapMarker 13.0 User Guide in the topic "Fallback Preferences". Prefer Matching ZIP Code over Matching City: When multiple close matches are generated, MapMarker selects the City close match over the ZIP Code close match by default. But you can use a new preference to accept a close match on postal code in preference to a close match on city, This is described in chapter 3 of the MapMarker 13.0 User Guide in the topic "Mulitiple Match Preferences". Report DPV expiration date (new API method): The MapMarker Java API has a new method that can be used to report the DPV expiration date. This is described in the MapMarker Developer Guide in the topic Determining DPV Availability. In the Desktop Application, the select Help > About to see the DPV expiration date. Reduced Memory Usage Option: You can choose to run MapMarker with a smaller memory footprint. This is described in the MapMarker Developer Guide in the topic: Configuring MapMarker for Reduced Memory Usage. Quick Initialization Option: You can configure MapMarker to startup more quickly. Faster startup may be important if you typically use MapMarker to geocode single addresses rather than geocoding a large number of addresses. This is described in the MapMarker Developer Guide in the topic: Configuring MapMarker for Quick Startup. Additional information in Help About box: The Help About dialog box displays complete MapMarker version information, including the data vintage. Address Dictionary Update The MapMarker Plus 13.0 Address Dictionary has been updated with the data generated from the following sources: Address data from the USPS ZIP + 4 database (vintage July 2007) Street geometry from Tele-Atlas, Inc. Dynamap 2000 Street Network Files (vintage July 2007) ZIP + 4 Centroids from Tele Atlas, Inc. Dynamap /ZIP + 4 Centroids (vintage Jul 2007, USPS currentness For MapMarker Plus 13.0, the total size of the Address Dictionary files for all states plus Puerto Rico Is approximately 2.26 GB. For a table of Address Dictionary File Sizes for each state, see the MapMarker Program Files appendix of the MapMarker Desktop User Guide. The Address Dictionary is updated quarterly to comply with USPS CASS standardization requirements. The CASS expiration date for MapMarker Plus 13.0 is October 28, MapMarker Plus 13.0 Release Notes 2

3 Operating Requirements This section describes the software and hardware requirements for running MapMarker Plus 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 9x 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 or later MapMarker Plus 13.0 ships 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) 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 _04 or earlier. For this reason, we recommend that you use JVM 1.5.0_05 or later when high server performance is required. MapMarker Plus 13.0 Release Notes 3

4 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 2000 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 13 can integrate with the following MapInfo products: MapInfo Professional MapInfo AnySite (USA) MapInfo Target Pro (USA) MapMarker Canada Envinsa MapMarker Geocoding Extender for Oracle MapMarker Geocoding Extender for SQL Server Note: You cannot install the same major version of MapMarker Plus USA and the standard version of MapMarker on the same workstation. However, you could install different major versions of MapMarker Plus and standard. For example, MapMarker 12 standard version could co-exist with MapMarker Plus 13. 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 256 MB RAM 5 GB available disk space (including 4GB for entire U.S. Address Dictionary) More specifically, the disk space requirements are as follows: MapMarker Plus 13.0 Release Notes 4

5 0.5 GB for DPV data (available with MapMarker Plus) 25 MB for the MapMarker software (100 MB if installed on a shared installation client since the JRE must also be installed) 100 MB for the JRE 20 MB for Tomcat web server 13 MB for the MapMarker SDK (with the Developer Product) 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 Plus 13.0 You may notice the following changes in MapMarker Plus 13.0 compared to earlier versions of the product. CASS Report Generation Requires DPV DPV confirmation is required for CASS reports. If you choose Produce a CASS Report in CASS geocoding preferences, the Use DPV mode check box is automatically checked. Enhanced ZIP + 4 and DPV Requirement If you are using DPV mode, and the address does not DPV confirm (with Y, S, or D confirmation code), then the USPS requires us to return ZIP Code and carrier route only for mailing-related information. That is, MapMarker will not return the Delivery Point, Check Digit, RecordType, or DefaultFlag. DPV Expiration If DPV expired on your system, MapMarker still functions normally except that you cannot use DPV and cannot create a CASS report. However, you can still geocode with CASS rules. This has been clarified in the DPV Data Expiration topic of the Desktop User Guide. You can also see the DPV expiration date when you select Help > About in the MapMarker Desktop Application. Exact Match Requirement More Strictly Enforced This behavioral change was made in response to Incident Number T23116 from the Pitney Bowes MapInfo incident tracking database. MapMarker Plus 13.0 now considers the street type as part of the Exact Match criteria. So if you require an Exact Match on Street Name and attempt to geocode the following address: 1 Global Rd, Troy NY you will not receive any close match candidates, because the input address has the wrong street type (Rd instead of Vw). This change in behavior is more consistent with the commonly understood interpretation of "exact match". MapMarker 12.x would correct the wrong street type and return an Exact Match candidate. That behavior was confusing since it did not meet the expected definition of "exact". MapMarker Plus 13.0 Release Notes 5

6 If you do want MapMarker to return more candidates, you can relax the match restrictions or use CASS mode to correct the address. Intersection Geocoding If your data contains intersections separated by a single ampersand (&), or the word "And" you may receive unexpected results. To avoid this problem, do not include ampersands or the word "And" in your input data. Fixes to Customer-Reported Issues We have worked to address problems and bugs that have been reported by customers. Following is a list of customer-reported incidents that have been addressed in MapMarker Plus The leading 'T' numbers are the Incident Numbers that Pitney Bowes MapInfo uses to track these customer issues. In some cases, the description is a consolidation of several related Incident Numbers. All of these items have been fixed in MapMarker Plus T17832: S4 or SX candidates do not return city name when UD source has a blank (or invalid) ZIP Code. S4 and SX candidates returned from a User Dictionary can now include the city name even if the ZIP Code was invalid or missing. T20134: Close candidate is not returned when US is mis-typed as UD. For example, UD HWY 12, LITCHFIELD MN was not returned as a close match. UD is now recognized as a typographical error for US T20138: Close candidate is not returned when there are leading zeroes in address number. For example, address of 5820 W 0720 N RD was not returned as close candidate. Leading zeroes are now ignored and the address is properly returned in non-cass mode. T20155: Close candidate is not returned when address has various abbreviations of County. For example, CTY RD 26 did not return a close match as expected. CTY and CNTY are now recognized correctly. T20210: Inconsistent geocoding results on a place name with and without a number prefix. For example, an address with a numeric prefix such as "1 Safeco Field" might generate a false close match. Number prefixes for place names no longer generate the questionable close match. T21178: Close candidate is not returned when address is missing the word "And". For example, 7411 N SOUTH HWY, LEWISTON ID did not return a close match but 7411 N AND SOUTH HWY did return a close match. The close match is now returned as expected. T21181: Close candidate is not returned when address is missing Highway designation. For example, 705 US 12 W, BOWMAN ND did not return close match candidate as expected, but 705 US HIGHWAY 12 W, BOWMAN ND did return a close match. This was fixed in an earlier release, but not previously documented in Release Notes. T When using both a user dictionary and address dictionary, postal code geocoding can return two close matches. We now return a single close match, as determined by the user-specified dictionary priority. T Developer Guide is missing information on S7 and S8 result codes. The S7 and S8 georesult codes are now documented in both the User and Developer Guides. T Documentation has incorrect and incomplete information on 15-character census blocks. Documentation has been updated. T21104: Close candidate is not returned for addresses like 1151 Walnut Hill West LN, Irving TX The West pre-directional is now interpreted correctly. T21105: Eastbound is not recognized as a street type. For example, Route 46 Eastbound, Fairfield NJ, now returns a close match as expected. T21107: Extra information in the input address was interfering with geocoding. MapMarker now parses out this extra information and returns a close match. T22894: In some cases, the alias candidate (with an S2 match) is returned as the first candidate, even though the second match in the list is an exact match (with an S5 result code). The S5 candidate is now placed at the top of the list. T20529: When geocoding in CASS mode, some close candidates is not returned as expected. For example, addresses such as 23 Cobb Pkwy Hwy 41 were not recognized properly because the word "Hwy" immediately followed "Pkwy". This address input is now handled correctly. T21415: Address with fractional number is not returning close match candidate. For example /4TH CLARA ST, CUDAHY CA was not returned as a close match. The "TH" is now ignored as part of the fractional address and the candidate is returned. MapMarker Plus 13.0 Release Notes 6

7 T21521: When periods are used to abbreviate U.S. Hwy, a close match is not found. For example, 6360 U.S. ROUTE 60, BARBOURSVILLE WV was not returned as a close match. The same address entered with no periods in US was correctly returned. the abbreviated U.S. is now recognized correctly. T21522: When periods are used to abbreviate ST. a close match is not found. For example, 6306 ST. RT. 7, PROCTORVILLE OH The abbreviated ST. is now recognized correctly. T21560: Multiple close candidates are returned when only one close match candidate is expected. When two candidates have the same main address, the one with ZIP + 4 information is now promoted to a close match and the other candidate is demoted. T20925: Close candidate is not returned for input address: 7900 THIRTY FIRST ST, Baltimore MD The spelled-out number "First" is now recognized and the address is returned as a close candidate. T20927: Close candidate is not returned with certain input addresses. For example: 6300 GEORGE WASH DR, CAMP SPRINGS MD was not returned. This has been resolved. T23116: Address with incorrect street type is returned with missing street type. With Exact Match required, an input address like: 200 N 22ND ST, MER ROUGE, LA was erroneously returning a close candidate of: 200 N 22ND, MER ROUGE, LA (with the street type missing). This example no longer returns a false close match candidates when Exact Match is required. A related behavioral change is described in Exact Match Requirement More Strictly Enforced on page 5. T21643: Geocoding failure with Parcel Precision data and address point interpolation preference. This has been fixed. T30677: ORA error when triggering MapMarker script. T23329: Using RPC server and MapMarker OCX, error 1843 halts the server when a bad address is encountered. The error message box has been eliminated so that geocoding can continue without the user clicking OK in the dialog box. Incomplete documentation for XML Get Versions Request. There was an incomplete Get Versions Request code snippet in the XML API chapter of the Developer Guide. This has been corrected. Known Issues and Clarifications The following section covers changes that were made after the MapMarker User Guide and Developer Guide were finalized. This also includes issues specifically related to Windows Vista, UNIX/Linux platforms, and workarounds to known issues. Microsoft Windows Vista-Related Issues, p. 7 UNIX / Linux-Related Issues, p. 8 Shared Installation Location of Files, p. 8 Log File for Cancelled or Failed Install, p. 9 MapInfo Streets Plus Shipped with MapMarker Plus, p. 9 S8 Georesult Codes and Address Interpolation, p. 9 Permissions on Geoappl Testing Application, p. 9 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. You must be an Administrator, and You must run the application with administrator credentials applied. MapMarker Plus 13.0 Release Notes 7

8 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 as described in the topic Starting the MapMarker Server in Chapter 2 of the MapMarker Version 13 Developer Guide. from an Administrator Command Prompt. Note: 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 2 of the MapMarker Version 13 Developer Guide. -Generating reports, log files, and updating tables: CASS 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 3 of the MapMarker Version 13 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 CASS 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. 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_USA_v13_Data. Under that folder, the DesktopInstaller folder contains the ClientSetup.exe. After completing the Shared installation, the administrator can share the MapMarker_USA_v13_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. MapMarker Plus 13.0 Release Notes 8

9 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 ( / ). MapInfo Streets Plus Shipped with MapMarker Plus MapInfo Streets Plus is shipped on separate media and included in your MapMarker Plus product box. This was not clear in the User Guide. S8 Georesult Codes and Address Interpolation It is possible to return an S8 candidate from geocoding when address point interpolation is not turned on. If the candidate is itself an address point, an S8 result code will be returned whether address point interpolation is turned on or not. This corrects an issue where geocoding without address point interpolation returned an S5 result code for candidates that were address points. This is the only instance that an S8 result code can be returned without using address point interpolation. A candidate cannot be promoted to S8. Nor can an S7 result be returned, unless you use address point interpolation. Permissions on Geoappl Testing Application The geoappl application is a C-based test program that can geocode a sample input file. This program is included with the Developer SDK and located in the sdk/additional_tools/geoeng/test directory of your MapMarker Plus 13.0 installation. You can run the program as follows: geoappl [infile] [outfile] [mapmarker data path] However, on HP UNIX machines, the geoappl program will not run unless you do both of the following: 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) Installer Dialog Box Does Not Provide Contact Information When installing In previous releases, the appropriate installation dialog box provided the support contact number so that you could acquire the product unlocking codes. The MapMarker Plus 13.0 installer Licensing dialog box does not provide that information. The serial number is located on a sheet of stickers in the MapMarker package. You also need the unlocking code to install the MapMarker features and data you purchased. Call (800) option 3, between 8 am and 7 pm, EST, Monday through Friday, and the MapMarker License Authorization desk will provide your unlocking code. Have your product serial number ready when you call. Geocoding Changes Implemented with MapMarker 11 or Later This section describes the specific geocoding changes that occurred when upgrading from MapMarker 10 (C-based geocoding engine) to MapMarker 11 (Java-based geocoding engine). This information clarifies these changes in geocoding behavior, and may also be helpful to MapMarker customers. MapMarker Plus 13.0 Release Notes 9

10 Combining Street Segments The MapMarker C (v10.x) engine combines common street segments into one street and returns this information as a single candidate. The Java engine (MapMarker 11.x or later) does not combine common street segments together and it will return multiple candidates for each street segment. This behavior can be seen when using the quick find dialog, try geocoding 1 Global Vw, Troy NY and click the ranges button to view all the street's house ranges. MapMarker 10 returns 1 close candidate with combined segment ranges: 1 GLOBAL VW 1-1, , , , , , MapMarker 11or later returns 1 close candidate with ranges just for that segment t 1 GLOBAL VW 1-1, , Using CASS Rules In MapMarker 10x, several CASS rules were applied only during CASS processing. In MapMarker 11.x or later, a number of these CASS-related rules are automatically used whether or not CASS geocoding is enabled. This change reduces false positives but also reduces the number returned close candidates. An example of this can be viewed when Geocoding 975 W Broadway, Saratoga Springs, NY, MapMarker v10.x would return a candidate for 975 N Broadway. Because the directional degree from W to N is 90 degrees or later MapMarker 11.x will no longer return a close candidate. Changes To Soundex Performance and Close Matches MapMarker 11 or later uses a longer soundex that is designed to reduce false positive candidates and to maximize search performance. With the reduction of false positives a MapMarker 11.x or later, users may see a very slight overall decrease in returned close candidates. A small side effect of this behavior can be seen when geocoding a street name of 'Global VW and Jordan RD'. Since the address does not use a valid intersection token of && it is treated as a street address by both the MapMarker 10 and 11 geocoders. The difference is the MapMarker 10 geocoder will return a close candidate street match of 1 Global VW, while as the MapMarker 11.x geocoder has a tighter soundex routine and will not return a close matched candidate in this case. User Dictionaries with Zeroes in Range Value When creating user dictionaries, MapMarker 11.x or later will no longer recognize house from and to range values of zero. It is recommended that when creating a user dictionary source table any invalid 0 range is changed to an empty string value. MapMarker Plus 13.0 Release Notes 10

11 Following is an example user dictionary source table. The following example shows the behavior for MapMarker 11.x or later: Candidate.score value Eliminated When using MapMarker 11.x or later the Candidate.score property is no longer available. Previously the score value was problematic and confusing to the user because it was misinterpreted to be the overall matching score. Actually the MapMarker 10.x score value was only an address spelling score. It is recommended to use the georesult or result code value to determine overall candidate matching quality. Erroneous Close Matches Eliminated for Rural Route Addresses When using MapMarker Plus 12.2 or later, close match S1 precision candidates will not be returned if the street input address contains a rural route followed by a post office box (for example. RR1 BOX 184A). In earlier MapMarker versions, a close match post office box candidate was returned by error. MapMarker Plus 13.0 Release Notes 11

12 Improved Close Matching for City / ZIP Code Conflicts A ZIP Code, city matching priority change was to made to MapMarker 11.x or later. The new rule states if two candidates are considered close internally and the input Zip Code, city does not correlate then choose the city matching candidate. The understanding is that it is more likely the city is correct than the Zip Code when an input address contains bad information. This rule change is consistent with United States Postal Service standards. More Consistent Georesult Codes In some cases expected georesult or result codes values can be different when comparing results form MapMarker 10.x to MapMarker 11. An example of this is found when geocoding 206 NEW ST,CHAMPAIGN,IL, (Note the input address does not contain a Pre-Directional). The candidate returned is 206 N New St Champaign, IL but the georesult will be different between the MapMarker 10.x and MapMarker 11. MapMarker 10.x will return a hyphen in the georesult (fourth position) for 'P' (as in pre-directional). MapMarker 11 will not return a hyphen in the 'P' position because the pre-directional was not supplied on input, this change was made to help improve consistencies between international geocoders. New Dependencies for C Programming API The C programming API is now re-implemented using the Java Native Interface (JNI). This places new dependencies on the deployment of custom applications as now the Java engine, JNI, and a properties file are now required. Address Type Not Used in Java API The concept of address Type is not used in the Java API. The U.S. adaptor simply sets the value to a default of "10" which used to indicate a street type. Other types were rural routes, PO BOX, Military, etc. Miscellaneous Fixes and Changes in Java-based Geocoder In addition to these behavioral changes, a new OEM licensing process was introduced. There were also several bugs fixed during the Java development process. MapMarker Plus 13.0 Release Notes 12