-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Geo data #5
Geo data #5
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really nice, clean, commented code, and I'm really thankful that you were motivated enough to mess with this - exifs are just nightmare 😖
Some small changes and will be good to go 👍
96dba03
to
e55e22e
Compare
Should be fixed now. I added a fallback to the GeoDataExif if the GeoData was empty just in case. |
When I wrote the suggestion code block, you can just click on "commit" button and it will apply my suggestion - but it's nice that you've added comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't check every single value - choose either form geoData
or exif
(unless you have some strong argument against it)
Co-authored-by: Mateusz Soszyński <mateusz.soszynski@tuta.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks and works fine - wonder how many issues it's gonna cause for other people, if just setting correct date did
Maybe some people have lat: 123124324235643543253453253425 lng: -new_york
😆
Thank you once again for making this ❤️ |
Adds the ability to add geo data automatically from googles JSON, and it will skip it if it is empty.
Holy frick this was annoying.