Provider - SPIKE - Identify Compatibility of services with ArcGIS Pro
Reports have appeared suggesting that services exposed by GCZ may not be fully compatible with ArcGIS Pro. The reason for this may be due to lack of coverage/support for specific endpoints that are only invoked by clients like ArcGIS Pro. Further investigation is needed to identify the support gaps in our custom Koop plugin on the Provider codebase.
Here is a statement from Esri Support after investigating our service's compatibility with ArcGIS Pro:
… it looks like "ignite" data-provider code that your user has authored themselves. Koop allows developers to author a "data-provider plugin" that can be installed with a Koop instance. This custom plugin performs the task of connecting to a remote data source ("ignite" in this case) and acquiring raw data. The network response suggests that your data provider expects all requests to include a layer ID, and fails if the route doesn't include one. Therefore, it isn't a problem with the Koop code base; it's a problem with the custom plugin. You will need to examine/debug your code and make it fault tolerant for routes that don't include a layer ID
Acceptance Criteria:
- Identify the specific requests that ArcGIS Pro is making on connection attempt
- Identify the requests that the Provider is failing to respond to correctly