We have found that, if you make a GetCapabilities request using external capabilities files, it always defaults to version 1.1.0, even if you specify a different version as a url parameter. For instance, http://[my_server]s:6080/arcgis/services/[folder_name]/BGS_EMODnet_bathymetry/MapServer/WCSServer?request=GetCapabilities&service=WCS&version=2.0.1 will return the GetCapabilities document for version 1.1.0 (if available, otherwise you will get an error), even though we’ve created the version 2.0.1 of the document. The only exception is version 1.0.0, which does return the correct version of the GetCapabilities document if specified in the url.
However, the correct query for a WCS v2 GetCapabilities request should use the AcceptVersions parameter as below. So we should check the expected vs actual behaviour, document that, and, if appropriate file a bug report with ESRI.
In section https://onegeology.github.io/documentation/providingdata.html#edit-the-getcapabilities-document is written:
However, the correct query for a WCS v2 GetCapabilities request should use the AcceptVersions parameter as below. So we should check the expected vs actual behaviour, document that, and, if appropriate file a bug report with ESRI.
http://[my_server]s:6080/arcgis/services/[folder_name]/BGS_EMODnet_bathymetry/MapServer/WCSServer?request=GetCapabilities&service=WCS&AcceptVersions=2.0.1,1.1.0,1.0.0&