Skip to content
BusRouter SG: Singapore Bus Routes Explorer
JavaScript CSS HTML
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Create FUNDING.yml Nov 2, 2019
art Updated artwork Oct 14, 2019
assets Upgrade all dependencies, fix bugs Apr 11, 2020
bus-arrival Upgrade to new arrivelah2 endpoint Jun 5, 2019
bus-first-last Track hash paths Feb 5, 2019
icons 1024x1024 icon image Nov 18, 2018
screenshots Feature graphic for Google Play Feb 10, 2019
tasks Changes and add debugging for scripts Jul 14, 2019
utils Fix text not rendering Oct 30, 2019
visualization Upgrade all dependencies, fix bugs Apr 11, 2020
well-known Add well-known files Feb 10, 2019
.babelrc Upgrade to core-js 3 Aug 17, 2019
.env.example Add README for env variables, add .env.example file Mar 17, 2019
.gitignore Ignore vscode settings folder Jun 5, 2019
.htmlnanorc Initial ‘next’ commit Oct 11, 2018
.postcssrc Inline mapbox’s CSS to remove one extra blocking call Nov 1, 2018
.posthtmlrc Extra config for posthtml, seems to be needed for next Parcel version Dec 22, 2018
CNAME Add README for env variables, add .env.example file Mar 17, 2019
cssnano.config.js Cssnano’s mergeLonghand messes up the safe area env CSS Nov 6, 2018
favicon.ico Update favicon Mar 26, 2016
index.html Remove traces of maptiler Apr 11, 2020
manifest.webmanifest Fix web manifest bug Dec 25, 2018
netlify.toml Use the BusRouter SG styles for static maps Jul 23, 2019
package-lock.json Upgrade all dependencies, fix bugs Apr 11, 2020
package.json Upgrade all dependencies, fix bugs Apr 11, 2020

BusRouter SG - Singapore Bus Routes Explorer

🚌 🗺 🇸🇬

Explore bus stops and routes on the map for all bus services in Singapore, with realtime bus arrival times and per-bus-stop passing routes overview.

Screenshot of BusRouter SG

Screenshot of BusRouter SG

Complete Feature Set

  • Show full route with all bus stops for every bus service.
  • Show all bus stops when zoomed in.
  • Show all routes that pass through one bus stop.
  • Show bus arrival times for a bus stop.

Previously known as Singapore Bus Routes Explorer, abbreviated as 'SBRE' and previously looks like this:

Screenshot of Singapore Bus Routes Explorer

🔖 Story

This web app is first build in 2012, to fulfill my curiosity about buses. Ever since then, I've been maintaing the app and data until today.

👉 Read more about it: Building BusRouter SG .

🛠 Technicalities


All data such as bus stops, services and routes are mostly scraped from, which means they are copyrighted by the Land Transport Authority.

Node.js is required to run the tasks to scrape data, massage the data, and run this web app.

Before running anything, run npm i to install all required dependencies.

Notes before diving in:

  • There are three important terms: stop, service and route.
  • One service have one or many routes, usually maximum two routes. It may be an A-to-B route or A-to-A route (roundtrip).
  • Services with two routes may contain A-to-B and B-to-A routes with different list of stops, usually on the opposite sides of the road. Some services may contain A-to-B and C-to-D routes where the first stop of a route may not be the last stop of the 2nd route, etc.

Before running the scripts, some environment variables are required. This project uses dotenv so one of the easier ways to add environment variables is:

  1. Duplicate .env.example file (copy & paste)
  2. Rename to .env
  3. Open the file and configure the variables

One of environment variables is ltaAccountKey which you'll need to request. The rest should be self-explanatory.

