Name
Temporarily disable spatial indexes during geocoding process
Temporarily disable spatial triggers during geocoding process
Commit scope
Precision level
Properties
WHERE clause
Schema
Table name
OK
Cancel
Use this window to run a geocoder in batch mode on the selected spatial layer. A geocoder transforms the non-spatial source data of the spatial layer into the spatial format required for this spatial layer.
For example, if this spatial layer had source data in columns NAME, ADDRESS, CITY, STATE, ZIP and was defined on a table column LOCATION of spatial data type ST_Point, the geocoder would take the source data and transform it to the ST_Point type to be used for the LOCATION column.
Name
Temporarily disable spatial indexes during geocoding process
Temporarily disable spatial triggers during geocoding process
Commit scope
Precision level
Properties
WHERE clause
Schema
Table name
OK
Cancel
Name
Use this box to select the registered geocoder that you want to run. The default value is the name of the geocoder that is shipped with the DB2 Universal Database Spatial Extender.
Temporarily disable spatial indexes during geocoding process
Select this check box to indicate that any spatial indexes that exist on the spatial layer column should be disabled during the geocoding process. Disabling the spatial indexes during geocoding will improve the performance of the process. The spatial indexes will be re-enabled after the geocoding process is finished.
The default is selected; that is, the indexes are disabled during the geocoder process.
Temporarily disable spatial triggers during geocoding process
Select this check box to indicate that any spatial triggers that exist on the spatial layer column should be disabled during the geocoding process. Disabling the spatial triggers during geocoding will improve the performance of the process. The spatial triggers will be re-enabled after the geocoding process is finished.
The default is selected; that is, the triggers are disabled during the geocoder process.
Commit scope
The Commit scope box contains the number of records to be geocoded before a commit is done on those records. For example, if this box contains the number 100, a commit is done for every 100 records that are geocoded.
The default is 1000 records. To change this number, use one of these methods:
Precision level
Use this spin button to specify the precision of the geocoding process. The maximum precision of geocoding (for example, house or apartment number) is 100. The minimum precision (for example, city level) is 1.
Properties
Use this box to specify any vendor-specific switches you want to control the geocoder.
WHERE clause
Optional: If you want to geocode only a subset of the rows in the table, use this box to specify a SELECT WHERE clause that will specify the criteria for the rows that you want. The WHERE clause can refer to any column in the selected table.
For example, type
Schema
Optional: Use this box to specify the schema for the report table. The report table is used to collect errors, if any, that occur during the geocoding process.
Use one of these methods:
push button
to open a window in which you can browse for the schema that you want.
If you do not specify a schema name, the current schema is used.
Table name
Optional: Use this box to specify the name of the report table that will be created in the schema that is specified in the Schema field. The report table is used to collect errors, if any, that occur during the geocoding process. The name you specify must not already exist in the schema specified in the Schema field.
Use one of these methods:
push button
to open a window in which you can browse for the table that you want.
