date:20200505

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread Jody Garnett

Thanks for the context, that helps:
- In SLD highlighting is done as a distinct layer, allowing a highlight to
be dawn in a consistent fashion and managed in the z-order (incase content
from several layers is considered selected and needs to be highlighted).
The CQL_Filter is very handy for this case, and indeed was added for this
use.
- In uDig (a desktop environment) the equivalent of a DirectLayer was used
for this purpose; the result was powerful ending up similar to labels where
content from several layers could be floated onto of the map to show
selection.

Given you requirements (a circle) having a specific layer seems fine? But
perhaps I do not see the entire picture yet.
--
Jody Garnett


On Tue, 5 May 2020 at 15:18,  wrote:

> Hi Jody, thanks for start the discuss about this proposal.
>
> The goal of this extension point is to give the possibility to
> enrich/decorate current feature styling.  The feature defined style can be
> maintained as is, and it will be possible to add, for example, a surrounded
> circle marking the feature.
>
> This extension point will make viable an upcoming dynamic features
> highlighting community module.  On this implementation, we'll be able to
> add highlight marks to any-layer current features style based on request
> vendor parameter; so the module will highlight  some features and leave the
> remaining others as default.
>
> Naturally, if other Geotools/Geoserver extension point already allows us
> to make this goal, it would be awesome to save unneeded development.  Do
> you have some lights about how to to this with existing GT/GS extensions?
>
> Thanks for your help :)
>
> Regards,
>
> Fernando Mino
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
>
> ==
>
> Fernando Mino
>
> Software Engineer
>
> GeoSolutions S.A.S.
>
> Via di Montramito 3/A
>
> 55054  Massarosa (LU)
>
> Italy
>
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> 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.
>
>
>
>
> From "Jody Garnett" jody.garn...@gmail.com
> To fernando.m...@geo-solutions.it
> Cc "Geoserver-devel" geoserver-devel@lists.sourceforge.net
> Date Tue, 5 May 2020 14:14:50 -0700
> Subject Re: [Geoserver-devel] GSIP 191 - New extension point in WMS
> rendering to enrich style symbolizers
>
> Happy to review the proposal, but the title is very generic - and
> "processing and enriching" has me curious?
>
> Reading the proposal ends up defining the following callback:
>
> *interface SymbolizersCallback {*
> */** Can modify the list of symbolizers to be painted */*
> *List apply(Feature feature, List
> symbolizers);*
> *}*
>
>
> Are you sure you are working at the right level of abstraction, the
> activity you are doing above is close in spirit to process stylers in the
> streaming renderer?
>
> I am trying to figure out higher level what you are trying to accomplish?
> Are you wishing to make up styles on the fly ... if so the result probably
> cannot be written out out via SLD, and may as well be your own rendering
> engine for a layer. The GeoTools rendering model has DirectLayer for this
> kind of case, used for things like map decorations, or mil2525b.
>
> I think this proposal needs some discussion before being ready to vote.
> --
> Jody Garnett
>
>
> On Tue, 5 May 2020 at 12:11,  wrote:
>
>> Hi Project Steering Committee and Community,
>>
>> I would like to start the voting stage for a new proposal titled "New
>> extension point in WMS rendering to enrich style symbolizers" with assigned
>> code GSIP 191.
>>
>> This is a proposal for adding an extension point for processing and
>> enriching style symbolizers in base to the feature being rendered.
>>
>> The technical detail in the proposal document:
>> https://github.com/geoserver/geoserver/wiki/GSIP-191
>>
>> Naturally, I'll be glad to answer any question or discuss about

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread Jody Garnett

In terms of design it best to do the work in the project responsible for
the abstractions, if not you risk getting broken easily by upstream
changes. It is also nice for the maintainers to have all the cards on the
table in terms of how the class is used, so they can make an informed
decision on making a method protected, or making a new method for your call
back to use.  Andrea is largely responsible for this class, if I was
maintaining it I would want to define strictly any callbacks in
StreamingRenderer so I could understand what it is possible to optimize, or
when I need to go slow to let a callback happen.

We should move the geotools discussion to that list, just in terms of what
you want to accomplish it looks like you may be at the wrong spot (working
with SE symbolizers rather then the java 2d based style

).
--
Jody Garnett


On Tue, 5 May 2020 at 15:27,  wrote:

