GeoServer Styles

A style describes how a resource is symbolized or rendered by the Web Map Service.
More information: http://geoserver.org/comm/
Contact Info: geoserver-users@sourceforge.net
Version: 1.0.0
BasePath:/geoserver/rest
All rights reserved
http://apache.org/licenses/LICENSE-2.0.html

Access

Methods

[ Jump to Models ]

Table of Contents

Default

Default

Up
delete /rest/layers/{layer}/styles
(deleteLayerStyles)
Invalid.

Path parameters

layer (required)
Path Parameter — Name of the layer to manage styles for

Responses

405

Method Not Allowed

Up
delete /styles/{style}
Delete style (deleteStyle)
Deletes a style.

Path parameters

style (required)
Path Parameter — Name of the style to delete.

Query parameters

purge (optional)
Query Parameter — Specifies whether the underlying file containing the style should be deleted on disk. default: false
recurse (optional)
Query Parameter — Removes references to the specified style in existing layers. default: false

Responses

200

OK

401

Unauthorized

Up
delete /styles
(deleteStyles)
Invalid. Use /styles/{style} instead.

Responses

405

Method Not Allowed

Up
delete /rest/workspaces/{workspace}/styles/{style}
Delete style in a given workspace (deleteWorkspaceStyle)
Deletes a style in a given workspace.

Path parameters

workspace (required)
Path Parameter — Name of the workspace for style definitions
style (required)
Path Parameter — Name of the style to delete.

Query parameters

purge (optional)
Query Parameter — Specifies whether the underlying file containing the style should be deleted on disk. default: false
recurse (optional)
Query Parameter — Removes references to the specified style in existing layers. default: false

Responses

200

OK

401

Unauthorized

Up
delete /workspaces/{workspace}/styles
(deleteWorkspaceStyles)
Invalid. Use /workspaces/{workspace}/styles/{style} instead.

Path parameters

workspace (required)
Path Parameter — Name of workspace

Responses

405

Method Not Allowed

Up
get /rest/layers/{layer}/styles
Get a list of layer alternate styles (getLayerStyles)
Displays a list of all alternate styles for a given layer. Use the "Accept:" header to specify format or append an extension to the endpoint (example "/layers/{layer}/styles.xml" for XML).

Path parameters

layer (required)
Path Parameter — Name of the layer to manage styles for

Return type

StyleList

Example data

Content-Type: application/xml
"\n  \n  \n\n"

Example data

Content-Type: application/json
"{\n  \"styles\": {\n    \"style\": [\n      {\n        \"name\": \"pophatch\",\n        \"href\": \"http://localhost:8080/geoserver/rest/layers/topp:states/styles/pophatch.json\"\n      },\n      {\n        \"name\": \"polygon\",\n        \"href\": \"http://localhost:8080/geoserver/rest/layers/topp:states/styles/polygon.json\"\n      }\n    ]\n  }\n}\n"

Produces

This API call produces the following media types according to the Accept request header; the media type will be conveyed by the Content-Type response header.

Responses

200

OK StyleList

Example data

Content-Type: application/xml

  
  

Example data

Content-Type: application/json
{
  "styles": {
    "style": [
      {
        "name": "pophatch",
        "href": "http://localhost:8080/geoserver/rest/layers/topp:states/styles/pophatch.json"
      },
      {
        "name": "polygon",
        "href": "http://localhost:8080/geoserver/rest/layers/topp:states/styles/polygon.json"
      }
    ]
  }
}

Up
get /styles/{style}
Retrieve a style (getStyle)

Retrieves a single style. Used to both request the style info and the style defintion body, depending on the media type requested. The media type can be specified either by using the "Accept:" header or by appending an extension to the endpoint. For example, a style info can be requested in XML format using "/styles/{style}.xml" or "Accept: application/xml". (Also available: "{style}.json", "Accept: application/json" "{style}.html", and "Accept: text/html").

The style definition body can be requested by either appending the file extension of the style file (e.g., "{style}.sld" or "{style}.css") or by specifying the correct media type for the style definition in the "Accept" header. Below are common style formats and the corresponding media types that can be used in the Accept header to request the style definition body.

Path parameters

style (required)
Path Parameter — Name of the style to retrieve.

Return type

Style

Example data

Content-Type: application/xml
"\n"

Example data

