open-MaStR icon indicating copy to clipboard operation
open-MaStR copied to clipboard

A collaborative software to download the energy database Marktstammdatenregister (MaStR)

Results 34 open-MaStR issues
Sort by recently updated
recently updated
newest added

Update to newest OEMetadata standard and update hardcoded information. Merge [create.py](https://github.com/OpenEnergyPlatform/open-MaStR/blob/production/open_mastr/soap_api/metadata/create.py) and [mastr_datapackage](https://github.com/OpenEnergyPlatform/open-MaStR/blob/production/open_mastr/soap_api/metadata/mastr_datapackage.json) open tasks: - [x] merge current dev into branch - [ ] update to [oemetadata v15 ](https://github.com/OpenEnergyPlatform/oemetadata/blob/develop/metadata/v152/template.json)...

Closes #382

:rocket: feature

For the [test-pypi-publish.yml](https://github.com/OpenEnergyPlatform/open-MaStR/blob/production/.github/workflows/test-pypi-publish.yml) we should make the version dynamic if possible. The idea is that it takes the version from `setup.py` and appends the current timestamp for example.

:rocket: feature

The links to license, contributing and citation in the readme work via markdown referencing. On [PyPI](https://pypi.org/project/open-mastr/#description), however, this won't work, e.g. the link to the license yields: https://pypi.org/project/open-mastr/LICENSE.txt/

:bug: bug

I get a key error when I download with bulk from scratch while parsing ``` Table 'hydro_extended' is filled with data 'einheitenwasser' from the bulk download. File 'EinheitenWasser.xml' is parsed....

:bug: bug

Similar to [CODE_OF_CONDUCT from oeo](https://github.com/OpenEnergyPlatform/ontology/blob/dev/CODE_OF_CONDUCT.md) However we have to adapt this text a little bit. For example, we need a contact person in the "Enforcement" Section.

The upload of the raw data into the OEP is not implemented yet. The basics are already there: https://github.com/OpenEnergyPlatform/open-MaStR/blob/master/import-api/sessions.py#L75-L103

:rocket: feature
:open_hands: help wanted

We need to tidy up the postprocessing folder. Then we need to define how a postprocessing notebook has to look like. Especially a criterion for - [ ] ~name of...

:scissors: post processing