Non-Biomass Emissions in Batch Processing¶
Non-biomass emissions calculations are integrated directly into the batch processing workflow. When enabled, the system automatically calculates non-biomass emissions (e.g., energy, fertilizers, pesticides, processing) for each plot in your collection using Life Cycle Assessment (LCA) methodology.
Overview¶
Non-biomass emissions are calculated automatically during batch processing when the non_biomass parameter is set to true in either:
- /batch_process - For plot-level batch processing
- /batch_supply_shed - For supply shed analysis
The calculations use the lca_payload structure within the input_payload parameter, which contains detailed supply chain data for accurate emissions calculations.
Supported Crop Types¶
Currently, non-biomass emissions are supported for the following crop types: - tea - timber - shrimp
If you attempt to use non_biomass=True with an unsupported crop type, the API will return an error.
Enabling Non-Biomass Emissions¶
In Batch Process¶
To enable non-biomass emissions in batch processing, set the non_biomass parameter to true:
In Batch Supply Shed¶
Similarly, for batch supply shed:
LCA Payload Structure¶
The lca_payload is a nested structure that contains detailed supply chain data. It should be provided within the input_payload parameter:
Key LCA Payload Fields¶
| Field | Type | Description |
|---|---|---|
hatchery |
object | Hatchery stage inputs (energy, chemicals, materials) |
nursery |
object | Nursery stage inputs (energy, chemicals, materials) |
farmgate |
object | Farm-level inputs (energy, feed, chemicals, materials, fertilisers, pesticides, biogenic_emissions) |
processing |
object | Processing facility inputs (energy, materials, chemicals) |
distribution |
object | Distribution inputs (transport) |
co_products |
array | Co-products with economic value allocation percentages |
country |
string | Country where production occurs |
year |
integer | Production year |
commodity_type |
string | Type of commodity (must match crop_type) |
commodity_yield |
object | Total commodity yield with value and unit |
product_fresh |
object | Fresh product quantity with value and unit |
product_finished |
object | Finished product quantity with value and unit |
product_cf |
float | Conversion factor from fresh to finished product |
production_area |
object | Production area in hectares |
Empty Lists and Default Values¶
If you provide empty lists (e.g., chemicals: [], materials: []), the system will automatically use default emission factors from the database. This ensures that all relevant emissions sources are accounted for, even if specific data is not available.
Important: Empty lists do not result in zero emissions - they trigger the use of default emission factors based on the crop type, country, and system type.
Processing Flow¶
When non_biomass=True is set:
- Input Validation: The system validates that the crop type is supported (tea, timber, or shrimp)
- LCA Payload Processing: The
lca_payloadfrominput_payloadis extracted and validated - Emissions Calculation: Non-biomass emissions are calculated for each plot using:
- User-provided inputs from the
lca_payload - Default emission factors from the database (when inputs are empty)
- Country and crop-specific emission factors
- Storage: Calculated emissions are stored alongside other batch processing results
Date Parameters¶
The date parameters used for non-biomass emissions calculations are derived from the batch process parameters:
- Start Date: Typically set to
YYYY-01-01(start of the calendar year) - End Date: Typically set to
YYYY-12-31(end of the calendar year), adjusted based on the processing month
The date parameter in batch processing represents the end date for the monitoring period (up until processing), not a cut-off date.
Response¶
Non-biomass emissions are calculated as part of the batch processing workflow. The batch process response indicates that processing has started:
Results are available once processing completes. Use the collection_id to track progress via /batch_progress and retrieve results via the Fetch API endpoints.
Example: Complete Batch Process with Non-Biomass Emissions¶
Additional Resources¶
- For detailed information on the
input_payloadstructure, see the Input Payload Documentation - For information on the core non-biomass emissions endpoint, see the Core Non-Biomass Emissions documentation
- For tracking batch processing progress, see the Batch Progress documentation