Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-1914

Batch Geo-coding Options: Command-line Script and Option to Geocode During Import

    Details

    • Type: New Feature
    • Status: Done/Fixed
    • Priority: Minor
    • Resolution: Fixed/Completed
    • Affects Version/s: 1.8
    • Fix Version/s: 1.8, 2.0
    • Component/s: None
    • Labels:
      None

      Description

      Rationale
      ========
      There is currently no way to geocode "batches" of contacts. During import we automatically disable geo-coding (if it's enabled) in order to prevent timeouts during processing (as each location being imported requires an external call to the geocoding service).

      Implementation
      ============
      1. Create command-line script which can be invoked to geo-code all contact address records, or a specified subset. Parameters are:

      • name: user name of authenticated user in CMS (needed)
      • pass: password of authenticated user in CMS (needed)
      • start : lowest contact.id record to begin geocoding processing. Default =1. (optional)
      • end : highest contact.id to process (if no endID, process thru highest ID in domain) (optional)
        If no parameters passed, process all contact addresses for domain 1.

      2. Option to Geocode during Import
      2.1 Add checkbox to Contact Import screen (if config->mapProvider and mapAPIKey are set) : Lookup mapping info during import?

      • default : false
      • checkbox description : " This option is not recommended for large imports. Use the command-line geocoding script instead."
        2.2 If checked, enable geocode lookup for each address insert.

        Attachments

          Activity

            People

            • Assignee:
              shailesh Shailesh Lende
              Reporter:
              dgg David Greenberg
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: