Using the location field editor you can to provide an accurate location within an entry. A location can be set using the search which is powered by Google Places, or by navigate with the map.
Fine adjustments to location can be set by dragging the map pin to an exact position, or by entering latitude and longitude coordinates.
||A text label to identify the field in an entry.
||A sanitised name to be used by the API.
||The default value allows you to set the default location for an entry.
||Prevents authors from editing the field in the entry editor.
|Allow multiple items to be added
||Sets the field to be repeatable, allowing an author to create a list of items.
This field editor supports the following validation methods.
||Provides guidance to an author for the expected content that the field should contain.
||Determines the size of the rendered editor in the entry editor. The default value is set to Medium.
Map centre position
If you want to set your map to be centred around a location other than the default of London, you can use this property to set where the map should be centred to.
Show latitude and longitude
It's possible to enter exact latitude and longitude values into the entry editor, however, most authors will want to use the search or set a location using the map.
This setting determines if the latitude and longitude number fields should be shown in the entry editor. By default these fields are not displayed.
If you want your authors to manually set the location using the navigation controls then you can disable the search box in the field editor. The search box is enabled by default.
Place search limitations
The location field editor uses the Google Places API Web Service to carry out location searches. There is a default limit set by Google of 1,000 free requests per 24 hour period.
Each text search counts as 10 requests to this service, the default limit in a 24 period could quickly be met if your authors use location searches in their entries regularly.
Increasing the limit
To increase the limit to 150,000 requests you'll need to verify your identity with Google by adding your billing information through the Google developer console. Once billing information has been added you can create an API Key via the Google API Console. This API key can then be applied to the project setting Google_ApiKey_Places.
Note: The credit card details provided for billing are purely to validate identity. The card will not be charged for use of the Google Places API Web Service.
If you feel you need more than the 150,000 requests then you can purchase a Google Maps API premium plan.
Full details can be found at the Google Place API usage and billing site