Hi Ian, the syntax is correct, it just happens to be SLD 1.1 and uses the new external mark syntax (the char code is in there). I believe it's mostly an issue of font install
Cheres Andrea On Tue, Jan 8, 2019 at 6:37 PM Ian Turton <[email protected]> wrote: > In GeoServer we use a slightly different format to handle ttf marks - see > https://docs.geoserver.org/stable/en/user/styling/sld/extensions/pointsymbols.html#bulk-ttf-marks > > So something like: > > <PointSymbolizer> > <Graphic> > <Mark> > <WellKnownName>ttf://ESRI Default Marker#0x005F</WellKnownName> > <Fill> > <CssParameter name="fill">#354da8</CssParameter> > </Fill> > <Stroke/> > </Mark> > <Size>16</Size> > </Graphic> > </PointSymbolizer> > > > On Tue, 8 Jan 2019 at 17:15, Malena Libman <[email protected]> > wrote: > >> Hi, >> >> I need some help, maybe someone can guide me. >> >> I'm working on Geoserver 2.14.1 on Tomcat 8.5, QGIS 3.4.3-Madeira. >> >> I have a really complex style in ArcGIS (awful) that I was able to import >> to qgis with "slyr" a plugin that takes the *.STYLE and makes it an xml >> style for QGIS. >> >> When I match my polygons in qgis I save that to an sld file. >> >> The file needs some work to be able to work on Geoserver, I know, but I >> have not been able to solve this snippet: >> <Fill> >> <GraphicFill> >> <Graphic> >> <Mark> >> <OnlineResource xlink:href="ttf://ESRI Default >> Marker" xlink:type="simple"/> >> <Format>ttf</Format> >> <MarkIndex>95</MarkIndex> >> <Fill> >> <CssParameter name="fill">#354da8</CssParameter> >> <CssParameter name="stroke-dasharray">15 >> 15</CssParameter> >> </Fill> >> </Mark> >> <Size>8</Size> >> </Graphic> >> </GraphicFill> >> </Fill> >> >> I understand I need to provide the ttf file, but I can't figure out where >> do I need to put it or if this syntax is correct, since I had to make so >> many changes. >> >> Can you guide me to where I might find a solution? Maybe there is >> something in the cookbook I missed... >> >> Attached you will find two files for reference, the original qgis and the >> one I have now that should work if it wasn't for the ttf mark (I think). >> >> Thanks in advance, >> >> Cheers >> >> Malena >> _______________________________________________ >> Geoserver-users mailing list >> >> Please make sure you read the following two resources before posting to >> this list: >> - Earning your support instead of buying it, but Ian Turton: >> http://www.ianturton.com/talks/foss4g.html#/ >> - The GeoServer user list posting guidelines: >> http://geoserver.org/comm/userlist-guidelines.html >> >> If you want to request a feature or an improvement, also see this: >> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >> >> >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> > > > -- > Ian Turton > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Regards, Andrea Aime == 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 ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
