OwlBoard

OwlBoard is both a backend API, and a frontend Arrival/Departure board webapp.

Powered by Node.JS and using the ldbs-json module, the OwlBoard API provides up to date train departure information for any station in the UK.

Whilst the application is open source, the webservice (owlboard.fb-infra.uk) is not openly available. National Rail Enquiries have limits on API access so to use this software yourself, you'll need to run your own instance after obtaining your own API key.

The webservice (owlboard.fb-infra.uk) may contain ads to support the running of the service, if ads are implemented, I intend to avoid 'dubious' advertisers that target and track users.

Currently only the public API is available as I am currently unable to request a key for the staff version.

Requirements:

To run this server you will need:

• Docker or Kubernetes

WebApp Colours:

• See CSS Variables

API Endpoints:

• /api/v1:

  • /test:

    • GET: Check your connection with the server
      • If Authentication: Basic header is provided your key will be checked, if not then just the conenction will be tested.

  • /list:

    • GET: Get list of stations

      • Request Header - Basic Auth -- Not Currently Implemented/Required on this route
      • Returns JSON: {"STATION NAME":{"CRS":"code","TIPLOC":"code"}}

    • /all:

      • GET: Get full CORPUS Data
      • Returns JSON in original CORPUS format minus any blank values.

  • /ldb:

    • /{crs}:
      • GET: Get arrival/departure board for {crs}
        • Request Header - Basic Auth -- Not Currently Implemented/Required on this route
        • Returns JSON: Formatted as per ldbs-json module.

  • /gitea:

    • POST: Post issue to Gitea Repo
      • Not yet implemented, submit issues at https://git.fjla.uk/fred.boniface/owlboard

• /api/kube:

  • /alive:

    • GET: Check alive
      • Returns JSON: {"status":"alive"}

  • /ready:

    • GET: Check ready
      • Returns JSON: {"state":""} ready or not_ready.

Stack:

• app.js -> Launches server, Entry Point, defines routers and middlewares.

  • routes -> Routers - Directs requests to controllers.

    • controllers -> Checks auth, sends response. Request doesn't pass further.
      • services -> Provide data and do tasks, uses other services and utils.

  • utils -> Provide utility functions that can be called by services.

  • configs -> Provide configuration details for other files.

  • static -> Holds files for static service, should be hosted behind a caching proxy.

Configuration:

The app is designed to be run within Kubernetes or within a Docker container, as such configuration is provided with environment variables. See the variable name and default options below. If a required configuration is not present the program will exit when that feature is initialised.

VAR	DEFAULT	REQUIRED	PURPOSE
OWL_SRV_PORT	8460	NO	Web Server Port
OWL_SRV_LISTEN	0.0.0.0	NO	Web Server Listen Address
OWL_DB_USER	owl	NO	Database Username
OWL_DB_PASS	twittwoo	NO	Database Password - Do not leave as default in production
OWL_DB_NAME	owlboard	NO	Database Name
OWL_DB_PORT	27017	NO	Database Server Port
OWL_DB_HOST	localhost	NO	Database Server Host
OWL_LDB_KEY		YES	National Rail LDBWS API Key
OWL_LDB_SVKEY		NO	National Rail LDBSVWS API Key
OWL_LDB_CORPUSUSER		YES	Network Rail CORPUS API Username
OWL_LDB_CORPUSPASS		YES	Network Rail CORPUS API Password
OWL_GIT_ISSUEBOT		NO	Gitea API Key for issue reporting

In the case that OWL_LDB_SVKEY is not available, staff versions of departure board, etc. will not be available.

In the case that OWL_GIT_ISSUEBOT is not available, the 'Report Issue' page will not be able to POST data.

Database Layout

The OwlBoard application will build the database if required at startup. All it needs is authentication details for a MongoDB server.

Collections

Collection	Contents	Purpose
corpus	Raw CORPUS data with blank keys removed	Code lookups
stations	Cleaned CORPUS Data, any objects with blank 3ALPHA & STANOX fields are removed	Validation before fetching Arr/Dep boards
meta	Lists the update time of corpus and station data	Will be used to update after a predetermined time period

Note that even after removing all objects from the CORPUS with a blank 3ALPHA & STANOX, many items remain which are not stations and will not have a board available. Going forwards methods to remove non-stations from this data will be introduced.