Spain · working on site and remotely

BGEO OPEN GIS SL

Open-source GIS software and a field app for viewing maps and recording spatial data where the work actually happens.

  • Open source
  • Offline field work
  • OGC standards

What we build

Field data collection that works without signal

Forms with typed fields, GPS capture, photographs and sketches, stored locally on the device and pushed to the server when the connection comes back. Edits made by two technicians on the same layer are reconciled, not overwritten.

Map and layer viewing on a phone or tablet

Vector and raster layers from WMS, WMTS, WFS, GeoPackage and MBTiles, with the same symbology and labelling the desk map uses. Base maps can be packaged for download before leaving the office.

GIS data integration

Connecting the field app and the desktop stack to what the organisation already runs: PostGIS, QGIS projects, GeoServer, asset registries, cadastral and utility datasets, CSV and shapefile imports that have to keep their attributes intact.

Custom GIS development

Plugins, processing scripts, server-side services and tailored versions of the field app for a specific survey workflow. We write against open formats and open libraries, so the result can be maintained by someone other than us.

Geospatial consulting

Reviewing a data model, choosing projections and coordinate reference systems, deciding what belongs on the device and what stays on the server, and documenting the decision so the next team inherits a reason rather than a setting.

Ways to work with us

Each engagement starts with a short technical conversation about your data, not a quotation form.

Most requested

Field app deployment

Our open-source mobile app configured around your layers, forms and sync endpoint, then rolled out to the crews who will use it.

  • Project and layer setup
  • Survey forms with validation rules
  • Offline base map packaging
  • Handover session with the field team

Data integration

Getting existing spatial data into one place that both the office and the field read from, without losing attributes or history.

  • PostGIS schema design
  • Shapefile, CSV and GeoPackage import
  • WMS / WFS service publishing
  • Sync rules and conflict handling

Custom development

Software written for one workflow: a plugin, a processing chain, a server component, or a branded build of the field app.

  • Requirements written as test cases
  • Open-source libraries and formats
  • Source code and build instructions
  • Technical documentation

Geospatial consulting

A technical review when the question is what to build, which standards to follow, or why the current setup keeps producing duplicates.

  • Data model and CRS review
  • Field workflow assessment
  • Open-source stack recommendation
  • Written findings you can act on

Scope and timeline are set after we have seen the data model and the field workflow. Ask for a consultation and we will tell you which of these you actually need.

How an engagement runs

  1. Technical call

    You describe the data you hold, the formats it arrives in and what the crew has to do with it on site. We ask about coordinate reference systems early, because that is where most of the pain lives.

  2. Data review

    We look at a sample of the real data — not a cleaned export — and map it against what the field app needs: geometry types, attribute domains, media, and who is allowed to edit what.

  3. Build and pilot

    A configured build goes to a small group first. They take it out, break something, and we fix it before the whole team depends on it.

  4. Handover

    You end up holding the configured project, the source where we wrote custom code, the sync setup and written documentation. Open formats throughout, so nothing is locked to us.

Tell us about your data

Send a short description of the project and a GIS engineer will reply — no sales call in between.

  • An engineer reads it, not a sales desk.
  • First reply asks about your formats, CRS and field workflow.
  • If open-source tools are the wrong answer for you, we say so.