[Geoserver-users] GeoServer 2.14.2 released

[Torben Barsballe]

We are happy to announce the release of GeoServer 2.14.2
. Downloads are provided (zip

|war

|exe
)
along with docs (html

|pdf
)
and extensions

.

This is a stable release of the GeoServer 2.14 series and is recommended
for all production systems. Users of prior releases of GeoServer are
encouraged to upgrade.

This release is made in conjunction with GeoTools 20.2 and GeoWebCache
1.14.2. Thanks to all who contributed to this release.

For more information please see our release notes (2.14.2

| 2.14.1

|2.14.0

|2.14-RC

).
Improvements and Fixes

This release includes a number of new features and improvements:

   - gs:DownloadEstimator (almost always) returns true when estimating full
   raster downloads at native resolution
   - Cannot create jp2k coverage through rest (IndexOutOfBounds)
   - KML ignores sortBy parameter when querying records
   - NullPointerException when using env() function with LIKE operator in
   CSS filters
   - Can't modify existing GWC blobstore via UI without renaming
   - NPE if a Jiffle Rendering Transformation is used with Channel Selection
   - OpenLayers2 preview does not trigger automatically on IE8
   - Bad rendering with JAI-EXT and Input/Output TransparentColor options
   - Complex MongoDB generated properties are not correctly handlded in SLDs
   - Move the GeoServer ENV Parametrization documentation to a more general
   Section
   - Allow expressions in ColorMapEntry labels for GetLegendGraphic

About GeoServer 2.14 Series

Additional information on the GeoServer 2.14 series:

   - New MongoDB extension
   
added
   - Style editor improvements including side by side editing
   

   - Nearest match support for WMS dimension handling
   

   - Upgrade notes documenting REST API feature type definition change
   

   - State of GeoServer 2.14
    (SlideShare)
   - GeoServer Ecosystem
   
   (SlideShare)
   - GeoServer Developers Workshop
   
   (SlideShare)
___
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

Re: [Geoserver-users] srsName OGC HTTP URI storedquery

[Nuno Oliveira]

Hi,
I have tried to reproduce this but could not, if you wish to give it a
try you can download the data set 
and stored query I used from the following link:
https://drive.google.com/file/d/1uCxzB-8wklx0kd7thLPwT6g9ITPlhvtv/view?
usp=sharing
Best regards,
Nuno Oliveira
On Wed, 2019-01-16 at 15:42 +, Verbeeck Bart (AIV) wrote:
> Dear list
>  
> When I invoke https://inspire.informatievlaanderen.be/overdrachtdiens
> ten/hy-n/wfs?request=GetFeature&typename=hy-
> n:WatercourseLink&srsName=http://www.opengis.net/def/crs/EPSG/0/4258&;
> service=WFS&count=1
>  
> I get GML with  srsName="http://www.opengis.net/def/crs/EPSG/0/4258";
>  
> When I call  a storedquery I get the same result https://inspire.info
> rmatievlaanderen.be/overdrachtdiensten/hy-
> p/wfs?request=GetFeature&Language=dut&CRS=http://www.opengis.net/def/
> crs/EPSG/0/4258&DataSetIdNamespace=informatievlaanderen-
> be&service=WFS&count=1&STOREDQUERY_ID=urn:x-inspire:storedQuery:hy-
> n:GetSpatialDataSet&version=2.0.0&DataSetIdCode=2aed0b7b-890f-47ba-
> 84ec-c0b87227a64c
>  
> But with  srsName="urn:ogc:def:crs:EPSG::4258"
>  
> This means the storedquery ignores my wfs setting (OGC HTTP URI)
> 
>  
> Below you find my stored query definition.
>  
> This happens in 2.13.1 and in 2.14.1
>  
> Is this a geoserver issue, or did I do something wrong?
>  
> Thanks!
>  
> Bart
>  
>  
>  
> 
>      xmlns:xs="http://www.w3.org/2001/XMLSchema";
>     xmlns:fes="http://www.opengis.net/fes/2.0";
>     xmlns:wfs="http://www.opengis.net/wfs/2.0";
>     xmlns:gml="http://www.opengis.net/gml/3.2";
>     xmlns:ows="http://www.opengis.net/ows/1.1";
>     xmlns:xlink="http://www.w3.org/1999/xlink";
>     id="urn:x-inspire:storedQuery:hy-n:GetSpatialDataSet">
> 
> 
> 
> 
> 
> language="urn:ogc:def:queryLanguage:OGC-WFS::WFS_QueryExpression"
> returnFeatureTypes="hy-n:WatercourseLink">
> 
> 
> 
> 
>  
> ___
> 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://w
> ww.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/co
> mm/userlist-guidelines.html
> 
> If you want to request a feature or an improvement, also see this: ht
> tps://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,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
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-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

