topic File size limit in manager.overwrite in ArcGIS API for Python Questions

File size limit in manager.overwrite

OGLEngineering — Mon, 16 Sep 2024 17:12:26 GMT

Hello. I was following this tutorial (https://learn.arcgis.com/en/projects/schedule-automated-near-real-time-data-updates/) and when it came time to update the data in my item, it failed because it was over 25mb. I looked into the code and it was overwite(...) in arcgis/managers.py that was forcing a limit of 25mb

if data_file and ( not isinstance(data_file, str) or not os.path.exists(data_file) or not os.path.isfile(data_file) or os.stat(data_file).st_size > int(2.5e7) ): raise ValueError( "The data file provided does not exist or could not be accessed." )

Is there any reason for this restriction? I removed the file size check and uploaded a 200mb+ geojson file and everything worked perfectly fine. Any insight?

Re: File size limit in manager.overwrite

BijanTaheri — Tue, 08 Oct 2024 11:40:51 GMT

I've also run into this problem before. Good find, i will have to remember this next time i need to upload something of this size.

Re: File size limit in manager.overwrite

Leo_Lerner — Tue, 08 Oct 2024 22:30:08 GMT

Thanks for posting this. The file size check was removed in the 24th September release of the API for Python 2.4.0.

This version will be compatible with the next release of ArcGIS Pro (3.4).

Please see the documentation on this change here (scroll down to overwrite() ) https://developers.arcgis.com/python/latest/guide/release-notes-240/

Re: File size limit in manager.overwrite

TheGreenOrange — Tue, 09 Dec 2025 20:44:11 GMT

This was a problem for us as well, took a long time and a call to ESRI before coming across this post...
25Mb? really? why......?
the error message

raise ValueError(
The data file provided does not exist or could not be accessed."

It doesn't even mention the file size limitation, so that took me down a lot of wrong paths.

I commented out that line and it's all working. And no, we can't go to a newer version of PRO because I tried that and it broke so many of our modelbuilder tools. We are staying on 3.3.6 until we upgrade enterprise.