Content-Type: application/json
"{\"style\":\n  {\"name\":\"rain\", \"format\":\"sld\",\n  \"languageVersion\": {\"version\":\"1.0.0\"},\n  \"filename\":\"rain.sld\"}\n}\n"

Example data

Content-Type: application/vnd.ogc.sld+xml
"\n\n  \n    rain\n    \n      rain\n      Rain distribution\n      \n        \n          \n            1.0\n            \n              \n              \n              \n              \n            \n          \n        \n      \n    \n  \n\n"

Produces

This API call produces the following media types according to the Accept request header; the media type will be conveyed by the Content-Type response header.

Responses

200

OK Style

Example data

Content-Type: application/xml

Example data

Content-Type: application/json
{"style":
  {"name":"rain", "format":"sld",
  "languageVersion": {"version":"1.0.0"},
  "filename":"rain.sld"}
}

Example data

Content-Type: application/vnd.ogc.sld+xml


  
    rain
    
      rain
      Rain distribution
      
        
          
            1.0
            
              
              
              
              
            
          
        
      
    
  


Up
get /styles
Get a list of styles (getStyles)
Displays a list of all styles on the server. Use the "Accept:" header to specify format or append an extension to the endpoint (example "/styles.xml" for XML).

Return type

StyleList

Example data

Content-Type: application/xml
"\n    \n        \n\n"

Example data

Content-Type: application/json
"{\"styles\":\n  {\"style\":\n    [ {\"href\":\"http://localhost:8080/geoserver/rest/styles/burg.json\", \"name\":\"burg\"},\n      {\"href\":\"http://localhost:8080/geoserver/rest/styles/capitals.json\", \"name\":\"capitals\"}]}}\n"

Produces

This API call produces the following media types according to the Accept request header; the media type will be conveyed by the Content-Type response header.

Responses

200

OK StyleList

Example data

Content-Type: application/xml

    
        

Example data

Content-Type: application/json
{"styles":
  {"style":
    [ {"href":"http://localhost:8080/geoserver/rest/styles/burg.json", "name":"burg"},
      {"href":"http://localhost:8080/geoserver/rest/styles/capitals.json", "name":"capitals"}]}}

Up
get /rest/workspaces/{workspace}/styles/{style}
Retrieve a style from a given workspace (getWorkspaceStyle)

Retrieves a single style. Used to both request the style info and the style defintion body, depending on the media type requested. The media type can be specified either by using the "Accept:" header or by appending an extension to the endpoint. For example, a style info can be requested in XML format using "/styles/{style}.xml" or "Accept: application/xml". (Also available: "{style}.json", "Accept: application/json" "{style}.html", and "Accept: text/html").

The style definition body can be requested by either appending the file extension of the style file (e.g., "{style}.sld" or "{style}.css") or by specifying the correct media type for the style definition in the "Accept" header. Below are common style formats and the corresponding media types that can be used in the Accept header to request the style definition body.

Path parameters

workspace (required)
Path Parameter — Name of the workspace for style definitions
style (required)
Path Parameter — Name of the style to retrieve.

Return type

StyleWorkspace

Example data

Content-Type: application/xml
"\n"

Example data

Content-Type: application/json
"{\"style\": \n  {\"name\":\"burg\", \n   \"workspace\": {\"name\":\"sf\"},\n   \"format\":\"sld\",\n   \"languageVersion\":{\"version\":\"1.0.0\"},\n   \"filename\":\"burg.sld\"}}\n"

Example data

Content-Type: application/vnd.ogc.sld+xml
"\n  \n    redflag\n    \n      burg\n      A small red flag\n      A sample of how to use an SVG based symbolizer\n\n      \n        \n          Red flag\n          \n            \n              \n                \n                image/svg+xml\n              \n              \n                20\n              \n            \n          \n        \n\n      \n    \n  \n              \n"

Produces

This API call produces the following media types according to the Accept request header; the media type will be conveyed by the Content-Type response header.

Responses

200

OK StyleWorkspace

Example data

Content-Type: application/xml

Example data

Content-Type: application/json
{"style": 
  {"name":"burg", 
   "workspace": {"name":"sf"},
   "format":"sld",
   "languageVersion":{"version":"1.0.0"},
   "filename":"burg.sld"}}

Example data

