Constructing geocode request


I’ve managed to make an OAuth library that successfully signs and sends correct URL’s to the Twitter API, however there seems to be a lack of information on how to construct more complex queries. If I add as the search parameters “&q=london.json” that works. If I add on any other parameters such as geocode, ending it with .json, it no longer works e.g.

How is the search segment of the URL supposed to be constructed?


In case anyone else runs across this, the answer is:

count=50.json& * everything else in get request * and end the entire request (so after the tokens etc) with “&q=* search parameter *”

Hopefully Twitter will move onto OAuth 2.0 soon as this implementation is a chaotic mess.