Vector Zonal Stats: Error when aligning OSM POIs to an Indonesian Regency

[alronlam]

Colab notebook for testing:

• https://colab.research.google.com/drive/147HWUgaBztsZuBPrI_HTckBrz_vl9l1l?usp=sharing

Scenario:

• Created an AOI GDF representing the Subang Regency of Indonesia.
• Tried simply counting the POIs within this area, but got the error seen in the screenshot:

Could it be a typo? Since the key error mentions "GeoWrangleer_aoi_index"

In case it's relevant, noting that the function works when I passed in grid tiles instead of the Subang Regency gdf itself.

[jtmiclat]

This error stems from us not supporting multiindex GeoDataFrames and dissolving generating a multiindex GeoDataFrame

Converting the following

aoi = idn[idn.ADM2_EN == "Subang"].dissolve(by="ADM2_EN")

to

aoi = idn[idn.ADM2_EN == "Subang"]

works.

[jtmiclat]

Alternatively, you can pass as_index as False and this doesn't generate a MultiIndex GeoDataFrame

aoi = idn[idn.ADM2_EN == "Subang"].dissolve(by="ADM2_EN", as_index=False)

[jtmiclat]

@butchtm @alronlam Should we support multiindex geodataframes or should we throw an assertion error telling users that we dont support it?

[butchtm]

@jtmiclat @alronlam

For now, we could do a quick fix to throw an assertion error so users are aware we don't support multi-index for now.

Then file an enhancement request to support multi-indexes separately later. cc @tm-kah-alforja

[alronlam]

Ahh I see. Agree with @butchtm I think we can just throw an assertion error for now so it's clear what the error is and how to fix it. I'm not really sure either if multi-index support is something that's necessary.

[jtmiclat]

Alright, i can take this on.

[butchtm]

Reopening this. Still reproducible error when I tried today. See this updated gist.