Kyle Barron
Kyle Barron
Huh... When I copied your code into an HTML file and ran it on localhost, the error traceback has `trips-layer` in it, which made me confused. Maybe the sourcemaps are...
Yeah must be an issue with the source maps...
I published @geoarrow/[email protected] with the latest main
I'm not a JS expert, and personally I always use React with a bundler. Based on the previous issue in https://github.com/geoarrow/deck.gl-layers/issues/109, it seemed like people were able to get something...
I merged the geoarrow-js pr. If you need me to create a patch release I can
I published 0.3.1 https://github.com/geoarrow/geoarrow-js/releases/tag/v0.3.1
> `WebGL warning: drawArraysInstanced: Instance fetch requires 100, but attribs only supply 0.` That could be a bug in deck.gl v9
Yeah this is a "separated" GeoArrow column, which deck.gl-layers does not yet support. See https://github.com/geoarrow/deck.gl-layers/issues/3
> It is not clear to me if [the buffer fix PR](https://github.com/visgl/deck.gl/pull/9021) is available in `v9.0.27`. The author mentioned it depends on the [UBO work PR](https://github.com/visgl/deck.gl/issues/8997), which hasn't been merged...
See my comment here https://github.com/visgl/deck.gl/issues/8960#issuecomment-2284791644 where I forked the previous HeatmapLayer repro that someone else had reported, updated to the latest deck.gl version, and am still getting the same issue....