-
Notifications
You must be signed in to change notification settings - Fork 106
Of API keys and large batches #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Hi @Forbin
But it's possible to do the job without configuration - here is a basic example: // ...
$adapter = App::make('geocoder.adapter';)
$providers = array(
new \Geocoder\Provider\CloudMadeProvider($adapter, 'api-key'),
new \Geocoder\Provider\MapQuestProvider($adapter, 'api-key', 'my-locale'),
);
try {
// maybe the chain provider is better here :)
Geocoder::registerProviders($providers);
Geocoder::using('cloudmade');
$geocode = Geocoder::geocode('10 rue Gambetta, Paris, France');
var_dump($geocode);
} catch (\Exception $e) {
echo $e->getMessage();
}
// ... Yes it's more work but why not to define your own service ?
|
Version 0.3 should now fix this as well :) |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure where to put the api keys in the Laravel version of geocoder. I do not see how in the config, so I am placing them in the willdurand provider files directly. That does not seem right. With the API keys in those files I am not getting anything back for MapQuest and CloudMade.
I am trying to process about 300,000 addresses for a database. Which provider would be best for that?
The text was updated successfully, but these errors were encountered: