The conversion from sf to EE is a two-step process. First,
sf_as_ee
transform sf objects into a GeoJSON format using
geojson_json. Second, the GeoJSON generated will be
encrusted in an HTTP request using the server-side objects (ee$Geometry$*).
If the sf object is a large spatial object (>1Mb) it is likely to cause
bottlenecks and plodding connections. See
Client
vs Server documentation for more details. For dealing with very large spatial
objects, it is recommended to import it into the GEE asset. See
ee_upload for creating uploaded pipelines.
Earth Engine is strict on polygon ring directions (outer ring
counter-clockwise, and the inner one clockwise). If check_ring_dir
is TRUE,
it check every ring, and revert them if necessary, to counter clockwise for outer,
and clockwise for inner (hole) ones. By default this is FALSE because
it is an expensive operation.