Hi Brad,

Hope this helps clear things up

/workspaces/<ws>/coveragestores/<cs>/coverages/<c>
workspacename <ws> = GLI_CEREAL
coveragestore <cs> = BARLEYHAR
coverage <c> = BARLEYHAR

I successfully created a image mosaic jdb coveragestore by posting an xml
at url1
url1:
http://geoserver.terrapop.org/geoserver/rest/workspaces/GLI_CEREAL/coveragestores/

This resulted in a successful coveragestore at the following address, url2.
However, no coverage/layer was automatically published from this
coveragestore. So I am looking for an example of creating the coverage from
the coveragestore I believe.
url2:
http://geoserver.terrapop.org/geoserver/rest/workspaces/GLI_CEREAL/coveragestores/BARLEYHAR

Also, I tried posting a coverage.xml to this new url and received a 403
error
http://geoserver.terrapop.org/geoserver/rest/workspaces/GLI_CEREAL/coveragestores/BARLEYHAR/coverages

On Tue, Nov 17, 2015 at 11:01 PM, Brad Hards <[email protected]> wrote:

> On Tue, 17 Nov 2015 04:34:05 PM David Haynes II wrote:
> > I tried posting to an xml to this url
> > "/workspaces/<ws>/coveragestores/<cs>/coverages/<c>" and received a 401
> > error.
> Can you say what you are really posting? What are <ws>, <cs> and <c> here?
> Also, can you confirm that that isn't the full URL (i.e. you really did
> put a
> machine name and protocol to the URL)?
>
> What is the data type you are trying to upload?
>
> What user are you trying to upload as?
>
> Brad
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>



-- 
David Haynes, Ph.D.
Research Associate Terra Populus
Minnesota Population Center
612-626-3933
www.terrapop.org
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to