Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: Transit toolkit with initial NextBus content. #42
NextBus provides a public api with live position and meta data for various transit systems in the US, e.g. positional data for buses in the San Francisco Muni system.
A NextBus toolkit would provide composite operators, types and applications to pull live data from NextBus.
I think this could be a good live data set to build sample applications for Streams, demonstrating use of various open source and product toolkits. E.g. initially it would use HTTPXMLContent from streamsx.inet, XMLParse from SPL standard toolkit, the geospatial toolkit and time functionality from streamsx.datetime. Subsequent improvements might use the timeseries toolkit.
Should this be streamsx.demo.nextbus?
Not sure about a generic transit repository at this point or what other transit based data feeds there are.
Vote for streamsx.demo.nextbus since initially this is likely to be seeded with some of the demo and tutorial apps that already exist. If over time there becomes more transit based data feeds we can create a transit based toolkit.
That makes sense, I was thinking of operators that would:
but those concepts can be generalized beyond transport, to anything that has a location (people, servers, etc.)
Creating the following:
streamsx.locationbasedservices -- toolkit for generic location based services
Closing this issue. Conversation about operators etc... should occur in the repositories.
Set up web pages and iniitial committers.