Detailed explanation of recurring terms
The core entity of Nearest! is a locator and represents a closed area of data. Inside every locator you have locations, elements and synchronizations and all configuration is limited to that app. You can define multiple locator apps to reflect various types of grouped locations such as stores for brand A and stores for brand B.
A location is a record in the Nearest! platform and describes an entity with a defined location. This entity can be a fixed location such as a store or place or a dynamic location such as a car or a truck. The geographical location is the only required property of that entity.
Every location can be extended with custom data. To do so you define elements. Elements are properties of the location entity and save all kind of data defined in a global elements configuration. Every element can be rendered in the web-app or is a data property of a location in the API.
Sometimes it is necessary to filter locations by its elements. Let's assume you have multiple stores and want to filter that stores by its offered services. Services would be the location element with a filter option. Every element can be a filter but not every data type makes sense to filter.
If you want to show relevance between multiple elements you can group them. Grouped elements have header, sub-header and footer for an additional description.
The process of importing, updating or removing locations from external sources is called synchronization. This is one of the core features of the Nearest! platform
An Interface represents a view on your data. This can be the web-app, a web-widget or our API. Currently only the the web-app is available to public but we are working hard on new interfaces such as a variety of awesome web-widgets, a native app build on top of the Nearest! React Native SDK, chat-bots or voice-assistant.
With our API you have direct access to your data and you can implement Nearest! functionality to your apps and programs.