<div dir="ltr">Hi Andrea, <br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 8, 2013 at 12:57 PM, Andrea Aime <span dir="ltr"><<a href="mailto:andrea.aime@geo-solutions.it" target="_blank">andrea.aime@geo-solutions.it</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>On Wed, May 8, 2013 at 12:33 PM, Giuseppe Sucameli <span dir="ltr"><<a href="mailto:brush.tyler@gmail.com" target="_blank">brush.tyler@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>IMHO the displacement shouldn't be used in that way, as empty space between graphics, though the SE1.1 specs doesn't define a proper tag to do that... In fact the Graphic->Displacement tag is already used in other contexts with the meaning of "distance in pixels from the hot-spot", not as space around the graphic symbol neither as offset between neighbour graphics.<br>
</div></div></div></div></blockquote><div><br></div></div><div>Right, but at the same time, the SE does not say how to use it in GraphicFill, so one is free to interpret.</div></div></div></div></blockquote><div><br></div>
<div>Not at all, it says:<br><br>""" The GraphicFill element both indicates that a stipple-fill repeated graphic will be used and specifies the fill graphic. [...] A “graphic” can be defined very informally as “a little picture”. The appearance of the graphic is defined with the embedded Graphic element, which is discussed in Subclause 11.3.2. """<br>
</div><div><br>so the meaning of Graphic elements is supposed to be the same for both GraphicFill and GraphicStroke.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>For example, GeoServer does not need SE 1.1 gap and InitialGap in graphic strokes because it uses the dasharray for that, another thing that is already in the SLD 1.0 spec and that had no proper definition of usage in combination with graphicstroke (moreover, it's more flexible than the simple gap syntax, one can create irregular symbol along lines, something like two circle, space, one circle, space, repeat).</div>
</div></div></div></blockquote><div><br></div><div>It's surely more flexible, but I've few inventiveness. For me a dash is a dash, so those dash-something elements should be used to render dashes, not graphic strokes. From my side I would draw both a graphic stroke and a dash line, BTW the XML schema allows to put GraphicStroke and SvgParameters toghether without explain how it must behave. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>
<div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I would define 2 new tags as GraphicFill tag's children, like it's already done in the GraphicStroke tag. <br>
GraphicStroke has Gap and InitialGap, we should use the same approach.</div>
</div></div></div></blockquote><div><br></div></div><div>Extending SLD is a minefield, what happens if OGC releases a corrigendum that adds the same tags, but with a slightly different semantic?</div></div></div></div></blockquote>
<div><br></div><div>The same that would happen if OGC defines what dasharray/dashoffset elements must be used for.<br>I agree with you extending SLD should be avoided, additions to GraphicFill tag could happen soon:<br>
""" Additional parameters for the GraphicFill may be provided in the future to provide more control the exact style of filling. """</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>The way we handle extensions in GeoServer is to use a VendorOptions tag, which can accomodate key/value pairs, </div></div></div></div></blockquote><div>
<br></div><div>We do the same in QGIS, and even the tag name it's the same! ;)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra"><div class="gmail_quote"><div>in this case we could have something like:</div><div><br></div><div><PolygonSymbolizer></div><div> ...</div><div> <VendorOption key="gapAbove">10</VendorOption></div>
</div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>
<VendorOption key="gapBelow">5</VendorOption><br></div><div> <VendorOption key="gapRight">5</VendorOption><br></div><div> <VendorOption key="gapLeft">15</VendorOption><br>
</div><div></PolygonSymbolizer></div></div></div></div></blockquote><div><br></div><div>s/key/name/<br><br></div><div>We already have a <VendorOption name="distance">20,15</VendorOption> that handle the distance between graphics in fill, but we are open to a shared naming convention, as far as possible.<br>
</div><div><br></div><div>Cheers.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>
Cheers</div><div>Andrea</div></div><div><br></div>-- <br><div dir="ltr"><div>==</div><div>GeoServer training in Milan, 6th & 7th June 2013! Visit <a href="http://geoserver.geo-solutions.it/" style="color:rgb(17,85,204)" target="_blank">http://geoserver.geo-solutions.it</a> for more information.<br>
==<br></div><div><br></div><div>Ing. Andrea Aime </div><div>@geowolf</div><div>Technical Lead</div><div><br></div><div>GeoSolutions S.A.S.</div><div>Via Poggio alle Viti 1187</div><div>55054 Massarosa (LU)</div><div>Italy</div>
<div>phone: <a href="tel:%2B39%200584%20962313" value="+390584962313" target="_blank">+39 0584 962313</a></div><div>fax: <a href="tel:%2B39%200584%201660272" value="+3905841660272" target="_blank">+39 0584 1660272</a></div>
<div>mob: <a href="tel:%2B39%20%C2%A0339%208844549" value="+393398844549" target="_blank">+39 339 8844549</a></div><div><br></div><div><a href="http://www.geo-solutions.it" target="_blank">http://www.geo-solutions.it</a></div>
<div><a href="http://twitter.com/geosolutions_it" target="_blank">http://twitter.com/geosolutions_it</a></div>
<div><br></div><div>-------------------------------------------------------</div></div>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Giuseppe Sucameli
</div></div></div>