search

GeoDaCenter / geoda

GeoDa: An introduction to spatial data analysis
http://geodacenter.github.io
GNU General Public License v3.0
705 stars 156 forks source link

classic regular regression, spatial lag, spatial error #290

Closed lixun910 closed 8 years ago

lixun910 commented 8 years ago

It crashed with a US. census tract polygon shapefile unnamed 2

lixun910 commented 8 years ago

This can't be reproduced after several related fixes of weights. One possible reason for this crash is out-of-memory, since this dataset will take up 1.5 Gb memory.

jkoschinsky commented 8 years ago

GeoDa 1.7.87

Steps:

  1. Load tract shapefile (will send link in separate message, 400+MB) in Win 7 Professional (64-bit): unhandled exception error message

In OSX Yosemite, 10.10.5

  1. Add basemap --> crash but then I tried again and it loads the basemap ok

Weights creation, histogram and connectivity map all created within seconds, which is impressive since file has over 73k records.

If you can try on your end to see if you can replicate the crash.

lixun910 commented 8 years ago

tested on my side OSX 10.6 10.10 Windows 7 32bit. Works fine. This data loading takes 1,5 Gb memory. Can you verify again? Thanks! screen shot 2016-03-04 at 1 57 52 pm

jkoschinsky commented 8 years ago

right - loading works fine but creation of distance matrix took over 20 min and still spinning so I force-quit.

On 4 March 2016 at 13:59, Xun Li notifications@github.com wrote:

tested on my side OSX 10.6 10.10 Windows 7 32bit. Works fine. This data loading takes 1,5 Gb memory. Can you verify again? Thanks! [image: screen shot 2016-03-04 at 1 57 52 pm] https://cloud.githubusercontent.com/assets/2423887/13540007/4ae0e046-e211-11e5-8aac-41ad2f655a85.png

— Reply to this email directly or view it on GitHub https://github.com/lixun910/geoda/issues/290#issuecomment-192465101.

Julia Koschinsky, Ph.D. Research Director Associate Research Professor Arizona State University School of Geographical Sciences and Urban Planning GeoDa Center for Geospatial Analysis and Computation julia.koschinsky@asu.edu

http://geodacenter.asu.edu http://www.facebook.com/geodacenter http://twitter.com/GeoDaCenter

lixun910 commented 8 years ago

Just tested: contiguity and KNN weights can be created in seconds. Threshold weights using bydefault value hands their -- I think that's because the by default value are too large, which makes every polygon searches too many neighbors (considering 73K records). Should user takes own risk of what a reasonable threshold should be input especially for a relatively large dataset?

jkoschinsky commented 8 years ago

yes, that's fine. We can close this.