Ian and Charles, Thanks for the clue (obvious really!) but I'm not sure there's much to work with:
>>>>>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE ServiceExceptionReport SYSTEM "http://atlas.track.gov.au:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";> <ServiceExceptionReport version="1.1.1" > <ServiceException> java.lang.NullPointerException null </ServiceException> </ServiceExceptionReport> <<<<<<<< Regarding the single layer vs 30 layers...this sounds enticing, but I'm still confused: We want the user to be able to turn any one of the 30 "layers" on or off to see that styled data (or combination of data layers) on the map. (eg, they might want to see fish species richness and turtle species richness on the same map. These are two of the attribute columns) The only way I know to do this is to publish the single shp file (which has 30 attribute columns, all on the same geometry) as a layer. Now, I [re-publish] this one layer 30 times, each time giving it the appropriate name and assigning the appropriate style. This gives us 30 "independent" layers in the viewing interface, but obviously each "layer" actually contains all 30 cols of data. So: I'm not sure how to optimise this. And it's a big question... some of the other shapefiles have hundreds of attribute columns (thus hundreds of SLDs) and it seems like we have to either: (a) create 100 shapefiles in Arc, each one with the *complete geometry* and one column of data; or (b) re-publish the same layer 100 times, with each layer containing all 100 cols of data. Thanks for any further insights! Kind regards, JB John Brisbin Managing Director, BoaB interactive Pty Ltd POB 802 Townsville, QLD 4810 M: 0407 471 565 | P: 07 3103 0574 Skype: boabjohn | Twitter: @boabjohn On 5/10/2011 11:36 PM, Ian Turton wrote: > On 5 October 2011 13:24, John Brisbin<[email protected]> wrote: >> PROBLEM >> >> We export an ESRI shapefile with 30 attribute columns. pgADMIN3 and >> shp2pgsql are used to push the shapefile into PostGIS. >> >> We have a stack of corresponding SLD files, manually loaded (one by one) >> through the GeoServer Style uploader. >> > Can you not have a single layer with 30 styles? instead of needing many > layers? > >> To publish these 30 layers (one by one): > [...] >> 8. We go to Layer Preview, and choose to view the layer as OpenLayers, >> and get not the preview map, but a download dialog asking if we want to >> save an xml file. This response is the same for all the WMS formats. The >> WFS format at least provides a CSV output, in which I can see the >> polygon IDs and their geometry data. The attribute data was not apparent. > What is the error message contained with in the XML file? It will > probably give you a clue as to the problem. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
