City of Nicosia, Cyprus found in Asia/Famagusta, not Asia/Nicosia
Closed this issue · 5 comments
I was using node-geo-tz to verify and update GeoNames timezone data, and stumbled on the odd result of Nicosia, Cyprus identified as being in Asia/Famagusta, not Asia/Nicosia.
const { find } = require('geo-tz');
console.log(find(35.1753, 33.3642));
Yields: ["Asia/Famagusta"]
Perhaps different coordinates for Nicosia would have worked better (it is close to the boundary between timezones), but these coordinates do appear like they should be safely inside the borders of the city.
Is this perhaps deliberate? The single city is split in its timezone history?
Okay, I guess this is more complicated than I would have expected. From Wikipedia:
From 30 October 2016 and onwards, Nicosia became the only capital city in the world that had two time zones, after the parliament of the de facto Turkish Republic of Northern Cyprus abolished standard time and decided that Northern Cyprus remains at UTC+03:00 year-round, following Turkey's example.[54][55] The following year, due to criticism from the Turkish Cypriot public in the north, the Turkish Cypriot government decided to go back to standard time, following the rest of Europe.
I guess the problem is deciding which side of the "green line" dividing Nicosia you're hoping to find when you look up latitude and longitude for Nicosia.
It's also very confusing to have one of the IANA timezones named after a city which itself has been split between timezones.
Considering what I've discovered looking into this further, I'm going to close this issue.
Once more, with feeling.
I do believe it is an open question of what side of the line to use or even if there should be an overlap of areas. In my original work, I gave all of the UN Buffer zone to Asia/Nicosia, but this was before when timezone-boundary-builder had overlapping zones.
As this is an artifact of the data from timezone-boundary-builder, any further discussion should happen in an issue in that repo.