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
Feature Request: geospatial column analysis #1473
Comments
Hi @proselotis, thank for you feature request! And enthusiasm - contributions are always welcomed! I would be happy to have you contribution for the feature, nevertheless there are a few points that need further definition.
Let me get back to you with some more detailed requirements for this feature so we can iterate together! |
Hi, An alternative could be to extend ydata-profiling to support GeoPandas. GeoPandas uses Shapely internally and can handle Points, Multi-Points, Lines, Multi-Lines, Polygons, Multi-Polygons. |
Missing functionality
As a newer user to ydata-profiling, I am leveraging the package with various types of data. One data type that I am using is geospatial data, I am currently using separate columns for Latitude and Longitude as float values. However the output of a bar chart and correlation may be useful in some cases, it may be more useful to provide the output in a form of a map so the coverage of different areas can data can be seen by the user. Unless I missed something reading through the documentation, there isn't any current functionality for this.
I noticed in the contributing guidelines this was highlighted as a potential EDA: extending data type support (GPS coordinates).
Proposed feature
Plotting of points on a map within the variable exploration so you could consider the coverage areas of the data.
I am happy to help contribute on a topic like this, however there are a few different paths this could appear in so I wanted to know if there was a preference from the ydata team.
Data size
Type of data
Alternatives considered
Additional context
No response
The text was updated successfully, but these errors were encountered: