15.05.2015 Views

D5 Annex report WP 7: ETISDatabase methodology ... - ETIS plus

D5 Annex report WP 7: ETISDatabase methodology ... - ETIS plus

D5 Annex report WP 7: ETISDatabase methodology ... - ETIS plus

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>D5</strong> <strong>Annex</strong> <strong>WP</strong> 7: <strong>ETIS</strong> DATABASE METHODOLOGY AND DATABASE USER<br />

MANUAL – PASSENGER TRANSPORT SUPPLY<br />

5 LINKS OF <strong>WP</strong> 7 TO OTHER WORKPACKAGES<br />

The <strong>methodology</strong> of data generation for the supporting indicators in the scope of <strong>WP</strong> 7 implies<br />

close linkages with other work packages, particularly to<br />

· <strong>WP</strong> 5, networks<br />

· <strong>WP</strong> 4, passenger demand<br />

· <strong>WP</strong> 3, freight demand<br />

Some of the variables required for the generation of data for <strong>WP</strong> 7’s supporting indicators will<br />

be provided by other work packages. The following table (Table 5.1) names those variables, for<br />

which data is coming from other work packages.<br />

Table 5.1<br />

Ref.<br />

supporting<br />

indicator<br />

List of variables required from other work packages<br />

Variable Title of the variable Data generated<br />

2.1.4 d i length of rail network link i belonging to corridor l <strong>WP</strong> 5<br />

2.1.4<br />

tg<br />

d k length of network link k on corridor l and meeting EC<br />

directive on standard track<br />

<strong>WP</strong> 5<br />

k<br />

directive on standard power supply<br />

2.1.4<br />

ps<br />

d length of network link k on corridor l and meeting EC <strong>WP</strong> 5<br />

2.1.4<br />

sg<br />

d k length of network link k on corridor l and meeting EC<br />

directive on train signaling system<br />

<strong>WP</strong> 5<br />

1.6.1<br />

s<br />

vol<br />

freight<br />

road freight transport volume <strong>WP</strong> 3<br />

1.6.1<br />

s<br />

vol road passenger transport volume<br />

passt<br />

<strong>WP</strong> 4<br />

1.6.1 rt s road type link s belong to <strong>WP</strong> 5<br />

by<br />

1.6.1 d ij<br />

rail<br />

road distance between i and j on the fastest path <strong>WP</strong> 5<br />

2.6.4 d ij<br />

rail<br />

distance between i and j by rail on the fastest route <strong>WP</strong> 5<br />

bu sin ess<br />

2.6.4 l share of rail business trips on relation (i,j) <strong>WP</strong> 4<br />

3.6.1<br />

3.6.2<br />

ij<br />

S pij<br />

share of travellers by air of trip purpose p between i<br />

and j<br />

<strong>WP</strong> 4<br />

3.6.1 A pik access time from i to k when travelling in trip purpose <strong>WP</strong> 7/ <strong>WP</strong> 4<br />

p<br />

3.6.1 E plj egress time from i to k when travelling in trip purpose p <strong>WP</strong> 7/ <strong>WP</strong> 4<br />

3.6.2 C pik access/egress costs from i to k when travelling in trip<br />

purpose p<br />

<strong>WP</strong> 7/ <strong>WP</strong> 4<br />

A sound co­operation and interface between these work packages, especially between <strong>WP</strong> 7,<br />

<strong>WP</strong> 4 and <strong>WP</strong> 5, is ensured by the fact, that the same partners play prominent roles in two or<br />

three of these work packages.<br />

R20040089.doc<br />

27 May 2004 35

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!