Giter Club home page Giter Club logo

timezone-boundary-builder's People

Contributors

dependabot[bot] avatar dustin-johnson avatar evansiroky avatar kevmo314 avatar nfuller avatar nilsnolde avatar redorkulated avatar renzoapm avatar ringsaturn avatar romaniakovlev avatar tpgillam avatar twitchax avatar voegelas avatar zverok avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

timezone-boundary-builder's Issues

2016j

Add new zones:

  • Asia/Atyrau
  • Europe/Saratov

adding "\n" to .json for parseability

IMO it would be nice to add newline characters to the .json (after every tz or even polygon).
I am trying to parse it with python atm and with the file just having one line this is way more complicated.
With 120MB a few more characters wouldn't hurt I think. Or are there any cases where having just one line is helpful?

GMT offsets in seas/oceans reversed

Just as an example (see image below), Asia/Baku (pink) is in GMT+4 while the timezone covering the adjacent Caspian Sea (green) shows Etc/GMT-3. I think the signs for water areas must be reversed to positive (+) in easterly direction and negative (-) the way around in order to comply with other (land) time zones.

https://i.imgur.com/ZG6q0um.jpg

Zone IDs switched in Greenland

Hey,
thanks for your great work!
I found a small issue in the shp release with oceans: The tzid's of two polygons in Greenland are switched: America/Danmarkshavn and America/Scoresbysund. America/Danmarkshavn should be the more northern one.

Greetings

Asia/Shanghai and Asia/Urumqi

From my reading of Xinjiang Time, it seems to me that Asia/Shanghai and Asia/Urumqi should overlap, since both time zones are in use in Xinjiang.

I'm guessing this is a deliberate choice, but maybe there should be some alias zone created for Asia/Shanghai that includes the entire zone?

Africa/Johannesburg

I happened to notice that the polygons for Africa/Johannesburg contain an odd vertical slice of Antarctica. I doubt that's intentional, but I could be mistaken.

2016i

Add new zone for Asia/Famagusta

