Make ArcPy FeatureSet Interoperable with the ArcGIS API for Python FeatureSet

[feralcatcolonist_old]

There are currently two implementations of the FeatureSet within the Esri-verse that are incompatible. Making these two objects interoperable would allow greater ease of use in translating enterprise geodatabase feature classes and web-based feature layers. 

For example, the gis.publish() accepts only one non-file input-- the feature collection. If the FeatureSet was compatible with the ArcPy implementation, a feature class could be turned into a FeatureSet and then a FeatureCollection for publishing. The current alternative is to either export the feature class into a hard file format, or create a map to host a service definition, and then publish.

https://developers.arcgis.com/python/api-reference/arcgis.gis.toc.html#arcgis.gis.Item.publish

This post makes the point very succinctly:

https://community.esri.com/t5/arcgis-api-for-python-questions/arcgis-featureset-arcpy-featureset/m-p...

So can we make the FeatureSet an actual FeatureSet?

[feralcatcolonist_old]

I think we can all agree that this is confusing.

Within the two Python libraries maintained by Esri, there should be agreement about naming objects, the capabilities of those objects, and of course, interoperability within the same language. 

[HannesZiegler]

You've got our attention!  We think this is a good suggestion and have entered it in our backlog. We're planning to explore the idea a bit further in the near term.  This does not guarantee that the idea will be developed so we encourage the community to continue voting and sharing feedback which will help teams gauge user demand. 

[Tyce_inCitu]

@feralcatcolonist_old, don't know if you saw this, but it looks like this was addressed in 2.0.1 https://developers.arcgis.com/python/guide/release-notes-201/

[feralcatcolonist_old]

@Tyce_inCitu I totally did! Very excited to see that in the release notes!