BONSAMURAIS / BONSAMURAIS/schema
smarter locations
- Dominant language
- PLpgSQL
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Right now, entries in the location table are countries according to https://www.geonames.org/countries/. This won't do for the future. Here are two problematic examples:
1) ecoinvent RoW activities are not countries. If anything they are logical expressions of the scheme "world minus region x, y, z"
2) regional LCA can demand locations on sub-country or cross-country scale
How to deal with this? I think we need GIS. Maybe @cmutel has some advice on this based on bw_regional?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the location table and the current assumption that entries are countries from the GeoNames country list. Compare that model with the ecoinvent RoW examples and the sub-country or cross-country regional LCA requirement, then review bw_regional for relevant guidance. Done means a decided approach for representing these location types, including whether GIS is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100