This page last changed on Jun 20, 2008 by groldan.

This should hopefully be an exhaustive list of everything that is possible to configure in GeoServer, including everything in the UI now, and everything that's configurable in other places. I'll start it roughly grouped by where things are now, eventually we should sort it out in to where it should go in the new UI.

Server Configuration

Verbose Determines whether xml output should have 'pretty printing', like new lines and tabs. This is only used by WCS right now, it is less essential since IE and Firefox both do this automatically for XML, but it could still be a nice option to have for curls and the like.
VerboseExceptions Prints the stack trace in OGC exceptions. Great for debugging, generally off by default so that users don't get big weird nasty messages
Character Set Sets the default character set, like of xml output (would be good to check the places this is used).
Proxy base URL Sets an alternate base url for ogc responses, so it can be in line with a configured proxy.
Logging Profile Sets the logging levels
Suppress StdOut logging Prevents logs from writing to standard out, just writes to a log location
Log Location The location on the file system to write the log to. Relative to data directory (at least by default, not sure if it's possible to set a full file path), default is logs/geoserver.log.
Contact Info I think these right now are only used in the WMS. Is some good metadata to have though.


There are a number of common service elements, that are in WCS, WFS and WMS.

Enabled Whether it's enable or not, global.
Online Resource The online resource metadata. For some reason this is in a different place than the other metadata elements, but probably doesn't need to be.
Name Service name, would be good to have a global service name, and the individual services copy from this. Like 'TOPP Data'.
Title This ends up usually being the same as name, since people don't know the difference. We should get across in the UI that name is the short way to refer to it, Title is how it will appear to clients.
Access Constraints The proper answer is generally NONE
Fees The proper answer is generally NONE
Maintainer Could be good to derive this from the contact info, allow over ride.
Keywords Maybe make people provide keywords in the start up tool, and get the start of these from there. Could also be nice to try to abstract out some more keywords from the data, maybe from the actual data, or the name of the database/table/file
Abstract Another good one to try to get people to fill out.

Notes: For the service level stuff they should probably derive name and title from the workspace name. When new users make a workspace they should probably specify a short name and a long name / title. The short name can be used as the namespace prefix and also as part of the full namespace.
Get people to specify a base url in the start up, like From there a new workspace with roads as the shortname would get a namespace url like Of course the namespace stuff is just for the WFS. But the WCS and WMS should derive their name and title's from the set workspace stuff.


JAI mem capacity These set JAI params, are used by both WMS and WCS, which is why they're at this level. Should ask geosolutions to figure out what they all mean.
JAI mem threshold  
JAI tile threads  
JAI tile priority  
JAI cache recycling  
JAI Image-I/O Caching  
JAI JPEG native acceleration  
JAI PNG native acceleration  


Right now this includes layer groups, which can be added and removed, and which each have:

Tile Cache Specifies a tilecache location. This should probably be deprecated now that we ship with GWC. That will come in a standard location. I guess it could be a thing to specify a remote GWC to do default caching? I can't think why right now though.
Layer-group Name  
Base Map Layers  
Base Map Styles  

And then there is the section on rendering, which has:

SVG Rendering Simple (Fast, but limited styling) Batik (Slow, but full styling) (This is just for vectors).
Antialias Check box, on or off. Sets globally for WMS, would be nice at per layer
Interpolation Nearest Neighbour/Bilinear/Bicubic (These are just for rasters I believe)
Watermarking Global Watermarking
Watermark URL  
Watermark transparency (0-100)
Watermark position  

(these would also be nice on a per layer basis)


Maximum Features Sets the maximum number of features returned by the WFS, is set globally, per featureType is also available. Only applies to WFS. Would be nice if it could apply to WMS as well in some way.
Number of Decimals The number of decimals to return in the WFS response. Useful for cutting off double/float rounding errors that lead to much more verbose output (43.000000003 vs 43). Only used in WFS, afaik.
srsName as XML makes srsName like <MultiLineString srsName=""> vs srsName="EPSG:4326" This may be less necessary, since more clients understand the former now?
Strict CITE Test Conformance Does a few little tweaks to make sure the CITE tests all run right - levels of strictness not generally desired.
Generate feature bounds Puts the bounding box on each feature returned, generated on the fly. Only really useful for multis, could be nice at a per featureType level.
Service Level Lets you set if transactions and locking should be turned on or not.
Validation Not really used at all, could eventually be a plugin for transactions.


Namespaces These are pretty top level now, they should be narrowed down to just be per featureType wfs options. Would also be good to set them per workspace when we get that concept, and then individual featureType's could override.
Styles These need a section to manage the available styles. We also should incorporate the styler code, and let people create styles easily, perhaps on one of the layer tabs.

CoverageStores and DataStores should each have their own wizards. These are pretty understood.

Layer level

Coverages and FeatureTypes have a few specific differences, but there is a decent bit of overlap:

WMS Path sets where it is grouped in the capabilities document. Would be really good to tie this in to layer groups. At the very least a layer group should also set the wms path.
Styles Sets the default and the additional styles. The layout really is not clear though, it looks like the additional ones are the ones that need setting. Should have a nice manager of what styles are set for the layer, and also let the styler edit them and add new ones. And a way to have the additional styles be ones that are already defined in the catalog.
SRS WCS doesn't allow over ride or anything. But both should be able to set the SRS, either look up or set it. We also want the ability to provide WKT from the admin console.
Title/Label, Abstract/Description, Keywords the first two are named different in each. These should line up, I sorta like label and description more than the straight ogc names.
Bounding Box Should be able to hit a button and generate, but also to fill in values since the generation could be very expensive.


Online Resource Not sure why this is per layer, while its not for vector data. I guess the specs may be different.
Request CRS / Response CRS These may be similar to the reprojecting options for vector data, need to ask to make sure, see if they can be collapsed to the same thing.
Supported Formats Not sure why you need to specify all of these, seems like they should just be on all the time. Figure out if there's a use case for turning them off. Should probably be a better input than just a text box though.
Interpolation Methods Again not sure why you'd turn them off. But if so should be better input.


Alias Nice option to rename the featureType, would be nice to have for raster too. Though our workspace concept in publishing should accomplish aliasing easily.
SRS Handling Over ride, reproject, etc. Good to have.
Metadata Url This would probably be good to have on the raster side too. Ideally we get metadata integration with geonetwork, which coordinates this automatically.
Caching Sets the http headers. Should probably coordinate with GWC.
Max Features Only applies to WFS.


These are things that aren't in the UI, but that we should probably support


The new geosearch stuff has brought options on whether a layer should be published to be crawled by google (this would probably be a very good time to try to force the user to fill out more metadata). And lets you set attributes to do the regionating on. Other things I could see being set here would be default thresholds for feature/raster switching in the older kml way of doing things. And perhaps turning on defaults of whether to return extendedData and/or style information. Other thing to be able to set is the various templates, should be able to do them through the web, even if it's just a big text box.

Notes: 'extendedData' is a means of adding the actual attributes to the KML in a way that Google Earth can parse and potentially do interesting stuff with, not sure what it's used for atm.  The regionating process does a fair bit of preprocessing with cached results, would probably be useful to add a 'clear index/rebuild index' button in the GUI someplace.


Would be good to be able to configure it through the web admin tool. We will start shipping with it integrated for 1.7. has information on the properties that can be set. SHould be able to set most things in the .properties file, excluding things that can be derived from the fact that it's a part of geoserver, like the wms url, or the layer if you're configuring it as a layer tab. But there's a lot of options there, like metatiling, a bunch of caching options, transparencies, mime types, size of pixels, etc. The other nice thing to have would be tools to do the seeding and expiring of caches. This could be in the tools section, or could be on the per layer gwc tab.

WMS stuff

Should be able to set per layer settings of anti alias on/off, perhaps a default format, slow or fast svg code. Other big thing to be able to do would be to set the color map. Would be awesome if we had a tool to try to guess a good palette to use. And/or being able to play with it in the preview window, see what the map might look like.

Another suggestion is that most of these should be in individual 'format' pages. Like on the svg one you would set slow or fast, you'd set default compression levels for jpeg, and things like that. But I suppose color map would be at a level above, since it applies to gif and png. The KML stuff would make logical sense in a format section. Also could allow users to disable plugins they may not like. Might also let them set a default format, for like when we use the WMS reflector.

That brings up 'WMS Reflector defaults'. Right now we hard code in defaults like epsg:4326, a default size, png, etc. It would be cool to be able to set these in the UI. Probably in the WMS section.

User/Role management

We've now got acegi working per layer level. We should have a gui to let admins set who has what role. 

Notes: We also want to add to have a GUI for managing which roles can perform which actions.  Definitely restricting layers/services by roles; there's been discussion of having permissions on the administrative side of things as well.

Template editing

Mentioned in the KML section we need these. I believe the list is 'description', 'time', 'title', and there may be one more. Then there also needs to be a GetFeatureInfo one. These all need to be configured on a per layer basis. Justin suggested a wicket/velocity example, that has a text area that you write in the template and it renders it on the fly. Could perhaps be easy to do this with freemarker.

Custom spatial reference system

This may be a tool, may be just a part of the resource page to add it in right there. Probably would be good to have another route to do it. Let users input their WKT, and define a number for it, and also be able to search for what may be defined, hopefully in a nice ajax-y way. If done right may be able to reuse the same tool in the two contexts.

Admin / Tools

There is an admin section now, but it doesn't do much of anything - it clears locks (which aren't really used) and frees memory and JAI memory, but when you hit those it often reports a negative amount. It'd be nice to build some cool admin tools though.

  • View log through the web
  • View most commonly made requests
  • Seed a geowebcache
  • Do KML regionating pre-processing / seeding
  • Build mosiacs and pyramids
  • (add more)
Document generated by Confluence on May 14, 2014 23:00