GeoPandas 1.0 release about geopandas HOT 11 OPEN

It is out!

• https://github.com/geopandas/geopandas/releases/tag/v1.0.0-alpha1
• https://pypi.org/project/geopandas/1.0.0a1/

I wrote a short blog post with some highlights - https://martinfleischmann.net/geopandas-1.0-is-coming.-what-will-change/

from geopandas.

I suggest the following release plan:

Start with 1.0-alpha1 by the end of March that contains all the API-related changes but not necessarily all the bugfixes and enhancements. For that, I believe we need

• #3223
• #3212
• #3133
• Look into numpy / pandas dev failures
• #3190
• #3237
• #3240

Then, ideally by mid April, we could do 1.0-rc1 that shall contain the enhancements and deprecations and cut final 1.0 by end of April. That should give people enough time to test against 1.0 before it is released and provide feedback if needed. It should also give us enough time to finish what needs to be finished as end of March is unrealistic at this point. Thoughts?

from geopandas.

@m-richards good catch! The typo was not the only issue, #3206 was not merged :D. I was writing that last week, assuming it will be in.

from geopandas.

I think it would be good to try and solve #1038 for 1.0 - the discussion there is old but the proposed solution is potentially breaking, so better to try and include and resolve for 1.0.
I took a scan through the issues / open PRs and noticed this one, probably also worth revisting / deciding whether to action #3019 / #1975 sooner than later.
(not sure if I will be able to make the scheduled meeting tomorrow/ today)

from geopandas.

@kylebarron I don't know much about that but if you can get @jorisvandenbossche on board I won't object.

from geopandas.

@martinfleis thanks for cutting the alpha and writing a summary up!. Just fyi in your blog post, there's a typo in the fiona to pyogrio migration guide link, latert-> latest I think, might be good to fix if you are sharing the link around to promote the alpha to test.

from geopandas.

I'd be motivated to get #3156 in to 1.0 if we can agree on a proposed API. I'd be happy to make a PR

from geopandas.

The last thing that touches the existing API in some way is #3190. Once we get that in, I propose cutting 1.0-alpha1.

from geopandas.

I still think #1038 would be good to resolve before 1.0 since it will likely involve an API break. Will have a look and see if I can move that forward. Edit: opened #3237 as a way to take that merge request/ discussion forward.

from geopandas.

I am planning to cut 1.0.0-alpha1 tonight as we're already a bit behind the anticipated schedule.

Next milestone is rc1 with all the new functionality. I suppose it will be pushed to the end of April, with 1.0 coming (optimistically) in early May. We do have a hard deadline 24/5 due to GeoPython starting a few days after that.

from geopandas.

All good now - https://geopandas.org/en/latest/docs/user_guide/fiona_to_pyogrio.html.

from geopandas.