logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Login


Options
View
Go to last post Go to first unread
Maurice  
#1 Posted : Wednesday, February 15, 2012 5:36:34 PM(UTC)
Maurice

Rank: Member

Groups: Registered
Joined: 7/16/2011(UTC)
Posts: 15

Thanks: 1 times
I have two suggestions to the API.

1. Multiple stop query.
Sometimes I want to get information for multiple stops at once. The current API only supports one stop_id for each call (for most of the methods) so multiple consecutive calls is required. Obviously this is not the best for performance.
Therefore I suggest allowing a comma-separated-list / semicolon-separated-list of stop_id's in stop related functions so we can reduce the number of calls to the server.

2. Stop is_active
Sometimes I want to know whether a stop is currently functioning, possibly used for filtering out results that are irrelevant. This either means defunct stops like "Green at Illinois Street Residence Hall" or stops that are not serving at night or weekends.
So an is_active field in the functions that return stop information would be very useful in this situation. This can either be according to the schedule or real time information. (I think according to schedule is good enough for most cases).

Maurice

Edited by user Thursday, February 16, 2012 10:38:08 AM(UTC)  | Reason: Not specified

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.