IngestaGeo

Ingestion, management and publishing of georeferenced maps

A single place in the cloud for all your geospatial data, published automatically for QGIS, ArcGIS or the web.

vectorpointsraster · COGbase
LayersRoad network · North providerRoad sectionsVector · PostGISBridge inventoryPoints · PostGISOrthophoto 2025Raster · COG on S3Flood riskRaster · new layerPublication requestflood_risk_2025.tif · 1.2 GBApproved · converting to COG+−05 km
12:47GPS ±3 m
IngestaGeoLayer viewer · A-6, km 214

PS-214 · Overpass

38 m from your position

Flood risk
High · T100
Condition rating
62 / 100
Last inspection
March 2025

Published layers, consulted in the field next to the structure.

Data processing and analysis

IngestaGeo centralises georeferenced data in a single place. It orchestrates a map server (GeoServer) through its REST API with a Python back-end. Layers are ingested with GDAL and OGR: vector layers into RDS and rasters into S3. Everything is compartmentalised and ready to scale on demand in the cloud.

What it does

  1. 01Almost any format

    Thanks to GDAL and OGR, we support virtually every geospatial format.

  2. 02Transparent for users

    Users upload their layers from a web interface. Once an administrator approves them, they are processed and made available to everyone else.

  3. 03Works with everything

    Compatible with QGIS and ArcGIS, and with web viewers such as OpenLayers, Leaflet, MapStore or GeoServer.

  4. 04Visibility by group

    Each layer can be restricted to certain user groups: a single system with all the data, served to each user according to their needs.

Automatic loading, transformation and publishing

It connects a centralised source of geospatial data with multiple tools and automates ingestion, so any user can publish their layers.

Useruploads a layerAdministratorapprovesGDAL · OGRtransformsGeoServerpublishes WMS/WFSQGISArcGISOpenLayersLeafletMapStoreA single source of geospatial data, published automatically for any tool.

Vector layers in OGR containers

For each vector layer a Docker container is started with the resources it needs. It runs OGR and ingests the layer into PostgreSQL with PostGIS so spatial operations can be performed on the data.

SHPGeoJSONDXFKMLGPKGDocker containerogr2ogr → PostGISresources sized to the layerPostgreSQL+ PostGISAmazon RDS

Cloud-optimised rasters

Rasters are converted to COG (Cloud Optimized GeoTIFF) with GDAL in a cloud container and stored in AWS S3, ready to be consumed from anywhere.

GeoTIFFfull, heavy fileGDALgdal_translate -of COGcloud containerCOG on Amazon S3served by tiles, only what you look at

Hierarchical organisation

Data is organised by user group, provider or project, layer group and subgroup.

User groupNorth MaintenanceProviderSurveyingProjectA-6 MotorwayLayer groupCartographyLayer groupInventoryLayer groupRisksLayer groupWorksvisible layerrestricted to another group

Where we have applied it

Want to see itin action?

We will show you IngestaGeo with data and cases similar to yours, and answer your technical questions.

Cookie preferences

Technical

Needed for the website to work and to remember your choice.

Always on

Google Analytics: visits and use of the website, in aggregate. Only if you accept.