• No results found

DATE DOCUMENT CONTACT MAIL PHONE. 9th February 2015 Appendix 3A1 Peter Holst HerzbergPeter Holst Herzberg

N/A
N/A
Protected

Academic year: 2021

Share "DATE DOCUMENT CONTACT MAIL PHONE. 9th February 2015 Appendix 3A1 Peter Holst HerzbergPeter Holst Herzberg"

Copied!
33
0
0

Loading.... (view fulltext now)

Full text

(1)

NEW TRAFFIC MAP

(2)

Guidelines to the Tenderer

This Appendix 3A1 contains the Customer’s documentation of the data and interfaces de-livered.

This section under the heading "Guidelines to Tenderer" will not form part of the final Contract. Appendix 3A1 will be included in the Contract without any other changes than removing this section. For this reason we use the term Supplier instead of Tenderer in the text in this Appen-dix 3A1. When we write “The Supplier shall describe…….” it is actually means “The Tenderer shall describe …”.

(3)

TABLE OF CONTENTS

1 INTERFACES TO OTHER IT SYSTEMS ... 4

Data architecture overview ... 4

1.1 Data Exchange input formats overview ... 5

1.2 Input Data Exchange formats ... 7

1.3 1.3.1 Thematic maps from VD GeoCloud ... 7

1.3.2 Dynamic data ... 8

1.3.2.1 Traffic Conditions, DynDB & DynAPM ... 8

1.3.2.2 E-certificate ... 12

1.3.2.3 Webcam data ... 13

1.3.2.4 Vinterman data ... 14

1.3.2.5 Ferry data ... 19

1.3.2.6 Lane status for the Limfjord Tunnel ... 27

1.3.2.7 Status of Limfjord Bridge... 27

1.3.2.8 Dynamic Service Area Information ... 30

1.3.2.9 Critical announcements ... 31

(4)

1

INTERFACES TO OTHER IT SYSTEMS

This appendix 3D gives a further description of the formats for a number of interfaces men-tioned in Appendix 3A, section 5.

The interfaces to the new traffic map are where possible based on international agreed and applied standard exchange methods and standard formats. However, a number of interfaces are proprietary and nonstandard.

The description of data exchange includes:

 Data architecture overview

 Data exchange format overview.

 Data exchange formats examples and guidelines.

DATA ARCHITECTURE OVERVIEW

1.1

(5)

DATA EXCHANGE INPUT FORMATS OVERVIEW

1.2

The tables show the exchange formats DRD uses for the different input data types.

Data name Format Description

B a c k g ro u n d map s ( K o rt d a ta )

Google Maps Google Maps for Work API Topographical and satellite maps from Google Maps for Work. Data is delivered in different zoom levels. Data will be retrieved by including a customer identifying parameter for statistical and in-voicing purposes.

GST Maps Web Map Service (WTMS) Topographical and satellite maps from GST. Data is delivered in different zoom levels. Data will be retrieved by including a customer identifying parameter for statistical and invoicing purposes.

FOT road network Web Map Feature Service (WFS)

Vector based road network for production of presentation net-works. V D C lou d d a ta

Bicycle Routes Web Feature Service

(WFS)

National and regional bicycle routes.

Road Train road net-work (Modulvogntog)

Web Feature Service (WFS) & Web Map Ser-vice (WMS)

Road Train road network is a special road network for extra-long vehicles and covers both state road and municipality roads. Data are: the actual road network, “Omkobling-spladser”, the companies cov-ered by the network and rest areas capable of handling Road Trains.

Dangerous goods road network (Farligt gods ruter)

Web Feature Service (WFS) & Web Map Ser-vice (WMS)

Dangerous goods road net-work is a special road netnet-work for vehicles carrying danger-ous goods and covers both state road and municipality roads.

Heavy Truck road net-work

(Tungvognsvejnettet)

Web Feature Service (WFS) & Web Map Ser-vice (WMS)

Heavy Truck road network is a special network that shows which category of trucks can drive at which roads. The net-work only covers state roads

(6)

and some former county roads.

Carpooling parking lot Web Feature Service

(WFS) & Web Map Ser-vice (WMS)

Parking lots along the road network for car pooling pur-poses.

Bridge data Web Feature Service (WFS) & Web Map Ser-vice (WMS)

Data about bridges, tunnels and portals: position (coordinates), ground clearance heights and

