-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Not uniform value for GPS coordinates #28
Comments
This is the same root problem as in #27. The value from Exif is overwritten by the XMP value. And since XMP properties can have any name, no conversions are made for the description as is done for Exif. (This should definitely be made clear in the README.) That being said, some are probably more "standardized" than others and could be converted (e.g. GPS properties and orientation). I will look into this after we have solved #27. |
Within the module I'm building, I'm using isNaN(parseFloat(suspect.description)) to make sure the coordinates are legit. I posted in #27 the fork I put together to bypass the flattening of the different tags. |
Please have a look at pull request #32 for a solution to this. |
Fixed in #32. |
For some pictures (like http://www.freemap.sk:3000/gallery/pictures/67129/image) the returned value of eg.
GPSLatitude
isbut for others (like https://user-images.githubusercontent.com/26544966/30610062-66d59c6e-9d7d-11e7-8a7b-99a26d36a8ff.JPG) it is
Could it be unified (in
description
)?The text was updated successfully, but these errors were encountered: