Skip to content

feat: Add initial route planner support - #1098

Draft
MoritzWeber0 wants to merge 25 commits into
mainfrom
feat/automatic-routing
Draft

feat: Add initial route planner support#1098
MoritzWeber0 wants to merge 25 commits into
mainfrom
feat/automatic-routing

Conversation

@MoritzWeber0

@MoritzWeber0 MoritzWeber0 commented Jul 23, 2026

Copy link
Copy Markdown
Member

Initial version of a route planner. Routing is outsourced to Transitous, matching to train categories in the FIP guide happens via individual prioritized queries for each individual leg of the journey. Once a query matches, the information is used and processing is stopped.

What is covered so far?

  • Automatic cross-border recognition
  • RE18 train from Aachen to Maastricht with partial availability
  • National DB trains in Germany
  • All operators without FIP in Germany, Denmark, Portugal and Ireland

TODO:

  • Filter stations that are no in Europe
  • Add support for custom border point definition
  • Use our dropdown implementation
  • Add all operators without FIP
  • Add more train categories from countries
  • Add Verkehrsverbund exception for Germany

@github-actions

Copy link
Copy Markdown

Hi there! 👋

Thank you for your contribution to the FIP Guide! 🚀
We appreciate your effort in making rail staff travel information more accessible. 🚄

Checklist before merging:

  • Added a description to the Pull Request
  • Checked the License of new pictures (non-commercial use without attribution)
  • Modified content in English
  • Modified content in German
  • Modified content in French

@netlify

netlify Bot commented Jul 23, 2026

Copy link
Copy Markdown

Deploy Preview for fipguide ready!

Name Link
🔨 Latest commit 3ec49f8
🔍 Latest deploy log https://app.netlify.com/projects/fipguide/deploys/6a7224970b684e0008bd8b1d
😎 Deploy Preview https://deploy-preview-1098--fipguide.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

…experimental message

- Extract transitous_mapping from operator frontmatter to transitous.yaml
- Extract country operators_without_fip queries to transitous.yaml
- Simplify operators_without_fip to a plain string list
- Update templates to read from resource files
- Add experimental warning message to route planner page
- Add fromName/toName/fromStopId/toStopId to query evaluation context
- Detect Liège–Maastricht section (FIP accepted)
- Detect Maastricht–Aachen section (FIP not accepted)
- Fallback for mixed legs (FIP partially accepted)
- Match both Arriva (Sneltrein RE18) and DB Regio (de-DELFI_de:nrw:re18) variants
- Pre-resolve countries for all legs before rendering
- Add fromCountry/toCountry to evalQuery for country-based matching
- Add NS International ICE as FIP accepted on DB page for domestic journeys
- Set reservation_required false for national ICE trains
@lenderom

lenderom commented Aug 3, 2026

Copy link
Copy Markdown
Member

Mega gut :D
Gibt es zufällig die Möglichkeit die Reservierungspflicht aus den Metadaten auszulesen? Z.B. bei den Grenzüberschreitenden ICEs?

@MoritzWeber0

MoritzWeber0 commented Aug 3, 2026

Copy link
Copy Markdown
Member Author

Mega gut :D Gibt es zufällig die Möglichkeit die Reservierungspflicht aus den Metadaten auszulesen? Z.B. bei den Grenzüberschreitenden ICEs?

Soweit ich weiß, steht das leider nicht in den GTFS Daten :(
Deshalb müssen wir das wohl manuell anhand der Zeiten nachpflegen oder auf reservation partially required setzen.

@MoritzWeber0 MoritzWeber0 added the technical Technical issues, e.g. related to Hugo, HTML, CSS, deployment, etc. label Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

technical Technical issues, e.g. related to Hugo, HTML, CSS, deployment, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants