Tomtom Meta Txt
Introduction to TomTom Traffic Flow – Intermediate Service – Protobuf
96 AE 3F 78 E3 77 3F B8 4F 09 AE 1D C2 BF A2 12 Benelux-6.meta; FlitspaalNLTomTom614 07 26 5E F7 1D A7 A5 AB 99 72 AE AB C7 20 B2 05 FlitspaalNLTomTom.ov2; RadarBETomTom607 4B DB D9 E3 B6 76 84 D9 A3 D3 E7 47 41 62 E9 DF RadarBETomTom.ov2; EasternEurope7051480 22 BD 73 5E A6 85 59 83 97 C2 C8 1B 7B 81 5C B5 EasternEurope-5.meta. 05 2C A3 DA 8D 1F 87 68 BC 13 9E 2F 92 F8 DB ED CentralandEasternEurope-101603.meta; CentralandEasternEurope 10118977 42 30 5A 60 6A 7C 46 80 07 A5 1C 6B 91 45 DA 15 CentralEurope-101527.meta; CentralEurope 10108891.
Executive summary
The TomTom Traffic Flow – Intermediate Service – Protobuf (hereafter called ‘Service’) is designed for server to server integration with traffic control center, routing, navigation, and mapping applications. It contains real-time travel times and speeds for segments, based on TomTom’s Traffic technology, with several possible granularities.
This document describes the data exchange method and the payload description of the Service interface. Be aware that the Service is available in two variations:
- TomTom Traffic Flow (Standard feed) and
- TomTom Traffic Flow Detailed (higher road coverage).
See more details on differences between Flow and Flow Detailed in the FAQ.
Scope
This document gives basic information on the Service and shows how to configure it to work with your environment. The user is expected to have basic installation knowledge and experience using protocol buffers.
Intended audience
This document is intended to be used by TomTom partners and customers (decision makers and developers).
What is the TomTom Traffic Flow – Intermediate Service – Protobuf
Standard configurations
TomTom offers traffic flow data to customers. The most basic data type is speed information and travel times, by segment. TomTom configures a custom product based upon your specific needs. The product is static, so included regions and features are fixed (once the product is configured).
Optional configurations
The Service gives users traffic flow data with highly customizable configuration options, in addition to the standard configuration.
| Option | Description |
|---|---|
| Dynamic sectioning | It describes the road links in smaller sections when conditions vary considerably within a longer road stretch. |
| Flow prediction | When enabled, the current and future speed information to a location at several points in time is provided. More information on the prediction horizon can be found in the flow feature matrix in the FAQ. |
| Closure flag | A flag to indicate whether a road segment is closed. When enabled, a special roadClosure field appears. If a road segment is closed, the average speed is the free-flow speed. If this option is not enabled, the average speed shown will be zero for segments affected by a road closure. |
| Relative speed | When enabled, the relative speed is provided. This is defined as the ratio of average speed to free-flowing speed (for example, 0.250 indicates a current real-time speed that is 25% of free-flow speed). |
| Traffic condition | When enabled, the current traffic condition is given. This is expressed with one out of eight available values. |
| Time to usual | When enabled, it gives the time in minutes for speed to return to usual speed (from the speed profile). This feature is an add-on to the Flow prediction feature and only works in combination with that option. |
| Miles per hour | The average speed is additionally provided in mph (all speeds are provided by default in km/h). |
| HOV lanes | Adds separate speed entries for lanes reserved for high-occupancy vehicles. Only the current speed for the whole location is available. |
| Map version | Provides name and version of the map that was used to create the content. |
RESTful API
The Service uses RESTful API (Representation State Transfer) technology. Since you only need to use one URL, the service is relatively uncomplicated to use.
How do you make a request?
To make a request, the URL is constructed as shown in the following sections. Note: requests may not function if made from a non-authenticated computer. More details are available in the section, “A secure connection” at https://developer.tomtom.com/intermediate-traffic-service.
Format
The sample URL is formatted in one of two possible ways:
(1) TomTom Traffic Flow
The following is an example URL:
(2) TomTom Traffic Flow Detailed
The following is an example URL:
Parameters
The following table provides a detailed explanation of the available fields that were previously shown in the Format section.
| Parameter | Description | Req'd? | Type / Values |
|---|---|---|---|
| baseURL | Base URL for calling the API. | Yes | traffic.tomtom.com |
| productName | Name of the product (feed) you are requesting. These will be indicated to you as part of the provisioning process. Typically, it explains the country (country code), type of feed (HDF is the flow feed) and the location referencing method (TMC or OpenLR). | Yes | e.g. |
key | Authorization key for access to the API. | Yes | String |
| [flowType] | When the feed is requested without parameter 'flowType' it contains ALL messages covered by the feed. In that case, the field averageSpeed in a message represents the current speed for congested road segments and the free-flow speed for non-congested road segments. By using the 'flowType' parameter, the response can be shaped to only support a certain speed type. This also affects the number of messages in the response. There are two values supported for this parameter:
When using this parameter, at the first request the free-flow information should be downloaded. Afterwards, non-free-flow information can be downloaded for each future request. The free-flow and non-free-flow data is related. The segments for both files should be in sync, otherwise there is a mismatch in the locations of the free-flow data. Therefore, every time the non-free-flow information is downloaded, it must be checked. This insures that the non-free-flow data corresponds to the free-flow data (that the user already has). The verification is done by confirming the clientID within supplierAndClientInfo in protocol buffers format. If the clientID of the non-free-flow content does not match the clientID of the free-flow content that was downloaded with the first request, the free-flow information must be re-requested. | No | flowType=nff flowType=ff |
Recommended HTTP headers
Since flow feeds can be very large, TomTom recommends optimizing the information transmission as much as possible. Through optimization, the client receives more up-to-date information.
If-Modified-Since
TomTom recommends using the standard HTTP headerIf-Modified-Sincewith the last value ofLast-Modifiedreceived. When this header is used properly, you avoid unnecessarily downloading identical content. For details, see the HTTP/1.1 standard (RFC2616 section 14.25).Accept-Encoding: Gzip
The TomTom Traffic Flow bulk feed supports gzip compression of all response types. However, responses are compressed only when requester states gzip support. This should be specified through the standard HTTP headerAccept-Encoding: gzip. TomTom recommends using this header type as it significantly reduces the payload size.
Response you receive after a request is made
Response example
If you make the following request:
You can expect a response that contains protocol buffers binary data. The textual representation of this data could look like this:
Response - Protobuf payload specification (analysis of the received output)
Protocol buffers is the de-facto standard for encoding and transmitting any structured information in a compact, platform independent way. TomTom uses protocol buffers (version 2) format for the output payload. After defining the data structure an encoder and a decoder can be generated for integration into C++, Java and several other languages. See also: http://code.google.com/p/protobuf or https://developers.google.com/protocol-buffers for more information.
Our output type uses the proprietary TomTom protocol buffers message types. The data structure of the protocol buffers output is defined by a .proto definition file. TomTom supports schema version 8 and above.
All fields are marked as optional, as recommended by Google, but the output always contains flow information (including a location).
Additionally, the only messages that are present are TrafficFlow, TrafficFlowWithPrediction, or TrafficFlowWithPredictionPerSection. The actual message type depends on the specific product definition (see product configuration options):
TrafficFlow:
This message type is used with products that are NOT configured for prediction. Optionally, TomTom supports breaking up locations into sections.TrafficFlowWithPrediction:
This message type is used with products configured for prediction and NOT for breaking up locations into sections.TrafficFlowWithPredictionPerSection:
This message type is used with products configured for prediction AND breaks up locations into sections.
In any other case, only TrafficFlow is included in the response.
The following table gives detailed information about the different messages used in the data structure.
Protocol buffers message type| Description | |
|---|---|
| TrafficFlowGroup | The traffic flow group is the top-level message. It provides meta data and the flow entries themselves. |
| MetaInformation | The meta information message provides data shared by all traffic flow messages. It contains the creation time, supplier and client information and the format version. |
| SupplierAndClientInfo | The supplier and client information message identifies the client and the supplier. |
| TrafficFlow | The traffic flow message assigns speed information to a location. It may also identify road blockages. |
| TrafficFlowWithPrediction | The traffic flow message assigns current and future speed information to a location at several points in time. It may also identify road blockages. |
| TrafficFlowWithPredictionPerSection | This message assigns current and future speed information to sections of a location at several points in time. |
| Speed | The speed message subsumes all speed and travel time related information. This message consists of:
|
| SectionSpeed | The SectionSpeed message provides speed information for the section of a location. The section is indicated by the offset of the starting point from the start point of the location. The ending offset is either the end of the location or the start of the next section, if there is a next section. SectionSpeed may also identify road blockages. |
| SpeedWithTimeStamp | SpeedWithTimeStamp gives speed information details at a point in a future time. This time value indicates the number of minutes relative to the creation time of this message, as established by the MetaInformation message. |
| SpeedVector | SpeedVector provides a set of section speed information details at a point in a future time. This time value indicates the number of minutes, relative to the creation time of this message, as established by the MetaInformation message. |
Geographical representation
Geographical representation of the road segments is an important part of the payload. There are two geographical representations that are supported: TMC and OpenLR. Since OpenLR prevents interpretation differences, licensing costs, map dependencies, or version dependencies, TomTom recommends using OpenLR instead of TMC. TMC based data is still offered for customers with existing platforms that need compatibility with their legacy systems.
Www kenbrockmfg com. OpenLR example (here printed using C escape sequences):
TMC example:
OpenLR
OpenLR (see http://www.openlr.org) is a dynamic location referencing method that allows referencing of any road on the complete digital map. Because of its flexibility, it is possible to describe traffic events on high level and lower level road classes that are usually not covered by TMC. The method is available free of charge. The Service uses binary format version 3, as described in the OpenLR whitepaper. The whitepaper, software developer kit, and open source reference implementation are available for download from the OpenLR website. TomTom offers support for third parties to implement and test their own implementations.
Traffic Message Channel (TMC)
When using TMC as a geographical representation, travel times are measured by a TMC link. A TMC link is part of a TMC path. A TMC link is a sequence of road elements that starts at a TMC location and ends at a next TMC location in the TMC path in the specified direction. You can recognize a TMC link by:
- TMC table (country code, location table number).
- Primary TMC location, defining the TMC point location at the end of the TMC link.
- Direction, as defined by the TMC path.
- The inclusion of internal / external road segments (see following examples).
- An optional extent (the default value is 1).
Generally, the set of TMC link identifiers that can be used in a TrafficFlowGroup is static. That means that in subsequent snapshots, the same locations are used. However, this is not always the situation. Sometimes, the set of the TMC link identifiers that are used can be changed. These changes occur when a new TMC table is introduced.
TMC link identifier
TMC Chain Information is composed of the following parts CVVDLLLLL[xE[E]]:
Part| Description | |
|---|---|
C | Hexadecimal country code as described in IEC 62106. |
VV | TMC Location Table code |
D | TMC direction of the chain (defined by the TMC path). For possible values: see TMC direction. |
LLLLL | TMC point location code. If the number is not five digits long, zeros are added at the beginning until there are five digits. |
[xE[E]] | Either empty, when extent = 1, or fixed letter 'x' followed by the extent (one or two digits). |
Using the specified TMC table, the secondary location (start of the stretch) can be found from the primary location, the direction, and the extent. C, VV and LLLLL correspond with the TMC Location Reference that is a unique identifier for a TMC location.
TMC direction
The possible values for D refers to the direction of travel (secondary to primary location) along the TMC path:
Value| Direction | Validity | |
|---|---|---|
p (lower case) | Positive | Internal + External |
n (lower case) | Negative | Internal + External |
+ | Positive | External |
- | Negative | External |
P (upper case) | Positive | Internal |
N (upper case) | Negative | Internal |
If the extent > 1 then the value for <direction> must be 'p' or 'n', including all internal and external road segments. See the section, Internal and external road segments for more details.
Internal and external road segments
To know exactly where a TMC link starts and ends, you should understand the concept of internal and external road segments. For each TMC point location and each direction, a composition is made of road segments that are part of the TMC location. An example of this is a highway junction or the roads between the exit and the entry. These are the internal road segments. Furthermore, a path of road segments is constructed, connecting the TMC locations. The road segments between two TMC locations are the external road segments, which are assigned to the TMC location where the path is leading.
If two consecutive TMC locations have an overlap or a reverse order in the TomTom map, they can be combined into one TMC link with an extent > 1. Typically, a TMC link includes both the internal and external road segments of a TMC location, so a TMC link usually starts at the end of the secondary location and ends at the end of the primary location. Sometimes, the travel time is provided just for the internal road segments or the external road segments, though this is unusual. This is indicated in the TMC link identifier.
Examples
Example 1: 817n39984x2
Given TMC location data
- Country code: 8
- Location table number: 17
- Direction from secondary to primary location: negative
- Primary location ID: 39984
- Extent: 2
How to interpret TMC location data to resolve secondary location
- Invert direction: negative -> positive.
- Since the resolved direction is positive, follow the positive offset path for 39984 in the TMC table for two extents.
- You will find the subsequent positive offsets are 39985 and 39986, therefore, the resolved secondary location is 39986.
Example 2: D01+27442
Given TMC location data
- Country code: D
- Location table number: 1
- Direction from secondary to primary location: positive (external only)
- Primary location ID: 27442
- Extent: 1 (if extent is not provided explicitly, then it is 1)
How to interpret TMC location data to resolve secondary location
Invert direction: positive -> negative.
Since the resolved direction is negative, follow the negative offset path for 27442 in TMC table for one extent.
You will find the subsequent negative offset is 30080.
Now follow the path for 27442 in that direction and only select segments that are marked as the external part of 27442.
Example 3: TMC location reference with section offsets
Given TMC location data
104p04168 and section offsets: 0m, 1500m
- Country code: 1
- Location table number: 4
- Direction from secondary to primary location: positive
- Primary location ID: 4168
- Extent: 1 (if extent not provided explicitly then it is 1)
How to interpret TMC location data to resolve secondary location
Invert direction: positive -> negative.
Since the resolved direction is negative, follow the negative offset path for 4168 in TMC table (see the following TMC location table excerpt).
The negative offset of 4168 is 4167, therefore, the resolved secondary location is 4167.
How to apply section offset information on resolved link
Given the resolved secondary location, apply section offset onto location path measured from secondary location.
In the following example, all section offsets are referring to 4167. That is, the first offset is 4167 itself and the second offset is 1500m away from 4167 along the location path to 4168.
Product configuration options
When the product is configured, there are some additional options that could be enabled or disabled depending on your specific preferences.
Option| Description | Example | |
|---|---|---|
| Dynamic sectioning | Allows sectioning: describing the road links in smaller sections when conditions vary considerably within a longer road stretch. |
|
| Flow prediction | Flow prediction is supported in two flavors, each variant uses a specific flow message type:
| Examples for each possible flow message type when prediction is enabled:
|
| Closure flag | A flag to indicate whether an affected location is closed. When enabled, a special field roadClosure will appear in case an affected location is closed, in that case the average speed should be ignored (the reported average speed is the current speed). In case this option is not enabled, the average speed shown is 0 for segments affected by a road closure. | Examples for each flow message type when the closure feature is enabled:
|
| Traffic condition | Provides a textual traffic condition indicator. When enabled, a categorization of current traffic condition is given. It can be any value out of seven values (the colors are added to better illustrate of the severity of each traffic condition; the colors are not contained in the feed):
| A TrafficFlow message with stationary traffic: trafficFlow-trafficCondition.pb.txt |
| Relative speed | When enabled, the relative speed to the free-flowing speed is given as a ratio (e.g. 0.250 indicates a current real-time speed that is 25% of free flow speed). | A TrafficFlow message with relativeSpeed: trafficFlow-relativeSpeed.pb.txt |
| Time to usual | Provides the time duration (in minutes) for the average speed (of the entire location) of a flow message to return to the usual speed (speed profile). This feature is only available for flow message types TrafficFlowWithPrediction and TrafficFlowWithPredictionPerSection. |
|
| HOV lanes | Adds separate speed entries for lanes reserved for high-occupancy vehicles, for now only the current speed for the whole location is available. | A TrafficFlow message with two speed entries, one for the regular lanes and one for the HOV lane(s): trafficFlow-HOV.pb.txt |
| Map version | Provides name and version of the map that was used to create the content. The map version is reported as part of the meta information of a traffic flow snapshot. | A snaphot with a single TrafficFlow message and a MetaInformation message with field mapVersion: trafficFlow-mapVersion.pb.txt |
Again, I have created a new tool in Excel.
My goal with this tool is to introduce a uniform meta-code file (Meta.txt)
The tool is a database and contains all the meta-codes for:
- countries (>6820) map version 700 till 1060
- cities (3116) version 715_1732
- Voices and Safety Cams (124)
- So called Equivalent-lines (1550) for map versions 990 till 1060
It is possible to add new lines to the database.
You can do so by putting the lines you want to add in the file Meta_input.txt and than start the input run.
You can choose for only checking (default) or checking and adding.
You can create a new Meta_Export.txt file from the database. You can also choose what you want to put in the new Meta_Export.txt file. Alone country meta-codes, or alone country and city meta-codes, or the whole database (countries, cities, Voices & Cams and Equivalent-lines).
The last one is the default.
First choose your wanted output and then start a output run.
The meta.txt files you find by tools like TTActivator, Activator_2019, etc. mostly contain everything.
It is also possible to do some maintenance on the database.
Most important is that you can choose your own name for the input-, output- and controle-file.For instance most people would like meta.txt as output-file.
If you have any questions, please ask them.
I hope you will have fun with it.
Como Activar Mapas Tomtom Meta.txt
The tool is made in MS-Excel 2019 and should work with MS Excel 2007 or higher.The rar file must be unpacked with a RAR version 5.x
Unpack the rar in a map and start the Excel
Update November 21 2020 16:00 PM:
Updated the meta-codes for map version 1060 and Equivalent lines for map version 1060.
Special thanks to master131 for the meta's
Regards
Peter
Tomtom Meta.txt 1015
Tomtom Meta.txt 1030
- meta-txt_Collector.rar (1.20 MB, 11 views)