v5.0.0
Released on December 19, 2022, geoBoundaries 5.0 had a number of changes - the most important of which being a large change in how our Git repository is stored in order to future-proof the project. As such, archival releases have been moved into seperate git repositories. These archives will also be linked on the website. Going forward, all future releases should be contained within this repository. A big thanks to GitHub's engineers for helping resolve a number of challenges related to storing our database on GH servers ❤️.
| Release | Date | Link |
|---|---|---|
| geoBoundaries 4.0.0 | August 31, 2021 | 299e006 |
| geoBoundaries 3.0.0 | June 5, 2020 | 7c8dbc5 |
| geoBoundaries 2.0.1 | December 7, 2019 | 375ea48 |
| geoBoundaries 1.3.4 | November 11, 2018 | d3f7490 |
The changes in 5.0.0 are noted below:
Version 5.0.0 ('Ceald'); Released 12/19/2022
- 248 issues closed, largely representative of new boundaries!
- Territories! We have nearly every territory in the world included now, with only a few exceptions.
- Rebuilt backend build - we can support cloud or local now (*though with the caveat the codebases aren't unified, so our cloud builds result in different outputs, and are much more error prone right now. Looking to unify in the future!).
- Upgrades to the website contrast tools.
- New CGAZ product - updated to 5.0.0, build cleaned up a good bit.
- Updated geography-based ID system to fix edge cases (especially in dense regions like India and France ADM4/5).
- Updated coverage for most of Africa, including significantly better licensure.
- Updated replications of UN SALB and UN OCHA COD datasets, standardized to the geoBoundaries schema and accessible by API.
- Many boundaries with corrected water boundaries (i.e., water boundaries were removed and normalized to coastlines)