Extraction formats overview - static map data
Extraction formats overview – static map data
=============================================
Classification
--------------
Behavior Type: Product information
Decision: UPDATE
Title
-----
Which static map data extraction format should I use (RDF, Navstreets, FGDB, or GDF)?
Symptoms
--------
Customers may report one or more of the following:
Uncertainty about which HERE static map data format is recommended for new integrations.
Difficulty understanding differences between RDF, Navstreets, FGDB, and GDF exports.
Questions about compatibility with database platforms, GIS tools, or compilation workflows.
Concerns about content differences between delivery formats.
Migration planning from legacy GDF, MapInfo TAB, or Shapefile-based workflows.
Confusion about which formats are still available for new customers.
Answer
------
For most new static map data compilation and database-driven workflows, RDF (Relational Data Format) is the recommended HERE extraction format. RDF provides a relational representation of HERE map data, supports premium content integration, and is compatible with common database environments.
FGDB (ESRI File Geodatabase) is typically preferred for GIS-centric workflows using ArcGIS tools.
Navstreets formats remain useful for GIS visualization and regional data consumption scenarios.
GDF 3.0 and certain legacy delivery options are maintained primarily for customers with existing licensed implementations and should generally not be selected for new integrations.
---
Root Cause
----------
HERE provides multiple extraction and exchange formats because customers integrate static map data into different types of production environments, databases, compilers, GIS platforms, and legacy navigation systems. Each format was designed to serve specific technical and operational requirements.
---
Impact
------
Selecting an inappropriate format can result in:
Increased integration complexity.
Additional data transformation effort.
Reduced compatibility with customer tools and workflows.
Higher maintenance costs.
Migration challenges from legacy technologies.
Inconsistent user expectations regarding data structure and supported content.
---
Recommended Actions
-------------------
### Use RDF when:
Building new compilation environments.
Loading HERE data into relational databases.
Using Oracle, Microsoft SQL Server, or similar database platforms.
Consuming multiple HERE premium products.
Flexible product selection is required through metadata-based filtering.
### Use FGDB when:
Working primarily with ESRI ArcGIS environments.
GIS analysis, routing, geocoding, and mapping functions are required.
Direct ArcGIS consumption is preferred with minimal data conversion.
### Use Navstreets when:
GIS visualization is a primary requirement.
Regional delivery models fit operational needs.
Existing enterprise GIS workflows depend on ESRI Shapefile or MapInfo formats.
### Use GDF only when:
Existing production systems already depend on GDF.
Standardized legacy navigation workflows require GDF compatibility.
Significant investments have already been made in GDF-based processing platforms.
---
Format Overview
---------------
### RDF (Relational Data Format) - Recommended
Characteristics
HERE proprietary relational format.
Contemporary data model.
Tables connected through common attributes.
Supports integration of HERE premium products.
Compatible with standard relational database platforms.
Delivered as seamless continental content.
Advantages
Recommended for new compiler implementations.
Flexible product selection through metadata tagging.
Database-friendly structure.
Broad support across database technologies.
Includes tooling for validation, viewing, clipping, and analysis.
Considerations
Delivery packages can be large because multiple content types may be included within a single installation.
---
### Navstreets (ESRI Shapefile and MapInfo TAB)
Characteristics
GIS-focused map representation.
Delivered by region.
Available as:
+ ESRI Shapefile (.shp)
+ MapInfo TAB (.tab)
Advantages
Strong market adoption.
Compatible with many commercial GIS products.
Supports visual exploration of map content.
Useful for enterprise GIS workflows.
Considerations
Shapefile technology is no longer actively advanced by ESRI.
Content differences may exist compared to other delivery formats depending on market requirements.
Primarily intended for GIS usage rather than database compilation.
---
### FGDB (ESRI File Geodatabase)
Characteristics
ArcGIS-optimized representation of HERE data.
Relational structure.
Delivered as seamless continental content.
Advantages
Direct consumption by ArcGIS tools.
Supports routing, geocoding, and mapping workflows.
SQL-based access to relational content.
Strong adoption among GIS-focused enterprise users.
Considerations
Large datasets may result in significant storage requirements.
Compatibility may vary depending on ArcGIS software versions.
---
### GDF 3.0 (Geographic Data Files)
Characteristics
Long-established navigation industry exchange format.
Sequential flat-file structure.
Record types connected through references and pointers.
Advantages
Widely recognized legacy navigation exchange format.
Suitable for organizations with established GDF workflows.
Considerations
Considered a legacy format.
Flat-file structure may increase processing complexity.
Some content types are not easily integrated.
Specialized tools or custom development may be required.
Variations between vendor implementations can reduce interoperability.
---
Expected Behavior
-----------------
Customers can choose the extraction format that aligns with their existing tooling, workflow requirements, and integration architecture.
RDF remains the preferred option for new database-driven and compilation-based implementations.
FGDB and Navstreets remain suitable for GIS-oriented use cases.
Legacy formats continue to support existing licensed customer environments where applicable.
Unexpected Behavior
-------------------
Assuming all formats contain identical structures, tooling, workflows, or content representations.
Selecting a legacy format for a new implementation without a specific business or technical requirement.
Expecting GIS-focused formats to provide the same compilation workflow advantages as RDF.
---
Product Scope
-------------
HERE Static Map Data Deliveries
RDF (Relational Data Format)
Navstreets
FGDB (ESRI File Geodatabase)
GDF 3.0
---
Availability Notes
------------------
MapInfo TAB and GDF formats are available only for customers with existing legacy licensing arrangements.
* New implementations should evaluate RDF or FGDB unless a specific legacy dependency exists.
---
Keywords / Tags
---------------
RDF, Relational Data Format, Navstreets, ESRI Shapefile, SHP, MapInfo TAB, FGDB, File Geodatabase, GDF 3.0, static map data, map extraction format, exchange format, GIS data, compiler workflow, HERE map data, legacy format
Updated 3 days ago