topic Pathname error message in ArcGIS Pro Questions

Pathname error message

SaraJL — Fri, 11 Apr 2025 21:25:11 GMT

Hello everyone!

I've been running into an issue where I'm receiving an error about spaces being in the raster pathname, but there aren't any spaces:

Any thoughts? I've tried move the raster to other folders, and it still shows the same error.

I'm on the latest version of ArcGIS Pro, Windows 11

Thank you!

Re: Pathname error message

DavidPike — Fri, 11 Apr 2025 21:33:36 GMT

The list by source tab in the table of contents does show the true path of the parent workspace (GDB/folder) but will still show the layer name below - rather than the filename as it appears in Catalog. I'd double-check the Catalog window and see how it appears within the GDB.

If it looks ok, then I'd try to shorten the filename to test, or export to a TIF and retry. Even export a small subset as .tif to test with.

Re: Pathname error message

DanPatterson — Fri, 11 Apr 2025 23:23:11 GMT

select the folder icon beside the "input raster" line and navigate to the raster and select it.

apparently this is an ongoing problem and this was one solution for some, but not for many.

on a side note not one is reporting these issues to tech support and there are no associated bugs on the public facing the bug list.

Solved: Zonal statistic as table always error with 'The in... - Page 2 - Esri Community

for a related and casual read/vent-fest

Re: Pathname error message

Robert_LeClair — Mon, 14 Apr 2025 22:44:49 GMT

Instead of storing the output raster dataset as fGDB raster, try creating the raster outside of the fGDB and save it as *.tif file. Does the error message persist?

Related, I would also try the fGDB storage route on your C: drive in a temporary directory like C:/temp/test.gdb and call the output digital_elevation_model_30 and see if the tool completes with or without the error message. If without then I wonder if the bigger problem is the name of the S: drive having space in it...maybe.

Re: Pathname error message

SaraJL — Tue, 15 Apr 2025 16:57:12 GMT

I was able to resolve it!

Originally, I was trying to save the output raster to the fGBD in the S: drive, but that wouldn't work, so then I was trying to just save it (the "hill1" output) to a regular folder in the S: drive so see if that would fix it. Sometimes that will work for me, but didn't in this case.

I was able to get it to eventually work by -->

Starting a new ArcGIS Pro project > exporting the raster out of the fGDB to a regular folder in the S: > renamed it to "mn_dem" > then I was able to generate a hillshade from the new version without a problem!

I wonder if the issue is the fGDB in the S: drive (which is a Windows Network Drive). We have really limited options at our organization for storage, so it's only Windows Network Drives or Google Drive. If it's vector data, I can actually get all of the tools to work just fine with fGDB, so not sure exactly what was causing the problem.

It's also possible that the name of the fGBD was too long and that could be the problem (maybe?)

*I usually try to avoid testing anything on the local computer if I can, because our public college computers are on an automatic data wipe schedule. So we typically don't recommend people to save to the C Drive if they can help it. It's a 50/50 chance on if they back it up or forget, and then lose their data.*

Anywho, that was how I was able to get it to work! If it works now, I'll take it - thank you for the recommendations!