weight restrictions. Data origin from DRD´s DANBRO database. Rest and Service

are-as (Rare-astepladser og serviceanlæg.)

Web Feature Service (WFS) & Web Map Ser-vice (WMS)

Data (static) information about Rest and Service Areas.

D y n a mi c D a ta Traffic Conditions, DynDB & DynAPM

Proprietary XML-format Data about current traffic

con-ditions. Data only covers a part of the DRD roads.

E-Certificates (E-attest) Proprietary XML-format Data about specific lorries span and weight classes based on WEB-number from E-certificate.

WEB CAM Denmark Proprietary XML-format/DATEX II

Web cam still pictures form both state and municipality roads in Denmark

WEB CAM Sweden Proprietary XML-format/DATEX II

Web cam still pictures form both state and municipality roads in Sweden

VINTERMAN Proprietary

XML-format/DATEX II

Data about slippery roads, salting and snow clearance status, position of salting/snow clearance vehicles, air and road temperature. Data also covers a number of bicycle routes.

Ferries Proprietary

XML-format/DATEX II

Location of ferry ports and current traffic status for the ferries.

Limfjord Tunnel Proprietary

XML-format/DATEX II

Data about how many lanes are open/closed in each direc-tion.

(7)

format/DATEX II is open or closed for road traf-fic.

Trafikman2 DATEX II Dynamic traffic data about

road works and other incidents on and information about the road network.

Real Time Parking Area Information

(Raste-pladsinformation)

DATEX II Data about free parking slots

for trucks and percentage of free slots.

Warm Asphalt RSS feed When the pavement is too warm

to carry lorries.

Critical announce-ments

RSS feed. Special and very critical traffic

messages with high im-portance. E.g. “Storebelt bridge is closed”

Typical Traffic Proprietary XML-format Data about historic traffic

con-dition.

INPUT DATA EXCHANGE FORMATS

1.3

1.3.1

Thematic maps from VD GeoCloud

Below are examples of links to Road Train data:

WMS: http://geocloud.vd.dk/VM/wms?request=GetCapabilities Vejnet – WMS: http://geocloud.vd.dk/VM/wms?LAYERS=VM:modulvogntog&STYLES=&FORMAT=image%2Fp ng&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=E PSG:25832&BBOX=198356,6013970,984788,6464530&WIDTH=960&HEIGHT=550 Omkoblingspladser – WMS:

(8)

http://geocloud.vd.dk/VM/wms?LAYERS=VM:omkoblingspladser&STYLES=&FORMAT=image %2Fpng&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&S RS=EPSG:25832&BBOX=198356,6013970,984788,6464530&WIDTH=960&HEIGHT=550 Virksomheder – WMS: http://geocloud.vd.dk/VM/wms?LAYERS=VM:virksomheder&STYLES=&FORMAT=image%2Fp ng&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=E PSG:25832&BBOX=198356,6013970,984788,6464530&WIDTH=960&HEIGHT=550 WFS: http://geocloud.vd.dk/VM/wfs?request=GetCapabilities Vejnet – WFS: http://geocloud.vd.dk/VM/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=V M:modulvogntog&maxFeatures=50 Omkoblingspladser – WFS: http://geocloud.vd.dk/VM/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=V M:omkoblingspladser&maxFeatures=50 Virksomheder – WFS: http://geocloud.vd.dk/VM/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=V M:virksomheder&maxFeatures=50

1.3.2

Dynamic data

The dynamic data are retrieved from a number of different sources.

1.3.2.1 Traffic Conditions, DynDB & DynAPM

XML-Format:

The following xml-files are used:

 Xml file containing road network: Configuration file with information about the road network

(9)

 Xml file containing segments: Configuration file with information about segments in one or more road networks and a certain zoom level. It is primary polyline coordinats. There exist an attribute telling the type of section: ”Motorvej”, ”Øvrige statsveje” or ”Kommuneveje”.

 Xml file containing traffic conditions: Data can be delivered for one or more road networks.

Data includes traffic conditions, travel times, speed etc. per segment.

Example of road network XML:

http://vej08.vd.dk/pls/dynapm/dynapm.dynapm_udt_xml.VejNetXMLVejnetGruppe?i_vejnetgrup pe_id=VG_dynAPM

<?xml version="1.0" encoding="iso-8859-1" ?> -<vejnetgruppe id="VG_dynAPM">

<vejnetgruppe_key_id>3</vejnetgruppe_key_id>

