Spatially Enabled Dataframe to Feature Service - how to avoid shapefile conversion?

[I_AM_ERROR]

Hi All,

Fairly new to publishing spatially enabled dataframes, looking for advice on the following

• python env either does not have arcpy, or has arcpy but does not have a license (not checked out or connected to license server
• create a spatially enabled dataframe from various data inputs
• publish to AGOL/Portal using either df.spatial.to_featurelayer() or gis.content.import_data()

Both of the above methods seem to export the dataframe out to shapefile first before publishing to feature class. This is causing a couple issues on the back end (field values are being converted to different datatypes resulting in a failed publish)

Is there a better way to publish spatially enabled dataframes in an environment that is not using arcpy?

Thanks!

[jcarlson]

A better way would probably be to avoid it entirely. I've had lots of similar trouble publishing from a dataframe directly to a layer.

Personally, I would built the destination layer first in order to control the data types, then use the Python API to append data to it.

[I_AM_ERROR]

I was considering that and, yeah it would probably give better control over the destination schema.

[I_AM_ERROR]

Just feels pretty odd having to write a file out to disk just to immediately read it back in....😐