Softwr

Maps · head to head

Lonboard vs Mapillary

Lonboard logo

Lonboard

Maps

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

From
Free
Rated
-
Full reviewWebsite
Mapillary logo

Mapillary

Maps

Platform for street-level imagery that crowdsources images to map the world and

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Lonboard has a free tier, so it costs nothing to try first.
  • 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; Mapillary no pricing information published on main website pages, suggesting either free service or hidden pricing model
  • They diverge on capability: Lonboard covers GeoArrow binary transfer, Mapillary covers Core Functionality.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Lonboard and Mapillary actually diverge.

Attributes where Lonboard and Mapillary differ
AttributeLonboardMapillary
Starting priceFreeOn request
Pricing modelOpen source, no licence feefreemium
Free tierYesNo
PlatformsLinux, macOS, WindowsWeb

Identical on both: 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 Mapillary

  • Core Functionality
  • User Interface

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

Mapillary

  • Street-level imagery for map editing and verificationnot Lonboard
  • Crowdsourcing photos to keep a map currentnot Lonboard
  • Extracting map features automatically with computer visionnot Lonboard
  • Embedding street imagery with MapillaryJSnot 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

Mapillary

  • No pricing information published on main website pages, suggesting either free service or hidden pricing model
  • Unclear monetization strategy makes it difficult for businesses to understand licensing costs for commercial use
  • No published tier structure or feature limits visible to potential customers

Pricing, plan by plan

Lonboard

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

Mapillary

On request

No published plan breakdown. See the Mapillary review.

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

  • You need core functionality.
  • You also want user interface.
Mapillary review

Questions people ask

Is Lonboard or Mapillary better?
Neither clearly leads. Lonboard starts at Free and Mapillary at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lonboard or Mapillary?
Lonboard has a free tier; the other does not. Paid plans start at Free for Lonboard and On request for Mapillary.
Does Lonboard or Mapillary run on more platforms?
Lonboard runs on Linux, macOS, Windows. Mapillary runs on Web.
Can I use Lonboard for free?
Yes. Lonboard has a free tier, so you can try it without paying. Mapillary starts at On request.
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 Mapillary is typically brought in for.
What can Lonboard do that Mapillary cannot?
Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget. Mapillary covers Core Functionality, User Interface.

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.

Mapillary: What is the pricing model for Mapillary?

Mapillary does not publish pricing information on its main website pages. The platform focuses on features like street-level imagery access, map updating through computer vision, and open data sharing, but specific costs and licensing tiers are not disclosed publicly.

Source
Lonboard: Who maintains it?

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

Mapillary: Can I use Mapillary for commercial purposes?

Specific details about commercial licensing for Mapillary are not published on the main website. Interested businesses should contact Mapillary directly through their support channels to discuss commercial use cases and licensing options.

Source
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.

Mapillary: Is Mapillary free to use for individual contributors?

Mapillary emphasizes open data sharing and community contributions but specific details about free vs. paid access for individuals are not clearly stated on the main website. Contact Mapillary support for clarification on access terms.

Source
Lonboard: Is it free for commercial use?

Yes, it is open source with no licence fee.

Share

Related pages

More on Lonboard

More on Mapillary

Keep looking

Other head to heads