The XYZ project consists of a backend and frontend component. The frontend will also be referred to as the client or browser in this documentation. The frontend interface contains a map control. Due to the serverless nature of XYZ deployments, we attempt to limit the use of server or serverside when referring to the backend.
Environment Settings define the setup of the backend to serve a client application and API.
Workspaces are a set of instructions which define the use of data as layers and locations to be used by the client application and API.
An object entry is a JSON key/value pair. The key being the identifier to look up an entry and retrieve its value. A key must have a value associated. Key and value are separated by a colon. Keys must be a string. Values may be a string, numeric, boolean, an array or objects.
Locales are a collection of regional bounds, gazetteer and layers.
Layers are data tables which can be displayed and interacted with.
Locations are features in data tables which can be selected and interacted with.
Deployment is act of deploying code from the repository to run as an XYZ instance.
Endpoints (also routes) make up the XYZ application interface. Distinct endpoints can be used to request data and edit data or make changes to the application settings themselves. The domain route (root /) will request the client interface (frontend) which links a graphic user interface and map control to backend endpoints.
Token (also acccess token) is a signed JSON Web Token used to transmit information about a user account from the client to the XYZ backend.