| Numéro d’ID de bogue |
BUG-000122275 |
| Envoi | May 9, 2019 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS for Desktop |
| Version trouvée | 10.7 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
After investigation, the two services provided are having problems. The main reason this fails is not because of missing a getcapabilities in the connection URL. A WCS connection is capable to find the highest version it supports at both the ArcGIS client and WCS server. It makes attempt calls to the server and append any query parameters where necessary.
The real problems:
1. http://neso.cryoland.enveo.at/cryoland/ows?service=wcs&request=GetCapabilities
there is no parameter inside the getcapabilities call, so the client does not know what coverage to "describecoverage".
2. http://ows.rasdaman.org/rasdaman/ows?SERVICE=WCS&REQUEST=GetCapabilities
The version this WCS supports is 2.1 and 2.0.1 as advertised. ArcMap supports 2.0.1 as the highest version. Theoretically, ArcMap can getcoverage based on 2.0.1. However, if attaching &version=2.0.1 to the URL above, the response is still using 2.1 version of getcapabilities. So the ArcMap client fails to parse it.
Étapes pour reproduire
ID de bogue: BUG-000122275
Logiciel: