Frequently Asked Questions (FAQ)
Frequently Asked Questions
Quick answers to common questions about Global Entity Matcher (GEM). For detailed information, see the linked documentation pages.
General Questions
What is GEM and GERS?
GEM (Global Entity Matcher) is a service that automatically aligns your geospatial datasets with GERS identifiers using AI-driven algorithms.
GERS (Global Entity Reference System) is a unique, persistent identifier for geospatial features—part of the Overture Maps Foundation's open standard.
→ Learn more: Understanding GERS IDs | Introduction
How can I access GEM?
Contact our sales team via the GEM product page to discuss requirements and deployment options.
→ Learn more: Getting Started
What use cases does GEM support?
GEM supports government, commercial, smart city, and technology applications including asset management, fleet management, urban planning, and location-based services.
→ Learn more: Use Cases
Will GEM support other data types?
Currently GEM focuses on road networks. Future expansions may include POIs, building footprints, and transit infrastructure as GERS evolves.
Technical Questions
What data formats does GEM support?
Input: Apache Parquet format with required fields: id (integer), is_navigable (boolean), geometry (WKT LineString).
→ Learn more: Data Preparation Guide | Quick Reference
How accurate is the matching?
- Matching Accuracy: >85% confidence for high-quality input data
- Processing Speed: ~100,000 segments/hour
- System Uptime: ≥99%
Quality depends on input data quality, geographic region, and data complexity. Use >60% confidence threshold for filtering.
→ Learn more: Technical Documentation
What are the processing time estimates?
| Dataset Size | Estimated Duration |
|---|---|
| < 10,000 roads | Minutes |
| 10,000 - 100,000 roads | 1-2 hours |
| 100,000 - 1M roads | 10-15 hours |
| > 1M roads | Contact for estimate |
What are the job statuses?
| Status | Description | Action |
|---|---|---|
| Requested | New request received | Pushed to the queue |
| In Progress | Actively processing | Wait for completion |
| Success | Results ready | Download via Azure CLI |
| Failed | Error occurred | Review logs, contact support |
What permissions do I need?
| Level | Capabilities |
|---|---|
| Read Access | View storage, download results, read job data |
| Full Access | All read permissions + upload data, trigger jobs |
Permissions are managed by your organization administrator.
How does GEM handle map updates?
GEM automatically tracks GERS ID changes as Overture Maps updates. By default, the latest available release is used. GERS IDs remain stable when features don't change.
Can GEM integrate with my existing systems?
Yes—cloud, on-premises, or hybrid deployment. Supports Azure CLI workflows, ETL pipelines, and batch processing.
→ Learn more: API Documentation
What about data privacy and security?
- Encryption in transit and at rest
- Role-based access controls
- Compliance with SOC 2, ISO 27001
- Configurable data residency and retention
Comparison Questions
Orbis Maps vs Overture Maps?
| TomTom Orbis Maps | Overture Maps | |
|---|---|---|
| Type | Commercial product | Open data initiative |
| Support | Fully supported | Community-driven |
| GERS | Supports GERS IDs | Defines GERS standard |
Both are complementary—GEM enables interoperability with either through GERS.
GEM vs traditional conflation?
| Aspect | Traditional | GEM |
|---|---|---|
| Approach | Manual/semi-automated | Fully automated AI |
| Reference | Proprietary | Open standard (GERS) |
| Updates | Manual re-conflation | Automatic sync |
| Maintenance | High effort | Low effort |
→ Learn more: Features & Benefits
Business Questions
What's the typical ROI?
Most customers see positive ROI within 6-12 months through:
- 70-90% reduction in manual conflation effort
- Faster time-to-market
- Higher data accuracy
How long does implementation take?
| Phase | Duration |
|---|---|
| Initial consultation | 1-2 weeks |
| Configuration | 2-4 weeks |
| Pilot | 4-6 weeks |
| Production | Varies by scope |
Can I try a pilot project?
Yes! Pilots typically run 4-6 weeks with a representative dataset to validate the approach before full deployment.
Troubleshooting
Authentication fails?
| Issue | Solution |
|---|---|
| Invalid credentials | Verify Client ID/Secret from dashboard |
| Expired token | Click Unwrap again in GEM UI |
| Wrong tenant | Verify Tenant ID matches your organization |
| Azure CLI missing | Install Azure CLI |
File upload fails?
- Verify file exists:
ls -lh /path/to/data.parquet - Check authentication:
az account show - Verify permissions: Ensure Full Access role
- Check format: Must be
.parquetextension
Job submission fails?
- Filename must match exactly (case-sensitive) with
.parquetextension - Required fields must be present:
id,is_navigable,geometry - File must be successfully uploaded to storage first
Job fails during processing?
Run validation on your input file:
1import pandas as pd23df = pd.read_parquet('your_data.parquet')4required = ['id', 'is_navigable', 'geometry']5missing = [f for f in required if f not in df.columns]6print(f"Missing fields: {missing}")7print(f"Null values:\n{df[required].isnull().sum()}")
→ Learn more: Data Preparation Guide
Results download fails?
- Ensure job status is Success
- Verify authentication is still valid
- Check destination directory exists
- Verify sufficient disk space
GEM not visible in sidebar?
Contact your system administrator to:
- Verify your organization has GEM access
- Enable GEM for your project
- Assign appropriate permissions
Still Have Questions?
- Contact Sales: GEM product page
- Documentation:
- Request a Demo: Reach out to see GEM in action