ArcGIS v. 2.9.3 and updated OIC
Having massive issues loading images to OIC using the "ImageList" utilizing the Amazon S3 Cloud Storage for 360 degrtee Imagery assets.
Parameters:
Error Messages:
Dead in the water here - any ideas??
Thank you.
Hi Owen,
Its unfortunate you are facing this issue. Can you check a couple of things..
1. Check if all the items in the list are accessible.
2. If all the items list are correct. ie make sure there are no items in the list that are not images.
3. If you have the images in a folder on your computer try adding the images by specifying the folder.
4. The image list should only contain the list of images. It should not have a header or should not be comma delimited. Each image path should be in a single line.
5. The image list should be a text file.
If you still face an issue with this please send me the list in a private message and I can have a look for you.
Also sometimes there could be more info in the logs folder in the oriented imagery GP Tools folder.
Thanks,
Randall
After reviewing your QC checks, all seems to be correct. See attached Image List.
HI,
Thank you for the file. Everything looks fine. Can you also check the documentation ( c:\Image_Mgmt_Workflows\OrientedImagery\Documentation\OrientedImageryCatalogManagement_UserGuide.pdf ) for the expected S3 bucket settings. See the chapter : Appendix C: AWS Bucket settings for Oriented Imagery.
This will basically ensure that the GPTool has access to the bucket. Its possible that the GPTool did not have access to the files and failed. Since it runs in multi processing mode it failed and crashed one of the processes.
BTW are you and OwenS the same person? Just checking.. 🙂
Will do. Why does ESRI only allow Amazon S3, Azure & Google Cloud the means for stroage & usage? Yes, I am OwensS - I have many accounts...
Thanks
I'm getting this issue as well. With both my data and Azure account, and with trying the tutorial in the Imagery Workflow files. Just wondering if anyone figured this out or I'm missing something. Looked into CORS but there's more documentation for AWS than Azure available that I can find. Matched up the setting on the Azure side as much as I could find.
We have our data on local servers. To resolve this issue we had to modify the allow-origin rules for CORS on our firewall (nginx) and the internal server (tomcat) serving the images.
Thanks Jeff! Still weird that even the Redlands Campus tutorial is giving this error with the provided list in the tutorial folder. I feel like I'm missing a setting on my machine or in Pro.
Looks like it's now working for me after upgrading to Pro 3.1 this morning.
Thanks!
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
