Is SmartData already a raw-photo processing checkout?
Not as the default self-service offer. BYO hosting remains for supported processed packages, while the photogrammetry engine is being readied for controlled processing workflows.
A SmartData photogrammetry engine for raw capture to hosted views
SmartData is moving toward an end-to-end pipeline that can process drone imagery into 3D Tiles, point clouds, and downstream Gaussian Splat packages for hosted review.
Status
In development
Best-fit audience
Drone processors who want repeatable hosted delivery
The roadmap bridge from today's BYO hosted-view packages to a future capture-to-processing-to-viewer SmartData workflow.
The end-to-end SmartData story: capture, process, host, review, and report.
BYO hosting remains the self-service path while SmartData-managed processing is introduced through scoped preview workflows.
A clearer alternative to handing clients raw folders, local viewer files, or one-off exports.
What this unlocks
Connect source data, SmartData processing, hosted views, and review outputs so operational teams can move from capture to decisions with less file handling.
ODM/NodeODM baseline for aerial photogrammetry
3D Tiles and georeferenced point cloud outputs
COLMAP branch planned for higher-quality splat training
QA reports and callback payloads for SmartData ingestion
Package outputs shaped for SmartData view roots
Future path for raw imagery to hosted viewer delivery
Workflow story
1
Capture imagery with the required overlap, metadata, and ground-control expectations.
2
Run the processing engine outside the web request path through worker infrastructure.
3
Generate 3D Tiles, point cloud, and QA artifacts.
4
Package outputs into SmartData-compatible hosted-view roots.
5
Publish the dataset into SmartData for team review, sharing, and reporting.
Commercial use cases
- The end-to-end SmartData story: capture, process, host, review, and report.
- BYO hosting remains the self-service path while SmartData-managed processing is introduced through scoped preview workflows.
- A clearer alternative to handing clients raw folders, local viewer files, or one-off exports.
Delivery notes
- The engine contract keeps heavy ODM/COLMAP/Nerfstudio jobs outside the web app.
- General raw-image checkout is not yet the default self-service path.
- Raw imagery processing should be scoped with the team until the self-service checkout path is ready.
Drone processors who want repeatable hosted delivery
SmartData gives this team a hosted workflow for turning complex capture outputs into reviewable evidence.
Surveyors moving from local processing tools to team review
SmartData gives this team a hosted workflow for turning complex capture outputs into reviewable evidence.
Asset teams that want fewer handoffs between capture, processing, and evidence review
SmartData gives this team a hosted workflow for turning complex capture outputs into reviewable evidence.
Common questions
Straight answers about inputs, availability, outputs, and where human review still matters.
Why mention ODM?
ODM/NodeODM is the baseline aerial photogrammetry path in the engine plan, with separate branches for splat quality where needed.
How does this connect to BYO hosting?
The same SmartData view package shapes used by BYO hosting become the output contract for future processing jobs.