Skip to content

Releases: OpenDRR/boundaries-db

v1.4.4-beta+20220913

16 Sep 15:31
74ecb99
Compare
Choose a tag to compare

v1.4.4-beta+20220831

01 Sep 15:12
b513f60
Compare
Choose a tag to compare

Fix issues with EPSG:900913 in PostGIS where it’s actually projecting it into a unknown coord 900914. Asking people on Stack Exchange, and looks like PostGIS has already deprecated EPSG:900913 and suppose to be using EPSG:3857. So @wkhchow recreated a new SQL backup of boundaries with EPSG:3857 in v1.4.4-beta+20220831.

  • Original filename: opendrr-boundaries_with_full_hexgrid1km_remove_PT_aug2022.sql
  • File size: 8,729,648,926 bytes
  • SHA-256 checksum: 29d88fdae3ea5be7e0f70c800c5e91c69fff4764719c8275e7638e1b87a833ab
  • Creation date: 2022-08-31
  • From archive: opendrr-boundaries_with_full_hexgrid1km_remove_PT_aug2022.7z

Full Changelog: v1.4.4-alpha+20220621...v1.4.4-beta+20220831

v1.4.4-alpha+20220621

01 Sep 15:00
1506e5a
Compare
Choose a tag to compare

Add EPSG:900913 hexgrid, by @wkhchow

  • Original filename: opendrr-boundaries_with_full_hexgrid1km_remove_PT.sql
  • File size: 8,729,712,573 bytes
  • SHA-256 checksum: 7d773f69a9444e72b373a3b175a5be8f2812c69cb7043f5db6331b89210cb001
  • Creation date: 2022-06-21
  • From archive: boundaries - update_900913.7z.001boundaries - update_900913.7z.008

Full Changelog: https://github.com/OpenDRR/boundaries-db/commits/v1.4.4-alpha+20220621

(previously prematurely tagged as v1.4.4 which has since been removed.)