> About the quick question, since I'm planing to extend StreamingRenderer
> class in Geoserver WMS, I only need to make the processSymbolizers method
> protected (it is currently private).  Do I need to make a Geotools proposal
> for this change?
>
> Is this plan good enough, or it is required to extend the Geotools API for
> handle by-feature interceptors(preprocessing objects), calling them inside
> the processSymbolizers code?
>
> Thanks!
>
> Regards,
>
> Fernando Mino
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
>
> ==
>
> Fernando Mino
>
> Software Engineer
>
> GeoSolutions S.A.S.
>
> Via di Montramito 3/A
>
> 55054  Massarosa (LU)
>
> Italy
>
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> 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.
>
>
>
>
> From "Jody Garnett" jody.garn...@gmail.com
> To fernando.m...@geo-solutions.it
> Cc "Geoserver-devel" geoserver-devel@lists.sourceforge.net
> Date Tue, 5 May 2020 14:41:15 -0700
> Subject Re: [Geoserver-devel] GSIP 191 - New extension point in WMS
> rendering to enrich style symbolizers
>
> Quick question, the proposal indicates you are going to make use of this
> callback "before every code point where the StreamingRenderer Geotools
> class is instanced"...
> But this callback is on a feature by feature basis.
>
> Do you mean to make a geotools proposal to define this callback, and then
> make use of the new API in geoserver?
> --
> Jody Garnett
>
>
> On Tue, 5 May 2020 at 12:11,  wrote:
>
>> Hi Project Steering Committee and Community,
>>
>> I would like to start the voting stage for a new proposal titled "New
>> extension point in WMS rendering to enrich style symbolizers" with assigned
>> code GSIP 191.
>>
>> This is a proposal for adding an extension point for processing and
>> enriching style symbolizers in base to the feature being rendered.
>>
>> The technical detail in the proposal document:
>> https://github.com/geoserver/geoserver/wiki/GSIP-191
>>
>> Naturally, I'll be glad to answer any question or discuss about the
>> proposal and implementation details.
>>
>> Thanks for your vote :)
>>
>> Regards,
>>
>> Fernando Mino
>>
>> ==
>>
>> GeoServer Professional Services from the experts! Visit
>> http://goo.gl/it488V for more information.
>>
>> ==
>>
>> Fernando Mino
>>
>> Software Engineer
>>
>> GeoSolutions S.A.S.
>>
>> Via di Montramito 3/A
>>
>> 55054  Massarosa (LU)
>>
>> Italy
>>
>> phone: +39 0584 962313
>>
>> fax: +39 0584 1660272
>>
>> 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

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread fernando . mino


   About the quick question, since I'm planing to extend StreamingRenderer 
class in Geoserver WMS, I only need to make the processSymbolizers method 
protected (it is currently private).  Do I need to make a Geotools proposal for 
this change?

   Is this plan good enough, or it is required to extend the Geotools API for 
handle by-feature interceptors(preprocessing objects), calling them inside the 
processSymbolizers code?

   Thanks!

   Regards,

   Fernando Mino

   ==

   GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.

   ==

   Fernando Mino

   Software Engineer

   GeoSolutions S.A.S.

   Via di Montramito 3/A

   55054  Massarosa (LU)

   Italy

   phone: +39 0584 962313

   fax: +39 0584 1660272

   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.

   From "Jody Garnett" jody.garn...@gmail.com
   To fernando.m...@geo-solutions.it
   Cc "Geoserver-devel" geoserver-devel@lists.sourceforge.net
   Date Tue, 5 May 2020 14:41:15 -0700
   Subject Re: [Geoserver-devel] GSIP 191 - New extension point in WMS 
rendering to enrich style symbolizers
   Quick question, the proposal indicates you are going to make use of this 
callback "before every code point where the StreamingRenderer Geotools class is 
instanced"...
   But this callback is on a feature by feature basis.
   Do you mean to make a geotools proposal to define this callback, and then 
make use of the new API in geoserver?
   --
   Jody Garnett
   On Tue, 5 May 2020 at 12:11,  wrote:

   Hi Project Steering Committee and Community,

   I would like to start the voting stage for a new proposal titled "New 
extension point in WMS rendering to enrich style symbolizers" with assigned 
code GSIP 191.

   This is a proposal for adding an extension point for processing and 
