Re: [Geoserver-devel] Trouble adding coverage through REST

Name, e.g. the new coverage/layer is called “test:sfdem <http://engsellis:8080/geoserver/web/wicket/bookmarkable/org.geoserver.web.data.resource.ResourceConfigurationPage?name=sfdem&wsName=test>” in this case. It’s starting to seem like a bug in GeoServer to me but I could be

Re: [Geoserver-devel] Trouble adding coverage through REST

, only PUT, which is shown in the table you pasted in your response. The error I am getting trying to POST a new coverage (which should be allowed by the API) is: 500 Internal Server Error “:Resource native name must not be null” Thanks, Scott *From:*Bryan Moore [mailto:br...@bryanmoore.com

Re: [Geoserver-devel] Generating GeoPackage with GeoServer

might give us some clue as to what might be happening. Cheers Andrea On Fri, Oct 21, 2016 at 6:21 PM, Bryan Moore <mailto:br...@bryanmoore.com>> wrote: I can successfully generate a GeoPackage file from the "nurc:Arc_Sample" layer included with GeoServer but the othe

Re: [Geoserver-devel] Trouble adding coverage through REST

Scott, However, the second step of adding the coverage, e.g.: curl -X POST -u admin:geoserver -H "Content-Type: application/json" -d '{ "coverage": { "name": "rest_test_01" } } ' "http://myhost:8080/geoserver/rest/workspaces/test/coveragestores/rest_test_01/coverages.json";

[Geoserver-devel] Generating GeoPackage with GeoServer

I can successfully generate a GeoPackage file from the "nurc:Arc_Sample" layer included with GeoServer but the other raster layers (nurc:Pk50095, nurc:mosaic, nurc:Img_Sample, sf:sfdem) fail. Environment: GeoServer v. 2.9.1, With WPS and GeoPackage extensions installed. (geoserver-2.9-SNAPSHOT