higgicd/accessibility_toolbox

Accessibility Toolbox for R and ArcGIS

accessibility_toolbox's Issues

getting null for all origin-destination combinations

I used your tool to calculate accessibility but continuously getting null for SUM_Ai in arcgis_pro.
could anyone tell me why and how to rectify it.

does it have to do anything with the "travel mode...." I used "car". and cutoff value as 60 minutes.

Thread time-outs for GTFS analysis with large multiprocessing pools in GUI

In my testing experience, the tool is less stable in large multiprocessing environments (e.g. our 36 core server) when using the GUI tool in ArcGIS Pro - it seems some threads time-out while waiting to load the network and GTFS timetables into memory. It could be due to the limited read speeds of the hdd on the server. However, the command line tool works fine for such analyses, it just takes a bit of time to spin up all the processes. On my 8-core desktop (with an ssd) I have not encountered any issues.

Suggestions for handling r5r

Hi Chris,

Thanks for this is a great toolbox. I was browsing the code related to r5r and just wanted to flag a couple things that would

1. Set Java memory

Ideally, one should set the Java memory before loading any libraries. This is to make sure Java will get the memory you set. In case you load a library that call .jInit(), then the call for options(java.parameters = Xmx...) could lose effect.

options(java.parameters = "-Xmx6G") # assign memory for r5r to work with
library(r5r)
library(...)

2. Accessibility calculation

I understand one might want to calculate travel time matrices and store the data for future use. Nonetheless, if the purpose is simply to calculate accessbility, then it would be best (simpler and more efficient) to use the r5r::accessibility() function.

unbound local error

I got an unbound local error while using the multiprocessing tool. Then I used tool without multi processing. I got the same error. Please help me with how to rectify.

"Start Time: Tuesday, November 30, 2021 11:29:56 AM
There are 16 cpu cores on this machine, using 15
Batching 215 chunks of origins
origins_i is already points...
Calculating origins_i Network Locations...
Finished pre-processing origins_i
destinations_j is already points...
Calculating destinations_j Network Locations...
Finished pre-processing destinations_j
Sending batch to multiprocessing pool...
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\multiprocessing\pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\multiprocessing\pool.py", line 44, in mapstar
return list(map(*args))
File "C:\Users\malle\Documents\Accessibility_Toolbox-master\Accessibility_Toolbox-master\access_calc_main.py", line 319, in access_multi
arcpy.management.AddField(od_lines, "Ai_"+f_name, "DOUBLE")
UnboundLocalError: local variable 'od_lines' referenced before assignment
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "", line 306, in execute
File "C:\Users\malle\Documents\Accessibility_Toolbox-master\Accessibility_Toolbox-master\access_calc_main.py", line 404, in main
result = pool.map(access_multi, jobs)
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\multiprocessing\pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\multiprocessing\pool.py", line 657, in get
raise self._value
UnboundLocalError: local variable 'od_lines' referenced before assignment
Failed to execute (AccessCalcProMP).
Failed at Tuesday, November 30, 2021 11:39:38 AM (Elapsed Time: 9 minutes 41 seconds)"

GUI tool fails in ArcGIS Pro 2.6

I've encountered a multiprocessing issue after updating to Pro 2.6 that causes the GUI version of the tool to fail. After talking with ESRI, it seems the new version of Pro is not working well with Python multiprocessing and an official bug has been identified. To get around this, you can use the command prompt and run the .py directly or revert to Pro 2.5.

Results

I've

origins = 4012245 & destination = 22765(hospitals)

Your tool is working and, the result(output) has only 9741 rows with all the frequency data and chosen accessibility values. Could you please make a comment on this like what would have been the reason?

Because Last time I did this operation with origins = 2500000, The output had accessibility results for all the origins(there were 2500000 rows in the output table). I couldn't understand why this time it changed.

Could you please tell me how to visualize accessibility values in ArcGIS pro using symbology?

Thank you in advance.