-
Notifications
You must be signed in to change notification settings - Fork 5
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
GeoPandas: Contribute enhancements, look up bugs already fixed #8
Comments
If that reassures you, I am planning to do a release before EuroScipy (which is end of August, I am also giving a talk there about GeoPandas). And contributing doesn't necessarily be to do actual coding, also giving feedback / opening issues about bugs / usability problems / enhancement requests you encounter during tutorials are very useful. (both are welcome!) Further, if you are worried/interested in the performance of geopandas, you can check out geopandas/geopandas#473 (the issue is about initial version of complete rewrite of internals of geopandas that should make it much faster) (sorry to hijack the issue here :-)) |
@jorisvandenbossche, thanks for chiming in! Please, hijack away.
Yes, this is very reassuring! Thanks so much. I look forward to seeing your presentation materials after EuroSciPy, and seeing if I can borrow something. Please feel free to grab anything from my tutorial materials (two notebooks plus markdown pages). I've gone ahead and commented on geopandas/geopandas#318. Hopefully it'll be of some use, and even better if someone points out a way to solve my problem. I'll actually try to submit a PR to address geopandas/geopandas#225 early next week. I've been looking into it and I think I know exactly what to do.
For my current usage patterns, performance is not a big deal. But it's great to hear about this cython work, and I've also heard about the Dask work (https://github.com/geopandas/geopandas/issues/461). My usage could definitely change in the future, depending on projects I'm involved with. |
@emiliom if the cython work is easily usable by that time (which I think is a decent bet) then benchmarking and performance testing would be very useful for the project. It would also be interesting to have people compare performance against other common tools like PostGIS, QGIS, and ArcGIS. |
Ok, will keep it in mind. I doubt I can offer any real benchmarking and performance testing other than anecdotal, qualitative feedback, by the time of our event (mid September) or during the event. But maybe afterwards we can think of something |
dissolve
method has been fixed!to_file()
,from_postgis
vsread_postgis()
) to confirm that:I should probably make a list of the bugs or questions I identified in my tutorial notebooks last year ...
The text was updated successfully, but these errors were encountered: