GIS Platform

GIS Platform is a web-based GIS solution. It supports the full cycle of working with spatial layers (vector and raster type): importing, creating, editing, customizing visualization, sharing, exporting, managing. It also enables performing geo analytical tasks using layers and geo tools provided.

Architecture

GIS Platform comprises a frontend and a backend parts. They communicate with each other via RESTful API interface. All communications are protected through SSL (in other words, HTTPS is used).

Frontend services

The frontend is used to interact with the GIS Platform service.

It provides the following web interfaces to access the service:

1. Web UI GIS Tools is a set of tools for working with geospatial layers: updating the layer, editing information inside the layer (geometry and attributes), geoprocessing and making geo analysis of the geodata (building buffer zones or accessibility zones from the objects and making spatial queries), customizing the visualization of the layer, exporting the layer to Shape, GeoJSON, CSV formats, etc.
2. Web UI Admin is a web application for managing service's configuration settings, users, and roles.

The frontend services can authenticate end users via login and password pair.

Backend services

SPCore

The SPCore backend service implements all necessary geospatial logic. It is the primary backend service the frontend communicates with.

SPCore uses:

• Apache ZooKeeper as a message queue for long-running tasks like buffer zone creation.

• Other pre-deployed On-Premise services:

  • Maps services

    • The raster Tiles API is accessed to get a Basemap.

  • Search services

    • The Geocoder API is accessed to work with geocoded data.
    • The Suggest API is accessed to provide suggestions on various objects on a map's overlay.

  • Navigation services

    • The Isochrone API is accessed via Navi-Front to get an area on the map that is reachable from a given point by car in a given amount of time.

  • Traffic API Proxy

    If the service is deployed and configured to get real-time traffic data from Traffic Servers, then end users and applications can use GIS Platform to plot colored traffic status on a map's overlay. SPCore interacts with the service in order to provide this capability.

SPCore stores:

• The raster images in an S3 compatible storage. This allows, for example, to store the tiled satellite imagery for further usage.
• The information on data layers, current configuration, users, and roles in PostgreSQL databases.

ZooKeeper

The ZooKeeper backend service acts as a message queue for long-running tasks like buffer zone creation.

Dependencies

• Shared infrastructure:

  • S3 compatible storage for storing tiled raster images. The GIS Platform requires two separate buckets in this storage: one for previews, other for raster images
  • PostgreSQL data storage with PostGIS extension

• Services:

  • Maps services with raster Tiles API
  • Search services with Geocoder API and Suggest API
  • Navigation services with Isochrone API
  • Traffic API Proxy configured to use Traffic Update servers that provide the data in raster format.

• Software on the machine used for deploying the GIS Platform service:

  • bash
  • curl
  • git
  • jq

For more information on how to check requirements for each service, refer to the System requirements document.

What's next?

• Find out how to install or update the service:

  • Installing GIS Platform
  • Updating GIS Platform

• Read more about On-Premise:

  • Solution architecture
  • System requirements