Extraction formats overview - static map data
Extraction formats overview - static map data
Map extraction formats or exchange formats are used to publish the raw data externally to customers so they can process it into their own production environment (compile).
RDF (Relational Data Format) -> proprietary format! -> recommended!
Contemporary data model,
Sets of tables joined by common attributes,
A relational representation of the HERE database,
All premium products integrated or compatible.
Data can be uploaded into most standard database environments, Oracle & Microsoft SQL Server are fully supported by HERE.
Continental clips, seamless.
RDF is best suited for “compiler customers” and aligns with “mainstream” information technology better than our other formats, it can offer added flexibility & efficiency within many customers settings.
Pro/Cons
Complimentary Tools: RDF Viewer – install, validate, view, clip, analyze via simple queries
All inclusive in a single installed RDF
Customers select the desired products using a meta tagging feature which is only available in RDF
Compatible with many Database Systems and fully supported. Customers can leverage abundant and cost effective developers
RDF can face greater challenges as it contains most of our available content in one delivery.
NavStreets (ESRI .shp and Mapinfo .tab)
Layered’, GIS-focused representations of HERE data delivered by region. Currently there are two formats within NAVSTREETs:
1. ESRI Shapefile: A GIS format proprietary to ESRI, although it is the most widely used format in the spatial industry.
2. MapInfo TAB: A GIS format proprietary to MapInfo (now owned by Pitney Bowes), although it has broad usage in the spatial industry.
Content delivery by region
Pro/Cons
Shapefile has very strong customer and third-party adoption
Can be used with commercial off-the shelf software
Ships with a defined project (APR à MXD, WOR) that displays the map data and allows users to browse the content easily
Esri has stopped supporting .shp.
Can have content discrepancies with other formats (being addressed per market needs)
NAVSTREETs is best suited for Enterprise customers, although it has found use in all of our markets – and is commonly used as a compliment to the compilation process.
If a visual interaction or GIS functionality is useful – NAVSTREETs can be a valuable addition.
FGDB (ESRI File GeoDataBase)
Preferred GIS application format.
Cutting edge ESRI ArcGIS representation of HERE database, optimized for ESRI toolsets.
Continental clips, seamless.
Fast adoption by Enterprise Market.
Pro/Cons
Fast…data can be directly consumed in ArcGIS tools.
Simple plug-and-play Routing, Geo-coding and Mapping with ESRI tools.
Relational. Use of simple SQL queries to extract data.
Large size files due to continental clips.
Optimal with Arc 9x, however, problematic with past versions.
FGDB is best suited for Enterprise customers, although it has found use in all of our markets – and is commonly used as a compliment to the compilation process.
If a visual interaction or GIS functionality is useful – FGDB can be a valuable addition.
GDF 3.0 (Geographic Data File)
A European standard developed in 1990’s that emerged to be the de-facto international standard for exchanging navigable databases.
Flat file structure, with record types related by pointers. Data is sequentially ordered.
Pro/Cons
More or less the leading standard in the Navigation Industry *
* be aware that there are “GDF flavors” between HERE & competition, making it less than a true standard
Flat file structure can be cumbersome for some customers and certain content types cannot be directly integrated
No out-of-the-box tools to read and work with format – customer must develop these (there is a Here GDF viewer available)
GDF is best suited for “compiler” customers If a standard format is a priority, or a company has significant technical or human investment around legacy GDF platforms.
GDF is be treated as legacy format by HERE, what is in a kind of “phase out”.
NOTE: Mapinfo and GDF are only available for legacy customers who licensed such format in the past.