Skip to content

Releases: evansiroky/timezone-boundary-builder

2026c

Choose a tag to compare

@evansiroky evansiroky released this 11 Jul 06:36

Zone Changes

  • Update to latest OSM data.
  • Recalculate timezones since 1970 and timezones since now with most recent timezone database data.

Other Changes

  • Fix a bug that caused similar timezones to not merge despite same UTC Offsets after transitions. (#210)

2026b

Choose a tag to compare

@evansiroky evansiroky released this 29 Apr 21:01

Zone Changes

  • Update to latest OSM data.
  • Recalculate timezones since 1970 and timezones since now with most recent timezone database data.

2026a

Choose a tag to compare

@evansiroky evansiroky released this 08 Mar 05:45

2026a

Zone Changes

  • Update to latest OSM data
  • Add an expected zone overlap between America/Los_Angeles and America/Vancouver for a disputed area of seaward boundary of the Strait of Juan de Fuca.

Other Changes

  • Implement a maximum overpass request gap.

2025c

Choose a tag to compare

@evansiroky evansiroky released this 08 Jan 08:04

Zone Changes

  • Merge ocean zones into other zones that have similar timekeeping methods in 1970 with oceans and Now with oceans data products. (#187)
  • Update to latest OSM data

Other Changes

  • Include mapping of combined zones with similar timekeeping methods as release outputs. (#195)
  • Update Readme with notes on zone merging including visualizations. (#194)
  • Improve algorithm for calculating zones with similar timekeeping methods. (#191)

2025b

Choose a tag to compare

@evansiroky evansiroky released this 24 Mar 06:16

Zone Changes

  • Add new zone America/Coyhaique by taking area from America/Santiago.
  • Directly use OpenStreetMap data for areas in North and South Dakota.
  • Update to latest OSM data

2025a

Choose a tag to compare

@evansiroky evansiroky released this 21 Jan 05:58

Zone Changes

  • Update to latest OSM data

2024b

Choose a tag to compare

@evansiroky evansiroky released this 10 Sep 06:02

Zone Changes

  • Remove Asia/Choibalsan as it has been moved to the "backward" file in the timezone database.
  • Add an expected zone overlap between Asia/Pyongyang and Asia/Shanghai for a disputed area within the Tumen River.
  • Explicitly include Kalapani Territory in both Asia/Kathmandu and Asia/Kolkata.
  • Update to latest OSM data

Other Changes

  • Update a few npm pacakges.

2024a

Choose a tag to compare

@evansiroky evansiroky released this 14 Mar 06:43

Zone Changes

  • Update to reflect "same since now" changes taking effect in Kazakhstan
  • Update to latest OSM data

Other Changes

  • Add GitHub Action to create a new issue upon detecting a new timezone database release (#169)
  • Additional notes in #168

2023d

Choose a tag to compare

@evansiroky evansiroky released this 29 Dec 10:28

Zone Changes

  • Directly use OpenStreetMap timezone relations for the following zones:
    • Asia/Shanghai
    • Asia/Tashkent
    • Asia/Thimphu
    • Asia/Urumqi
    • Asia/Yangon
    • Asia/Yekaterinburg
    • Australia/Adelaide
    • Australia/Brisbane
    • Australia/Darwin
    • Australia/Hobart
    • Australia/Lindeman
    • Australia/Lord_Howe
    • Australia/Melbourne
    • Australia/Perth
    • Europe/Astrakhan
    • Europe/Berlin
    • Europe/Busingen
    • Europe/Kirov
    • Europe/Kyiv
    • Europe/Moscow
    • Europe/Paris
    • Europe/Samara
    • Europe/Saratov
    • Europe/Volgograd
    • Indian/Kerguelen
    • Pacific/Auckland
    • Pacific/Gambier
    • Pacific/Guam
    • Pacific/Honolulu
    • Pacific/Kwajalein
    • Pacific/Majuro
    • Pacific/Midway
    • Pacific/Noumea
    • Pacific/Pago_Pago
    • Pacific/Pitcairn
    • Pacific/Tahiti
  • Update to latest OSM data

Other Changes

  • Add code to be able to output additional release products (#145)
    • Add output of zones that share same timekeeping method since 1970
    • Add output of zones that share same timekeeping method since the current time
  • Add caching of various operations to reuse data from previous calculations
  • Refactor input data output
    • Move downloads to dedicated folder
    • Add cached data to dedicated folder
    • Include root-level files in root of zip file
  • Add ability to reuse downloaded OSM timezone comparison data by copying it to the working directory and reusing it on calculation retries
  • Refactor README noting new release types
  • Note Sponsorship Opportunity

2023b

Choose a tag to compare

@evansiroky evansiroky released this 26 Mar 08:09

Zone Changes

  • Directly use OpenStreetMap timezone relations for the following zones:
    • Africa/Porto-Novo
    • America/Anchorage
    • America/Fortaleza
    • America/Havana
    • America/Metlakatla
    • America/Nome
    • America/Noronha
    • America/Nuuk
    • America/Puerto_Rico
    • America/Punta_Arenas
    • America/Recife
    • America/Santiago
    • America/Sao_Paulo
    • America/Sitka
    • America/St_Thomas
    • Arctic/Longyearbyen
    • Asia/Aqtau
    • Asia/Atyrau
    • Asia/Bangkok
    • Asia/Famagusta
    • Asia/Gaza
    • Asia/Hebron
    • Asia/Ho_Chi_Minh
    • Asia/Jerusalem
    • Asia/Kamchatka
    • Asia/Khandyga
    • Asia/Krasnoyarsk
    • Asia/Kuala_Lumpur
    • Asia/Magadan
    • Asia/Nicosia
    • Asia/Pyongyang
    • Asia/Qostanay
    • Asia/Qyzylorda
    • Asia/Srednekolymsk
    • Asia/Ust-Nera
    • Asia/Vladivostok
    • Asia/Yakutsk
    • Pacific/Easter
  • Allow timezones America/Anchorage and America/Dawson to overlap (#145)
  • Update to latest OSM data