Geocoding: New Composite Address Locator PDF Print E-mail

Written by AGRC Administrator,

A composite address locator is now available from the agrc ftp site.To download, right click on the link below and select Save Target As: 

ftp://ftp.agrc.utah.gov/SGID_Vector/AddressLocator/GC_StatewideStreets_Composite.loc

After saving this file, make sure the file extension is .loc NOT .loc.txtThis locator references the U024.StatewideStreets feature class and its S_NAME, ALIAS_1, ALIAS_2, and ACS_ALIAS fields. This a file-based locator file with a .loc extension. This small file references 4 address locators on the SGID ArcSDE database server and can be used from ArcCatalog or ArcMap. It should not need to be rebuilt as changes are made to the U024.StatewideStreets feature class . A high speed internet connection is necessary for this locator to perform adequately.

The U024.StatewideStreets feature class contains several attributes to hold alias street names and address coordinate system (ACS) aliases. Examples.

  • Highway 68 is a street name alias for Redwood Road in SL County
  • 1700 W is an ACS alias for Redwood Road in SL County

When setting up a standard address locator in ArcGIS, these fields are not taken into consideration in finding candidate locations for an address to be geocoded. A composite address locator allows for the alias and ACS alias data to be used to make a match when a match is not found when just considering the street name field (S_NAME).

Why is this being distributed as a file? Composite address locators do not currently work when stored within ArcSDE.

Why does this locator not use SDE via Direct Connect? ArcGIS does not seem to support composite address locators via SDE Direct Connects. This .loc file uses the traditional Application Connect. The problem has been reported to ESRI as a bug.


Users' Comments  
 

Display 1 of 1 comments

1. Wed, 01-21-2009 at 11:55 AM

>>>> Greg Williams wrote:>>> 
Is this the one that goes off the AGRC SDE server then? And, Is it possible to get all the files and rebuild the locators so that it is all local?  
 
- Yes the composite locator is built off our SDE server...you can download the locator, examine it and build the same locator off of locally stored data...The SDE-based StatewideStreets dataset is available in SHP and FGDB formats...download here
 
>>> Greg Williams wrote: >>> 
A few more questions...  
 
The composite locator references 4 locators (GC_Statewidestreets, *_Alias1, *_Alias2, and *_ACS) is that correct? I can see GC_Statewidestreets SHP and fileGDB on the link you sent, are all 4 locators built off that file? or are they separate files that need to be downloaded too?  
 
- yes, all off the same file 
 
Is it the same file as on the SDE server?  
 
- yes, should be the same file unless you catch us in between SDE updates and our FTP file update process. I think they are out of synch at the moment but that should be fixed with SHP and fileGDB updates in the next couple days...we update the data about every 6-8 weeks 
 
Are there any cons to downloading the data vs using the server?  
 
- if you use the SDE connection, it probably is a bit slower and obviously it will not work if you can't get an internet connection to our server 
- if you go for the local option, you'll want to download the data periodically to keep it current with our latest updates. We usually post updates as content items on the GIS Portal at http://gis.utah.gov/sgid- transportation/ 
 
Also, do you have a recommendation on the shp vs gdb?  
 
- no hard recommendation really...i'd bet fileGDB is a bit faster though...just a hunch

Display 1 of 1 comments

Add your comment

05, Dec. 2007
Last Updated ( 11, Aug. 2009 )
 
< Prev   Next >

AGRC Contacts | UGIC Contacts

feed image feed image

Utah GIS Portal © 2009 AGRC

Optimized for