Converting from Ether Maps

Minimum Craft Requirement

This feature requires a minimum of Craft 4.13.0+ or 5.5.0+.

Importing Address Data

Converting from an Ether Maps "Map" field to an "Address (Google Maps)" field is relatively straightforward... simply switch the field type on the field's settings page.

Just change the field type!

After saving the field as an "Address (Google Maps)" field, all data associated with that field will automatically be imported into the Google Maps plugin.

One Field at a Time

When you update a single field, only the data for that specific field will be migrated over. Each Address field will need to be converted individually.

Field Configuration Not Included

The field's settings will not be ported, only the field's existing data will be transferred over.

You may still want to configure the Google Maps field to your liking, it will not automatically reflect how you had it configured with Ether Maps.

Deploying to Production

When deploying to a production environment, you'll most likely be using Project Config (opens new window) to keep all of your configuration settings in sync. Don't worry, there will be little (or no) action required on your part.

All relevant Address data will be converted once your Project Config changes are applied.

Twig Template Changes

For proximity searches, you'll likely need to update your templates to reflect the new field type.

Pay close attention to the different options available for proximity searches.

• Google Maps (new)
• Ether Maps (old)

{% set entries = craft.entries
    .myAddressField({
        'target': 'Barcelona, Spain',
        'range': 100,
        'units': 'mi'
    })
    .orderBy('distance')
    .all() %}

	Google Maps (new)	Ether Maps (old)
Center of the proximity search	target	location
Range of the proximity search	range	radius
Units of measurement for range	units	unit

Complex Proximity Searches

For more complex searches, see the complete Proximity Search documentation.