Eduard Ruffert & Dr. Benedikt Mandel email: ruffert@mkm.de & mandel@mkm.de

1. GTF spotlightsTN 1. Goal & Motivation of spotlightsTN/GTF 2. Principles of development 3. GTF-CM / Examples 4. Further steps Eduard Ruffert & Dr. Benedikt Mandel email: ruffert@mkm.de & mandel@mkm.de MKmetric Gesellschaft für Systemplanung mbH, Karlsruhe

2. Goal of spotlightsTN/GTF • Get the modelling community in Europe (in the World) to “establish the necessity of a common exchange format for transportation models” •  suggestion of a conceptual view as a basis • contact modellers / software providers • discuss GTF Goal •  means for discussion: GTF-CM •  discuss GTF-CM: • Outcome: Agreement & Common Understanding • Email spotlights@mkm.de • Forum gtf.mkm.de • Mailinglistgtf@lists.mkm.de

3. Approach for a solution Matching Data Models using GTF Data Model X/Y/Z GTF Data Model Z/Y/X Solution GTF: „Atomic“ Informational Unit Sizes

4. Overview of interchange structure Concept Client Programmes GTF / TIP GTF / TIP Applications Models Applic –data Operating System Y Operating System X

5. Provider Workspace / User System Application A Filter GTF / TIP data Filter in–house incremental data App. B GTF@Prov. GTF@WS Model User data GTF / TIP data in–house data Operating System X Operating System Y Internet Detail of interchange structure

6. Overview of requirements Supporting Model Communication 1. 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)

7. Overview of requirements 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

8. Universe of GTF GTF = “Generalised Transportation-data Format” - the conceptual modelGTF-XML = the underlying transmission format

9. GTF usage GTF = mediator format UNETRANS TOP GDF NWB Emme/2 ... (strategic and/or operative) UNETRANS TOP GDF NWB Emme/2 ... (strategic and/or operative) Model Y Model X GTF

10. mapping 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 Expert vocabulary GTF-CM The travel timeon Link L from Node A to Node B is X. Node B Node A Link L travel_time = X Problem domain Computer terms

11. Problem Domain Zone Flow – Link Centroid centroid Link Flow on infrastructure Link Intersection – Node Segment – Link in Zone A Infrastructure – Node Boundary / Mountain / River etc. in Zone B

12. GTF-CM

13. GTF-CM

14. GTF-Conceptual Model (CM) ...

15. Main principles • all information is on Link • each object: tree structure (super/sub association) • all problem domain classes are founded on a few framework classes • the number of top level problem domain classes shall be small • Note: • the GTF-CM specification contains both problem domain classes (Toplevels + Sublevels) & Framework classes

16. Principles / Framework classes for GTF-CM specification

17. Example application 1: Transport terminal schematic view of a public transport terminal* * taken from the BRIDGES/D4 report ”Handling Traffic Modelling Networks in GIS” by DTU/TetraPlan

18. Example application 1: in GTF terms Node P Node “Airport” A 5) 6) 3) 1) 2) 4) 8) 7) Node Q

19. Example application 1: GTF objects . . . . . . . . . * Note: associations are not depicted

20. <!-- definition of the Airport Node-Network example--> • <GTFDB id=1 name="Airport Network Example"> • <N id=”1” name=”P"> • </N> • <N id=”2” name=”Q"> • </N> • <!-- definition of the internal Nodes --> • <N id=”3” name=”Airport A”> • <N id=”4” name="A1 airport access"> • </N> • <N id=”5” name="A2 airport egress"> • </N> • <N id=”6” name="A3 check-in counter"> • </N> • <N id=”7” name="A4 check-out counter"> • </N> • <N id=”8” name="A5 departure national"> • </N> • <N id=”9” name="A6 departure international"> • </N> • <N id=”10” name="A7 arrival national"> • </N> • <N id=”11” name="A8 arrival international"> • </N> • </N> • <!-- definition of the link from Node O to Airport A --> • <L id=”10000” name="Route 66 to Airport A" starts_in="1" ends_in="4"> • </L> • <!-- definition of the link from Airport A to Node D --> • <L id=20000 name="Highway 928" starts_in="5" ends_in="2"> • </L> • <!-- definition of the internal links of Node Airport A--> • <L id=30000 name="to check-in" starts_in="4" ends_in="6"> • </L> • <L id=30001 name="from check-out " starts_in="7" ends_in="5"> • </L> • <L id=30010 name="to departure national" starts_in="6" ends_in="8"> • </L> • <L id=30011 name="to departure international" starts_in="6" ends_in="9"> • </L> • <L id=30020 name="from arrival national" starts_in="10" ends_in="7"> • </L> • <L id=30021 name="from arrival international" starts_in="11" ends_in="7"> • </L> • <L id=30030 name="from arrival national transfer to departure national" starts_in="10" ends_in="8"> • </L> • <L id=30031 name="from arrival national transfer to departure international" starts_in="10" ends_in="9"> • </L> • <L id=30040 name="from arrival international transfer to departure national" starts_in="11" ends_in="8"> • </L> • <L id=30041 name="from arrival international transfer to departure international" starts_in="11" ends_in="9"> • </L> • <GTFDB> Example application 1: XML file MKmetric 15th August 2001 Copenhagen

