How to actually use Cook European Rail Timetable without losing your mind
Cook European Rail Timetable is desktop software for designing professional-looking railway posters. It predates everything on the internet by about fifteen years and doesn't pretend to be anything other than what it is. You feed it a timetable, it lays out stations and connections on a map-like grid, and you export a PDF. That's the entire pipeline. First you need a valid timetable source. The software accepts several formats: CSV, Excel, and its own proprietary Cook format. Most people end up writing a script to convert whatever data they have into the Cook format because the CSV import is brutally rigid. I spent a Tuesday morning trying to get a 400-row CSV of Eurostar connections to parse correctly only to discover the delimiter was hardcoded in a way that ignored any escaping rules. Ended up just writing a Python script that read the spreadsheet and spit out a .csvt file with the correct structure. Took twenty minutes once I understood the format. After the data loads, you set up your canvas. The software uses a coordinate system where the X axis represents distance along the route and the Y axis represents time. This is the critical part most beginners miss. The X coordinate isn't miles or kilometers in the traditional sense. It's a proportional spacing value. If you put two stations too far apart on the X axis, your connecting times look wrong even if the actual numbers are correct. I learned this the hard way when a client complained that the Amsterdam to Brussels leg looked like it took three hours instead of one forty-five. The timetable data was fine. The station coordinates were wrong.
Once your coordinates are set, you configure the display. Line colors, station dot sizes, the density of the time axis. There's a preview mode that renders a low-resolution version of your poster so you can check alignment before committing to a full export. Don't skip this. Exporting at full resolution takes roughly twenty seconds per page on a modern machine, and going back to fix a misaligned station label after export is a waste of time. The export options include PDF, PNG, and JPEG. PDF is the standard for print work. PNG works fine for screen sharing or internal documents. The software will let you export high-resolution images, but the file sizes grow fast. A single A1 poster at 300 DPI comes out around 45 megabytes. Fine if you have the disk space. Annoying if you're working over a slow connection and need to send a proof to a client.
The Cook European Rail Timetable download
The official distribution comes through the Cook website. There's no app store version, no cloud subscription. You buy a license, download the installer, and run it locally. The current version requires Windows 10 or later. There's a Linux compatibility layer workaround if you're determined, but the font rendering gets strange under Wine and I wouldn't recommend it for anything production-critical. The license model is perpetual with optional annual support contracts. The base software includes the standard timetable engine. There are add-on modules for specific regions or enhanced routing databases that you purchase separately. If you're only doing domestic UK routes, the base package covers everything. If you're building cross-border posters with connections between national rail systems, you'll want the expanded European dataset.
Get the Full Details
Things that will go wrong
The software has some real limitations. It doesn't handle dynamic scheduling well. If your timetable changes frequently, you're going to spend a lot of time repositioning elements. I've worked with operators who update their timetables monthly and found themselves spending three to four hours each cycle just retuning the layout. They eventually wrote a custom API integration that pulled directly from their scheduling database and auto-updated the Cook project file. Took about two weeks to build. Saved them probably ten hours a month going forward. The font handling is another weak spot. The software ships with a limited set of typefaces, and custom fonts don't always render consistently across machines. If you send a project file to a colleague and they have different fonts installed, your layout shifts. It's a minor issue until it suddenly costs you six hours reformatting an entire poster series right before a print deadline. There's also no built-in collaboration. Multiple people cannot work on the same project simultaneously. You can share project files over a network drive, but file locking is rudimentary and corruption has happened when two people edit the same file at the same time. I've seen it. It's not fun.
When Cook European Rail Timetable isn't the right call
If you need animated or interactive timetables, this software won't help you. It produces static images and PDFs. For web-based interactive journey planners, you'd be better off using something like OpenTripPlanner or building a custom solution with GTFS data. If your operation requires real-time updates pushed automatically to displayed timetables at stations, Cook doesn't integrate with those systems. It's a design tool, not a operations platform. For simple point-to-point connection tables without a visual map component, dedicated spreadsheet templates might do the job faster. The software shines when you need that classic illustrated railway poster look with route maps, colored lines, and station positions relative to each other. Everything else is either overkill or poorly suited. I keep a reference copy of the manual on my desktop even though I've used this software for years. That should tell you something about the UX. The interface is functional but dated, and the help documentation covers more edge cases than the menus make obvious. If you're starting fresh with it, budget extra time for learning the quirks rather than assuming it will behave like modern design software. It won't. But for what it does, it does it better than anything else I've found.
