We have recently had the GeoImage functions deployed to our Cloud instance, howe

Given that the function wouldn't know much about the source of the images, the chances are that the pictures taken are not geo-tagged. Can you check if location services are enabled on your mobile device?

Thanks for the reply.

I missed that from the original post. The pictures on the IOS device are 100% heritages. I'm trying to determine if IOS strips the tags, or if the IOS Appian app is doing it. The Android App doesn't appear to give any control over the photo size etc, but the IOS version does so it's not impossible it's something in the App.

Cheers
Chris

Heritages?! That would be 'geo tagged' :-)

Not sure where the tags are being stripped. But thanks for the follow up on heritages. I was just starting a search for "iOS Heritage" :)

Chris, could you try setting the photo size to "Original" in the Appian app? It's possible the resizing is removing the EXIF data. Another way to test would be to upload the image on your phone from the web interface and see if that picks up the data.

Chris - the explanation is that the ios file browser you use in Appian to upload an image (the default photo browser provided by Apple to apps) strips out identifying tags such as location and date/time. Android doesn't do this kind of auto-stripping. (It sounds like you have observed that there are far fewer tags in an iOS image.)

This has been a known issue, so I apologize for not pointing it out on the component thread.

If you turn location on, take a photo on your iPhone, and email it to a process or upload from a desktop, you will see the tags remain.

The only way to change this behavior from the Appian side is to create a custom photo browser in the Appian app instead of using apple's default one. Note that mobile safari's file uploader will do the same thing (remove the tags). If this is a high priority issue for you can you explain your use case and it can be turned into an enhancement request?

Thanks for the reply Elizabth. Thats a shame, as whilst as an organisation we are Android, we cant prevent people using their own device, nor would be really want to.
Including a custom photo browsers would be great, so I'll discuss internally as to if its worthy of requesting an enhancement.

Thanks again for the reply.

Chris