|
|
Bart van den Eijnden created an issue |
|
WCS 1.1 GetCapabilities should advertise with workspace prefix |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.7.2 |
|
Assignee: |
Unassigned |
|
Components: |
WCS |
|
Created: |
04/Aug/15 9:07 PM |
|
Priority: |
|
|
Reporter: |
|
When doing a WCS 1.1 GetCapabilities request, GeoServer does not advertise the workspace, which can lead to conflicts. Also, when doing a GetCoverage, GeoServer will not accept the advertised identifier from the GetCapabilities response in case of duplicates (multiple coverages with the same name in different workspaces). When embedding a WCS request in WPS this leads to issues in my case. WCS 1.0 and 2.0 do advertise the workspace in some kind of form. 2.0: <wcs:CoverageId>foo__dem_large</wcs:CoverageId> 1.1: <wcs:Identifier>dem_large</wcs:Identifier> <?xml version=“1.0” encoding=“UTF-8”?><wps:ExecuteResponse xmlns:xs=“http://www.w3.org/2001/XMLSchema” xmlns:wps=“http://www.opengis.net/wps/1.0.0” xmlns:ows=“http://www.opengis.net/ows/1.1” xmlns:xlink=“http://www.w3.org/1999/xlink” xml:lang=“en” service=“WPS” serviceInstance=“http://localhost:8080/geoserver/ows?” version=“1.0.0”><wps:Process wps:processVersion=“1.0.0”><ows:Identifier>ras:Contour</ows:Identifier><ows:Title>Contour</ows:Title><ows:Abstract>Computes contour lines at specified intervals or levels for the values in a raster.</ows:Abstract></wps:Process><wps:Status creationTime=“2015-08-03T09:59:05.403Z”><wps:ProcessFailed><ows:ExceptionReport version=“1.1.0”><ows:Exception exceptionCode=“NoApplicableCode”><ows:ExceptionText>Failed to retrieve value for input data |
|
|
|
This message was sent by Atlassian JIRA (v6.5-OD-08-001#65007-sha1:1fc9846) |
|
|