search

GeoDaCenter / spatial_access

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

increase impedance #58

Open ifarah opened 5 years ago

ifarah commented 5 years ago

I compared Logan's, Dan's, and GoogleMaps' results for a tract in Lincoln Park, Hyde Park, and Midway: The results increased but are still below. Could you increase the impedance a bit more so I can rerun and revalidate?

  1. LP: Origin: 17031071100 (41.921800, -87.651100) Destination: 17031460400 (41.744500, -87.563700) Logan:1351 (22.52) NOW: 1357 (22.61) Dan:1440 (24) Googlemaps: 26-35 min

  2. HP Origin: 17031836200 (41.790469, -87.601284) Destination: 17031170100 (41.955900, -87.794800) Logan:1468 (24.46) NOW: 1762 (29.36) Dan:1980 (33) Googlemaps: 28-60 min

  3. Midway Origin: 17031561100 (41.788869, -87.771909) Destination: 17031030400 (41.986952, -87.672079) Logan:1674 (27.9) NOW: 1886 (31.43) Dan:2040 (34) Googlemaps: 30-50 min

lmnoel commented 5 years ago

yep, will do

lmnoel commented 5 years ago

Were you able to update the configs @ifarah?

ifarah commented 5 years ago

Yes! It worked by defining it locally.

lmnoel commented 5 years ago

Do you have updated parameters that work better that I should persist to the package?

ifarah commented 5 years ago

Not yet, since we're still stuck with the "spatial extent" maximum. Will do whenever we fix the other issue.

lmnoel commented 5 years ago

@ifarah pinging here also, see require_extended_range boolean of Configs

ifarah commented 5 years ago

Still need to check how this change looks when comparing to Dan's