Quebec City/RTC GTFS Import

This page describes the proposed import process of GTFS data for the RTC bus service provider in the Urban agglomeration of Québec, Quebec, Canada.

Community Buy-in

Pending

License Approval

Existing RTC network downloaded into JOSM

The license approval is pending. The project will be added to the Imports Catalogue.

Before Starting

The current state of the network (before import) is shown in the image to the right. There are very few stops and a total of 4 routes mapped, 3 of which are incomplete. Nevertheless, I corrected the tag information with respect to PTv2 requirements as well as GTFS requirements manually to make the existing data handling during import easier. This was only possible because there was very little already mapped. In the future, when updating the network using a bulk import, there should be no need to correct things manually because everything should be identical or very close to PTv2 and GTFS standards already.

Proposed Import Process

I propose to do the import using a Python script that generates JOSM XML files, handles conflation within the GTFS dataset and with respect to existing OSM data automatically. It doesn't delete any existing data but rather adds action=modify tag to existing data if need be and preserves all existing ids. It also makes sure changes to existing data also cascade to relation members. The script takes a RTC GTFS zip file as input and executes the steps summarized below (latest from here). The script is a work in progress and it meant as tool to help and not fully automate everything. It can accessed here.

1. Unzip GTFS archive and load data in to memory.
2. Using the calendar_dates.txt file/data, it finds the latest service_id in order to ensure only the latest data will be imported.
3. Filters the whole GTFS dataset keeping only data that corresponds to the latest service_id.
   

   GTFS stops unique by stop_id and stop_code with slightly different coordinates and how they get merged. Stops within 5 meters from each other get merged.
4. Writes the GTFS stops to GeoJSON for visualization (to spot apparent problems and potential problems).
5. It downloads existing OSM data using overpy. This includes existing bus stops (nodes), route relations, and route_master relations along with the member nodes and ways. It converts the data into an internal format to be able to work with it in the script.
6. Handles conflation within the GTFS dataset stops.
7. Creates new OSM nodes for the stops making sure to not duplicate or delete existing stops (explained in detail below).
8. For each trip (trip_id) for a given route (route_id), it finds the longest trip for each direction (the one with the most number of stops).
9. It creates the OSM routes and master_route relations using the identified longest trips respecting transportv2 requirements. It handles conflation with existing relations (explained in detail below).
10. Write the JOSM XML files (nodes and relations)

Conflation handling with existing stops in OSM

In a similar fashion conflation between already merged GTFS stops and existing OSM stops is handled by checking if there are any existing stops in OSM that are with x meters (distance used was 5 meters) of each GTFS stop. If there are, the tags of the existing OSM stop and coordinates are replaced by the corresponding information of the GTFS stop keeping the existing OSM id and other information intact. In a single case, there was more than one existing OSM stop in the vicinity of a GTFS stop. I handled this case manually and reran the script. This check (checking of existing stops in proximity to GTFS stops) is only done with existing stops that are within the boundaries of the Urban agglomeration of Québec.

Conflation handling with existing relations in OSM

Once the route relations are created by the script, it compares them with existing route relations that match the name, operator, and ref tags from OSM when applicable. Any matching existing route relation gets assigned new tags (from the GTFS) dataset and the member nodes are all replaced with new nodes (that are a result of the stop creation and conflation handling from the previous steps). The member ways remain intact as they are better handled manually in JOSM (if there is a need to change/update them).

The generated XML file imported into JOSM

Route_master relations are handled in a similar fashion where existing route_master relations all get new tags and in this case the member relations are completely replaced by new ones (already created and conflation handled in the previous steps).

During any conflation handling with existing data (nodes, or relations), the existing node, way, or relation, gets a action=modify tag written in the output XML.