GeoAccessor.from_geodataframe() mangles geometries

Describe the bug Using GeoAccessor.from_geodataframe() results in mangled geometries. It seems to happen on more complex polygons with many holes.

To Reproduce Steps to reproduce the behavior:

import geopandas as gpd
from arcgis import GIS
import requests
from arcgis.features import GeoAccessor


gis=GIS("https://arcgis.com",username, password)

base_url = 'https://services1.arcgis.com/Hp6G80Pky0om7QvQ/arcgis/rest/services/DoD_Sites_Boundaries_Public/FeatureServer/0/query'

payload = {
'f': 'geojson',
'where': "SITE_NAME='Eglin Air Force Base'",
'outSR': 4326,
'outFields': '*'
}
response = requests.get(base_url, params=payload)

gdf=gpd.GeoDataFrame.from_features(response.json()['features'], crs="epsg:4326")

sedf=GeoAccessor.from_geodataframe(gdf, column_name="geometry")

lyr = sedf.spatial.to_featurelayer('test_poly')

Screenshots Source data: After converting to a Spatially Enabled dataframe: A closeup: Result:

Expected behavior I expect the geometries to stay the same.

Platform:

• OS: Windows 10
• Browser: Chrome
• Python API Version: 1.8.5

Additional context I tried the .buffer(0) method before converting to SEDF - didn’t work. I tried the make_valid() function from shapely.validation too, same result. Filling holes before converting to a spatially enabled dataframe worked, but it is not an acceptable solution.

[davidgrubmanchoicehotels]

Just for context, I have pretty much the same exact code as @manuela-butuc. Here is a screenshot of trying to upload the Census Subdivisions through a geodataframe and the sedf=GeoAccessor.from_geodataframe(gdf, column_name=“geometry”) command.

It does look kinda cool I must say.

[achapkowski]

@manuela-butuc thank you for the code and sample, we’ll take a look at this and get back to you.