Skip to main content
  • EN

I’m a newby to FME.

I’m about to write workspaces to refresh a list of AGOL feature services.  So far I’ve written a simple one that works on a small service.

I’ve got a few questions.

  1. When I search for potential pitfalls in this forum, they are 5+ years ago and relate to AGOL time outs and also issues updating large datasets.  .  I’m on the latest release of Form & will use Flow (Hosted).  Are these issues still relevant these days ?My largest dataset is our Cadastre being about 140K features.  Am I safe to use the Writer ?
  2. I am doing truncate & inserts.  One might argue that I could use ChangeDetector beforehand, however, I reckon the processing required to compare 140K features would be greater than a simple truncate & insert. (am I right?)
  3. If an error is encountered, I would like to quickly restore the destination feature service back to what it was. Any tips on the best approach to doing that ?  My idea is to copy the destination service elsewhere in AGOL before commencing the update.  If update fails, then rename the services so the backup takes on the production feature service name.   Any better ways ?

Hi

I can tell you how I see this, but you can make up your own mind.

  1. AGOL write errors still occur. Its not a FME thing but the Esri environment sometimes returning a problem. But I wouldn’t say it is often
  2. I would go the changedetector all the time, especially if you know the fields that you are going to be checking aren’t going to change over time. You can do some amazing stuff with changedetector, but some of it can require a bit of thinking. But I don’t think you should need it in this particular example. I don’t think your cadastre will have many ocassions when all the feature change, so it will be a very simple update. Make sure to user a geometry allowance, especially if you have different precisions in source/destination. For AGOL, to update, you need to ensure the update feature has the AGOL Id on it (little bit more painful than updates in other formats)
  3. You can always take a copy of the data before you update, and keep it for your records. Check out the transformer ArcGIS_AP_fileexportgdb  if you want to get a file gdb of the data before you overwrite the layer in AGOL.

It will take a while, but once you get into all the these things, you will be amazed by the ability of FME in this space.

Thanks @todd_davis Much as I thought that AGOL writing would still fail at times.

Still looking for a response to my third question.  Hopefully someone posts :)

Reply


Community Stats

30,144
Posts
114,426
Replies
37,787
Members
Terms & ConditionsCookie 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.