Howdy Charles: I've upped the logging level and will see if I can make sense of anything.
Can I just follow the "how to publish 30 layers" thread just a bit further? When you say: > The idea is you publish this layer once, with all attributes exposed I'm not sure how to "expose" all the attributes? Following my original scenario, I added a new resource, which allowed me to select the one shapefile table from the PostGIS store. At what point am I able to expose all the attributes? Do you mean (under the [Publishing tab]) to move all the relevant styles over to the [Selected styles] pane? If this works how I think it works, then what we get delivered to the user is a *single layer* that can be selected in the map viewer. If the user is cluey, they can right click, choose to Edit Style, and then browse a drop-down list of the 30 different styles. That's interesting, and certainly saves data storage space, but how can the user see 2 layers at once? And how do we display the human-friendly layer title in the layer panel? I think these are the key deliverables I have to provide...and the "edit style" strategy seems to go a different conceptual path? The CSS editor looks interesting: this would cut the effort of uploading SLDs. 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 6/10/2011 12:28 AM, Charles Galpin wrote: > On Oct 5, 2011, at 8:49 AM, John Brisbin wrote: > >> java.lang.NullPointerException >> > Time to look at the logs. If you don't see enough detail increase the level > > http://docs.geoserver.org/latest/en/user/webadmin/server/globalsettings.html > >> 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 idea is you publish this layer once, with all attributes exposed. Then > you make a different style for each kind of data and this style just works > with the attributes it cares about. Then from your client you use the same > layer but specify a different style. > > I encourage you to take a look at the css plugin if you haven't. It makes > creating style very easy and manageable. > > http://docs.geoserver.org/latest/en/user/community/css/index.html > > hth > charles > > ------------------------------------------------------------------------------ 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
