Skip to main content
Question

Issue with Updating/Truncating AGOL Feature Service via FME Flow – "413 Request Entity Too Large" Error

  • February 25, 2025
  • 1 reply
  • 47 views
aawad.93
Contributor

Hi everyone,

I am working with a large dataset (over 500,000 records) stored in PostGIS, which I am reading into FME and writing to ArcGIS Online (AGOL). My goal is to automate this process by publishing the FME Workbench to FME Flow, so the AGOL feature service updates every few hours.

When I overwrite the data, the Workbench runs without any issues. However, I want to truncate the existing data instead of overwriting it. When I attempt to do this, I encounter the following error:

413 Client Error: Request Entity Too Large

Occasionally, I receive other request size-related errors as well. I tried adjusting the Features Per Request parameter to 500, but the issue persists.

I’d like to ask if anyone has experienced this issue before and what possible solutions or workarounds exist to efficiently truncate and update the AGOL feature service without running into request size limitations.

Any insights or recommendations would be greatly appreciated!

Thanks in advance.

1 reply

nielsgerrits
VIP
Forum|alt.badge.img+52

I’m not very experienced in migrating data to arcgis online, but I believe the AGOL writer is not the correct approach for larger amounts of data. As you experienced, trying to do these larger requests will lead to time-outs and fail eventually.

Someone at the FME User Conference in Bonn showed a similar case. If I remember well, they uploaded a file geodatabase to AGOL and published a service based on this uploaded gdb. For the update cycle, they uploaded another file geodatabase, with the same featureclasses and schema’s, and then switched the source of the service from gdb a to gdb b.

If you look in AGOL and open a featureservice, you will see an Update button. You can use this button to upload and replace the data under the service. Now, if you do these actions while DevTools (f12) is open, and you look in tab Network, you will see which requests are done when the buttons are clicked. Then using HTTPCallers you’ll be able to reproduce these steps and do it automagically. I know this can work as a teammember produced something similar in the past. But it will take some work.

The ArcGISOnlineConnector has the action Update, which I expected to do the same, but this seems not to be the case. The source file geodatabase in arcgis online is updated, but the service created from this file geodatabase show no changes after updating the file geodatabase.

churchfraser
1 person upvoted this
  • churchfraser
    churchfraser

Reply


Most helpful members this week

Community Stats

30,846
Posts
116,936
Replies
38,670
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.