The ArcGIS harvesting tasks generate the ows_url property by doing a (right) partitioning of the harvested resource identifier.
This works fine for MapServer services, since they give each layer the base URL + "/" + a unique number for the layer. The result is that the final URL is equal to the base URL.
However, the same is implemented for an ImageServer and in that case the partitioning truncate the URL, loosing the final path.
As an example, the ows_url for an ImageServer resource from the sample service https://sampleserver6.arcgisonline.com/arcgis/rest/services/Toronto/ImageServer, gets truncated to https://sampleserver6.arcgisonline.com/arcgis/rest/services/Toronto, breaking the visualization of the layer inside the GeoNode client.
A solution that should work for both cases is to use the harvester remote URL, rather then the harvested resource identifier.
The ArcGIS harvesting tasks generate the
ows_urlproperty by doing a (right) partitioning of the harvested resource identifier. This works fine forMapServerservices, since they give each layer the base URL + "/" + a unique number for the layer. The result is that the final URL is equal to the base URL. However, the same is implemented for anImageServerand in that case the partitioning truncate the URL, loosing the final path.As an example, the ows_url for an ImageServer resource from the sample service
https://sampleserver6.arcgisonline.com/arcgis/rest/services/Toronto/ImageServer, gets truncated tohttps://sampleserver6.arcgisonline.com/arcgis/rest/services/Toronto, breaking the visualization of the layer inside the GeoNode client.A solution that should work for both cases is to use the harvester remote URL, rather then the harvested resource identifier.