<vejnetgruppe_beskrivelse>Vejnet-gruppe indeholdende dynAPM vejnette-ne</vejnetgruppe_beskrivelse>

-<vejnet keyid="12">

<vejnet_id>dynAPM_S</vejnet_id> <ikon_punkt_xkoor>0</ikon_punkt_xkoor> <ikon_punkt_ykoor>0</ikon_punkt_ykoor> <ikon_type>1</ikon_type> <vises_paa_zoom_niveau>0</vises_paa_zoom_niveau> <box_oevre_venstre_xkoor>731110</box_oevre_venstre_xkoor> <box_oevre_venstre_ykoor>-6191968</box_oevre_venstre_ykoor> <box_nedre_hoejre_xkoor>778541</box_nedre_hoejre_xkoor> <box_nedre_hoejre_ykoor>-6159937</box_nedre_hoejre_ykoor> </vejnet> -<vejnet keyid="9">

<vejnet_id>dynAPM_T</vejnet_id>

<ikon_punkt_xkoor>548659</ikon_punkt_xkoor> <ikon_punkt_ykoor>-6154157</ikon_punkt_ykoor> . . </vejnetgruppe> Example of segment XML:

XML with segment data and coordinates according to zoom level (11 zoom levels)

(10)

The delivered data in different zoom levels take into account a relevant distance from the road centre line: http://vej08.vd.dk/pls/dynapm/dynapm.dynapm_udt_xml.VejNetXMLSegmenter?i_vejnet_id=dyn APM_K&i_zoom_niveau=1 <?xml version="1.0" encoding="iso-8859-1" ?> <VejNetXMLSegmenter>

<vejnet id="dynAPM_K" type="Segmenter"> <vejnet_key_id>6</vejnet_key_id>

<vejnet_beskrivelse>dynAPM_K vejnet</vejnet_beskrivelse> <zoom_niveau>1</zoom_niveau>

<segment id="AM3_SE0001" key_id="2596">

<vej_retning gruppe_seq_no="8" rute_seq_no="1">Motorring 3 sydgående</vej_retning> <fra_punkt id="AM3_P0001" key_id="1697">

<beskrivelse>X Kgs Lyngby</beskrivelse> </fra_punkt>

<til_punkt id="AM3_P0002" key_id="1698"> <beskrivelse><17> Jægersborgvej</beskrivelse>

</til_punkt>

<segment_koord id="AM3_SE0001" key_id="2596" prev_key_id="2760" next_key_id="2598"> <koord>720973,-6186056 720951,-6185856 720890,-6185501</koord>

</segment_koord> </segment>

<segment id="AM3_SE0002" key_id="2597">

<vej_retning gruppe_seq_no="18" rute_seq_no="26">Motorring 3 nordgående</vej_retning> <fra_punkt id="AM3_P0002" key_id="1698">

(11)

</fra_punkt>

<til_punkt id="AM3_P0001" key_id="1697"> <beskrivelse>X Kgs Lyngby</beskrivelse>

</til_punkt>

<segment_koord id="AM3_SE0002" key_id="2597" prev_key_id="2599" next_key_id="2761"> <koord>720921,-6185505 720971,-6185635 720994,-6185712 6185830 721019,-6185890 721015,-6186069</koord> </segment_koord> </segment> . . </vejnet> </VejNetXMLSegmenter>

Example of XML with traffic conditions:

It is possible to define more than one VEJNET_ID in the same query separated by comma.

The traffic conditions are calculated from

1. If the number of cars is less than zero is returned "no data" (255). 2. If the number of cars is greater than n1 returned "queue-forming" (30). 3. If the average speed is lower than h1% of the free speed returned also "Queue-formation" (30).

4. If the average speed is less than (number of cars * d1) returned again "Queue-formation" (30).

5. If the number of cars is greater than n2 returned "Heavy traffic" (20).

6. If the average speed is lower than h2% of the free speed returned also "Heavy traffic" (20). 7. If the average speed is less than (number of cars * d2) returned again "Close tra-received" (20).

In dynAPM it can not be assume that the default rate is the same for all segments, so H1 and H2 is defined as percentages of the default speed. H1 is set at 40%, and H2 is set at 80%, equivalent to 44km / h and 88km / h at a default speed (speed of the sign) at 110km / h.

(12)

http://vej08.vd.dk/pls/dynapm/dynapm.dynapm_udt_xml.VejNetXMLTrafiktilstande?i_vejnet_id= dynAPM_K,dynAPM_T

<?xml version="1.0" encoding="iso-8859-1" ?> <VejNetXMLTrafiktilstande>

<vejnet id="dynAPM_K" type="Trafiktilstande"> <vejnet_key_id>6</vejnet_key_id>

<vejnet_beskrivelse>dynAPM_K vejnet</vejnet_beskrivelse> <segment key_id="2625"> <trafiktilstand>10</trafiktilstand> <rejsetid>,48</rejsetid> <hastighed>107,75</hastighed> <laengde>,9</laengde> <hist_rejsetid>,51</hist_rejsetid> <prognose15>,49</prognose15> <prognose30>,5</prognose30> <paalidelighed>Høj</paalidelighed> <tidspunkt>01.08.2011 12:00</tidspunkt> </segment> <segment key_id="2640"> <trafiktilstand>10</trafiktilstand> <rejsetid>1,13</rejsetid> <hastighed>99,77</hastighed> <laengde>1,9</laengde> <hist_rejsetid>1,07</hist_rejsetid> <prognose15>1,12</prognose15> <prognose30>1,1</prognose30> <paalidelighed>Høj</paalidelighed> <tidspunkt>01.08.2011 12:00</tidspunkt> </segment> . . </vejnet> </VejNetXMLTrafiktilstande>

1.3.2.2 E-certificate

The XML-service will deliver a table containing a combination of span and weight class based on a “WRB-number” as input. The “WEB-number” is the identification number of the

(13)

Spv

Klasse

2

50

4

54

6

64

8

78

10

86

15

89

20

89

25

87

30

93

40

112

50

120

60

126

80

132

100

136

200

142

1.3.2.3 Webcam data

XML-Format:

(14)

Example <ROWS time="2011-10-31 15:00:07"> <ROW num="295"> <Lat>56,13559</Lat> <Long>10,15648</Long> <Route><![CDATA[501/Ring 02]]></Route> <Place><![CDATA[Viby]]></Place> <DirText><![CDATA[sydvest/E45]]></DirText> <Direction>260</Direction> <Link>http://webcam.trafikken.dk/webcam/aahavevej_1.jpg</Link> <Info><![CDATA[Rute 501/Ring 02, Viby mod sydvest retning E45]]></Info> </ROW>

<ROW num="297"> Unique Id of the camera <Lat>56,13559</Lat> Geographical latitude as WSG84 <Long>10,15648</Long> Geographical longitude as WSG84 <Route><![CDATA[501/Ring 02]]></Route> Route

<Place><![CDATA[Viby]]></Place> Place on route <DirText><![CDATA[sydvest/E45]]></DirText> Direction text <Direction>260</Direction> Direction degrees

<Link>http://webcam.trafikken.dk/webcam/aahavevej_1.jpg</Link> Link to pictures from the camera <Info><![CDATA[Rute 501/Ring 02, Viby mod sydvest retning

E45]]></Info>

Text combining the other text elements

1.3.2.4 Vinterman data

XML-Format:

The System shall be able to read or receive XML files with the Vinterman data themes. These themes include:

 Road and air Temperatures

 Wind

 Icy roads information both as point data and as road section data

 Salting information both as point data and as road section data

 Vehicle location and “track”

The data are supplied as text files in a number of different XML formats described with the fol-lowing examples:

(15)

Road and air temperatures Example <mstdata time="2011-10-31 14:50:22"> <msttemp id="1000"> <coord>M717415,-6211087</coord> <dkshow>0</dkshow> <air>14</air> <road>14</road> </msttemp> <msttemp id="1001"> <coord>M682352,-6205283</coord> <dkshow>0</dkshow> <air>12</air> <road>12</road> </msttemp>

<msttemp id=”1000”> Unique Id of the measuring station

<coord>M717415,-6211087</coord> Geographical coordinates as UTM32 datum WSG84 <air>14</air> Air temperature

<road>14</road> Road temperature

Wind Example <mstdata time="2011-10-31 14:50:22"> <mstwind id="1018"> <coord>M695357,-6165882</coord> <windspeed>1</windspeed> <winddir>10</winddir> </mstwind> <mstwind id="1181"> <coord>M708726,-6205138</coord> <windspeed>1</windspeed> <winddir>10</winddir> </mstwind>

