[GeoSciML] using SLDs - big problem with OneGeology layer naming conventions

Simon.Cox at csiro.au Simon.Cox at csiro.au
Mon Oct 15 17:58:29 EDT 2012

ESRI fail?

Simon Cox

Sent from my phone so please excuse typos.

-----Original Message-----
From: Steve Richard [steve.richard at azgs.az.gov]
Received: Tuesday, 16 Oct 2012, 2:06
To: A mailing list for GeoSciML [geosciml at lists.opengeospatial.org]
Subject: [GeoSciML] using SLDs - big problem with OneGeology layer naming conventions

Hi everyone-

I've been trying to get SLD's assembled as examples for OneGeology services using GeoSciML-portrayal. OneGeology requires WMS layers to be named with a pattern that results in layer names in each service being unique (see http://www.onegeology.org/wmsCookbook/2_5.html), e.g. USA_USGIN_3M_Lithostratigraphy.  From the experimenting I've done, looking at the OGC spec, GeoServer, and ArcGIS server documentation, it looks like the 'sld:NamedLayer' value in an SLD has to match one of the layer names in the WMS you want to apply the SLD to.

The effect is that the SLD will have to be customized for each OneGeology WMS you want to use it against, because the layer names will be unique to each service.  This greatly complicates the work for generating a client that uses SLD to customize map portrayals from OneGeology services.

Am I missing something here, or does oneGeology need to require additional layers in each service that are named something like SLD_lithology and SLD_age, so one SLD file can be applied to multiple services....


WMS request:

In the SLD:
<sld:StyledLayerDescriptor xmlns:gml="....">

In the WMS GetCapabilities:
              <Title><![CDATA[AZGS USGIN Geology]]></Title>
              <BoundingBox ...>
              <Layer queryable="1">

Stephen M Richard
Arizona Geological Survey
416 W. congress #100
Tucson, AZ
AZGS: 520-770-3500
Office: 520-209-4127
FAX: 520-770-3505

More information about the GeoSciML mailing list