BUG: export to a wide GeoDataFrame may fail assigning an active geometry

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

No repository file or test is identified in the issue. First check the referenced GeoPandas PR and issue, then reproduce export of a wide GeoDataFrame with a MultiIndex against the available GeoPandas release; the work is done when active geometry assignment succeeds without an unnecessary compatibility patch.

Written by the indexing model from the issue text.

Description

There are some issues with creation of a wide GeoDataFrame with a MultiIndex. Both are coming from GeoPandas and one is being if fixed in https://github.com/geopandas/geopandas/pull/2088 while the other is reported at https://github.com/geopandas/geopandas/issues/2806.

Depending on the resolution of the latter, we may need to apply a patch on our side passing an indexer like set_geometry(("geometry", "", "")) instead of a simple set_geometry("geometry"). But we still need a release of GeoPandas (coming soon!) with the fix of the former, so it may be all resolved there.

Dominant language
Python
Stars
139
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xarray-contrib/xvec

All issues in xarray-contrib/xvec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.