[Geoserver-users] How to avoid nasty tile overlapping effects in windbarbs layer?

GeoServer GeoServer User
1

Hello,

I'm drawing a windbarb layer following Geoserver documentation and examples from GeoSolutions blog. Everything works well except tiled mode - nasty artefacts between adjacent tiles are easily to spot, eg:

https://geo.nebula.grid.icm.edu.pl:8443/geoserver/um/wms?service=WMS&version=1.1.0&request=GetMap&layers=um:wind_wgs2&styles=&bbox=0.2635588889068249,44.05613912816206,38.74505907998744,66.78182100121094&width=558&height=330&srs=EPSG:4326&format=application/openlayers#toggle

Remember to switch mode to "Tiled", zoom to, say 1:2M and pan to 22East, 56North.

If I remember well, user manual states that this can happen in case of mixing tiles with some WPS field functions. Is it possible to use any workaround for that?

Regards

Maciej

P.S. Style definition follows:

<StyledLayerDescriptor version="1.0.0"
   xmlns="http://www.opengis.net/sld&quot; xmlns:gml="http://www.opengis.net/gml&quot;
   xmlns:ogc="http://www.opengis.net/ogc&quot; xmlns:xlink="http://www.w3.org/1999/xlink&quot;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation="http://www.opengis.net/sld ./StyledLayerDescriptor.xsd">
    <NamedLayer>
       <Name>windbarbs</Name>
       <UserStyle>
          <Title>windbarbs</Title>
          <FeatureTypeStyle>
             <Transformation>
                <ogc:Function name="ras:RasterAsPointCollection">
                   <ogc:Function name="parameter">
                      <ogc:Literal>data</ogc:Literal>
                   </ogc:Function>
                   <ogc:Function name="parameter">
                     <ogc:Literal>interpolation</ogc:Literal>
                     <ogc:Literal>InterpolationBilinear</ogc:Literal>
                   </ogc:Function>
                   <ogc:Function name="parameter">
                     <ogc:Literal>scale</ogc:Literal>
                     <ogc:Function name="Categorize">
                      <ogc:Function name="env">
                        <ogc:Literal>wms_scale_denominator</ogc:Literal>
                      </ogc:Function>
                        <ogc:Literal>1</ogc:Literal>
                        <ogc:Literal>1000000</ogc:Literal>
                        <ogc:Literal>0.6</ogc:Literal>
                        <ogc:Literal>2000000</ogc:Literal>
                        <ogc:Literal>0.3</ogc:Literal>
                        <ogc:Literal>4000000</ogc:Literal>
                        <ogc:Literal>0.15</ogc:Literal>
                        <ogc:Literal>8000000</ogc:Literal>
                        <ogc:Literal>0.075</ogc:Literal>
                        <ogc:Literal>16000000</ogc:Literal>
                        <ogc:Literal>0.0375</ogc:Literal>
                     </ogc:Function>
                   </ogc:Function>
                </ogc:Function>
             </Transformation>
             <Rule>
                <MaxScaleDenominator>20000000</MaxScaleDenominator>
                <PointSymbolizer>
                   <Graphic>
                      <Mark>
                        <WellKnownName>windbarbs://default(
                          <ogc:Mul>
                          <ogc:PropertyName>speed</ogc:PropertyName>
                            <ogc:Literal>1</ogc:Literal>
                          </ogc:Mul>
                          )[m/s]
                        </WellKnownName>
                           <Stroke>
                              <CssParameter name="stroke">000000</CssParameter>
                              <CssParameter name="stroke-width">1</CssParameter>
                           </Stroke>
                        </Mark>
                        <Size>
                         <ogc:Function name="Categorize">
                             <!-- Value to transform -->
                           <ogc:PropertyName>speed</ogc:PropertyName>
                               <ogc:Literal>6</ogc:Literal>
                               <ogc:Literal>1.543333332</ogc:Literal>
                               <ogc:Literal>20</ogc:Literal>
                            </ogc:Function>
                        </Size>
                        <Rotation>
                           <ogc:Function name="Categorize">
