a Competence Centre of
Direct access
to database


ecoinvent v3

EcoSpold v2 Data Format

You can now download a beta-version (beta 4) of the ecoSpold format version 2 which is designed to replace the current ecoSpold format for the next version of the ecoinvent database, scheduled for release in 2011. This fourth beta version has been tested and is currently used in our own software development. It includes a conversion tool to convert ecoSpold1 files to ecoSpold2 files.

The beta 4 of the ecoSpold 2 format is used in the ecoEditor2 software that is intended for creating and editing datasets for the ecoinvent database version 3. The ecoEditor 2 software is currently tested in a beta version and will, together with the final version of the ecoSpold 2 format be released in spring 2010. Until then, we welcome comments from users and software developers (mail: support(at)ecoinvent.org).

    
The open source ecoSpold data format v1 (ecoSpold v1) was launched in 2000 and is today the most widely used data exchange format for LCI data. The ecoinvent Centre was the first to use this data format for their own LCI database. Other databases adopted the format, and all important LCA software tools have an interface to use datasets in ecoSpold format.

However, both LCA and LCA software have developed since the release of ecoSpold v1, and to take advantage of all the new developments, a revision of the ecoSpold format has become necessary. An ad hoc expert working group was formed by ecoinvent to guide the revision process, and an open hearing has been conducted among users of the ecoSpold format, in order to collect their input and wishes for a new ecoSpold format v2. The result of this hearing and the way the input has been treated can be seen in a public report.

The changes from ecoSpold v1 to v2 can be summarised under the following headings:

(1) Structural change:

In ecoSpold v1 the three types of datasets (elementary flow, process, and impact category) were all handled within the same dataset structure. In ecoSpold v2, separate dataset definitions are applied for these three. "Process" will be called "Activity". "Elementary flows" will be called "Exchanges with environment". There will be master lists for allowed “Elementary flows" as well as for "Products and Wastes" and "Locations". The references to entries in these master lists will be made through UUIDs. Note: The impact category dataset definition has not yet been fully determined, and will be tackled by the working group at a later stage in the format development.

(2) Facilitating database maintenance and extension:

  • Option for parent-child relationships between activity datasets
  • Option for expressing geographical information using GIS coordinates
  • Option to use formulas and variables in numerical fields
  • Use of UUIDs for internal references in datasets
  • New field to declare macro-economic scenario for forecasted activities

(3) Better support for alternative modelling options and data exchange with the ILCD format:

  • Option to declare the market model (attributional, consequential) used for an activity
  • The direct linking of an activity (process) name and single product output name has become obsolete.
  • Reduction of the number of required fields
  • New field to declare technology level for activities (new, modern, current, old, outdated)
  • New field to declare an activity as a market activity
  • Addition of joker elements to enable simpler extension of the format

(4) Support for mass balances, energy balances and monetary balances:

  • The category/subcategory concept for processes/activities has been dropped. Instead, options have been introduced to declare multiple classification schemes, tags, and multiple properties of exchanges, e.g. price, dry mass, water content, energy content, elementary or substance composition
  • New field to declare annual production volume
  • New output type: “addition to capital goods”
  • New field to declare product transfer coefficients (outputs relative to inputs)

(5) Support for language versions:

  • Option to add language versions for all text fields

(6) Support for better documentation:

  • Option to add images
  • Option to add more than one validator
  • Fields for uncertainty information made more general and adding numerical fields for the pedigree matrix