Loading the gazetteer data

Loading the gazetteer data

The quickest way to start a Gazetteer Metadata Service is to import the ArcSDE export files on the ArcIMS Gazetteer Data disk into your ArcSDE database. The gazetteer import scripts can only be used with Enterprise ArcSDE. Don't attempt to load the gazetteer export files until you have successfully created a regular Metadata Service in the ArcSDE database.

To create a Gazetteer Metadata Service using the ArcSDE export files on the Gazetteer Data disk, you need to do the following:

  1. Install the gazetteer import scripts
  2. Import the data into ArcSDE
  3. Index the gazetteer places
  4. Create a Gazetteer Metadata Service

If you didn’t install the gazetteer import scripts when you installed ArcIMS, you can run the installation program again to install them; they won’t be installed by default. Choose a Custom installation and install the Gazetteer option under Metadata Solutions. Two scripts are provided with the Gazetteer install option: gazImport.bat for Windows and gazImport.sh for Unix; they are located at <ArcIMS Install location>\Metadata\Gazetteer. Use the script that is appropriate for your operating system to import the gazetteer ArcSDE export files.

The gazetteer import scripts must be run on a machine where Enterprise ArcSDE is installed, or where the SDEHOME environment variable has been set and SDEHOME/bin has been included in the PATH environment variable. You may want to install the gazetteer import scripts onto a different machine than ArcIMS, or copy the appropriate script to a different location from which it can be run.

On the Gazetteer Data disk, the world folder has the following ArcSDE export files containing Gazetteer Metadata Service tables pre-loaded with the world gazetteer places:

The usa folder on the Gazetteer Data disk, has the following ArcSDE export files containing Gazetteer Metadata Service tables pre-loaded with the U.S. gazetteer places:

You can either load the gazetteer data directly from disk, or you can copy the data to the same location as the gazetteer import scripts. When the Gazetteer Data feature is selected, the ArcIMS installation program installs the following ArcSDE export files that you must load into ArcSDE:

When the world gazetteer data is loaded properly it will consume 350-650 megabytes of disk space depending on which database you are using.

You may want to work with your ArcSDE and database administrators to plan where and how to load the gazetteer data. Because the gazetteer needs to be administered separately from other Metadata Services, you may want a different user to own the gazetteer data, and you may want to store the gazetteer data in a different database or tablespace. By default, the gazetteer import scripts will load the data into ArcSDE using the DEFAULTS DBTUNE keyword for SQL Server and DB2 databases, and the IMS_GAZETTEER keyword for Oracle.

You can specify a custom DBTUNE configuration keyword on the command line when running the gazetteer import scripts. For Oracle, a custom keyword used to load the gazetteer data must not include "DISABLE STORAGE IN ROW" in the values for the XML_DOC_LOB_STORAGE and XML_DOC_VAL_LOB_STORAGE parameters. For SQL Server, if a regular Metadata Service and a Gazetteer Metadata Service are in the same database, add a second full-text catalog to the database and use a custom DBTUNE keyword with the new full-text catalog's name in the XML_IDX_FULLTEXT_CATALOG parameter. See Configuring a database to support text indexing for more information.

