-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker: Point Cloud Usability and Polish #536
Comments
I'd like to contribute to this project. I can take a look at this? |
@Gmadges Of course. Happy to engage with you and help you get started. As preparation, to make sure you have a sense for the high-level ideas behind the code you are going to change, you'll want to read up on: And read this code Then we can have a sync and make sure any questions you have get answered, give you some tips for how to proceed etc. Welcome to loaders.gl! |
Awesome, thank you!
What is the best method to ask questions? here on this issue? |
Yes, of course, we can start here. You could also sign up for the kepler.gl or deck.gl slack channels. E.g. keplergl/kepler.gl#643 |
Mentioning this tracker issue in future release tracker issue, but closing for inactivity |
v2.x Point cloud category
Also, see discussion at end of #659
PointCloudLayer
...getBounds
function to each point cloud loader (it is small enough) or we could place a helper in theloader-utils
module for now, or we could even create a new@loaders.gl/meshes
"category module" for mesh-related utilities.v2.1
Point Cloud Example Features
Point Cloud Samples
The text was updated successfully, but these errors were encountered: