Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
OpenCage Geocoding Connector
Overview
The OpenCage Geocoding Connector provides access to the OpenCage REST API for geocoding and reverse geocoding. This API allows developers to convert addresses or place names into coordinates and transform latitude/longitude pairs into human-readable locations. It supports JSON, XML, and GeoJSON output formats, making it ideal for logistics, travel apps, mapping solutions, and analytics tools.
Integration Overview
The OpenCage Connector exposes the following endpoints:
- Forward Geocoding – Convert addresses or place names into geographic coordinates.
- Reverse Geocoding – Convert latitude/longitude pairs into addresses and location metadata.
- GeoJSON Support – Retrieve geocoding data formatted for GIS workflows.
- XML Support – Retrieve geocoding data in XML format for legacy or specialized systems.
Detailed Integration Documentation
Forward Geocoding (JSON)
| Operation ID | forwardGeocodingJson |
| Endpoint | /json |
| Parameters |
|
| Purpose | Converts an address or place into geographic coordinates. |
| Output | JSON with coordinates, formatted address, confidence score, and other metadata. |
| Workflow Example | Useful for address lookups in travel or logistics platforms. |
Reverse Geocoding (JSON)
| Operation ID | reverseGeocodingJson |
| Endpoint | /json |
| Parameters |
|
| Purpose | Converts latitude and longitude into a human-readable address and location data. |
| Output | JSON with address, location context, and confidence metadata. |
| Workflow Example | Perfect for displaying user locations or analyzing GPS data. |
Forward Geocoding (GeoJSON)
| Operation ID | forwardGeocodingGeojson |
| Endpoint | /geojson |
| Parameters |
|
| Purpose | Same as forward geocoding but returns data in GeoJSON format for GIS applications. |
| Output | GeoJSON object with coordinates and location metadata. |
| Workflow Example | Useful for mapping or spatial analytics tools. |
Reverse Geocoding (GeoJSON)
| Operation ID | reverseGeocodingGeojson |
| Endpoint | /geojson |
| Parameters |
|
| Purpose | Reverse geocoding with GeoJSON output for spatial systems. |
| Output | GeoJSON object containing location and address data. |
| Workflow Example | Enables integration with mapping libraries and GIS dashboards. |
Forward or Reverse Geocoding (XML)
| Operation ID | geocodingXml |
| Endpoint | /xml |
| Parameters |
|
| Purpose | Provides XML output for forward or reverse geocoding. |
| Output | XML document with location details. |
| Workflow Example | Designed for legacy systems or XML-based integrations. |
Workflow Creation with the Connector
Example Workflow: Location Finder Tool
| Retrieve Agency Information | Use the getAllAgencies action to fetch a list of federal agencies and identify agencies of interest (e.g., environmental-protection-agency). |
| Search Relevant Documents | Execute the searchDocuments action with format=json, conditions[agency_ids][] for selected agencies, and conditions[type]=RULE. Process results to extract relevant documents. |
| Export and Analyze Documents | Use the getDocument action with document_number and format=csv for specific documents. Store CSV files in GCP Cloud Storage and analyze using Google BigQuery. |
This workflow enables applications to explore agency details, search regulatory documents, and analyze data, enhancing regulatory compliance and research capabilities on GCP.
Pricing
iSolution logo - white - transparent 250 px