<msttemp id=”1018”> Unique Id of the measuring station

<coord>M695357,-6165882</coord> Geographical coordinates as UTM32 datum WSG84 <windspeed>1</windspeed> Wind speed in meter/second

<winddir>10</winddir> Wind direction in degrees

Icy road warnings

Example <roadreportmun time="2011-10-31 14:50:22"> <mun id="101"> <coord>M723722,-6178437</coord> <Location>4570</Location> <report>

<![CDATA[<b>Statsveje:</b><br> <br><b>København Kommune, Primære ve je:</b><br><br><b>København Kommune, Øvrige veje:</b><br>]]>

</report> </mun>

<mun id=”101”> Unique Id of the municipality, 99 means all Denmark <coord> M622257,-6132276</coord> Geographical coordinates as UTM32 datum WSG84 <Location> AlertC Location code

(16)

Salting information Example <roadsaltmun time="2011-10-31 14:50:22"> <mun id="101"> <coord>M723722,-6178437</coord> <Location>4570</Location> <report>

<![CDATA[ <b>Statsveje:</b><br>Ingen information om seneste saltning<br><b>København Kommune, Pri mære veje:</b><br>Ingen information om seneste saltning<br><b>København Kommune, Øvrige ve je:</b><br>Ingen information om seneste saltning]]>

</report> </mun>

<mun id=”101”> Unique Id of the municipality, 99 means all Denmark <coord> M622257,-6132276</coord> Geographical coordinates as UTM32 datum WSG84 <Location> AlertC Location code

<report> Textual report about the salting situation

Example for a bicycle area warning. :

(17)
(18)
(19)

1.3.2.5 Ferry data

Format description:

Ferry data are delivered in two different CSV formats. Ferry messages input as CSV format 1

The System shall be able to read and store Ferry departures and irregularities from a num-ber of ferry companies.

In case of a cancellation and delay, the System shall create or update a corresponding traf-fic message.

The data are provided as ftp PUSH from the ferry company

All planned departures for a period are exchanged. The period depends often on the num-ber of departures each day. The period is given by the first and the last departure in the text file.

All departures are exchanged even if they have not changed since the last exchange. No error handling or keep-alive signaling. All departures are sent at regular time intervals and no history is kept.

The information in the text file are separated by ”;”.

Optional fields are placed last in the records and can be omitted or written as “”. Field Format Mandatory Description

Route AFAN, 4 letters

Yes AF= code for the departure terminal AN= code for the arrival terminal Date YYYYMMDD Yes Departure date, e.g. 20080813 Departure time HHMM Yes Departure time, e.g. 1230

Sailing time HHMM Yes Sailing time, e.g. 0230 equals 2 hours and 30 minutes FB Always ”FB” No Not used

Ferry name Text No Not used Ferry route

type

1 letter Yes A= ordinary, F= fright, R= rail/train Only ”A” are to be imported State 2 digits Yes 00=normal operation

01=no reservation possible 02=cancelled

(20)

Example: RFPU;20011210;1245;0045;FB;SH;A;00 RFPU;20011210;1315;0045;FB;;A;00 RFPU;20011210;1345;0045;FB;;A;01 RFPU;20011210;1415;0045;FB;PB;A;02 RFPU;20011210;1445;0045;FB;SH;A;00 RFPU;20011210;1515;0045;FB;;A;00;0025 RFPU;20011210;1545;0045;FB;DE;A;00;0030 RFPU;20011210;1615;0045;FB;PB;A;00 RFPU;20011210;1645;0045;FB;SH;A;00;0015

Ferry messages input as CSV format 2

The System shall be able to read and store Ferry departures and irregularities from a number of ferry companies.

In case of a cancellation and delay, the System shall create or update a corresponding traffic message.

The data are provided as via http PULL

They are one feed for each ferry line, e.g. are departures from “Alstrafikken” read by

http://www.faergen.dk/info/AT_departures.txt

