11/12th October 2001

Barcelona MKmetric

Eduard Ruffert & Dr. Benedikt Mandel

email: ruffert@mkm.de & mandel@mkm.de

MKmetric Gesellschaft für Systemplanung mbH, Karlsruhe

1. Requirements

2. Development

3. Way forward

11/12th October 2001

Barcelona MKmetric

GTF / TIP data

Workspace / User System

GTF@WS GTF@Prov.

Filter FilterApplication A

App.B

User data

Model

in–housedata

in–houseincrementaldata

GTF / TIP data

Provider

Operating System X Operating System Y

Internet

Interchange structure

11/12th October 2001

Barcelona MKmetric

Supporting Model Communication1. Model requirements:

GTF = Generalised Transportation data Format- EDI format to exchange transportation modelling

information- not to impose formats or contents constraints on

modellers exchanging data- not specifically for GIS

GTF specifies building blocks (entities) GTF is a general structure of the information transport models use

Principles:- not too many basic building blocks (generic entities)- generalised enough for (mainly) modelling information

and (also) other information

• GTF = Exchange of Data (homogeneous & generic)

Overview of requirements

11/12th October 2001

Barcelona MKmetric

Supporting Model Communication

2. EDI requirements:

- cross-platform- structured & segmented- flexible & scalable- use of existing standards- human readability

CONTENTS of GTF : GTF Conceptual Model (GTF-CM) FORMAT & PROTOCOL : GTF-XML

Overview of requirements

11/12th October 2001

Barcelona MKmetric

GTF = “Generalised Transportation-data

Format” - the conceptual model

GTF-XML = the underlying

transmission format

Universe of GTF

11/12th October 2001

Barcelona MKmetric

Development: GTF definition

GTF = for the exchange of strategic transportation modelling information GTF-CM is means of discussion

= capture the vocabulary of the problem domain in computer terms

Problemdomain

Computerterms

The travel timeon Link L

from Node A to Node B

is X.

Node A Node B

Link L

travel_time = X

mapping

LinkAttr ibutes

Alternative

Zone

Unit

Terminator

Vessel

Link

TransportProduction

Node

Meta

Junction

1 *

1 *

0..1

*

1

*

0..1

*

0..1

*

in_def inition_of

uses_in_def inition

0..1

*

0..1

*

can_travel_withcan_carry

0..1

*

Note: Meta, Attribute(and some other, e.g.

Group) classes/objects canbe used (associated) to anyother class instance (object)

and not only toTransportProduction objects.

But this diagramsymbolically shows this

association between Metaand TransportProduction.

Chain

Zone

barrier

0..1

*

Mode

uses_in_def inition

in_def inition_of 0..1

*

is_of_mode

specif ies_mode

0..1

*

allowed_on

allows

0..1

*

DynamicSegmentation

Grouping

Pa th

groups

part_of

0..1

*

Milepost

0..1*

0..1

*

starts_in start_of1 *

ends_in end_of1 *

is_active_in

has_activities_list

1

*

regulates

has_regulations_list

0..1

*

travels_with

carries

0..1

*

defines

definition_units_list

0..1

*

allowed_on

allowed_alternatives_list

0..1

*

allowed_on

allowed_services_list

0..1

*

defines

definition_services_list

0..1

*

in_definition_of

uses_in_definition

0..1

*

can_travel_with

can_carry

0..1

*

used_by

uses_vessels_list

0..1

*

centroid_of

localises

0..1

*

uses_in_definition

in_definition_of

0..1

*

is_of_mode

specifies_mode

0..1

*

allowed_on

allows

0..1

*

Zone

barrier

0..1

*

groups

part_of

0..1

*

0..1

*

0..1

*

11/12th October 2001

Barcelona MKmetric

GTF-Conceptual Model (CM)

...

11/12th October 2001

Barcelona MKmetric

Principles / Framework classes for GTF-CM specification

super

sub

0..1

*0..1

*

associated_object

comments_list

1

*

identifier_of_comment

has_id

0..1

0..1

identifier_of_object

has_identifier

0..1

0..1

OGISPointer

shape_list

1

*

11/12th October 2001

Barcelona MKmetric

OO concepts overview

Development views

1. Conceptual

2. Specification

3. Implementation

Where are we now? Why?1 + 2 +3

11/12th October 2001

Barcelona MKmetric

OO concepts overview

Sequence of development steps?

First 1. Conceptual

Then 2. Specification

Then 3. Implementation

In detail ...

on the basis of MoU ...

and propsed GTF Specification.

GTF = mediator format

...

Emme/2

TOP

Polydrom

GDF

NWB

GTFfile

ReaderAPI

• • • • • • • • • • •

Func1

FuncN

...

...

Emme/2

TOP

Polydrom

GDF

NWB

15th August 2001 MKmetric

additional specificstructuring

Way Forward

export reading

11/12th October 2001

Barcelona MKmetric

Further steps after spotlightsTN

• From “Conceptual Model” to “Data Model”

• From “Common Understanding” to “Ontology”

• Standardisation

• Library of procedures