AnsweredAssumed Answered

geofence - limitations - count and memory

Question asked by dhoyesriaustralia-com-au-esridist Employee on Dec 4, 2016
Latest reply on Jul 12, 2017 by dhoyesriaustralia-com-au-esridist

Hi team,

this is my first foray into GEX and it's a step at a time.

In our site, we wish to run a simple GeoTag to track less than a dozen vehicles.

We have a set of polygons representing "chunks" of a limited part of the street network. Each event that falls within one of the roadway chunks to be tagged with the name of the chunk.

In my understanding this is a simple case of the use of a GeoFence.

I have the RoadChunks available in a Feature Service and I can load and use a subset of these as Geofence and capture these in a test case.

The problem is - I cant use all my polygons (And there are >36,000) - When loading the Geofence, I get an out of memory message from GEX.

I understand that there is a 4GB memory usage limit. (#Our server actually has 16GB available) and I can see the memory warning message comes up at around the 4GB limit (observed in Task Manager). So it sort of makes sense, but....

My RoadChunk polygons are quite simple (6-8 vertices each) and when in a file geodatabase take up a few 10s of MB.

1. Why do I run out of memory at around 10,000 loaded "chunks"?

2. Could I increase the memory limit to (say) 12 GB ?

3. any other tricks?

4. Am I being unrealistic wanting to use such a large number of Geofence polygons?

5. Can anyone suggest another strategy?

Outcomes