MGMLaboratory
Back

Menu

01Home
02About Us
03Projects
04Publications
05Member
06Articles
07Contact

Let's Talk

Open in Mail app

Socials

Malang (ID) --:--Privacy PolicyTerms of Service

November 5, 20172 min read

Sketching a REST API for Malang Public TransportSketching a REST API for Malang Public Transport

The proposed service would answer cost, time, and booking questions for local transport riders.

  • Journal
  • Publications

Written by

  • SRShirasaka RenIT & Infrastructure · Student Member

In this article

  1. 01What the proposed API should offer
  2. 02Six indices per mode
  3. 03Why a web service rather than an app

Information technology has already improved public transport in many cities, but Malang had little of it in 2017. Riders had no reliable way to find out which vehicle serves a route, how long the trip takes, or what it costs. Two researchers from Universitas Brawijaya responded with a design for a REST API that local transport services could expose.

01/03

What the proposed API should offer

The paper is a design proposal, and its main output is a list of capabilities the interface should carry.

  • A search facility that finds the right mode of transport for a trip.
  • Cost estimation and time estimation for that trip.
  • The ability to call or book a public transport vehicle.
  • A list of every mode available, plus detailed records for a single mode, including its route.
An angkot, the share taxi format common in Indonesian cities. Image: Bayu Oktarino, CC BY-SA 4.0.
Fig. 01An angkot, the share taxi format common in Indonesian cities. Image: Bayu Oktarino, CC BY-SA 4.0.

02/03

Six indices per mode

The detailed record for each mode carries more than a name and a line on a map. The design calls for an index of comfortability, security, safety, privacy, availability, and accessibility. Those six values give an application something to compare and filter on, which is what turns a transport directory into a service that helps someone choose.

Angkot queued along a street. Image: Teguhj, CC BY-SA 4.0, via Wikimedia Commons.
Fig. 02Angkot queued along a street. Image: Teguhj, CC BY-SA 4.0, via Wikimedia Commons.

03/03

Why a web service rather than an app

The authors frame the work as service-oriented architecture and expose it through REST, with the keywords listing web service design as the approach. Putting the data behind an interface means any developer can build a rider application on top of it, and the transport operator manages one source of truth.

It is worth being clear about the stage. The paper presents a draft proposal of the interface. It does not report a deployed service or a measured outcome, so the value here is the specification itself.

Source

  1. Agi Putra Kharisma and Aryo Pinandito (2017). Design of REST API for Local Public Transportation Information Services in Malang City. Journal of Information Technology and Computer Science.

    DOI10.25126/jitecs.20172226 (opens in a new tab)

Next articleWhat Happens to Your Layout on a Small Screen(Keep scrolling)(Read it next)(Loading)