Dear list, I managed to upload a GeoTiff via REST without letting GeoServer making a local copy in the data/ directory. I did this by means of the 'external' keywork, e.g.:
> curl -u $USER:$PASSWORD -XPUT -H 'Content-type: text/plain' -d > 'file:/path/to/my.geo.tif' > http://$HOST:$PORT/geoserver/rest/workspaces/$WORKSPACE/coveragestores/my.geo.tif/external.geotiff In this case the name of the coverageStore is "my.geo.tif", whereas the name of the coverage and the published layer is turned into "my.geo". Is this somehow part of the philosophy of the REST configuration, or is this a bug? I recover the correct name information by PUTting this to the coverage, e.g.: > curl -u $USER:$PASSWORD -XPUT -H 'Content-type: text/xml' -d > '<coverage><name>my.geo.tif</name><title>my.geo.tif</title><metadata><entry > key="dirName">my.geo.tif_my.geo.tif</entry></metadata><enabled>true</enabled></coverage>' > http://$HOST:$PORT/geoserver/rest/workspaces/$WORKSPACE/coveragestores/my.geo.tif/coverages/my.geo.tif This way, I can visualize the map, but I hope not to bring some inconsistent configuration beneath the surface. Thanks for the help. Regards, Piero -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/RESTful-geotiff-uploading-tp6116966p6377678.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
