About Vahrplan
Source code
GithubFAQ
Was the underlying concept of Vahrplan your idea?
No, it wasn't. The idea of splitting journeys originates from the project Tespace and is explained in the video linked below. The goal of Vahrplan is a symbiosis of Tespace and traditional journey planners.
The links I'm sharing from Vahrplan are too long. Can I shorten them?
Yes, you can. Activate short link generation in the settings.
How can I save my settings across browser sessions?
You can enable this in the settings.
What tools/libraries/frameworks does Vahrplan use?
Here is an (incomplete) list. You may inform yourself using the links below on how to support them.
Miscellaneous tools
- Programming language: TypeScript
- Meta framework: SvelteKit
- Containerization: Docker
- Linter: ESLint
- Code-Formatter: Prettier
Fahrplandaten
- Routing: Motis
- Raw data: Transitous
- Processing of Motis data: motis-fptf-client
- Processing of data from proprietary sources: hafas-client
Backend
Frontend
- Build tool: Vite
- Map library: Leaflet
- Map tiles: OpenStreetMap
Tools on a broader level
- Reverse proxy: nginx
- Analytics: Plausible (Communtiy Edition)
- Mail server: mailcow
How can I support Vahrplan?
The best support is spreading the word and letting your friends and family know about Vahrplan. If you want, you can also leave the projects I'm using (see above) or me a donation.
I found a bug. How can I report it?
I would be happy to learn about it. You can report a bug on GitHub:
Fahrplan starts with an F. Are you stupid?
Vahrplan stands for "Vollautomatische Hilfe für Routenplanung". Similarities with real words are coincidental.