Binary data distribution for tzf and tzf-rs.

If you have any questions or suggestions, please open an issue in the upstream tzf repository.

You can view the file in tzf-bin-viewer once you download it.

The underlying data structures are defined in the tzinfo.proto.

• main — source code, workflows, and embed.go template; never tagged
• data — latest generated binaries as an orphan commit (force-pushed on each update); the tip commit is what gets tagged for releases

Historical data is accessible via tags — each tag points to a single orphan commit on data that contains the binary files for that timezone-boundary-builder version.

Import a tagged version (tags point to data branch commits containing the embedded files):

import tzfdist "github.com/ringsaturn/tzf-dist"

// tzfdist.CompressTopoData        — full precision CompressedTopoTimezones
// tzfdist.TopologyCompressTopoData — lite CompressedTopoTimezones
// tzfdist.PreindexData             — tile pre-index

[dependencies]
tzf-dist = "..."

If you need full data precision, use the full feature flag with git based dependency(full data is not available on crates.io due to size constraints):

[dependencies]
tzf-dist = { git = "https://github.com/ringsaturn/tzf-dist", tag = "...", features = ["full"], default-features = false}

Binary files are attached to each GitHub Release as assets, built from the corresponding timezone-boundary-builder release.

Tags are created manually from the data branch tip after automated data generation. Creating a GitHub Release from a tag triggers asset upload via the release workflow.

Code is licensed under the MIT License. See LICENSE for details.

Data is licensed under ODbL. See DATA_LICENSE for details. Same with the timezone-boundary-builder.