transical
transical converts publically-available GTFS transit schedules into calendar events, bundled into iCalendar (.ics) files.
It’s designed to automate putting public transit schedules in your calendar. iCalendar files can be imported into Google Calendar, Apple Calendar, Evolution, Thunderbird, or just about any other calendar application.
installing
pipx is the preferred way to install transical. Unlike pip alone: it automatically isolates the package from your other Python packages, puts the package in your PATH, and installs manpages.
On pipx systems:
pipx install transical
Install shell autocompletions with transical --autocomplete.
do you really want to use pip?
pip is not recommended. On pip systems, for global installation:
pip install transical
usage
transical input.gtfs 2026-07-01/2026-08-01 output.ics
That's it! transical interactively walks you through picking a route, origin stop, and destination stop, before producing an output file with all the transit journeys that fall between the specified dates.
$ transical https://feeds.mta.maryland.gov/gtfs/marc 2026-07-01/2026-08-01 output.ics
No route was provided. Use arrow keys to select a route from the menu below.
🔄› 11704 · MARC · BRUNSWICK - WASHINGTON
11705 · MARC · PENN - WASHINGTON
11706 · MARC · CAMDEN - WASHINGTON
Selecting route. Hit </> to search.
You can directly import transical's .ics outputs in desktop applications (guides linked) like Google Calendar, Apple Calendar, Evolution, and Thunderbird.
You can also send outputs to yourself to import events on another device, with a tool like xdg-email:
xdg-email --attach output.ics recipient@example.com
more features
transical supports adding event reminders, and it even has its own filtering language to let you granularly choose journeys based on time of day and day of week.
transical has a noninteractive, script mode, too; it won't output anything it doesn't need to when called with --route and --termini flags already provided to it.
Read more about using transical or writing filter expressions. You can also find this documentation in transical's manpages, or see an overview with transical --help.
developing and building
This project uses uv.
Clone the repository with Git and use uv to install dependencies:
git clone git@github.com:solanto/transical.git
cd transical
uv sync
Run the program in development with uv run:
uv run transical
And build the package with uv build:
uv build
This not only packages the program itself, but also converts documentation in docs to manpages—installable via pipx—by way of a custom Pandoc pipeline. You can check out this pipeline in tools.
acknowledgements
komoot's free photon API for OpenStreetMap lets this project make station names prettier in your calendar. Thanks, komoot!
contributing
Feel free to ask questions or make suggestions here or at person@dandelion.computer. I'll do my best to collaborate with those who'd like to!
If you fork transical, be sure to change meta:ORG_DOMAIN to your own domain (which could even be something like your-username.github.io). transical uses this identifier to tell remote servers exactly whose code is requesting information, as well as to document exactly whose code made the events in produced iCalendar files.
license
GNU General Public License v3.0 or later. See license in LICENSE.md.
Metadata
Release files for transical 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| transical-0.3.tar.gz | 28.1 kB | Without provenance | Details for transical-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| transical-0.3-py3-none-any.whl | Python 3 | none | any | Details for transical-0.3-py3-none-any.whl |
Total release size: 57.6 kB
Release files / transical-0.3.tar.gz
| Download URL | transical-0.3.tar.gz |
|---|---|
| Size | 28.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ec052100b4a33f21fa8eee7d8a20259b507b7cd3691885257414088e7803121
|
|
BLAKE2b-256 checksum How to use checksums |
20b8612ac48951fbb05b6aeba88728240f0fd69c59ccd2d42428503afd776af9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"openSUSE Tumbleweed","version":"20260623","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / transical-0.3-py3-none-any.whl
| Download URL | transical-0.3-py3-none-any.whl |
|---|---|
| Size | 29.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cc9dda2bcd1099de9e25508a15ea696c0a2eb92f4d8476a90612ff5325a503f
|
|
BLAKE2b-256 checksum How to use checksums |
30c35d4a57c52d390ac271d89b84bfd2316c852124ed9cf75f7492c801e8b5a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"openSUSE Tumbleweed","version":"20260623","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for transical 0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.