Potree Integration in React App
Budget: $10 – $30 USD
I have an existing React application that now needs a fully-functional Potree viewer so users can explore point-cloud data directly inside the app. The core job is to wire Potree into my current React component structure, load a sample LAS/LAZ file I provide, and expose the usual viewer controls (orbit, measure, clip) without breaking the rest of the interface.
You’ll be working with a mature codebase (React 18, Vite bundler) and should already feel comfortable dealing with WebGL libraries such as Three.js, because Potree relies on them under the hood. Clear, well-commented code is important to me: I want to understand how the viewer is initialised, where assets live, and how I can swap point-cloud files later on.
Deliverables
• A React component (or hook) that mounts and unmounts a Potree viewer cleanly
• Configuration for custom asset paths so the viewer loads textures, shaders, and point clouds from the public folder
• One example page wired into my existing router that proves everything works
• A brief README explaining installation steps, key props, and how to extend the setup
Acceptance criteria
The viewer must render the provided point cloud with basic interaction tools, maintain 60 fps on a typical laptop, and leave no console errors or React warnings.
If this sounds straightforward for you, let’s get started; I’ll share the repo and sample data as soon as we agree.
You’ll be working with a mature codebase (React 18, Vite bundler) and should already feel comfortable dealing with WebGL libraries such as Three.js, because Potree relies on them under the hood. Clear, well-commented code is important to me: I want to understand how the viewer is initialised, where assets live, and how I can swap point-cloud files later on.
Deliverables
• A React component (or hook) that mounts and unmounts a Potree viewer cleanly
• Configuration for custom asset paths so the viewer loads textures, shaders, and point clouds from the public folder
• One example page wired into my existing router that proves everything works
• A brief README explaining installation steps, key props, and how to extend the setup
Acceptance criteria
The viewer must render the provided point cloud with basic interaction tools, maintain 60 fps on a typical laptop, and leave no console errors or React warnings.
If this sounds straightforward for you, let’s get started; I’ll share the repo and sample data as soon as we agree.