It may seem like lately geo APIs and mashups are getting a lot of coverage here on ProgrammableWeb, and for due reason: the geo API providers have been busy. From the release of v3 of the Google Maps API to the release of Yahoo!'s Placemaker "geo-enrichment" platform, there has been a lot of activity on the mapping front in the last few weeks.
As a consumer of APIs, one thing you encounter every day are API rate limits. Just about every API has limits on the number of calls you can make against their API. As developers, we accept the limits because in many cases we are getting the API for free. And in some cases, even the rates aren't enough for a provider to get what it needs, as when Google put the kibosh on Translate. Are limits simply a sign that a provider needs to find a strategy that scales?