Hi Andrea,
I couldn't make it work. It seems like when using external. the
whole request body is taken as a URL:
$ curl -u admin:geoserver -XPUT -H "Content-type: multipart/form-data" -F
"file=/tmp/test.tif"
Hi Victor,
not sure, but from a quick glance in the code, try adding "coverageName" as
a form parameter in the upload (I believe this means the upload will have
to be a form multipart one)
Cheers
Andrea
On Sun, Nov 13, 2016 at 12:33 PM, Víctor González <
victor.gonza...@geomati.co> wrote:
>
Hi,
Thanks for your responses.
@Peter The problem is that the raster files are uploaded by other process
to the server and we
don't know their metadata beforehand nor we have the possibility to use a
GUI manually for each of them.
@Andrea Thanks, I should have read the doc more carefully...
As far as I know, you have to change the way you're creating the coverage
store,
using the "external" syntax similar to this example configuring a shapefile
that's
already on disk:
http://docs.geoserver.org/latest/en/user/rest/examples/curl.html#adding-an-existing-shapefile
Sorry I don't have an
Hi Victor,
usually, with REST, it works like this:
If you want to update some property X of some resource Y, first try to
configure similar resource via web UI and then make a GET request via
REST so that you can see the full configuration with all the options and
their values.
In your
Hi,
I'm loading a new GeoTIFF layer using REST by adding a new coveragestore
and coverage (requests below). After that, the layer does not have
information about bands and I have to use the "Reload band definitions"
option in the web GUI to load them manually (because I don't know the
raster
