Which application or package is this feature request for?
schedule, stations
Feature
With the incoming new line and extension to North-South Line it's a perfect time to add MRT schedule support. The schedule data already available in https://jakartamrt.co.id/id/val/stasiuns as raw json data but cleanup and formatting will be needed.
Ideal solution or implementation
Proposed endpoint urls:
- Station
/mrt/stations/ - list of stations
/mrt/schedules/ - current schedule
/mrt/routes/ - current route
Challenge
Current schedule data which obtained on https://jakartamrt.co.id/id/val/stasiuns has some weird gap and inconsistency, so some "hardcoded" or "fictional" time needs to be added, (note: these data will be marked as fictional and will be skipped on returns).

With this, the current schedule schema will need to be modified to mark these schedule.
{
"id": "sc_mart",
"station_id": "AC",
"station_origin_id": "JAKK",
"station_destination_id": "TPK",
"train_id": "2400",
"line": "MRT NORTH-SOUTH LINE",
"route": "LEBAKBULUS-BUNDARANHI",
"departs_at": "2024-03-10T09:55:07.213Z",
"arrives_at": "2024-03-10T09:55:09.213Z",
"is_active": false // <-- marking fictional/hardcoded schedule
"metadata": {
"origin": {
"color": "#DD0067"
}
},
"created_at": "2024-03-10T09:55:07.213Z",
"updated_at": "2024-03-10T09:55:07.213Z"
}
Which application or package is this feature request for?
schedule, stations
Feature
With the incoming new line and extension to North-South Line it's a perfect time to add MRT schedule support. The schedule data already available in https://jakartamrt.co.id/id/val/stasiuns as raw
jsondata but cleanup and formatting will be needed.Ideal solution or implementation
Proposed endpoint urls:
/mrt/stations/- list of stations/mrt/schedules/- current schedule/mrt/routes/- current routeChallenge
Current schedule data which obtained on https://jakartamrt.co.id/id/val/stasiuns has some weird gap and inconsistency, so some "hardcoded" or "fictional" time needs to be added, (note: these data will be marked as fictional and will be skipped on returns).
With this, the current schedule schema will need to be modified to mark these schedule.
{ "id": "sc_mart", "station_id": "AC", "station_origin_id": "JAKK", "station_destination_id": "TPK", "train_id": "2400", "line": "MRT NORTH-SOUTH LINE", "route": "LEBAKBULUS-BUNDARANHI", "departs_at": "2024-03-10T09:55:07.213Z", "arrives_at": "2024-03-10T09:55:09.213Z", "is_active": false // <-- marking fictional/hardcoded schedule "metadata": { "origin": { "color": "#DD0067" } }, "created_at": "2024-03-10T09:55:07.213Z", "updated_at": "2024-03-10T09:55:07.213Z" }