-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Bug Report: Confusing Error with Geometry Column #1567
Labels
Comments
saulshanabrook
added a commit
to saulshanabrook/ydata-profiling
that referenced
this issue
Mar 29, 2024
Fixes ydataai#1567 by raising a better error message pointing out when a column has an unsortable index.
fabclmnt
pushed a commit
to saulshanabrook/ydata-profiling
that referenced
this issue
Apr 5, 2024
Fixes ydataai#1567 by raising a better error message pointing out when a column has an unsortable index.
closed based on #1568 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behaviour
When I create a report on a dataset with geometry column, like from GeoPandas, it will raise a confusing error:
Expected Behaviour
It's fine that ydata doesn't support geodata, but it would nice to either to drop this column or tell me I should drop it beforehand.
Data Description
For the reproducible example, I just made some sample data. My data is available here: https://github.com/saulshanabrook/property-data
Code that reproduces the bug
pandas-profiling version
v4.1.1
Dependencies
The text was updated successfully, but these errors were encountered: