Coordinate precesion is low in projected views about deck.gl HOT 9 CLOSED

In the deck.gl v3 beta releases we now have both 64 bit layers, and meter offset mode for 32 bit layers, which both solve this. Already consumable from beta releases and will be merged to master

from deck.gl.

@kachkaev Did you ever find a workaround for this? Basically makes the built-in layers unusable atm :(

from deck.gl.

This is different from the primitive distortion issue, but might be alleviated by that fix depending what coordinate system you are using.

As you mentioned, there's a tradeoff between precision (CPU 64bit floating point) and speed (GPU 32bit floating point in glsl 1.00), and we chose the latter. There are walkarounds, e.g. using multiple coordinate systems. The ideal solution is to simulate high-precision floating point operations, we have done some work on that but need more tests (1+ week(s)) before we are comfortable to release it.

from deck.gl.

@contra still no workaround unfortunately. Had to limit the zoom level to 14, but this is not possible in any app. Really looking forward for a solution by @gnavvy. Would be good if the official example was properly synced with the library upon release (see #43)!

from deck.gl.

@kachkaev could you share a slice of your data please? We didn't observe salient distortion until zoom > 18 (if we are both referring to the mapbox zoom level). wondering how your data is formatted.

from deck.gl.

@gnavvy the images and the animation above are obtained from your data, which you refer to from the example. I did not have to change anything in it to observe wobbling and distortions in all browsers I tested this in.

from deck.gl.

@gnavvy Wobbling is visible in the demo (Chrome @ 52.0.2743.116 (64-bit), OSX)

from deck.gl.

Any implementation tips? I could take a whack at this if I knew where to start!

from deck.gl.

@contra - We are finalizing a general solution for high zoom levels and higher coordinate precision. Stay tuned.

from deck.gl.