After some confusion, I discovered this note in the docs:
Note
Currently xlink:href
strings must be valid URLs before expression expansion is performed. This means that the URL cannot be completely provided by an expression. The xlink:href
string must explicitly include at least the prefix http://
http://docs.geoserver.org/latest/en/user/styling/sld/extensions/pointsymbols.html#dynamic-symbolizers
If its a relatively simple change to lift this restriction, I’d be willing to do it. Can someone point me toward the relevant code?
Thanks,
···
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Hi Jason,
I believe that right now the above statement is no more valid… the history of this is complicated and I’m not sure I remember it properly,
but believe it went like this:
- Originally the system allowed any kind of string, allowing dynamic URLs of any kind
- Then someone weaving a OGC labelled baton came and switched the very API to use URL, making it impossible to use addresses that were not a valid URl
- After a while and seeing the issues it caused the “common sense brigade” fought back and added the pure string approach back, making it possible to use whatever address again (or at least hoping to do so)
So could you let us know, what is it that you tried, and that did not work?
Cheers
Andrea
···
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.
So, we have an attribute “symbol” that clearly contains a valid https URL to a valid gif. If we use:
sld:ExternalGraphic
<sld:OnlineResource xmlns:xlink=“http://www.w3.org/1999/xlink” xlink:type=“simple” xlink:href=“${symbol}”/>
sld:Formatimage/gif</sld:Format>
</sld:ExternalGraphic>
We see a bunch of errors in the log saying:
WARN [org.geotools.renderer.style] - Unable to read image at file://styles/https://
If we change it to:
xlink:href=“https://${strSubstringStart(symbol, 8)}”
Works like a charm.
···
On Thu, Jul 26, 2018 at 8:52 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi Jason,
I believe that right now the above statement is no more valid… the history of this is complicated and I’m not sure I remember it properly,
but believe it went like this:
- Originally the system allowed any kind of string, allowing dynamic URLs of any kind
- Then someone weaving a OGC labelled baton came and switched the very API to use URL, making it impossible to use addresses that were not a valid URl
- After a while and seeing the issues it caused the “common sense brigade” fought back and added the pure string approach back, making it possible to use whatever address again (or at least hoping to do so)
So could you let us know, what is it that you tried, and that did not work?
Cheers
Andrea
On Wed, Jul 25, 2018 at 5:00 PM Jason Newmoyer <jason@anonymised.com> wrote:
After some confusion, I discovered this note in the docs:
Note
Currently xlink:href
strings must be valid URLs before expression expansion is performed. This means that the URL cannot be completely provided by an expression. The xlink:href
string must explicitly include at least the prefix http://
http://docs.geoserver.org/latest/en/user/styling/sld/extensions/pointsymbols.html#dynamic-symbolizers
If its a relatively simple change to lift this restriction, I’d be willing to do it. Can someone point me toward the relevant code?
Thanks,
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
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.
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Hum… Does not ring a bell but I’d suggest tracing the code in a debugger and see what happens. Don’t have quick pointers, I’m mostly on mobile this week
Cheers
Andrea
···
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
On Thu, Jul 26, 2018 at 8:52 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi Jason,
I believe that right now the above statement is no more valid… the history of this is complicated and I’m not sure I remember it properly,
but believe it went like this:
- Originally the system allowed any kind of string, allowing dynamic URLs of any kind
- Then someone weaving a OGC labelled baton came and switched the very API to use URL, making it impossible to use addresses that were not a valid URl
- After a while and seeing the issues it caused the “common sense brigade” fought back and added the pure string approach back, making it possible to use whatever address again (or at least hoping to do so)
So could you let us know, what is it that you tried, and that did not work?
Cheers
Andrea
On Wed, Jul 25, 2018 at 5:00 PM Jason Newmoyer <jason@anonymised.com> wrote:
After some confusion, I discovered this note in the docs:
Note
Currently xlink:href
strings must be valid URLs before expression expansion is performed. This means that the URL cannot be completely provided by an expression. The xlink:href
string must explicitly include at least the prefix http://
http://docs.geoserver.org/latest/en/user/styling/sld/extensions/pointsymbols.html#dynamic-symbolizers
If its a relatively simple change to lift this restriction, I’d be willing to do it. Can someone point me toward the relevant code?
Thanks,
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
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.