Getlocations Fields and Adress_Field

This thread appears to be referencing another thread somewhere else.

FYI
Getlocations Fields does all its geocoding clientside, in the browser, using javascript, eg before submission. The practical problems of identifying the addressfield components in the DOM so that the javascript can geocode the address make it almost impossible to use Addressfield for geocoding purposes which is why Getlocations_fields has its own address components.

If you want to geocode on Addressfield components you can do this with Geofield or Geolocation modules, both of which do their geocoding after submission. You can then use the Getlocations module (without getlocations_fields) to provide display support.

I am also using Drupal Commerce, which has the Address Field module as a dependency. IMO, this is bad, but this is a fact. I do NOT use any Postal address field, but use my own static address components instead.

On this module's project page, it is stated:

Do not install the (...) Addressfield (...) modules at the same time as Getlocations_fields, this will not work.

Having the the Address Field module installed without Postal address fields used does not cause problems however. Maybe the project page note can be more clear on this.

Thanks.

I have edited the project page to reflect this. The Addressfield module uses different css identifiers so the presence of those fields in the input form should not interfere with Getlocations_fields geolocation.
Getlocations has a concept "current supported modules" which is an array of locative modules, if for instance you have both Getlocations_fields and Geofield installed only Getlocations_fields will be detected as it is the first in the list.

Great, thanks for the clarification.

Now the project page stating

The Addressfield module can co-exist with Getlocations_fields but will not be used for geolocating addresses.

is clear.