I didn't find anything from a search of the list archive, so maybe this hasn't been brought up before, but is there any way that the venue api could be made a bit more consistent on naming conventions for data fields?

example: When searching, the city field is called "city_name", but when you get the venue by the id that came back, the city is now "city". Makes it interesting to write parsing for bringing the response back in or caching it to a local db...

This is the same with at least region and country i believe, i haven't gotten real far in using it yet, but I'll report more if I find them.

Thanks!

Reply via email to