[Geoserver-users] Retrieving SVG files from Postgres Table and Making Images Links

[Julierme Pinheiro]

Hi GeoServer users,

Looking at GeoServer documentation
,
I got the piece of SLD bellow, but burg02.svg is being retrieved from
$GEOSERVER_DATA_DIR/styles.


I would like to have:
1 - burg02.svg being retrieved from a postgres table;
2 - make a webpage link on burg02.svg through the  SLD file


   
 
   
   image/svg+xml
 
 20
   
 


Any hint on how I could achieve items 1 and 2 will be very appreciated.

Kind regards
___
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

[Geoserver-users] --- FOSSGIS-Konferenz 2019 Dresden - Programm veröffentlicht, Anmeldung eröffnet ---

[Konferenzorganisation]

Sehr geehrte FOSSGIS-Aktive, sehr geehrte FOSSGIS-Anfänger, 
OSM-Begeisterte und Interessierte,


das Programm der FOSSGIS-Konferenz 2019 ist veröffentlicht. Das 
Programmkomitee hat eine vielfältige und interessante Auswahl an 
Beiträgen aus den vielen eingegangenen Vorschlägen zusammengestellt (zum 
Programm: https://www.fossgis-konferenz.de/2019/programm).
Der Ticketverkauf ist ebenfalls eröffnet! 
(https://www.fossgis-konferenz.de/2019/anmeldung)


Vom 13. bis 16. März 2019 tagt die FOSSGIS-Konferenz 2019 in Dresden. 
Sie wird vom gemeinnützigen FOSSGIS e.V., der OpenStreetMap-Community 
und der Hochschule für Technik und Wirtschaft Dresden (HTW Dresden) 
veranstaltet.


Die FOSSGIS-Konferenz ist die im D-A-CH-Raum führende Konferenz für 
Freie und Open Source Software für Geoinformationssysteme sowie für die 
Themen OpenStreetMap und Open Data. An vier Tagen werden in Vorträgen 
für Einsteiger und Experten, Hands-On-Workshops, Demo-Sessions und 
Anwendertreffen Einblicke in die neusten Entwicklungen und 
Anwendungsmöglichkeiten von Softwareprojekten gegeben.


Die Teilnehmeranzahl ist aus Kapazitätsgründen auf 400 Personen 
begrenzt. Aus diesem Grund bitten wir um eine frühzeitige Anmeldung. 
Frühentschlossene profitieren dabei bis zum 06.02.2019 von einem 
Preisnachlass.


Preise FOSSGIS-Konferenz 2019:
   Supporterticket (Unterstützer): ab € 250
   Standardticket (Normalpreis): € 190
   Standardticket (Frühbucherrabatt bis 06.02.2019): € 150
   Studierendenticket, Rentnerticket: € 40
   Community-Ticket: € 0*
   Workshop: € 100
   Workshop (Frühbucherrabatt bis 06.02.2019): € 90
Im Konferenzticket enthalten:  FOSSGIS-Konferenz-Teilnahme, Pausensnack, 
Tasche und wenn bestellt Tagungsband, T-Shirt und Abendveranstaltung 
"Dialoge im Bärenzwinger" (teilnehmerbegrenzt).
(*Das kostenfreie Community-Ticket ist vorgesehen für Aktive aus dem 
Open-Source- und OpenStreetMap-Bereich – Entwickler, aktive Mapper – 
sowie für aktive Helfer bei der Konferenz 2019.)


Am Abend des ersten Konferenztages, dem 13. März 2019, findet die 
Abendveranstaltung "Dialoge im Bärenzwinger" statt. Beachten Sie auch 
die anderen "Social Events" rund um die FOSSGIS: 
https://fossgis-konferenz.de/2019/socialevents/.


Viele weitere Informationen zur FOSSGIS-Konferenz (Programm, Anreise und 
Unterkunft, Anmeldung, Helfermöglichkeiten und Sponsoren) entnehmen Sie 
bitte der Konferenzhomepage: https://www.fossgis-konferenz.de/2019/.


Helfer:
Freiwillige Helfer sind eingeladen und willkommen während der Konferenz 
bei den Videoaufnahmen, als Sessionleiter oder beim Catering zu 
unterstützen. Bei Interesse bitte im Helfersystem 
(https://helfer-2019.fossgis.de/) anmelden und eine E-Mail an 
konferenz-o...@fossgis.de senden. Helfer dürfen das kostenfreie 
"Community-Ticket" buchen.


OSM-Event:
Die Konferenz setzt sich ab Freitagnachmittag mit 
OpenStreetMap-spezifischen Vorträgen fort. Beginn ist 15 Uhr mit dem 
OSM-Quiz. Am 16. März 2019 findet der traditionelle OSM-Samstag als 
OSM-UnKonferenz (BarCamp) statt. Das Programm wird am Samstagmorgen nach 
Begrüßung und Einführung durch die Teilnehmerinnen & Teilnehmer 
gemeinsam festgelegt. Die Teilnahme am Dresdner OSM-Event ist kostenfrei 
und unabhängig von der FOSSGIS-Konferenz möglich. Für eine bessere 
Planung ist eine Anmeldung über das FOSSGIS-Konferenz-Anmeldesystem sehr 
erwünscht. Weitere Informationen zum OSM-Samstag gibt es unter 
https://wiki.openstreetmap.org/wiki/FOSSGIS_2019/OSM-Samstag.


Termine und Informationen:

FOSSGIS-Konferenz 2019: 13.-16.03.2019
Programm: https://www.fossgis-konferenz.de/2019/programm/
Teilnehmeranmeldung: 
https://www.fossgis-konferenz.de/2019/anmeldung/ (Frühbucher bis 
06.02.2019)

Social Events: https://fossgis-konferenz.de/2019/socialevents/
OSM-Samstag: 
https://wiki.openstreetmap.org/wiki/FOSSGIS_2019/OSM-Samstag
Exkursion zum Mathematisch-Physikalischen Salon im Zwinger, 15:30 
Uhr, Infos siehe Social Events.

Alle Informationen: https://www.fossgis-konferenz.de/2019/
Fragen an konferenz-o...@fossgis.de
Twitter: https://twitter.com/FOSSGIS_Konf #FOSSGIS2019

Das FOSSGIS-Konferenz-Organisationsteam freut sich darauf, Sie zu einer 
spannenden FOSSGIS-Konferenz in Dresden begrüßen zu dürfen.



--
...
FOSSGIS-Konferenz - OSM-Samstag - 13.-16. März 2019 in der HTW Dresden.
https://www.fossgis-konferenz.de   https://twitter.com/FOSSGIS_Konf
...


___
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

Re: [Geoserver-users] Geoserver compatibility

[Rich Fecher]

Sidharth,
GeoWave will run in GeoServer 2.14.1, but GeoWave's current support is for
Apache HBase 1.4.x as well as Cloudera HBase 1.2.0 (CDH 5.x) and
Hortonworks HBase 1.1.2. Now that the companies have merged we'd likely be
looking at CDH 6.x support in the future - which is in fact HBase 2.0 and
Hadoop3. However, until AWS EMR updates versions we'd be hesitant to forgo
support for EMR's versions and right now EMR is on HBase 1.4.x and Hadoop
2.8.x.

Stay tuned!
Rich

On Fri, Jan 18, 2019 at 6:57 AM Andrea Aime 
wrote:

> The packages provided at geoserver.org have no support for HBase/Hadoop
> whatsoever.
> However, there are two projects with GeoServer integrations, GeoMesa and
> GeoWave, that seem to have some Hadoop support,
> so you might want to check on their list (or maybe you get lucky and they
> will notice this mail, unfortunately
> you did not cite HBase in the mail subject, so they might not)
>
> Cheers
> Andrea
>
>
> On Fri, Jan 18, 2019 at 12:49 PM Sidharth Kumar <
> sidharthkumar2...@gmail.com> wrote:
>
>> Hi,
>>
>> Could you please confirm if geoserver 2.14.1 is compatible with HBase
>> 2.0.0.3.1(Hadoop3).
>>
>> Warm Regards
>>
>> Sidharth Kumar | Mob: +91 8197 555 599| Skype: itzsidharth
>> ___
>> 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
> --- *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
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
___
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

Re: [Geoserver-users] Geoserver compatibility

[Andrea Aime]

The packages provided at geoserver.org have no support for HBase/Hadoop
whatsoever.
However, there are two projects with GeoServer integrations, GeoMesa and
GeoWave, that seem to have some Hadoop support,
so you might want to check on their list (or maybe you get lucky and they
will notice this mail, unfortunately
you did not cite HBase in the mail subject, so they might not)

Cheers
Andrea


On Fri, Jan 18, 2019 at 12:49 PM Sidharth Kumar 
wrote:

> Hi,
>
> Could you please confirm if geoserver 2.14.1 is compatible with HBase
> 2.0.0.3.1(Hadoop3).
>
> Warm Regards
>
> Sidharth Kumar | Mob: +91 8197 555 599| Skype: itzsidharth
> ___
> 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
--- *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


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

[Geoserver-users] Geoserver compatibility

[Sidharth Kumar]

Hi,

Could you please confirm if geoserver 2.14.1 is compatible with HBase
2.0.0.3.1(Hadoop3).

Warm Regards

Sidharth Kumar | Mob: +91 8197 555 599| Skype: itzsidharth
___
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

Re: [Geoserver-users] Aggregates can't link to remote workspaces since 2.13

[Florent Gravin]

Hi,

Thanks for answers.

Aggregate... you mean layer group?

YES

Yes it was possible, pretty usefull.
So w consider doing a PR to make this possible though an option.

Cheers

On Wed, Jan 16, 2019 at 4:35 PM Andrea Aime 
wrote:

> On Wed, Jan 16, 2019 at 4:04 PM Florent Gravin <
> florent.gra...@camptocamp.com> wrote:
>
>> Hi community,
>>
>> Before 2.13, we could create an aggregate in workspace1 and point on
>> layers that belong to workspace2.
>>
>
> Aggregate... you mean layer group?
>  Since 2.13, it not possible anymore.
>
>> Is it an undesirable side effect of Isolate workspace integration ? Is it
>> a bug or is it wanted ?
>>
>
> I did not know it was possible, was definitely a bug though, only top
> level layer groups should be allowed to refer
> layers from multiple workspaces, a local workspace group should be able to
> refer only to local layers, or
> there would be misbehaviors when using workspace specific services
> (hopefully just the layer going away,
> worst case scenario a hard exception).
>
>
>> We found this option pretty usefull.
>>
>
> I guess it could become a configuration option (off by default, the
> current behavior is the expected one),
> if you are interested in donating a code change, see:
> https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md
>
> 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
> --- *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.*
>


-- 
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Florent Gravin*
*Front-end Technical Leader*
+33 4 58 48 20 36
___
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

Re: [Geoserver-users] Labeling polygons at centroid point

[Eugene Podshivalov]

Thanks everyone for the replies. I do make tiled requests, so it explains
everything.

Regards,
Eugene

пт, 18 янв. 2019 г. в 11:39, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi>:

> Hi,
>
>
>
> If your client is making tiled requests then you will have one label for
> each tile.
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* Eugene Podshivalov [mailto:yauge...@gmail.com]
> *Lähetetty:* 18. tammikuuta 2019 10:17
> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
> *Aihe:* [Geoserver-users] Labeling polygons at centroid point
>
>
>
> Hi all,
>
> It is stated in the documentation
> 
> that by default polygons are labeled only once at centroid point, but
> whatever parameters I define it always repeats a label within a polygon at
> some fixed intervals.
>
>
>
> Does it work properly for anyone?
>
>
>
> My YSLD style looks at follows
>
> feature-styles:
>
> - rules:
>
>   - symbolizers:
>
> - polygon:
>
> geometry: ${geom}
>
> fill-color: '#da7171'
>
> - text:
>
> geometry: ${geom}
>
> label: ${name}
>
> font-family: SansSerif
>
> font-size: 15
>
> fill-color: black
>
> and the result looks like this
>
> [image: image.png]
>
>
>
> The same thing happens with the SLD style.
>
>
>
> Regards,
>
> Eugene
>
___
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

Re: [Geoserver-users] Labeling polygons at centroid point

[Rahkonen Jukka (MML)]

Hi,

If your client is making tiled requests then you will have one label for each 
tile.

-Jukka Rahkonen-

Lähettäjä: Eugene Podshivalov [mailto:yauge...@gmail.com]
Lähetetty: 18. tammikuuta 2019 10:17
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Labeling polygons at centroid point

Hi all,
It is stated in the 
documentation
 that by default polygons are labeled only once at centroid point, but whatever 
parameters I define it always repeats a label within a polygon at some fixed 
intervals.

Does it work properly for anyone?

My YSLD style looks at follows

feature-styles:

- rules:

  - symbolizers:

- polygon:

geometry: ${geom}

fill-color: '#da7171'

- text:

geometry: ${geom}

label: ${name}

font-family: SansSerif

font-size: 15

fill-color: black
and the result looks like this
[image.png]

The same thing happens with the SLD style.

Regards,
Eugene
___
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

Re: [Geoserver-users] Labeling polygons at centroid point

[Ian Turton]

Polygons are labeled once at the centroid of the visible part of the
polygon. But if you make a series of tiled requests then each tile will be
labeled at the centroid of the polygon on that tile. To avoid this set the
geometry element of the textsymbolizer to use the centroid function on the
whole geometry,  See
https://gis.stackexchange.com/questions/37138/polygon-label-repeated-for-each-tile
for a fuller explanation.

Ian

On Fri, 18 Jan 2019 at 08:20, Eugene Podshivalov  wrote:

> Hi all,
> It is stated in the documentation
> 
> that by default polygons are labeled only once at centroid point, but
> whatever parameters I define it always repeats a label within a polygon at
> some fixed intervals.
>
> Does it work properly for anyone?
>
> My YSLD style looks at follows
>
> feature-styles:
> - rules:
>   - symbolizers:
> - polygon:
> geometry: ${geom}
> fill-color: '#da7171'
> - text:
> geometry: ${geom}
> label: ${name}
> font-family: SansSerif
> font-size: 15
> fill-color: black
>
> and the result looks like this
> [image: image.png]
>
> The same thing happens with the SLD style.
>
> Regards,
> Eugene
> ___
> 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
>


-- 
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


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

[Geoserver-users] Labeling polygons at centroid point

[Eugene Podshivalov]

Hi all,
It is stated in the documentation

that by default polygons are labeled only once at centroid point, but
whatever parameters I define it always repeats a label within a polygon at
some fixed intervals.

Does it work properly for anyone?

My YSLD style looks at follows

feature-styles:
- rules:
  - symbolizers:
- polygon:
geometry: ${geom}
fill-color: '#da7171'
- text:
geometry: ${geom}
label: ${name}
font-family: SansSerif
font-size: 15
fill-color: black

and the result looks like this
[image: image.png]

The same thing happens with the SLD style.

Regards,
Eugene
___
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