Thanks for the tip David. The layers were _not_ configured with gsconfig, rather they were configured using the GeoServer Web UI and then added to GeoNode with the updatelayers management command. GeoServer does not seem to have any trouble rendering them via WMS etc http://tsudat.dev.aifdr.org/geoserver-geonode-dev/wms?service=WMS&version=1.1.0&request=GetMap&layers=tsudat:ga_250m&styles=&bbox=91.999,-60.001,172.006,-7.994&width=512&height=332&srs=EPSG:4326&format=application/openlayers
That said, running your code snippet does indicate that the 'grid' setting is NONE (among other things like '__weakref__ ' which dont seem to be a problem). Not sure if that is/could be the problem, but I see no indication of a 'grid' setting in the GeoServer UI. Any other ideas? Jeff On Mon, Mar 28, 2011 at 12:23 PM, David Winslow <dwins...@opengeo.org> wrote: > I seem to recall running into a similar issue before - GeoNode uses > RESTConfig heavily, RESTConfig does not safeguard against invalid > configurations as well as it might, and the WCS describe coverage encoder > does not inspect its inputs very deeply, so you can get some weird behavior > if GeoNode produces a bogus configuration. Here is a script I use (it > requires gsconfig.py, available from http://github.com/dwins/gsconfig.py, > although if you have a running geonode then gsconfig.py will already be > available to you): https://gist.github.com/891080 > It produces a listing of entities within the geoserver configuration which > have null properties, then I skim through the output (usually with judicious > use of grep) to identify layers that are likely to cause problems (missing > bounding boxes etc.) For errors with particularly useless messages I > sometimes have to look through geoserver code to identify the property > access which is causing the problem. > -- > David Winslow > OpenGeo - http://opengeo.org/ > > On Mon, Mar 28, 2011 at 2:59 PM, Jeff Johnson <jjohn...@opengeo.org> wrote: >> >> Hi All, >> >> Anyone have an idea why this DescribeCoverage Request returns invalid xml? >> >> >> http://tsudat.dev.aifdr.org/geoserver-geonode-dev/wcs?service=WCS&request=DescribeCoverage&version=1.0.0&coverage=ga_250m >> >> Looks like the RangeSet set tag is mis-matched? >> >> Im running 2.0-SNAPSHOT inside of GeoNode (geonode.org) >> >> Thanks in advance, >> >> Jeff >> >> >> ------------------------------------------------------------------------------ >> Create and publish websites with WebMatrix >> Use the most popular FREE web apps or write code yourself; >> WebMatrix provides all the features you need to develop and publish >> your website. http://p.sf.net/sfu/ms-webmatrix-sf >> _______________________________________________ >> Geoserver-users mailing list >> Geoserver-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-users > > ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