Create builder config for all timezones

  • Africa/Abidjan
  • Africa/Accra
  • Africa/Addis_Ababa
  • Africa/Algiers
  • Africa/Asmara
  • Africa/Bamako
  • Africa/Bangui
  • Africa/Banjul
  • Africa/Bissau
  • Africa/Blantyre
  • Africa/Brazzaville
  • Africa/Bujumbura
  • Africa/Cairo
  • Africa/Casablanca
  • Africa/Ceuta
  • Africa/Conakry
  • Africa/Dakar
  • Africa/Dar_es_Salaam
  • Africa/Djibouti
  • Africa/Douala
  • Africa/El_Aaiun
  • Africa/Freetown
  • Africa/Gaborone
  • Africa/Harare
  • Africa/Johannesburg
  • Africa/Juba
  • Africa/Kampala
  • Africa/Khartoum
  • Africa/Kigali
  • Africa/Kinshasa
  • Africa/Lagos
  • Africa/Libreville
  • Africa/Lome
  • Africa/Luanda
  • Africa/Lubumbashi
  • Africa/Lusaka
  • Africa/Malabo
  • Africa/Maputo
  • Africa/Maseru
  • Africa/Mbabane
  • Africa/Mogadishu
  • Africa/Monrovia
  • Africa/Nairobi
  • Africa/Ndjamena
  • Africa/Niamey
  • Africa/Nouakchott
  • Africa/Ouagadougou
  • Africa/Porto-Novo
  • Africa/Sao_Tome
  • Africa/Tripoli
  • Africa/Tunis
  • Africa/Windhoek
  • America/Adak
  • America/Anchorage
  • America/Anguilla
  • America/Antigua
  • America/Araguaina
  • America/Argentina/Buenos_Aires
  • America/Argentina/Catamarca
  • America/Argentina/Cordoba
  • America/Argentina/Jujuy
  • America/Argentina/La_Rioja
  • America/Argentina/Mendoza
  • America/Argentina/Rio_Gallegos
  • America/Argentina/Salta
  • America/Argentina/San_Juan
  • America/Argentina/San_Luis
  • America/Argentina/Tucuman
  • America/Argentina/Ushuaia
  • America/Aruba
  • America/Asuncion
  • America/Atikokan
  • America/Bahia
  • America/Bahia_Banderas
  • America/Barbados
  • America/Belem
  • America/Belize
  • America/Blanc-Sablon
  • America/Boa_Vista
  • America/Bogota
  • America/Boise
  • America/Cambridge_Bay
  • America/Campo_Grande
  • America/Cancun
  • America/Caracas
  • America/Cayenne
  • America/Cayman
  • America/Chicago
  • America/Chihuahua
  • America/Coral_Harbour
  • America/Costa_Rica
  • America/Creston
  • America/Cuiaba
  • America/Curacao
  • America/Danmarkshavn
  • America/Dawson
  • America/Dawson_Creek
  • America/Denver
  • America/Detroit
  • America/Dominica
  • America/Edmonton
  • America/Eirunepe
  • America/El_Salvador
  • America/Fort_Nelson
  • America/Fortaleza
  • America/Glace_Bay
  • America/Godthab
  • America/Goose_Bay
  • America/Grand_Turk
  • America/Grenada
  • America/Guadeloupe
  • America/Guatemala
  • America/Guayaquil
  • America/Guyana
  • America/Halifax
  • America/Havana
  • America/Hermosillo
  • America/Indiana/Indianapolis
  • America/Indiana/Knox
  • America/Indiana/Marengo
  • America/Indiana/Petersburg
  • America/Indiana/Tell_City
  • America/Indiana/Vevay
  • America/Indiana/Vincennes
  • America/Indiana/Winamac
  • America/Inuvik
  • America/Iqaluit
  • America/Jamaica
  • America/Juneau
  • America/Kentucky/Louisville
  • America/Kentucky/Monticello
  • America/Kralendijk
  • America/La_Paz
  • America/Lima
  • America/Los_Angeles
  • America/Lower_Princes
  • America/Maceio
  • America/Managua
  • America/Manaus
  • America/Marigot
  • America/Martinique
  • America/Matamoros
  • America/Mazatlan
  • America/Menominee
  • America/Merida
  • America/Metlakatla
  • America/Mexico_City
  • America/Miquelon
  • America/Moncton
  • America/Monterrey
  • America/Montevideo
  • America/Montreal
  • America/Montserrat
  • America/Nassau
  • America/New_York
  • America/Nipigon
  • America/Nome
  • America/Noronha
  • America/North_Dakota/Beulah
  • America/North_Dakota/Center
  • America/North_Dakota/New_Salem
  • America/Ojinaga
  • America/Panama
  • America/Pangnirtung
  • America/Paramaribo
  • America/Phoenix
  • America/Port_of_Spain
  • America/Port-au-Prince
  • America/Porto_Velho
  • America/Puerto_Rico
  • America/Rainy_River
  • America/Rankin_Inlet
  • America/Recife
  • America/Regina
  • America/Resolute
  • America/Rio_Branco
  • America/Santarem
  • America/Santiago
  • America/Santo_Domingo
  • America/Sao_Paulo
  • America/Scoresbysund
  • America/Sitka
  • America/St_Barthelemy
  • America/St_Johns
  • America/St_Kitts
  • America/St_Lucia
  • America/St_Thomas
  • America/St_Vincent
  • America/Swift_Current
  • America/Tegucigalpa
  • America/Thule
  • America/Thunder_Bay
  • America/Tijuana
  • America/Toronto
  • America/Tortola
  • America/Vancouver
  • America/Whitehorse
  • America/Winnipeg
  • America/Yakutat
  • America/Yellowknife
  • Antarctica/Macquarie
  • Arctic/Longyearbyen
  • Asia/Aden
  • Asia/Almaty
  • Asia/Amman
  • Asia/Anadyr
  • Asia/Aqtau
  • Asia/Aqtobe
  • Asia/Ashgabat
  • Asia/Baghdad
  • Asia/Bahrain
  • Asia/Baku
  • Asia/Bangkok
  • Asia/Barnaul
  • Asia/Beirut
  • Asia/Bishkek
  • Asia/Brunei
  • Asia/Chita
  • Asia/Choibalsan
  • Asia/Chongqing
  • Asia/Colombo
  • Asia/Damascus
  • Asia/Dhaka
  • Asia/Dili
  • Asia/Dubai
  • Asia/Dushanbe
  • Asia/Gaza
  • Asia/Harbin
  • Asia/Hebron
  • Asia/Ho_Chi_Minh
  • Asia/Hong_Kong
  • Asia/Hovd
  • Asia/Irkutsk
  • Asia/Jakarta
  • Asia/Jayapura
  • Asia/Jerusalem
  • Asia/Kabul
  • Asia/Kamchatka
  • Asia/Karachi
  • Asia/Kashgar
  • Asia/Kathmandu
  • Asia/Khandyga
  • Asia/Kolkata
  • Asia/Krasnoyarsk
  • Asia/Kuala_Lumpur
  • Asia/Kuching
  • Asia/Kuwait
  • Asia/Macau
  • Asia/Magadan
  • Asia/Makassar
  • Asia/Manila
  • Asia/Muscat
  • Asia/Nicosia
  • Asia/Novokuznetsk
  • Asia/Novosibirsk
  • Asia/Omsk
  • Asia/Oral
  • Asia/Phnom_Penh
  • Asia/Pontianak
  • Asia/Pyongyang
  • Asia/Qatar
  • Asia/Qyzylorda
  • Asia/Rangoon
  • Asia/Riyadh
  • Asia/Sakhalin
  • Asia/Samarkand
  • Asia/Seoul
  • Asia/Shanghai
  • Asia/Singapore
  • Asia/Srednekolymsk
  • Asia/Taipei
  • Asia/Tashkent
  • Asia/Tbilisi
  • Asia/Tehran
  • Asia/Thimphu
  • Asia/Tokyo
  • Asia/Tomsk
  • Asia/Ulaanbaatar
  • Asia/Urumqi
  • Asia/Ust-Nera
  • Asia/Vientiane
  • Asia/Vladivostok
  • Asia/Yakutsk
  • Asia/Yekaterinburg
  • Asia/Yerevan
  • Atlantic/Azores
  • Atlantic/Bermuda
  • Atlantic/Canary
  • Atlantic/Cape_Verde
  • Atlantic/Faroe
  • Atlantic/Madeira
  • Atlantic/Reykjavik
  • Atlantic/South_Georgia
  • Atlantic/St_Helena
  • Atlantic/Stanley
  • Australia/Adelaide
  • Australia/Brisbane
  • Australia/Broken_Hill
  • Australia/Currie
  • Australia/Darwin
  • Australia/Eucla
  • Australia/Hobart
  • Australia/Lindeman
  • Australia/Lord_Howe
  • Australia/Melbourne
  • Australia/Perth
  • Australia/Sydney
  • Europe/Amsterdam
  • Europe/Andorra
  • Europe/Astrakhan
  • Europe/Athens
  • Europe/Belgrade
  • Europe/Berlin
  • Europe/Bratislava
  • Europe/Brussels
  • Europe/Bucharest
  • Europe/Budapest
  • Europe/Busingen
  • Europe/Chisinau
  • Europe/Copenhagen
  • Europe/Dublin
  • Europe/Gibraltar
  • Europe/Guernsey
  • Europe/Helsinki
  • Europe/Isle_of_Man
  • Europe/Istanbul
  • Europe/Jersey
  • Europe/Kaliningrad
  • Europe/Kiev
  • Europe/Kirov
  • Europe/Lisbon
  • Europe/Ljubljana
  • Europe/London
  • Europe/Luxembourg
  • Europe/Madrid
  • Europe/Malta
  • Europe/Mariehamn
  • Europe/Minsk
  • Europe/Monaco
  • Europe/Moscow
  • Europe/Oslo
  • Europe/Paris
  • Europe/Podgorica
  • Europe/Prague
  • Europe/Riga
  • Europe/Rome
  • Europe/Samara
  • Europe/San_Marino
  • Europe/Sarajevo
  • Europe/Simferopol
  • Europe/Skopje
  • Europe/Sofia
  • Europe/Stockholm
  • Europe/Tallinn
  • Europe/Tirane
  • Europe/Ulyanovsk
  • Europe/Uzhgorod
  • Europe/Vaduz
  • Europe/Vatican
  • Europe/Vienna
  • Europe/Vilnius
  • Europe/Volgograd
  • Europe/Warsaw
  • Europe/Zagreb
  • Europe/Zaporozhye
  • Europe/Zurich
  • Indian/Antananarivo
  • Indian/Chagos
  • Indian/Christmas
  • Indian/Cocos
  • Indian/Comoro
  • Indian/Kerguelen
  • Indian/Mahe
  • Indian/Maldives
  • Indian/Mauritius
  • Indian/Mayotte
  • Indian/Reunion
  • Pacific/Apia
  • Pacific/Auckland
  • Pacific/Bougainville
  • Pacific/Chatham
  • Pacific/Chuuk
  • Pacific/Easter
  • Pacific/Efate
  • Pacific/Enderbury
  • Pacific/Fakaofo
  • Pacific/Fiji
  • Pacific/Funafuti
  • Pacific/Galapagos
  • Pacific/Gambier
  • Pacific/Guadalcanal
  • Pacific/Guam
  • Pacific/Honolulu
  • Pacific/Johnston
  • Pacific/Kiritimati
  • Pacific/Kosrae
  • Pacific/Kwajalein
  • Pacific/Majuro
  • Pacific/Marquesas
  • Pacific/Midway
  • Pacific/Nauru
  • Pacific/Niue
  • Pacific/Norfolk
  • Pacific/Noumea
  • Pacific/Pago_Pago
  • Pacific/Palau
  • Pacific/Pitcairn
  • Pacific/Pohnpei
  • Pacific/Port_Moresby
  • Pacific/Rarotonga
  • Pacific/Saipan
  • Pacific/Tahiti
  • Pacific/Tarawa
  • Pacific/Tongatapu
  • Pacific/Wake
  • Pacific/Wallis
  • Pacific/Yap

