1<!DOCTYPE html> 2<html lang="en"> 3 <head> 4 <meta charset="utf-8" /> 5 <meta name="viewport" content="width=device-width, initial-scale=1" /> 6 <meta name="color-scheme" content="light dark" /> 7 <title>OTP Summit 2026 Bern</title> 8 <meta property="og:description" content="OTP Summit 2026 Bern" /> 9 10 <!-- Pico.css --> 11 <link 12 rel="stylesheet" 13 href="https://cdn.jsdelivr.net/npm/@picocss/[email protected]/css/pico.min.css" 14 /> 15 <style> 16 main p img { 17 max-width: 330px; 18 padding: 25px; 19 display: inline; 20 } 21 22 header { 23 position: relative; 24 margin-bottom: 40px; 25 } 26 27 header .logo { 28 position: absolute; 29 bottom: 5px; 30 right: 5px; 31 width: 120px; 32 } 33 34 </style> 35 </head> 36 37 <body> 38 <main class="container"> 39 40 <header style="position: relative;"> 41 <img class="logo" src="img/otp-logo.svg" > 42 <img src="img/header.jpg" alt="Helsinki"> 43 </header> 44 45 46 <h1>OTP Summit 2026 Bern</h1> 47 <h3>5th-9th of October 2026</h3> 48 <p>The worldwide OpenTripPlanner community is meeting in Bern, 49 Switzerland, from 5â9 October 2026, as part of the <a 50 href="https://open-transport.org/">Open Transport Community 51 Conference (OTCC)</a>. Expect talks and discussions on all items 52 for OTP, plenty of chances to socialise, and â new this year â a 53 joint (un)program with the Open Transport Community.</p> 54 <h2 id="schedule">Schedule</h2> 55 <p>The main conference on Thursday and Friday is open to anyone 56 interested in OTP, from newcomers to experienced users â this is 57 the best entry point if your organization is exploring OTP for the 58 first time.</p> 59 <p>The MondayâWednesday sessions require prior OTP knowledge and 60 involvement to get the most out of them. They include a dedicated 61 OTP Product Day on Wednesday for companies actively contributing 62 to OTP development.</p> 63 <h3 id="monday">Monday</h3> 64 <p>OTP-only program at a different venue, aimed at developers with 65 OTP expertise.</p> 66 <p>There are only 12 spots available for developers. Please signup 67 by email to Thomas Gran, Entur. OTP Core Developers will be given 68 priority. Lunch is served at the restaurant, but each participant 69 will need to pay for their own meal.</p> 70 <p>Location:</p> 71 <p>Kursaal Bern AG<br /> 72 Swissôtel Kursaal<br /> 73 Bern</p> 74 <h3 id="tuesday-wednesday-otcc-hackdays">Tuesday-Wednesday: OTCC 75 Hackdays</h3> 76 <p>These sessions are aimed at developers who are already very 77 familiar with OTP development and to interact and collaborate with 78 the OTCC community.</p> 79 <p>Location:</p> 80 <p><strong>Trüsselstrasse 2</strong><br /> 81 3014 Bern<br /> 82 Switzerland</p> 83 <h3 id="wednesday-product-day">Wednesday: Product day</h3> 84 <p>These sessions are aimed at people with product 85 responsibilities, and has an agenda that is different from the 86 other sessions during the OTCC Hackdays, even if itâs at the same 87 location.</p> 88 <p>Location:</p> 89 <p><strong>Trüsselstrasse 2</strong><br /> 90 3014 Bern<br /> 91 Switzerland</p> 92 <h3 id="thursday-friday-otcc-unconference">Thursday-Friday: OTCC 93 (Un)conference</h3> 94 <p>This year, we co-host with OTCC to strengthen collaboration in 95 open-source mobility. At this conference, many members of the OTP 96 community will be present. Here you will be able to learn about 97 the product, usage, future plans, and see if OTP may be the 98 solution fitting your needs, alongside attracting new designers 99 and developers to our community.</p> 100 <p>There will be ample opportunity to socialise.</p> 101 <p>Location:</p> 102 <p><strong>SBB Headquarters</strong><br /> 103 Hilfikerstrasse 1<br /> 104 3014 Bern<br /> 105 Switzerland</p> 106 <h2 id="registration">Registration</h2> 107 <p>Registration for Tuesday-Friday is done through <a
108 href="https://pretix.eu/fossgis/open-transport-2026/">the OTCC 109 registration form</a>. If you are interested in joining the 110 Monday, send us a message. Tickets can be free for OTP-affiliated 111 attendees; OTP is sponsoring a block of free places. Buy a ticket 112 to support Open Transport Community.</p> 113 <h2 id="contact">Contact</h2> 114 <p>Should you have any questions, please email <a 115 href="mailto:[email protected]">[email protected]</a> or 116 <a 117 href="mailto:[email protected]">[email protected]</a> 118 or join the <a 119 href="https://gitter.im/opentripplanner/OpenTripPlanner">Gitter 120 chat</a>.</p> 121 <h2 id="partners">Partners</h2> 122 <p><img src="img/fintraffic.png" alt="Fintraffic" /> <img 123 src="img/hsl.png" alt="HSL" /> <img src="img/entur.png" 124 alt="Entur" /> <img src="img/skanetrafiken.png" 125 alt="Skanetrafiken" /></p> 126 </main> 127 </body> 128</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.