SQL source for weather coordinates using PostGIS

.readthedocs.yaml

@@ -7,9 +7,9 @@ version: 2
 
 # Set the version of Python and other tools you might need
 build:
-  os: ubuntu-20.04
+  os: ubuntu-22.04
   tools:
-    python: "3.9"
+    python: "3.11"
 
 # Configure python
 python:
@@ -18,4 +18,5 @@ python:
 
 # Build documentation in the docs/ directory with Sphinx
 sphinx:
-  configuration: docs/readthedocs/conf.py
+  configuration: docs/readthedocs/conf.py
+  fail_on_warning: true

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 - Copy methods for container classes [#726](https://github.com/ie3-institute/PowerSystemDataModel/issues/726)
 - Allow hierarchic grid structure for JointGridContainer [#768](https://github.com/ie3-institute/PowerSystemDataModel/issues/768)
+- Adding SQL id coordinate sources (``IdCoordinateSource``) [#689](https://github.com/ie3-institute/PowerSystemDataModel/issues/689)
 
 ### Fixed
 - Fixed wrong rated power unit hint [#804](https://github.com/ie3-institute/PowerSystemDataModel/issues/804)

docs/readthedocs/conf.py

@@ -18,12 +18,12 @@
 # -- Project information -----------------------------------------------------
 
 project = 'PowerSystemDataModel'
-copyright = u'2020. TU Dortmund University, Institute of Energy Systems, Energy Efficiency and Energy Economics, Research group Distribution grid planning and operation '
+copyright = 'ie3'
 author = 'Johannes Hiry, Debopama Sen Sarma, Chris Kittl'
 
 # The full version, including alpha/beta/rc tags
-version = '1.0'
-release = '1.0.1-SNAPSHOT'
+version = '3.0.0'
+release = '4.0-SNAPSHOT'
 
 pygments_style = 'tango'
 add_function_parentheses = True
@@ -35,12 +35,12 @@
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
 # ones.
 extensions = [
-    'recommonmark',
-    'sphinx.ext.autosectionlabel'
+    'sphinx.ext.intersphinx',
+    'myst_parser'
 ]
 
-# Prefix all autogenerated labels wit the document to get unique labels (e.g. `index:Hello`)
-autosectionlabel_prefix_document = True
+myst_enable_extensions = ["dollarmath", "amsmath"]
+myst_heading_anchors = 4
 
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']
@@ -49,7 +49,8 @@
 # directories to ignore when looking for source files.
 # This pattern also affects html_static_path and html_extra_path.
 exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store', 'venv']
-
+exclude_trees = ['.build']
+source_suffix = ['.rst', '.md']
 source_encoding = 'utf-8-sig'
 
 # -- Options for HTML output -------------------------------------------------

docs/readthedocs/models/ValidationUtils.rst → docs/readthedocs/io/ValidationUtils.md

@@ -1,32 +1,26 @@
-****************
-Validation Utils
-****************
+# Validation Utils
 This page gives an overview about the ValidationUtils in the *PowerSystemDataModel*.
 
-What are the ValidationUtils?
-=============================
+## What are the ValidationUtils?
 The methods in ValidationUtils and subclasses can be used to check that objects are valid, meaning their parameters have valid values and they are correctly connected.
 
-What is checked?
-================
+## What is checked?
 - The check methods include checks that assigned values are valid, e.g. lines are not allowed to have negative lengths or the rated power factor of any unit must be between 0 and 1.
 - Furthermore, several connections are checked, e.g. that lines only connect nodes of the same voltage level or that the voltage levels indicated for the transformer sides match the voltage levels of the nodes they are connected to.
 
-How does it work?
-=================
-- The method :code:`ValidationUtils.check(Object)` is the only method that should be called by the user.
+## How does it work?
+- The method `ValidationUtils.check(Object)` is the only method that should be called by the user.
 - This check method identifies the object class and forwards it to a specific check method for the given object
 - The overall structure of the ValidationUtils methods follows a cascading scheme, orientated along the class tree
-- Example: A :code:`LineInput lineInput` should be checked
-    1. :code:`ValidationUtils.check(lineInput)` is called
-    2. :code:`ValidationUtils.check(lineInput)` identifies the class of the object as :code:`AssetInput` and calls :code:`ValidationUtils.checkAsset(lineInput)`
-    3. :code:`ValidationUtils.checkAsset(lineInput)`, if applicable, checks those parameters that all :code:`AssetInput` have in common (e.g. operation time) and further identifies the object, more specifically, as a :code:`ConnectorInput` and calls :code:`ConnectorValidationUtils.check(lineInput)`
-    4. :code:`ConnectorValidationUtils.check(lineInput)`, if applicable, checks those parameters that all :code:`ConnectorInput` have in common and further identifies the object, more specifically, as a :code:`LineInput` and calls :code:`ConnectorValidationUtils.checkLine(lineInput)`
-    5. :code:`ConnectorValidationUtils.checkLine(lineInput)` checks all specific parameters of a :code:`LineInput`
+- Example: A `LineInput lineInput` should be checked
+    1. `ValidationUtils.check(lineInput)` is called
+    2. `ValidationUtils.check(lineInput)` identifies the class of the object as `AssetInput` and calls `ValidationUtils.checkAsset(lineInput)`
+    3. `ValidationUtils.checkAsset(lineInput)`, if applicable, checks those parameters that all `AssetInput` have in common (e.g. operation time) and further identifies the object, more specifically, as a `ConnectorInput` and calls `ConnectorValidationUtils.check(lineInput)`
+    4. `ConnectorValidationUtils.check(lineInput)`, if applicable, checks those parameters that all `ConnectorInput` have in common and further identifies the object, more specifically, as a `LineInput` and calls `ConnectorValidationUtils.checkLine(lineInput)`
+    5. `ConnectorValidationUtils.checkLine(lineInput)` checks all specific parameters of a `LineInput`
 - ValidationUtils furthermore contains several utils methods used in the subclasses
 
-Which objects are checked?
-==========================
+## Which objects are checked?
 The ValidationUtils include validation checks for...
 
 - NodeValidationUtils
@@ -80,8 +74,7 @@ The ValidationUtils include validation checks for...
     - RawGridElements
     - SystemParticipants
 
-What should be considered?
-==========================
+## What should be considered?
 - Due to many checks with if-conditions, the usage of the ValidationUtils for many objects might be runtime relevant.
 - The check for a GridContainer includes the interplay of the contained entities as well as the checks of all contained entities.
 - If new classes are introduced to the *PowerSystemDataModel*, make sure to follow the forwarding structure of the ValidationUtils methods when writing the check methods!

docs/readthedocs/io/basiciousage.rst

@@ -8,9 +8,10 @@ Therefore, the I/O-package is structured as highly modular.
 .. toctree::
    :maxdepth: 2
 
-   influxdb
    csvfiles
-
+   sql
+   influxdb
+   ValidationUtils.md
 
 
 Data sink structure