mapbox / mapbox/mapbox-gl-js

Support for Point Clouds

Open
#3,450 19 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature :green_apple:
Dominant language
TypeScript
Stars
12.4k
Forks
2.4k
PR merge metrics
No merged PRs in 30d

Description

I'm currently working on a library for a LiDAR and wanted to make use of Mapbox GL JS for visualizing point clouds both in real-time (while driving your car) but also statically (for the route).

For this use-case here are the road-blockers I encountered.

1/ I'm not able to extrude points. I can hack around this with small polygons. But then it seems like this is roughly the smallest polygon I can get to show up (there's probably a filter for noise?):

![Smallest extruded polygons](https://cloud.githubusercontent.com/assets/527241/19661163/7d4c9a6e-99e7-11e6-971d-a14ef6fb50f8.png)

2/ The extrusion feature seems to not support values < 1.
Here's what happens for a fractional 0.5 extrusion value:

![Fractional extrusion height](https://cloud.githubusercontent.com/assets/527241/19661162/7d4a025e-99e7-11e6-9546-97b5259b5103.png)

3/ There is no streaming source. My plan was to either use a Websocket server pushing point clouds into the browser and updating a source or exposing a GeoJSON endpoint which changes every second.

I don't expect support for point clouds in the foreseeable future.
I just want to bring blockers for the point cloud / LiDAR use-case to your attention.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies three broad blockers: point extrusion, fractional extrusion values, and streaming point-cloud sources. No files, tests, or entry points are named; review the existing extrusion and source-update behavior first, then clarify scope and acceptance criteria with maintainers before starting.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
computer-graphics, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.