Zonal statistic as table always error with 'The input path contains spaces'

[ShuwenLiu]

Zonal statistic as table always error with 'The input path contains spaces'. However, the 'Zonal statistic' using the exact setting could successful be run.

This the detail of 'Zonal Statistics as Table'

Zonal Statistics as Table
=====================
Tool Path

Input Raster or Feature Zone Data E:\research EMIT\EMIT ArcGIS\EMIT ArcGIS.gdb\EMIT_tiles
Zone Field OBJECTID
Input Value Raster ai_v3_yr.tif
Output Table E:\research EMIT\EMIT ArcGIS\EMIT ArcGIS.gdb\ZonalSt_EMIT_ti1
Ignore NoData in Calculations DATA
Statistics Type MEAN
Process as Multidimensional CURRENT_SLICE
Percentile Values 90
Percentile Interpolation Type AUTO_DETECT
Calculate Circular Statistics ARITHMETIC
Circular Wrap Value 360
Output Join Layer
=====================
Messages

Start Time: Wednesday, December 11, 2024 9:52:31 PM
ERROR 000622: Failed to execute (ZonalStatisticsAsTable). Parameters are not valid.
ERROR 010819: The input path contains spaces.
Failed to execute (ZonalStatisticsAsTable).
Failed at Wednesday, December 11, 2024 9:52:31 PM (Elapsed Time: 0.20 seconds)

This the detail of 'Zonal Statistics as'

Zonal Statistics
=====================
Tool Path

Input Raster or Feature Zone Data E:\research EMIT\EMIT ArcGIS\EMIT ArcGIS.gdb\EMIT_tiles
Zone Field OBJECTID
Input Value Raster ai_v3_yr.tif
Output Raster E:\research EMIT\EMIT ArcGIS\EMIT ArcGIS.gdb\ZonalSt_EMIT1
Statistics Type MEAN
Ignore NoData in Calculations DATA
Process as Multidimensional CURRENT_SLICE
Percentile Value 90
Percentile Interpolation Type AUTO_DETECT
Calculate Circular Statistics ARITHMETIC
Circular Wrap Value 360
=====================
Messages

Start Time: Wednesday, December 11, 2024 9:50:48 PM
Value raster being used as snap raster; this is new default behavior.
WARNING 010566: Some zones may not have been rasterized.
Succeeded at Wednesday, December 11, 2024 9:52:31 PM (Elapsed Time: 1 minutes 42 seconds)

[JoabelBarbieri]

It would be funny if not upsetting !

[ISGGISAdmin]

Having the exact same error^ this definitely needs to be registered as a Bug.

[JeffreyToony_MPD]

A couple of my crime analysts are having the same issue but the rest of them are not, when accessing the exact same path. Why does it work for some but not others on the same data path?

[JosephRigley]

It seems having a dash in the file path can trigger the same or a similar error. Had Viewshed throw this error until the dash was changed to underscore.

[JoabelBarbieri]

dash or no dash, it doesn't work here

The most infuriating thing is the Esri error./solution to this problem

010819: The input path contains spaces.

Description
The Esri Grid format raster does not support path names that include spaces.

Solution
Remove the spaces in the folder names.

Are you kidding me? There's no space to being with.....

And IT WORKS in ARCMAP - it's clearly a PRO issue!

[JosephRigley]

Indeed, it's not a good look for Pro

[Guilherme_Oliveira]

This is really annoying and should be marked as bug for sure !

I've got the same error working in ArcgisPro interface. But it seems that it is not related to the path with spaces. Running the same process with the same inputs in a arcpy standalone script, it worked this way:

    arcpy.sa.ZonalStatisticsAsTable(

        in_zone_data=properties,  # feature class in a gdb

        zone_field=id_field, # string

        in_value_raster=fiscal_modules, # raster in a gdb

        out_table=os.path.join(output_gdb, 'zonal_table_mod_fiscal'),

        ignore_nodata="DATA",

        statistics_type="MAJORITY",

        process_as_multidimensional="CURRENT_SLICE",

        circular_calculation="ARITHMETIC",

        circular_wrap_value=360,

    )

Note: my inputs are placed in a path with spaces.

However, if I left the 'percentile_interpolation_type' and 'percentile_values' arguments, the function fails.
Another issue is that the out_join_layer is not being created as an output.
We are paying a lot for this, ESRI. This shouldn't happen in such a basic tool in a professional software.

[DFarming]

Good to see this still isn't fixed as of 3.5..

Tools I've seen it in:
Zonal Statistics
Expand
Shrink

All on input fields that have nothing to do with a filepath

[NishaniMoragoda]

Hi @ShuwenLiu, thank you for sharing this on the community.

I am Nishani Moragoda from Esri. We tried to reproduce this issue based on your test case, using data located in (i) a local drive, (ii) a UNC path, and (iii) a mapped drive (with 8dot3name enabled and disabled in the local drive and mapped drive). But we could not reproduce this error, and our tests worked as expected in ArcGIS Pro 3.5.

If you have steps to reproduce this issue, please contact Esri Technical Support to report this, so we can investigate it using those information. Please make sure to include details on the nature of the data, full data and output paths, drive type, available storage on the drive, and any other information that might help us reproduce and fix this issue.

Thank you for your support to improve the software!

Best regards,

Nishani