Passing binary data to the Accessors - GeoParquet/GeoArrow #8984
Unanswered
janneskruseMapular
asked this question in
Q&A
Replies: 1 comment 5 replies
-
If you want to see some source code, kepler.gl 3.0 has a GeoArrowLayer implementation, and also the GeoArrowLayers from lonboard are staged in (but not yet published from) deck.gl-community/modules/arrow-layers. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I was recently trying to catch up on the awesome work of Kyle Barron (e.g. here: https://observablehq.com/@kylebarron/geoparquet-on-the-web). However, I was unable to get it to run with Deck.gl.
What I am trying to do is, to render GeoArrow or Geoparquet converted to GeoArrow as a layer with deck. I was reading the documentation on how to pass binary data to Deck gl. and WebGl in general:
https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/vertexAttribPointer
https://deck.gl/docs/api-reference/core/layer#basic-properties
https://deck.gl/docs/developer-guide/performance
And so I think I would need to pass the data to the accessors via the attributes on the data object like so for coordinates (size 2: x, y) and colors (size 3: r,g,b):
If I do so, by either using real data as GeoArrow or creating random data, I get all my data points rendered at origin (0,0). Does anyone have an idea what could cause that and how to solve it?
Thanks a lot in advance!
This is my code for the map component:
Beta Was this translation helpful? Give feedback.
All reactions