rurseekatze / node-tileserver

A lightweight tileserver based on NodeJS for serving bitmap and vector tiles.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Rendering artefact

rurseekatze opened this issue · comments

Fix a bug that causes rendering artefacts. In every known case a lines goes either from the top left corner parallel to the tile bound or from the top left corner to the bottom right corner of a tile.

The bug can be seen on the map of the OpenRailwayMap project (which uses node-tileserver for rendering):

1

1

Another strange diagonal rendering bug here (though less close to 45 degrees than that above), orange line North-west of Peterborough:
screenshot 2

Also see here near Christchurch, horizontal orange line (primarily):
screenshot 3
Zoomed in, part of the artifact is retained, as the bridge (?) appears to be rendered with 'spikes' to the left and right, above and below the orange line:
screenshot 4

Not sure if this bug is related, but it changes on different zoom levels (the Peterborough one does too). For example, at this zoom level a large chunk of the map is either absent or rendered very differently, between Brentwood and Woodford (top), and west of Sidcup to Northfleet (bottom). Going to this area and zooming in shows all the lines, and zooming out shows the non-black lines.
screenshot 6

328
canvas

Interestingly the bug shows up differently in prerendered and when rendered in browser, so this smells for me like using an uninitialized variable.

When we once looked into this there always were line segments from the data that ended exactly at the tile border.