Hi, I am experimenting with using the STAC catalog connection from the ArcGIS Pro client to a STAC API through a Azure API Management service to manage my STAC fastapi service.
I have found that although direct blob access to the hrefs of a STAC Item work, links that route the connection through an Azure API Management display more inconsistent behaviour, my sentinel 2 granule data, that totals at 1.7 GB approximately loads fine, but Sentinel-1 data that can sometimes hit 3 GB of data hits an error
ERROR BELOW
S1A_20160330_30_asc_175827_175852_VVVH_G0_GB_OSGB_RTCK_SpkRL: Failed to add data, unsupported data type. C:\Users\USER\Documents\ArcGIS\Projects\MyProject\STAC-CATALOG.astac/StacItemHref/https://(AZURE-APIM).net/collections/(STAC-COLLECTION)/items/S1A_20160330_30_asc_175827_175852_VVVH_G0_GB_OSGB_RTCK_SpkRL
Failed to open raster dataset [Failed to open raster dataset: `C:\Users\USER\Documents\ArcGIS\Projects\MyProject\STAC-CATALOG.astac/StacItemHref/https://(AZURE-APIM).net/collections/(STAC-COLLECTION)/items/S1A_20160330_30_asc_175827_175852_VVVH_G0_GB_OSGB_RTCK_SpkRL' does not exist in the file system, and is not recognized as a supported dataset name.]
Failed to open raster dataset [Failed to open raster dataset: `C:\Users\USER\Documents\ArcGIS\Projects\MyProject\STAC-CATALOG.astac/StacItemHref/https://(AZURE-APIM).net/collections/(STAC-COLLECTION)/items/S1A_20160330_30_asc_175827_175852_VVVH_G0_GB_OSGB_RTCK_SpkRL' does not exist in the file system, and is not recognized as a supported dataset name.]
All three of these errors are displayed along with "Failed to add data to map"
I have confirmed that the sentinel-1 data is valid and can be imported into ArcGIS Pro both locally and using the direct blob url to the STAC datas container in azure blob storage, as the href instead of being through an APIM that routes the connection through a proxy redirect using a 302 method.
Using my sentinel-2 data works through APIM with no issues.
I was curious on if there is perhaps a different behaviour with larger blobs through a 302 redirect, and or if anyone has any experience testing ArcGIS Pro's STAC Connection through an Azure API Management service.
