-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Photo taking/tagging/submitting from within OwnTracks app #824
Comments
Yes! First thoughts: We could either take a photograph or select an existing photograph from the photo library. This would be similar to the process to create a card. With the photograph we could require a "POI" to be entered. As the next step, we would
|
Is it possible to manipulate / augment the EXIF data in a taken photograph with, say, a designated |
I can extract the original filename e.g. |
I suspect the taken photograph would remain on the iPhone storage which it should. Its filename or UUID would be transported in a I would suggest the |
It looks a bit as though curry is on me tomorrow evening! |
probably due to falling through as we don't yet have code for |
So, after discussion, I think we've settled on:
That way, people can shoot a photo, then upload a POI location with a thumbnail of the photo. In theory, the thumbnail can be displayed on the map and hopefully Android and Frontend will at some stage have the capabilities of displaying the thumbnail for the location likewise. |
Would it be technically possible to take photographs from within the OwnTracks iOS app (Android would follow suit if feasable) which are then either submitted via MQTT (or HTTP if that is the selected transport) tagged in such a way (EXIF data?) that there can be a direct association between the picture and the OwnTracks location?
I'm thinking along the lines of:
/pic
where it is storedtag
and/or currentPoI
if set.This might be quite a bit of work, but possibly a neat feature to have, and in fact somebody at
#geomobNL
recently actually asked for this.The text was updated successfully, but these errors were encountered: