Thumbnail for Emergy Analysis of Maize Production in Ghana

Emergy Analysis of Maize Production in Ghana

Important usage condition: Use and redistribution are governed by CC BY-SA 4.0. Review and comply with the license before using the data.
Persistent identifier
doi:10.60507/FK2/EPR96Z
Published version
1.0
Publication date
2023-09-18
License
CC BY-SA 4.0

Description

The data file entitled “Emergy analysis of maize production in Ghana” is based on an empirical study to assess the resource as well as energy use efficiency of maize production systems using the Emergy-Data Envelopment Analysis approach, which was developed within the context of the BiomassWeb Project. The study area was Bolgatanga and Bongo Districts, Ghana, sub-Saharan Africa. The approach was developed by coupling Emergy Analysis and Data Envelopment Analysis methods into a framework, and integrating the concept of eco-efficiency into the framework to assess the resource as well as energy use efficiency and sustainability of agroecosystems as a whole. In this data file, the Emergy Analysis method is applied to achieve enviromental and economic accounting of maize production systems in Ghana. The Agricultural Production Systems sIMulator (APSIM) was used to model five maize-based production scenarios as follows: 1. Extensive rainfed maize system if the external input is 0 kg/ha/yr urea, with/ without manure (Extensive0). 2. Extensive rainfed maize system if the external input is 12 kg/ha/yr NPK, with/ without manure (Extensive12). 3. Rainfed maize-legume (cowpea - Vigna unguiculata, soybean - Glycine max, or groundnut - Arachis hypogaea) intercropping system if the external input is 20 kg/ha/yr urea, with/ without manure (Intercrop20). 4. Intensive maize system if the external input is 50 kg/ha/yr urea, including supplemental irrigation (Intensive50). 5. Intensive maize system if the external input is 100 kg/ha/yr urea, including supplemental irrigation (Intensive100). The five scenarios were compared on the basis of the evaluation that was achieved using the Emergy Analysis to account for resource as well as energy use efficiency and sustainability. The data were processed using mathemathical functions in Microsoft Excel. The data file is organized in seven sheet tabs, and they are linked. Comments have been added to make the content self-explanatory. Where secondary data have been used, the sources have been cited. This data file was authored by Mwambo, Francis Molua.

Creators

Keywords

emergy analysis, maize production, environmental and economic accounting, resource use efficiency, energy use efficiency, agricultural sustainability, farming, environment

Files

Before downloading: Use and redistribution are governed by CC BY-SA 4.0. Review and comply with the license before using the data.
FileTypeBytesChecksum
metadata.xmltext/xml23023MD5 f125f03e7991c131b3d7a7fa04c4eff9
proj_BiomassWEB.pngimage/png8538MD5 e9c4a0d8be3dd540418d726da628a877
type_datasets.pngimage/png7086MD5 5414abd839cc504aac2dbdc5aeec35d0
ZEF_agr_emergy-analysis-maize-production-systems_ghana.xlsapplication/vnd.ms-excel190976MD5 79789d395bed39e115cc6153dd44ebb4

Citation

Francis Molua Mwambo, 2023-09-18, Emergy Analysis of Maize Production in Ghana, doi:10.60507/FK2/EPR96Z, V1.0

Additional Dataverse fields

Export metadata

Static metadata exports available for this published dataset version:

Complete Dataverse metadata

Expected crawler behaviour

Use a stable, truthful User-Agent with product/version and a working contact URL. Across all IP addresses and HTTP connections used by one crawler identity, allow no more than 5 requests in flight and wait at least 20 seconds between request starts. Crawl URLs listed in the catalog sitemap, including file pages and download URLs when they are published, use conditional requests, honor Retry-After, and apply exponential backoff after errors.

The welcome page may link to the interactive repository for human navigation. Automated clients must not treat that human link as a catalog crawl target.

Read the live machine-readable crawler policy before and during a crawl. Stop crawling when it reports CPU or memory utilization at or above 80% and 80% respectively.