Set latitude and longitude values on a form using Google Maps. The map includes a search field and a current location link. When a pin is placed or dragged on the map, the latitude and longitude fields are updated.
This bundle is compatible with Symfony 3 and 4. Use composer to install:
composer require krixer/google-map-form-type-bundle
Register the bundle in your config/bundles.php:
// config/bundles.php return [ // ... Oh\GoogleMapFormTypeBundle\OhGoogleMapFormTypeBundle::class => ['all' => true], ];
Create options file in config/packages directory
# config/packages/oh_google_map_form_type.yaml oh_google_map_form_type: api_key: "%google_maps_api_key%"
This bundle contains a new FormType called GoogleMapType which can be used in your forms like so:
$builder->add('latlng', GoogleMapType::class);
On your model you will have to process the latitude and longitude array
// Your model eg, src/My/Location/Entity/MyLocation.php
use Oh\GoogleMapFormTypeBundle\Traits\LocationTrait;
class MyLocation
{
// ... include your lat and lng fields here using LocationTrait
use LocationTrait;
}
Include the twig template for the layout. It's generally a good idea to overwrite the form template in your own twig template
# your config.yml
twig:
form_themes:
# This uses the default - you can put your own one here
- 'OhGoogleMapFormTypeBundle:Form:fields.html.twig'
If you are intending to override some of the elements in the template then you can do so by extending the default google_maps.html.twig. This example adds a callback to the javascript when a new map position is selected.
{# your template which is inluded in the config.yml (above)
eg src/My/Location/Resources/views/Form/fields.html.twig #}
{% extends "OhGoogleMapFormTypeBundle:Form:google_maps.html.twig" %}
{% block oh_google_maps_callback %}
<script type="text/javascript">
var oh_google_maps_callback = function(location, gmap){
// logs to the console your new latitude
console.log('Your new latitude is: '+location.lat());
}
</script>
{% endblock %}
There are a number of options, mostly self-explanatory
array(
'type' => HiddenType::class, // the types to render the lat and lng fields as
'addr_type' => TextType::class, // the type to render the address field
'attr' => ['class' => 'form-group'],
'search_enabled' => true,
'options' => [], // the options for both the fields
'lat_options' => [], // the options for just the lat field
'lng_options' => [], // the options for just the lng field
'addr_options' => [], // the options for just the addr field
'lat_name' => 'latitude', // the name of the lat field
'lng_name' => 'longitude', // the name of the lng field
'addr_name' => 'address', // the name of the addr field (optional)
'error_bubbling' => false,
'map_width' => '100%', // the width of the map
'map_height' => '300px', // the height of the map
'default_lat' => 41.390205, // the starting position on the map
'default_lng' => 2.154007, // the starting position on the map
'include_jquery' => false, // jquery needs to be included above the field (ie not at the bottom of the page)
'include_gmaps_js'=>true // is this the best place to include the google maps javascript?
)
Default form Current position Search locations LatLng validation
Because the form type template includes javascript, there's not yet a way to bunch it all together at the very bottom of the page, so it is included at the bottom of the field. This means that jquery and the javascript plugin in Resources/public/js needs to be included before the field. I'm not sure of a way around this, but I think it's going to be addressed in a later version of the form framework.
- Ollie Harridge (ollietb) as main author.
- Hector Escriche (krixer) as contributor.