Error 000121 when running Generate Service From Oriented Imagery Dataset tool

[AaronKoelker]

Hello, I'm trying to publish an Oriented Imagery Dataset to ArcGIS Online using the Generate Service From Oriented Imagery Dataset (ArcGIS Pro 3.6). The tool is failing with Error 000121 : Cannot analyze the dataset. The documentation on this errors says it occurs because the Analyze tool can only be used on datasets in an ArcSDE (enterprise) geodatabase. While my data is only in a file geodatabase, I haven't seen anything anywhere saying that Oriented imagery can only be published from an SDE geodatabase, so I'm a little confused by this error message and solution. 

Has anyone else run into this or have an idea of what's going on? Does my oriented imagery dataset really need to be in an enterprise geodatabase first in order to publish it to AGO? 

[Robert_LeClair]

Are you using the workflow as described here - Oriented Imagery in ArcGIS Pro: Create & Publish to ArcGIS Online

[AaronKoelker]

Thanks @Robert_LeClair. No, not that exact page but I was following an Esri tutorial video and referring to the documentation pages for the individual tools. That video shows a file geodatabase being used and successfully publishing to an Enterprise portal (the tool documentation mentions ArcGIS Online too, though).

This part in the workflow you shared sticks out to me: 

-If the images are going to be viewed only in ArcGIS Pro, you can add a folder with the images.

-If the dataset is going to be published to ArcGIS Online, input a CSV file with the following fields: X, Y, Spatial Reference System, Image Path, Camera Heading, Pitch, Roll, Height. To add orientation information such as Omega, Phi, Kappa, the extra field should follow this schema: 2|H_WKID|V_WKID|X|Y|Z|RA1|RA2|RA3.

I had used a folder of images with lat/lon info in the EXIF data, then I manually updated some of the other fields after the dataset was created. Not sure why they source would matter if they both end up in an Oriented Imagery dataset with the same fields, and I haven't found anything else that mentions or explains why a CSV should be used if publishing to AGO specifically. 

[PeterS · Accepted solution]

Hi Aaron,

I ran into the same issue and found that it only occurs when the footprint layer is included in the service. If I leave that out, publishing works fine.

What worked for me was pointing the tool to the file geodatabase where the OI dataset is stored, rather than to the layer in the map. The map can still be open, but for the Input Oriented Imagery Dataset parameter, you need to browse to the actual feature class in the file geodatabase.

It seems the issue may be related to how the tool retrieves the footprint layer from the map. The only downside is that the ArcGIS Pro symbology does not carry over, but that can be set in ArcGIS Online.

Hope this helps.

Peter

[AaronKoelker]

Thanks Peter, I will try that. I did manage to get an OI service published after testing the 360 Video to Oriented Imagery GP tool, too. That tool initially gave me an error that my OI dataset needed to be Z-enabled, and I was able to get a service up after doing that. I'm curious if that might have been what was triggering the initial issue I had with the Generate Service tool, too (but giving a less clear error message as a result).

However I also skipped the footprint layer the second time, so perhaps that really is the only issue. I did not point directly at the OI dataset using the full file geodatabase path.

[AaronKoelker]

I can confirm that was the solution. If the box to include footprints is checked, then for the input OI dataset you must browse to the actual dataset within the file geodatabase and add it from there directly. You cannot add it from the map as a layer input. 

If anyone from Esri sees this, it would be great if the tool could be enhanced to allow inputs from the map, or at the very least, add a more specific error message to catch this scenario so that users know how to address it. The current error (000121) and the suggested solution on the error page are misleading in this case. 

[Robert_LeClair]

@KoryKramer - FYI