nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Geocoding Developer's Kit for ArcGIS 10.0?

JonHall

Is there a "Geocoding Rule base Developer Guide", and GDK, for ArcGIS 10.0?

If so, how where may I obtain a copy?
Thanks,
Jon
************************
I looked back a couple months in this forum, and Bruce H. had responded on 8/26/2010 to a similar Q:
"...10.x locators use the all-new geocoding engine in ArcGIS 10. These are customizable via editing the .lot.xml file(s) in the Locators directory. Documentation for this is still under construction, but you should be able to see similarities with the CLS file elements."

Any update on the status of that documentation?
Thanks,
Jon

Find more posts tagged with

Accepted answers

All comments

GabiVoicu

Thank you so very much for your answer Bruce!

Please help me understand better I'm a little confused.

What do you mean by "using the StreetMap Premium 2016 R3 USA locator"?

Yes, my reference data has StName as "Avenue S" but I'm not geocoding my addresses.

I'm trying to build a custom locator for our data to be used online on our city interactive maps.

When you talk about the Standardize Address Tool versus the Geocode Address Tool - what's the difference ?

I really thought the Standardize Address Tool was the section called standardization under the USAddress.lot xml file that we can edit.

We did change a few things in this USAddress.lot file to match our data and we were hoping to learn how to add an exception rule or something to accommodate this scenario as well....

Thank you again

Best Regards

Gabi

bharold

Hello Gabi

If you geocode your addresses then the StName output will contain the value in the reference data, like 'Trail West' and 'Avenue South'. For example this address: "31541 Trail West Rd, Sylvia, Kansas, 67581"

...generates a StName value of 'Trail West' using the StreetMap Premium 2016 R3 USA locator.

The Standardize Addresses tool doesn't know what is in the reference data, whereas the Geocode Addresses tool does. Back in the day parsing addresses was deterministic (any address had only one interpretation) and Standardize Addresses behaved in a controlled fashion. We could not use that approach globally, so unfortunately you need to use Geocode Addresses to do the srandardization. The World Service will work if you do not have StreetMap, but it will cost credits.

Regards

GabiVoicu

Hi Bruce

How exactly should we add the exception in the Standardize Address Tool for street names like "Trail West" to avoid returning West as a suffix but rather as a street name.....

We have a similar scenario on "Avenue S" for example and I'm sure there are many more like that and it seems to be common practice to be able to add an exception rule....but HOW?

Thank you

Gabi

GabiVoicu

OMG Ronnie – thank you , thank you, thank you for your so very prompt response!

You just made my Friday !

Appreciate your inputs and sharing your discoveries a lot!

…it does help to hear and read about your links and comments !

mvolz47

So geocoding addresses with apartment numbers gets better match rates than the OOTB v10 address locator that is supposed to handle sub-units?

RonnieRichards

Hello Gabi,

Unfortunately no we have reverted back to the 9.x locator style for units because the 10.x locators are still not documented well or work very well for that matter. We expect an address locator with units to match at 100% and this is not the case in the current versions and locator style. There are bugs in the new styles.

Below are all of my ArcGIS Ideas, enhancements and bugs which you might consider reviewing and voting for if you agree. Several releases and years later we are still waiting and now looking at 3rd party solutions because when we call support they call this a "Customization" yet no complete documentation exists and we are using the out of the box locator style.

Fully document the Customizing Locator process and update Locator documentation

https://c.na9.visual.force.com/apex/ideaView?id=087E00000005AR4IAM

Standardize Addresses Tool mixed case results and other inconsistencies

https://c.na9.visual.force.com/apex/ideaView?id=087E00000004GOqIAM

#NIM070066 The Standardize Addresses tool does not return the same address standardization using ArcGIS Version 10 address locators as compared to version 9.3.1 address locators.

Update File based locator's reference feature class

https://c.na9.visual.force.com/apex/ideaView?id=087E00000004EhvIAE

Locator style for Apartment / Units in core product

https://c.na9.visual.force.com/apex/ideaView?id=08730000000by67AAA

#NIM081240 [Enhancement] Please add support for building/unit/apartment numbers in the standard locator styles.

#BUG-000093854 When using the US Address-Single House Subaddress locator style with the Find tool, the match score is improved if using '#' as the unit indicator instead of 'APT' even if the original input data uses 'APT'.

#NIM059962 Cannot create an address locator with a multipoint shape file. The result is a Background Processing Error or ArcGIS Application Error.

schemaLockingEnabled for Geocode services

https://c.na9.visual.force.com/apex/ideaView?id=087E0000000CxTRIA0

GabiVoicu

Hi Ronnie !

I know it has been a while since you have posted this thread but I was just wondering if you ever figured out how to make exceptions rules - trying to do the same thing here.

Thanks a lot

Gabi

deleted-user-F4cUDEZyawYe

We too need a Geocoding Rule Base Developer Guide for v. 10.

AllenMartin

May we have an update to the expected availability of the GDK for v10?

Thanks,
Allen

bharold

Hi Ronnie

If your reference data has "Trail West" as the street name then the ArcGIS 10 geocoding engine will interpret any address accordingly, when geocoding. The exception is in the Standardize Addresses tool, which will parse out the highest number of grammar components it can from the input, hence returning West as a suffix direction.

Regards

RonnieRichards

The technical paper is a great start but I am having difficulties trying to find out how to make exception rules. Is using the GDK9.2 and encoding a .pat still the only way?

Like the example in the GDK (page 62), "123 TRAIL WEST" where trail could be a suffix type and west is also a pre/post direction but "TRAIL WEST" is the accepted street name.

I have tried adding TRAIL WEST to the StreetAlias section of ths USAddress.lot.xml but no luck.

Any advice on how to create a new pattern for street name exceptions?

Thanks
Ronnie

bharold

Hi

Please download this technical paper:

http://resources.arcgis.com/gallery/file/geocoding/details?entryID=51EE55F8-1422-2418-7F8B-FD82DE958878

Regards

GastonPezzuchi

Any news on an updated version of ESRI's GDK for ArcGIS 10?

Thanks

bharold

Hi Jon

The "how to" document on locator customization is still in the works, we are hoping to have it ready not long after SP1.

Regards

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.