search

GeoDaCenter / spatial_access

https://spatial.uchicago.edu
37 stars 11 forks source link

Convert transit format to the one p2p can read #22

Closed jkoschinsky closed 5 years ago

jkoschinsky commented 5 years ago

Dan's transit matrices from OpenTrip Planner are stored in a different format (closer to our spatial weights matrix format). One example for Seattle (he's generating this for 20 cities):

https://lab.dfsnow.me:8080/matrix/seattle_matrix.csv.bz2

Please convert this format to the one that p2p can read as input.

lmnoel commented 5 years ago

Are these matrices guaranteed to be symmetrical?

lmnoel commented 5 years ago

And what precisely do the ids correspond to?

jkoschinsky commented 5 years ago

Yes, matrices will always be symmetrical (NxN). IDs are FIPS codes for Census tracts.

The format is: ID origin, ID destination1, travel time ID origin, ID destination2, travel time ...

For transit, self-times are included (oddly, for transit, they are sometimes slightly over zero depending on the method of calculating travel time in OpenTripPlanner). The Seattle link I had sent was for transit.

However, for driving, self-times are excluded because they're generated based on pgrouting. I'll send you an example of the driving format separately.