Select to view content in your preferred language

Error with calculating time lapse polygons

1181
2
Jump to solution
10-04-2021 04:47 AM
corrag
by
New Contributor

Hi there!

I'm trying to run the Prepare Time Lapse Polygons tool to create a bunch of service areas from my public transit-enabled network data set but I receive the following error:

Failed to get Service Area result from parallel processing.
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\concurrent\futures\process.py", line 175, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "C:\Users\corrag\OneDrive - Tyrens Group\Dokument\GIS-grundata\_ArcToolboxes\TransitNetworkAnalysisTools\TransitNetworkAnalysisTools_0.5.1\parallel_sa.py", line 401, in solve_service_area
sa.solve(time_of_day)
File "C:\...\...\_ArcToolboxes\TransitNetworkAnalysisTools\TransitNetworkAnalysisTools_0.5.1\parallel_sa.py", line 285, in solve
self.sa_solver.addFields(arcpy.nax.ServiceAreaInputDataType.Facilities, field_defs)
AttributeError: 'ServiceArea' object has no attribute 'addFields'
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\...\...\_ArcToolboxes\TransitNetworkAnalysisTools\TransitNetworkAnalysisTools_0.5.1\parallel_sa.py", line 529, in solve_sa_in_parallel
result = future.result()
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\concurrent\futures\_base.py", line 425, in result
return self.__get_result()
File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\concurrent\futures\_base.py", line 384, in __get_result
raise self._exception
AttributeError: 'ServiceArea' object has no attribute 'addFields'
Service Area script failed.
Failed to execute (PrepareTimeLapsePolygons).

Based on the messages this happens right after the tool calculates the first set of service areas:

Solving Service Areas in parallel...
Finished Service Area calculation 1 of 24.

I am able to use the Calculate Accessibility Matrix and Calculate Travel Time Statistics tools without error, and the built-in Service Area tool in ArcGIS Pro also works for me. I am running ArcGIS Pro 2.6.3.

Here are the input parameters that I've used:

Facilities t_central_hpl
Output Time Lapse Polygons C:\...\...\Default.gdb\t_central_hpl_PrepareTimeLapsePolygons
Network Data Source ND_316518_Ostgotatrafiken
Travel Mode PublicTransport
Cutoff Times 15;30;45
Cutoff Time Units Minutes
Start Day (Weekday or YYYYMMDD date) 20211115
Start Time (HH:MM) (24 hour time) 07:00
End Day (Weekday or YYYYMMDD date) 20211115
End Time (HH:MM) (24 hour time) 08:55
Time Increment (minutes) 5
Travel Direction Toward Facilities
Geometry At Cutoff Disks
Geometry At Overlap Overlap
Maximum Number of Parallel Processes 4
Barriers
Precalculate Network Locations true

@MelindaMorang  do you have any idea what I can do to fix this, or any other information that would be useful for you to diagnose the problem?

0 Kudos
1 Solution

Accepted Solutions
MelindaMorang
Esri Regular Contributor

The addFields() method was added to the arcpy.nax solver objects in ArcGIS Pro 2.7, so that's why you're seeing an error in 2.6.3.

The best solution is for you to update your software to the latest (Pro 2.8.2), or at least 2.7, if you're able.

The alternative solution is to fall back to the older, slower ArcMap version of these tools: https://arcg.is/1u8WKS 

View solution in original post

2 Replies
MelindaMorang
Esri Regular Contributor

The addFields() method was added to the arcpy.nax solver objects in ArcGIS Pro 2.7, so that's why you're seeing an error in 2.6.3.

The best solution is for you to update your software to the latest (Pro 2.8.2), or at least 2.7, if you're able.

The alternative solution is to fall back to the older, slower ArcMap version of these tools: https://arcg.is/1u8WKS 

corrag
by
New Contributor

Thanks @MelindaMorang ! Thanks for confirming that this has to do with the version of ArcGIS Pro I'm running and not some other problem with my data set. I'll see if it's possible for me to upgrade to a newer version of ArcGIS Pro.

0 Kudos