Using pictures taken with Field Maps in an oriented imagery layer

[Vincentde_Jonge]

Hiya,

I've been trying to find a way to use pictures taken using Field Maps (or another ArcGIS App) in an oriented imagery layer, or at the very least the direction in which the picture was taken. Of course, we first tried using QuickCapture, but as we also need to fill in quite a few attributes, the lack of a form like in Field Maps/Survey123 proved too cumbersome. 

As the info required comes from the exifdata, I next used QC, Field Maps and Survey 123 to take pictures. It turns out every app gives back different exifdata. I compared the exifdata using exiftool.

Field Maps doesn't give GPSImgDirection (or equivalent), so it seems it's impossible to get the picture direction from there. Survey123 does give the direction and an easy way to get it in the feature service, but doesn't seem to provide other parameters for the oriented imagery layer (roll, depth etc). QuickCapture does provide all those things, but doesn't have the functionality to provide nice forms.

Am I doing something wrong/missing something? Is there any other way to use the ArcGIS apps to take picture and have the img direction in there? 

[DougBrowning]

No QuickCapture is the only one setting the tags so far and its a bummer.  I thought I posted an idea for it but cannot find it.  I have talked directly to 123 team on this though.  I think its weird to have all these apps to view them but no way to take them.  They tend to assume its drone imagery a lot.  Teams need to coordinate better.

[DavidSolari]

I'm curious, do photos taken outside of Field Maps and then attached later have the same metadata issue? If not then using the device's built-in camera app (or something you grab from the app store if the stock app's lacking) would be a clunky workaround. Not that this is an excuse to not log as much metadata as possible in a GIS collection app, hope the team can patch this up for the next big release.

[Vincentde_Jonge]

Well, I didn't want to explore this right away, as it'd be a lot harder to make sure it's the same on every device. I don't see a reason why this wouldn't work in theory. However, I might just suggest settling for imgdirection only for now, since that's the most important thing the stakeholders actually have a use for. 

I'll post an update here if I do end up trying a third-party camera app and importing the pictures afterwards.