QNAS – Qatar National Address Service Connector by iSolution
The QNAS Connector enables seamless integration with Qatar’s National Address system, providing access to accurate location data for zones, streets, and buildings. It supports retrieving zone lists, street details, building information, and geolocation coordinates.
Integration Overview
This document provides a comprehensive guide for each integration point, detailing its purpose, configuration, and workflow support using the QNAS custom connector.
- Zone List Integration. Retrieves a list of all zones in Qatar.
- Zone Polygon Integration. Fetches polygon boundary coordinates for a specific zone.
- Street List Integration. Retrieves a list of streets within a specific zone.
- Street Polygon Integration. Fetches polygon boundary coordinates for a specific street.
- Building List Integration. Retrieves a list of buildings on a specific street.
- Geolocation Integration. Provides geolocation coordinates for a specific building.
Detailed Integration Documentation
Zone List Integration
| Purpose | Retrieves a list of all zones in Qatar — the entry point for location-data queries. |
|---|---|
| Input details | Required: None (fetches all available zones). |
| Configuration | Ensure the connector is configured to access the QNAS system securely. |
| Output | Successful: a list of zone names or identifiers. Failure: connectivity or configuration errors. |
| Workflow example | 1. Configure the connector. 2. Use Zone List to retrieve zones. 3. Store the zone list for subsequent integrations. |
Zone Polygon Integration
| Purpose | Fetches polygon boundary coordinates for a specific zone — useful for mapping applications. |
|---|---|
| Input details | Required: Zone Name or Identifier (e.g. Zone1). |
| Configuration | Ensure the zone name matches the format returned by Zone List. |
| Output | Successful: polygon coordinates for the zone. Failure: invalid zone name or missing parameters. |
| Workflow example | 1. Retrieve zones via Zone List. 2. Select a zone and use Zone Polygon for its coordinates. 3. Use for mapping/visualization. |
Street List & Street Polygon
| Purpose | Retrieves streets within a zone (Street List), and polygon boundary coordinates for a specific street (Street Polygon). |
|---|---|
| Input details | Required: Zone Name or Identifier; Street Name or Identifier (for Street Polygon). |
| Configuration | Verify the zone/street names are valid and sourced from prior integrations. |
| Output | Successful: a list of street names/identifiers, or a street’s polygon coordinates. Failure: invalid zone/street or connectivity issues. |
| Workflow example | 1. Select a zone via Zone List. 2. Use Street List to retrieve its streets. 3. Use Street Polygon for a street’s boundary. |
Building List Integration
| Purpose | Retrieves a list of buildings on a specific street within a zone — for address-specific queries. |
|---|---|
| Input details | Required: Zone Name or Identifier; Street Name or Identifier. |
| Configuration | Confirm zone and street names are accurate and sourced from prior integrations. |
| Output | Successful: a list of building names or identifiers. Failure: invalid zone or street parameters. |
| Workflow example | 1. Navigate zones and streets. 2. Use Building List to retrieve buildings on the street. 3. Store the building list. |
Geolocation Integration
| Purpose | Provides geolocation coordinates (latitude and longitude) for a specific building — essential for location-based services. |
|---|---|
| Input details | Required: Zone Name/Identifier; Street Name/Identifier; Building Name/Identifier (e.g. BuildingX). |
| Configuration | Ensure all parameters are valid and obtained from prior integration points. |
| Output | Successful: latitude and longitude for the building. Failure: invalid zone, street, or building parameters. |
| Workflow example | 1. Identify a building via Zone/Street/Building List. 2. Use Geolocation to fetch its coordinates. 3. Apply in location-based applications. |
Example Workflow: Retrieving Geolocation of a Building
| Prepare query | Configure the connector to access the QNAS system. |
|---|---|
| Retrieve zone → street → building | Use Zone List, Street List, and Building List to drill down (e.g. Zone1 → StreetA → BuildingX). |
| Fetch geolocation | Use Geolocation to retrieve the building’s coordinates; store lat/long for application use. |
| Monitor | Track integration activity via Google Cloud Monitoring/Logging; verify parameter formats to avoid errors. |
Use Case
A logistics tech provider integrates the QNAS Connector with Google Cloud Platform (GCP) to enable precise location intelligence in Qatar. Through zone, street, and building retrieval from the QNAS API, the provider builds a verified address hierarchy. Using the geolocation endpoint, exact latitude and longitude coordinates for buildings are retrieved and mapped via Google Maps. This data is exported to BigQuery using Cloud Functions and visualized through Looker Studio — enhancing last-mile delivery, asset tracking, and service-location accuracy.
For technical support, contact custom-connectors-support@isolutions.sa.