topic Re: Zonal statistic as table always error with 'The input path contains spaces' in Geoprocessing Questions

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

ShuwenLiu — Thu, 12 Dec 2024 04:11:10 GMT

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)

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

DanPatterson — Thu, 12 Dec 2024 04:52:56 GMT

E:\research EMIT\EMIT ArcGIS\EMIT ArcGIS.gdb\

try copying the gdb to a simpler folder name without spaces and report if an error occurs

You could also try specifying a folder as the destination and a *.dbf as the output type, since the output can either be a gdb table or a *.dbf file in a folder

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

Jordenjames — Thu, 12 Dec 2024 10:28:26 GMT

The "Zonal Statistics as Table" tool in ArcGIS can sometimes throw an error if the file path contains spaces. To resolve this, try the following:

Move the input files: Place your input data (both raster and shapefile) in a directory with no spaces in the file path.
Rename files or folders: If the folder or file names contain spaces, rename them to remove spaces (e.g., "My Folder" to "MyFolder").
Use short paths: Use short file paths (e.g., C:\Data\ instead of C:\My Data).

This should prevent the error from occurring.

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

DFarming — Tue, 27 May 2025 02:57:32 GMT

This is not the solution. It will fix the message sometimes, depending on what field is causing the problem. But it also happens on fields that do not take directories, instead integers.

It likely has nothing to do with the filepath, I've been running various Arc projects with a space in the filepath for the past 4-5 years.

Try and manually browse to the file to add it as an input. In random situations (like the one that got me to this thread) I have this error pop up if I'm dragging a layer from the project contents to an input field (or selecting in dropdown), if I instead use the browse button and select the layer in a .gdb it will work fine.

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

JoabelBarbieri — Sat, 22 Mar 2025 20:55:43 GMT

It's not fixed It's so frustrating.

ERROR 010819: The input path contains spaces.

The path is this: C:\Users\user1\Desktop\Stands.shp

Where is the *** space Esri? Where?

Manually browsing doesn't help either. We pay a ton of money for this software and this is what we get

BTW, it works perfectly in ArcMAP, but in the one that is supposed to be the future of GIS, nope! Shame Esri, shame!!

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

DFarming — Mon, 10 Feb 2025 00:57:15 GMT

Well, apparently I have a space in my Percentile Values filepath, so I guess I can't use this tool now..

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

ISGGISAdmin — Wed, 05 Mar 2025 19:46:30 GMT

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

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

JoabelBarbieri — Sat, 22 Mar 2025 20:50:44 GMT

Who marked this as a solution? It's not, it's misleading and ESRI thinks it's fixed!! Please unmark it as a solution !!!!!!~!

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

JoabelBarbieri — Sat, 22 Mar 2025 20:56:27 GMT

It would be funny if not upsetting !

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

JeffreyToony_MPD — Mon, 31 Mar 2025 13:01:50 GMT

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?

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

JosephRigley — Wed, 02 Apr 2025 20:47:45 GMT

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.

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

JoabelBarbieri — Wed, 23 Apr 2025 15:21:28 GMT

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!

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

ArmandoFreites16 — Tue, 08 Apr 2025 04:41:30 GMT

OK you need select the elements from the folder icon in the window of the geoprocess and the problem solve. I do this

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

JoabelBarbieri — Wed, 23 Apr 2025 15:14:45 GMT

Wrong. It's not solved. I do this, select using the folder icon and the error persist. This is not the solution to this problem

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

JosephRigley — Thu, 24 Apr 2025 13:21:18 GMT

Indeed, it's not a good look for Pro

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

Guilherme_Oliveira — Fri, 25 Apr 2025 17:11:08 GMT

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.

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

DFarming — Tue, 27 May 2025 02:53:01 GMT

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

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

NishaniMoragoda — Fri, 30 May 2025 01:04:31 GMT

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

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

OlympiaTaken — Wed, 11 Jun 2025 00:42:38 GMT

Hey buddy,

Totally understand your frustration, I encountered the same issue and the ESRI troubleshooting is ridiculous.
The workaround I found was to create a new APRX and import only the layers needed for the processing, it solved the spaces problem.

Hope it helps.

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

EmileeFreeman — Thu, 07 Aug 2025 21:27:15 GMT

I just ran across this issue today in 3.5.2. Was pulling my hair out trying to find a solution because I seemingly had no spaces in my "input path". Shoutout to @OlympiaTaken for their comment - this made me test out a different pro project and led me down a testing rabbit hole.

What I found was that if the Pro Project's file path has any spaces in it, the tool will fail with Error 010819 - even if the input layers themselves are stored in a location with no spaces. If the Pro Project itself is saved to a new location with no spaces, the tool then has no issues running. Magic!

We're gonna try submitting this as a case to ESRI. Let me know if this works for you.