https://github.com/croyla/bmtc-platforms-geojson
[Unofficial] Collections of BMTC platform / route information in JSON/GeoJSON format
https://github.com/croyla/bmtc-platforms-geojson
Last synced: 4 months ago
JSON representation
[Unofficial] Collections of BMTC platform / route information in JSON/GeoJSON format
- Host: GitHub
- URL: https://github.com/croyla/bmtc-platforms-geojson
- Owner: croyla
- License: mit-0
- Created: 2024-12-23T08:26:43.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2025-01-03T14:06:08.000Z (5 months ago)
- Last Synced: 2025-01-03T15:21:58.082Z (5 months ago)
- Language: Python
- Size: 594 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.MD
- License: LICENSE
Awesome Lists containing this project
README
## [Unofficial] BMTC Platform information in GeoJSON
Unofficial GeoJSONs platform-route information for bus stands in bengaluru
in geojson file format.
### Output Files
Output files are in `out/`. These contain `platforms-routes-.geojson`
Every feature is a point. Each feature represents a platform. Each feature contains the following properties:
| Property | Value | Optional | Description |
|----------|--------|----------|-----------------------------------------------------------------------------------------|
| Platform | String | no | A human-readable unique name of the platform |
| Alias | List | yes | A list of names the BMTC-API asociates with this platform (E.g B2 and 2) |
| Routes | List | no | A list of objects that pass through this platform (According to BMTC and our overrides) |
A route object contains the following properties:
| Property | Value | Description |
|-------------|-----------------|---------------------------------------------------------------------------------------------------------------------|
| Name | String | The route number of this route |
| Destination | String | The destination stop name of this route |
| From | Integer | The BMTC-API ID for the stop this platform/route is associated with |
| UniqueName | String | The "routename" value provided by the BMTC-API or labelled as shor-name in the gtfs, this doesnt have to be unique. |
| Id | Integer | The BMTC-API ID for this route |
| BayReported | Null or Integer | The bay this is reported to be in. |
| Stops | List | A list of stop names this route is known to go through, this is not necessarily exhaustive. |
### Input Files
Input files are in `in/`. These contain the platform location for each stop. These files are user-contributed geojson files. The naming format is `platforms-.geojson`
These are processed and populated by the script.
Every feature is a point. Each feature represents a platform. Each feature contains the following properties:
| Property | Value | Optional | Description |
|----------|--------|----------|--------------------------------------------------------------------------|
| Platform | String | no | A human-readable unique name of the platform |
| Alias | List | yes | A list of names the BMTC-API asociates with this platform (E.g B2 and 2) |
### Raw Files
Raw files are in `raw/`. These files contain route - platform data in json files. The naming format is `platforms-.json`
These files are intermediary files that are then used to populate the `in/` files and generate `out/` files.
### Running it yourself
#### 1. Installation
Clone the repo in your desired directory.
#### 2. Dependents
Ensure you have the python package `csv` installed, and you are using python 3. You must have a local bmtc-gtfs copy
with proper BMTC-API IDs to run the script.
#### 3. Running
You can run the program itself by running `python3 ... `.
Please have a look at `raw/commands.txt` for a clearer understanding.
### Contributing
- The data for platforms - routes mapping is taken from BMTC-API, it is not accurate all the time. Simply creating an issue
for an inaccurate or unknown route wherein you can provide the actual platform for the route will allow this to be rectified
- The geojson / geographic data is manually created, and it may be inaccurate. Should new platforms open up, or old
platforms shut down, this would need updating. Please create an issue for this matter, and provide your changes to existing
files in a PR in which the issue is mentioned.
- The current stop collection does not represent all platformed stops operated by BMTC. If you are aware of one please raise
an issue on this repository. If you have already created a geojson for the same please create a PR referencing the issue.
- There are numerous platforms and buses that are not in the files. Please have a look at the `help/` directory to see where you can help.
The help directory is structured into "Unknown" and "Unsorted". "Unsorted" refers to an unrecognised platform, "Unknown" refers to no platform information.
- To add a new feature, fix a bug, or optimise some code please create the relevant issue and reference it in your PR.
- To update the files, please create a PR with the description noting the date, and if possible please link / upload the gtfs used for the run.
#### Tools for Contributing
- [geojson-blrtransit](https://geojson.blrtransit.com/)
- [geojson.io](https://geojson.io/)
- [bmtc-gtfs github](https://github.com/Vonter/bmtc-gtfs/)
### Credits
- [Namma BMTC](https://bmtcwebportal.amnex.com/commuter/dashboard)
- [Vonter's bmtc-gtfs](https://github.com/Vonter/bmtc-gtfs)