Clever Devices feed

[Kari]

We are working with Clever Devices to bring CCT (Cobb Community Transit) realtime feed into OneBusAway for the Atlanta region. We are talking with Clever Devices as to what is required from their side, in terms of the realtime data fields. So far their feed looks to be formatted in a different way than other feeds we have consumed.  Has anyone worked with a Clever Devices feed before? Is there a repeater out there that we could make use of?  Also, to include a new agency/feed into OBA's GTFS-realtime, what is the minimum set of data required, so that we can consume it into OBA.

Thanks and Regards,

Tushar Humbe

[Kurt Raschke]

Are you working with the Clever Bus Time API (such as is described at http://www.transitchicago.com/asset.aspx?AssetId=2917)? I have looked into writing a transformer to turn that API into GTFS-realtime before, but it would be a pain because most of the data we would need is not included or would take some effort to derive.

In short, for a minimal GTFS-realtime TripUpdate feed, you need the trip ID as it appears in the GTFS feed, and the trip's schedule deviation. If the data are coming from a system which is actually able to generate distinct predictions for upcoming stops instead of just applying the schedule deviation, then those (stop ID, time) pairs can also be included in the TripUpdate feed.  Note that when I refer to 'time' at a specific stop, that can either be the schedule deviation of the trip at that stop (a relative value) or the actual time when the trip will arrive/depart (an absolute value).  The vehicle ID is also helpful to have, particularly if you are also including a VehiclePosition feed.

For a VehiclePosition feed, the minimal elements are the vehicle ID and the vehicle's latitude and longitude. It is also helpful to include the trip ID of the trip that the vehicle is serving in the VehiclePosition feed; this facilitates linking entities from the VehiclePosition and TripUpdate feeds.

-Kurt

Sent from my iPad

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-devel...@googlegroups.com.
To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

[Tushar Humbe]

We are using the following APIs from Clever Devices: 

http://gocct.cobbcounty.org/packet/json/vehicle?routes=20&lastVehicleHttpRequestTime=1370013370839

http://gocct.cobbcounty.org/packet/json/vehicle 

Is there a way to "add on to" the GTFS realtime format to include frequency based realtime updates? For example, can we get rid of trip IDs for a particular agency, and just have a frequency based update. (Next Bus in 5min, 25 min, etc.). But at the same time, do not disturb the Agencies which use trip IDs in their GTFS feed. 

Thanks and Regards,

Tushar Humbe

[Sean Barbeau]

Tushar, Kari, and Kurt,
We're dealing with this same issue in Pinellas County with a Clever Devices feed there:
http://www.psta.net/developers/RidePSTA%20API%20Guide.pdf

From talking with Clever Devices, there is apparently a "tripID" field in the "3.7 Predictions" API, but its a "restricted" element that is not included in the results by default, and you must request that your agency enable this per your API key.  TripID is also only available in newer versions of Clever Device's system, so I don't know if it would be available at CCT.

Assuming that trip_ids are provided (we haven't tested this yet), there are two remaining issues that I see:

1. The limitation on only returning 10 records at a time (so if there are 100 vehicles on the road, you need to query the API 10 times, each time specifying which stopIDs or vehicleIDs to return, to construct a single GTFS-realtime Trip Update dataset)
2. The lack of matching IDS with a GTFS dataset (trip_ids, stop_ids, route_ids)
   

Assuming we can get a mapping between GTFS IDs and the Clever Devices IDs, we could implement workarounds for the above two issues, but it would be far easier to implement a GTFS-realtime feed if Clever Devices simply allowed returning a full dataset in a single request, and provided IDs that match GTFS IDs.  We're going to follow up with Clever Devices about this, and I'd like to touch base with you Tushar before I do.  Could you please contact me offline at bar...@cutr.usf.edu?

To answer your other question - per the GTFS-realtime spec, you can include an absolute "time" instead of a delay in the StopTimeEvent:
https://developers.google.com/transit/gtfs-realtime/reference#StopTimeEvent

In frequency-based systems, this is actually the right way to provide real-time info (vs. using "delay") (see https://developers.google.com/transit/gtfs-realtime/trip-updates).  If you don't have trip_ids, you can specify a route_id instead in TripDescriptor (https://developers.google.com/transit/gtfs-realtime/reference#StopTimeEvent), although I don't know if OneBusAway will match GTFS-realtime updates without trip_ids.  Additionally, this provides ambiguous data in the case where multiple directions of the same route arrive at the same stop (e.g., transit centers).

Sean

On Wednesday, October 30, 2013 2:19:50 PM UTC-4, Tushar Humbe wrote:

We are using the following APIs from Clever Devices: 

http://gocct.cobbcounty.org/packet/json/vehicle?routes=20&lastVehicleHttpRequestTime=1370013370839

http://gocct.cobbcounty.org/packet/json/vehicle 

Is there a way to "add on to" the GTFS realtime format to include frequency based realtime updates? For example, can we get rid of trip IDs for a particular agency, and just have a frequency based update. (Next Bus in 5min, 25 min, etc.). But at the same time, do not disturb the Agencies which use trip IDs in their GTFS feed. 

Thanks and Regards,

Tushar Humbe

On Tue, Oct 29, 2013 at 12:52 PM, Kurt Raschke <ku...@kurtraschke.com> wrote:

Are you working with the Clever Bus Time API (such as is described at http://www.transitchicago.com/asset.aspx?AssetId=2917)? I have looked into writing a transformer to turn that API into GTFS-realtime before, but it would be a pain because most of the data we would need is not included or would take some effort to derive.

In short, for a minimal GTFS-realtime TripUpdate feed, you need the trip ID as it appears in the GTFS feed, and the trip's schedule deviation. If the data are coming from a system which is actually able to generate distinct predictions for upcoming stops instead of just applying the schedule deviation, then those (stop ID, time) pairs can also be included in the TripUpdate feed.  Note that when I refer to 'time' at a specific stop, that can either be the schedule deviation of the trip at that stop (a relative value) or the actual time when the trip will arrive/depart (an absolute value).  The vehicle ID is also helpful to have, particularly if you are also including a VehiclePosition feed.

For a VehiclePosition feed, the minimal elements are the vehicle ID and the vehicle's latitude and longitude. It is also helpful to include the trip ID of the trip that the vehicle is serving in the VehiclePosition feed; this facilitates linking entities from the VehiclePosition and TripUpdate feeds.

-Kurt

Sent from my iPad

On Oct 29, 2013, at 11:28, "Kari" <kariew...@irgmail.com> wrote:

We are working with Clever Devices to bring CCT (Cobb Community Transit) realtime feed into OneBusAway for the Atlanta region. We are talking with Clever Devices as to what is required from their side, in terms of the realtime data fields. So far their feed looks to be formatted in a different way than other feeds we have consumed.  Has anyone worked with a Clever Devices feed before? Is there a repeater out there that we could make use of?  Also, to include a new agency/feed into OBA's GTFS-realtime, what is the minimum set of data required, so that we can consume it into OBA.

Thanks and Regards,

Tushar Humbe

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-developers+unsub...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-developers+unsub...@googlegroups.com.

[Aaron Antrim]

Quick follow up on this 2-year-old thread.

Was the real-time information from the Clever Devices API successfully incorporated in OneBusAway?

I do see Cobb Community Transit under "supported agencies" (http://atlanta.onebusaway.org/where/standard/agencies.action) so I assume the answer is yes.

Does this mean there is now a data converter available for the Clever Devices API? I do not see one listed at:

https://github.com/OneBusAway/onebusaway-application-modules/wiki/Real-Time-Data-Configuration-Guide#data-processing-tools

[Sean Barbeau]

To close the loop on this thread (sorry for the very delayed response!), in Pinellas County we didn't end up building our own converter.  PSTA acquired a GTFS-realtime feed directly from Clever Devices instead.

Kari or Kurt,

Do you know if a Clever Devices API => GTFS-realtime feed converter exists?  To my knowledge none exists (there aren't any listed in the awesome-transit page, which is where I've been cataloging tools).

Sean

[Watkins, Kari E]

I don’t think it ever happened.  Landon would know better though.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-devel...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-devel...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-devel...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.

Visit this group at https://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/d/optout.

[Nathan Selikoff]

Here in Orlando, LYNX is in the process of rolling out Clever Devices to the fleet, so I'm also interested in utilizing a Clever Devices => GTFS-Realtime feed converter if it exists (or creating/helping create one if it doesn't).

-Nathan

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-developers+unsub...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-developers+unsub...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at http://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-developers+unsub...@googlegroups.com.

[Tim Cooper]

There doesn't seem to be a Clever Devices to Google Realtime other than a module that Clever offers.  I'm currently trying to create a realtime feed in .Net.  I have access to the Clever database along with the API.  

Has LYNX created a solution yet?

Tim

[Nathan Selikoff]

Hi Tim,

I'm not actually with LYNX, but from what I know they are going in a different direction. I was hoping to try creating a converter based on the API, but database access would probably make it much easier. If you end up creating a converter please let us know.

--
You received this message because you are subscribed to a topic in the Google Groups "onebusaway-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/onebusaway-developers/-AIMyaW9pLo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to onebusaway-devel...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at https://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/d/optout.

--

Nathan Selikoff

@nselikoff

407-319-5198

Consulting (awakeningstudios.com)

Art (nathanselikoff.com)

[Tim Cooper]

Thanks for the quick reply!  If I get something together, I'll be sure to share.

On Wednesday, December 14, 2016 at 12:02:53 PM UTC-5, Nathan Selikoff wrote:

Hi Tim,

I'm not actually with LYNX, but from what I know they are going in a different direction. I was hoping to try creating a converter based on the API, but database access would probably make it much easier. If you end up creating a converter please let us know.

On Wed, Dec 14, 2016 at 11:53 AM Tim Cooper <timothy....@gmail.com> wrote:

There doesn't seem to be a Clever Devices to Google Realtime other than a module that Clever offers.  I'm currently trying to create a realtime feed in .Net.  I have access to the Clever database along with the API.  

Has LYNX created a solution yet?

Tim

On Thursday, October 27, 2016 at 2:11:02 PM UTC-4, Nathan Selikoff wrote:

Here in Orlando, LYNX is in the process of rolling out Clever Devices to the fleet, so I'm also interested in utilizing a Clever Devices => GTFS-Realtime feed converter if it exists (or creating/helping create one if it doesn't).

-Nathan

--
You received this message because you are subscribed to a topic in the Google Groups "onebusaway-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/onebusaway-developers/-AIMyaW9pLo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to onebusaway-developers+unsub...@googlegroups.com.

To post to this group, send email to onebusaway...@googlegroups.com.
Visit this group at https://groups.google.com/group/onebusaway-developers.
For more options, visit https://groups.google.com/d/optout.

[ruc...@umich.edu]

Hi,

Any luck on this converter? I'm working to integrate Ann Arbor's clever devices data with OBA.

[Sean Barbeau]

Unfortunately I haven't heard any more on this.

I've been cataloging all GTFS-realtime converters I've come across on the awesome-transit site, specifically at this subheading:

https://github.com/luqmaan/awesome-transit#gtfs-realtime-convertors

Sean

[Nathan Selikoff]

We have not made any progress on this unfortunately.