Docs / HERE Optimized Map for Analytics (OMA) Data Specification
Optimized Map for Analytics Data Specification

HERE Map Content and OMA Data Model Comparison

Road Representation Example

The following example shows a road as represented in the HERE Map Content catalog as well as in OMA.

Figure 1. Road
Figure 2. Node and Segment Representation
Figure 3. HERE Map Content and OMA Model

Layers data is delivered using the Protocol Buffer Publication Format (Protobuf) augmented by Versioning and Compression to further optimize the availability of this data. However in this example we are mapping the protobuf model to a relational data model in order to have an idea of the complexity of the normalized and nested structures used in the model.

1. The following are the tables involved in a query that relates the speed limit attribute with the segment using HERE Map Content model:

Table 1. speed_limit
partition_name segment_anchor_index value source unlimited
18453288 001 50 POSTED_SIGN false
18453288 002 30 POSTED_SIGN false
Table 2. segment_anchor_index
segment_anchor_index index
001 0
002 1
001 2
Table 3. segment_anchor
index first_segment_start_offset oriented_segment_ref last_segment_end_offset attribute_orientation
0 0 100 0.5 FORWARD
1 0.5 100 1 FORWARD
2 0 101 1 FORWARD
Table 4. oriented_segment
oriented_segment_ref segment_ref inverted
100 200 false
101 201 false
Table 5. segment_ref
segment_ref partition_name identifier
200 18453288 here:cm:segment:359030763
201 18453288 here:cm:segment:359041359

2. The following are the tables involved in a query that relates the speed limit attribute with the segment using OMA model:

Table 6. speed_limit
segment_identifier segment_start_offset segment_end_offset segment_inverted attribute_orientation value source unlimited partition_name
here:cm:segment:359030763 0 0.5 false FORWARD 50 POSTED_SIGN false 18453288
here:cm:segment:359030763 0.5 1 false FORWARD 30 POSTED_SIGN false

18453288

here:cm:segment:359041359 0 1 false FORWARD 50 POSTED_SIGN false

18453288