-
Notifications
You must be signed in to change notification settings - Fork 25
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3 pre-release / release master ticket #72
Comments
3.0.a2 -2020/05/05release changes added in #73 |
3.0a3 - 2020/05/07Lines 1 to 4 in 5c6d683
|
3.0a4 - 2020/06/25Lines 1 to 4 in 21e6cba
|
3.0a5 (2020-06-29)Lines 1 to 4 in 9986e4f
Thanks @geospatial-jeff |
3.0a6 - 2020/07/31Lines 1 to 12 in c989249
|
3.0a7 - 2020/07/31Lines 1 to 6 in 157d319
|
3.0a8 - 2020/08/21Lines 1 to 7 in e3d82ba
|
3.0a9 and 3.0a10 - 2020/08/24Lines 1 to 7 in d26cde1
|
3.0.0a13 (2020-10-13)
|
3.0.0a14 (2020-10-22)
with MosaicBackend(
f"stac+{stac_endpoint}",
query.copy(),
11,
14,
backend_options={
"accessor": lambda feature: feature["id"],
"stac_next_link_key": "next",
}
) as mosaic:
Breaking changes
|
we just publish the first release candidate 馃コ I think the library is almost ready to go. Next changes will be mostly documentation related Changes3.0.0rc1 (2021-02-11)
breaking
|
Alright I lied I just pushed a
|
After intensive and precious work from @kylebarron (myself and @geospatial-jeff) we are releasing a new version of cogeo-mosaic today 馃帀 .
We refactored a lot of internal functions and methods and introduced new Backend concept, plus the adoption of Pydantic model for mosaicjson definition.
we created a doc to ease the migration: https://github.com/developmentseed/cogeo-mosaic/blob/master/docs/v3_migration.md
thanks a lot to @kylebarron and @geospatial-jeff for their help.
3.0a.1 - 2020/05/01
https://pypi.org/project/cogeo-mosaic/3.0a1/
The text was updated successfully, but these errors were encountered: