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
D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND 4 THE FREIGHT OD DATA MODEL 4.1 Introduction In this chapter the proposed freight OD transport chain data model is described. The exact structure of the type of model to be used is depending on the specific structure of the available data. For this reason not all details but merely the basic principles and available tools will be discussed. The exact model in full detail will be developed along the construction process in the remaining of the project. Some results obtained in the testing phase are already described in chapter 6. 4.2 General structure The general structure of this model to be used can be split up into the following parts: 1. Combining trade/transport/transhipment data sources 2. Estimating data gaps 3. Adding information to the OD matrix In the first part all available trade and transport data sources are being combined into one database by a topdown approach. This approach will have the same structure as the NEAC database construction model. It might be the case that some regional information is missing in transport or trade data or that no data are available at all for a specific geographical area. In this case estimation methods are required that can estimate data by modelling. Next procedures will be applied to add information to the OD matrix. Container information, cargo type information and characteristics on the OD flows will be estimated. Also estimation procedures will be applied for the translation from tonnes to vehicles/vessels and if possible by type, translating containerised tonnes into TEUs. Finally all this information will be used to determine transport performance information (tonnekm, vehiclekm/vesselkm and TEUkm). This will be described in more detail in the following sections. 4.3 Combining trade/transport/transhipment data sources The first step in the topdown approach is to combine all collected trade/transport sources into one database. Here we use the trade data as the foundation of the whole database and refine this with information that can be found in the transport and transhipment data sources. In the INFOSTAT project a pilot database has been constructed with the topdown approach. As described in paragraph 6.4 there are some restrictions on data combinations. In INFOSTAT a database with two transhipment points has been constructed. A conclusion was that for all elements of the chain, data should be available to ensure quality of the results. Up to this point two transhipment points in the chain structure by combining sources seems to be the limit on the level of detail. Document2 27 May 2004 19
- Page 1: D5 Annex report WP 3: ETIS Databa
- Page 4 and 5: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 7: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 10 and 11: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 12 and 13: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 14 and 15: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 16 and 17: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 20 and 21: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 22 and 23: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 24 and 25: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 26 and 27: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 28 and 29: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 31 and 32: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 33 and 34: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 35 and 36: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 37 and 38: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 39 and 40: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 41: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 44 and 45: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 46 and 47: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 48 and 49: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 50 and 51: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 52 and 53: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 54 and 55: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 56 and 57: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 58 and 59: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 60 and 61: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 62 and 63: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 64 and 65: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 66 and 67: D5 Annex WP 3: DATABASE METHODOLOGY
<strong>D5</strong> <strong>Annex</strong> <strong>WP</strong> 3: DATABASE METHODOLOGY AND DATABASE USER<br />
MANUAL – FREIGHT TRANSPORT DEMAND<br />
4 THE FREIGHT OD DATA MODEL<br />
4.1 Introduction<br />
In this chapter the proposed freight OD transport chain data model is described. The exact<br />
structure of the type of model to be used is depending on the specific structure of the available<br />
data. For this reason not all details but merely the basic principles and available tools will be<br />
discussed. The exact model in full detail will be developed along the construction process in the<br />
remaining of the project. Some results obtained in the testing phase are already described in<br />
chapter 6.<br />
4.2 General structure<br />
The general structure of this model to be used can be split up into the following parts:<br />
1. Combining trade/transport/transhipment data sources<br />
2. Estimating data gaps<br />
3. Adding information to the OD matrix<br />
In the first part all available trade and transport data sources are being combined into one<br />
database by a topdown approach. This approach will have the same structure as the NEAC<br />
database construction model. It might be the case that some regional information is missing in<br />
transport or trade data or that no data are available at all for a specific geographical area. In this<br />
case estimation methods are required that can estimate data by modelling. Next procedures will<br />
be applied to add information to the OD matrix. Container information, cargo type information<br />
and characteristics on the OD flows will be estimated. Also estimation procedures will be<br />
applied for the translation from tonnes to vehicles/vessels and if possible by type, translating<br />
containerised tonnes into TEUs. Finally all this information will be used to determine transport<br />
performance information (tonnekm, vehiclekm/vesselkm and TEUkm). This will be described<br />
in more detail in the following sections.<br />
4.3 Combining trade/transport/transhipment data sources<br />
The first step in the topdown approach is to combine all collected trade/transport sources into<br />
one database. Here we use the trade data as the foundation of the whole database and refine this<br />
with information that can be found in the transport and transhipment data sources. In the<br />
INFOSTAT project a pilot database has been constructed with the topdown approach. As<br />
described in paragraph 6.4 there are some restrictions on data combinations. In INFOSTAT a<br />
database with two transhipment points has been constructed. A conclusion was that for all<br />
elements of the chain, data should be available to ensure quality of the results.<br />
Up to this point two transhipment points in the chain structure by combining sources seems to<br />
be the limit on the level of detail.<br />
Document2<br />
27 May 2004<br />
19