Maps · head to head
Lonboard vs Transit

Lonboard
Maps
Python map rendering in Jupyter that skips GeoJSON and moves millions of features without choking
- From
- Free
- Rated
- -

Transit
Maps
Public transit trip planning and real-time arrivals for buses, trains and shared bikes and scooters
- From
- Free
- Rated
- -
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; Transit coverage depends entirely on whether the local transit agency publishes a real-time feed, so quality swings sharply between well-funded metro systems and smaller regional operators.
- They diverge on capability: Lonboard covers GeoArrow binary transfer, Transit covers Real-time arrivals.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Lonboard and Transit actually diverge.
Identical on both: starting price (Free), 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 Transit
- Real-time arrivals
- Multi-modal trip planning
- Service alerts
- In-app fare payment
- Offline schedules
- GO transit and micromobility layers
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 Transit
- A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot Transit
- A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot Transit
- A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot Transit
Transit
- A commuter in a city with a well-maintained GTFS-realtime feed wanting live bus and train arrivalsnot Lonboard
- A rider comparing a transit trip against a bike share or scooter leg for the last milenot Lonboard
- A visitor needing offline-capable static schedules in a city with patchy data coveragenot Lonboard
- Someone wanting to buy a transit fare inside the same app used to plan the trip, in supported citiesnot 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
Transit
- Coverage depends entirely on whether the local transit agency publishes a real-time feed, so quality swings sharply between well-funded metro systems and smaller regional operators.
- The company earns its revenue by selling agencies a paid analytics product built from rider trip data, which means the free app functions partly as a data-collection layer for a business customer, not only as a public service.
- In-app fare payment is only available in a limited set of cities, so the headline feature is not something most riders can actually use.
- Static schedule fallback in low-data cities is only as accurate as the agency last published, and service changes can go unreflected for weeks.
- The app has no offline routing without a cached area, so it is not reliable for navigation in areas with poor mobile signal.
Pricing, plan by plan
Lonboard
Free- LonboardFree
- Open source, no licence fee
- No usage limits
- Installed from PyPI or conda
Transit
Free- Rider appFree
- Real-time arrivals and trip planning
- No ads shown to riders
- In-app fare purchase where supported
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.
Choose Transit if
- You need real-time arrivals.
- You want to start without paying.
- You work on iOS, Android, Web.
- You also want multi-modal trip planning.
Questions people ask
- Is Lonboard or Transit better?
- Neither clearly leads. Lonboard starts at Free and Transit at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Lonboard or Transit?
- Lonboard starts at Free and Transit at Free.
- Does Lonboard or Transit run on more platforms?
- Lonboard runs on Linux, macOS, Windows. Transit runs on iOS, Android, Web.
- 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 Transit is typically brought in for.
- What can Lonboard do that Transit cannot?
- Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget. Transit covers Real-time arrivals, Multi-modal trip planning, Service alerts, In-app fare payment.
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.
Transit: Does Transit cost anything to use?
No. The rider app is free with no subscription and no ads; the company earns money separately by selling agencies a paid data and communication platform.
Lonboard: Who maintains it?
Development Seed, a geospatial engineering consultancy, as an open source project. There is no commercial support offering.
Transit: Does it work in every city?
No. Coverage depends on whether the local transit agency publishes a GTFS or GTFS-realtime feed; some smaller markets have static schedules only.
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.
Transit: Can I buy a bus or train ticket in the app?
Only in cities where the local agency has integrated fare payment; elsewhere you still need the agency app or a physical ticket.
Lonboard: Is it free for commercial use?
Yes, it is open source with no licence fee.
Related pages
Other head to heads
- Lonboard vs deck.gl
- Lonboard vs QGIS
- Lonboard vs CARTO
- Lonboard vs Fused
- Lonboard vs Potree
- Lonboard vs Foursquare Spatial Studio
- Lonboard vs SAGA GIS
- Lonboard vs GRASS GIS
- Lonboard vs WhiteboxTools
- Lonboard vs Kepler.gl
- Lonboard vs Agisoft Metashape
- Lonboard vs Leaflet
- Lonboard vs Sygic GPS Navigation
- Lonboard vs TomTom
- Lonboard vs Waze
- Lonboard vs What3words
- Lonboard vs TomTom Developer Portal
- Lonboard vs Citymapper
- Lonboard vs Ride with GPS
- Lonboard vs Google Maps
- Lonboard vs HERE WeGo
- Lonboard vs ArcGIS Survey123
- Lonboard vs Felt
- Lonboard vs MapQuest
- Lonboard vs Apple Maps
- Lonboard vs Gaia GPS
- Lonboard vs GraphHopper
- Lonboard vs IndoorAtlas
- Lonboard vs Esri ArcGIS
- Transit vs deck.gl
- Transit vs QGIS
- Transit vs CARTO
- Transit vs Fused
- Transit vs Potree
- Transit vs Foursquare Spatial Studio
- Transit vs SAGA GIS
- Transit vs GRASS GIS
- Transit vs WhiteboxTools
- Transit vs Kepler.gl
- Transit vs Agisoft Metashape
- Transit vs Leaflet
- Transit vs Sygic GPS Navigation
- Transit vs TomTom
- Transit vs Waze
- Transit vs What3words
- Transit vs TomTom Developer Portal
- Transit vs Citymapper
- Transit vs Ride with GPS
- Transit vs Google Maps
- Transit vs HERE WeGo
- Transit vs ArcGIS Survey123
- Transit vs Felt
- Transit vs MapQuest
- Transit vs Apple Maps
- Transit vs Gaia GPS
- Transit vs GraphHopper
- Transit vs IndoorAtlas
- Transit vs Esri ArcGIS
