jannikmi/timezonefinder

AI Summary: This issue investigates a discrepancy where a performance report shows Numba JIT as available and active on Python 3.13.11, even though Numba's official documentation states it only supports Python up to version 3.12. The goal is to understand how this seemingly impossible configuration is being reported.

AI Summary: This issue proposes a documentation update for the 'Alternative python packages' section. It involves moving this section into a standalone .rst file. Additionally, it suggests adding a point to the `tzfpy` comparison, highlighting that `tzfpy` uses the full set of over 440 timezones, which is a key distinction for comprehensive localization needs.

AI Summary: The task is to investigate why the timezonefinder library (version 7.0.0) lacks a platform-independent wheel for ARM architectures, leading to installation and runtime issues on ARM-based systems. The solution involves either creating a platform-independent wheel or determining why the existing build process fails to produce one, and then releasing a new version of the library that addresses this compatibility problem.

AI Summary: Optimize the `timezonefinder` Python package by modifying how NumPy arrays are created when reading polygon binary files. Instead of creating them repeatedly, the task involves constructing and reusing the arrays in memory to improve performance.

AI Summary: Implement proper smoke tests for the `timezonefinder` Python package that run against built distributions (wheels and sdists) within the GitHub Actions workflow. This involves investigating and resolving inconsistencies in how sdists and wheels are built to ensure that necessary files (like `hole_registry.json`) are included, and then creating tests that verify the functionality of the built packages.

AI Summary: The task is to debug a `ModuleNotFoundError` for the `timezonefinder` Python package. The error occurs when importing `timezonefinder.flatbuf`, indicating a problem with the installation or build process of the package's FlatBuffers component. The solution likely involves verifying the installation of the `flatbuffers` dependency and potentially rebuilding the package or its FlatBuffers-related parts.

AI Summary: Enhance the `timezonefinder` Python package by adding a script that generates a markdown file containing statistics (size, index properties, etc.) about the data used. This report should be generated by redirecting the standard output of `file_converter.py` and added to version control.

AI Summary: This task involves modifying the `timezonefinder` Python package to provide a globally accessible, thread-safe instance of the `TimezoneFinder` class. This requires adding a global instance, ensuring thread safety, updating existing functions to use the global instance, writing tests, and updating the documentation to reflect the changes while maintaining backward compatibility.

AI Summary: Optimize the `timezonefinder` Python package to improve performance by first checking bounding boxes to quickly eliminate potential timezone polygons before performing more expensive point-in-polygon (PIP) tests. The goal is to return the timezone as soon as only one possibility remains after bounding box checks.

AI Summary: The task involves removing support for Python 3.8 in the `timezonefinder` package due to its end-of-life. This includes updating the testing environments (tox, GitHub Actions), removing Python 3.8 from the build matrix, and adding support for newer Python versions with corresponding tests.

AI Summary: Create an 'examples' folder containing Python scripts demonstrating the usage of the timezonefinder package, based on examples from the documentation. These scripts should then be imported and tested to ensure they run without errors.

AI Summary: Investigate and implement data compression techniques for the timezone data within the `timezonefinder` Python package to reduce its disk footprint (currently >60MB). This involves exploring options like using 16-bit integers instead of 32-bit integers, analyzing the impact on precision (especially near the equator), and balancing file size reduction with maintaining the library's accuracy and speed. The goal is to optimize the package size without sacrificing its unique selling point of high precision.

AI Summary: Update the `timezonefinder` project's README to prominently mention `tzfpy` as a faster, more memory-efficient alternative, acknowledging its slightly reduced border accuracy. This involves adding a section or paragraph clearly comparing the two packages and guiding users to choose the best option based on their needs (speed vs. accuracy).

AI Summary: The task involves researching alternative raycasting algorithms and libraries for a Python package that determines time zones based on coordinates. This includes evaluating the feasibility of externalizing the raycasting functionality into a separate Python library, considering the current implementation's use of a custom C extension and the alternative's reliance on a Rust-based geometry library. The goal is to improve the raycasting algorithm used for timezone determination.

AI Summary: Update the project's README to clearly state the data source (https://github.com/evansiroky/timezone-boundary-builder) and its license, including information about the data size (~63MB).

AI Summary: Investigate alternative binary file formats, such as BISON, to replace the custom format used in the timezonefinder Python package. The goal is to improve maintainability without sacrificing disk space or performance. This involves researching suitable alternatives, evaluating their support for necessary data structures, stability, file size, and read/seek performance.