search

GeoDaCenter / spatial_access

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

ERROR: Running driving meters (increase "infinity") #63

Closed ifarah closed 5 years ago

ifarah commented 5 years ago

For estimating meters, this ran super fast but gave me almost all "infinity" since the distances are really large. Is there a way to increase "infinity"?

Screen Shot 2019-04-24 at 5 45 32 PM Screen Shot 2019-04-24 at 5 45 40 PM
ifarah commented 5 years ago

Where can we expand the spatial extent? Now it's set approximately to 60 km? Or what is the maximum area for computing the actual value?

ifarah commented 5 years ago

Also, could 'infinity' be set as a different number than '65535'? Now it it seems like an actual value. Could it be '-1' instead?

ifarah commented 5 years ago

I want to change line 44 of NetworkInterface.py: self.area_threshold = None if disable_area_threshold else 5000 # km

I changed the line locally, but it's not reading it when I read in the package. how can I change things locally @lmnoel ?

lmnoel commented 5 years ago

I'm not completely sure what you are asking. Will you be in at ~2 today @ifarah ?

ifarah commented 5 years ago

It's basically throwing an error because the bounding box is too large. The maximum is 2000 km2, but the bounding box for Chicago is 2067.3912994771686km2

lmnoel commented 5 years ago

The bounding box too large and the 65535 are two separate issues--the boolean flag in the TransitMatrix should disable the bounding box too large exception. Is that not the case?

ifarah commented 5 years ago

Yes. I agree they are two issues. Not sure what flag you're talking about. I'll be here at 2 pm.

lmnoel commented 5 years ago

clarified in #64