Open DOSull opened 5 years ago
Hi David. thanks for reaching out. The intention in original code was to weight the edges by the number of trips (.N
) between each pair of stops so it would consider the service frequency. I wrote this code when I was writting a paper on the intersection of complex networks and transport geography, looking at network science and accessibility.
However, I do recognize that it makes sense to weigh by travel_time
, it depends on the purpose of the analysis. Are you doing routing analysis?
my comment was based on the documentation which says "with information on route frequency and on travel time". I missed the first and was focused on the second.
Either way, it has become clear to me that the resulting network is of limited usefulness for detailed analysis, since it will tell you the 'nearness' (in some sense) of stops, but information about how routes chain places together over multiple stops at a particular time of day is lost in the summarisation.
Still a fun script to mess around with.
I see. David, it sounds like you're looking for clustering techniques / community detection in spatial networks. Perhaps you would be interested in having a look at these papers, if you haven't already:
Hi, Found this useful messing with GTFS (thanks!) but I think there is an error in line 301
which results in the edge weights being some effectively arbitrary nonsense. Corrected to
and I got results more to my liking!