Lead-210
b5bffb1f-1e13-56b7-a45f-eb5c262078e4
agribalyse 3.2
prepared- Name
- Lead-210
- Context
- Emissions to water
- Unit
- kg
- CAS
- 14255-04-0
- EC
- —
- Method
- prepared
- Substance
- fo-35dfc4c164eb199e
- Target flow
- 4d9a8790-3ddd-11dd-9812-0050c2490048
Everything this outcome recorded
{
"source_uuid": "b5bffb1f-1e13-56b7-a45f-eb5c262078e4",
"source_name": "Lead-210",
"source_context": [
"Emissions to water"
],
"source_context_iri": "https://vocab.brightway.one/flow-contexts/envi-wate-unkn",
"source_unit": "kg",
"source_cas": "14255-04-0",
"target_elementary_flow_id": "4d9a8790-3ddd-11dd-9812-0050c2490048",
"prepared_target_elementary_flow_id": "4d9a8790-3ddd-11dd-9812-0050c2490048",
"target_flow_object_id": "fo-35dfc4c164eb199e",
"target_name": "Lead-210",
"target_context": [
"Environmental",
"Water",
"Unknown"
],
"target_unit": "kBq",
"prepared_target_resolution": "direct-active-target",
"prepared_target_trace": [
"4d9a8790-3ddd-11dd-9812-0050c2490048"
],
"prepared_context_decision": "mapped",
"provenance": {
"prov:wasGeneratedBy": "merge_agribalyse",
"prov:wasAttributedTo": "brightway-flows",
"prov:hadPrimarySource": [
"agribalyse:3.2:b5bffb1f-1e13-56b7-a45f-eb5c262078e4",
"Lead-210",
""
],
"prov:wasDerivedFrom": "randonneur_replace_table:prepared_mapping"
},
"conversion_factor": 2840000000000.0,
"conversion_comment": "`Lead-210/kg`, a mass of lead-210 released to water, onto EF 3.1's `Lead-210` in kBq. A mass of a radioactive isotope converts to an activity by its specific activity, which follows from the half-life (22.2 years): 2.84e+12 Bq per gram, which is the same number of kBq per kilogram. The value is the one ChemLin gives and this list already publishes on the substance (`chemlin-isotopes.json`). AGRIBALYSE also ships `Lead-210` in kBq, which reaches the same flow without conversion; this is its mass twin, used in 13 datasets at amounts no larger than 7.5e-21 kg. On the first five-list full build (2 September 2026, `944b274`) the row reached this flow by itself with no number on the mapping, and so published its amount in the wrong unit (#370)."
}