Parse error

I was hoping to build this into a Gradle plugin to automate downloading timezone data into an Android app (along with another library to convert to Java) but ran into an error running the script per instructions in readme:

getting data for Argentina
downloading from overpass
waiting 4 seconds
Success, decreasing overpass request gap
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
error converting geojson to geometry
error converting overpass result to geojson
n {}

/Users/phil/.../timezone-boundary-builder/index.js:210
            throw e
            ^
[object Object]

Fix Viedma Glacier area again

The borders in OSM in this area have changed again and the boundary building process needs to be fixed. This should be the last blocking issue before 2018d is released.

2018g

  • Get original script working with current OSM data
  • #46
  • #42
  • #41
  • #40
  • #51
  • #49
  • Update changelog
  • Update README
  • Update Wiki about errors
  • Create release with uploaded files

Update to canonical names

One of my users pointed out that my library is returning Asia/Rangoon instead of Asia/Yangon for locations in Myanmar. mattjohnsonpint/GeoTimeZone#28

This appears to stem from the data in the timezones.json file here.

Could you please check that the time zone ids are all canoncialized to the current Zone entries instead of Link entries?

Thanks.

Refactor Northeastern Arizona boundaries

There's been a report at https://github.com/darkskyapp/tz-lookup/issues/7 that the town of Page, AZ is resolving to America/Denver when it should be America/Phoenix.

