- From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Mar 2017 09:31:27 +0000
- To: public-media-capture-logs@w3.org
@gmandyam
> boolean enableGeoTagging. Would that be a reasonable alternative?
It will solve issue, partially, yet introduce side-effects. If `enableGeoTagging = true;` UA would need to show Geolocation permission UI, since the geolocation would be exposed and can be easily read, e.g. with exif.js.
I think it would be preferable to split geolocation data accusition and it's setters for the captured image.
```
navigator.geolocation.getCurrentPosition(pos => {
imgCap.takePhoto().then(photo => { photo.saveMetadata({geolocation: pos}); })
});
```
In this way, permission related functionality would be controlled by Geolocation API.
As for getting image metadata, developers need external js libraries for parsing blob to get information about result of 3A algorithms. I think it would be nice to provide such information in Image Capture API.
--
GitHub Notification of comment by alexshalamov
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/154#issuecomment-288663395 using your GitHub account
Received on Thursday, 23 March 2017 09:31:33 UTC