. Example: "AFGANGS-HAVN";"AFGANGSLEJE";"PLANMÆSSIG_AFGANG";"FORVENTET_AFGANG";"ANKOMSTHAVN";"PLANMÆSSIG_ AN-KOMST";"FORVENTET_ANKOMST";"FÆRGE";"UDSOLGT_PAX";"UDSOLGT_CAR";"AFLYST";"STATUS";"PAXCHE CKINTID";"CARCHECKINTID";"NOTE";"FIRMA" "BOJ";"";"22-09-2011 13:00:00";"22-09-2011 13:00:00";"FYN";"22-09-2011 13:50:00";"22-09-2011 13:50:00";"AT";"Nej";"Nej";"Nej";"Normal";"22-09-2011 12:50:00";"22-09-2011 12:50:00";"";"AT" "FYN";"";"22-09-2011 14:00:00";"22-09-2011 14:00:00";"BOJ";"22-09-2011 14:50:00";"22-09-2011 14:50:00";"AT";"Nej";"Nej";"Nej";"Normal";"22-09-2011 13:50:00";"22-09-2011 13:50:00";"";"AT" "BOJ";"";"22-09-2011 15:00:00";"22-09-2011 15:00:00";"FYN";"22-09-2011 15:50:00";"22-09-2011 15:50:00";"AT";"Nej";"Nej";"Nej";"Normal";"22-09-2011 14:50:00";"22-09-2011 14:50:00";"";"AT" "FYN";"";"22-09-2011 16:00:00";"22-09-2011 16:00:00";"BOJ";"22-09-2011 16:50:00";"22-09-2011 16:50:00";"AT";"Nej";"Nej";"Nej";"Normal";"22-09-2011 15:50:00";"22-09-2011 15:50:00";"";"AT"

Translation of the Danish headers:

AFGANGSHAVN Departure terminal AFGANGSLEJE Not used

PLANMÆSSIG_AFGANG Not used FORVENTET_AFGANG Departure time ANKOMSTHAVN Arrival terminal PLANMÆSSIG_ANKOMST Planned arrival time FORVENTET_ANKOMST Expected arrival time

FÆRGE Not used

(21)

UDSOLGT_CAR No reservation possible (Ja for yes and Nej for No) AFLYST Cancelled (Ja for yes and Nej for No)

STATUS Not used

PAXCHECKINTID Not used CARCHECKINTID Not used

NOTE Not used

FIRMA Not used

The delay is calculated as the difference between excepted and planned arrival time.

XML-format example for a combined ferry service: XSD:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Steen Kjeltoft (Vejdirektoratet) -->

<!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by Steen Kjeltoft (Vejdirektoratet) -->

