Closed hansthompson closed 7 years ago
@juliuste and me created many JS modules related to public transport, each returning data in a very similar structure. To make these modules fully interoperable and have this structure written down somewhere, we created the Friendly Public Transport Format (FPTF).
One of the most important reasons we don't use plain GTFS is that it is very cumbersome to work with. FPTF aims to be very consumer-friendly.
It would be a perfectly valid use-case to store FPTF data encoded as protocol buffers and we might want to add .proto
definitions soon!
Also note that GTFS Realtime, with its nested structures, is a lot more convenient than normal GTFS (just plain CSV). As this format intends to also (and mainly?) cover static/planned data and trip planning, it makes sense to also have a less database-like format in these areas.
I think it would make sense to add Protocol Buffer definitions to this repo that match the spec.
From https://github.com/public-transport/friendly-public-transport-format/pull/20#issuecomment-339103222
My point is that you can't use
oneof
to assign two possible types to one name such asregion
. You have to useregion
®ionRef
.
repeated
doesn't work inside aoneof
declaration.
Hi. I like to play around with public transit data like I'm sure you do to.
I'm interested in how you would frame the argument of your format vs. a real-time protocol buffer.
https://developers.google.com/protocol-buffers/
There is a protocol buffer specifically for sending real time data for public transit.
https://developers.google.com/transit/gtfs-realtime/reference/