Installing Databases for Global Geocoding - spectrum_platform - 23.1

Spectrum Installation Guide for Linux
Product type
Software
Portfolio
Integrate
Locate
Verify
Product family
Spectrum
Product
Spectrum > Spectrum Platform
Version
23.1
Language
English
Product name
Spectrum Technology Platform
Title
Spectrum Installation Guide for Linux
Copyright
2024
First publish date
2007
Last updated
2024-12-10
Published on
2024-12-10T17:44:21.099131

International geocoding databases contain the data necessary to perform geocoding and reverse geocoding for locations outside the U.S. Each country has its own database, and some countries have optional databases that provide enhanced geocoding.

These databases are for use in Global Geocoding.

Note: Do not install geocoding databases on a network drive. Doing so can cause performance problems.

To install the international geocoding databases you need to meet the following requirements:

  • You must have Java 11 installed.
  • You must point your JAVA_HOME environment variable to your JDK 11 installation location.
  1. Download your Spectrum Product Database (SPD) format files from Precisely using the link provided in the Precisely communication or from data.precisely.com.
  2. The database is downloaded as a zip file. Unzip the database before proceeding with the installation.
  3. Install the SPD files:
    1. Place the SPD files in SpectrumDirectory/server/import. This is the default location for SPD files. The Spectrum Technology Platform server monitors this folder and looks for new files in two-second intervals.
      You can change the location of the data import directory by altering the spectrum.import.dir property in the SpectrumDirectory/server/conf/spectrum-container.properties file.
    2. When the server detects new SPD files, the server automatically extracts the SPD files to SpectrumDirectory/server/ref-data.
      You can change the location of the data storage folder by altering the spectrum.data.manager.storage.dir property in the Data Manager settings section of the SpectrumDirectory/server/conf/spectrum-container.properties file.
  4. At this point the data will become available and you can add it as a Spectrum database resource in the Spectrum Databases section of Management Console.
  5. After you install the database files, use either the Database Resource tool in the Management Console or the Global Addressing Administration Utility database commands to define the database as a resource.
  6. After the SPD files are extracted and are no longer needed, use the CLI commands to delete the SPD files. Do not manually delete the SPD files from the location where the server extracted the SPD files. Instead, use these CLI commands to delete the SPD files. For more information about the Product Data CLI commands, see Administration Utility in your Spectrum Technology Platform Administration Guide.
    1. Run the productdata list command to view the details for the currently installed SPD files. The results provide current information without having to access the file system. We suggest that you run this command before you run the productdata delete command, to make an informed decision about the data to delete.
    2. Run the productdata delete command to delete the SPD files from the Spectrum Technology Platform.

      Example

      productdata delete --p productName --c productComponent --q qualifier --v dataVintage

      spectrum> productdata delete --p gam --c gav --q GAV-DEU --v 201907

AUS G-NAF

If you installed the Australia Geocoded National Address File (G-NAF), you must specify the GNAF123 and GNAF456 as separate paths but in the same database resource in Management Console. GNAF123 contains the point-level dictionary. This has the highest precision of geocoding (characterized by Reliability Level 1, 2, or 3.) GNAF456 contains the remainder of address information in G-NAF that does not meet high precision geocoding criteria (characterized by Reliability Level 4, 5, or 6.) We recommend that you use both databases to validate the existence of addresses but only use GNAF123 for parcel-level geocoding. If you do not require parcel-level geocodes you can use GNAF456 for geocoding.