<!--W3C Schema generated by XMLSpy v2005 rel. 3 U (http://www.altova.com)-->

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="ferryroutes">

<xs:annotation>

<xs:documentation>The root element</xs:documentation> </xs:annotation>

<xs:complexType> <xs:sequence>

<xs:element ref="departureTerminal" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence>

</xs:complexType> </xs:element>

<xs:element name="coordinates"> <xs:annotation>

<xs:documentation>Coordinates for the departure terminal as latitude and longitude in WSG84</xs:documentation>

</xs:annotation> <xs:complexType>

(22)

<xs:sequence> <xs:element ref="latitude"/> <xs:element ref="longitude"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="departure"> <xs:annotation>

<xs:documentation>A single departure</xs:documentation> </xs:annotation>

<xs:complexType> <xs:sequence>

<xs:element name="departureDateTime" type="xs:string"/> <xs:element ref="statusCode"/>

<xs:element name="departureText" type="xs:string"/> </xs:sequence>

</xs:complexType> </xs:element>

<xs:element name="departureTerminal"> <xs:annotation>

<xs:documentation>Departure terminal og harbour as all ferry departures are mod-elled to be departing from the same position.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element ref="terminalName"/> <xs:element ref="coordinates"/> <xs:element name="region"> <xs:annotation>

<xs:documentation>AlertC area code for region</xs:documentation> </xs:annotation>

</xs:element>

(23)

<xs:element ref="event_type"/> </xs:sequence>

</xs:complexType> </xs:element>

<xs:element name="departureText" type="xs:string"> <xs:annotation>

<xs:documentation>A text describing anormalities for a departure</xs:documentation> </xs:annotation>

</xs:element>

<xs:element name="departures"> <xs:annotation>

<xs:documentation>Departures from 1 ferryLine from the Departure termi-nal</xs:documentation>

</xs:annotation> <xs:complexType>

<xs:sequence>

<xs:element ref="departure" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence>

</xs:complexType> </xs:element>

<xs:element name="event_type"> <xs:annotation>

<xs:documentation>1 if only normal departures from the departure terminal. 2 otherwise.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="1"/> <xs:enumeration value="2"/> </xs:restriction> </xs:simpleType> </xs:element>

(24)

<xs:annotation>

<xs:documentation>The name of the ferry company</xs:documentation> </xs:annotation>

</xs:element>

<xs:element name="ferryCompanyURL" type="xs:string"> <xs:annotation>

<xs:documentation>An URL to the internet site for the ferry compa-ny</xs:documentation>

</xs:annotation> </xs:element>

<xs:element name="ferryLine"> <xs:annotation>

<xs:documentation>A specific ferryline sailing from the departure termi-nal</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element ref="lineName"/> <xs:element ref="ferryCompany"/> <xs:element ref="ferryCompanyURL"/> <xs:element ref="ferrySailingTime"/> <xs:element ref="departures"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="ferrySailingTime" type="xs:string"> <xs:annotation>

<xs:documentation>The sailing time as hh:mm, a range hh:mm-hh:mm if the sailing time can vary</xs:documentation>

</xs:annotation> </xs:element>

<xs:element name="latitude" type="xs:string"> <xs:annotation>

(25)

<xs:documentation>Latitude in WSG84</xs:documentation> </xs:annotation>

</xs:element>

<xs:element name="lineName" type="xs:string"> <xs:annotation>

<xs:documentation>The name of the specific ferry line, e.g. Odden-Ebeltoft</xs:documentation>

</xs:annotation> </xs:element>

<xs:element name="longitude" type="xs:string"> <xs:annotation> <xs:documentation>Longitude in WSG84</xs:documentation> </xs:annotation> </xs:element> <xs:element name="statusCode"> <xs:annotation>

<xs:documentation>Statuscode for a departure (normal, cancelled, noreservation and delayed)</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="delayed"/> <xs:enumeration value="cancelled"/> <xs:enumeration value="noreservation"/> <xs:enumeration value="normal"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="terminalName" type="xs:string"> <xs:annotation>

<xs:documentation>The name of the departure terminal, e.g. Odden</xs:documentation>

(26)

</xs:element> </xs:schema>

(27)

1.3.2.6 Lane status for the Limfjord Tunnel

Format:

The data can be read as a text file as ftp PULL. Example:  E1N 2011-05-05 01:04:31Z  E2N 2011-05-05 01:04:31Z  E3N 2011-05-05 01:04:31Z  W1S 2011-05-05 01:03:09Z  W2S 2011-05-05 01:03:09Z  W3S 2011-05-05 01:03:09Z Explanations:

 First character tells if the record concerns the east bound (E) or west bound (W) tube

 Second character tells the lane number (1 is the right and slowest lane)

 Third character tells the direction of the traffic, North (N), South (S) or Closed (X)

 The rest of the record contains the time as UTC time

The combination E and N or W and S tells that the traffic is in the normal direction The combination E and S or W and N tells that the traffic is in the opposite direction The file contains always the 6 shown lines.

The specific data location and access information will be provided during the start-up of the delivery phase.

1.3.2.7 Status of Limfjord Bridge

Format:

The status of the bridge is either open or closed for road traffic:

Indgang OFF: Closed=True

Indgang ON: Closed=False.

(28)

Example from .NET:

(29)

The Service is accessed:

static string bridgeOpen(SqlConnection connLog)

{

try

{

ConsoleApplication1.limfjordBridge.TrafficClient ws = new

ConsoleApplication1.limfjordBridge.TrafficClient();

var result = ws.GetLimfjordsbro().Closed.ToString();

string lanestate = "open";

if (result == "True") lanestate = "closed";

return lanestate;

}

catch (Exception ex)

(30)

updateLog(connLog, "Fejl i web-servicekald" + ex.ToString()); return "open";

} }

1.3.2.8 Dynamic Service Area Information

At present, there only exist data for “Kongsted Rasteplads” near Ringsted.

Data are read vis http://10.242.113.200:8081/ every 5 minute. The format is Datex II Situation Publication, recordtype ”CarParks”. The location is given as a location code (AlertC location code).

Example of DATEX II XML file:

<?xml version="1.0" encoding="UTF-8"?>

<d2LogicalModel xmlns="http://datex2.eu/schema/2/2_0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" modelBaseVersion="2"> <exchange> <supplierIdentification> <country>dk</country> <nationalIdentifier>DRD</nationalIdentifier> </supplierIdentification> </exchange>

<payloadPublication xsi:type="SituationPublication" lang="dk"> <publicationTime>2014-10-13T14:13:07+02:00</publicationTime> <publicationCreator>

