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

Google geocoding - against terms of service?

          Details

          • Type: Bug
          • Status: Open
          • Priority: Major
          • Resolution: Unresolved
          • Affects Version/s: 4.7
          • Fix Version/s: Unscheduled
          • Component/s: None
          • Labels:
          • Versioning Impact:
            Patch (backwards-compatible bug fixes)
          • Documentation Required?:
            None
          • Funding Source:
            Needs Funding

            Description

            I've just spotted that CiviCRM's geocoding implementation is probably against Google's terms of service: https://developers.google.com/maps/terms#section_10

            CiviCRM geocodes and stores the information indefinitely, which is against 10.5 d. No caching or storage

            CiviCRM can geocode using Google, but then display the data on a different mapping provider, which is against 10.4 d and e; No use of Content without a Google map, No use of Content with a non-Google map

            In order to comply with the terms, we would have to only geocode 'on demand' ie: when a user requested the address plotted on a Google map. This would effectively kill any radius searching capabilities.

              Attachments

                Activity

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    john John K.
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    4 Start watching this issue

                    Dates

                    • Created:
                      Updated: