[Geoserver-users] REST Configuration API

[Justin_Deoliveira]

Hmmm... I am still not seeing the exception in the logs. Come to think of it I think i added the logging statement in my latest patch to fix the related issue. What build are you running?

Patel, Ronak Avinash (US SSA) wrote:

Hi Justin,

I set the logs to verbose like you said and I get the following error:

14 Apr 11:13:33 DEBUG [geoserver.filters] - filtering
http://patel-dev.irad.net:8080/geoserver/rest/workspaces/leia11/coverage
stores/blah/file.geotiff
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - Converted URL
to lowercase, from:
'/rest/workspaces/leia11/coveragestores/blah/file.geotiff'; to:
'/rest/workspaces/leia11/coveragestores/blah/file.geotiff' and
httpMethod= PUT
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - ~~~~~~~~~~
antPath= /** methodList= [Ljava.lang.String;@893918
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - method[0]:
GET
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - Candidate is:
'/rest/workspaces/leia11/coveragestores/blah/file.geotiff'; antPath is
/**; matchedPath=true; matchedMethods=false
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - ~~~~~~~~~~
antPath= /** methodList= [Ljava.lang.String;@327236
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - method[0]:
POST
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - method[1]:
DELETE
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - method[2]:
PUT
14 Apr 11:13:33 DEBUG
[security.RESTfulPathBasedFilterInvocationDefinitionMap] - Candidate is:
'/rest/workspaces/leia11/coveragestores/blah/file.geotiff'; antPath is
/**; matchedPath=true; matchedMethods=true
14 Apr 11:13:33 DEBUG [gce.arcgrid] - ArcGridFormatFactory is
availaible.
14 Apr 11:13:33 DEBUG [gce.arcgrid] - Creating a new ArcGriFormat.
14 Apr 11:13:33 INFO [catalog.rest] - PUT file, mimetype: image/geotiff
14 Apr 11:13:33 INFO [catalog.rest] - Using existing coverage store:
blah
14 Apr 11:13:33 DEBUG [gce.arcgrid] - ArcGridFormatFactory is
availaible.
14 Apr 11:13:33 DEBUG [gce.arcgrid] - Creating a new ArcGriFormat.
14 Apr 11:13:33 ERROR [geoserver.rest] - Error auto-configuring
coverage:java.lang.NullPointerException

Like you said, I blow away the contents of the
/opt/geoserver-1.7.3/data_dir/data/coveragestorename to get rid of my
geotiff file.

I see that the HTTP PUT does indeed upload my file to geoserver fine.
The problem seems to be with processing the geotiff file after a
successfull upload.

Hopefully this is helpful.

Thanks,

Ronak Patel

-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com] Sent: Tuesday, April 14, 2009 10:43 AM
To: Patel, Ronak Avinash (US SSA)
Cc: geoserver-users@lists.sourceforge.net; Froumis, James A (US SSA)
Subject: Re: [Geoserver-users] REST Configuration API

Hi Patel,

Can you log into the admin console and turn on verbose logging.

Config -> Server and change logging to GEOSERVER_DEVELOPER. And then try

again including the stack trace from the error log.

Also, when files are uploaded they get put into the "data" directory under neath GEOSERVER_DATA_DIR, you may want to try clearing out the appropriate sub directories to ensure a "fresh" start. Which reminds me I fixed an issue recently with files not being able to overwrite existing files, that might be coming into play here.

Thanks,

-Justin

Patel, Ronak Avinash (US SSA) wrote:

Justin,

By the way, I am actually PUTing the image to the server and NOT
POSTing.

I keep getting this error when I try to upload a png or jpg:

14 Apr 10:00:08 INFO [catalog.rest] - PUT file, mimetype: image/jpeg
14 Apr 10:00:08 INFO [catalog.rest] - Using existing coverage store:
blah
14 Apr 10:00:08 ERROR [geoserver.rest] - Error auto-configuring
coverage:Unsupported file format
14 Apr 10:00:22 INFO [catalog.rest] - PUT file, mimetype: image/png
14 Apr 10:00:22 INFO [catalog.rest] - Using existing coverage store:
blah
14 Apr 10:00:22 ERROR [geoserver.rest] - Error auto-configuring
coverage:Unsupported file format

When I try to upload a GeoTiff, I always get the following error:

14 Apr 10:03:49 INFO [catalog.rest] - PUT file, mimetype: image/tif
14 Apr 10:03:49 INFO [catalog.rest] - Using existing coverage store:
blah
14 Apr 10:03:49 ERROR [geoserver.rest] - Error auto-configuring
coverage:java.lang.NullPointerException

I hope that helps in debugging the situation.

Thanks a million!!

Ronak Patel

-----Original Message-----
From: Patel, Ronak Avinash (US SSA) Sent: Tuesday, April 14, 2009 9:50 AM
To: 'Justin Deoliveira'
Cc: geoserver-users@lists.sourceforge.net; Froumis, James A (US SSA)
Subject: RE: [Geoserver-users] REST Configuration API

Justin,

I desperately tried all day yesterday to try to POST a coverage and

get

Geoserver to accept my image (a GeoTiff).

I am POSTing to a CoverageStore and Workspace that I create using the
REST API.

I am POSTing the following:

URL:

/geoserver/rest/workspaces/testWorkspace/coveragestores/testStore/file.g

eotiff

POST ContentType image/tif and the POST content is the file.

I noticed that if I set the configure=none&coverageName=test flags in
the URL, then the file is ingested by Geoserver without complaining.

When I don't set these cgi parameters, things fail and complain.

Why does this happen?

Also, do I have to create a layer to host the image in the WMS? Or is
this done automatically?

Thanks a million!!

Ronak Patel

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.