derhuerst
commented
10 months ago I'm working for a small startup developing an public transport app and currently we are using v6.db.transport.rest within our app.
Glad my API is helping you achieve your mission!
Please donate, even if you're just a startup (like Stadt.Land.Netz has done it!), so that I can cover server costs and spend more time (that doesn't conflict with making a living) on the *.transport.rest APIs.
Since we are piloting our app in other European countries I wanted to ask if you are interested in setting up API's for those. We currently don't have the knowledge and resources to do that ourselves, but we might have the connections to provide transport data.
Depends on the kind of transport data source:
- If it's very similar to the other
*.transport.restAPIs, namely a HAFAS API endpoint, then yes! - If it's a different API, writing a (long-term-maintained) client for it is currently not aligned with my priorities, sorry. In this case, I suggest you to open an Issue in the kpublictransport, public-transport-enabler or bahn.expert repo, depending on the best fit.
- If you have static transit data (plus a realtime feed containing delays & cancellations, optionally), consider running a router. MOTIS, OTP, navitia are the well-known & powerful ones; Or get in touch with the people navitia SaaS offering and ask if they would like to run a routing instance for your data.
If/once there is a running HTTP API, I'm happy to let a *.tranport.rest sub-domain redirect to it and add it to the list at https://transport.rest/ !
Hello, I'm working for a small startup developing an public transport app and currently we are using v6.db.transport.rest within our app. Since we are piloting our app in other European countries I wanted to ask if you are interested in setting up API's for those. We currently don't have the knowledge and resources to do that ourselves, but we might have the connections to provide transport data. Let me know what you think, greetings Jakob