← Back to productsLevel 2 - Product sheet

GISMart

v0.2.0 Software Objlab - OBJ-GIS-001 da 4.800 €/anno

Level 3 - Commercial request

This sheet summarizes value, pricing and use cases. From here you can move to the dedicated areas or to the client portal for the next action.

GISmart is the geospatial enabling layer that makes any management software (ERP, CRM, logistics, asset management) location-aware through multi-tenant APIs, without requiring GIS skills or a dedicated GIS desktop.

What it solves

The management systems save addresses but cannot show records on a map nor query them by area or distance.
Adding geographic intelligence requires specialized GIS skills and spatial SQL that the teams do not have.
Commercial and operational analysis (territories, coverages, clusters, heatmaps) remain manual or impossible without a spatial layer.
Massive import/export of georeferenced data and integrations with external providers (geocoding, routing, weather) are costly to build from scratch.

Software that enables geographic information of data, with programmable and callable APIs from any application.

What it does

GISmart is a backend and an integration layer that brings geographic intelligence inside existing management software, without replacing it. It exposes multi-tenant REST APIs, operational workspaces via browser, and support services, allowing a business application to make its own data "location-aware" with just a few calls.

The data model is deliberately generic: each record is a business_entity identified by an entity_type (for example customer, warehouse, property, plant, service_point), coordinates or geometry, and free metadata for domain attributes. This allows the same core GIS to be reused for sales, logistics, suppliers, utilities, real estate, and asset management.

Module	Role
`core`	General GIS APIs and services: entities, layers, service zones, spatial analytics, bulk I/O
`admin`	Tenant management, users, roles, permissions, tokens, audit and jobs
`sales`	Commercial vertical: leads, opportunities, customers, territories, suppliers, KPIs
`logistics`	GIS-first operational vertical: warehouses, vehicles, deliveries, loads
`suppliers`	Supplier network: directory, coverage, risk monitoring, procurement KPIs
`utilities`	Import administrative boundaries, spatial joins, dataset diagnostics
`mobile`	Authentication and task synchronization for field operators

Key Features

Geocoding of addresses with selectable providers (Nominatim, mock, auto mode with fallback).
Spatial storage on PostGIS with GeoJSON output ready for web maps (Leaflet).
Nearby search and area/distance queries without writing spatial SQL.
Backend spatial analytics: clustering, DBSCAN, density grid, heatmap, service zone overlap and coverage gap.
Temporal queries on the history of entity positions and playback of movements.
Automatic spatial join and enrichment of entities with nearest zone and last position.
Routing, distance matrix and isochrones (offline-safe geodetic provider or OSRM).
Weather (point) and economic area-level enrichment services (mock or World Bank).
Mass import/export of entities in CSV, JSON, XLSX and SQL formats, with preview and map projection.
Embeddable JavaScript widgets to mount a map inside third-party applications.
Ready-to-use browser workspaces (sales/logistics/suppliers dashboard, GIS studio, GIS analytics, IO studio, admin center, provider center).

Architecture

Python 3.12+ Stack based on FastAPI, SQLAlchemy 2 and GeoAlchemy2, with PostgreSQL + PostGIS as the sole spatial database. The canonical external coordinate system is WGS84 (EPSG:4326) with GeoJSON payload for frontend rendering. A provider abstraction layer manages geocoding, routing, weather, economy and OIDC discovery with retry, in-memory circuit breaker and optional Redis cache. Long operations (bulk import, enrichment, connector, compliance) are delegated to background jobs on database queue, with dedicated workers and scheduler; Redis is optional with automatic fallback to the backend database. The architecture is multi-tenant with security, audit and governance as first-class concepts: tenant-scoped API tokens (Bearer), role-based permissions, HMAC SHA-256 signed webhooks and hardened OIDC/OAuth2 for production. Observability included via Prometheus endpoint /metrics, request-id correlation and optional Prometheus/Grafana/Alertmanager stack.

Requirements

Python 3.12+ as API runtime.
PostgreSQL with PostGIS extension enabled (database gismart, script sql/init.sql).
Main dependencies: FastAPI, Uvicorn, SQLAlchemy 2, GeoAlchemy2, psycopg 3, openpyxl, PyJWT, Alembic.
Optional Redis (queue/cache) via GISMART_REDIS_URL, with automatic fallback to the database.
Flexible deployment: Docker/docker-compose, Windows installer (Inno Setup) or desktop shell Electron with integrated Chromium.
Optional external providers for geocoding (Nominatim), routing (OSRM), weather and economy (World Bank).

Compliance & regulations

GDPR

Regolamento UE 2016/679 - protezione dati

Copertura baseline: policy di retention configurabile su audit event e background job, anonimizzazione delle entita', export dati soggetto e report firmati. Non e' una certificazione, ma uno strato operativo a supporto della conformita'.

Reports & dossiers

Report di compliance firmatoJSON firmato (HMAC)
Genera un report di conformita' con firma opzionale per audit e governance dei dati.
Export massivo entita'CSV, JSON, XLSX, SQL
Esporta le business entity filtrate per backup, migrazione o richieste di portabilita' dati.
Export join confini amministrativiGeoJSON
Esporta il risultato del join spaziale tra entita' e confini amministrativi importati.
Audit event logJSON (API)
Traccia le azioni amministrative tenant-scoped per revisione e conformita'.

Try it

GISMart sul campo

Interrogazione per prossimita' su mappa, risposta GeoJSON e geocodifica delle anagrafiche che avete gia'.

Frequently asked questions

Sostituisce QGIS o ArcGIS?

No, and it doesn't try to. GISMart is not a desktop GIS: it's a layer that makes your existing management software location-aware through APIs. If you need to draw maps, you need a GIS. If you need your management system to know where things are, this is what you need.

What can be mapped?

Real estate, buildings, units and lots on one side; technical assets such as installations, sites, warehouses, cabinets, and service points on the other. The categories are not predefined: they are defined with a type of entity and free metadata, so the model adapts to the domain rather than the opposite.

Come si integra con il nostro software?

With REST APIs that return GeoJSON, the format that maps in the browser consume directly. There are queries for proximity and for area, and endpoints ready for grouping points on the map.

Che database richiede?

PostgreSQL with the PostGIS extension, which is the de facto standard for spatial data. GISMart does not introduce a proprietary geographic repository.

Try it Client area — download Parla con un esperto

Use cases

Territori e coperture analizzati senza scrivere SQL spaziale

Rete vendita resa geografica

Un'azienda con CRM esistente integra GISmart per mostrare clienti e fornitori su mappa, assegnare territori e individuare clienti scoperti senza referente o area, generando heatmap e analisi di copertura per la forza vendita.

Consegne e carico monitorati in un unico workspace GIS-first

Logistica di consegna ottimizzata

Un operatore logistico usa il modulo logistics per georeferenziare magazzini, veicoli e consegne, individuare consegne non assegnate, bilanciare il carico per magazzino e pianificare percorsi con matrice distanze e isocrone.