[twitter-dev] Invalid timescale error on location trends

2010-07-05 Thread Heidi Hysell
I'm trying to use the trends/location/woeid functionality (http:// dev.twitter.com/doc/get/trends/location/:woeid) and keep on getting the following error: code: 31 message: Invalid timescale: must be 'current', 'hourly', or 'daily' The documentation doesn't specify anything about sending in a

Re: [twitter-dev] Invalid timescale error on location trends

2010-07-05 Thread Raffi Krikorian
hey heidi. can you provide more information? i just tried the following few things: http://api.twitter.com/1/trends/2487956.xml (trends in SF) http://api.twitter.com/1/trends/2487956/current.xml (same as above) http://api.twitter.com/1/trends/2487956/hourly.xml (hourly version of trends from