Skip to main content

Docker Image Versions

Specify image tags for Verify components. Helmfile (Unix/Linux):
Helmfile (Windows):
Helm:
Contact your Loqate representative for available image tags.

Country-Specific Deployments

Deploy dedicated Spatial-API instances for high-traffic countries to optimize performance and enable independent scaling.

Why Use Country-Specific Deployments

  • Better performance: Dedicated resources for frequently queried countries
  • Flexible scaling: Scale each country independently based on traffic
  • Cost optimization: Allocate resources where needed

Configuration

Set verify.dataset to the ISO 3166-2 country code. Keep a row (rest of world) deployment for other countries. Example: United Kingdom deployment
Example with custom storage path:
Common Country Codes:

Certified Datasets

Verify supports postal authority-certified validation:
  • CASS - United States (Coding Accuracy Support System)
  • SERP - Canada (Software Evaluation and Recognition Program)
  • AMAS - Australia (Address Matching Approval System)

Requirements

  • License key with certified features enabled
  • Certified libraries (downloaded automatically to lib64 folder)
  • Spatial-API configured for the certified country
CASS Restriction: CASS data cannot be downloaded from locations outside the United States due to legal requirements.

Example: AMAS (Australia)

The certified engine activates automatically when licensed libraries are present.

Premium Datasets

Premium datasets provide enhanced data quality for:
  • France
  • Ireland
  • United States

Deployment Options

Option 1: Dedicated deployments (recommended for high volume)
Option 2: Single rest-of-world deployment Set verify.dataset=row to handle all premium countries with one deployment. Simpler but less flexible scaling.

Premium US Resources

The premium US dataset requires more resources:
Apply via Helm:

Resource Allocation

Configure CPU and memory based on expected traffic.

Example Configuration

Via values file:
Via Helm:
Start conservative and adjust based on Prometheus metrics.

AI Parser (Optional)

Enable AI-enhanced parsing for improved accuracy with unstructured addresses.

Requirements

  • Separate persistent storage (at least 4Gi)
  • Additional resources for TensorFlow Serving and AI Parser components

Enable AI Parser

In helmfile, add to QueryCoordinator values:
Configure AI storage:
Uncomment AI Parser sections in helmfile and apply:
See the AI Parser section in helmfile.yaml for detailed configuration.

Next Steps