Dies ist eine Sammlung von Skripten zum Beispiel der Integration von Geodaten anhand der [AREG API](https://chat.gdi-sh.de/aregapi) des LVermGeo SH. Die hier als Beispiel integrierten Geodaten sind Schuldaten des Bildungsministeriums, aus dem OpenData Portal.
Mithilfe von diesen Skripten können Daten in einer Datenbank ahnand ihrer bestehenden Adresse die entsprechende AREG URI sowie weitere Adress-Attribute aus dem AREG ("Normregisters für Adressen") zugeordnet werden.
Für mehr Informationen siehe [GDI-DE WIKI](https://wiki.gdi-de.org/display/GeoKomZ/How+To+Integrieren+mit+Adressen).
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Um die Skripte einsetzen zu können, müssen sie heruntergeladen oder geklont werden.
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)!
Auserdem muss Python inklusive der folgenden Pakete installiert sein:
-[ ] [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:
-[ ] [Set up project integrations](https://code.schleswig-holstein.de/maximilian.loch/adressen-integration/-/settings/integrations)
## Collaborate with your team
-[ ] [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)
-[ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## 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)
## Konfigurationsdatei
***
Damit die Skripte mit beliebigen Daten verwendet werden können, wird eine Konfigurationsdatei eingesetzt, in welcher die Verbindungsinformationen für die Datenbank eingetragen werden.
# Editing this README
Als Beispiel wird in diesem Repository die Konfigurationsdatei `example_conn.cfg` bereitgestellt. Diese Datei muss angepasst und umbennant werden.
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!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
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.
## Name
Choose a self-explaining name for your project.
## 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.
```conf
[connection]
host=IPAdressedesHosts
port=Port
dbname=DatenbankName
user=Username
pwd=Passwort
```
## 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.
In der Beispieldatei müssen die Platzhalter mit den jeweiligen Informationen ausgetauscht werden. Anschließend muss die Dateiname zu `db_conn.cfg` umbenannt werden, damit sie vom Python Skript erkannt wird.
## 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.
## Nutzung
## 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.
Nach den Änderungen können die Skripte eingesetzt werden.
## 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.
```bash
$ python geocoder_script.py
$ python adressen_update_script.py
```
## 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.
Die Skripte geben nach erfolgreichen Durchlauf Informationen in der Kommandozeile aus. Für das Geocodieren der Adressen ist das eine Statistik über die Erfolgsrate über die Geocodierung.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
Dies ist ein Beispiel für die Statistik nach dem Geocoding:
## 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.
statistics:
823 from 1025 geocoded >> 80.29%
30 features with missing attributes
172 features with errors
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.
geocoding dataset finished, closing programm
```
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## Lizenz
## License
For open source projects, say how it is licensed.
Die Lizenz für die Skripte ist die [GNU General Public License v3 (GPL-3)](https://www.gnu.org/licenses/gpl-3.0.en.html).
## 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.
