mario.parse_exiobase#

mario.parse_exiobase(table: str, unit: str, path: str, model: str = 'Database', name: str = None, year: int = None, calc_all: bool = False, download: bool = False, **kwargs)#

Dispatch to the appropriate EXIOBASE parser.

Parameters:

  • table (str) – acceptable values are “IOT” or “SUT”

  • unit (str) – Acceptable values are “Hybrid” or “Monetary”

  • path (str) – path to folder/file of the database (varies by the type of database) When download=True, this becomes the local download/cache directory where MARIO stores the EXIOBASE files before parsing them.

  • calc_all (boolean) – if True, by default will calculate z,v,e after parsing

  • download (boolean, Optional) – when True, download the requested EXIOBASE package into path and then parse it locally. Monetary downloads require year.

  • year (int, Optional) – optional to the Database (just for recoding the metadata)

  • name (str, Optional) – optional but suggested. is useful for visualization and metadata.

  • **kwargs (dict) –

    all the specific configuation of single exiobase parsers (please refer to the separate function documentations for more information). For hybrid EXIOBASE, the most relevant parser-specific argument is extensions=...:

    • HSUT valid options are "all", resource, Land, Emiss, Emis_unreg_w, Unreg_w, waste_sup, waste_use, pack_sup_waste, pack_use_waste, mach_sup_waste, mach_use_waste, stock_addition, and crop_res;

    • HIOT valid options are "all", resource, Land, Emiss, Emis_unreg_w, waste_sup, waste_use, pack_sup_waste, pack_use_waste, mach_sup_waste, mach_use_waste, stock_addition, and crop_res.

Returns:

returns a mario.Database according to the type of exiobase database specified

Return type:

mario.Database

Raises:

WrongInput – if non-valid values are passed to the arguments.

On this page