Skip to content

Releases: wmgeolab/geoBoundaries

v6.0.0

14 Sep 12:52
@DanRunfola DanRunfola
v6.0.0
1289e40
Compare
Choose a tag to compare
v6.0.0 Latest
Latest

Version 6.0.0 ('Modeg'); Released 9/14/23

Issues: 64 issues closed, covering a wide range of improvements to the dataset.

New API: Our old (gbRequest.html) API will be fully deprecated soon, after a year of live testing of the updated API. Future requests should take the following format:
https://www.geoboundaries.org/api/current/gbOpen/[3-LETTER-ISO-CODE]/[ADM-LEVEL]/
More information can be found at https://www.geoboundaries.org/api.html.

Updated R Package: With the update of our API, the original R package for geoBoundaries will stop functioning. As we could not get in touch with the previous maintainer, we have forked the package and updated it accordingly. We will begin work to get it integrated into CRAN in the near future, as well as update some other pieces of the library (documentation, capabilities, and a few other pieces). A huge thanks to the original authors, as we wouldn't have explored R without your encouragement; if anyone is interested in contributing to this effort, we would be very excited to have you (as we mostly use python over here!).

CGAZ Updates: We have done another pass at updating the CGAZ product, which should generally have more consistent attribute information now.

More Regular Builds: We're making big strides towards getting more regular builds, to reduce the time between when a PR is accepted and the introduction of the data into the final dataset. Our average cadence is about once a week, today, and we hope to get to a consistent nightly cadence soon!

What's Changed

New Contributors

Full Changelog: v5.0.0...v6.0.0

Contributors

DanRunfola, jamesnelmore, and 9 other contributors
Assets 2

v5.0.0

23 Jan 14:10
@DanRunfola DanRunfola
v5.0.0
b7dd6a5
Compare
Choose a tag to compare
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)
Assets 2