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

16.05.2015 Views

D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND The last step of this method is the modification of the record structure. The record structure is modified in such a way that a transport chain with two transhipment locations fits in the structure: · Origin country (ETIS country classification) · First transhipment location (still empty in this phase) · Second transhipment location (still empty in this phase) · Destination country (ETIS country classification) · Mode at origin · Mode between transhipment locations · Mode at destination · NSTR 2 digit commodity classification · Value of the goods (in Euro) · Volume of the goods (in tonnes) · Indicator absolute difference between import and export registration · Indicator relative difference between import and export registration · Indicator for intra­EU or extra­EU trade In the second method the transhipment locations will be filled. Method 2: Estimation of transhipment In the first method the database structure has been set up in such a way that information for maximum two transhipment locations along the transport chain can be stored. In the first method, the transhipment locations are still empty. In the second method the transhipment locations will be estimated. Since it is not feasible to estimate transhipment at inland terminals in the ETIS project, only transhipment at seaports is included. For the estimation of the transhipment locations two types of flows are distinguished: · Transit flows; goods transhipped in a port with both origin and destination outside the country where the port is located (either mode before or mode after transhipment is sea transport); · Import and export by sea; Import: transport by sea from a country to a port (located in a different country) where the goods are transhipped after which they are transported by a land mode to the destination region (which is located in the same country as the port); Export: transport from a region by a land mode to a port (which is located in the same region as the origin region) where the goods are transhipped after which they are transported by sea to a country (which is different than the origin country). In this method first the transit flows are estimated and added to the O/D matrix, secondly the import and export by sea is estimated and added to the O/D matrix. 48 Document2 27 May 2004

D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND Transit flows Data about transit in seaports is available for ports in Belgium, the Netherlands and Germany, for ports in other countries no data is available for transit. There are some problems with this data (intra­EU transit is not included in the Belgium data, transit through the Netherlands is not collected anymore for the year 2000), but these gaps can be filled by applying estimation procedures in order to construct a complete and consistent transit database. This data has the following format: · Origin country (for instance Southern America) · Transhipment port (for instance Hamburg in Germany) · Destination country (for instance Austria) · Mode before transhipment (for instance sea transport) · Mode after transhipment (for instance road transport) · Commodity type (according to the NSTR2 or NSTR1 classification) · Volume of the goods (weight in tonnes) These transit flows have to included in the O/D matrix in such a way that double countings are avoided. This is done in three steps: 1. Match transit flows with international trade flows; 2. Make corrections for confusion between trade and transport flows; 3. Add remaining transit flows. Match transit flows with international trade flows In the first step the transit flows through ports in Belgium, the Netherlands and Germany are matched with the international trade flows in the modified Comext database resulting from method 1. An example how these flows are matched is given in table 6.4. Table 6.4 Origin region Mode origin Matching transit flows with international trade flows Transh. region Mode Transh. region Mode destination Destination region Volume (tonnes) Flow type USA sea Germany 25000 International USA sea Rotterdam (NL) rail Germany 15000 Transit In the Comext database it is known that 25.000 tonnes of a specific commodity is transported from the USA to Germany with mode sea (for extra­EU trade the mode of transport at the border of the Community). From the transit data it is known that 15.000 tonnes of a specific commodity is transported by sea from the USA to Rotterdam where the goods are transhipped onto mode rail and then transported to Germany. In this example all transit can be matched with the international trade, in the O/D matrix the international trade will be reduced by the transit flows (25.000 – 15.000 = 10.000 tonnes) and a record will be added to the O/D matrix for the transit through Rotterdam with a volume of 15.000 tonnes. Document2 27 May 2004 49

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

MANUAL – FREIGHT TRANSPORT DEMAND<br />

Transit flows<br />

Data about transit in seaports is available for ports in Belgium, the Netherlands and Germany,<br />

for ports in other countries no data is available for transit. There are some problems with this<br />

data (intra­EU transit is not included in the Belgium data, transit through the Netherlands is not<br />

collected anymore for the year 2000), but these gaps can be filled by applying estimation<br />

procedures in order to construct a complete and consistent transit database. This data has the<br />

following format:<br />

· Origin country (for instance Southern America)<br />

· Transhipment port (for instance Hamburg in Germany)<br />

· Destination country (for instance Austria)<br />

· Mode before transhipment (for instance sea transport)<br />

· Mode after transhipment (for instance road transport)<br />

· Commodity type (according to the NSTR2 or NSTR1 classification)<br />

· Volume of the goods (weight in tonnes)<br />

These transit flows have to included in the O/D matrix in such a way that double countings are<br />

avoided. This is done in three steps:<br />

1. Match transit flows with international trade flows;<br />

2. Make corrections for confusion between trade and transport flows;<br />

3. Add remaining transit flows.<br />

Match transit flows with international trade flows<br />

In the first step the transit flows through ports in Belgium, the Netherlands and Germany are<br />

matched with the international trade flows in the modified Comext database resulting from<br />

method 1.<br />

An example how these flows are matched is given in table 6.4.<br />

Table 6.4<br />

Origin<br />

region<br />

Mode<br />

origin<br />

Matching transit flows with international trade flows<br />

Transh.<br />

region<br />

Mode Transh. region Mode<br />

destination<br />

Destination<br />

region<br />

Volume<br />

(tonnes)<br />

Flow type<br />

USA sea Germany 25000 International<br />

USA sea Rotterdam<br />

(NL)<br />

rail Germany 15000 Transit<br />

In the Comext database it is known that 25.000 tonnes of a specific commodity is transported<br />

from the USA to Germany with mode sea (for extra­EU trade the mode of transport at the<br />

border of the Community). From the transit data it is known that 15.000 tonnes of a specific<br />

commodity is transported by sea from the USA to Rotterdam where the goods are transhipped<br />

onto mode rail and then transported to Germany. In this example all transit can be matched with<br />

the international trade, in the O/D matrix the international trade will be reduced by the transit<br />

flows (25.000 – 15.000 = 10.000 tonnes) and a record will be added to the O/D matrix for the<br />

transit through Rotterdam with a volume of 15.000 tonnes.<br />

Document2<br />

27 May 2004<br />

49

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

Saved successfully!

Ooh no, something went wrong!