Re: [Geoserver-users] Legend issue - multiple symbols for cased lines
Actually it turns out that for our particular case (cased polygon outlines) the visual quality of simply having two LIneSymbolizers in the same rule is acceptable (although obviously not ideal where polygons meet). And this of course produces a correct Legend. So we'll go with this for now. On Thu, Feb 23, 2017 at 10:59 AM, Martin Davis wrote: > Makes sense, Andrea. > > In this particular case the rules are as simple as can be - no filters or > scale dependency. So that should be the easiest case to handle. > > I can see how this could be hard to do for complex rules. But then again, > if the rules are different, the Legend should probably show separate > entries for them. > > Not sure I'll be able to rustle up funding to work on this, but I'll give > it a try. > > On Thu, Feb 23, 2017 at 10:36 AM, Andrea Aime < > andrea.a...@geo-solutions.it> wrote: > >> On Thu, Feb 23, 2017 at 7:19 PM, Martin Davis wrote: >> >>> As I understand it, the recommended approach for producing "cased" lines >>> (e.g. for roads or polygon outlines) is to specify each different line >>> style in a separate FeatureTypeStyle. >>> >>> However, this seems to produce Legend graphics with the different line >>> styles on separate lines. (See attached map tile and legend). >>> >>> Is this a known issue? Any workaround or fix? >>> >> >> Well know issue. Fix is not trivial (not at all), but I have something in >> mind. >> >> So, the two feature type styles are painted separately, and might be >> completely unrelated... like, for example, two feature type styles >> could be used to z order features that should appear in the back and in >> the front. >> >> So one would have to compare rules in higher FTS with the lower ones, and >> if they are a match, merge the >> symbolizer from the higher FTS with the lower rules, making the higher >> fts rule disappear. >> Basically, restructure the SLD so that you end up with a single FTS. >> >> The tricky part is defining what a "match" is. In general, it's taking >> the filters of the two rules, combining them, >> and determining that they are not "logically empty". The >> SimplifyingFilterVisitor has some symbolic evaluation >> capabilities, but they are limited and sometimes expensive. >> >> I think you can imagine how this can easily spiral out of control with >> very complex styles (having many FTS layers). >> Still, I'd give it a try, maybe trying to constrain the application of >> this logic to some "sane-ish" simpler case. >> >> Cheers >> Andrea >> >> >> -- >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> phone: +39 0584 962313 <+39%200584%20962313> >> fax: +39 0584 1660272 <+39%200584%20166%200272> >> mob: +39 339 8844549 <+39%20339%20884%204549> >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* >> >> Le informazioni contenute in questo messaggio di posta elettronica e/o >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il >> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >> darcene notizia via e-mail e di procedere alla distruzione del messaggio >> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, >> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >> principi dettati dal D.Lgs. 196/2003. >> >> >> >> The information in this message and/or attachments, is intended solely >> for the attention and use of the named addressee(s) and may be confidential >> or proprietary in nature or covered by the provisions of privacy act >> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection >> Code).Any use not in accord with its purpose, any disclosure, reproduction, >> copying, distribution, or either dissemination, either whole or partial, is >> strictly forbidden except previous formal approval of the named >> addressee(s). If you are not the intended recipient, please contact >> immediately the sender by telephone, fax or e-mail and delete the >> information in this message that has been received in error. The sender >> does not give any warranty or accept liability as the content, accuracy or >> completeness of sent messages and accepts no responsibility for changes >> made after they were sent or for other risks which arise as a result of >> e-mail transmission, viruses, etc. >> >> --- >> > > -- Check out the vibrant tech community on one of the world's most engaging te
Re: [Geoserver-users] Legend issue - multiple symbols for cased lines
Makes sense, Andrea. In this particular case the rules are as simple as can be - no filters or scale dependency. So that should be the easiest case to handle. I can see how this could be hard to do for complex rules. But then again, if the rules are different, the Legend should probably show separate entries for them. Not sure I'll be able to rustle up funding to work on this, but I'll give it a try. On Thu, Feb 23, 2017 at 10:36 AM, Andrea Aime wrote: > On Thu, Feb 23, 2017 at 7:19 PM, Martin Davis wrote: > >> As I understand it, the recommended approach for producing "cased" lines >> (e.g. for roads or polygon outlines) is to specify each different line >> style in a separate FeatureTypeStyle. >> >> However, this seems to produce Legend graphics with the different line >> styles on separate lines. (See attached map tile and legend). >> >> Is this a known issue? Any workaround or fix? >> > > Well know issue. Fix is not trivial (not at all), but I have something in > mind. > > So, the two feature type styles are painted separately, and might be > completely unrelated... like, for example, two feature type styles > could be used to z order features that should appear in the back and in > the front. > > So one would have to compare rules in higher FTS with the lower ones, and > if they are a match, merge the > symbolizer from the higher FTS with the lower rules, making the higher fts > rule disappear. > Basically, restructure the SLD so that you end up with a single FTS. > > The tricky part is defining what a "match" is. In general, it's taking the > filters of the two rules, combining them, > and determining that they are not "logically empty". The > SimplifyingFilterVisitor has some symbolic evaluation > capabilities, but they are limited and sometimes expensive. > > I think you can imagine how this can easily spiral out of control with > very complex styles (having many FTS layers). > Still, I'd give it a try, maybe trying to constrain the application of > this logic to some "sane-ish" simpler case. > > Cheers > Andrea > > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > --- > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Legend issue - multiple symbols for cased lines
On Thu, Feb 23, 2017 at 7:19 PM, Martin Davis wrote: > As I understand it, the recommended approach for producing "cased" lines > (e.g. for roads or polygon outlines) is to specify each different line > style in a separate FeatureTypeStyle. > > However, this seems to produce Legend graphics with the different line > styles on separate lines. (See attached map tile and legend). > > Is this a known issue? Any workaround or fix? > Well know issue. Fix is not trivial (not at all), but I have something in mind. So, the two feature type styles are painted separately, and might be completely unrelated... like, for example, two feature type styles could be used to z order features that should appear in the back and in the front. So one would have to compare rules in higher FTS with the lower ones, and if they are a match, merge the symbolizer from the higher FTS with the lower rules, making the higher fts rule disappear. Basically, restructure the SLD so that you end up with a single FTS. The tricky part is defining what a "match" is. In general, it's taking the filters of the two rules, combining them, and determining that they are not "logically empty". The SimplifyingFilterVisitor has some symbolic evaluation capabilities, but they are limited and sometimes expensive. I think you can imagine how this can easily spiral out of control with very complex styles (having many FTS layers). Still, I'd give it a try, maybe trying to constrain the application of this logic to some "sane-ish" simpler case. Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Legend issue - multiple symbols for cased lines
As I understand it, the recommended approach for producing "cased" lines (e.g. for roads or polygon outlines) is to specify each different line style in a separate FeatureTypeStyle. However, this seems to produce Legend graphics with the different line styles on separate lines. (See attached map tile and legend). Is this a known issue? Any workaround or fix? -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
