Timeline for Arcpy "MemoryError"; Get Classification Breaks on a TIF Raster; Jenks Breaks; Python
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2018 at 2:40 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 29, 2018 at 5:16 | comment | added | user2856 | How long did the 233, 679 (158207) array take to run? I roughly guesstimated ~5 hours based on how long it took to run on a 10,000 element array. | |
| May 29, 2018 at 4:59 | answer | added | user2856 | timeline score: 1 | |
| May 29, 2018 at 3:45 | comment | added | Michael Stimson | 87% isn't a valuable figure, what is important is the physical load in mebibytes, Esri can only address 4 GiB of memory and it sounds like you're filling that up. Considering you're reading the whole raster into memory and performing a purely python function I would suggest you consider either ArcGIS Pro (64 bit) or GDAL 64 bit.. my preference is for GDAL. Read gis.stackexchange.com/questions/32995/… about using GDAL to read a raster into a numpy array. | |
| May 29, 2018 at 3:35 | comment | added | Austin Gates | @MichaelStimson My task manager shows my memory reaching 87% capacity when I run it on the larger raster, and then I get the MemoryError. | |
| May 29, 2018 at 3:29 | history | edited | Austin Gates | CC BY-SA 4.0 |
corrected a null value problem in the RasterToNumPyArray
|
| May 29, 2018 at 3:28 | comment | added | Austin Gates | @MichaelStimson I apologize, I was wrong. The raster that is generating the memory error is a much larger raster. I was able to generate break values for the smaller subset of the array, which was my original post: [0, 35, 150, 350, 516, 696, 896, 3337, 4132, 428760.0]. Yet I need to run the function on the larger raster, which I fixed in the edit below. | |
| May 29, 2018 at 3:27 | history | edited | PolyGeo♦ |
edited tags
|
|
| May 29, 2018 at 3:17 | history | edited | Austin Gates | CC BY-SA 4.0 |
Typo. Correction at the bottom of question. Need to run on larger raster.
|
| May 29, 2018 at 2:59 | history | edited | ahmadhanb | CC BY-SA 4.0 |
added 24 characters in body
|
| May 29, 2018 at 2:51 | comment | added | Michael Stimson | What does task manager say about your memory usage? 233 x 679 isn't a large raster, are you sure that your raster is only 233 rows and 679 columns? Be aware that ArcGIS Desktop is only a 32bit application and can only address 2**32 bytes of memory for each instance of Arc - program, script and data. | |
| May 29, 2018 at 2:38 | review | First posts | |||
| May 29, 2018 at 5:29 | |||||
| May 29, 2018 at 2:37 | history | asked | Austin Gates | CC BY-SA 4.0 |