Private Spatial APIs - Precisely Data Integrity Suite

The Private Spatial APIs deploys Spatial APIs into a private cloud environment. This includes a range of Spatial APIs and management application that enables an organization to rapidly integrate location information into business applications and processes. This enables organizations to create and embed maps, understand spatial relationships, and carry out spatial calculations.

The following are the main components of Private Spatial APIs:

• Spatial Manager: The foundation of Private Spatial APIs is the spatial repository which is managed by the Spatial Manager application. It allows users to create connections to supported data sources and to then configure tables, layers, maps, tiles, and styles which are used in the APIs. These are collectively known as "Named Resources". The named resources are persisted to a MongoDB database which is a pre-requisite for the deployment.
• REST Feature Service / OGC Web Feature Service (WFS): Serves geographical features in a vector format such as Geo JSON or GML. Requests are essentially a query with spatial and attribute filters.
• REST Mapping Service / OGC Web Map Service (WMS): Serves georeferenced map images which can be dynamically specified. Requests can include a bounding box or center and width along with the maps and layers to use and their styles.
• REST Map Tiling Service / OGC Web Map Tiling Service (WMTS): The Map Tiling Service returns map tiles on the fly or from a tile cache at the user's request. Both image-based tiles and vector tiles can be served.
• Supporting APIs: The supporting services are there to facilitate integration with Precisely web and desktop applications. All these services are internal and not intended for direct use.
• External / Other Services:
  • MongoDB Database: This is a required pre-requisite. The named resources managed by Private Spatial APIs using Spatial Manager are persisted to a MongoDB database.
  • Keycloak: This is an optional service but is required if role-based access control (RBAC) is needed for individual named resources. You can use it as an IDP allowing SSO, User/Role provisioning & ACL management.