Skip to main content
Solved

Writing features to ArcGIS Online

  • December 14, 2022
  • 7 replies
  • 559 views
anne_kathr1ne
Contributor
Forum|alt.badge.img

Hi,

 

Im trying to write approx 17.000 rows into an existing feature service in AGOL. I get the error "entity too large for url", so I assume its too many rows. I have tested with a few rows, and that works fine. 

 

I have tried now to use the ModuloCounter and a TestFilter to split into smaller groups, and then add multiple AGOL-writers, so they only write one group at the time. Im not sure this is the best way to go, as I would the need a lot of writers.

imageAnother is to use the FeatureWriter to do the same, but I would still need to do the setup for all the groups, so not sure if thats ideal.

 

image 

Does anyone have any better suggestion?

 

Best,

Anne Kathrine

Best answer by tomfriedl

sometimes less is more, the help writes:

Features Per Request

This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.

Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.

This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.

If this parameter is not provided, it defaults to 1000.

View original
Did this help you find an answer to your question?

7 replies

tomfriedl
Contributor
Forum|alt.badge.img+13
  • tomfriedlContributor
  • Contributor
  • December 14, 2022

Have you set the writer-parameter "Features Per Request"?

https://community.safe.com/general-10/fme-form-starter-20721
anne_kathr1ne
Contributor
Forum|alt.badge.img
  • anne_kathr1neContributor
  • Author
  • Contributor
  • December 15, 2022
tomfriedl wrote:

Have you set the writer-parameter "Features Per Request"?

Hi @tomfriedl​ , yes, I added as many 0's as I could, just to make sure :)

tomfriedl
Contributor
Forum|alt.badge.img+13
  • tomfriedlContributor
  • Contributor
  • Best Answer
  • December 15, 2022

sometimes less is more, the help writes:

Features Per Request

This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.

Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.

This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.

If this parameter is not provided, it defaults to 1000.

https://community.safe.com/general-10/fme-form-starter-20721
anne_kathr1ne
Contributor
Forum|alt.badge.img
  • anne_kathr1neContributor
  • Author
  • Contributor
  • December 15, 2022
tomfriedl wrote:

sometimes less is more, the help writes:

Features Per Request

This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.

Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.

This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.

If this parameter is not provided, it defaults to 1000.

Hi @tomfriedl​ Im not sure it will help adjusting, since I anyway gets an error when trying to write less features than what is specified. So I think I need to find a more neat way to write data in smaller groups.

anne_kathr1ne
Contributor
Forum|alt.badge.img
  • anne_kathr1neContributor
  • Author
  • Contributor
  • December 21, 2022
tomfriedl wrote:

sometimes less is more, the help writes:

Features Per Request

This parameter specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, Upsert, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.

Note: This parameter is only applicable when writing to an existing Feature Service. If the Feature Service was created in the same translation, then this parameter is ignored.

This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.

If this parameter is not provided, it defaults to 1000.

Hi @tomfriedl​ ,

You were right. It worked fine adjusting the features pr request to 100. I think I just needed a few days to sink in what you actually suggested! ;)

matthewb
Contributor
Forum|alt.badge.img+7
  • matthewbContributor
  • Contributor
  • June 28, 2024

I’m having the same error, even when I dial my process down to 10 features per request.  Are there other processes that could be modified to improve this performance?

jaywood
Participant
Forum|alt.badge.img+1
  • jaywoodParticipant
  • Participant
  • November 17, 2024

I was facing similar issue. Writer Mode to Asynchronous with Report Yes and Time Out 300 fixed this problem

Reply


Helpful Members This Week

Community Stats

30,990
Posts
117,465
Replies
38,773
Members

Latest FME

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.