ArcGIS Server Banner

Locators in a geodatabase stored in Oracle

Locators in a geodatabase stored in Oracle

Release 9.3 E-mail This TopicPrintable VersionGive Us feedback
Locators are datasets that contain a snapshot of the reference data you would use for geocoding. It contains information on how an address is standardized, the searching methods used for address matches, and the type of information that is returned when there is a match. For more information on how locators are created and used, see the topics in the "Building an address locator" book in this help system. You can begin with Defining the address locator components.

Locators in ArcCatalog

When you connect to your geodatabase in ArcCatalog, if you have created an address locator in your geodatabase, it would appear in the Catalog tree as shown below:

Address locator in ArcCatalog

Locators in an Oracle DBMS

When a new locator is created, a corresponding locator dataset table is created in the geodatabase. The locator dataset table contains a snapshot of the locator’s reference data, which includes all the attribute and shape information needed for geocoding stored in a format optimized for quick information search and retrieval.

After a new locator is created, it does not use the original reference data; it refers to the locator dataset table.

Locator dataset table names are the same as locator names but suffixed with _lox. If the locator name contains spaces, the spaces will be replaced with an underscore in the locator dataset table name.

The locator dataset table is used as a way to persist a collection of binary data blocks (similar to files) in a database.

NOTE: You should not modify the contents of the locator dataset table.

<locator_name>_lox

When you create a locator, ArcSDE reads geocoding specific attributes from the reference feature classes, organizes the data in an efficient proprietary binary structure, and stores a snapshot of the reference data in the locator dataset table. Thus, after the locator is created, it does not use the original reference data but only refers to the locator dataset table. As specified by the EmbedGeocodingRules locator property, the locator may also store a copy of its geocoding rule files in its geocoding index table.

The locator dataset table is used as a way to persist a collection of binary data blocks (similar to files) in a database. You should not modify the contents of the locator dataset table.


Field name Field type Description
FILEID NUMBER(9) ID of the internal geocoding index data block

NOT NULL
SEGID NUMBER(9) ID of a subsection (segment) of the internal geocoding index data block

NOT NULL
DATA BLOB Binary data of the subsection (segment) of the internal geocoding index data block

NOT NULL

Click the link below to view the tables in the DBMS involved in a locator. In this example, the CITY_STREETS_LOX table is the locator dataset for the streetranges locator.

Oracle locator diagram

Another example of the tables that make up a locator can be seen when you click the following link:

Locator example

In this example, a geodatabase contains a STREET feature class that represents street centerlines for a particular geographic area, such as a city. In addition to the geometry for the street centerlines, the STREET feature class contains attributes for the address ranges that can be found along the street and the components of the street name. The table schema required to store a locator to allow address geocoding on this feature class is shown below.

Locators in an XML document

At present, locators are not supported in XML documents. Therefore, if you have locators in your geodatabase, export your geodatabase to an XML workspace document, then import the XML workspace document to another database, you will have to re-create the locators.