21. Example application 2:Socio-Economic data * * Note: data are fictive

22. Example application 2: in GTF terms Terminator association Meta Zone 1 Transport- Production Population Economy- Characteristics

23. Example application 2: GTF objects . . . . . . . . .

24. Example application 2: XML file <!-- definition of the Socio-Economic data Example--> <GTFDB id=1 name="Socio-Economy Example"> <N id= "2"> <TE id= "3"> <ZO id= "4" name= "1"> </TE> <TE id= "5"> <ZO id= "6" name= "2"> </TE> <TE id= "7"> <ZO id= "8" name= "3"> </TE> </N> <M> <TP> <POP id= "30000" number = "150000" income= "10000" associations= "1"> <ECH id= "685902" GDP= "5.7" associations= "1"> <POP id= "30001" number = "67000" income= "13000" associations= "2"> <ECH id= "685903" GDP= "6.3" associations= "2"> <POP id= "30002" number = "82000" income= "9500" associations= "3"> <ECH id= "685904" GDP= "5.2" associations= "3"> </TP> </M> <GTFDB> MKmetric 15th August 2001 Copenhagen

25. Example application 3:Public Transport Terminal Terminal Stop Route Junction Segment Junction

26. Example application 3: in GTF terms Node 1 Node 3 Node 2 Link 1 Link 2 Node::Junction 8 Node::Junction 4 Link::Segment 12

27. Example application 3: GTF objects * Note: associations are not depicted

28. Example application 3: XML file <!-- definition of the Public Transport example--> <GTFDB id= "0" name= "Public Transport Example"> <N id= "1"> </N> <N id= "2" type= "stop"> </N> <N id= "3"> </N> <N id= "4"> <JU id= "5" associations= "1"> <JU id= "6"> <JU id= "7" associations= "2"> <JU id= "8"> <JU id= "9" associations= "3"> </N> <L id= "10" starts_in="1" ends_in="2"> </L> <L id= "11" starts_in="2" ends_in="3"> </L> <L id= "12"> <SEG id= "13" starts_in= "5" ends_in= "6"> </L> <L id= "14"> <SEG id= "15" starts_in= "6" ends_in= "7"> </L> <L id= "16"> <SEG id= "17" starts_in= "7" ends_in= "8"> </L> <L id= "18"> <SEG id= "19" starts_in= "8" ends_in= "9"> </L> <GTFDB> MKmetric 15th August 2001 Copenhagen

29. Road M1 M2 M3 Example application 4:Dynamic Segmentation

30. Example application 4: in GTF terms Link::Segment 3 Link::Segment 1 Node:: Junction 3 Node:: Junction 1 Link::Segment 2 Node:: Junction 2 DynamicSegmentation:: Milepost 2 DynamicSegmentation:: Milepost 1 DynamicSegmentation:: Milepost 2

31. Example application 4: GTF objects * Note: associations are not depicted

32. Example application 4: XML file • <!-- definition of the Public Transport example--> • <GTFDB id= "0” name= "Public Transport Example"> • <N id= "1”> • </N> • <N id= "2”> • </N> • <N id= "3”> • </N> • <D> • <MI id= "4” distance_from_beginning= "234” distance_from_ending= "15”> • <MI id= "5” distance_from_beginning= "126” distance_from_ending= "124”> • <MI id= "6” distance_from_beginning= "96” distance_from_ending= "53”> • </D> • <L id= "7”> • <SEG id= "8” starts_in= "?” ends_in= "1”> • </L> • <L id= "9”> • <SEG id= "10” starts_in= "1” ends_in= "2”> • </L> • <L id= "11”> • <SEG id= "12” starts_in= "2” ends_in= "3”> • </L> • <GTFDB> MKmetric 15th August 2001 Copenhagen

33. Emme/2 Emme/2 TOP TOP Polydrom GDF NWB Polydrom GTFfile GDF NWB ... ... additional specificstructuring export reading Reader API Func1 ... FuncN MKmetric GTF = mediator format 15th August 2001

34. Emme/2 Emme/2 TOP TOP Polydrom GDF NWB Polydrom GTFfile GDF NWB ... ... specificstructuring import writing Writer API Func1 ... FuncN MKmetric GTF = mediator format 15th August 2001

35. Further steps after spotlightsTN • From “Conceptual Model” to “Data Model” • From “Common Agreement” to “Ontology” • Standardisation • Library of procedures

36. GTF spotlightsTN Email spotlights@mkm.de Forum http://gtf.mkm.de Mailinglistgtf@lists.mkm.de Contact Eduard Ruffert email: ruffert@mkm.de Tel.: ++49 (0) 700 MKMETRIC