Requirements
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Tranquilla
- Stack tecnologico
- python
- Ambito
- build-system, data-engineering
Direzione di ricerca
No files, tests, or entry points are named. Start by reviewing the requirements in this issue alongside the repository structure and existing workflow description. The issue is complete only when the inputs, outputs, methodology, validation approach, and configuration options have been turned into an agreed, implementable architecture.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Hello!
I'm adding an issue to summarize the ideas on the architecture to facilitate coordination.
This issue is meant to collect feedback on the (a) inputs, (b) outputs, (c) methodology and (d) configuration options.
Feel free to comment and integrate relevant points into this message: the list can ideally be updated to track all relevant ideas that appear.
Motivation: validated grid data for power-system models using open data
Inputs
- Open Street Map data [main requirement for minimum viable product]
- the architecture shall support additional custom data with standard data format
Outputs
- Substations
- Lines
- Cables
- Converters/Transformers
- Their graph representation (basically substation ids for lines/cables)
- Electrical parameters as appropriate (Line types / impedance values)
- Rated power capacity
- Optionally visual representations of the resulting network
- While we start with HV lines, we can consider a modular architecture to support LV/MV in the future
Methodology
We agree on the conceptual steps of the model
- download data
- cleaning/harmonizing the raw data
- building the graph-representation of the network
- validation of the result: estimating error-metrics against known datasets and track changes in results over time.
pypsa-earth-status (name could be revised) can support on the validation
Options
- Regional scope: it shall be global as well as regional
- Line Types shall optionally change by region
- The cleaning steps must contain multiple heuristics, that can be optionally used for cleaning
- The building step shall require heuristics on how to merge the entries (e.g. using substation geometries, spatial tolerance, relations, etc)
Looking forward to hear your opinion!
I give permission to all maintainers to edit this message to track all relevant information that may follow in the discussion.
- Lingua principale
- Python
- Stelle
- 6
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
stephrobert/dsoxlab#238 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
sublimehq/package_control#1780 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
nwg-piotr/nwg-displays#145 ·