Proposal: Transit toolkit with initial NextBus content. #42

Closed
ddebrunner opened this Issue Apr 27, 2014 · 8 comments

Comments

Projects
None yet
5 participants
@ddebrunner
Member

ddebrunner commented Apr 27, 2014

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.

http://www.nextbus.com/xmlFeedDocs/NextBusXMLFeed.pdf

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.

@ddebrunner

This comment has been minimized.

Show comment
Hide comment
@ddebrunner

ddebrunner Apr 27, 2014

Member

If we wanted to broaden the concept, then maybe a transit toolkit, streamsx.transit and within it there would be namespaces for various data providers, e.g. com.ibm.streamsx.transit.nextbus.

I think I actually like the broader concept better.

Member

ddebrunner commented Apr 27, 2014

If we wanted to broaden the concept, then maybe a transit toolkit, streamsx.transit and within it there would be namespaces for various data providers, e.g. com.ibm.streamsx.transit.nextbus.

I think I actually like the broader concept better.

@ddebrunner ddebrunner changed the title from Proposal: NextBus toolkit to Proposal: Transit toolkit with initial NextBus content. Apr 27, 2014

@ddebrunner

This comment has been minimized.

Show comment
Hide comment
@ddebrunner

ddebrunner May 17, 2014

Member

If there are no objections I'll create this repository soon.

Member

ddebrunner commented May 17, 2014

If there are no objections I'll create this repository soon.

@hildrum

This comment has been minimized.

Show comment
Hide comment
@hildrum

hildrum May 17, 2014

Contributor

FWIW, I like the broader concept better.

Contributor

hildrum commented May 17, 2014

FWIW, I like the broader concept better.

@petenicholls

This comment has been minimized.

Show comment
Hide comment
@petenicholls

petenicholls May 21, 2014

Member

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.

Member

petenicholls commented May 21, 2014

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.

@ddebrunner

This comment has been minimized.

Show comment
Hide comment
@ddebrunner

ddebrunner May 21, 2014

Member

Other transit type available feeds are California road sensors, San Francisco parking.

I'd really like to separate out the reuseable components from a demo using those components, hence the request for a toolkit, rather than a demo.

Member

ddebrunner commented May 21, 2014

Other transit type available feeds are California road sensors, San Francisco parking.

I'd really like to separate out the reuseable components from a demo using those components, hence the request for a toolkit, rather than a demo.

@mikespicer

This comment has been minimized.

Show comment
Hide comment
@mikespicer

mikespicer May 22, 2014

Member

Could we separate this into generic Location Based Services and Transit specific interfaces for Next Bus etc.

Member

mikespicer commented May 22, 2014

Could we separate this into generic Location Based Services and Transit specific interfaces for Next Bus etc.

@ddebrunner

This comment has been minimized.

Show comment
Hide comment
@ddebrunner

ddebrunner May 22, 2014

Member

That makes sense, I was thinking of operators that would:

  • Detect if a vehicle has not moved in the last N seconds
  • Detect if two buses on the same route are within N meters of each other

but those concepts can be generalized beyond transport, to anything that has a location (people, servers, etc.)

Member

ddebrunner commented May 22, 2014

That makes sense, I was thinking of operators that would:

  • Detect if a vehicle has not moved in the last N seconds
  • Detect if two buses on the same route are within N meters of each other

but those concepts can be generalized beyond transport, to anything that has a location (people, servers, etc.)

@petenicholls

This comment has been minimized.

Show comment
Hide comment
@petenicholls

petenicholls May 23, 2014

Member

Creating the following:
streamsx.transportation -- toolkit for adaptors to access transit feeds as well as generic transportation based operators and functions

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.

Member

petenicholls commented May 23, 2014

Creating the following:
streamsx.transportation -- toolkit for adaptors to access transit feeds as well as generic transportation based operators and functions

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.

@chanskw chanskw reopened this Oct 20, 2015

@chanskw chanskw closed this Oct 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment