Issues with overlay - oversimplifies in some cases, not sure what's wrong
See original GitHub issueTwo geodataframes with boundaries (census tracts and proprietary boundaries):

after
splits = gp.overlay(nhds, cts, how='intersection')
result is weired:

Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Don't Be Addicted: The Oft-Overlooked Dangers of Simplification
Our failure to recognize that there is a trade-off between relying on simplifications and our ability to exploit the many opportunities that a...
Read more >Understanding Our Rocky Relationship with Concrete Overlays
Concrete Decor columnist Chris Sullivan discusses installing concrete overlays.
Read more >Oversimplification - Bad Arguments - Wiley Online Library
The fallacy of oversimplification occurs when we attempt to make something appear simpler by ignoring certain relevant complexities.
Read more >Why AI & Overlay Widgets Fail to Protect or Serve
Overlays Affect the Users' Existing Assistive Technology Tools ... This is the most significant. Any person with a disability has their favorite ...
Read more >Way get info if JavaScriptObject is one of defined overlay objects
My problem is that I don't know what object is created in native code. ... bad case is that it's something else (string,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@Casyfill I think that is what the
geodataframefunctionis_validdoes. Usually something likedf.geometry = df.geometry.buffer(0)solves simple issues that cause geometries to not be valid.You could try to create a new clean environment? (that’s what also solved it in the issue you linked to). I suppose the problem is that you updates some libraries with conda-forge, and there is some conflict between other libraries from the default channel.