Hello Piero,
I will check the issue reported as soon as possible and give you feedbacks
on that.
Thanks,
Alessio.
-------------------------------------------------------
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
http://www.geo-solutions.it
http://geo-solutions.blogspot.com
http://www.linkedin.com/in/alessiofabiani
http://twitter.com/geosolutions_it
-------------------------------------------------------
On Wed, May 18, 2011 at 2:54 PM, Piero Campa <[email protected]> wrote:
> 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
>
------------------------------------------------------------------------------
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