<country>dk</country>

<nationalIdentifier>Kongsted</nationalIdentifier> </publicationCreator>

<situation id="CarparkKongsted" version="1"> <headerInformation>

<confidentiality>noRestriction</confidentiality> <informationStatus>real</informationStatus> </headerInformation>

<situationRecord xsi:type="CarParks" id="CarparkKongsted" version="1">

<situationRecordCreationTime>2014-10-13T14:13:07+02:00</situationRecordCreationTime> <situationRecordVersionTime>2014-10-13T14:13:07+02:00</situationRecordVersionTime> <probabilityOfOccurrence>certain</probabilityOfOccurrence>

(31)

<validity> <validityStatus>definedByValidityTimeSpec</validityStatus> <validityTimeSpecification> <overallStartTime>2014-10-13T14:13:07+02:00</overallStartTime> </validityTimeSpecification> </validity> <groupOfLocations xsi:type="Point"> <alertCPoint xsi:type="AlertCMethod2Point"> <alertCLocationCountryCode>E</alertCLocationCountryCode> <alertCLocationTableNumber>33</alertCLocationTableNumber> <alertCLocationTableVersion>1</alertCLocationTableVersion> <alertCDirection> <alertCDirectionCoded>positive</alertCDirectionCoded> </alertCDirection> <alertCMethod2PrimaryPointLocation> <alertCLocation> <specificLocation>1752</specificLocation> </alertCLocation> </alertCMethod2PrimaryPointLocation> </alertCPoint> </groupOfLocations> <carParkIdentity>Kongsted</carParkIdentity> <carParkOccupancy>34</carParkOccupancy> <numberOfVacantParkingSpaces>23</numberOfVacantParkingSpaces> <carParksExtension> <vehicleType>lorry</vehicleType> </carParksExtension> </situationRecord> </situation> </payloadPublication> </d2LogicalModel>

1.3.2.9 Critical announcements

Data will be delivered as a RSS feed. Se example below:

(32)

1.3.2.10 Typical traffic

Data will be delivered in two formats:

 Standard Open Geospatial Consortium (OGC) Web Map Tile Service (WMTS) for general

map purpose and

 A standard Open Geospatial Consortium (OGC) Get Feature Service for user click services.

During the clarification phase the exact format and location will be communicated to the suppli-er.

(33)

Example of request string: (WMS GetFeatureInfo): http://prod.speedmap.dk/mapserver/mapserv.exe?MAP=c:/inetpub/speedmap.triona.se/root/spe edmap/parttables/2010_rg1_d1_dt1_ts5_tt3.map&LAYERS=2010_1_1_1_5_3&SERVICE=WM S&VERSION=1.1.1&REQUEST=GetFeatureInfo&SRS=EPSG%3A32632&EXCEPTIONS=appli cton/vnd.ogc.se_xml&BBOX=722068.384632%2C6176406.884684%2C726310.572303%2C61 79219.384688&X=485.8500061035156&Y=340.1000061035156&INFO_FORMAT=application/ vnd.ogc.gml&QUERY_LAYERS=2010_1_1_1_5_3&WIDTH=1086&HEIGHT=720

References

Related documents

With great flexibility in terms of storage capacity and system power, this system offers the ideal solution for high self-consumption and intelligent energy management for nearly

This product is not a dangerous good according to the Australian Code for the Transportation of Dangerous Goods by Road and Rail (ADG Code), the International Maritime Dangerous

They are the building blocks, such as the technical platform upon which the EHR system is built (e.g.,Windows, Linux, or MacIntosh, etc.) Also what kind of database structure

Not classified as Dangerous Goods by the criteria of the “Australian Code for the Transport of Dangerous Goods by Road &amp; Rail” and the “New Zealand NZS5433: Transport of

The proposed method is a refi ned Earned Schedule (ES) based nonlinear CEAC model modifi ed with a new parameter representing the S-shaped contingency consumption as a portion of

As anxiety and alexithymia are positively correlated, no differences were hypothesized between repressors and the two high trait anxiety groups (high-anxious and defensive

This review was performed to determine if the Company completed the NAIC Annual Statement in accordance with the NAIC Annual Statement Instructions and to

From this planning stage, a sur- gical template is generated for implant placement, allowing minimally invasive surgical techniques while assuring accuracy of implant placement