https://github.com/mierune/gtfs-go
QGIS-Plugin to parse GTFS data, to show and aggregate routes and stops.
https://github.com/mierune/gtfs-go
gtfs python qgis qgis-plugin traffic-analysis
Last synced: 10 months ago
JSON representation
QGIS-Plugin to parse GTFS data, to show and aggregate routes and stops.
- Host: GitHub
- URL: https://github.com/mierune/gtfs-go
- Owner: MIERUNE
- License: gpl-2.0
- Created: 2020-11-05T05:17:00.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2025-05-29T00:12:23.000Z (about 1 year ago)
- Last Synced: 2025-05-29T01:24:29.780Z (about 1 year ago)
- Topics: gtfs, python, qgis, qgis-plugin, traffic-analysis
- Language: Python
- Homepage: https://mierune.co.jp
- Size: 6.43 MB
- Stars: 121
- Watchers: 7
- Forks: 11
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# GTFS-GO
QGIS Plugin to extract GTFS-data as GeoJSON and render routes and stops on the Map.
## Usage
### General
#### Select datasource
- local zipfile
- download preset datasource
### Processing
#### Simple parsing - routes and stops
GTFS tables has routes-data and stops-data but tables-structure is somewhat complicated.
This plugin can parse them into simple routes and stops GeoJSON files, also set a beautiful style on layers.
#### Traffic frequency aggregation
GTFS also has service time-table information. This plugin can aggregate traffic frequency, how many times do each PATH used. PATH means lines between two stops.
In addition, it is possible to unify SIMILAR stops - having same parent_stop or same prefix or same stop_name and near to each.
- numbers along with lines indicate a frequency of each lines, set on left side towards direction of path (UK traffic style)
- larger number of frequency, lines become bolder
- result.csv is a table comparing before and after unified stops.
### unifying algorithm
You can see similar stops unified into one stop.
- before
- after
#### stops unifying rules
Smaller number of rules is prefered.
1. parent_stops
- if stops have parent_stops value, unifying them into parent station
- new stop_id is parent's one
2. stop_id prefix
- by defining delimiter, split stop_name into prefix and suffix, group same prefix stops
- new stop_id is the first stop's one in grouped stops ordered by stop_id ascending.
3. stop_name and distance
- unifying stops having same stop_name and near to each in certain extent - 0.003 degree in terms of lonlat-plane
- new stop_id is the first stop's one in grouped stops ordered by stop_id ascending.
#### unifying result
In result.csv, you can see stops unifying result.
## Acknowledgements
Version2.0.0, in which the frequency aggregating function is added, got technically and financially supported by [Toyota Mobility Foundation](https://toyotamobilityfoundation.jp/) and [Traffic Brain](https://t-brain.jp/). Thank you for great contributions!
## Contribution
### Translation
1. edit to `gtfs_go.pro` and add `GTFSGO_lang_encoding.ts` inside the `TRANSLATION` variable
2. cd i18n
3. generate the translation files with `pylupdate5 ../gtfs_go.pro` on debian you have to install pylupdate with `apt install pyqt5-dev-tools`
4. edit the newly generated file GTFSGO_lang.ts to contain the new translations
5. generate qm file with `lrelease GTFSGO_lang_encoding.ts`
### new data sources
- Some data sources can be added from [here](https://transitfeeds.com/search?q=gtfs) however you need to check they have all the [required](https://github.com/MIERUNE/GTFS-GO/blob/master/gtfs_parser/constants.py) .txt files
### Tests
- needs pandas
```
pip install pandas
```
```
cd GTFS-GO
python -m unittest discover gtfs_parser/tests
```