As of right now, it appears that the area around Page, AZ relies on data that was imported into OpenStreetMap from the efele.net shapefile. The shaded area is America/Phoenix.

screen shot 2017-03-17 at 9 43 09 am

I've read a few online articles here and there that suggest that Page, AZ and surrounding areas should be in America/Phoenix. So, I'm creating this issue to try and figure out the best way to draw the boundaries in Northeastern Arizona. Shown below are the current boundaries:

screen shot 2017-03-17 at 10 14 54 am

All of the shaded area is America/Phoenix and the unshaded is America/Denver. In OSM, the boundary appears to be an import of the efele.net shapefile outlining the boundary of the Navajo Nation enclaving the Hopi Reservation. Unfortunately, I'm not sure if an OSM relation exists for either the Navajo Nation or Hopi Reservation.

Add description entries to all manual geometries

  • operation 1 of zone: Africa/Ceuta
  • operation 1 of zone: Africa/Juba
  • operation 1 of zone: Africa/Khartoum
  • operation 1 of zone: Africa/Kinshasa
  • operation 1 of zone: Africa/Lubumbashi
  • operation 1 of zone: America/Adak
  • operation 1 of zone: America/Anchorage
  • operation 1 of zone: America/Argentina/Buenos_Aires
  • operation 1 of zone: America/Argentina/Cordoba
  • operation 1 of zone: America/Argentina/Salta
  • operation 1 of zone: America/Bahia_Banderas
  • operation 1 of zone: America/Blanc-Sablon
  • operation 2 of zone: America/Blanc-Sablon
  • operation 1 of zone: America/Cayenne
  • operation 1 of zone: America/Danmarkshavn
  • operation 0 of zone: America/Dawson
  • operation 1 of zone: America/Fortaleza
  • operation 1 of zone: America/Glace_Bay
  • operation 1 of zone: America/Godthab
  • operation 2 of zone: America/Godthab
  • operation 3 of zone: America/Godthab
  • operation 1 of zone: America/Goose_Bay
  • operation 1 of zone: America/Guayaquil
  • operation 1 of zone: America/Halifax
  • operation 1 of zone: America/Havana
  • operation 1 of zone: America/Hermosillo
  • operation 0 of zone: America/Inuvik
  • operation 1 of zone: America/Juneau
  • operation 1 of zone: America/Mazatlan
  • operation 1 of zone: America/Metlakatla
  • operation 1 of zone: America/Mexico_City
  • operation 1 of zone: America/Moncton
  • operation 3 of zone: America/Moncton
  • operation 1 of zone: America/Montreal
  • operation 2 of zone: America/Montreal
  • operation 3 of zone: America/Montreal
  • operation 4 of zone: America/Montreal
  • operation 1 of zone: America/New_York
  • operation 26 of zone: America/New_York
  • operation 27 of zone: America/New_York
  • operation 1 of zone: America/Nome
  • operation 1 of zone: America/Noronha
  • operation 1 of zone: America/Puerto_Rico
  • operation 1 of zone: America/Rainy_River
  • operation 1 of zone: America/Recife
  • operation 1 of zone: America/Sao_Paulo
  • operation 1 of zone: America/Scoresbysund
  • operation 1 of zone: America/Sitka
  • operation 3 of zone: America/Sitka
  • operation 1 of zone: America/St_Johns
  • operation 1 of zone: America/St_Thomas
  • operation 1 of zone: America/Thule
  • operation 1 of zone: America/Tijuana
  • operation 1 of zone: America/Vancouver
  • operation 1 of zone: America/Whitehorse
  • operation 1 of zone: America/Winnipeg
  • operation 1 of zone: America/Yakutat
  • operation 1 of zone: America/Yellowknife
  • operation 1 of zone: Antarctica/Macquarie
  • operation 1 of zone: Arctic/Longyearbyen
  • operation 1 of zone: Asia/Almaty
  • operation 1 of zone: Asia/Famagusta
  • operation 1 of zone: Asia/Gaza
  • operation 1 of zone: Asia/Hebron
  • operation 1 of zone: Asia/Hovd
  • operation 1 of zone: Asia/Jakarta
  • operation 1 of zone: Asia/Jayapura
  • operation 1 of zone: Asia/Kuala_Lumpur
  • operation 1 of zone: Asia/Kuching
  • operation 1 of zone: Asia/Makassar
  • operation 1 of zone: Asia/Nicosia
  • operation 1 of zone: Asia/Sakhalin
  • operation 1 of zone: Asia/Ulaanbaatar
  • operation 1 of zone: Asia/Ust-Nera
  • operation 1 of zone: Asia/Vladivostok
  • operation 1 of zone: Asia/Yakutsk
  • operation 1 of zone: Atlantic/Azores
  • operation 1 of zone: Atlantic/Canary
  • operation 1 of zone: Atlantic/Madeira
  • operation 1 of zone: Australia/Brisbane
  • operation 1 of zone: Australia/Currie
  • operation 1 of zone: Australia/Eucla
  • operation 1 of zone: Australia/Hobart
  • operation 2 of zone: Australia/Hobart
  • operation 1 of zone: Australia/Lindeman
  • operation 1 of zone: Australia/Lord_Howe
  • operation 1 of zone: Australia/Perth
  • operation 3 of zone: Australia/Sydney
  • operation 4 of zone: Australia/Sydney
  • operation 1 of zone: Europe/Amsterdam
  • operation 1 of zone: Europe/Astrakhan
  • operation 3 of zone: Europe/Berlin
  • operation 1 of zone: Europe/Busingen
  • operation 1 of zone: Europe/Lisbon
  • operation 1 of zone: Europe/Madrid
  • operation 1 of zone: Europe/Oslo
  • operation 1 of zone: Europe/Paris
  • operation 1 of zone: Indian/Christmas
  • operation 1 of zone: Indian/Cocos
  • operation 1 of zone: Indian/Kerguelen
  • operation 1 of zone: Indian/Mayotte
  • operation 1 of zone: Indian/Reunion
  • operation 1 of zone: Pacific/Auckland
  • operation 1 of zone: Pacific/Chatham
  • operation 1 of zone: Pacific/Easter
  • operation 1 of zone: Pacific/Enderbury
  • operation 1 of zone: Pacific/Galapagos
  • operation 1 of zone: Pacific/Gambier
  • operation 1 of zone: Pacific/Guam
  • operation 1 of zone: Pacific/Honolulu
  • operation 1 of zone: Pacific/Johnston
  • operation 1 of zone: Pacific/Kiritimati
  • operation 1 of zone: Pacific/Kwajalein
  • operation 1 of zone: Pacific/Majuro
  • operation 1 of zone: Pacific/Marquesas
  • operation 1 of zone: Pacific/Midway
  • operation 1 of zone: Pacific/Norfolk
  • operation 1 of zone: Pacific/Noumea
  • operation 1 of zone: Pacific/Pago_Pago
  • operation 1 of zone: Pacific/Saipan
  • operation 1 of zone: Pacific/Tahiti
  • operation 1 of zone: Pacific/Tarawa
  • operation 1 of zone: Pacific/Wake
  • operation 1 of zone: Pacific/Wallis

Oceans not covered

Hi,
is there a way to merge with timezones on water? Die Oceans are covered with timezone stripes aswell and i'd need them.

Flo

Error generating France

I am getting an error when processing data for France (all preceding regions consistently work as expected). The error is repeatable when resuming the script. If I delete other regions generated json files (in downloads directory) and resume the script the deleted regions are correctly generated and the script fails on France again.

getting data for France
downloading from overpass
waiting 4 seconds
Success, decreasing overpass request gap
/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/jsts/dist/jsts.min.js:17
if(null!==t._sym||null!==e._sym||null!==t._next||null!==e._next)throw new IllegalStateException("Edges are already initialized");return t.init(e),t},Li.create=function(t,e){var n=new Li(t),i=new Li(e);return n.init(i),n},ro(wi,Li),io(wi.prototype,{mark:function(){this._isMarked=!0},setMark:function(t){this._isMarked=t},isMarked:function(){return this._isMarked},interfaces_:function(){return[]},getClass:function(){return wi}}),wi.setMarkBoth=function(t,e){t.setMark(e),t.sym().setMark(e)},wi.isMarked=function(t){return t.isMarked()},wi.setMark=function(t,e){t.setMark(e)},wi.markBoth=function(t){t.mark(),t.sym().mark()},wi.mark=function(t){t.mark()},io(Ri.prototype,{insert:function(t,e,n){var i=this.create(t,e);null!==n?n.insert(i):this.vertexMap.put(t,i);var r=this.vertexMap.get(e);return null!==r?r.insert(i.sym()):this.vertexMap.put(e,i.sym()),i},create:function(t,e){var n=this.createEdge(t),i=this.createEdge(e);return Li.

TypeError: Cannot read property 'getGeometryType' of undefined
    at Fi.write (/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/jsts/dist/jsts.min.js:17:10307)
    at qi.write (/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/jsts/dist/jsts.min.js:17:13980)
    at geomToGeoJsonString (/Users/eric_hansen/dev/timezone-boundary-builder/index.js:110:39)
    at asynclib.auto.saveSingleMultiPolygon (/Users/eric_hansen/dev/timezone-boundary-builder/index.js:187:38)
    at runTask (/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:1619:13)
    at /Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:1559:13
    at processQueue (/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:1569:13)
    at taskComplete (/Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:1588:9)
    at /Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:1612:17
    at /Users/eric_hansen/dev/timezone-boundary-builder/node_modules/async/dist/async.js:906:16

Upload to Wikipedia

Hi Evan,

I think your rendering of the time zone maps would fit better than the older image of the tz_world data shown on Wikipedia here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

Would you either please grant permission to release the rendered image under one of the Creative Commons licenses accepted on Wikimedia Commons, or perhaps just upload it there yourself?

Thanks a lot.
-Matt

Asia/Shanghai Asia/Taipei overlap

Those overlap are not necessary. These islands are disputed, but they are just being disputed in the same way as the entire territory of Taiwan is being disputed.

error converting geojson to geometry

node --max-old-space-size=8192 index.js
....[some expected output]...
getting data for Atikokan-tz
downloading from overpass
waiting 4 seconds
Success, decreasing overpass request gap
combining border
error converting geojson to geometry
error converting overpass result to geojson

/timezone-boundary-builder/index.js:202
throw e
^
[object Object]

Enviroment:
Windows 10
node --version
v6.9.4
EDIT: File: debug_geojson_read_error.json contains a Polygon representing the border of Atikokan timezone

Asia/Krasnoyarsk and America/Santiago: Fail to select the areas

Hi there,

When opening the shapefile in Google Earth v7.3.3832 and selecting any timezone area, GE normally navigates to that area showing tzid under the left-side 'Places' window. But this is only partially true for Asia/Krasnoyarsk - in fact, only a group of island polygons are visible/selectable while the rest of the Krasnoyarsk Krai remains in focus but without any noticeable polygon boundaries. No navigation is possible. I wonder if the issue is somehow related to unclosed polygon?

EDIT: I have the same issue with continental Chile (America/Santiago) except a group of Pacific islands lying westwards the country.

See the image: https://i.imgur.com/EJaYdLE.jpg

Thanks!

Pacific/Auckland

The bounding box for Pacific/Auckland seems to be incorrect:

-29.03033,-179.059153
-29.03033,179.364359
-52.821369,179.364359
-52.821369,-179.059153
-29.03033,-179.059153

2017a

  • New Zone America/Punta_Arenas
  • Four Alabama towns by GA border observe Eastern time
  • Manually build America/Chicago from states and county boundaries
  • Manually build America/Mexico_City
  • Figure out what is wrong w/ Syria boundary
  • Figure out what is wrong w/ Turkey boundary
  • Resolve Asia/Chita - Asia/Irkutsk overlap
  • Resolve Europe/Belgrade - Europe/Zagreb overlap
  • Patch area in Asia/Kashgar

Node version in readme

The readme states:

The script has only been verified to run with Node.js 6 on the MacOS platform

Is this still true? Node has evolved considerably. I don't expect folks running the script would want to downgrade. Node 6 (Boron) is still in "Maintenance LTS" status, but not for much longer.

Thanks.

Groupsing Island Chains

First of all, let me say THANK YOU very much for creating this! This seems like a much more viable and accurate option than efele.net maps. In particular, I love that you've included territorial waters, as this eliminates all the complex shoreline data in Alaska and Canada (for example).

However, I'm curious if something more can be done in defining territorial waters better for island chains? For example, the waters in the Hawaiian Islands are all probably in the Pacific/Honolulu time zone, but since the territorial waters are drawn around the individual islands, only the areas where the boundaries overlap are merged. There's a small gap between Maui and Hawaii and a larger gap between Oahu and Kauai that should also be considered part of these waters, IMHO.

image

Same goes for Micronesia, Marshall Islands, and many other places.

Any thoughts on how to reconcile this without manually drawing polygons? I really like the approach of using OpenStreetMaps as a primary source.

Handling of timezones in China

  1. The Asia/Urumqi in Southern China should be removed. As the original coloring of that zone were based on dubious historical message, and more importantly no one in that area would actually use UTC+6, which is the current value for that Asia/Urumqi zone, therefore that area should not be Asia/Urumqi.
  2. I can't find any sources for anyone in Tibet and Qinghai area use UTC+6 time, as such it might not be appropriate to color them as Asia/Urumqi or Asia/Kashgar.
  3. Because more than one time are used by different population in Xinjiang, I suggest coloring that area with strips of UTC+6 and UTC+8.
  4. perhaps Asia/Kashgar, Asia/Harbin and Asia/Chongqing should be completely removed from the map as their existence in tz.db is only for legacy reason.

About shape file to geojson

i want to find a way to produce the geojson file from your shapefile.

but i find that ,the tool from the web or ogr2ogr can not produce the same content compared with your shapfile.geojson.zip released on the web.
EG:
The geojson i produced (the same shapefile) :
{ "tzid": "Africa/Abidjan" }, "geometry": { "type": "Polygon", "coordinates": [ [ [ -5.440683, 4.896553 ], [ -5.555659, 4.882248 ]...
-- WGS84

different with your data
{"tzid":"Africa/Abidjan"},"geometry":{"type":"Polygon","coordinates":[[[-5.440683,4.896553],[-5.303699,4.912035]

Can you tell me which way you used to produce the geojson file

Thanks.

request for a smaller version of the combined.json

For some applications it might not be feasible to have a 120MB .json file as data basis.
With certain simplifications and tricks it should theoretically be possible to compress the data to around 7MB (cf. timezonefinderL data, consisting of simplified tz_world data).

Without trying to go into those extremes the question is how reduce data size while still keeping an acceptable level of accuracy.

Next release

@evansiroky do you have any plan to releases? I need some fixes from master and I am interesting should wait release from you or build release by myself.

Better model disputed territories in Doklam area

Hello,
I noticed that there is a hole at 89.0714, 27.5442 for the 2018d release of timezones.shapefile.zip vs timezones-with-oceans.shapefile.zip. I assume that this is a disputed area based on some comments on openstreetmap.org; however, the hole exists in the timezones.shapefile.zip file but not the timezones-with-oceans.shapefile.zip file.

area at 89.0714, 27.5442 for timezones-with-oceans.shapefile.zip
image

versus area at 89.0714, 27.5442 for timezones.shapefile.zip
image

Question for timezone data format

Hey ,

Thank you for the amazing project, and we will have a maintained timezone service.
Just have a small question:

Is that possible to have timezone Abbreviation Name and code, like EST, Eastern Standard Time.

Thanks

Can not connect the open street server?

I Try to download the Time zone datasheet,but it shows the log;

waiting 4 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 8 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 16 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 32 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 64 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 128 seconds
{ message: 'Request failed: HTTP 400', statusCode: 400 }
Increasing overpass request gap
waiting 256 seconds

Validation error

I can't generate shape file because of validation errors.

load zones into memory
do validation
Validation error: America/Argentina/Rio_Gallegos intersects America/Punta_Arenas area: 0.08795638367089173
Validation error: Asia/Chita intersects Asia/Shanghai area: 0.0007959703837724789
Validation error: Asia/Manila intersects Asia/Shanghai area: 0.21316446632400018
Validation error: Asia/Ust-Nera intersects Asia/Yakutsk area: 2.9578565029596997
Validation error: Europe/Ljubljana intersects Europe/Zagreb area: 0.005178844060499668
done
error! Zone validation unsuccessful

Bad negative area for Africa/Lubumbashi

Firstly, this is great! I've been trying to figure out how to get territorial waters into the efele data set for a while, now I don't have to!

I downloaded the 2017a release, and I have some issues with the geoJson version of the data.

It looks like Africa/Lubumbashi has one negative polygon with only 4 points (3 if you don't count the dupe at the end), it also looks like it's area is 0. Also, the points go beyond 6 significant digits. Here is the json w/ a most of the points of the positive area removed for readability :

{
"type" : "Feature",
"properties" : {
"tzid" : "Africa/Lubumbashi"
},
"geometry" : {
"type" : "Polygon",
"coordinates" : [ [ [ 23.8940358, 4.8313928 ], .... a ton of points removed .... [ 23.8940358, 4.8313928 ] ], [ [ 24.4123887, -1.7179482 ], [ 24.440029068012333, -1.735314196891881 ], [ 24.440029068012333, -1.7353141968918806 ], [ 24.4123887, -1.7179482 ] ] ]
}
}

Timezone subset ?

Hi,

I only need a timezone extract subset (just Europe)
I modify timezone.json and remove all timezones I don't need

is it the good solution ?

Ocean time zones are incorrect

The ocean time zones, i.e. the ones named like ETC/Gmt+X or ETC/Gmt-X, seem to be inverted. That is, to the east of Greenwich the ETC/Gmt-X is used, whereas it must be ETC/Gmt+X. For more detailed and visual illustration of what I mean, see this issue: RomanIakovlev/timeshape#4 (comment). This is consistent in both shape files and geojson releases.

validation error ?

Thanks for your projet

I try to execute your script like recommanded in the doc
node --max-old-space-size=8192 index.js

but I got this error at validation step

validating zones
load zones into memory
do validation
Validation error: America/Argentina/Rio_Gallegos intersects America/Punta_Arenas area: 0.2113007296132473
Validation error: America/Argentina/Rio_Gallegos intersects America/Santiago area: 0.4102222149999935
Encountered TopologyException, retry with GeometryPrecisionReducer
Validation error: America/Punta_Arenas intersects America/Santiago area: 0.21130072961324728

I'm doing something wrong ?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.