https://github.com/croyla/bangalore_transit_app

Currently testing and working with bangalore transit data to visualize journeys from point to point
https://github.com/croyla/bangalore_transit_app

Last synced: 3 months ago
JSON representation

Currently testing and working with bangalore transit data to visualize journeys from point to point

• Host: GitHub
• URL: https://github.com/croyla/bangalore_transit_app
• Owner: croyla
• Created: 2024-05-09T14:19:18.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-06-11T10:52:26.000Z (12 months ago)
• Last Synced: 2025-01-16T05:23:04.813Z (5 months ago)
• Language: Dart
• Size: 15.8 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# bangalore_transit_app

A highly unoptimized unusable application built in flutter. The goal of this application is to find all possible (metro / bus) lines and transfers from point a to point b. It is not optimised and needs to be fiddled with to be used on a functional basis.

- Data for BMTC from [Vonter github repo](https://github.com/Vonter/bmtc-gtfs)

- Data for Namma Metro (BMRCL) from [geohacker github repo](https://github.com/geohacker/namma-metro?)

## Images from the application

###### 1. All stops overlayed on the map:

![stop_map](images/stops_map.png)

This overlay is slightly inaccurate due to icon offset, the more you zoom in the more accurate it gets. If it does not show the stops on the map initially please reload the map with the "Clear Map" button. These stops are clickable to get screen 2.

###### 2. Stop overview / information:

![stop_overview](images/stop_overview.png)

This lists all the routes touching this stop. The "Add Start" button is used to add a start / end to a journey. The routes are clickable to get screen 3, and the stops are also clickable to get the same screen of that stop.

###### 3. Route overview / information:

![route_overview](images/route_overview.png)

This lists all the stops this route touches. The stops are clickable to get screen 2.

###### 4. Options sidebar:

![options](images/options.png)

Closer stops only means only stops that are geographically closer to the destination will be counted for transfers, this prevents transfers such as Majestic > Banashankari > KR Market but also prevents viable edge cases at the moment (see To-Do)

###### 5. Journey Overview / information:

![journey_overview](images/journey_overview.png)

The journey is from Mallasandra Apartment to Kengeri, the leg of the journey is Mallasandra Apartment to Konanakunte Cross. 

###### 6. Journeys Overview:

![journeys_overview](images/journeys_overview.png)

This screen currently gets duplicated results, need to fine-tune and fix this. This lists all the possible journeys from "start" to "end".

###### 7. Journeys overlayed on the map:

![journeys_map](images/journeys_map.png)

The blue line is via Banashankari and the brown line is via Konanakunte Cross, these lines are clickable to get screen 5.

# To-Do

### (in no particular order)

- [ ] Use sharedprefs for Maximum Transfers, Walking Distance

- [ ] Prevent duplicate journeys in getRoutes

- [ ] Use route polylines for distance, not actual geographical distance (for closer stops setting)

- [ ] Use OSRM or something similar for getNearbyStops, and walk polyline

- [ ] Implement a local database for data storage as opposed to the current (always reading from) geojson implementation

- [ ] Modify metro data to be able to be parsed correctly by application

- [ ] Parse geojson info into the application more accurately (relations between stops and routes are a bit goofy at the moment)

- [ ] Store timing information where available to display as well

- [ ] SIFT THROUGH AND CLEAN GTFS DATA!!!