New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata: Support reading GPS information from xmp #4106
Comments
Thank you for your feedback! We do not yet read GPS information from xmp files. If you let digikam write the GPS information into the EXIF fields supported by PhotoPrism, Lat/Lng should be updated during the next indexing. |
Thank you for triaging my issue. I want to add some further findings:
|
Someone correct me if I'm wrong here, but wouldn't the same limitation of not reading XMP for geodata also apply to writing such data? Say I use Photoprism to assign a location to a picture that metadata would ONLY live in Photoprism right? |
@GlassedSilver Except from the image orientation PhotoPrism does not yet write metadata changes back to originals files. https://docs.photoprism.app/user-guide/library/metadata/ At this time changed geodata would live in PhotoPrism's database and the yaml export files. https://docs.photoprism.app/user-guide/backups/export/ Writing metadata back to original files (EXIF and/or xmp) is planned for the future. Improving the xmp parser is a perequisite for this: |
1. What is not working as documented?
Reading in GPS data from XMP sidecar files generally works. However, when updating (e.g., adding them for the first time) GPS information with an external program such as digikam, it will not get updated in Photoprism even after a complete re-index.
Often GPS files are added afterwards based on a GPX file because the camera itself does not have an embedded GPS tracker.
2. How can we reproduce it?
3. What behavior do you expect?
Photoprism should pick up the new GPS information and save it in its internal yml sidecar files and show the geoinformation in the UI.
4. What could be the cause of your problem?
The GPS location gets read in when first importing, but it cannot be not updated afterwards by a re-index operation.
6. Which software versions do you use?
Latest docker image with latest docker-compose example.
The text was updated successfully, but these errors were encountered: