first push

This commit is contained in:
2023-11-30 03:30:33 +01:00
parent 62d699db5c
commit 7cb9ce0aa8
10 changed files with 187 additions and 89 deletions

4
.gitignore vendored Normal file
View File

@@ -0,0 +1,4 @@
__pycache__/
.idea/
app/
*.log

View File

@@ -1,93 +1,7 @@
# AutoPicture V3
Dies ist die dritte Version von AutoPicture. Diese Version läuft wie AutoPicture V2 mit Python3 aber dieses mal in einem Dockercontainer. Damit vereinfacht sich die Nutzung auf den verschiedenen Betriebssystemen
# Erste Schritte
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
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:
```
cd existing_repo
git remote add origin https://gitlab.com/DasMoorhuhn/autopicture-v3.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.com/DasMoorhuhn/autopicture-v3/-/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)
- [ ] [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)
## 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)
***
# Editing this README
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
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.
## 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.
## 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.
Um AutoPicture V3 nutzen zu können muss als erstes das Script `buildForLinux.sh` oder auf Windows `buildForWindows.bat` ausgeführt werden.

25
docs/Documentation.md Normal file
View File

@@ -0,0 +1,25 @@
# HelperClass
## ExifData
Diese Klasse dient als Model für die Parameter eines Bildes. Für jedes Bild wird ein Objekt angelegt.
## ScanDir(self, logger:logging)
In dieser Klasse befinden sich die Methoden zum Scannen des temporären Bilder Pfades.
### recursiveScanDir(self, pathForScan:str)
Hiermit wird der im Parameter übergebene Ordner rekursiv nach Dateien gescannt. Die Methode gibt eine liste mit allen Bildern in diesem Verzeichnis zurück
### scanFolder
### countImages
Diese Methode gibt die Anzahl der gescannten Bilder zurück.
## getMeta()
### getMetaData(self, images:list)

1
install.py Normal file
View File

@@ -0,0 +1 @@
# TODO

4
requirements.txt Normal file
View File

@@ -0,0 +1,4 @@
pillow
python-magic
progressbar
virtualenv

10
src/exif_data.py Normal file
View File

@@ -0,0 +1,10 @@
class ExifData:
"""This is for an object that stores the data of a picture"""
def __init__(self, image_path, image_name, day, month, year, time, make) -> None:
self.path = image_path
self.name = image_name
self.day = int(day)
self.month = int(month)
self.year = int(year)
self.time = str(time)
self.make = str(make)

39
src/file_handler.py Normal file
View File

@@ -0,0 +1,39 @@
import os
import time
import shutil
import logging
from progressbar.progressbar import ProgressBar
from exif_data import ExifData
def sort_pictures(images:list, dst:str, logger:logging.Logger):
image_total = len(images)
image_counter = 0
logging_infos = []
progress_bar = ProgressBar(
maxval=image_total,
term_width=70
)
print(f"Start sorting {image_total} images\n")
progress_bar.start()
start_timer = time.process_time()
for image in images:
image:ExifData
path = os.path.join(dst, str(image.make), str(image.year), str(image.month), str(image.day))
if not os.path.exists(path): os.makedirs(path)
stat_info = os.stat(image.path)
shutil.move(src=image.path, dst=f"{path}/{image.name}")
# os.chmod(path=f"{path}/{image.name}", mode=stat_info.st_mode)
# logging_infos.append(f"Moved {image.path} -> {path}/{image.name}")
logger.info(f"Moved {image.path} -> {path}/{image.name}")
progress_bar.update(image_counter)
image_counter += 1
progress_bar.finish()
print(f"\nDone\nSorted {image_total} images in {round(start_timer, 2)} seconds")
return logging_infos

15
src/folder_handler.py Normal file
View File

@@ -0,0 +1,15 @@
import os
def scan_dir(path:str):
return next(os.walk(path))[2]
def recursive_scan_dir(path:str):
results = []
for root, folders, files in os.walk(path):
list_files = os.listdir(root)
for file in list_files:
current_file = f"{root}{os.sep}{file}"
if os.path.isfile(current_file): results.append(current_file)
return results

23
src/main.py Normal file
View File

@@ -0,0 +1,23 @@
import sys
import logging
from meta_data_handler import MetadataHandler
from file_handler import sort_pictures
from folder_handler import *
sys.path.append("../")
log_folder = "."
src = "../app/TempPic"
dst = "../app/Bilder"
logger = logging.getLogger('AutoPicture')
logger.setLevel(logging.DEBUG)
handler = logging.FileHandler(filename=f'{log_folder}/AutoPicture.log', encoding='utf-8', mode='a')
handler.setFormatter(logging.Formatter('%(asctime)s|%(levelname)s|%(name)s|:%(message)s'))
logger.addHandler(handler)
metadata_handler = MetadataHandler()
files = recursive_scan_dir("../app")
exif_data = metadata_handler.get_meta_data(images=files)
sort_pictures(images=exif_data, dst=dst, logger=logger)

63
src/meta_data_handler.py Normal file
View File

@@ -0,0 +1,63 @@
import magic
from PIL import Image
from PIL import ExifTags
from exif_data import ExifData
class MetadataHandler:
"""This class is for getting the meta data from a image or a video"""
def __init__(self) -> None:
self.__videoFormats = ["MP4", "MOV", "M4V", "MKV", "AVI", "WMV", "AVCHD", "WEBM", "MPEG"]
self.__pictureFormats = ["JPG", "JPEG", "PNG", "TIFF"]
self.__keyWords = ["DateTime", "Make"]
def __is_file_video(self, path:str):
mime = magic.Magic(mime=True)
file = mime.from_file(path)
if file.find('video') != -1: return True
else: return False
def __get_image_meta_data(self, image_path):
image_extension = str(image_path).split("/")[-1].split(".")
# TODO: Sort out videos
img = Image.open(f"{image_path}")
values = []
for tag, text in img.getexif().items():
if tag in ExifTags.TAGS:
if image_extension[1].upper() in self.__pictureFormats:
values.append(ExifTags.TAGS[tag] + "|" + str(text))
return self.__filter_date_and_make(metaTags=self.__filter_data(value=values), imagePath=image_path)
def __filter_date_and_make(self, metaTags: list, imagePath):
day = None
month = None
year = None
time = None
make = str(metaTags[1]).split("|")[1]
image_name = str(imagePath).split("/")[-1]
_date = str(metaTags[0]).split("|")
time = _date[1].split(" ")[1]
_date = _date[1].split(" ")[0].split(":")
day = _date[2]
month = _date[1]
year = _date[0]
return ExifData(image_path=imagePath, image_name=image_name, day=day, month=month, year=year, time=time, make=make)
def __filter_data(self, value):
value_return = []
for k in self.__keyWords:
for v in value:
temp = v.split("|")
if temp[0] == k:
value_return.append(v)
return value_return
def get_meta_data(self, images: list):
exif_data_list = []
for image in images:
exif_data_list.append(self.__get_image_meta_data(image_path=image))
return exif_data_list