[ 
https://issues.apache.org/jira/browse/CB-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457399#comment-13457399
 ] 

Lorin Beer commented on CB-1285:
--------------------------------

I took a look at this and the related issues.

We can provide the exif metadata in a few ways:

1. provide the metadata as a json string to the success callback
2. overwrite the Cordova created image with the metadata of the original.

I believe Android saves the metadata, and restores it after it has been 
stripped.

The simplest way is 1, but this changes the expected return value of the 'data' 
field in the success callback, which is the images path.

Before I implement and test, anyone have any suggestions on which method would 
be best?
                
> Include EXIF metadata in image upload
> -------------------------------------
>
>                 Key: CB-1285
>                 URL: https://issues.apache.org/jira/browse/CB-1285
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: iOS
>    Affects Versions: 2.0.0
>         Environment: iOS 5.1.1 (iPad 2 & iPhone 4)
>            Reporter: Stephen McKamey
>            Assignee: Lorin Beer
>             Fix For: 2.2.0
>
>
> Now that Cordova only supports iOS 4.2+, it would be great if it would 
> include the additional EXIF metadata which exists in original image files. 
> Currently this is all stripped. I've noticed a recent increased trend of iOS 
> apps declaring that they can gain access to EXIF data if the user permits 
> location information. If EXIF & geo data were passed through this would be a 
> huge gain for Cordova.
> Related: a similar issue (CB-295) was opened for Android and it sounds like 
> it was implemented. From the other issue, it sounded like it was a side 
> effect of resizing the image. If no resizing needs to occur (i.e., the 
> untouched original bits are desired), then perhaps this would help?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to