Re: [Geoserver-users] Variable substitution in SLD for geoserver 2.13 RasterSymbolizer ChannelSelection

2018-04-11 Thread Andrea Aime
Hi,
the SLD schema does not allow to specify a function inside the channel
selection, we have extended bits
and pieces in raster symbolizer to work off expressions, but I don't think
channel selection is one that got
worked on, I had a quick pick at the SLD parsing code and it appears to
only work off a simple name.

If you are interested in having that supported, see this process:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Cheers
Andrea



On Tue, Apr 10, 2018 at 3:06 AM, Roboubi, Shahin <
srobo...@mdacorporation.com> wrote:

> This is a cross-post from https://gis.stackexchange.com/
> questions/278774/variable-substitution-in-sld-for-geoserver-2-13-
> rastersymbolizer-channelselectio as I was told that this may be a better
> place to ask this question:
>
>
>
> I'm trying to publish a layer with a style that allows the extended WMS
> request to specify what image bands to map to the RGB values. Based on
> existing examples I assumed that my SLD should have something like the
> following RasterSymbolizer element:
>
>
>
> **
>
> **
>
> **
>
> **
>
> *  *
>
> *   redchan*
>
> *   1*
>
> *  *
>
> **
>
> *  ...*
>
>
>
> But the SLD validation fails with the following error:
>
>
>
> *Element 'SourceChannelName' is a simple type, so it must have no element
> information item [children]*
>
>
>
> I am following this documentation:
>
>
>
> http://docs.geoserver.org/stable/en/user/styling/sld/
> reference/rastersymbolizer.html http://docs.geoserver.org/
> stable/en/user/styling/sld/extensions/substitution.html
>
>
>
> Is there a way to do this or is it not supported for the ChannelSelection
> element? Are there any more examples and/or documentation for SLD variable
> substitution that I can look at?
>
>
>
> Thanks,
>
> Shahin
>
> This electronic correspondence, including any attachments, is intended
> solely for the use of the intended recipient(s) and may contain legally
> privileged, proprietary and/or confidential information. If you are not the
> intended recipient, please immediately notify the sender by reply e-mail
> and permanently delete all copies of this electronic correspondence and
> associated attachments. Any use, disclosure, dissemination, distribution or
> copying of this electronic correspondence and any attachments for any
> purposes that have not been specifically authorized by the sender is
> strictly prohibited.
>
> 
> --
> 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
>
> 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
>
>
> Geoserver-users@lists.sourceforge.net
> 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

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 

[Geoserver-users] Variable substitution in SLD for geoserver 2.13 RasterSymbolizer ChannelSelection

2018-04-09 Thread Roboubi, Shahin
This is a cross-post from 
https://gis.stackexchange.com/questions/278774/variable-substitution-in-sld-for-geoserver-2-13-rastersymbolizer-channelselectio
 as I was told that this may be a better place to ask this question:

I'm trying to publish a layer with a style that allows the extended WMS request 
to specify what image bands to map to the RGB values. Based on existing 
examples I assumed that my SLD should have something like the following 
RasterSymbolizer element:



  

  
   redchan
   1
  

  ...

But the SLD validation fails with the following error:

Element 'SourceChannelName' is a simple type, so it must have no element 
information item [children]

I am following this documentation:

http://docs.geoserver.org/stable/en/user/styling/sld/reference/rastersymbolizer.html
 
http://docs.geoserver.org/stable/en/user/styling/sld/extensions/substitution.html

Is there a way to do this or is it not supported for the ChannelSelection 
element? Are there any more examples and/or documentation for SLD variable 
substitution that I can look at?

Thanks,
Shahin

This electronic correspondence, including any attachments, is intended solely 
for the use of the intended recipient(s) and may contain legally privileged, 
proprietary and/or confidential information. If you are not the intended 
recipient, please immediately notify the sender by reply e-mail and permanently 
delete all copies of this electronic correspondence and associated attachments. 
Any use, disclosure, dissemination, distribution or copying of this electronic 
correspondence and any attachments for any purposes that have not been 
specifically authorized by the sender is strictly prohibited.
--
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

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


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users