Evan Siroky
Evan Siroky
I'm aware that there have been releases to the timezone database and that the current timezone-boundary-builder's release is not up-to-date. The release of `2021b` caused an immense amount of controversy...
> I will recommend to the stake holders in the project I'm working on that we update our location data every time there is a release of timezone-boundary-builder rather than...
I believe this use case of "what is the historical timezone identifier of a particular GPS coordinate" doesn't have a good example of why it is needed to be answered...
There currently aren't plans to support React Native, but I'm happy to review and merge PRs that would enable React Native support.
> We are using nx workspace for running the app and building it . Building will transpile typeScript file into JavaScript (under the hood, its what tsc does)... This is...
See https://github.com/mbostock/shapefile/issues/51.
I'm adding a reference to the [tz mailing list discussion](https://mm.icann.org/pipermail/tz/2022-July/031635.html) about this. In the mailing list discussion, I agree with the [comment made by Chris Walton](https://mm.icann.org/pipermail/tz/2022-July/031636.html) that I am skeptical...
I've sent a message to the OSM user [Arctic gnome](https://www.openstreetmap.org/user/Arctic%20gnome) to request their input. I believe they have made most of these edits to the `America/Nipigon` and `America/Toronto` timezones.
We oughta remove the code for the signs stuff if that won't be maintained anymore.
We still need to merge to master to trigger semantic-release...