OIC cannot read coordinates from Images in AWS S3

597
5
06-07-2023 06:16 AM
bogdanpalade2
New Contributor III

Another issue from the long list of issues that OIC has. Sometimes I wonder if this tool is just a test or a very beta version.

So, the issue is:

Images in the local drive get inserted in the OIC (with folder option) and the coordinates are read perfectly. 

Same images, uploaded on AWS (with imagelist option), when trying to add them to the catalogue return "Could not extract coordinate info to add image". The bucket is public and the images are publicly available from every browser outside or inside our firewall (tested).

Any thoughts?

 

0 Kudos
5 Replies
RandallRebello
Occasional Contributor II

Hi Bodan, 

The issue you are facing is probably because you have not set the CORS policy for the bucket. If you read documentation of the tool which can be found here

 

0 Kudos
bogdanpalade2
New Contributor III

Hi Randall,

There is a CORS policy in place:

[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"PUT",
"POST",
"GET"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": []
}
]

Maybe its not correct?

0 Kudos
RandallRebello
Occasional Contributor II

Please have a look at the document. 

0 Kudos
bogdanpalade2
New Contributor III

Hi, I did have a look again and read the annexes. I updated the bucket policy and the CORS and now I get a VersionJSON error (see attached). 

Bucket policy:

{
"Version": "2012-10-17",
"Id": "Policy1467091827492",
"Statement": [
{
"Sid": "Stmt1467091817285",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::unisfa/*"
}
]
}

 

CORS:

 

[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"GET"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]

 

oic1.png

0 Kudos
bogdanpalade2
New Contributor III

The "VersionJSON" error I think it's unrelated to the "Could not extract coordinate info to add image" error. It appears when running all tools, but it doesn t influence the results.

0 Kudos