Spike artifacts when zoomed out over GeoJSON datasource about harp.gl

[ninok]

Thanks for creating the issue. Can you please also attach the style that you used for the geojson?

[nzjony]

Removing the wontfix label, it seems to be a genuine problem. Could be related to the issue reported internally: HARP-10866

[nzjony]

This is still a valid issue. I managed to recreate it, so will reopen.

[nzjony]

@harrycollin , basically we don't handle rendering MultiPolygon's correctly when styled using solid-line.

It seems it is an issue with the way we use geojson-vt to do the subdivision, we need to know if the edge added is part of the original data or whether it is synthentic.

@robertoraggi created the internal ticket and can perhaps give some more info than I can describe.

Edit: Roberto described it a bit more to me, basically, geojson-vt will add such synthentic edges so that each tile has closed polygons, however when rendering the polygons with lines, we don't want to render these lines, because they will introduce artifacts.

[harrycollin]

@nzjony thanks for the insight. I look forward to hearing more on this :)

[nzjony]

@harrycollin , no worries. All going well, we plan to start fixing it in 1-2 weeks.

[harrycollin]

@ninok Updated the original

[harrycollin]

@ninok Where you see 'this.fillColor.hex' & 'this.strokeColor.hex' it is just a random hex colour for the moment.

[ninok]

Still cannot reproduce on Chrome 81 Ubuntu 20.04.
@HHammerite Can you try to load your file in this example: https://www.harp.gl/docs/master/examples/#geojson-viewer.html

[harrycollin]

Interesting. I can't reproduce it either on that example at my original zoom level. Here is a screenshot of me zoomed out at a similar distance.

But I do see it when zoomed in a bit more.

But when zoomed even further, the whole layer disappears.

I think I might record a video and post it here because the experience is so inconsistent.

[harrycollin]

Here is a video I recorded https://www.youtube.com/watch?v=5E9MdB9JHjc

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

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

[harrycollin]

@nzjony Awesome! Are there any initial thoughts on what could be causing this?

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

[nzjony]

@harrycollin , sorry no update on our side.

[harrycollin]

No problem!

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

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