The scripts are:

  • node tasks/fetchServices
  • node tasks/fetchServiceStops
    • Loop through all bus services and scrape{SERVICE_NUMBER}.html
    • Grabs a list of stops for every service
    • Generates serviceStops.json, a mapping of every service to stops, separated by routes.
    • Generates stops.json, a list of stops with names and coordinates
  • For route polylines (route lines of a service between all stops, containing just a list of coordinates), everything is scraped from their respective sources, ignoring dirty data, in best-effort ways:
    • MyTransport.SG: node tasks/fetchRoutesMyTransportSG - most reliable so far, but some lines are kind of weird and overlapping in wrong ways
    • OneMap.SG: node tasks/fetchRoutesOneMapSG
    • TowerTransit.SG: node tasks/fetchRoutesTowerTransitSG - pretty reliable source
    • Mapbox: node tasks/fetchRoutesMapboxAPI - using Mapbox Directions API to fill in the blanks, for services that don't have routes.
    • node tasks/exposeFaultyRoutes - for exposing routes that may be faulty, which is good for comparing the quality for all sources above.
  • For stops, everything is scraped from their respective sources too, to get stop names and (hopefully) accurate coordinates:
    • LTA DataMall: node tasks/fetchStopsLTA
    • OneMap.SG: node tasks/fetchStopsOneMap
    • OpenStreetMap: node tasks/fetchStopsOverPass - data queried via OverPass API, generated with Overpass Turbo
    • node tasks/repositionStops - Generates stops2.json with additional stop names and (hopefully) more accurate coordinates
    • node tasks/repositionStopLabels - Generates stops3.json with adjusted label positionings.
  • node tasks/fetchRoutesLTA
    • Fetches all routes with stop information for approximate arrival times for first and last buses.
    • The approximate arrival times are for every single stop. They are not the first bus that departs from first stop or last bus towards last stop. Every. Single. Stop.
    • Generates routes.lta.json, a mapping of all stops to services with approximate arrival times for first and last buses.
  • For generating GeoJSON files
    • node tasks/geojsonRoutes
    • node tasks/geojsonStops
  • For generating final JSON files to be consumed by the web app
    • node tasks/fetchAbbrs
    • node tasks/generateServices
      • Service names are dynamically generated from the stops
      • Generates for usage in web app
    • node tasks/generateStops
      • Stop coordinates are rounded to 5-number precision
      • Generates for usage in web app
    • node tasks/generateRoutesPolyline
    • node tasks/generateFirstLast
      • Approximate arrival times for first and last buses for every service in every single stop
      • Generates for usage in web app
  • For fun
    • node tasks/trivia - Trivia questions with answers

Current version of the data is 3, all located under ./data/3 folder. All JSON files are "immutable", in the sense that all scripts above do not modify existing JSON files that are generated by other scripts. Every script is written to only create or modify its own JSON files and should not overwrite other JSON files.

Everything else are older versions of the data and being left there for legacy reasons.

When there's a data update, run the scripts in these order:

  1. node tasks/fetchServices
  2. node tasks/fetchServiceStops
  3. Stops data
    1. node tasks/fetchStopsOneMapSG
    2. node tasks/fetchStopsOverpass
    3. node tasks/repositionStops
    4. node tasks/repositionStopLabels
  4. Routes data
    1. node tasks/fetchRoutesMyTransportSG --override
      • Mutates/updates the routes data because of override option
      • Doesn't delete services/routes that are gone
    2. node tasks/fetchRoutesOneMapSG --override
      • Mutates/updates the routes data because of override option
      • Doesn't delete services/routes that are gone
    3. node tasks/fetchRoutesMapboxAPI
      • Usually not needed, unless there are routes that are missing
      • Doesn't delete services/routes that are gone
  5. First/last bus data
    1. node tasks/fetchRoutesLTA
  6. GeoJSON data (not used in web app)
    1. node tasks/geojsonStops
    2. node tasks/geojsonRoutes
  7. Finalized data (used in web app)
    1. node tasks/fetchAbbrs
      • To be used for next two scripts.
    2. node tasks/generateStops
    3. node tasks/generateServices
    4. node tasks/generateRoutesPolyline
    5. node tasks/generateFirstLast


There's a separate visualization mini-site on /visualization/ URL.

The scripts to generate the data, in order:

  1. node visualization/build-routes
    • Reads stops2.json and transform routes data with "levels" for 3D extrusion
    • Generates visualization/data/routes.json for usage on mini-site and visualization/data/levels.json to be read by the build-stops script
  2. node visualization/build-stops
    • Reads stops.geojson and buffered into circle polygons which will be 3D-extruded
    • Generates visualization/data/stops.3d.json for usage on mini-site

Web App

The scripts for the web app:

  • npm start - start server for development
  • npm run build - build for production and deployment, in ./dist folder.

📜 License

Data © LTA © OneMap © OSM contributors. Everything else: MIT

🎤 Feedback

If you have any feedback, tweet me at @cheeaun.

🙇‍ Credits

You can’t perform that action at this time.