Repository navigation
data: re-deliver BAFU-2026 inventory with unit-keyed flow ids - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
On 2026-09-02 the biosphere flow id scheme in sentier-importers changed (PR #13): the unit joined the uuid5 hash, so ids are now
uuid5(name|category|subcategory|unit)instead ofuuid5(name|category|subcategory|""). sentier-vocab (#33) and sentier-mappings were re-minted with the new scheme, but the payload in this repo was still the 2026-08-07 generation. As a result, 0 of 2,515 distinct biosphere flow ids in the inventory matched any source code in thebafu-2026-v1__ef-3.1bridge in sentier-mappings, so no biosphere exchange could be resolved to an EF 3.1 flow.How it was regenerated
Regenerated from sentier-importers at
f14d448using the 22 registry sourcesbafu-<sector>-processesandbafu-<sector>-exchangesfor the 11 sectors (01-agriculture through 10-building-services plus 99-obsolete), processes before exchanges for each sector, delivered into this checkout with:No changes were made to the importer. Only the 11
exchanges.parquetfiles differ; everyprocesses.parquetandmetadata.jsoncame out byte-identical tomain(the source citation in each metadata description is intact).Verification
exchanges.parquetversus source codes insentier-mappings/data/bafu-2026-v1__ef-3.1/biosphere-*.json: before 0 / 2,515, after 2,558 / 2,679. The distinct count rose because flows that share name and category but differ in unit now receive separate ids, which is the purpose of the re-mint. The 121 remaining unmatched ids are flows the EF 3.1 bridge does not cover at all (noise, Thorium-232, gross calorific energy in biomass, ocean salt water, Uranium alpha, and similar), affecting 2.96% of biosphere exchange rows.process_idin the newprocesses.parquetis identical tomain, and row counts and column sets ofexchanges.parquetare unchanged. The only column that differs isflow; 100% of biosphere rows were re-keyed and 0 technosphere rows changed, so technosphere links are untouched.scripts/validate.py(the CI schema gate) passes locally:OK, 11 sector folder(s) validate against the schema contracts.07-construction/exchanges.parquet, 1,525,244 to 1,530,528 bytes); several files shrank slightly. No sharding needed.🤖 Generated with Claude Code