
STARTER PACKS / MOBILITY
TRANSIT SCHEDULE PUBLISHING
STARTER PACK
60 DAYS - 4.900€
GTFS AND NeTEx GENERATION FROM YOUR SCHEDULING TOOLS - FOR ONE OPERATOR.

problem
YOU HAVE A SCHEDULING SYSTEM AND ROUTES THAT WORK, BUT GENERATING GTFS OR NeTEx FOR THE NATIONAL ACCESS POINT IS A QUARTERLY MANUAL EXPORT THAT NEVER QUITE MATCHES YOUR LIVE TIMETABLE. THE ISSUE IS NOT MORE SCHEDULING SOFTWARE - IT'S AUTOMATING WHAT YOU ALREADY HAVE INTO STANDARD FEEDS.
GTFS GENERATION IS A
QUARTERLY MANUAL
EXPORT
Someone in operations spends two days every quarter producing the file.
NETEX COMPLIANCE IS
UNCERTAIN
The national access point keeps flagging issues you don't have time to fix.
STOP NAMES AREN'T
MULTI-LINGUAL
Tourist apps show only the local language. Cross-border travellers are confused.
REAL-TIME AND
SCHEDULE DRIFT APART
Your published schedule is from October. Operations changed routes in February.
OPERATORS DON'T NEED ANOTHER SCHEDULER. THEY NEED THE FEEDS THEY ALREADY OWE TO STAY CURRENT, AUTOMATICALLY.
solution
HOW WE APPROACH THIS
(simple and a bit refreshing)
We connect to your existing scheduling system, generate GTFS and NeTEx automatically, validate against the standards, and submit to the national access point on the cadence required.
We connect it using:
- ETSI NGSI-LD Smart Data Models for public transport schedules.
- The Vela Context Data Hub.
- Your existing scheduling tool - Hastus, IVU.timetable, Trapeze FX, custom databases, even spreadsheets.
No replacement of your scheduling tool. No new operations process. No 'enterprise digitalisation committee'.
Once the connection is built → GTFS and NeTEx generate continuously, validate automatically, and submit to the NAP without manual intervention.
Then we expand - adding multi-language stop names, accessibility data, and tariff information.
What You Get (in 60 Days)
- Automated GTFS Generation - daily generation. Always current with your scheduling system.
- NeTEx generation (where applicable)- National Access Point compliant. Cross-border data sharing supported.
- Continuous validation - canonical GTFS Validator runs on every change. Issues flagged before publish.
- NAP submission - automated submission to your relevant national mobility data point.
- Multi-language stop names - configurable per language. Tourist-facing apps show the right name.
- NGSI-LD context graph - your schedule data, queryable on the Vela Context Hub.
THIS IS YOUR SCHEDULE-PUBLISHING INFRASTRUCTURE, NOT A PILOT.
Who This Is For
Transit operators that:
- Run scheduled service (bus, tram, rail, trolleybus, ferry).
- Have a scheduling system that produces accurate timetables.
- Need NAP compliance but don't have a dedicated team for it.
- Want multi-language and accessibility improvements without rebuilding.
Need real-time on top of schedule? Add Vela Pulse subscription - same data, RT layer.
We start with the Starter Pack (one operator, existing scheduling system, GTFS + optional NeTEx) because this gives you 80% of value in 60 days with minimal cost and no risk.
pricing
STARTER PACK
4.900€
one time setup
(20 working hours included for consulting and developing)
-
- Fully managed shared hosted Vela Context Data Hub instance
-
The essentials
Metadata and data viewer / editor
Searchable metadata and data portal
Authentication and authorization
Scheduling-system connector (Hastus, IVU.timetable, Trapeze FX, custom)
Database
NGSI-LD Context Broker
Operator / route / line / stop / trip hierarchy
Semantic model for public transport schedules
GTFS Static generator with continuous validation
NeTEx generator (where applicable)
Multi-language stop name management
NAP submission automation
Public schedule lookup widget
Data ownership
API for database access and direct Context broker access
Installation
-
Support
E-mail support (Business hours)
(OPTIONAL) 12 MONTH SUPPORT EXTENSION
990€ per month
12-month support extension,
hosting & support, billed monthly after 90 days period
(5 working hours per month included for consulting and developing)
Quarterly review session
New routes / lines / stops onboarded
NAP-compliance monitoring
Support
E-mail support
Want the architecture walkthrough?
We’ll show:
- How your scheduling tool generates compliant feeds automatically.
- How NAP submission actually works.
- How multi-language stop names propagate to journey planners.
VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR MOBILITY · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES