Is Lonboard or PDAL better?

Neither clearly leads. Lonboard starts at Free and PDAL at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.

Which is cheaper, Lonboard or PDAL?

Lonboard starts at Free and PDAL at Free.

Does Lonboard or PDAL run on more platforms?

Lonboard runs on Linux, macOS, Windows. PDAL runs on Linux, Windows, macOS.

Can I use Lonboard for free?

Both have a free tier, so you can try either at no cost before committing.

What is Lonboard best used for?

Lonboard is most often used for an analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that size, a researcher publishing a reproducible analysis where the visualisation must run from the same script as the processing, a data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a gis, a team building an internal analysis pipeline on geoparquet that wants rendering without a serialisation step in the middle. Of those, an analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that size and a researcher publishing a reproducible analysis where the visualisation must run from the same script as the processing are not what PDAL is typically brought in for.

What can Lonboard do that PDAL cannot?

Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget. PDAL covers Format translation, JSON pipelines, Ground classification filters, Reprojection.

Maps · head to head

Lonboard vs PDAL

Lonboard

Maps

Python map rendering in Jupyter that skips GeoJSON and moves millions of features without choking

From: Free
Rated: -

Full review Website

PDAL

Libraries

Open source C++ library and command line tool for point cloud translation and processing

From: Free
Rated: -

Full review Website

The short version

Each has a real cost: Lonboard it is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file; PDAL it is a library and command line tool with no graphical interface, so anyone expecting to inspect, edit or visualise a point cloud needs entirely separate software.
They diverge on capability: Lonboard covers GeoArrow binary transfer, PDAL covers Format translation.
Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Lonboard and PDAL actually diverge.

Attributes where Lonboard and PDAL differ
Attribute	Lonboard	PDAL
Platforms	Linux, macOS, Windows	Linux, Windows, macOS
Category	Maps	Libraries

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Lonboard

GeoArrow binary transfer
GeoPandas input
deck.gl layers
Jupyter widget
Large dataset handling
Styling by attribute
Open source licence

Only in PDAL

Format translation
JSON pipelines
Ground classification filters
Reprojection
Rasterisation
Python bindings
Streaming mode
Cloud-native output

What people use each for

The jobs each tool is most often brought in to do.

Lonboard

An analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that sizenot PDAL
A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot PDAL
A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot PDAL
A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot PDAL

PDAL

A mapping agency building a repeatable pipeline that reprojects, classifies ground and tiles a national lidar datasetnot Lonboard
A developer converting client-delivered LAS files into cloud-optimised COPC for streaming to a web viewernot Lonboard
A researcher scripting outlier removal and DEM generation from drone lidar inside a Python notebooknot Lonboard
A survey firm automating quality checks on incoming point cloud deliveries rather than opening each file by handnot Lonboard

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Lonboard

It is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file
Maintenance sits with Development Seed as an open source side output of a consultancy, so roadmap priorities follow client projects and there is no support contract to buy
Layer coverage is a subset of deck.gl, so an analyst needing a less common layer type has to drop to pydeck or write JavaScript rather than staying in Python
It expects data already in GeoPandas or Arrow form, which means the performance benefit depends on the rest of your pipeline being Arrow-friendly; reading a large Shapefile is still the slow step
Rendering happens in the browser, so very large datasets are ultimately limited by the client machine's memory and GPU rather than by the server, and a laptop will still fail on data a workstation handles

PDAL

It is a library and command line tool with no graphical interface, so anyone expecting to inspect, edit or visualise a point cloud needs entirely separate software.
Pipelines are written as JSON with filter-specific parameters, and getting classification results right requires understanding the underlying algorithms rather than tuning a slider.
Development depends heavily on a small contributor base and on public sector contract funding, which is a concentration risk for an organisation making it load-bearing.
There is no vendor support tier to purchase; paid help means a consulting engagement, which suits an agency with a procurement process and suits a small firm poorly.
Error messages and documentation assume geospatial and command line fluency, so the practical adoption cost is staff capability rather than licence fees.

Pricing, plan by plan

Lonboard

Free

LonboardFree
- Open source, no licence fee
- No usage limits
- Installed from PyPI or conda

PDAL

Free

PDALFree
- BSD licence
- Library, command line tool and Python bindings
- No usage or seat limits

Which should you pick?

Choose Lonboard if

You need geoarrow binary transfer.
You want to start without paying.
You work on Linux, macOS, Windows.
You also want geopandas input.

Lonboard review

Choose PDAL if

You need format translation.
You want to start without paying.
You work on Linux, Windows, macOS.
You also want json pipelines.

PDAL review

Questions people ask

Is Lonboard or PDAL better?: Neither clearly leads. Lonboard starts at Free and PDAL at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lonboard or PDAL?: Lonboard starts at Free and PDAL at Free.
Does Lonboard or PDAL run on more platforms?: Lonboard runs on Linux, macOS, Windows. PDAL runs on Linux, Windows, macOS.
Can I use Lonboard for free?: Both have a free tier, so you can try either at no cost before committing.
What is Lonboard best used for?: Lonboard is most often used for an analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that size, a researcher publishing a reproducible analysis where the visualisation must run from the same script as the processing, a data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a gis, a team building an internal analysis pipeline on geoparquet that wants rendering without a serialisation step in the middle. Of those, an analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that size and a researcher publishing a reproducible analysis where the visualisation must run from the same script as the processing are not what PDAL is typically brought in for.
What can Lonboard do that PDAL cannot?: Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget. PDAL covers Format translation, JSON pipelines, Ground classification filters, Reprojection.

Answered from the vendors’ own pages

Lonboard: Why not just use pydeck?

pydeck serialises geometry to GeoJSON to reach the browser. Lonboard uses a binary GeoArrow pipeline, which is the reason it handles far larger datasets in the same notebook.

PDAL: Is PDAL a product I can buy?

No. It is a free BSD-licensed library and command line tool. There is nothing to purchase.

Lonboard: Who maintains it?

Development Seed, a geospatial engineering consultancy, as an open source project. There is no commercial support offering.

PDAL: Who maintains it?

An open contributor community with development led substantially by Hobu Inc, funded largely through US public sector contracts.

Lonboard: Does it work outside Jupyter?

It is built as a Jupyter widget. Exporting to standalone HTML is possible, but the intended environment is a notebook.

PDAL: Can I get commercial support?

Only by contracting Hobu or an independent consultancy. There is no support subscription.

Lonboard: Is it free for commercial use?

Yes, it is open source with no licence fee.

PDAL: Does it have a viewer?

No. Use QGIS, CloudCompare or a web viewer for visualisation; PDAL handles the processing.

Lonboard vs PDAL

Lonboard

PDAL

The short version

Where they differ

What each one covers

Only in Lonboard

Only in PDAL

What people use each for

Lonboard

PDAL

Where each one falls short

Lonboard

PDAL

Pricing, plan by plan

Lonboard

PDAL

Which should you pick?

Choose Lonboard if

Choose PDAL if

Questions people ask

Answered from the vendors’ own pages

Related pages

More on Lonboard

More on PDAL

Keep looking

Other head to heads