"Stop #### not found" response?

Paul Wilson

unread,

Sep 6, 2011, 9:36:15 AM9/6/11

to smsmyb...@googlegroups.com

Hello,

I am trying to query stop location:
http://www.smsmybus.com/api/v1/getstoplocation?key=pw83s92o;stopID=2505

I get "Stop 2505 not found".

However, it shows up on the list at:
http://www.cityofmadison.com/metro/busstopdepartures/number/4.cfm

Just curious to know if there is something wrong with my query, or some
other back-end issue/limitation?

Paul

--
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --
Paul Wilson ~ UW-Madison ~ 608-263-0807 ~ cal: http://bit.ly/pphw-cal
Associate Professor, Engineering Physics. ~ http://cnerg.engr.wisc.edu
Chair, Energy Analysis& Policy Program ~ http://nelson.wisc.edu/eap

Greg Tracy

unread,

Sep 6, 2011, 9:58:59 AM9/6/11

to smsmyb...@googlegroups.com

You found a hole in the datastore. Odd. The way the datastore is
setup, each route/stop pair stores a stop location and for some reason
the routes going through that stop are not configured with a location.

I can fix this but it won't happen until later today.

Greg Tracy

unread,

Nov 5, 2011, 11:18:30 PM11/5/11

to smsmyb...@googlegroups.com

Circling back on this one... I've been patching a bunch of holes in the Stop list.

I don't know of any holes right now, but I've set things up to email me when a request comes in for a stop that is missing. Interestingly, this method has highlighted the fact that a lot of users routinely ask for the wrong stop when they are using the SMS interface! I had no idea...