initial commit

.gitignore

@@ -0,0 +1,26 @@
+# Byte-compiled / optimized / DLL files
+__pycache__
+
+# Distribution / packaging
+.Python
+build/
+dist/
+.idea
+*.pickle
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*egg-info/
+
+
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at **info@wisdamapp.org**.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing
+
+WISDAM welcomes your expertise and enthusiasm!
+
+If you are not a developer, there are many other possibilities that do not require programming skills to help WISDAM to evolve.
+You can also contribute by:
+* extending the manual
+* develop tutorials, presentations, and other educational materials
+* providing datasets
+* participating in discussions
+* help with outreach and onboard new contributors
+* **write grant proposals and help with other fundraising efforts**
+
+## Contribution to WISDAMcore
+The [WISDAMcore](https://github.com/WISDAMapp/WISDAMcore) package is the mathematical core behind WISDAM. 
+
+WISDAMcore is dealing with all the **direct-georeferencing - mapping - photogrammetry**.
+
+We are also seeking for contributors to that package.
+
+## Bug reporting and bug fixing
+
+You can help us **by submitting bug reports or fixing bugs** in the [WISDAM bug tracker](https://github.com/WISDAMapp/WISDAM/issues/).
+
+## New features and enhancements
+
+If you wish to contribute patches you can:
+
+1. [fork the project](https://help.github.com/forking/)
+2. make your changes
+3. commit to your repository
+4. and then [create a pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
+
+ The development team can then review your contribution and commit it upstream as appropriate.
+
+If you commit a new feature, add `[FEATURE]` to your commit message AND give a clear description of the new feature. 
+
+For large-scale changes, you should first open a [discussion topic](https://github.com/WISDAMapp/WISDAM/discussions/categories/ideas).

INSTALL.md

@@ -0,0 +1,51 @@
+# INSTALLATION
+
+## Binary and Wheels
+The latest binary and wheel can be found at https://github.com/wisdamapp/wisdam/releases/latest
+There you will find a wheel which can 
+
+### From Source
+In the `WISDAM` directory (same one where you found this file after cloning the git repo), execute:
+```
+  pip install .
+```
+
+Testing is done using **pytest** can be found in the folder *tests*.
+
+## Dependencies
+
+### Python
+WISDAM is tested and runs on **Python 3.10** and **Python 3.11**.
+
+WISDAM has currently only been tested on Windows.
+
+### Packages
+WISDAM thankfully relies only on a lot of packages. The main packages are:
+- [numpy](https://www.numpy.org)
+- [pyproj - Python interface to proj](https://pyproj4.github.io/pyproj/stable)
+- [rasterio - Easy access to geospatial raster](https://rasterio.readthedocs.io/en/stable)
+- [shapely](https://shapely.readthedocs.io/en/stable/index.html)
+- [QT6 with PySide6](https://doc.qt.io/qtforpython-6) under the GPLv3.
+- [Pillow](https://python-pillow.org/)
+- [LibRaw](https://www.libraw.org/) under the LGPLv2.1 using [rawpy](https://pypi.org/project/rawpy).
+- [pandas](https://pandas.pydata.org/)
+- [geopandas](https://geopandas.org/en/stable/)
+- [Exiftool](https://exiftool.org/) with [PyExiftool](https://github.com/sylikc/pyexiftool) as interface to EXIFTool's command line
+
+The source codes to comply with GPL for QT, PySide6 and LibRaw can be found at [dependecy source codes](https://github.com/WISDAMapp/dependency_source_codes) repository in the WISDAMapp GitHub project.
+
+## Notes on PyProj
+This packages heavily depends on pyproj CRS and Transformer.
+
+## Notes on QT6 ui-Files
+If you change the "ui"-Files you need to convert them to Python files.
+You can use the provided batch file under "scripts".
+
+## Building using PyInstaller
+If you want to compile an executable there is a workflow for PyInstaller using the provided WISDAM_pyinstaller.spec
+
+In the `WISDAM` directory (same one where you found this file after cloning the git repo), execute:
+
+```pyinstaller WISDAM_pyinstaller.spec```
+
+You need to install PyInstaller beforehand.