ArcGIS Pro maximum path length limitation for File-Geodatabase

[HagenProbsthain2]

Please allow long paths if this is activated under Windows operating systems. The current limit of 260 characters (248 for the directory path) is often much too short. When working with filegeodatabases, strange behavior occurs when the limit is reached

[BillFox]

I searched and found these notes and some options to try

• https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-...
• https://support.esri.com/en-us/bug/in-arcgis-pro-with-the-arcgis-reality-extension-the-3d-bug-000163...
• https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry

[HagenProbsthain2]

Yes, I had already found that and checked the LongPathsEnabled setting in Windows (it was already set to 1). The third link you posted says: "Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from many common Win32 file and directory functions. However, your app must opt-in to the new behavior." I suspect that ArcGIS Pro has not implemented this yet, otherwise it would not cause such strange behavior with a file geodatabase when the (short) maximum path length is reached.

An example of this is that feature classes can be imported into the fGDB but then can no longer be renamed. In this case, the error message states that the feature class is locked by another application. Or you try to create an fGDB in a path that already consists of the maximum of 248 characters. The fGDB is created in the catalog, but after renaming it suddenly disappears without a message.

A workaround is to map drive letters, but this can be a problem if projects are passed on to other employees or customers.

[SSWoodward]

Thanks for this Idea @HagenProbsthain2,

Can you share what version of ArcGIS Pro you are using?