Answers.Body: <p>Your questions are not provider specific and you didn't specify one, but if you are using Google, it looks like the documentation you reference is a bit out of date with regards to Google's requirement for API keys: the use of API keys was optional until changes recently went into effect in the Google Maps Platform. This month's Cividesk newsletter includes an article that details what needs to be done for Google APIs to continue functioning properly - you'll find that article <a href="https://www.cividesk.com/blog/post/important-changes-google-mapping-and-geocoding-services#" rel="nofollow noreferrer">HERE</a>.</p>
  
  <p>That said, I copy and paste your questions and intersperse them with my responses below and include links to resources where you should find more detailed instruction:</p>
  
  <p><strong>Q1:</strong> How long does it run each time it is triggered? (max exec time?)</p>
  
  <p><strong>A1:</strong> It depends on  how you run the cron - the answer to <a href="https://civicrm.stackexchange.com/questions/25038/long-running-scheduled-job">THIS</a> question should point you in the right direction.</p>
  
  <p><strong>Q2:</strong> Can I throttle the amount of contacts it attempts to code for each run? I want to avoid it running non-stop and killing the server by overloading it.</p>
  
  <p><strong>A2:</strong> You will find job parameters detailed <a href="https://docs.civicrm.org/user/en/latest/initial-set-up/scheduled-jobs/#job_geocode" rel="nofollow noreferrer">HERE</a> (including throttle and limiting to specific contact IDs).</p>
  
  <p><strong>Q3:</strong> I don't like to have more than one street address field (disabling supplemental 1,2,3) as users do not consistently input the their data right if you give them too many options. However, is it okay to include APT numbers etc in the main street address field and it still geocode reliably? I've done a few tests on records but not with a large sample.</p>
  
  <p><strong>A3:</strong> The basic rule of thumb is to specify addresses in accordance with the format used by the national postal service of the country concerned. Additional tips on address formatting can be found <a href="https://developers.google.com/maps/faq#geocoder_queryformat" rel="nofollow noreferrer">HERE</a>. CiviCRM includes an optional plugin for interfacing the the United States Postal Services (USPS) Address Standardization web service, details of which you will find <a href="https://docs.civicrm.org/user/en/latest/initial-set-up/addresses/#address-standardization" rel="nofollow noreferrer">HERE</a>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-13T07:02:00.800Z
Answers.LastActivityDate: 2018-09-13T07:02:00.800Z
Answers.UserDisplayName: Tamar Meir - Cividesk
Body: <p>The log says the scheduled job ran and worked, but I checked some contacts and see nothing happened. I had it set to run daily. It geocodes just fine on import and upon saving a record.</p>
  
  <p>So, I have some questions.</p>
  
  <ul>
  <li>How long does it run each time it is triggered? (max exec time?)</li>
  <li>Can I throttle the amount of contacts it attempts to code for each run? I want to avoid it running non-stop and killing the server by overloading it.</li>
  <li>I don't like to have more than one street address field (disabling supplemental 1,2,3) as users do not consistently input the their data right if you give them too many options. However, is it okay to include APT numbers etc in the main street address field and it still geocode reliably? I've done a few tests on records but not with a large sample.</li>
  </ul>
  
  <p>I don't see in the docs clear answers: <a href="https://docs.civicrm.org/user/en/latest/initial-set-up/mapping/" rel="nofollow noreferrer">https://docs.civicrm.org/user/en/latest/initial-set-up/mapping/</a></p>
  
  <p>Perhaps we can update the docs more on this?</p>
  
Tags: <geocoding>
Title: Setting up geocoding
ThreadText: # Setting up geocoding
  
  (Asked by: username_0 on 2018-08-27)
  
  The log says the scheduled job ran and worked, but I checked some contacts and see nothing happened. I had it set to run daily. It geocodes just fine on import and upon saving a record.
  
  So, I have some questions.
  
  * How long does it run each time it is triggered? (max exec time?)
  * Can I throttle the amount of contacts it attempts to code for each run? I want to avoid it running non-stop and killing the server by overloading it.
  * I don't like to have more than one street address field (disabling supplemental 1,2,3) as users do not consistently input the their data right if you give them too many options. However, is it okay to include APT numbers etc in the main street address field and it still geocode reliably? I've done a few tests on records but not with a large sample.
  
  I don't see in the docs clear answers: <https://docs.civicrm.org/user/en/latest/initial-set-up/mapping/>
  
  Perhaps we can update the docs more on this?
  
  **Tags:** geocoding
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-09-13. Score: 2 | Accepted answer
  
  Your questions are not provider specific and you didn't specify one, but if you are using Google, it looks like the documentation you reference is a bit out of date with regards to Google's requirement for API keys: the use of API keys was optional until changes recently went into effect in the Google Maps Platform. This month's Cividesk newsletter includes an article that details what needs to be done for Google APIs to continue functioning properly - you'll find that article [HERE](https://www.cividesk.com/blog/post/important-changes-google-mapping-and-geocoding-services#).
  
  That said, I copy and paste your questions and intersperse them with my responses below and include links to resources where you should find more detailed instruction:
  
  **Q1:** How long does it run each time it is triggered? (max exec time?)
  
  **A1:** It depends on how you run the cron - the answer to [THIS](https://civicrm.stackexchange.com/questions/25038/long-running-scheduled-job) question should point you in the right direction.
  
  **Q2:** Can I throttle the amount of contacts it attempts to code for each run? I want to avoid it running non-stop and killing the server by overloading it.
  
  **A2:** You will find job parameters detailed [HERE](https://docs.civicrm.org/user/en/latest/initial-set-up/scheduled-jobs/#job_geocode) (including throttle and limiting to specific contact IDs).
  
  **Q3:** I don't like to have more than one street address field (disabling supplemental 1,2,3) as users do not consistently input the their data right if you give them too many options. However, is it okay to include APT numbers etc in the main street address field and it still geocode reliably? I've done a few tests on records but not with a large sample.
  
  **A3:** The basic rule of thumb is to specify addresses in accordance with the format used by the national postal service of the country concerned. Additional tips on address formatting can be found [HERE](https://developers.google.com/maps/faq#geocoder_queryformat). CiviCRM includes an optional plugin for interfacing the the United States Postal Services (USPS) Address Standardization web service, details of which you will find [HERE](https://docs.civicrm.org/user/en/latest/initial-set-up/addresses/#address-standardization).
  
  
  ---
  
  