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 region Ruhrgebiet in Germany. The goods are characterised by commodity group and characteristics such as manifestation, conditioned, hazardous and/or unitised. The volume of the goods is expressed in tonnes, value, tonnekilometres, number of vehicles/vessels, vehicle/vesselkilometres, number of TEUs and TEUkilometres. Because part of the information is estimated, on this level of detail the results should be interpreted in a proper way by transport experts. As the data is aggregated to a less detailed level, the results become more reliable and can be easier understand and interpreted. Detailed data can only be interpreted in the proper way by transport experts, in order to avoid problems with the interpretation of the results common users should only get access to aggregated OD data. The most detailed OD data can only be used by experts who are trained on the specific characteristics of the database. Developing a training program after the project might be an option. More aggregate submatrices will be developed for the final product that are easier to understand and interpreted by a broader audience. 66 Document2 27 May 2004
D5 Annex WP 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL – FREIGHT TRANSPORT DEMAND 7 OBSERVATIONS UP TO PHASE 2 7.1 Introduction This chapter describes the observations up to phase 2 of ETIS reference database on legal aspects and organisational aspects. These descriptions will be extended along the course of the project based on experiences. 7.2 Legal aspects and organisational aspects EUROSTAT has provided data to ETIS free of charge for use within the project. No arrangements have been made yet on future use of the data by third parties outside the Commission. For now the data have to be considered restricted. Some data available at EUROSTAT (for instance international interregional road transport data) cannot be provided due to the statistical law or because of confidentiality reasons. For other data available at EUROSTAT (for instance the porttoport data) a license has to be signed in which it is expressed that the data will only be used in this project. The conditions of data delivery from national statistical offices also differ from country to country. For some countries the data can be downloaded from the internet without any restrictions (for instance trade data of Spain), the only restriction is that the statistical office should be mentioned as source (for instance transport data in the Netherlands), a price has to be paid and a contract has to be signed for restricted use (for instance transport data in Germany) or in addition an official letter from the European Commission is required (for instance transport data France). As has also been discussed at the second open conference of ETIS it is recommended that a discussion is opened on how this data collected can be streamlined in the future as a follow up of the current ETIS projects. Should this be done through EUROSTAT or is a less formalised approach more appropriate. In any case it should be attempted to come to long lasting agreements on data delivery to avoid time consuming data collection procedures. 7.3 Other remarks It has been observed in chapter 6 that the resulting OD matrix is very detailed which requires caution in its use. In case the most detailed level is used the reliability of the figures is in some cases relatively low due to the fact that some elements have been estimated. The user therefore has to be guided. One option is to provide only submatrices that do not contain all the variables in one matrix, to be used by the common users. The complete matrix can be used by expert users only which need to be trained to make the proper selections and interpretations. Document2 27 May 2004 67
- Page 16 and 17: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 19 and 20: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 21 and 22: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 23 and 24: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 25 and 26: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 27 and 28: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 29: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 32 and 33: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 34 and 35: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 36 and 37: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 38 and 39: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 40 and 41: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 43 and 44: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 45 and 46: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 47 and 48: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 49 and 50: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 51 and 52: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 53 and 54: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 55 and 56: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 57 and 58: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 59 and 60: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 61 and 62: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 63 and 64: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 65: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 71 and 72: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 73 and 74: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 75: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 79 and 80: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 81 and 82: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 83 and 84: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 85 and 86: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 87 and 88: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 89 and 90: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 91 and 92: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 93 and 94: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 95 and 96: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 97 and 98: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 99 and 100: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 101 and 102: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 103 and 104: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 105 and 106: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 107 and 108: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 109 and 110: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 111 and 112: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 113 and 114: D5 Annex WP 3: DATABASE METHODOLOGY
- Page 115 and 116: D5 Annex WP 3: DATABASE METHODOLOGY
<strong>D5</strong> <strong>Annex</strong> <strong>WP</strong> 3: DATABASE METHODOLOGY AND DATABASE USER MANUAL –<br />
FREIGHT TRANSPORT DEMAND<br />
region Ruhrgebiet in Germany. The goods are characterised by commodity group and<br />
characteristics such as manifestation, conditioned, hazardous and/or unitised. The volume of the<br />
goods is expressed in tonnes, value, tonnekilometres, number of vehicles/vessels,<br />
vehicle/vesselkilometres, number of TEUs and TEUkilometres. Because part of the<br />
information is estimated, on this level of detail the results should be interpreted in a proper way<br />
by transport experts. As the data is aggregated to a less detailed level, the results become more<br />
reliable and can be easier understand and interpreted.<br />
Detailed data can only be interpreted in the proper way by transport experts, in order to avoid<br />
problems with the interpretation of the results common users should only get access to<br />
aggregated OD data.<br />
The most detailed OD data can only be used by experts who are trained on the specific<br />
characteristics of the database. Developing a training program after the project might be an<br />
option. More aggregate submatrices will be developed for the final product that are easier to<br />
understand and interpreted by a broader audience.<br />
66<br />
Document2<br />
27 May 2004