Jannik Kissinger

Why? Then your data would suggest that this area is in two timezones... I don't think that makes sense.

But still a timezone has to be unique and therefore the surrounding timezone would need to be excluded from the surrounded tz. Otherwise algorithms don't really have a chance of...

For me the ideal solution would be to convince them to correct the data (for me layered polygons are mistakes), but I don't know realistic this is. By the way...

I really don't want to hijack this post, but since no one answered yet, here is my explanation: Like in other older issues (e.g. https://github.com/mattbornski/tzwhere/issues/8), probably the timezone data used...

Hm, that's not good... `timezone_at()` is the normal function for checking timezones (like `tz_NameAt`) with just a few optimizations. `closest_timezone_at()` is a real proximity algorithm (searching for the closest timezone,...

Thank you for the fast response. The documentation states: ``` positional arguments: poetry_args Poetry args, pass them after -- at the end of the command ``` running ` poeareq requirements.txt...

Thanks. `poeareq --ignore-errors existing.requirements.txt --poetry-args --lock` works with version `1.4.0`. The documentation however suggests using `poeareq --ignore-errors --poetry-args --lock existing.requirements.txt` ``` usage: poetry-add-requirements.txt [-h] [-D] [-I] [-i] [-n] [-p ...]...