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

Version 2 pre-release / release master ticket #133

Closed
vincentsarago opened this issue May 7, 2020 · 11 comments
Closed

Version 2 pre-release / release master ticket #133

vincentsarago opened this issue May 7, 2020 · 11 comments

Comments

@vincentsarago
Copy link
Member

vincentsarago commented May 7, 2020

Because of #127, #132 and #126 we have to cut a new major release.

rio-cogeo/CHANGES.txt

Lines 1 to 7 in 25f9a72

2.0a1 (TBD)
------------------
- Dropping python 2 (#128)
- use new mercantile xy_bounds for better web-optimized file (#126)
- Allow temporary file on disk when using MemoryFile output
- add `--blocksize` option in CLI (#131)
- depreciate `rio_cogeo.utils.get_maximum_overview_level` and use rasterio.rio.overview.get_maximum_overview_level (#132)

changes are now in https://github.com/cogeotiff/rio-cogeo/tree/v2

@vincentsarago
Copy link
Member Author

2.0a1 - 2020/05/07

https://pypi.org/project/rio-cogeo/2.0a1/

@vincentsarago
Copy link
Member Author

FYI: I'm going to merge the V2 branch to master

@vincentsarago
Copy link
Member Author

2.0a3 - 2020/06/15

rio-cogeo/CHANGES.txt

Lines 1 to 4 in 5645799

2.0a3 (2020-06-15)
------------------
- add `info` CLI (#134)
- use `Deflate` as default temporary compression (#137)

@vincentsarago
Copy link
Member Author

2.0a4 - 2020/06/15

rio-cogeo/CHANGES.txt

Lines 1 to 3 in e4e4fdd

2.0a4 (2020-06-15)
------------------
- Force output width and height (#140)

@vincentsarago
Copy link
Member Author

2.0a5 - 2020/07/31

rio-cogeo/CHANGES.txt

Lines 1 to 6 in db8dabc

2.0a5 (2020-07-31)
------------------
- move most of the cogeo info code in rio_cogeo.cogeo.cog_info api
- add cog_validation info in cogeo info result
- cog_validate returns a tuple (is_valid, errors, warnings) (#142, co-author with @geospatial-jeff)
- add scale, offset, image tags and band color interpretation in cog_info (#145, #146 and #147)

@vincentsarago
Copy link
Member Author

2.0a6 - 2020/08/18

rio-cogeo/CHANGES.txt

Lines 1 to 7 in b9b5730

2.0a6 (2020-08-18)
------------------
- fix bug in cogeo.info when CRS in not set.
- add minzoom/maxzoom in cogeo.info output.
Breaking Changes:
- rio_cogeo.utils.get_max_zoom renamed rio_cogeo.utils.get_zooms and now return min/max zoom.

@vincentsarago
Copy link
Member Author

2.0a7 - 2020/09/23

rio-cogeo/CHANGES.txt

Lines 1 to 5 in 05be391

2.0a7 (2020-09-23)
------------------
- remove duplicate `count` information in rio_cogeo.cogeo.cog_info output (#150)
- allow COG with IFD offset up to 200 bytes to accomodate with GDAL 3.1 changes (#151)
- fix zoom level calculation in rio_cogeo.cogeo.cog_info

I think we are ok for an official release, Target date: 2020/09/28

@kylebarron
Copy link
Member

Official beta or 2.0?

@vincentsarago
Copy link
Member Author

@kylebarron I think we are fine to do an offical 2.0 directly. The only reason for the major version is the drop of python 2

@vincentsarago
Copy link
Member Author

2.0a8 - 2020/09/28

https://github.com/cogeotiff/rio-cogeo/releases/tag/2.0a8

Fixes #156

Official release of 2.0 is postponed to next week

@vincentsarago
Copy link
Member Author

2.0.0 - 2020/10/05

https://pypi.org/project/rio-cogeo/2.0.0/

🎉 thanks everyone!

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

No branches or pull requests

2 participants