enriching style symbolizers in base to the feature being rendered.

   The technical detail in the proposal document:

   https://github.com/geoserver/geoserver/wiki/GSIP-191

   Naturally, I'll be glad to answer any question or discuss about the proposal 
and implementation details.

   Thanks for your vote :)

   Regards,

   Fernando Mino

   ==

   GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.

   ==

   Fernando Mino

   Software Engineer

   GeoSolutions S.A.S.

   Via di Montramito 3/A

   55054  Massarosa (LU)

   Italy

   phone: +39 0584 962313

   fax: +39 0584 1660272

   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-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread fernando . mino


   Hi Jody, thanks for start the discuss about this proposal.

   The goal of this extension point is to give the possibility to 
enrich/decorate current feature styling.  The feature defined style can be 
maintained as is, and it will be possible to add, for example, a surrounded 
circle marking the feature.

   This extension point will make viable an upcoming dynamic features 
highlighting community module.  On this implementation, we'll be able to add 
highlight marks to any-layer current features style based on request vendor 
parameter; so the module will highlight  some features and leave the remaining 
others as default.

   Naturally, if other Geotools/Geoserver extension point already allows us to 
make this goal, it would be awesome to save unneeded development.  Do you have 
some lights about how to to this with existing GT/GS extensions?

   Thanks for your help :)

   Regards,

   Fernando Mino

   ==

   GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.

   ==

   Fernando Mino

   Software Engineer

   GeoSolutions S.A.S.

   Via di Montramito 3/A

   55054  Massarosa (LU)

   Italy

   phone: +39 0584 962313

   fax: +39 0584 1660272

   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.

   From "Jody Garnett" jody.garn...@gmail.com
   To fernando.m...@geo-solutions.it
   Cc "Geoserver-devel" geoserver-devel@lists.sourceforge.net
   Date Tue, 5 May 2020 14:14:50 -0700
   Subject Re: [Geoserver-devel] GSIP 191 - New extension point in WMS 
rendering to enrich style symbolizers
   Happy to review the proposal, but the title is very generic - and 
"processing and enriching" has me curious?
   Reading the proposal ends up defining the following callback:

   interface SymbolizersCallback {

  /** Can modify the list of symbolizers to be painted */

  List apply(Feature feature, List symbolizers);

   }

   Are you sure you are working at the right level of abstraction, the activity 
you are doing above is close in spirit to process stylers in the streaming 
renderer?
   I am trying to figure out higher level what you are trying to accomplish? 
Are you wishing to make up styles on the fly ... if so the result probably 
cannot be written out out via SLD, and may as well be your own rendering engine 
for a layer. The GeoTools rendering model has DirectLayer for this kind of 
case, used for things like map decorations, or mil2525b.
   I think this proposal needs some discussion before being ready to vote.
   --
   Jody Garnett
   On Tue, 5 May 2020 at 12:11,  wrote:

   Hi Project Steering Committee and Community,

   I would like to start the voting stage for a new proposal titled "New 
extension point in WMS rendering to enrich style symbolizers" with assigned 
code GSIP 191.

   This is a proposal for adding an extension point for processing and 
enriching style symbolizers in base to the feature being rendered.

   The technical detail in the proposal document:

   https://github.com/geoserver/geoserver/wiki/GSIP-191

   Naturally, I'll be glad to answer any question or discuss about the proposal 
and implementation details.

   Thanks for your vote :)

   Regards,

   Fernando Mino

   ==

   GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.

   ==

   Fernando Mino

   Software Engineer

   GeoSolutions S.A.S.

   Via di Montramito 3/A

   55054  Massarosa (LU)

   Italy

   phone: +39 0584 962313

   fax: +39 0584 1660272

   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

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread Jody Garnett

Quick question, the proposal indicates you are going to make use of this
callback "before every code point where the StreamingRenderer Geotools
class is instanced"...
But this callback is on a feature by feature basis.

Do you mean to make a geotools proposal to define this callback, and then
make use of the new API in geoserver?
--
Jody Garnett


On Tue, 5 May 2020 at 12:11,  wrote:

> Hi Project Steering Committee and Community,
>
> I would like to start the voting stage for a new proposal titled "New
> extension point in WMS rendering to enrich style symbolizers" with assigned
> code GSIP 191.
>
> This is a proposal for adding an extension point for processing and
> enriching style symbolizers in base to the feature being rendered.
>
> The technical detail in the proposal document:
> https://github.com/geoserver/geoserver/wiki/GSIP-191
>
> Naturally, I'll be glad to answer any question or discuss about the
> proposal and implementation details.
>
> Thanks for your vote :)
>
> Regards,
>
> Fernando Mino
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
>
> ==
>
> Fernando Mino
>
> Software Engineer
>
> GeoSolutions S.A.S.
>
> Via di Montramito 3/A
>
> 55054  Massarosa (LU)
>
> Italy
>
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> 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-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread Jody Garnett

Happy to review the proposal, but the title is very generic - and
"processing and enriching" has me curious?

Reading the proposal ends up defining the following callback:

*interface SymbolizersCallback {*
*/** Can modify the list of symbolizers to be painted */*
*List apply(Feature feature, List symbolizers);*
*}*


Are you sure you are working at the right level of abstraction, the
activity you are doing above is close in spirit to process stylers in the
streaming renderer?

I am trying to figure out higher level what you are trying to accomplish?
Are you wishing to make up styles on the fly ... if so the result probably
cannot be written out out via SLD, and may as well be your own rendering
engine for a layer. The GeoTools rendering model has DirectLayer for this
kind of case, used for things like map decorations, or mil2525b.

I think this proposal needs some discussion before being ready to vote.
--
Jody Garnett


On Tue, 5 May 2020 at 12:11,  wrote:

> Hi Project Steering Committee and Community,
>
> I would like to start the voting stage for a new proposal titled "New
> extension point in WMS rendering to enrich style symbolizers" with assigned
> code GSIP 191.
>
> This is a proposal for adding an extension point for processing and
> enriching style symbolizers in base to the feature being rendered.
>
> The technical detail in the proposal document:
> https://github.com/geoserver/geoserver/wiki/GSIP-191
>
> Naturally, I'll be glad to answer any question or discuss about the
> proposal and implementation details.
>
> Thanks for your vote :)
>
> Regards,
>
> Fernando Mino
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
>
> ==
>
> Fernando Mino
>
> Software Engineer
>
> GeoSolutions S.A.S.
>
> Via di Montramito 3/A
>
> 55054  Massarosa (LU)
>
> Italy
>
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> 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-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

2020-05-05 Thread fernando . mino


   Hi Project Steering Committee and Community,

   I would like to start the voting stage for a new proposal titled "New 
extension point in WMS rendering to enrich style symbolizers" with assigned 
code GSIP 191.

   This is a proposal for adding an extension point for processing and 
enriching style symbolizers in base to the feature being rendered.

   The technical detail in the proposal document:

   https://github.com/geoserver/geoserver/wiki/GSIP-191

   Naturally, I'll be glad to answer any question or discuss about the proposal 
and implementation details.

   Thanks for your vote :)

   Regards,

   Fernando Mino

   ==

   GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.

   ==

   Fernando Mino

   Software Engineer

   GeoSolutions S.A.S.

   Via di Montramito 3/A

   55054  Massarosa (LU)

   Italy

   phone: +39 0584 962313

   fax: +39 0584 1660272

   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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9606) JdbcStore: allow directories to be automatically cached

2020-05-05 Thread Niels Charlier (JIRA)

Niels Charlier ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1d2c4019-de4e-4624-8b27-2486941601cf
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 ) / New Feature ( 
https://osgeo-org.atlassian.net/browse/GEOS-9606?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 ) GEOS-9606 ( 
https://osgeo-org.atlassian.net/browse/GEOS-9606?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 ) JdbcStore: allow directories to be automatically cached ( 
https://osgeo-org.atlassian.net/browse/GEOS-9606?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 )

Issue Type: New Feature Assignee: Unassigned Components: JDBCStore Created: 
05/May/20 3:10 PM Priority: Medium Reporter: Niels Charlier ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1d2c4019-de4e-4624-8b27-2486941601cf
 )

Now files are cached by calling the file() or dir() method, so that they can be 
passed on to libraries that can only handle files, such as SLD.

But this feature doesn't work when users have to provide a path via 
configuration, to for example an Application Mapping File, because application 
schema datastore is in geotools and not resource aware.

The new feature would keep some resource automatically cached on the file 
system at all times. It would be specified in the same manner as 
ignoreDirectories which bypasses the jdbcstore for some directories. The 
difference being though, is that with the new features the content of the file 
will still remain in the database, and automatically synced between nodes and 
survice re-deployment of a server from scratch.

( 
https://osgeo-org.atlassian.net/browse/GEOS-9606#add-comment?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-9606#add-comment?atlOrigin=eyJpIjoiMzBiYmFjYzg1MDUxNDI0ODk5OWI0OGYzODIxZmJjZmEiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- 
sha1:bfbb988 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9605) WFS serves deformed data when store is 4D (at least postgis and shp)

2020-05-05 Thread Richard Duivenvoorde (JIRA)

Richard Duivenvoorde ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A962dcbb5-105d-4b46-be3a-260ed24e958b
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-9605?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 ) GEOS-9605 ( 
https://osgeo-org.atlassian.net/browse/GEOS-9605?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 ) WFS serves deformed data when store is 4D (at least postgis and shp) ( 
https://osgeo-org.atlassian.net/browse/GEOS-9605?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.17.0 Assignee: Unassigned Attachments: 
picture1.png, picture2.png, picture3.png, polygon4d.zip, strange.png 
Components: PostGIS, WFS Created: 05/May/20 12:16 PM Environment:

Geoserver bin on linux, Postgis on linux, local shpfile

Priority: Medium Reporter: Richard Duivenvoorde ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A962dcbb5-105d-4b46-be3a-260ed24e958b
 )

A client received some shapefiles, stored those in Postgis (via drag and drop 
in QGIS) and published in Geoserver.
While the WMS output was right (these were thousands of square buildings), the 
WFS showed very strange huge polygons:

( https://osgeo-org.atlassian.net/secure/attachment/33475/33475_strange.png )

After some investigation, it appeared that the shapefile was '4D' (you can 
create a new shapefile in QGIS, and tell it to add Z or M or both, attached is 
an example set: polygon4d.zip ( 
https://osgeo-org.atlassian.net/secure/attachment/33476/33476_polygon4d.zip ) ).

As you can see below the coordinates in the db are 4D:

id_0|geom   
 
|
  1|MULTIPOLYGON(((4.7418850506254 52.973914531383926 0 0,5.3187909469922845 
52.664355269918765 0 0,5.431357
  2|MULTIPOLYGON(((5.684633710542017 52.959843655862784 0 0,6.036405598570606 
53.26940291732794 0 0,6.655524
  3|MULTIPOLYGON(((5.079586063132845 51.890457116255874 0 0,5.557995830851724 
51.693464858959864 0 0,5.33286

>From the WFS the zero's are taken into account in the preparation of 2D 
>coordinates:

52.97391453 4.74188505 0 52.66435527 5.31879095 0 52.28444163 
5.43135795 0 52.56585914 4.58710542 0 52.97391453 4.74188505 0

Giving rise to pictures like:

( https://osgeo-org.atlassian.net/secure/attachment/33474/33474_picture1.png )

purple polygons are real data (prepared shp), the orange ones are deformed ones.

Looking at:

( https://osgeo-org.atlassian.net/secure/attachment/33473/33473_picture2.png )

You see it is using 0 as either x or y of coordinate pairs.

Publishing the attached shp's OR adding them to postgis gives these results.

BUT: the strange thing is that the WMS output (below in the layer preview) is 
just right:

( https://osgeo-org.atlassian.net/secure/attachment/33472/33472_picture3.png )

If I'm correct OGC-WFS is either 2D or 3D only???
So I understand this is a data issue also, so not sure what a reasonable 
solution is:

* maybe geoserver/geotools can test a store of layers in the store if they are 
more then 3D and maybe give a warning?
* maybe the 3D and 4D coordinate could be ignored for WFS (like it is doing for 
WMS?)

As said: easy reproducable by just using attached shp. Also postgis is doing 
this.

( 
https://osgeo-org.atlassian.net/browse/GEOS-9605#add-comment?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-9605#add-comment?atlOrigin=eyJpIjoiMTlhMTNiNWEyN2Y0NGZkMDk0NGY5ZWQwYjBlYjZkMWIiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- 
sha1:bfbb988 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

Re: [Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

[Geoserver-devel] GSIP 191 - New extension point in WMS rendering to enrich style symbolizers

[Geoserver-devel] [JIRA] (GEOS-9606) JdbcStore: allow directories to be automatically cached

[Geoserver-devel] [JIRA] (GEOS-9605) WFS serves deformed data when store is 4D (at least postgis and shp)

9 matches

Site Navigation

Mail list logo

Footer information