Coordinate when to load the gazetteer data with the database administrator to ensure this process won’t impact the performance of other operations in the database. Follow the steps below to import the gazetteer data.

  1. Verify that your version of ArcSDE meets the system requirements.
    For information on compatible versions of ArcSDE, go to the ArcIMS Web site and click System Requirements on the left. Specify your configuration, then on the resulting page, click Compatibility Notes in the Quick Links box.
  2. If the gazetteer import script will be run on a machine that does not have ArcSDE installed, add the SDEHOME environment variable and set its value to the ArcSDE install location for the ArcSDE server that will be used to load the data. For example, on Windows, “D:\ArcGIS\ArcSDE\sqlexe”, or on UNIX, “/disk1/sdeexe”. Modify your system’s PATH variable to include %SDEHOME%\bin on Windows or $SDEHOME/bin on UNIX.
  3. Make sure the Gazetteer Data disk is available or copy the ArcSDE export files to the same location as the gazetteer import script.
  4. Open the operating system’s command window and navigate to the location where the gazetteer import script is located.

  5. Run the gazetteer import script for your operating system. The arguments for the script are:

    gazImport <rdbms> <sde_server_name> <sde_instance_port> <database> <username> <password> {config_keyword} {table_prefix} {source_file}

    For Oracle, provide a "#" for the database parameter. The config_keyword, table_prefix, and source_file parameters are optional. If a value isn't provided for config_keyword, the DEFAULTS keyword will be used for SQL Server and DB2 and the IMS_GAZETTEER keyword will be used for Oracle. If table_prefix isn't specified the default table prefix "gazusa92" will be used. If source_file isn't specified, the script will look for the gazusa92 export files in the same folder as the gazetteer import script. To accept the default, value for an optional parameter, provide a "#" in place of another value.

    For Oracle, if you want to use the default DBTUNE parameter and the default table prefix, gazusa92, and you have copied the gazusa92, gazusa92d, gazusa92dr, gazusa92r, and gazusa92u files to the same location as the gazetteer import script, type the following on the command line, for example:

    gazImport oracle sdeServer 5151 # aUser aPassword

    This will create one feature class and four tables in the database named gazusa92, gazusa92d, gazusa92dr, gazusa92r, and gazusa92u. If you want to load the data into the database using the "gazetteer" table prefix, and you want to read the gazworld92 files from the Gazetteer Data disk, type the following on the command line, for example:

    gazImport oracle sdeServer 5151 # aUser aPassword # gazetteer D:\world\gazworld92

    For the source_file argument, you must provide either a full path or relative path to the location of the files along with the table prefix used to name the files. With the value D:\world\gazworld92, the gazetteer import script will look for the files gazworld92, gazworld92d, gazworld92dr, gazworld92r, and gazworld92u in the D\world folder on your computer.

    It takes approximately 20 minutes to load the gazetteer data. While the script runs, you may see error messages indicating that tables such as gazusa92 and gazusa92_v couldn’t be deleted from the database. Ignore this if you haven’t previously installed the gazetteer data using the gazusa92 table prefix—the script attempts to delete preexisting gazetteer tabes from the database before creating new tables with the same name. You will only have a <table_prefix>_v view in the database if you manually created a view with a name like this following instructions provided with earlier versions of ArcIMS to create a custom Gazetteer Metadata Service.

  6. In the command window, navigate to the location where the ArcIMS metadata commands are installed.

  7. Run the aimsmetaindx command with the default indexNew option to add the gazetteer places to the Gazetteer Metadata Service's text index. The places must be indexed before they can be searched. The arguments for the aimsmetaindx command are as follows:

    aimsmetaindx <sde_server_machine> <sde_instance> <database> <username> <password> {table_name_prefix} {logfile} {indexNew | indexAll} {localcodepage}

    Provide the same ArcSDE connection information used to load the data. Provide the table prefix used by the gazetteer import script for the table_name_prefix argument. For example, with an Oracle database, you would type the following on the command line if you accepted the default table prefix when loading the gazetteer data:

    aimsmetaindx sdeServer 5151 # aUser aPassword gazusa92

    It may take a few hours to index the gazetteer place names. With the default Oracle and DB2 DBTUNE settings, the aimsmetaindx command will complete when updates to the text indexes are finished. With the default SQL Server DBTUNE settings, the aimsmetaindx command will finish immediately but indexing will have just begun in the database. See Manually updating text indexes for more information. See the DBTUNE configuration parameter name configuration string pairsfor more information.

  8. Edit the sample ArcXML configuration file, Gazetteer.axl, using a text editor to access the Gazetteer Metadata Service data that you just loaded. Provide the same ArcSDE connection information and DBTUNE configuration keyword used to load the data in the SDEWORKSPACE and CONFIG_PARAMETER elements, respectively. Provide the table prefix used by the gazetteer import script in the TABLE_NAME element.
  9. In ArcIMS Administrator, start the Gazetteer Metadata Service using the edited Gazetteer.axl configuration file. If the Gazetteer.axl file contains the correct information, ArcIMS will locate the feature class and tables that were loaded by the gazetteer import script; because these objects already exist, a new set of objects won't be created in the database.

For regular Metadata Services, it can be useful to set up an automated program to run the aimsmetaindx command or to schedule updates to the text indexes in the database. Because Gazetteer Metadata Services typically are not modified on a regular basis, it would be best to update the text indexes with the latest place names using the aimsmetaindx command after changes are made.

Once the Gazetteer Metadata Service has been started, you can configure Metadata Explorer or other applications to use this service.



Search code: @loading_the_gazetteer_data