Technical Architecture Diagram

Spatial Data Repository

CPU: 2-cores
HDD: 50GB+
64-bit Windows 2003 or newer
One of OGC-compliant databases:
Microsoft SQL Server 2008 or newer *
PostgreSQL with PostGIS
Oracle 10g or newer
(*) – recommended solution

Corporate GIS / Advanced Analytical GIS

CPU: 4-cores (more cores recommended)
SuperPI 1M benchmark ~ 20sec
RAM: 16GB+
HDD: 100GB+
64-bit Windows 2008R2 or newer
IIS 7 or newer
.NET Framework 4.6.2 Full


Microsoft Silverlight 5 or newer
and one of the following:

  • Internet Explorer 7 or newer
  • Google Chrome
  • Apple Safari
  • Mozilla Firefox
Technical Specification Diagram - Earthlight

Integration and interoperability

Data is always stored in one, central, OGC-compliant database. All modern GIS systems can access spatial data directly from the database, without using vendor-specific middleware like ArcSDE. Moreover StatMap provides a set of synchronization tools which ensures that Spatial Data Repository is always kept in sync with external data sources, like other databases, flat files or web services.

Performance and scalability

StatMap server solutions try to save database resources and cache all spatial data. Therefore only changes are sent to database and during rendering operations database is not being used. This architecture ensures rendering speed below 0.1 sec per map and easily handles 100+ users from a single server. Since all data is stored in a central database it is very easy to scale system horizontally. Please note that Spatial Data Repository is always underutilized and even under heavy load StatMap servers rarely fetch data from the SDR.

Publishing spatial datasets

Since all instances of StatMap servers are always kept in sync with Spatial Data Repository all spatial datasets can be easily published directly from StatMap Earthlight within a few minutes. In addition StatMap Aurora can collect data from public members and fetch results directly to SDR or to CRM system.