-
Notifications
You must be signed in to change notification settings - Fork 206
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
exif.js doesn't read orientation tags properly #181
Comments
Specifically RIM0342.JPG is wrong, and RIM0352.JPG is right, in the CUAS example. |
So, this is now implemented (a67ff2a) but is not working properly.
|
Filed an issue here: exif-js/exif-js#45 |
@jywarren I noticed there was a update in issue exif-js/exif-js#45. Would you like to update here too? Thanks! |
Hmm do you think it was fixed? |
No @jywarren, the issue is still open. |
I think we'll have to try to help solve it upstream in exif.js. Thanks! |
@jywarren @gauravano I started working looking at the exif data today when looking at your modularization of exporter code PR. Will definitely look into this more. Just wondering what API are we using exactly? There wasn't much documentation to guide me |
We're probably going to start doing this in Leaflet.DistortableImage as part of @rexagod's new GPS placement API -- see publiclab/Leaflet.DistortableImage#169 -- although it's still in progress. But It basically uses the Exif.js library to dig GPS tags out of the images, and to auto-place them accordingly! |
http://mapknitter.org/maps/gps-test shows several which seem to be off by increments of 90 degrees;
See how this is done in the backend: https://github.com/publiclab/mapknitter/blob/master/app/models/warpable.rb#L231-L242
EXIF orientation values:
The text was updated successfully, but these errors were encountered: