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

Steve Richard steve.richard at azgs.az.gov
Mon Oct 15 19:56:24 EDT 2012


That's what I though initially, but after some research it looks like it
might actually be consistent with SLD design...
stee

> -----Original Message-----
> From: Simon.Cox at csiro.au [mailto:Simon.Cox at csiro.au]
> Sent: Monday, October 15, 2012 2:58 PM
> To: geosciml at lists.opengeospatial.org; steve.richard at azgs.az.gov
> Subject: RE: [GeoSciML] using SLDs - big problem with OneGeology layer
naming
> conventions
> 
> ESRI fail?
> 
> Simon Cox
> CSIRO
> 
> 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....
> 
> steve
> 
> 
> Example:
> WMS request:
> http://services.azgs.az.gov/ArcGIS/services/OneGeology/AZGS_USGIN_Geology
> /MapServer/WMSServer?request=GetMap&service=WMS&version=1.3.0&&CRS
> =CRS:84&BBOX=-114,28,-
> 66,45&WIDTH=1765&HEIGHT=1000&STYLES=geology-
> lithology&FORMAT=image/png&LAYERS=USA_USGIN_3M_Lithostratigraphy&SL
> D=http://schemas.usgin.org/schemas/slds/CGISedimentLithology0000.sld
> 
> In the SLD:
> <sld:StyledLayerDescriptor xmlns:gml="....">
>             <sld:NamedLayer>
>
<sld:Name>USA_USGIN_3M_Lithostratigraphy</sld:Name>
>                         <sld:UserStyle>
>                                     <sld:Name>geology-lithology</sld:Name>
> <rules...>
> 
> In the WMS GetCapabilities:
> <Layer>
>         <Name>AZGS_USGIN_Geology</Name>
>               <Title><![CDATA[AZGS USGIN Geology]]></Title>
>               <CRS>....</CRS>
>               <EX_GeographicBoundingBox>...</EX_GeographicBoundingBox>
>               <BoundingBox ...>
>               <Layer queryable="1">
>
<Name><![CDATA[USA_USGIN_3M_Lithostratigraphy]]></Name>
> 
> 
> 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