Include Feature Classes as source and output options

Levon_H — Thu, 02 May 2024 19:07:39 GMT

We have many scripts running now that update AGOL layers from File Geodatabase Feature Classes written in python (arcpy, ArcGIS API for Python). These are stand-alone scripts scheduled by Windows Task Manager as well as Notebooks for implementation and scheduling. A drag and drop utility like this could eliminate all of that.

Re: Include Feature Classes as source and output options

MaxPayson — Thu, 02 May 2024 19:51:39 GMT

Hi @Levon_H , thank you for the idea! Where are your file geodatabases stored?

We are actively working on support for reading feature classes from file geodatabases. Like other file inputs, the files will need to be stored in an accessible and supported location (AmazonS3, Azure Storage, or uploaded locally to Online), so I'm curious if this will fit your use case? Also, if there are more details you can share about your current workflow (is there intermediary processing, is it updating multiple layers in a single service, etc), that would be very helpful as well!

idea Include Feature Classes as source and output options in Data Pipelines Ideas

Include Feature Classes as source and output options

Re: Include Feature Classes as source and output options