2.1

2.1 Version

Infotripla Premium Feed in Finland

Submitted by jjlaakso on Friday, 17 October, 2014 - 10:12
Organization name
Infotripla Ltd
Organization description

Infotripla is a Finnish company providing information technology services for transport and logistics business areas. The services cover solutions for service providers, end users and professional users. One solution is to provide traffic data from easy to use interfaces - fully supporting DATEXII

Website
http://www.infotripla.fi
Country/Region
Finland
Centre type
SP
Location Referencing Format
RDS-TMC
Covered network

The whole road network and a few cities' streets in Finland. Snapshot data available: - Unplanned events - Current roadworks - Future roadworks - Poor road weather warnings - Urban unplanned events

Publication
Situation
Contact name
Juha Laakso
Extension
On
Contact mail
info5@infotripla.fi

Unused Enumeration DataClassEnum

Submitted by Joerg Freudenstein on Monday, 14 July, 2014 - 09:35
Source
Website

The Enumeration "DataClassEnum" seems not to be used within the data model (i.e. there is no attribute using it).
Maybe it's some kind of meta information, but I'm not sure about this.

It should be checked, whether this enumeration is still necessary or if there is some construct or attribute missing, which was intendet to use it.

Italian Motorways Operators DATEX II Profile and Extensions

Status definition refers to ISO 14187
Card
Profile object
Motorways Running Operations
Profile information

 The profile is been elaborate by the IT DATEX II Motorways technical group after inputs and requirements from other groups such as Italian Mare Nostrum and has aimed to finalize common operating environment to run Operational DATEX II data exchange to run Motorways Operatorse needs, based on the pluriannual DATEX1 experience.

Organization name
Italian Motorways Operators DATEX technical group
Organization description

A group set on the umbrella of previous TEMPO Program and Easyway Program to share information and best practices about Traffic Data Exchange among TMC and TIC Centres, by Motorways Operators involved in the Programs, including AISCAT and other partners such as ANAS and Technical organizations, with people directly involved in EU related committes such as DATEX TG, Easyway DG groups and TC278/WG8.

This group aim to share experiences and refine hamonized specification for comon data exchange application using DATEX.

Country/Region
Italy
Centre type
TMC
Contact name
Fabrizio Paoletti
Contact mail
fpaoletti@autostrade.it
PDF Documentation

Name and Definition Group of Locations not consistent with underlying model

Submitted by bard on Friday, 7 February, 2014 - 15:28
Source
ES5

The definition:
"One or more physically separate locations. Multiple locations may be related, as in an itinerary (or route), or may be unrelated. It is not for identifying the same physical location using different referencing systems."

The confusing thing is stating that a group can be 1. That is strange.

The clause "It is not for identifying the same location using different referencing systems" is wrong. It is the only way to do it within the group of locations.

Alert-C location referencing: documentation bug

Submitted by Anonymous (not verified) on Wednesday, 28 August, 2013 - 11:09
Source
Website

A bug is found from documentation, concerning Alert-C direction (section 7.2.8 in User Guide). Example 5 states that effect is for positive direction, when it should be to both directions.

Detailed question (and answer) is found from the following link:

http://www.datex2.eu/content/alert-c-location-referencing-question

DATEX II profile for Mobile Lane Closure Trailers

Status definition refers to ISO 14187
Card
Profile object
Situation
Profile information

Mobile Lane Closure Trailors are used to inidicate road works or road maintenance, lane closures or road closures.

This DATEX II profile can be used to transfer information from Mobile Lane Closure Trailers from central to central, for example from some service provider to some management system. Usually the data is generated inside the trailer system itself and collected by a service provider.

This profile can be especially uesful for short term events, in which the situation cannot be scheduled in advance. The information can be subject to change, for instance the position (moving road maintenance) or the signals and symbols displayed to the drivers. Therefore it is possible to transfer the data at a high frequency.

Organization name
Hessen Mobil
Organization description

Hessen Mobil plans, builds, maintains and manages the entire inter urban road network of Hessen (Germany) making for a total of 17,000 km of road network in charge.

Website
www.mobil.hessen.de/
Country/Region
Hessen, Germany
Centre type
TMC
Contact name
Jörg Freudenstein
Contact mail
joerg.freudenstein@albrechtConsult.com

Schema availability when using namespace

Submitted by Joerg Freudenstein on Wednesday, 6 March, 2013 - 17:01
Source
Website

The DATEX Namespace http://datex2.eu/schema/2/2_0 is by definition an URI, not an valid URL. Newertheless it is good pratice to guide users to the schema, if they try to resolve the namespace in a webbrowser.
In DATEX, this doesn't work and produces a 403 error (which is actually no bug, see above).

I suggest to implement some forwarding to the current DATEX schema.

DATEX Tool crashes on huge models

Submitted by Joerg Freudenstein on Tuesday, 26 February, 2013 - 11:08
Source
Website

The DATEX Tool crashes by selecting something in the tree when using a huge data model (with a lot of extensions).
It's a standard Windows message which terminates the program and which does not give any additional information about the problem.

The problem and a way to reproduce it is described in detail to Jonas Jäderberg.

NotManagedCause requirements

Submitted by Fabrizio.Paoletti on Monday, 11 February, 2013 - 17:18
Source
Datex stakeholder

we have a need for NotManagedCause to be used to specify any kind of SituationRecord that is not managed directly by a TCC ( which manage its only road competence and may refere to situation record outside competence that could be not available in the TCC system )

causeType is already referring to many situation, but not to all.. so it should be better to model allowing for NotManaged Cause any "SituationRecordClass"Type that has been provided for any different other Classes.