GIS and Media fusion

"The explosive growth of the GeoWeb and geographic information has made GIS powerful media for the general public to communicate, but perhaps more importantly, GIS have also become media for constructive dialogs and interactions about social issues." - Sui & Goodchild

User Tools

Site Tools


ogo:fossgis13

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
ogo:fossgis13 [2013/06/14 16:40]
oertz
ogo:fossgis13 [2013/06/30 10:51]
oertz
Line 161: Line 161:
     * **be careful** when you copy/paste style files to be sure you adapt these names (that'​s a classic trap to forget !)     * **be careful** when you copy/paste style files to be sure you adapt these names (that'​s a classic trap to forget !)
  
-===== Discovering Symbology Encoging further with NamedStyles =====+===== Discovering Symbology Encoging ​1.1 further with NamedStyles =====
   * **creation of another style dedicated to meteocities layer ...**   * **creation of another style dedicated to meteocities layer ...**
     * we create the //​pointCities.xml//​ file in //​DEEGREE_WORKSPACE_ROOT/​styles//​ directory     * we create the //​pointCities.xml//​ file in //​DEEGREE_WORKSPACE_ROOT/​styles//​ directory
Line 406: Line 406:
 </​code>​ </​code>​
  
-  * **see below the final result you should get ...**+  * **see below the intermediary ​result you should get ...**
 {{:​ogo:​ogo:​resultpart1.png|}} {{:​ogo:​ogo:​resultpart1.png|}}
  
-===== Part II : discovering Symbology Encoging further with UserStyles ===== +  * **creation of one more style introducing filtered rule ...** 
-  * [[SLD/SE Part2]]+    * we create the NamedStyle “pointFOSSGIS” based on our NamedStyle “pointCities” by adding a filtered Rule element 
 +    * we add a StyleRef for this new style to meteocities <​FeatureLayer>​ 
 +    * we have now two cartographic rules, each applies to a set of features :  
 +      * the first rule applies only to the city of Rapperswil: by adding a filter to this rule (using the <​ogc:​Filter>​ syntax), we select Rappelswils'​ feature by its ID=0 so as to control the rendering engine to apply an ExternalGraphic based PointSymbolizer to __that feature only__ 
 +      * the second rule applies to all other features of the layer: by adding the <​ElseFilter/>​ element to this rule, we select all the other features that have not been selected by another filtered rule (here it means ID <> 0) and this is to control the rendering engine to apply our previous combination of PointSymbolizer/​TextSymbolizer to all these other features 
 +    * this logic is not different than the common if...then...else statment in programming 
 +    * we test it as usual ! 
 + 
 +<​code>​ 
 +<​FeatureTypeStyle ...> 
 + 
 +  <​Name>​pointFOSSGIS</​Name>​ 
 +  <​Description>​ 
 +    <​Title>​Discover filtered Rule element</​Title>​ 
 +  </​Description>​ 
 +   
 +  <​Rule>​ 
 +    <​ogc:​Filter>​ 
 +      <​ogc:​PropertyIsEqualTo>​ 
 +        <​ogc:​PropertyName>​ID</​ogc:​PropertyName>​ 
 +        <​ogc:​Literal>​0</​ogc:​Literal>​ 
 +      </​ogc:​PropertyIsEqualTo>​ 
 +    </​ogc:​Filter>​ 
 +     
 +    <​PointSymbolizer>​ 
 +      <​Graphic>​ 
 +        <​ExternalGraphic>​ 
 +          <​OnlineResource xlink:​href="​images/​fossgis_logo.png"/>​ 
 +          <​Format>​image/​png</​Format>​ 
 +        </​ExternalGraphic>​ 
 +        <​AnchorPoint>​ 
 +          <​AnchorPointX>​0.2</​AnchorPointX>​ 
 +          <​AnchorPointY>​0.4</​AnchorPointY>​ 
 +        </​AnchorPoint>​ 
 +      </​Graphic>​ 
 +    </​PointSymbolizer>​ 
 +  </​Rule>​ 
 +   
 +  <​Rule>​ 
 +    <​ElseFilter/>​ 
 +    <​PointSymbolizer>​ 
 +      <​Graphic>​ 
 +        <​Mark>​ 
 +          <​WellKnownName>​circle</​WellKnownName>​ 
 +          <​Fill>​ 
 +            <​SvgParameter name="​fill">#​FFFFFF</​SvgParameter>​ 
 +          </​Fill>​ 
 +          <​Stroke>​ 
 +            <​SvgParameter name="​stroke">#​000000</​SvgParameter>​ 
 +            <​SvgParameter name="​stroke-width">​2</​SvgParameter>​ 
 +          </​Stroke>​ 
 +        </​Mark>​ 
 +        <​Size>​6</​Size>​ 
 +      </​Graphic>​ 
 +    </​PointSymbolizer>​ 
 +    <​TextSymbolizer>​ 
 +      <​Label>​ 
 +        <​ogc:​PropertyName>​NAME</​ogc:​PropertyName>​ 
 +      </​Label>​ 
 +      <​LabelPlacement>​ 
 +        <​PointPlacement>​ 
 +          <​Displacement>​ 
 +            <​DisplacementX>​0</​DisplacementX>​ 
 +            <​DisplacementY>​-10</​DisplacementY>​ 
 +          </​Displacement>​ 
 +        </​PointPlacement>​ 
 +      </​LabelPlacement>​ 
 +      <​Fill>​ 
 +        <​SvgParameter name="​fill">#​000000</​SvgParameter> ​        
 +      </​Fill> ​  
 +    </​TextSymbolizer>​ 
 +  </​Rule>​ 
 +   
 +</​FeatureTypeStyle>​ 
 +</​code>​ 
 + 
 +  * **see below the final result you should get ...** 
 +{{:​ogo:​mapfossgis.png|}} 
 + 
 +===== Part II : discovering Symbology Encoging ​1.1 further with UserStyles ===== 
 +**Preliminary : before going to part II, we need to configure on last thing on our deegree3** ​ 
 +  * creation of a deegreeWMS configuration ... 
 +    * we create the mywfs.xml file in DEEGREE_WORKSPACE_ROOT/​services directory 
 +    * it configure the WFS service so that all the underlying FeatureStore can be queried with EPSG:4326 and EPSG:21781 SRS 
 +    * reload deegree3 from the console and test it by requesting : http://​localhost:​8080/​services/​mywfs?​service=WFS&​request=GetCapabilities  
 + 
 +<​code>​ 
 +<​deegreeWFS xmlns="​http://​www.deegree.org/​services/​wfs"​ 
 +    xmlns:​xsi="​http://​www.w3.org/​2001/​XMLSchema-instance"​ configVersion="​3.2.0"​ 
 +    xsi:​schemaLocation="​http://​www.deegree.org/​services/​wfs http://​schemas.deegree.org/​services/​wfs/​3.2.0/​wfs_configuration.xsd">​ 
 + 
 +    <​QueryCRS>​urn:​ogc:​def:​crs:​EPSG::​4326</​QueryCRS>​ 
 +    <​QueryCRS>​urn:​ogc:​def:​crs:​EPSG::​21781</​QueryCRS>​ 
 +     
 +</​deegreeWFS>​ 
 +</​code>​  
 + 
 +**SLD/SE Part2**
  
 +In the following part we will present the UserStyle SLD 1.1 mechanism for client customization while pursueing to discover styling capacities of SE 1.1.
 +  * go to [[SLD/SE Part2]] ...
ogo/fossgis13.txt · Last modified: 2018/05/16 10:05 (external edit)