Location
Learn about how Maica uses Locations within the overall solution.
Last updated
Was this helpful?
.svg?alt=media&token=63cf31eb-c598-4fab-b9ff-0a05ca54831f)
.svg?alt=media&token=213783ff-fbc4-4ac8-b766-39ced3d3816c)
User Guide
Learn about how Maica uses Locations within the overall solution.
Last updated
Was this helpful?
Locations in Maica specify a particular geographic address that may be used across your organisation. A typical example of this might be a wellness centre, therapy studio, or headquarters.
Locations capture information such as MMM classifications, addresses, and geolocation coordinates derived from Google, via Maica's Google Maps API integration.
The purpose of Locations is to abstract the actual address information from the end user (or Resources) when managing either or . The end user does not need to be concerned with entering the right address everytime an or is managed but rather can simply select the Location.
Locations are primarily used when managing and . This allows the end user to simply select a Location rather than entering an address manually. Maica's Google Maps API integration also uses Locations to geo-code each one which is then used to calculate travel times between . Locations are also set for each as their primary Location so Maica can track the travel time from this address.
Locations are a good way to abstract the management of addresses manually, so we encourage you to capture Locations for each address that is used more than once and should be globally accessible.