Clipped VectorTile rendering with renderMode: 'image' when browser is zoomed

[mshubin]

Describe the bug
I have a similar issue which has been raised here but this time with VectorTile using renderMode: 'image'.

When user zoomed the browser (with Ctrl-+ for example) it makes tiles clipped as in animation below:

.. there is a some kind of 'clip' between tiles.

The bug doesn't occur when:

• Browser is 100%
• imageMode is 'hybrid'

To Reproduce
Steps to reproduce the behavior:

1. Go to https://codesandbox.io/s/clipped-mvt-rendering-with-browser-zoom-ecocl?fontsize=14&hidenavigation=1&theme=dark
2. Zoom your browser (I reproduced with 150%)
3. Reload the url (otherwise it will work)
4. Zoom to left from 'Juranville' city
5. On level 19 you'll see the output as in animation

Expected behavior
The rendering as when the browser is not zoomed.

Thank you in advance and have a nice day,

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jeroenvheel]

I also have the same problem !! I’m going to turn off image rendering tomorrow and see if it’s working.

[jeroenvheel]

When using Image / hybrid or vector i still git the clipped vector

[jeroenvheel]

I fixed this by adding a bigger buffer to the tile vector

[Benjaki2]

I am having this problem as well.

[ahocevar]

The screenshot that @jeroenvheel looks like the vector tile source might have polygons with the wrong winding order. That could be fixed by configuring the MVT format with ol/Feature as featureClass:

import VectorTileSource from 'ol/source/VectorTile';
import MVT from 'ol/format/MVT';
import Feature from 'ol/Feature';

new VectorTileSource({
  format: new MVT({
    featureClass: Feature
  }),
})

[Benjaki2]

Here are some examples:

OL-latest

OL5.3.0 ✅

Code example
https://codepen.io/benjaki/pen/zYvzGxd

[ahocevar]

@Benjaki2 Your issue is caused by an invalid tilegrid. Probably due to #10974. Thanks for the test case, that should help to isolate the issue.

[ahocevar]

@Benjaki2 Your issue is fixed with #10982

@mshubin's issue looks similar, so I think that should also be fixed. Can you please test with the fix applied and report back?

[mshubin]

@ahocevar I confirm, I've tested it in my codesandbox example with last 6.3.2-dev and the issue doesn't occur anymore 👍 Can't wait to integrate it in our app.

Thank you very much !

[Benjaki2]

Looks great. Thank you! @ahocevar