Error while running WASCOBS on 3.0

[Amélie Davis]

Hi,

I got the following error while running the WASCOBs tool using ArcGIS 3.0.2.   

Traceback (most recent call last):
  File "C:\ACPF_V4_Pro_05092022\Scripts\WASCOBSP4.py", line 437, in <module>
    Dir_Stats = DirectionStats(flownet)
  File "C:\ACPF_V4_Pro_05092022\Scripts\WASCOBSP4.py", line 111, in DirectionStats
    Dir_Stats = arcpy.DirectionalMean_stats(flownet, "Dir_Stats", "", "LINKNO")
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\stats.py", line 1732, in DirectionalMean
    raise e
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\stats.py", line 1729, in DirectionalMean
    retval = convertArcObjectToPythonObject(gp.DirectionalMean_stats(*gp_fixargs((Input_Feature_Class, Output_Feature_Class, Orientation_Only, Case_Field), True)))
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda>
    return lambda *args: val(*gp_fixargs(args, True))
arcgisscripting.ExecuteError: Traceback (most recent call last):
  File "<string>", line 2362, in execute
  File "c:\program files\arcgis\pro\Resources\ArcToolbox\Scripts\DirectionalMean.py", line 697, in createOutput
    spatRef, changed =self.checkDomainProjection()
  File "c:\program files\arcgis\pro\Resources\ArcToolbox\Scripts\DirectionalMean.py", line 669, in checkDomainProjection
    projectionChange = UTILS.extentDomain3D(self.ssdo.spatialRef,
  File "c:\program files\arcgis\pro\Resources\ArcToolbox\Scripts\SSUtilities.py", line 1714, in extentDomain3D
    setZDomainProjection(min(minValues[2] - extend, zMin),
TypeError: '>' not supported between instances of 'float' and 'NoneType'

Failed to execute (DirectionalMean).

The tool runs in 3.0 on another watershed that I had already processed in ArcGIS Pro2.9.  Can someone confirm if this means there are no identifiable WASCOBs in my current watershed and I can ignore the error or if I need to dig into it (and if so, if anyone has an idea of where to start that would be wonderful.  It seems to be some projection issue but I am using data that are all in a geodatabase so the data are all in the same coordinate system (here UTM Zone 16N which is an  appropriate projection for this watershed). 

Any help with this is greatly appreciated.

Sincerely,

Amélie

Amélie Davis, Ph.D., GISP, ENV-SP Associate Professor Miami University (on personal leave 2022-2023) Department of Geography Institute for the Environment and Sustainability Shideler Hall 213, Oxford, OH 45056 O: 513-529-0809 | davi...@miamiOH.edu https://sites.google.com/site/sustlandcomlab/