brad5993

ArcGIS 10.0 SP2 was released today and it has a lot of good improvements for geocoding.

• Performance improvements for geocoding for matching tables of addresses and single address match.
• Overall improvements for geocoding. For example, issues for repairing locators are resolved.
• Locator Style improvements for 10.0 SP2, including correction in ZIP+4 Range locator style to support leading zero of the 4 digit code and improved handling of spelling issues when geocoding.

NOTE:  10.0 SP2 does not contain one of the memory leak fixes that is in ArcGIS 10 SP1 (Desktop, Engine, Server) Geocoding – Memory Leak for Composite Locators Patch. 

Please install ArcGIS 10 SP2 (Desktop, Engine, Server) Geocoding – Memory Leak for Composite Locators Patch on top of 10.0 SP2 in order for the final leak fix to be included.

Today a patch was released for 10.0 SP1 in regards to geocoding.  This patch addresses two memory leaks and I would suggest installing it as soon as it is convenient.  The issues that were addressed are below.

NIM066846- Composite locator leaks memory in ArcGIS Server and may cause stability issues with the geocode service if system resources get low.

Description: When geocoding with a composite locator that is published to ArcGIS Server, memory continues to grow and will not be released until the service is stopped or the service is restarted. If system resources become low, stability issues can occur with the geocoding service.

NIM064726 – Composite locators leak ~50 bytes per geocode.

Description: When geocoding a table of addresses with a composite locator in ArcGIS Desktop, 50 bytes of memory leak for every record in the input table.

ArcGIS 10 SP1 (Desktop, Engine, Server) Geocoding – Memory Leak for Composite Locators Patch

At ArcGIS 10.0 we now have the ability to geocode addresses that are entered in a single line.  Below is a link to a detailed explanation of how Single-line and Multi-line geocoding worked when 10.0 was shipped.  Following the link, I will explain some of the changes that have been made at 10.0 SP1 to further enhance the overall geocoding experience.

What is the difference between Single-line and Multi-line geocoding at ArcGIS 10?

Changes made to Multi-line geocoding at 10.0 SP1

1. Multi-line geocoding now supports entering the entire address in one field for those customers that don’t have their data parsed into separate fields.  For example, the ‘Street or Intersection’ field in the US Address – Dual Ranges locator style will use Single-line geocoding when only the first field is mapped and the other fields are mapped to ‘<None>’.

2. Multi-line input now will only show fields that were used to build the locator.  This reduces the confusion for users because now they will only see the fields that are actually used where before they would see all of them.  For example, if you build a US Address – Dual Ranges locator but only map the Street fields and the zip fields, you will only see ‘Street or Intersection’ and ‘Zip’ when you attempt to batch geocode.

Changes made to Single-line geocoding at 10.0 SP1

1. Added MaxCandidates property with a default value of 200 to help improve Single-line geocoding performance for geocoding that returns a lot of candidates.  When using the ‘Find’ dialog in ArcMap, this property will limit the total number of candidates returned to the value specified, in this case 200.  This property will also get applied if you are using ‘Find Address Candidates’ with SOAP or REST.

2. Added MaxPerfectCandidates property with a default value of 200 to help improve Single-line geocoding performance for geocoding that returns a lot of perfect candidates.  When using the ‘Find’ dialog in ArcMap, this property will limit the total number of perfect (Score of 100) candidates returned to the value specified, in this case 200.  This property will also get applied if you are using ‘Find Address Candidates’ with SOAP or REST.

3. Added SearchTimeout property with a default value of 1 (value is in seconds) to help improve Single-line geocoding performance for geocoding that could take a lot of time such as Gazetteer searches.  When using the ‘Find’ dialog in ArcMap, this property will limit the search time to the value specified, in this case 1 second.  This property will also get applied if you are using ‘Find Address Candidates’ with SOAP or REST.