cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorin Beer (JIRA)" <>
Subject [jira] [Commented] (CB-1285) Include EXIF metadata in image upload
Date Wed, 31 Oct 2012 15:43:13 GMT


Lorin Beer commented on CB-1285:

sent my reply to the whole list rather than replying here.

Hi George,

you should have access to the original date and time, as well as all the other metadata, through
the solution I posted in CB-1246.

The solution we decided to pursue for CB-1285 was to properly embed the metadata in exif format
within the jpeg header as per  the exif header standard. This would mean writing/using a serverside
jpeg exif parser to read the data back out. As Shaz mentioned, writing an Exif Reader for
unit tests may be a possibility, but only if such a project would provide significant utility
to the Cordova community. For validation programatically, I'd rather hack together tests using
an existing reader, which may have an incompatible license, making it impossible to include
into Cordova Core.

If you have any questions about how to use the solution posted in CB-1246, please ask!
> Include EXIF metadata in image upload
> -------------------------------------
>                 Key: CB-1285
>                 URL:
>             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.3.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:

View raw message