Location and coordinates

Which configuration is used for a record?

prepareModel() determines the recordlocationName, e.g. "Milan", which affects the available Machine Learning models

getConfig() determines the record zone, e.g. "Milan MPZ", which determines the specific configuration (rules) applied for the record

As of release 2.1, locationName is an optional parameter.

How should I test the behaviour on a real device, outside of a given location?

⚠️ In order to test for a given location, outside of that location geozone, we recommend providing mock coordinates within that zone.

What if coordinates and location name are not aligned?

If both locationName and coordinates are provided, coordinates are considered first.

Note that this check happens in two places in the SDK lifecycle:

1. prepareModel() defines the locationName
2. getConfig() retrieves the correct zone