For a short introduction about datasources, see → General information on datasources.
List of datasources
In the table, the list of datasources:
| Datasource |
Default value |
Description |
|---|---|---|
|
DS_MAIN |
-2 |
Main datasource, used to simplify the import operation specifying if the source of data is the same for all datasources or for most of them. Type: String Allowed values:
|
|
DS_MODE |
-1 |
Datasource grouping all the entities related to properly express the user behavior; for example, to describe route choices and intermodality. At data model level it groups:
Type: String Allowed values:
|
|
DS_STRATEGY |
-2 |
Datasource used to import intermodal strategies used by Hyperpath. Type: String Allowed values:
|
|
DS_NETW |
-1 |
Datasource used to import the supply network with all its properties, used by model based simulation engines. Type: String Allowed values:
|
|
DS_PARK |
-2 |
Datasource used to import all the characteristics of the parking sites like capacity or fee. Type: String Allowed values:
|
|
DS_CLOC |
-1 |
Datasource used to import count locations, and all the characteristics of the count detector sites like monitored street. Type: String Allowed values:
|
|
DS_DEMD |
-1 |
Datasource of the demand, that is all the data related to the Offer-Demand flows. Type: String Allowed values:
|
|
DS_DVAL |
-1 |
Datasource used to import day validities, like valid days or day types. Type: String Allowed values:
|
|
DS_SCEN |
-1 |
Datasource used to import scenarios, that is all the settings related to the scenarios like simulations data and KPIs. Type: String Allowed values:
|
|
DS_FUNC |
-1 |
Datasource used to import functions, that is all the values of the functions like function type, parameter values and parsable expressions. Type: String Allowed values:
|
|
DS_EXTE |
-2 |
Datasource used to import externalities, that is all the definitions related to the externalities functions like vehicle fleet and pollution per vehicle type. Type: String Allowed values:
|
|
DS_TRAN |
-2 |
Datasource is used to import transit, that is all the characteristics of the public transport service like routes and stops. Type: String Allowed values:
|
|
DS_RTTRAN |
-2 |
Datasource used to import real time transit data Type: String Allowed values:
|
|
DS_TPRB |
-2 |
Datasource used to import turn probabilities, that is all the values of the turn probabilities from a previous generic assignment. For example, like turn probabilities per link per DTA interval from dynamic assignment. Type: String Allowed values:
|
|
DS_TPRB_OUT |
-2 |
Datasource used to export turn probabilities. You can define multiple outputs by using a comma as a separator between the different datasources. Type: String Allowed values:
|
|
DS_JUNC |
-1 |
Datasource used to import junctions, that is all the characteristics related to the junctions like pocket lanes, lane turns and conflict areas. Type: String Allowed values:
|
|
DS_SIGN |
-1 |
Datasource used to import traffic signals, that is all the settings related to the network traffic signals like stages, signal groups and timings. Type: String Allowed values:
|
|
DS_STRT |
-1 |
Datasource used to import street graph, that is all the characteristics of the street network like topology and addresses. Type: String Allowed values:
|
|
DS_PLOC |
-2 |
Datasource used to import predefined locations, that is TMC data. Type: String Allowed values:
|
|
DS_EVNT |
-1 |
Datasource used to import events, that is all the data about the events occurring on the network and are updated in real-time like event location and effects. Type: String Allowed values:
|
|
DS_EVENT_SERVICE |
-2 |
Datasource used to import signal events. Type: String Allowed values:
|
|
DS_TATT |
-1 |
Datasource used to import temporary attributes. These attributes are related to the link attributes with the planned temporary changes of the attributes' value like change of capacity and LTZ. Type: String Allowed values:
|
|
DS_STAT |
-2 |
Datasource used to import street's temporary attributes. These attributes are related to the street's attributes with the planned temporary changes of the attributes' value, like change of capacity and speed limit. Type: String Allowed values:
|
|
DS_BPER |
-2 |
Datasource of the base performances, that is all the expected values of the network objects' performance like travel times. Type: String
|
| DS_CPER |
-2 |
Datasource of the current performances, that is all the values of the network objects' performance, updated in real-time like travel times. Type: String Allowed values:
|
|
DS_TSTA |
-1 |
Datasource used to import traffic states, that is any real-time measures like flow measures, speed measures. Type: String Allowed values:
|
|
DS_HTST |
-2 |
Datasource used to import historical traffic states, that are expected measure values like historical flow counts and average revealed speed. Type: String Allowed values:
|
|
DS_LKST |
-2 |
Datasource used to import link-street relations, that is the connection between the street network and the assignment model network. Type: String Allowed values:
|
|
DS_POIS |
-2 |
Datasource used to import points of interests, that is all the information about relevant locations like touristic sites. Type: String Allowed values:
|
|
DS_UDAS |
-2 |
Datasource used to import User Defined Attributes (UDAs) Type: String Allowed values:
|
|
DS_SHAPES |
-2 |
Datasource used to import polygon shapes. Type: String Allowed values:
|
|
DS_PATH |
-2 |
Datasource used to import predefined paths. Type: String Allowed values:
|
|
DS_ConfigurationOptions
|
-2 |
Additional configuration options datasource. Type: String Allowed values:
|
|
DS_OPUT |
-1 |
Sets the address of outputs if software returns any, in case of having several outputs comma should be used as seperator. Type: String Allowed values:
|
|
DS_TSTA_FORECAST |
-2 |
Involved in MLF-STF communication (see → MLF-STF communication). |
Supported .NET applications for each datasource
In the table, you can distinguish four distinct markers:
-
Option used: YES
-
Input datasource: >
-
Output datasource: →
| Datasource |
Marker |
TDE |
TRE |
TRE Addin |
TRE Planning |
MTF |
HP |
VT |
VMS |
DDM |
TRE Viewer |
Transit Assignment |
Online Transit Assignment |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DS_MAIN |
> |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
DS_MODE |
> |
YES |
YES |
YES |
YES |
YES |
YES | YES | YES | YES | YES |
YES |
YES |
|
DS_STRATEGY |
> |
YES |
|
|
|
|
YES |
|
|
|
|
YES |
|
|
DS_NETW |
> |
YES |
YES |
YES |
YES |
YES |
|
|
YES |
YES |
YES |
YES | |
|
DS_PARK |
> |
YES |
YES |
|
|
|
|
||||||
|
DS_CLOC |
> |
YES |
YES |
|
YES |
YES |
|
|
|
|
|
||
|
DS_DEMD |
> |
YES |
YES |
YES |
YES |
YES |
|
|
YES |
|
|
YES | YES |
|
DS_DEMS |
> |
YES |
YES |
YES |
YES |
YES |
|
|
YES |
|
|
YES | YES |
|
DS_DVAL |
> |
YES |
YES |
YES |
YES |
YES |
YES |
|
YES |
YES |
|
YES | YES |
|
DS_SCEN |
> |
YES |
YES |
|
YES |
YES |
YES |
|
|
|
YES |
||
|
DS_FUNC |
> |
YES |
YES |
YES |
YES |
YES |
YES |
|
|
|
YES |
||
|
DS_EXTE |
> |
YES |
YES |
|
YES |
YES |
YES |
|
|
|
YES |
||
|
DS_TRAN |
> |
YES |
|
|
|
|
YES |
|
|
|
YES |
YES | YES |
|
DS_RTTRAN |
> |
YES |
|
|
|
|
YES |
|
|
|
|
YES | |
|
DS_TPRB |
> |
YES |
YES |
YES |
YES |
YES |
|
|
|
|
YES |
YES | |
|
DS_TPRB_OUT |
→ |
YES |
YES |
|
YES |
YES |
|
|
|
|
|
YES |
YES |
|
DS_JUNC |
> |
YES |
YES |
YES |
YES |
YES |
|
|
|
|
YES |
||
|
DS_SIGN |
> |
YES |
YES |
YES |
YES |
YES |
|
|
|
|
YES |
||
|
DS_STRT |
> |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
DS_PLOC |
> |
YES |
|
|
|
|
|
|
|
|
|
||
|
DS_EVNT |
> |
YES |
YES |
|
YES |
YES |
YES |
|
YES |
|
|
YES | |
|
DS_EVENT_SERVICE |
> |
YES |
YES |
|
YES |
YES |
|
|
|
|
|
||
|
DS_TATT |
> |
YES |
YES |
YES |
YES |
YES |
|
|
|
|
YES |
||
|
DS_STAT |
> |
YES |
|
|
|
YES |
|
|
|
|
|
||
|
DS_BPER |
> |
YES |
|
|
|
YES |
|
|
|
|
|
||
| DS_CPER |
> |
YES |
|
|
|
YES |
|
|
|
|
|
||
|
DS_TSTA |
> |
YES |
YES |
|
YES |
YES |
YES |
|
|
|
YES |
YES | |
|
DS_HTST |
> |
YES |
YES |
|
YES |
YES |
YES |
|
|
|
YES |
||
|
DS_LKST |
> |
YES |
YES |
|
YES |
YES |
|
|
YES |
YES |
YES |
||
|
DS_POIS |
> |
YES |
|
|
|
|
YES |
|
|
|
|
||
|
DS_UDAS |
> |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES | YES |
|
DS_SHAPES |
> |
YES |
|
|
|
|
YES |
|
|
|
|
||
|
DS_PATH |
> |
YES |
YES |
YES |
YES |
YES |
YES |
|
|
|
YES |
||
|
DS_OPUT |
→ |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES | YES |
Supported file formats for each datasource
Supported data storage formats for input and output are:
| Prefix storage type | Format | Description |
|---|---|---|
|
txt |
Text file |
Simple text file formatted as a CSV file |
|
bin |
Binary file |
TDE binary file |
|
visum |
Visum text files |
Set of Visum data text files (.net, .dmd, .xml) |
|
visumcom |
Visum binary file |
Visum data binary file (.ver) (Visum 13 or later; input only) |
|
postgresql |
PostgreSQL database |
PostgreSQL with PostGIS extension |
|
shape |
Shapefile |
Standard shapefile with data (.shp, .dbf) |
|
webservice |
|
|
|
commandline |
|
|
|
sqlite |
|
|
Important: sqlite is NOT production ready, and txt and shape are at anexperimental level on few datasources.
| Datasource |
postgresql |
visum |
visumcom |
bin |
webservice |
txt |
commandline |
shape |
sqlite |
|---|---|---|---|---|---|---|---|---|---|
|
DS_MAIN |
YES |
YES |
YES |
|
|
|
|
|
|
|
DS_MODE |
YES |
YES |
YES |
YES |
|
YES |
|||
|
DS_STRATEGY |
YES |
YES |
YES |
|
|
YES |
|
|
|
|
DS_NETW |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
DS_PARK |
YES |
YES |
YES |
YES |
YES |
|
YES |
|
|
|
DS_CLOC |
YES |
YES |
YES |
|
|
|
|
|
|
|
DS_DEMD |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
DS_DVAL |
YES |
YES |
YES |
YES |
|
YES |
|
|
|
|
DS_SCEN |
YES |
YES |
|
YES |
|
|
|
|
|
|
DS_FUNC |
YES |
YES |
YES |
YES |
|
YES |
|
|
|
|
DS_EXTE@ |
YES |
|
|
YES |
|
YES |
|
|
|
|
DS_TRAN |
YES |
YES |
|
YES |
|
YES |
|
|
|
|
DS_RTTRAN |
YES |
|
|
|
YES |
|
|
|
|
|
DS_TPRB |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
DS_TPRB_OUT |
YES |
|
|
YES |
|
|
|
|
|
|
DS_JUNC@ |
YES |
YES |
|
YES |
|
|
|
|
|
|
DS_SIGN |
YES |
YES |
|
YES |
|
|
|
|
|
|
DS_STRT |
YES |
YES |
YES |
YES |
|
YES |
|
|
|
|
DS_PLOC |
YES |
YES |
YES |
|
|
|
|
|
|
|
DS_EVNT |
YES |
|
|
YES |
|
|
|
|
|
|
DS_EVENT_SERVICE |
YES |
|
|
|
YES |
|
|
|
|
|
DS_TATT |
YES |
YES |
|
YES |
|
|
|
|
|
|
DS_STAT |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
DS_BPER |
|
|
|
|
|
|
|
|
|
| DS_CPER |
|
|
|
|
|
|
|
|
|
|
DS_TSTA |
YES |
|
|
|
|
YES |
|
|
|
|
DS_HTST |
YES |
|
|
|
|
YES |
|
|
|
|
DS_LKST |
YES |
YES |
YES |
||||||
|
DS_POIS |
YES |
YES |
YES |
|
|
|
|
|
|
|
DS_UDAS |
YES |
YES |
YES |
|
|
YES |
|
|
|
|
DS_SHAPES |
YES |
YES |
|
|
|
|
|
|
|
|
DS_PATH |
YES |
YES |
|
|
|
||||
|
DS_ConfigurationOptions |
|||||||||
|
DS_OPUT |
Interactions between datasources
In some specific contexts, the value assignable to a datasource can be influenced to the values set for another datasource.
The combination of values of different datasources can modify the behavior of the application.
Here you find a table summarizing:
-
The description of the context.
-
The link associated to a topic hosting the necessary information.
| Context | Description |
|---|---|
|
Scenarios |
You can evaluate different scenarios to improve the network performance. The datasources involved are:
|
|
Optima planning |
In Optima Planning it's necessary to set five datasources:
|