nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR 100014 Summarize Within failed

MarkBinder

I have a Python script that goes through several steps including using arcpy.analysis.SummarizeWithin(). When I run the script in the Python window of ArcGIS Pro it works just fine. When I run the script in an IDE like Spyder or Visual Studio Code sometimes I get the ERROR 100014 code; and sometimes it works.

I am completely baffled why sometimes it works sometimes and not others. All of the datasets are the same each time.

Any suggestions?

Najděte více příspěvků označených jako

Accepted answers

All comments

DanPatterson

perhaps Error: 100014: Summarize within failed (esri.com)

MarkBinder

That doesn’t work.

DanPatterson

That is the only reference on the Tech Support to that error message, so perhaps you need to contact Tech Support. They may have other references that aren't publically reported since they are still under investigation.

PatSmyth

Did you ever find a workaround for this? Experiencing the same thing: Summarize within run fine in Pro python window; but fails when run in jupyter notebook (clone of pro env) or vscode (same clone of env). Same non-descriptive ERROR 100014 code that has been mentioned in countless other support threads. This is asinine that this tool has so many caveats that have not been addressed in releases of Pro.

MarkBinder

Unfortunately, I have not. The really weird part is that some days it works and some days it doesn't. I've spent hours trying to get it to work one day and the next day it runs with no problem.

I wish I had better news.

KatMcDonald-Miranda

I'm also getting this error, but only when I add a Summary Field to the tool. When I don't add the field, the tool runs fine.

tschulzke

I seem to have stumbled upon something that I haven't seen addressed in any of my searches online but may help here. Because the "Summary Field" is basically the reason for using this tool, I reluctantly tried @KatMcDonald-Miranda's solution above, but it threw me a new error (100019) for the "Add shape summary attributes" checkbox. Although this function is supposedly optional (https://pro.arcgis.com/en/pro-app/latest/tool-reference/analysis/summarize-within.htm), when I checked the box for it and re-added the summary field I had removed, the tool finally ran successfully. Again, the irony is that the documentation says both "Summary Field" and "Add shape summary attributes" are optional parameters, but Error 100019 says otherwise and requires that at least one of these "optional" options be utilized (see screenshot below). Going back to the original problem, it seems that Error 100014 has nothing to do with the real reason the tool fails (as we can see in this thread where the path and/or file name length workaround/solution did nothing to fix the problem), rather the "Add shape summary statistics" box must be checked for the tool to run successfully.

Not sure if this is a version issue, but I am running Pro 3.1.1 and never encountered this problem when using the "Summarize Within" tool in earlier versions of Pro.

OrrGvili

cant make it work with script it run fine in pro 3.1.1

but failed when run with pyton script.
after successful run in pro i copyd the python command and try to run it with the script still get the ERROR 100014

SageGrouse

I was getting this error, but the solution was to define the projections on my input Feature Classes.

RyanColeman

I'm in the same situation. It works in ArcGIS Pro Geoprocessing but analysis.SummarizeWithin in arcpy no longer works at all. Tried defining the projection, with or without the summary table, in memory and on disk, result is always ERROR 100014: Summarize Within failed. I'm on 3.1.3 worked fine prior to updating

josethomazini_imagem

Hey, Mark.

I was facing the same issue.

Now I think I´ve found the solution, so follows my suggestion.

This is the example they´ve provided in the documentation:

 arcpy.analysis.SummarizeWithin('neighborhoods', 'crimes', 'neighborhood_crimes')

The 3 parameteres (in_polygons, in_sum_features and out_feature_class), must be all feature names (not paths).

The function will look for the parent folder path in the workspace env variable, so the documentation says you must declare it first, as:

 arcpy.env.workspace = r'path\to\your\workspace'

What the documentation never tells you is that the out_feature_class won´t be saved in the workspace. The function generates the output in the project´s gdb, NOT in your workspace.

Look again the output that ArcPRO generated. It is not in the same workspace you are using (you may not realize that if you are not using your own gdb).

So, if you set the environment variable to the scratch-workspace the function will be able to join it to the out_featur_class name.

Since I want the output to be generated along with the other input features (in the same workspace), I just set the scratch-workspace path the same as the workspace path:

arcpy.env.scratchWorkspace = arcpy.env.workspace

ArcPRO aways works because it must declare those env variables internally. But if you export the python command from the history tab it won´t provide you the env variables. That´s just not fair with us, poor mortals. 😁

Hope it works for you too.

ParkerJohnsonGas

Quite a late response but ( I see that there is no Solution selected so...) I was running into this issue as well, not with any scripting but just within the Pro client.

For me, running 'Make Feature Layer' on my feature classes I was originally using as input and utilizing those Layers in the tool was the only thing that could get it to work. In the tool Documentation the inputs are defined as Feature Layers, but I was using Feature Classes.

Maybe make sure that any scripts are creating Feature Layers that get fed into the Summarize Within tool parameters. Hopefully you aren't experiencing this anymore, but if so I hope this may help.

AS_Oxford

This is the only suggestion in this thread that worked for me. I would never have thought of that solution - thank you! I just added the line to change the scratch workspace to my gdb's workspace and the tool ran successfully. It's a bit annoying because it creates a scratch.gdb in that folder, which I did not want, so I set the code to delete it and reset the scratch workspace after running the tool. I hope ESRI can fix this and/or add this info to the documentation because this is a really bizarre requirement.

AS_Oxford

Thanks for the suggestion but this did not work for me. The only thing that worked was to set the scratch workspace to the actual workspace, as suggested above. After that I could use either layers or feature classes successfully in the code. Maybe your layers were created in the scratch workspace, so that's why this worked for you?

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.