Content-Type: application/vnd.ogc.sld+xml

  
    redflag
    
      burg
      A small red flag
      A sample of how to use an SVG based symbolizer

      
        
          Red flag
          
            
              
                
                image/svg+xml
              
              
                20
              
            
          
        

      
    
  
              

Up
get /workspaces/{workspace}/styles
Get a list of styles in a given workspace (getWorkspaceStyles)
Displays a list of all styles in a given workspace. Use the "Accept:" header to specify format or append an extension to the endpoint (example "/workspaces/{workspace}/styles.xml" for XML).

Path parameters

workspace (required)
Path Parameter — Name of workspace

Return type

StyleList

Example data

Content-Type: application/xml
"\n  \n  \n\n"

Example data

Content-Type: application/json
"{\n  \"styles\": {\n    \"style\": [\n      {\n        \"name\": \"burg\",\n        \"href\": \"http://localhost:8080/geoserver/rest/workspaces/sf/styles/burg.json\"\n      },\n      {\n        \"name\": \"dem\",\n        \"href\": \"http://localhost:8080/geoserver/rest/workspaces/sf/styles/dem.json\"\n      }\n    ]\n  }\n}\n"

Produces

This API call produces the following media types according to the Accept request header; the media type will be conveyed by the Content-Type response header.

Responses

200

OK StyleList

Example data

Content-Type: application/xml

  
  

Example data

Content-Type: application/json
{
  "styles": {
    "style": [
      {
        "name": "burg",
        "href": "http://localhost:8080/geoserver/rest/workspaces/sf/styles/burg.json"
      },
      {
        "name": "dem",
        "href": "http://localhost:8080/geoserver/rest/workspaces/sf/styles/dem.json"
      }
    ]
  }
}

Up
post /rest/layers/{layer}/styles
Add a new style (postLayerStyles)
Adds a new style entry to the layer. The style named in styleBody must already exist, and will not be altered by this request.

Path parameters

layer (required)
Path Parameter — Name of the layer to manage styles for

Consumes

This API call consumes the following media types via the Content-Type request header:

Request body

styleBody StyleInfoPost (required)
Body Parameter — Style body information naming an existing style to add to the layer

Query parameters

default (optional)
Query Parameter — Whether to make this the default style for the layer. default: false

Responses

201

Created

Up
post /styles/{style}
(postStyle)
Invalid. Use PUT to edit a style, or POST with /styles to add a new style.

Path parameters

style (required)
Path Parameter — Name of the style to retrieve.

Responses

405

Method Not Allowed

Up
post /styles
Add a new style (postStyles)

Adds a new style entry to the server. Using POST with the application/xml or application/json content only adds the style info to the catalog and does not upload style content. PUT to /styles/{style} to upload the style in this case.

Use POST with a style file (application/vnd.ogc.sld+xml or application/vnd.ogc.sld+xml for SLD; additional style types are added by extensions) to generate a style info and upload the style all at once. Then seperately PUT the style info at /styles/{style} to make any desired changes to the generated catalog entry. You can also use POST with a ZIP file to upload a SLD 1.0 (application/vnd.ogc.sld+xml) file and any associated icon files, and then separately PUT the style info at /styles/{style}. POST with a ZIP file does not support any other style types.

Consumes

This API call consumes the following media types via the Content-Type request header:

Request body

styleBody StyleInfoPost (required)
Body Parameter

The style body of a request JSON or XML style uploads follow the schema. For example:

  • application/xml:

    <style>
      <name>roads_style</name>
      <filename>roads.sld</filename>
    </style>
    
  • application/json:

    {
      "style": { 
        "name": "roads_style", 
        "filename": "roads.sld"
      }
    }
    

Otherwise, the style body is an actual style:

  • application/zip:

    <ZIP file containing SLD and icons>
    
  • application/vnd.ogc.sld+xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <StyledLayerDescriptor version="1.0.0" 
     xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" 
     xmlns="http://www.opengis.net/sld" 
     xmlns:ogc="http://www.opengis.net/ogc" 
     xmlns:xlink="http://www.w3.org/1999/xlink" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <!-- a Named Layer is the basic building block of an SLD document -->
      <NamedLayer>
        <Name>default_line</Name>
        <UserStyle>
        <!-- Styles can have names, titles and abstracts -->
          <Title>Default Line</Title>
          <Abstract>A sample style that draws a line</Abstract>
          <!-- FeatureTypeStyles describe how to render different features -->
          <!-- A FeatureTypeStyle for rendering lines -->
          <FeatureTypeStyle>
            <Rule>
              <Name>rule1</Name>
              <Title>Blue Line</Title>
              <Abstract>A solid blue line with a 1 pixel width</Abstract>
              <LineSymbolizer>
                <Stroke>
                  <CssParameter name="stroke">#0000FF</CssParameter>
                </Stroke>
              </LineSymbolizer>
            </Rule>
          </FeatureTypeStyle>
        </UserStyle>
      </NamedLayer>
    </StyledLayerDescriptor>
    

Request headers

Query parameters

name (optional)
Query Parameter — The name of the style. Used only when POSTing a style file or ZIP bundle, to determine the name of the style in the catalog. Generated from the filename if not provided.

Responses

201

Created

Up
post /rest/workspaces/{workspace}/styles/{style}
(postWorkspaceStyle)
Invalid. Use PUT to edit a style, or POST with /workspaces/{workspace}/styles to add a new style.

Path parameters

workspace (required)
Path Parameter — Name of the workspace for style definitions
style (required)
Path Parameter — Name of the style to retrieve.

Responses

405

Method Not Allowed

Up
post /workspaces/{workspace}/styles
Add a new style to a given workspace (postWorkspaceStyles)

Adds a new style entry to the server. Using POST with the application/xml or application/json content only adds the style info to the catalog and does not upload style content. PUT to /workspaces/{workspace}/styles/{style} to upload the style in this case.

Use POST with a style file (application/vnd.ogc.sld+xml or application/vnd.ogc.sld+xml for SLD; additional style types are added by extensions) to generate a style info and upload the style all at once. Then seperately PUT the style info at /workspaces/{workspace}/styles/{style} to make any desired changes to the generated catalog entry. You can also use POST with a ZIP file to upload a SLD 1.0 (application/vnd.ogc.sld+xml) file and any associated icon files, and then separately PUT the style info at /workspaces/{workspace}/styles/{style}. POST with a ZIP file does not support any other style types.

Path parameters

workspace (required)
Path Parameter — Name of workspace

Consumes

This API call consumes the following media types via the Content-Type request header:

Request body

styleBody StyleInfoPost (required)
Body Parameter

The style body of a request JSON or XML style uploads follow the schema. For example:

  • application/xml:

    <style>
      <name>roads_style</name>
      <filename>roads.sld</filename>
    </style>
    
  • application/json:

    {
      "style": { 
        "name": "roads_style", 
        "filename": "roads.sld"
      }
    }
    

Otherwise, the style body is an actual style:

  • application/zip:

    <ZIP file containing SLD and icons>
    
  • application/vnd.ogc.sld+xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <StyledLayerDescriptor version="1.0.0" 
     xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" 
     xmlns="http://www.opengis.net/sld" 
     xmlns:ogc="http://www.opengis.net/ogc" 
     xmlns:xlink="http://www.w3.org/1999/xlink" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <!-- a Named Layer is the basic building block of an SLD document -->
      <NamedLayer>
        <Name>default_line</Name>
        <UserStyle>
        <!-- Styles can have names, titles and abstracts -->
          <Title>Default Line</Title>
          <Abstract>A sample style that draws a line</Abstract>
          <!-- FeatureTypeStyles describe how to render different features -->
          <!-- A FeatureTypeStyle for rendering lines -->
          <FeatureTypeStyle>
            <Rule>
              <Name>rule1</Name>
              <Title>Blue Line</Title>
              <Abstract>A solid blue line with a 1 pixel width</Abstract>
              <LineSymbolizer>
                <Stroke>
                  <CssParameter name="stroke">#0000FF</CssParameter>
                </Stroke>
              </LineSymbolizer>
            </Rule>
          </FeatureTypeStyle>
        </UserStyle>
      </NamedLayer>
    </StyledLayerDescriptor>
    

Request headers

Query parameters

name (optional)
Query Parameter — The name of the style. Used only when POSTing a style file or ZIP bundle, to determine the name of the style in the catalog. Generated from the filename if not provided.

Responses

201

Created

Up
put /rest/layers/{layer}/styles
(putLayerStyles)
Invalid. Use POST to modify the styles for a layer.

Path parameters

layer (required)
Path Parameter — Name of the layer to manage styles for

