OpenEnergyPlatform / OpenEnergyPlatform/oemetadata

Add OEMetadata Module - Transportation Systems

Open
#297 1 comment 0 reactions 1 assignee View on GitHub

@carstenhoyerklick is already working on this.

Since Mar 17, 2026.

other: help wanted 🙋 part: backend 🧱 status: discussion 💬 type: feature 🛠
Dominant language
Python
Stars
26
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Description of the issue

Module - Transportation Systems (CHK)

Ideas of solution

Module - Transportation Systems (CHK)
# Key Description Example Ontology Class Badge Card.
1 moduleName The name of the module WIP Transportation Systems [0..1]
2 transportMode XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
3 meansOfTransport XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
4 transportInfrastructure XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
5 dataGenerationMethod XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
6 surveyPopulation XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
7 elementaryUnit XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
8 spatialUnit XA base year, month or day. The time for which the data should be accurate. Date Format is ISO 8601. 2020-01-01 dct:date Silver [0..1]
9 moduleDescription A description of the module. It should be usable as summary information for the module that is described by the metadata. Example table used to illustrate the OEMetadata structure and features. dct:description Silver [0..1]

Workflow checklist

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.