Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev/bugfix #97

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Dev/bugfix #97

merged 2 commits into from
Feb 22, 2024

Conversation

peterrrock2
Copy link
Collaborator

Merge fix for crs

…ns function

This is a quick fix for #95. The main issue is that the from_records
function is inherited from the pandas library, and it does not track
so when it creates a GeoDataFrame from a list of records, it does not
assign the column labeled "geometry" as a geometry column, and, with
the new change to pandas 2, it looks like this ends up throwing the
following error:

ValueError: Assigning CRS to a GeoDataFrame without a geometry column
is not supported. Use GeoDataFrame.set_geometry to set the active
geometry column.`

If we use the constructor for the GeoDataFrame object intead, then
geopandas correctly handles the geometry column, and we can
assign the crs to the GeoDataFrame object directly.
Fix issue in from_records not tracking crs correctly in intersections function
@peterrrock2
Copy link
Collaborator Author

Already approved by Jeanne on merge into branch

@peterrrock2 peterrrock2 merged commit c6375ae into master Feb 22, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant