Hi Scott,
Are you setting the tileGrid property when creating the vector layer? If
so, remove it.
I think everyone copies this code off the Geoserver website:
var map = new ol.Map({
target: 'map',
view: new ol.View({
center: [0, 0],
zoom: 2
}),
layers: [new ol.layer.VectorTile({
style:simpleStyle,
source: new ol.source.VectorTile({
tilePixelRatio: 1, // oversampling when > 1
tileGrid: ol.tilegrid.createXYZ({maxZoom: 19}),
format: new ol.format.MVT(),
url: '/geoserver/gwc/service/tms/1.0.0/' + layer +
'@EPSG%3A'+projection_epsg_no+'@pbf/{z}/{x}/{-y}.pbf'
})
})]
});
Supplying the tileGrid property creates the gridlines in 2.15.0. Not sure
why it doesn't for earlier versions.
Matt.
On Wed, May 22, 2019 at 7:10 PM Andrea Aime <[email protected]>
wrote:
> Hi Jody,
> yes I believe that vector tiles are supposed to have a gutter outside the
> tile to prevent borders painted by the client from showing up
> like they do. I'm seeing a fixed buffer of 12 pixels in the code, plus an
> amount dependent on the style used... however at some point
> I believe that the tile resolution was pumped up with an oversampling
> factor of 16 (around Oct 18th, by Devon), maybe that's interacting badly
> with the gutter computation... just speculation at the moment, I have not
> really looked into it
>
> Cheers
> Andrea
>
>
> On Tue, May 21, 2019 at 9:26 PM Jody Garnett <[email protected]>
> wrote:
>
>> Just to clarify, what is the intended functionality here? Are the
>> polygons intended to extend past the tile boundary and be "clipped" (and
>> thus not render an edge)?
>> --
>> Jody Garnett
>>
>>
>> On Tue, 21 May 2019 at 02:06, SW <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> We're also using OpenLayers and GeoServer/GWC generated vector tiles to
>>> display features on a map.
>>>
>>> We recently upgraded to 2.15.0 and noticed the same gridlines around the
>>> internal edges of the vector tile.
>>>
>>> Here's an example of what we're seeing for a layer styled in OpenLayers
>>> CSS
>>> with stroke width of 3:
>>> https://www.dropbox.com/s/mdwni4fs3hegy3t/Grid_lines_1.PNG?dl=0
>>> In this cases the internal grid is quite obvious.
>>>
>>> And here's an example of what we're seeing for a layer styled in
>>> OpenLayers
>>> CSS with stroke width of 1:
>>> https://www.dropbox.com/s/15blsn6tvz9z800/Grid_lines_3.PNG?dl=0
>>> In this case the internal grid is faint, but still visible.
>>>
>>> To help isolate the problem we read the GeoServer vector tiles into
>>> Maputnik
>>> (Mapbox GL JS) and Leaflet. In both cases we still see the same internal
>>> grid issue.
>>> The width of the internal grid seems to be proportional to the width of
>>> the
>>> feature's outline stroke style, although this might be due to overlaps
>>> betwen the tiles obscuring the full style.
>>>
>>> To narrow down which version of GeoServer migth have introduced the
>>> issue,
>>> we stepped back through the recent releases.
>>> It looks like it was introduced in 2.14.1 as we see the issue in that
>>> release, but not in 2.14.0.
>>>
>>> In the response above Andrea provided a link to:
>>> http://vtp2018.s3-eu-west-1.amazonaws.com/vtpext-wmts.html#/
>>> I can see the internal grid in some cases on that site - for example I
>>> see
>>> it with the "Night" SLD style:
>>>
>>> https://www.dropbox.com/s/q1grew5r7b40le2/Night_vector_tile_grid_lines.PNG?dl=0
>>>
>>> And if I edit the Mapbox style, I can see it more clearly:
>>> https://www.dropbox.com/s/nxtla7y0w08k4by/Night_with_grids.png?dl=0
>>>
>>> Any idea what might be going on with the internal grids?
>>>
>>> Thanks,
>>> Scott
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>> [email protected]
>>> 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
>>
>>
>> [email protected]
>> 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
>
>
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
