diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000000000000000000000000000000000000..2963614f85dc27f8623aa8c1a5d72698d753f3c3
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,8 @@
+.Rproj.user
+.Rhistory
+.RData
+.Ruserdata
+schema-sh-geojson-test.Rproj
+create_schema_def.R
+create_a_valid_schema.R
+create_Schema.py
\ No newline at end of file
diff --git a/4_valid_examples.csv b/4_valid_examples.csv
new file mode 100644
index 0000000000000000000000000000000000000000..ee43c92a94b9cb93f29bcf8d5939670a7c0e7f94
--- /dev/null
+++ b/4_valid_examples.csv
@@ -0,0 +1,6 @@
+Kreis Gemeinde Anlage Leistung Nabenhöhe Rotordurchmesser AN_RW AN_HW Status
+Ostholstein Schönwalde am Bungsberg 0001 - 1 WKA Siemens SWT.3.0-113 - 3,0 MW 3000 kW Nennleist. Rotor. 92,5 113 32616585 6005019 vor Inbetriebnahme
+Kiel Kiel 0001 - WKA 1 Nordex N131 3000 kW Nennleist. Rotor. 134 131 32571605 6013660 im Gen.Verf.
+Dithmarschen Albersdorf 0006 - WKA 6 Vestas V 112 3.3 MW G10/2014/016 3300 kW Nennleist. Rotor. 94 112 32516771 5998370 in Betrieb
+Dithmarschen Friedrichskoog 0006 - WKA 6 G10/2017/024 Enercon E92 TES 2350 kW Nennleist. Rotor. 103,9 92 32495906 5985254 im Gen.Verf.
+Dithmarschen Wöhrden 0002 - WKA Nordex N131/3600 3600 kW Nennleist. Rotor. 32496854 6001866 im Gen.Verf.
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000000000000000000000000000000000000..7247b0b27faf32607cd43309a6792384037e2bb1
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,7 @@
+# Changelog Schema SH GeoJSON Test
+
+
+## 0.1.0 (2024-04-03)
+
+### initial table-schema, readme & changelog
+- frictionless table schema and csv examples with geojson objects
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000000000000000000000000000000000000..70d24dd1037450158a7fa2cf2d3bf0e97b0f0fb7
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,40 @@
+DL-DE->BY-2.0
+Datenlizenz Deutschland – Namensnennung – Version 2.0
+(1) Jede Nutzung ist unter den Bedingungen dieser „Datenlizenz Deutschland – Namensnennung – Version 2.0" zulässig.
+
+Die bereitgestellten Daten und Metadaten dürfen für die kommerzielle und nicht kommerzielle Nutzung insbesondere
+
+vervielfältigt, ausgedruckt, präsentiert, verändert, bearbeitet sowie an Dritte übermittelt werden;
+mit eigenen Daten und Daten Anderer zusammengeführt und zu selbständigen neuen Datensätzen verbunden werden;
+in interne und externe Geschäftsprozesse, Produkte und Anwendungen in öffentlichen und nicht öffentlichen elektronischen Netzwerken eingebunden werden.
+(2) Bei der Nutzung ist sicherzustellen, dass folgende Angaben als Quellenvermerk enthalten sind:
+
+Bezeichnung des Bereitstellers nach dessen Maßgabe,
+der Vermerk „Datenlizenz Deutschland – Namensnennung – Version 2.0" oder „dl-de/by-2-0" mit Verweis auf den Lizenztext unter www.govdata.de/dl-de/by-2-0 sowie
+einen Verweis auf den Datensatz (URI).
+Dies gilt nur soweit die datenhaltende Stelle die Angaben 1. bis 3. zum Quellenvermerk bereitstellt.
+
+(3) Veränderungen, Bearbeitungen, neue Gestaltungen oder sonstige Abwandlungen sind im Quellenvermerk mit dem Hinweis zu versehen, dass die Daten geändert wurden.
+
+
+
+Data licence Germany – attribution – version 2.0
+(1) Any use will be permitted provided it fulfils the requirements of this "Data licence Germany – attribution – Version 2.0".
+
+The data and meta-data provided may, for commercial and non-commercial use, in particular
+
+be copied, printed, presented, altered, processed and transmitted to third parties;
+be merged with own data and with the data of others and be combined to form new and independent datasets;
+be integrated in internal and external business processes, products and applications in public and non-public electronic networks.
+(2) The user must ensure that the source note contains the following information:
+
+the name of the provider,
+the annotation "Data licence Germany – attribution – Version 2.0" or "dl-de/by-2-0" referring to the licence text available at www.govdata.de/dl-de/by-2-0, and
+a reference to the dataset (URI).
+This applies only if the entity keeping the data provides the pieces of information 1-3 for the source note.
+
+(3) Changes, editing, new designs or other amendments must be marked as such in the source note.
+
+
+
+URL: http://www.govdata.de/dl-de/by-2-0
diff --git a/README.md b/README.md
index bb68a4bae13b933133d7af716d6d5726d93b6f63..ecdea84d07b894d86ed2957c5354311b6b57d7cd 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,46 @@
# schema-sh-geojson-test
+# Test Tabellen Schema mit geojson Objekten (exemplarisches Schema)
-## Getting started
+Dieses Schema ermöglicht es, Daten gemäß frictionlessdata Table Schema Spezifikation mit geojson Objekten gemäß GeoJSON oder TopoJSON Spezifikation zu beschreiben. Mit diesem Schema soll erprobt werden, ob derart Felder bis zu TP3 (Validata) geprüft und in wie weit Geo-Typen berücksichtigt werden. Außerdem werden Beispiel .csv Dateien mit korrekter als auch falscher Formatierung erstellt, um diese in TP3 testen zu können.
+....
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+## Hinweise zur Veröffentlichung der Winddaten Schleswig-Holstein
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+...
-## Add your files
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+## Rechtliche Rahmenbedingungen
-```
-cd existing_repo
-git remote add origin https://code.schleswig-holstein.de/dollinja/schema-sh-geojson-test.git
-git branch -M main
-git push -uf origin main
-```
+_...bspw. Verweise auf Gesetzestexte, Verordnungen..._
-## Integrate with your tools
-- [ ] [Set up project integrations](https://code.schleswig-holstein.de/dollinja/schema-sh-geojson-test/-/settings/integrations)
-## Collaborate with your team
+## Zweck
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+_...Warum, Wozu, ggf. in Bezug auf Allgemeinwohl _
-## Test and Deploy
-Use the built-in continuous integration in GitLab.
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+## Datei Format
-***
+_... bspw.:
+Die Datei muss in UTF-8 kodiert sein. Der Spaltenkopf in der ersten Zeile ist erforderlich.
+Als Koordinatenbezugssystem (KBS bzw. CRS) wird EPSG:25832 verwendet.
-# Editing this README
+Dateiname: keine Vorgabe
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-## Suggestions for a good README
+# Übermittlung von Daten
+...
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+# Beispiel-Dateien
+ggf. Links in csv u. Excel
-## Name
-Choose a self-explaining name for your project.
+# Aktualisierungen
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+# Quellen
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+# Informationen
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
diff --git a/schema.json b/schema.json
new file mode 100644
index 0000000000000000000000000000000000000000..0f3c7bcc5f3d8f8410b61a5ded10468f5951506e
--- /dev/null
+++ b/schema.json
@@ -0,0 +1,155 @@
+{
+ "$schema": "https://specs.frictionlessdata.io/schemas/table-schema.json",
+ "name": "nitratmessdienst_schleswig-holstein",
+ "title": "Nitratmessdienst Schleswig-Holstein",
+ "description": "Daten des Nitratmessdienstes Schleswig-Holsteins basierend auf Beprobungen von Praxisflächen sowie Versuchsflächen der Landwirtschaftskammer Schleswig-Holsteins",
+ "countryCode": "DE",
+ "path": "https://opendata.schleswig-holstein.de/schema/nmd-sh.json",
+ "created": "2023-12-28",
+ "lastModified": "2024-02-26",
+ "version": "0.2.0",
+ "contributors": [
+ {
+ "title": "Dr. Jesper Zedlitz",
+ "email": "jesper.zedlitz@stk.landsh.de",
+ "organisation": "Staatskanzlei Schleswig-Holstein",
+ "role": "author"
+ }
+ ],
+ "fields": [
+ {
+ "name": "Region_ID",
+ "type": "integer"
+ },
+ {
+ "name": "Messung_ID",
+ "type": "integer"
+ },
+ {
+ "name": "NMD_ID",
+ "type": "integer",
+ "constraints": {
+ "minimum": 1,
+ "maximum": 2
+ }
+ },
+ {
+ "name": "Region",
+ "type": "string",
+ "constraints": {
+ "enum": [
+ "Marsch",
+ "Östliches Hügelland",
+ "Geest",
+ "Östliches Hügelland südlicher Teil",
+ "Östliches Hügelland nördlicher Teil",
+ "Östliches Hügelland mittlerer Teil"
+ ]
+ }
+ },
+ {
+ "name": "Datum",
+ "type": "date",
+ "format": "%d.%m.%Y"
+ },
+ {
+ "name": "Kulturart",
+ "type": "string",
+ "constraints": {
+ "enum": [
+ "Spelzweizen",
+ "Winterfutterbsen",
+ "Kleegras",
+ "Gemüse",
+ "Grassamenvermehrung",
+ "Ackergras",
+ "Winterroggen",
+ "Winterweizen",
+ "Sommerung",
+ "Zwischenfrucht",
+ "Winterraps",
+ "Wintertriticale",
+ "Wintergerste",
+ "Kohl"
+ ]
+ }
+ },
+ {
+ "name": "Vorfrucht",
+ "type": "string",
+ "constraints": {
+ "enum": [
+ "Ackerbohne",
+ "Rüben",
+ "Mais/Stangenbohnen",
+ "Grassamenvermehrung",
+ "Spelzweizen",
+ "Ackergras",
+ "Kartoffeln",
+ "Körnermais",
+ "Stangenbohnen",
+ "Zwischenfrucht",
+ "Silomais",
+ "Sommergerste",
+ "Winterroggen",
+ "Zuckerrüben",
+ "Kohl",
+ "Winterraps",
+ "Wintergerste",
+ "Wintertriticale",
+ "Winterweizen",
+ "Ackerbohnen",
+ "Hafer",
+ "Kleegras",
+ "Sommerweizen",
+ "Weizen/Erbse",
+ "Gemüse"
+ ]
+ }
+ },
+ {
+ "name": "Bodenart",
+ "type": "string",
+ "constraints": {
+ "enum": [
+ "uL",
+ "tL",
+ "S",
+ "l'S",
+ "sL",
+ "lS"
+ ]
+ }
+ },
+ {
+ "name": "Nmin [kg/ha] 0 - 30 cm",
+ "type": "integer",
+ "unit": "kg/har"
+ },
+ {
+ "name": "Nmin [kg/ha] 30 - 60 cm",
+ "type": "integer",
+ "unit": "kg/har"
+ },
+ {
+ "name": "Nmin [kg/ha] 60 - 90 cm",
+ "type": "integer",
+ "unit": "kg/har"
+ },
+ {
+ "name": "Nmin [kg/ha] 0 - 90 cm",
+ "type": "integer",
+ "unit": "kg/har"
+ },
+ {
+ "name": "Ökolandbau",
+ "type": "boolean",
+ "trueValues": [
+ "ja"
+ ],
+ "falseValues": [
+ "nein"
+ ]
+ }
+ ]
+}
\ No newline at end of file