Input data

Data tables

Naming conventions for data tables and parameters

Note

• Parameter name and table name conventions are in place due to technical reasons of the underlying relational postgre-sql database on the OEP.

The following conventions will be automatically checked when uploading a table on the OEP, and error messages will be raised in case of violation. Users need to correct them and their compliance is mandatory.

Do's

• use ASCII characters only
• use lower case only
• use the singular instead of the plural.
• use underscores

Don'ts

• table name must not exceed maximal character limit = 50
• no points
• no commas
• no spaces
• no special characters
• avoid dates
• no hyphens. If dates are used, then without -! E.g.: 2022-10-21 will through an error. Use underscore instead!
• don't start parameter name with a number

Delimiter

Use semicolon ; as the column delimiter.

Decimal separator

Use point . as decimal separator.

SEDOS Reference Dataset (SRD) versioning

For the SRD, the following version tags apply:

• srd_range_sedos: Final SRD with ranges to include parametric uncertainty from different sources.
• srd_range_v1: Updated SRD, after project end.
• srd_point_sedos: SEDOS-specific values from srd_range_sedos that serve as a basis for all scnearios.

Datatypes

Available datatypes and corresponding formatting examples:

dtype	example	comment
json	"{""key1"": ""text"", ""key2"": ""text""}"	{"key1": "text", ...} might work as well. If you're using an table edititor make sure to use ASCII characters only
float array	[0.02, 279.5]	arrays with strings should be formatted as strings ("['string1', 'string2']"
text	"text"	String data should have text as datatype (text serves as "string")
integer	27
text array	"[""TH"", ""BW""]"	["TH","BW"] might work as well. If you're using an table edititor make sure to use ASCII characters only

Table naming

Follow the nomenclature for table and process naming in sheet: Nomenclature_Processes.

Note

• Create a new data package for each process, e.g. wind_onshore, chp, ...
  
• Or use the type column to put multiple processes in one data package
• You can use a single datapackage for both demand data and other constraint data (tech-independent parameters),e.g.:
  
  • emission limit,
    
  • natural domestic limit,
    
  • WACC

Parameter naming

Follow the nomenclature for parameter naming in sheet: Parameter_Set.

Note

• Parameter names must be linked to a concept in an ontology

It is importance that every parameter name is linked to a suitable ontological concept via the metadata to enable its clear interpretation.
In case you cannot find a suitable ontology concept (e.g. because it's not in the ontology yet), please make sure your chosen parameter name is clear and common in the domain. In this case avoid acronyms.

Ontological annotations

• In the nomenclature for parameter naming in sheet: Parameter_Set, we made suggestions for suitable ontology concepts for usage across the SEDOS APs.
  
  Please use them or make suggestions of better suitable concepts.

For more background information regarding for linking parameter names and ontology concepts, using OEM, see here.

For a practical manual linking parameter names to a suitable ontology concepts, using oemetadata builder, see here.

Parameter naming in case of missing suitable ontology concept

It is likely that not every parameter concept is already covered by an ontology. In this case, linking your parameter name to a suitable ontology concept is not directly possible.

It might, however, be indirectly possible by linking it to a distinct selection of related ontology concepts. In this case you would link your parameter name to multiple related concepts.

For a practical manual linking parameter names to multiple related ontology concepts, using oemetadata builder, see here.