<ogc:PropertyName>speed</ogc:PropertyName>
                                <!-- Output values and thresholds -->
                                <ogc:Literal>0</ogc:Literal>
                                <ogc:Literal>1.543333332</ogc:Literal>
                                <ogc:Add>
                                 <ogc:Literal>180</ogc:Literal>
<ogc:PropertyName>direction</ogc:PropertyName>
                                </ogc:Add>
                         </ogc:Function>
                      </Rotation>
                   </Graphic>
                </PointSymbolizer>
                <PointSymbolizer>
                   <Graphic>
                      <Mark>
                        <WellKnownName>circle</WellKnownName>
                         <Fill>
                            <CssParameter name="fill">
                               <ogc:Literal>#ff0000</ogc:Literal>
                            </CssParameter>
                         </Fill>
                      </Mark>
                      <Size>3</Size>
                   </Graphic>
                </PointSymbolizer>
             </Rule>
          </FeatureTypeStyle>
       </UserStyle>
    </NamedLayer>
</StyledLayerDescriptor>

2

I'm not sure if it's directly related issue, but in the "Contour" function, two parameter settings ("smooth" and "simplify") are ignored in Tiled mode.

Have both problems arisen from the same background?

Maciej

W dniu 2015-03-31 o 14:00, Maciej Filocha pisze:

I'm drawing a windbarb layer following Geoserver documentation and
examples from GeoSolutions blog. Everything works well except tiled mode
- nasty artefacts between adjacent tiles are easily to spot, eg:

https://geo.nebula.grid.icm.edu.pl:8443/geoserver/um/wms?service=WMS&version=1.1.0&request=GetMap&layers=um:wind_wgs2&styles=&bbox=0.2635588889068249,44.05613912816206,38.74505907998744,66.78182100121094&width=558&height=330&srs=EPSG:4326&format=application/openlayers#toggle

Remember to switch mode to "Tiled", zoom to, say 1:2M and pan to 22East,
56North.

If I remember well, user manual states that this can happen in case of
mixing tiles with some WPS field functions. Is it possible to use any
workaround for that?

3

Hi Maciej,

in relation to the windbarb issue with tiled request, which GeoServer version are you using?
We did some image quality improvements in the latest versions. Not sure if you have encountered a problem which has been analyzed and fixed in the meantime (last 2 months).

If you are already using the latest version, do you have any chance to open a JIRA and share a sample data?

Best Regards,

Daniele

···

On Thu, Apr 2, 2015 at 10:06 AM, Maciej Filocha <m.filocha@anonymised.com> wrote:

I’m not sure if it’s directly related issue, but in the “Contour”
function, two parameter settings (“smooth” and “simplify”) are ignored
in Tiled mode.

Have both problems arisen from the same background?

Maciej

W dniu 2015-03-31 o 14:00, Maciej Filocha pisze:

I’m drawing a windbarb layer following Geoserver documentation and
examples from GeoSolutions blog. Everything works well except tiled mode

  • nasty artefacts between adjacent tiles are easily to spot, eg:

https://geo.nebula.grid.icm.edu.pl:8443/geoserver/um/wms?service=WMS&version=1.1.0&request=GetMap&layers=um:wind_wgs2&styles=&bbox=0.2635588889068249,44.05613912816206,38.74505907998744,66.78182100121094&width=558&height=330&srs=EPSG:4326&format=application/openlayers#toggle

Remember to switch mode to “Tiled”, zoom to, say 1:2M and pan to 22East,
56North.

If I remember well, user manual states that this can happen in case of
mixing tiles with some WPS field functions. Is it possible to use any
workaround for that?

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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 dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

4

W dniu 2015-04-03 o 11:59, Daniele Romagnoli pisze:

Hi Maciej,
in relation to the windbarb issue with tiled request, which GeoServer
version are you using?
We did some image quality improvements in the latest versions. Not sure
if you have encountered a problem which has been analyzed and fixed in
the meantime (last 2 months).

If you are already using the latest version, do you have any chance to
open a JIRA and share a sample data?

I'm using Geoserver 2.7.0. Bug report created:

https://osgeo-org.atlassian.net/browse/GEOS-6969

Regards

Maciej