geofield_update

Purpose

This module is useful if you currently use the geofield module and have added thousands of nodes in under 24 hours (through an import or similar).

You will notice that many nodes will not have automatically had the GPS coordinates "looked up"; therefore things such as "maps" will not work properly because the GPS coordinates of associated addresses are missing/empty/blank.

Why did this happen?

The geofield API only allows 1,000 lookups per day. If you add more than 1,000, let's say 5,000 nodes/addresses in one day, the last 4,000 added will NOT have any GPS points associated to them because you've exhausted your 1,000 lookups in a day. Unfortunately, the geofield module does not retroactively review each node to update the GPS coordinates. Without the geofield_update module you will need to revisit, load and save each node manually in order to get the GPS coordinates set for any node in which you have associated a geofield.

What does geofield_update do?

This module, geofield_update, will allow you to specify which content types have geofield's associated, and will then automatically load and save each node that is missing a geofield GPS entry.

You can specify the number of nodes to be processed per cron run.

Important Notes

You should ensure that the number of times "per cron run" that you've selected, divided by the number of times per day your cron runs, does not exceed 1,000. Furthermore, you should allow manual entries some space to breathe, so if you typically have 50 addresses/nodes added manually per day, you wouldn't want geofield_update to be exceeding 950 lookups per day.

Where can I make changes to the default settings?

Once installed, all options are available under "cron" with the following location: /admin/config/system/cron/geofield_update