I need to ignore spaces when matching alphanumeric house numbers (e.g., "101A" matches to "101 A"). It seems like the noise characters found in the XML configuration would be the ideal way of handling this. Am I correct? But I see based on the "Customizing..." white paper that they aren't yet implemented. Anyone know when they will be implemented? Or have ideas for a work-around? Thanks!
ThibautD - you are correct; they are only ignored in the street column. If you have a space in the address number, the user must also enter a space to match it. If the reference data leaves out the space, an address with a space in the house number won't match. Seems inconsistent with the concept of geocoding. And the old 9.3 geocoders had no problem with this. Brad- I am trying to customize the US Single Address locator. Any ideas?
Oh and ThibautD, you suggested fixing the problem by editing the style, and I am trying to do just that. But it's not clear how when the noise_chars don't appear to be field-specific. They are just under grammar>spelling>character_equivalency_table. Thanks for your help.
Thanks, Brad - that helped! Just one question - is there a data dictionary or other reference for the XML format used in the locator configuration file. I found the "Customizing Locators in ArcGIS 10" whitepaper and assumed that was it, but there's nothing in there documenting these different mapping schemas. The comments in the xml file help, but I still don't have a sense of when I would point to one versus another.