You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you slice a GeoSeries, the Union indexing only leaves offsets for the sliced members, but the underlying point and sub-offsets are not modified or copied. However, if you then later use a coordinate accessor like sliced.polygons.x, the .x accessor doesn't understand that the offsets have changed and returns the same indices regardless of which slice you are calling it on.
…`.polygons` `GeoSeries` accessors (#685)
This PR uses the `column._meta` object to slice the sub-geometry accessors named in the title so that `.x`, `.y`, and `.xy` uses reflect any previous slicing that has occurred to the `GeoSeries`.
Fixes#683
Authors:
- H. Thomson Comer (https://github.com/thomcom)
Approvers:
- Michael Wang (https://github.com/isVoid)
URL: #685
Describe the bug
When you slice a
GeoSeries
, theUnion
indexing only leaves offsets for the sliced members, but the underlying point and sub-offsets are not modified or copied. However, if you then later use a coordinate accessor likesliced.polygons.x
, the.x
accessor doesn't understand that the offsets have changed and returns the same indices regardless of which slice you are calling it on.Steps/Code to reproduce bug
Expected behavior
The result of the two print results should be different
.x
values, reflecting different polygons.The text was updated successfully, but these errors were encountered: