Softwr

Libraries · head to head

CollectiveAccess vs Lonboard

C

CollectiveAccess

Libraries

Open source collections management and presentation

From
Free
Rated
-
Full reviewWebsite
Lonboard logo

Lonboard

Maps

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: CollectiveAccess requires technical knowledge to install and configure on web servers; 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
  • They diverge on capability: CollectiveAccess covers Configurable cataloging, Lonboard covers GeoArrow binary transfer.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which CollectiveAccess and Lonboard actually diverge.

Attributes where CollectiveAccess and Lonboard differ
AttributeCollectiveAccessLonboard
Pricing modelUnknownOpen source, no licence fee
PlatformsWebLinux, macOS, Windows
CategoryLibrariesMaps
Founded2003Unknown

Identical on both: starting price (Free), 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 CollectiveAccess

  • Configurable cataloging
  • Digital asset management
  • Relationship mapping
  • Provenance tracking
  • Loan management
  • Exhibition management
  • Web publishing (Pawtucket)
  • Import/export tools

Only in Lonboard

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

What people use each for

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

CollectiveAccess

  • Museum collection managementnot Lonboard
  • Archival descriptionnot Lonboard
  • Digital asset managementnot Lonboard
  • Exhibition developmentnot Lonboard

Lonboard

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

Where each one falls short

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

CollectiveAccess

  • Requires technical knowledge to install and configure on web servers
  • Limited commercial support compared to proprietary alternatives

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

Pricing, plan by plan

CollectiveAccess

Free

No published plan breakdown. See the CollectiveAccess review.

Lonboard

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

Which should you pick?

Choose CollectiveAccess if

  • You need configurable cataloging.
  • You want to start without paying.
  • You also want digital asset management.
CollectiveAccess review

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

Questions people ask

Is CollectiveAccess or Lonboard better?
Neither clearly leads. CollectiveAccess starts at Free and Lonboard at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CollectiveAccess or Lonboard?
CollectiveAccess starts at Free and Lonboard at Free.
Does CollectiveAccess or Lonboard run on more platforms?
CollectiveAccess runs on Web. Lonboard runs on Linux, macOS, Windows.
Can I use CollectiveAccess for free?
Both have a free tier, so you can try either at no cost before committing.
What is CollectiveAccess best used for?
CollectiveAccess is most often used for museum collection management, archival description, digital asset management, exhibition development. Of those, museum collection management and archival description are not what Lonboard is typically brought in for.
What can CollectiveAccess do that Lonboard cannot?
CollectiveAccess covers Configurable cataloging, Digital asset management, Relationship mapping, Provenance tracking. Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget.

Answered from the vendors’ own pages

CollectiveAccess: Is CollectiveAccess free?

Yes, CollectiveAccess is completely free and open-source software licensed under the GNU Public License version 3, with no commercial licensing model.

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.

CollectiveAccess: What does CollectiveAccess do?

CollectiveAccess is web-based collections management software for cataloguing and publishing museum and archival collections, with multi-user support allowing collaboration on metadata entry and collection organization.

Lonboard: Who maintains it?

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

CollectiveAccess: Who uses CollectiveAccess?

CollectiveAccess is used by hundreds of institutions from national museums to local history consortia, highly specialized archives, and catalogues raisonnés, including the Munich City Museum which manages over 200,000 objects.

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.

Lonboard: Is it free for commercial use?

Yes, it is open source with no licence fee.

Share

Related pages

More on CollectiveAccess

More on Lonboard

Keep looking

Other head to heads