Softwr

Maps · head to head

Lonboard vs WhiteboxTools

Lonboard logo

Lonboard

Maps

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

From
Free
Rated
-
Full reviewWebsite
WhiteboxTools logo

WhiteboxTools

Maps

Open source geospatial analysis engine with several hundred raster, LiDAR and hydrological tools

From
Free
Rated
-
Full reviewWebsite

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; WhiteboxTools there is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
  • They diverge on capability: Lonboard covers GeoArrow binary transfer, WhiteboxTools covers Hydrological analysis.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Lonboard and WhiteboxTools actually diverge.

Attributes where Lonboard and WhiteboxTools differ
AttributeLonboardWhiteboxTools
PlatformsLinux, macOS, WindowsWindows, macOS, Linux

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

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 WhiteboxTools

  • Hydrological analysis
  • LiDAR processing
  • Terrain derivatives
  • Raster analysis
  • Image processing
  • Python and R front ends
  • QGIS plugin
  • MIT licence

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 WhiteboxTools
  • A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot WhiteboxTools
  • A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot WhiteboxTools
  • A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot WhiteboxTools

WhiteboxTools

  • A hydrologist who needs depression breaching rather than filling on a large DEM, because filling destroys the drainage structure the model depends onnot Lonboard
  • A forestry or environmental team processing airborne LiDAR into canopy height and terrain models without buying a point cloud licence per analystnot Lonboard
  • A GIS developer embedding terrain analysis into a commercial product, where the MIT licence avoids the copyleft obligations of GRASS or SAGAnot Lonboard
  • A university teaching geomorphometry where every student needs the full toolset on their own laptop at zero costnot 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

WhiteboxTools

  • There is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
  • Maintenance depends on a single academic research group and effectively on one professor, which is a real continuity risk for anything embedded in a production pipeline for a decade.
  • It is command line first; the QGIS plugin and Python bindings help, but analysts who expect a graphical workflow with previews and undo find it unforgiving.
  • Documentation is a reference manual rather than a set of worked workflows, so knowing which of 450 tools to chain for a given problem requires domain knowledge the software does not supply.
  • Naming and behaviour overlap confusingly with the older Whitebox GAT, a separate GPL-licensed desktop GIS from the same group, and adopters regularly install or cite the wrong one.

Pricing, plan by plan

Lonboard

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

WhiteboxTools

Free
  • WhiteboxTools open coreFree
    • MIT licence
    • Over 450 geospatial tools
    • Python, R and QGIS front ends

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 WhiteboxTools if

  • You need hydrological analysis.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want lidar processing.
WhiteboxTools review

Questions people ask

Is Lonboard or WhiteboxTools better?
Neither clearly leads. Lonboard starts at Free and WhiteboxTools at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lonboard or WhiteboxTools?
Lonboard starts at Free and WhiteboxTools at Free.
Does Lonboard or WhiteboxTools run on more platforms?
Lonboard runs on Linux, macOS, Windows. WhiteboxTools runs on Windows, macOS, Linux.
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 WhiteboxTools is typically brought in for.
What can Lonboard do that WhiteboxTools cannot?
Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget. WhiteboxTools covers Hydrological analysis, LiDAR processing, Terrain derivatives, Raster analysis.

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.

WhiteboxTools: Is WhiteboxTools free for commercial use?

Yes. It is MIT licensed, which permits commercial use and embedding without a copyleft obligation.

Lonboard: Who maintains it?

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

WhiteboxTools: Is there paid support?

No general commercial support contract is offered. Support is GitHub issues and community forums. Budget internal expertise instead.

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.

WhiteboxTools: Who maintains it?

Professor John Lindsay and the Geomorphometry and Hydrogeomatics Research Group at the University of Guelph, Canada.

Lonboard: Is it free for commercial use?

Yes, it is open source with no licence fee.

WhiteboxTools: How is it different from Whitebox GAT?

Whitebox GAT is an older GPL-licensed desktop GIS from the same group. WhiteboxTools is the newer Rust command line engine with a permissive licence. They are not the same product.

WhiteboxTools: Can I use it from QGIS?

Yes, through a plugin, and also from Python and R.

Share

Related pages

More on Lonboard

More on WhiteboxTools

Keep looking

Other head to heads