Timezonefinder

------------------

breaking changes:

* new dependency: using `h3 <https://uber.github.io/h3-py/intro.html>`__ for indexing the timezone polygons to check ("shortcuts) instead of the previous own indexing implementation. technical details: storing all 41,162 hex cells at resolution 3 and the corresponding timezone polygons which appear in them in the ``shortcuts.bin`` (~500 KB).
* removed ``.closest_timezone_at()``: with the current data set with ocean zones in use, any point is included in some zone. it is therefore not meaningful to search for the closest boundary! Also the timezone polygons do NOT follow the shorelines. This makes the results of ``closest_timezone_at()`` somewhat less expressive. Maintaining the non-trivial distance computation algorithms is not really at the core responsibility of this package.
* officially only supporting ``python>=3.7`` (removed official support for ``python3.6``, since the ``numpy`` dependency did so)
* removed ``v`` from the github release/version tags

internals:

* updated the data to `2021c <https://github.com/evansiroky/timezone-boundary-builder/releases/tag/2021c>`__. please note that timezone polygons might be overlapping (cf. e.g. `timezone-boundary-builder/issue/105 <https://github.com/evansiroky/timezone-boundary-builder/issues/105>`__) and that hence a query coordinate can actually match multiple time zones. ``timezonefinder`` does currently NOT support such multiplicity and will always only return the first found match.
* shortcuts: sorting according to size of polygons (amount of coordinates) instead of the count of zone ids. useful as optimisation: smaller polygons will be checked first and can hence be "ruled-out" faster
* "most common": now meaning the zone with the largest polygons in the shortcut (last in the shortcut sorting). please note that this does not necessarily mean the most area in the shortcut is covered by this zone. the polygon size is just an easier to compute heuristic.
* officially supporting python versions >=3.7,<3.11 (like ``numba``)
* using poetry for dependency management
* using GitHub actions for CI instead of travis
* some minor typing improvements
* pre-commit hook improvements

In case you have criticism or feedback please reach out by creating an issue, discussion or PR on GitHub.

------------------

* added function ``unique_timezone_at()`` (based on the request in issue 112). Allows querying for the unique zone within the corresponding shortcut.

------------------

* BUGFIX: get_geometry() now also works for the last zone
* add get_geometry() tests
* black code style
* pre-commit checks

------------------

* update the command line interface. the package can now directly be called with ``timezonefinder``
* added the new query functions to the command line interface (to match the online API)

------------------

MAJOR CHANGES:

Due to multiple user requests the ocean timezones ("Etc/GMT+-XX") are now included in the data files per default. fix 88. Since ocean timezones span the whole globe, now every point lies within a timezone!

API changes:
* added ``timezone_at_land()``: replaces the previous ``timezone_at()`` and returns ``None`` in case of a matched ocean timezone.

* deprecated ``certain_timezone_at()``. only meaningful in the case of timezone data WITHOUT oceans. Has equal results as ``timezone_at()``, but is more expensive to use.
* also looking a single closest timezone boundary with ``closest_timezone_at()`` is not really meaningful, since every point lies within a zone!
* refactored tests. new test cases for ocean timezones

------------------

BUGFIX: handle output destination for data files correctly in file_converter.py (FIX 107)

* updated the data to `2020d <https://github.com/evansiroky/timezone-boundary-builder/releases/tag/2020d>`__
* disable a test case for an Uzbek enclave. tests fail at this coordinate, possibly a bug. issue filed here: https://github.com/evansiroky/timezone-boundary-builder/issues/94
* update parse_data.sh script to properly handle new data format