Skip to content

In the pythons extensions section let's create a new "transit" edge provider. It takes a gtfs file. The edge expansion specification follows: [Contains lat/lon/time] -> for every nearby stop, a vertex with stop_id, and time at arrival [Contains stop id] -> for every vehicle departure in the next X hours, a vertex representing being on the vehicle moments after boarding. It should have (time, trip_id, stop sequence in trip, and "vehicle_state:boarding"). This is a boarding vertex... #12

In the pythons extensions section let's create a new "transit" edge provider. It takes a gtfs file. The edge expansion specification follows: [Contains lat/lon/time] -> for every nearby stop, a vertex with stop_id, and time at arrival [Contains stop id] -> for every vehicle departure in the next X hours, a vertex representing being on the vehicle moments after boarding. It should have (time, trip_id, stop sequence in trip, and "vehicle_state:boarding"). This is a boarding vertex...

In the pythons extensions section let's create a new "transit" edge provider. It takes a gtfs file. The edge expansion specification follows: [Contains lat/lon/time] -> for every nearby stop, a vertex with stop_id, and time at arrival [Contains stop id] -> for every vehicle departure in the next X hours, a vertex representing being on the vehicle moments after boarding. It should have (time, trip_id, stop sequence in trip, and "vehicle_state:boarding"). This is a boarding vertex... #12

Triggered via dynamic July 26, 2025 07:05
Status Success
Total duration 18m 28s
Artifacts 1

copilot

on: dynamic
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size Digest
results Expired
298 Bytes
sha256:6da99b71acb04b824fdee6b02c99f50eb31909c144e5e00c7514c9b518c35b3b