If you do a POST to /rest/workspaces/foo/coveragestores.json:
and then a second POST to /rest/workspaces/foo/coveragestores/myCoverage/coverages.json to create the coverage:
The coverage creates fine, but the Native/LatLon bounds are not set – which then crashes (eg. GetCapabilities) requests and generally does bad things. Obviously I can specify them manually, but it'd be miles better if GeoServer auto-calculated them like it does in the UI. The same POSTs work fine for Feature Types and the bounds are auto-calculated.
Looking at the code, there are CatalogBuilder.initFeatureType() and CatalogBuilder.initWMSLayer() methods which do this auto-detection, but the same thing doesn't occur for coverages. CatalogBuilder.buildCoverage(AbstractGridCoverage2DReader reader, Map customParameters) does it, but is only called for PUT requests which include an attached file, not for POST requests.
|Attachment||add-initcataloginfo-for-post-requests-with-test.patch [ 55939 ]|
|Attachment||add-initcataloginfo-for-post-requests-with-test.patch [ 55940 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||2.1.2 [ 17445 ]|
|Fix Version/s||2.2.x [ 17106 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|