Ability to remove a stop and show the projected result

[RaenonX]

Exploitable metrics

• Passenger Travel Time (to stops)
  • Create random agents and measure their traffic time from the place around the removed stop to the random destination.
  • Could replace "random agents" of the above with corresponding population data to increase the accuracy of the simulation. Reference
• Bus Travel Time #22
  • Estimate the chance of bus stopping at a certain stop to estimate the bus traveling speed.
  • Too many stops will increase the traveling time of a single trip for the bus.
• Budget Change #23
  • Need to find the budget data first
• Passenger Flow
  • If we can somehow get the hourly flow data, then this would be implementable. (#6 @yayen-lin)

Notes

• We need to determine how we will use the application (via CLI or Flask), then to implement this.
  • It's best to be able to compare the before and the after, so Flask might be preferred. However, it takes more time to implement than CLI (usually).

[RaenonX]

Work by @jmsusanto

Population data overlap with the current metro routes and the BRT routes in the future. Jeremy's Bus Sim Study (Starter).zip

[RaenonX]

@jmsusanto

I just checked your nb. It looks exploitable!

It feels like you've already gained some knowledge about the population data. For this, I think the "random agent" of the original proposal can be replaced with simulated agents according to the population density, so that the randomness could be reduced while the accuracy could be increased.

[RaenonX]

22 and #23 for continued work.