Another possible approach could be try to fix the mismatch of label partials, which is caused by conflict resolution when "partials" option is defined. Probably by excluding partial labels from conflict resolution somehow, i.e. if a label is to be drawn partially then it should be drawn at a fixed position. Not sure if it that is possible to implement.
Cheers, Eugene пн, 21 янв. 2019 г. в 13:14, Eugene Podshivalov <yauge...@gmail.com>: > You lose a lot of flexibility, but that's the only solution that >> worked 100% of the time for me. > > I'm using the label-on-point approach as well right now, but as you've > correctly noted, it is less flexible than it could be with label-on-polygon > one. > Apart from the afore-mentioned necessity to define the area-zoom levels, > the conflict resolution has less space for resolving collisions with other > labels, which will lead to some label not displayed at all. > > Fixing the issue with duplicated labels in meta-tiling would be a huge > jump forward in geoserver's polygon labeling capabilities. > > Cheers, > Eugene > > > > пн, 21 янв. 2019 г. в 12:49, Andrea Aime <andrea.a...@geo-solutions.it>: > >> Hi, >> for those having WPS plugged in there is also a better polygon label >> function called "labelPoint": >> >> >> http://docs.geotools.org/latest/userguide/library/main/function_list.html#labelpoint-polygon-tolerance-labelpoint >> >> I don't know what the tolerance parameter means though. Ian (cc'ed) do >> you remember? >> >> Cheers >> Andrea >> >> >> On Mon, Jan 21, 2019 at 9:11 AM Arnaud L. <arnaud.lis...@codata.eu> >> wrote: >> >>> Hi Eugene >>> >>> Le 20/01/2019 à 18:52, Eugene Podshivalov a écrit : >>> > Meta-tiling resolves most of the issues with duplicated labels but >>> they >>> > are still happening on geometries which cover several meta-tiles. You >>> > can see that illustrated on the diagram below. >>> > >>> > Would it be possible to resolve it by putting a label only to that >>> > meta-tile which covers the largest portion of the geometry? >>> >>> This is the kind of problem that could be fixed by placing the label on >>> the centroid of the polygon instead of using automatic placement (which >>> would position the label on the centroid of the *visible* portion of the >>> polygon). >>> You can see a solution by Andrea here for instance : >>> >>> https://gis.stackexchange.com/questions/265836/label-polygon-at-central-position-dynamically >>> >>> Cheers >>> >>> -- >>> Arnaud >>> >>> >>> _______________________________________________ >>> 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
