Answers.Body: <p>I've been able to correct this issue by running the Geocode and Parse Addresses Job.</p>
  
  <p>Thansk! </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T18:43:09.537Z
Answers.LastActivityDate: 2015-12-04T18:43:09.537Z
Answers.UserDisplayName: trvrtwr
Answers.Body: <p>After running the update command on database, you need to clear the civicrm cache (also make empty the civicrm_cache table) and delete the civicrm temporary file.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T18:24:39.060Z
Answers.Text: I've run the Clean-up Temporary Data and Files (cleanup) Job, which I believe should do what you suggested, but still the same issue.
  
  Would I be correct to assume it may have something to do with updating the Geocode?
Answers.UserDisplayName: trvrtwr
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-04T18:19:05.437Z
Answers.LastActivityDate: 2015-12-04T18:19:05.437Z
Answers.UserDisplayName: Prem Patel
Body: <p>So I was playing with the contact mapping option for a search profile. I noticed that mapping did not work when the postal code was entered with a space in it.
  Example: "E1C E1C" rather than "E1CE1C"
  When I tried to view the map I would get:
  <em>Error This address does not contain latitude/longitude information and cannot be mapped.</em> </p>
  
  <p>So I decided to run an update on the database: UPDATE <code>civicrm_address</code> SET <code>postal_code</code> = REPLACE(<code>postal_code</code>, ' ', '').</p>
  
  <p>Which was successfull.. But still when trying to view map that error appears for the contacts that once had the space in their postal code.</p>
  
  <p>If I go into the contact edit, edit the address field, change nothing, and just hit save, the issue is resolved. But I don't want to have to do that for every contact. Surely there most be a way to force it to update?</p>
  
  <p>I hope I was clear with my issue. Any help would be appreciated.</p>
  
  <p>I've also run the Clean-up Temporary Data and Files (cleanup) Job,  but still the same issue. </p>
  
  <p>Would I be correct to assume it may have something to do with updating the Geocode?</p>
  
  <p>Civicrm: 4.6.10
  Joomla: 3.4.5</p>
  
  <p>Thanks!</p>
  
  <p>I've been able to correct this issue by running the Geocode and Parse Addresses Job.</p>
  
  <p>Thansk!</p>
  
Tags: <database><upgrade>
Title: updated database from backend, issues when searching that field - Geocoding issue with Postal Code update
ThreadText: # updated database from backend, issues when searching that field - Geocoding issue with Postal Code update
  
  (Asked by: username_0 on 2015-12-04)
  
  So I was playing with the contact mapping option for a search profile. I noticed that mapping did not work when the postal code was entered with a space in it.
  Example: "E1C E1C" rather than "E1CE1C"
  When I tried to view the map I would get:
  *Error This address does not contain latitude/longitude information and cannot be mapped.*
  
  So I decided to run an update on the database: UPDATE `civicrm_address` SET `postal_code` = REPLACE(`postal_code`, ' ', '').
  
  Which was successfull.. But still when trying to view map that error appears for the contacts that once had the space in their postal code.
  
  If I go into the contact edit, edit the address field, change nothing, and just hit save, the issue is resolved. But I don't want to have to do that for every contact. Surely there most be a way to force it to update?
  
  I hope I was clear with my issue. Any help would be appreciated.
  
  I've also run the Clean-up Temporary Data and Files (cleanup) Job, but still the same issue.
  
  Would I be correct to assume it may have something to do with updating the Geocode?
  
  Civicrm: 4.6.10
  Joomla: 3.4.5
  
  Thanks!
  
  I've been able to correct this issue by running the Geocode and Parse Addresses Job.
  
  Thansk!
  
  **Tags:** database, upgrade
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2015-12-04. Score: 1 | Accepted answer
  
  I've been able to correct this issue by running the Geocode and Parse Addresses Job.
  
  Thansk!
  
  
  ---
  
  ### Answer by username_1 on 2015-12-04. Score: 1
  
  After running the update command on database, you need to clear the civicrm cache (also make empty the civicrm\_cache table) and delete the civicrm temporary file.
  
  > **Comments:**
  > **username_0**: I've run the Clean-up Temporary Data and Files (cleanup) Job, which I believe should do what you suggested, but still the same issue.  Would I be correct to assume it may have something to do with updating the Geocode?  
  
  ---
  
  