Responses

405

Method Not Allowed

Up
put /styles/{style}
Modify a single style (putStyle)

Modifies a single style. Use the "Accept:" header to specify format or append an extension to the endpoint (example /styles/{style}.xml for XML).

Using PUT with the application/xml or application/json content modifies the style info in the catalog and does not alter the style content. Using PUT with any other format will modify the content of the style. You can also use PUT with a ZIP file to upload a SLD 1.0 (application/vnd.ogc.sld+xml) file and any associated icon files

Path parameters

style (required)
Path Parameter — Name of the style to edit.

Consumes

This API call consumes the following media types via the Content-Type request header:

Request body

styleBody StyleInfoPost (required)
Body Parameter

The style body of a request. For a PUT, only values which should be changed need to be included. JSON or XML style uploads follow the schema, and alter the style configuration. For example:

  • application/xml:

    <style>
      <name>roads_style</name>
      <languageVersion>
        <version>1.0.0</version>
      </languageVersion>
      <filename>roads.sld</filename>
      <legend>
        <width>32</width>
        <height>32</height>
        <format>image/png; charset=UTF-8</format>
        <onlineResource>legend.png</onlineResource>
      </legend>
    </style>
    
  • application/json:

    {
      "style": { 
        "name": "roads_style", 
        "languageVersion": {
          "version": "1.0.0"
        },
        "filename": "roads.sld",
        "legend": {
          "format": "image/png; charset=UTF-8",
          "height": 32,
          "width": 32,
          "onlineResource": "grass_fill.png"
        }
      }
    }
    

Otherwise, the style body is an actual style:

  • application/zip:

    <ZIP file containing SLD and icons>
    
  • application/vnd.ogc.sld+xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <StyledLayerDescriptor version="1.0.0" 
     xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" 
     xmlns="http://www.opengis.net/sld" 
     xmlns:ogc="http://www.opengis.net/ogc" 
     xmlns:xlink="http://www.w3.org/1999/xlink" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <!-- a Named Layer is the basic building block of an SLD document -->
      <NamedLayer>
        <Name>default_line</Name>
        <UserStyle>
        <!-- Styles can have names, titles and abstracts -->
          <Title>Default Line</Title>
          <Abstract>A sample style that draws a line</Abstract>
          <!-- FeatureTypeStyles describe how to render different features -->
          <!-- A FeatureTypeStyle for rendering lines -->
          <FeatureTypeStyle>
            <Rule>
              <Name>rule1</Name>
              <Title>Blue Line</Title>
              <Abstract>A solid blue line with a 1 pixel width</Abstract>
              <LineSymbolizer>
                <Stroke>
                  <CssParameter name="stroke">#0000FF</CssParameter>
                </Stroke>
              </LineSymbolizer>
            </Rule>
          </FeatureTypeStyle>
        </UserStyle>
      </NamedLayer>
    </StyledLayerDescriptor>
    

Query parameters

raw (optional)
Query Parameter — When set to "true", will forgo parsing and encoding of the uploaded style content, and instead the style will be streamed directly to the GeoServer configuration. Use this setting if the content and formatting of the style is to be preserved exactly. May result in an invalid and unusable style if the payload is malformed. Allowable values are "true" or "false" (default). Only used when uploading a style file. default: false

Responses

200

OK

401

Unauthorized

Up
put /styles
(putStyles)
Invalid. Use POST for adding a new style, or use PUT with /styles/{style} to edit/upload an existing style.

Responses

405

Method Not Allowed

Up
put /rest/workspaces/{workspace}/styles/{style}
Modify a single style in a given workspace (putWorkspaceStyle)

Modifies a single style in a given workspace. Use the "Accept:" header to specify format or append an extension to the endpoint (example /workspaces/{workspace}/styles/{style}.xml for XML).

Using PUT with the application/xml or application/json content modifies the style info in the catalog and does not alter the style content. Using PUT with any other format will modify the content of the style. You can also use PUT with a ZIP file to upload a SLD 1.0 (application/vnd.ogc.sld+xml) file and any associated icon files

Path parameters

workspace (required)
Path Parameter — Name of the workspace for style definitions
style (required)
Path Parameter — Name of the style to retrieve.

Consumes

This API call consumes the following media types via the Content-Type request header:

Request body

styleBody StyleInfoPost (required)
Body Parameter

The style body of a request. For a PUT, only values which should be changed need to be included. JSON or XML style uploads follow the schema, and alter the style configuration. For example:

  • application/xml:

    <style>
      <name>roads_style</name>
      <languageVersion>
        <version>1.0.0</version>
      </languageVersion>
      <filename>roads.sld</filename>
      <legend>
        <width>32</width>
        <height>32</height>
        <format>image/png; charset=UTF-8</format>
        <onlineResource>legend.png</onlineResource>
      </legend>
    </style>
    
  • application/json:

    {
      "style": { 
        "name": "roads_style", 
        "languageVersion": {
          "version": "1.0.0"
        },
        "filename": "roads.sld",
        "legend": {
          "format": "image/png; charset=UTF-8",
          "height": 32,
          "width": 32,
          "onlineResource": "grass_fill.png"
        }
      }
    }
    

Otherwise, the style body is an actual style:

  • application/zip:

    <ZIP file containing SLD and icons>
    
  • application/vnd.ogc.sld+xml:

    <?xml version="1.0" encoding="UTF-8"?>
    <StyledLayerDescriptor version="1.0.0" 
     xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" 
     xmlns="http://www.opengis.net/sld" 
     xmlns:ogc="http://www.opengis.net/ogc" 
     xmlns:xlink="http://www.w3.org/1999/xlink" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <!-- a Named Layer is the basic building block of an SLD document -->
      <NamedLayer>
        <Name>default_line</Name>
        <UserStyle>
        <!-- Styles can have names, titles and abstracts -->
          <Title>Default Line</Title>
          <Abstract>A sample style that draws a line</Abstract>
          <!-- FeatureTypeStyles describe how to render different features -->
          <!-- A FeatureTypeStyle for rendering lines -->
          <FeatureTypeStyle>
            <Rule>
              <Name>rule1</Name>
              <Title>Blue Line</Title>
              <Abstract>A solid blue line with a 1 pixel width</Abstract>
              <LineSymbolizer>
                <Stroke>
                  <CssParameter name="stroke">#0000FF</CssParameter>
                </Stroke>
              </LineSymbolizer>
            </Rule>
          </FeatureTypeStyle>
        </UserStyle>
      </NamedLayer>
    </StyledLayerDescriptor>
    

Query parameters

raw (optional)
Query Parameter — When set to "true", will forgo parsing and encoding of the uploaded style content, and instead the style will be streamed directly to the GeoServer configuration. Use this setting if the content and formatting of the style is to be preserved exactly. May result in an invalid and unusable style if the payload is malformed. Allowable values are "true" or "false" (default). Only used when uploading a style file.

Responses

200

OK

401

Unauthorized

Up
put /workspaces/{workspace}/styles
(putWorkspaceStyles)
Invalid. Use POST for adding a new style, or use PUT with /workspaces/{workspace}/styles/{style} to edit/upload an existing style.

Path parameters

workspace (required)
Path Parameter — Name of workspace

Responses

405

Method Not Allowed

Models

[ Jump to Methods ]

Table of Contents

  1. Style - style
  2. StyleInfoPost - style
  3. StyleLayer - style
  4. StyleLayer_layer -
  5. StyleList - styles
  6. StyleListItem - style
  7. StyleWorkspace - style
  8. StyleWorkspace_workspace -
  9. Style_languageVersion -

Style - style Up

name (optional)
String Name of style
format (optional)
String Format of style
languageVersion (optional)
filename (optional)
String File name of the style

StyleInfoPost - style Up

name (optional)
String Name of style
example: roads_style
filename (optional)
String Name of filename containing SLD code
example: roads.sld

StyleLayer - style Up

name (optional)
String Name of style
layer (optional)
format (optional)
String Format of style
languageVersion (optional)
filename (optional)
String File name of the style

StyleLayer_layer - Up

name (optional)
String Name of layer containing the style

StyleList - styles Up

StyleListItem - style Up

name (optional)
String Name of style
href (optional)
String URL to style definition

StyleWorkspace - style Up

name (optional)
String Name of style
workspace (optional)
format (optional)
String Format of style
languageVersion (optional)
filename (optional)
String File name of the style

StyleWorkspace_workspace - Up

name (optional)
String Name of workspace containing the style

Style_languageVersion - Up

version (optional)
String Version of style format