16.05.2015 Views

D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus

D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus

D5 Annex report WP 3: ETIS Database methodology ... - ETIS plus

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>D5</strong> <strong>Annex</strong> <strong>WP</strong> 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL –<br />

FREIGHT TRANSPORT DEMAND<br />

Table D.2<br />

Example of Container Registration<br />

Mode Container Meaning<br />

Sea<br />

Road<br />

Yes<br />

No<br />

Commodity transported over sea in a container<br />

Commodity transported by road not in a container<br />

A possible extension to this method is to include also a type of container (large, other) on the<br />

place where otherwise a ‘yes’ would occur. Still a further extension would be to include in stead<br />

of a variable for container only, a variable for classification of loading units types.<br />

Should there be a Restriction on the Number of Links in a Transport Chain?<br />

Combining all the solutions in the previous paragraphs for the problems encountered in the<br />

computer example we see that for registering one flow, many variables are needed. If we take a<br />

look at the transportation of the computer from point A to point F we see that six locations have<br />

to be registered. One origin, four transhipment locations and a destination. Also five modes (one<br />

for each link) have to be registered together with the passive modes and container indications.<br />

This means 21 (= 3 x 5+ 6) variables are necessary for this transport chain. Furthermore<br />

variables are needed to describe the commodity, the weight and the value. Many transport flows<br />

will be less complex but there will also be more complex transport flows meaning that even<br />

more variables are needed.<br />

A partial solution to reduce the size of the database is to use a dynamic data structure in which<br />

for every transhipment place a variable is ‘made’ in the software. This means that sophisticated<br />

software has to be developed. The flow structure however still will be complex and difficult to<br />

comprehend.<br />

Another more pragmatic solution is to restrict the number of links. This also has disadvantages<br />

however, since it is important in case of inter­modal transport to describe all transhipment that<br />

takes place. Furthermore reducing the number of transhipment points in the database also has<br />

some negative impacts on the reliability of the information to be extracted. To get more insight<br />

in this a look will be taken at the example in figure 5.4<br />

158<br />

Document2<br />

27 May 2004

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

Saved successfully!

Ooh no, something went wrong!