gtfs-parquet
Parse GTFS feeds to/from Parquet via Polars — fast, compact, typed.
Features
- Parse GTFS from zip, directory, or URL
- Read NeTEx timetables (European profile) as the same GTFS tables
- Write to Parquet (zstd-compressed) or back to GTFS
- Strongly typed schemas with optimised dtypes (Float32 coords, Int16 sequences)
- Built on Polars — zero-copy reads, lazy evaluation ready
- Operations: calendar expansion, network analysis, route/stop/trip stats, timetable graphs, CSA connections
Installation
pip install gtfs-parquet
Quick start
from gtfs_parquet import parse_gtfs, write_parquet, read_parquet, write_gtfs
# Parse a GTFS zip (local path or URL)
feed = parse_gtfs("gtfs.zip")
# Write to Parquet — directory, .zip, or .tar (auto-detected by extension)
write_parquet(feed, "output/") # directory of .parquet files
write_parquet(feed, "output.zip") # zip archive (no extra compression)
write_parquet(feed, "output.tar") # tar archive (single file, no extra compression)
# Read back (same formats)
feed = read_parquet("output/")
feed = read_parquet("output.zip")
feed = read_parquet("output.tar")
# Convert back to GTFS zip
write_gtfs(feed, "roundtrip.zip")
Additional top-level helpers: parse_gtfs_dir, parse_gtfs_zip, write_gtfs_dir, and
to_parquet_bytes(feed), which returns {table_name: parquet_bytes} without writing to disk
(handy for uploading to object storage).
Large feeds
parse_gtfs_zip loads the whole feed in memory. For a national feed that takes several GB of RAM. When you only
need the Parquet files, convert_gtfs_zip streams the conversion instead:
from gtfs_parquet import convert_gtfs_zip
paths = convert_gtfs_zip("gtfs.zip", "output/") # {"stops": Path("output/stops.parquet"), ...}
Tables are converted one at a time, and large files are read in 16 MB blocks,
stored as temporary Parquet files in out_dir until the table is written.
Rows keep the order of the source file (sort=True sorts them). A file with an
unescaped quote (12" Street outside quotes) raises a ValueError instead of
being read whole.
| German national feed (298 MB zip, 40M stop times) | Peak RAM | Parquet |
|---|---|---|
parse_gtfs_zip + write_parquet |
10.7 GB | 320 MB |
convert_gtfs_zip, all 20 threads |
1.6 GB | 120 MB |
convert_gtfs_zip, POLARS_MAX_THREADS=4 |
0.5 GB | 120 MB |
Memory grows with the number of Polars threads, which defaults to the number of
CPU cores: set POLARS_MAX_THREADS before importing Polars to limit it.
NeTEx
Some operators publish their timetable only in NeTEx, the European XML format.
parse_netex reads it as GTFS tables, typed like a parsed GTFS feed; convert_netex writes them as Parquet,
the same files convert_gtfs_zip writes:
from gtfs_parquet import convert_netex, parse_netex
feed = parse_netex("IT-IT-TRENITALIA_L1.xml.gz") # .xml, .xml.gz, or a .zip of XML files
paths = convert_netex("IT-IT-TRENITALIA_L1.xml.gz", "output/")
| NeTEx | GTFS |
|---|---|
Operator / Authority |
agency |
StopPlace, its Quays |
stops: stations and their stops |
Line (TransportMode) |
routes (basic route_type) |
ServiceJourney (Name) |
trips (trip_short_name) |
TimetabledPassingTime |
stop_times, day offsets as times past 24:00 |
DayType, DayTypeAssignment, OperatingPeriod / UicOperatingPeriod |
calendar_dates, one service per set of dates |
ServiceLink geometry along the journey pattern |
shapes |
The file is read in one streaming pass. Trenitalia's timetable (302 MB of XML, 16,675 journeys) converts in about 10 seconds with 0.6 GB of RAM.
Compression
Parquet output is significantly smaller than the original GTFS zip thanks to zstd compression and optimised column types:
| Feed | GTFS zip | Parquet | Sorted (sort=True) |
|---|---|---|---|
| MBTA | 24.8 MB | 8.3 MB | 8.3 MB |
| FlixBus (EU) | 30.6 MB | 13.5 MB | 16.3 MB |
| Germany (national) | 298.2 MB | 119 MB | 320 MB |
Since 0.6.0, rows keep the order of the source files by default: feeds usually list related rows together, and sorting by id often breaks that up.
Feed object
Feed is a plain dataclass with one optional polars.DataFrame attribute per GTFS
file (e.g. feed.stops, feed.routes, feed.stop_times). Only files present
in the source feed are populated.
feed.tables() # dict of all non-None tables
feed.validate() # check required files and columns
Operations
All operations are standalone functions that take a Feed as their first argument.
Import from the ops submodules:
from gtfs_parquet.ops.calendar import (
get_dates, get_first_week, get_week, get_active_services,
subset_dates, compute_trip_activity, compute_busiest_date,
)
from gtfs_parquet.ops.trips import get_trips, compute_trip_stats
from gtfs_parquet.ops.routes import get_routes, build_route_timetable, compute_route_stats
from gtfs_parquet.ops.stops import (
get_stops, get_stop_times, get_start_and_end_times,
build_stop_timetable, compute_stop_activity, compute_stop_stats,
)
from gtfs_parquet.ops.network import describe, compute_network_stats
from gtfs_parquet.ops.restrict import restrict_to_routes, restrict_to_dates, restrict_to_trips
from gtfs_parquet.ops.clean import clean, clean_ids, drop_zombies
from gtfs_parquet.ops.graph import (
build_timetable_graph, get_service_day_counts, build_stop_lookup,
compute_segment_frequencies, compute_connections, served_stations,
)
dates = get_dates(feed)
week = get_first_week(feed)
services = get_active_services(feed, dates[0])
trip_stats = compute_trip_stats(feed)
route_stats = compute_route_stats(feed, [dates[0]], trip_stats)
stop_stats = compute_stop_stats(feed, [dates[0]])
# Timetable graph for routing
graph = build_timetable_graph(feed, services, hour_filter=(6, 22))
# CSA-compatible connections
connections = compute_connections(feed, services)
# Segment frequencies weighted by service days
day_counts = get_service_day_counts(feed, dates)
freqs = compute_segment_frequencies(feed, services, service_day_counts=day_counts)
The API is inspired by gtfs-kit, re-implemented on Polars for significantly better performance.
Performance vs gtfs-kit
Benchmarked on the STIB (Brussels) feed (~5.5 MB, ~9 000 trips):
| Operation | gtfs-kit (pandas) | gtfs-parquet (Polars) | Speedup |
|---|---|---|---|
| Load feed | 2.97 s | 0.40 s | 7x |
compute_trip_stats |
57.46 s | 0.05 s | 1149x |
compute_stop_stats |
9.67 s | 0.19 s | 51x |
compute_route_stats |
2.12 s | 0.08 s | 27x |
compute_busiest_date |
0.07 s | 0.06 s | 1x |
Peak process memory: 1020 MB (gtfs-kit) vs 744 MB (gtfs-parquet).
License
Metadata
Release files for gtfs-parquet 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gtfs_parquet-0.7.0.tar.gz | 56.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gtfs_parquet-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 101.1 kB
Release files / gtfs_parquet-0.7.0.tar.gz
| Download URL | gtfs_parquet-0.7.0.tar.gz |
|---|---|
| Size | 56.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae10b7919dde3f1b67342829feeb3575f2c621de53e3bc33a7b776731467ef60
|
|
BLAKE2b-256 checksum How to use checksums |
843866f36894ba1427dfdcfac7dd5d8bdc608509d367b62d4afc7a788bedda39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / gtfs_parquet-0.7.0-py3-none-any.whl
| Download URL | gtfs_parquet-0.7.0-py3-none-any.whl |
|---|---|
| Size | 44.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
517d74354c77c06babbdd7ffc498333652dcccba320082e5ee1ce7107d3f4ba7
|
|
BLAKE2b-256 checksum How to use checksums |
21d1995fc279b63a3da3c222cde8ba9a65e1e10cfcb339868f23aed1954df048
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log