Service · App development

Custom geo (geographic) app development.

A custom app for everything involving location, maps and spatial data. Field surveys, asset tracking, ecological research, indoor positioning, smart city and real-time fleet tracking, built on a mapping stack that fits your data and your industry. Native for iOS and Android, with offline tiles and GIS integrations.

Mapbox & LeafletPDOK & ESRIOffline tilesGeoJSON & shapefile

A geo app is more than a map with points.

A geographic app, or geo app for short, ties your workflow to the place where it happens. For a field surveyor, that means a form that attaches itself to the polygon of the plot they are standing on. For a fleet coordinator, it means 280 vehicles moving across a map in real time, with geofences around warehouses and customers. For a municipal enforcement officer, it means an enforcement report that lands as a GPS point on PDOK's public space layer. In each case, the map is not decoration but the heart of the workflow.

Most industry software has a blind spot here. A standard CRM or ERP is about customers and hours, not coordinates, projections or indoor routing. Anyone who tries to squeeze a geo workflow into a generic package ends up with disconnected mobile forms plus a GIS file that has to be converted manually at the end of the day. Not because it cannot be done, but because spatial data has a fundamentally different structure from tables with rows and fields.

We build custom geo apps for organisations where location is essential to the workflow itself, not as reporting after the fact, but as guidance during the work. That means a stack in which Mapbox, Leaflet, ESRI or PDOK runs directly in the app, integrations with your existing GIS or CAD environment, and an offline mode that genuinely works offline. For field surveys in a nature reserve with no signal, for inspection rounds in an underground car park, and for archaeological work where uploading to a server is simply not an option.

Geo often overlaps with other disciplines within app development: a field service app quickly gains a map layer, logistics planning calls for routing, and an asset management system relies on location. We carry those lines through so that the mapping layer does not become a standalone module but is woven into the entire application. For the overlap with inspection and technician workflows, see also our page on field service apps, as many geo projects are effectively an extension of those.

Three common forms.

Which form suits your organisation depends on who works with the map, whether the data originates indoors or outdoors, and which mapping stack you already have in place. In the first conversation we advise which variant will deliver the most.

Compact project · fixed sprint budget

Field survey and site recording app

A mobile app that lets ecologists, archaeologists, valuers or vegetation surveyors capture points, lines and polygons in the field, with photo attachments and forms that differ per object type. It works offline on a pre-downloaded map area, syncs as soon as there is a network again, and exports directly to GeoJSON, shapefile or a GIS platform such as QGIS or ArcGIS Online. Often with automatic GPS accuracy detection and the option to achieve sub-metre precision with an external GNSS receiver.

Offline tilesGeoJSON exportGNSS integrationQGIS publishing
Mid-sized project · fixed sprint budget

Asset tracking and fleet app

For logistics, recycling, gritting, waste collection, technical maintenance or construction equipment: a live map of all your vehicles, machines or containers, with geofences around warehouses, customers and project areas. Push notifications when an asset enters or leaves a geofence, automatic trip logging, mileage reporting and an integration with your fleet or ERP system. For the transport side of this story we often build on the approach from our transport software practice, because geo and planning form a single whole there.

Real-time trackingGeofencingMapbox & MaptilerTrip logging
Larger project · fixed sprint budget

Smart city and public space app

For municipalities, water boards, environmental agencies and provinces: an app that links public space reports, asset inspections or resident feedback to the official map layers of PDOK, BAG, BRO and the Land Registry (Kadaster). With an accessible public version for residents and a professional section for enforcement officers. INSPIRE-compliant where public notices are concerned, with an audit log for enforcement procedures, and interoperable with your GIS environment. Overlaps with our experience in software for municipalities.

PDOK & BAGINSPIRE-compliantAudit logPublic version

What a geo app can do as standard.

The functional layers that recur in almost every geo project, whether you have field research, asset tracking or smart city in mind. Each time, we adapt this foundation to your industry, your data and your existing GIS environment.

  • Multi-stack mapping engineA mapping layer that works with Mapbox GL, Maptiler, Leaflet on top of OpenStreetMap, Google Maps or ESRI ArcGIS, depending on your licences, target audience and map style. Together we choose what fits and build the app so that the underlying tile providers can be replaced later without a redesign.
  • Importing vector and raster dataNative support for GeoJSON, shapefile, KML, GeoTIFF, GeoPackage and CSV with coordinates. Heavy datasets are tiled client-side and only relevant features are rendered, so even thousands of polygons run smoothly on a phone.
  • Offline tiles and offline dataThe employee selects a work area in advance and downloads tiles plus features locally. In the field, the app then works fully offline, even deep in a nature reserve, in a factory hall or on the Wadden Sea. Synchronisation happens automatically as soon as there is a connection again, with conflict resolution for objects that were edited by several field workers at the same time.
  • GPS accuracy and GNSS supportFor most use cases, a device's built-in GPS chip is sufficient, using CoreLocation on iOS and the Fused Location Provider on Android. For sub-metre or centimetre precision, we connect external GNSS receivers via Bluetooth (Trimble, Emlid, Septentrio), with RTK correction via an NTRIP stream.
  • Routing and navigationRouting on public roads via the Mapbox Directions API, Google Directions or OSRM, plus off-road routing for sites without roads. For multi-stop fleet flows, the app generates an optimised sequence with estimated arrival times and recalculates when there are traffic jams or road closures.
  • Geofencing and triggersDraw polygons around warehouses, customer locations, project areas or nature zones. The app responds when a user or asset enters or leaves them: by suggesting a form, sending a notification to the office, or starting time tracking. Works in the background, even when the app is not open.
  • Indoor positioningFor situations without GPS coverage: indoor positioning based on Bluetooth beacons, Wi-Fi fingerprinting or a BIM model (IFC) of the building. Suitable for warehouse picking, hospital routing or inspections in tunnels and car parks.
  • AR overlayWith ARKit (iOS) or ARCore (Android), we can use the camera to overlay underground cables, pipes, archaeological layers or planned buildings onto the real world. Especially useful for excavators, designers and public-facing applications in public spaces.
  • Integration with your GIS environmentTwo-way integration with QGIS, ArcGIS Online, GeoServer or your own PostGIS database. Whatever is captured in the field appears immediately on your map at the office, and whatever the GIS analyst draws lands straight away as a layer on the devices in the field.
  • GDPR-compliant location handlingLocation data of individuals is special-category personal data under the GDPR. We build consent flows, data minimisation and retention periods directly into the app, with an audit log of when location is and is not collected. Also for fleet flows with vehicles assigned to individuals and for public apps in which residents share their location.
  • Maintenance contract (optional)Ongoing maintenance, OS updates, security patches and further development for a fixed monthly price. We can include tile licences, GNSS firmware updates and GDPR reviews.

When a geo app is the right choice.

Not every work process involving a map needs its own geo app: sometimes a dashboard in QGIS or a feature layer in ArcGIS Online is enough. Six signals that custom geo software really pays off.

Fieldwork

Data originates outside the office

Your inspectors, ecologists or supervisors record on site the facts that later end up in a report or analysis. The less they note down in the field and the more they retype later, the more noise creeps into the final reporting, and the longer the lead time. A geo app captures it at the point of observation.

Offline

No or poor network in the work area

A nature reserve, underground infrastructure, a storage shed, a remote construction site: wherever the mobile network is patchy or absent, a browser-based GIS tool fails. Built natively, with pre-downloaded tiles and local storage, the app keeps working.

Volume

Many objects or many fields

A ranger measuring thirty tree trunks a day, a harbour master registering a hundred containers an hour, an enforcement officer carrying out six inspections in a morning: the seconds per registration add up. A purpose-built flow is then much faster than a generic "add point" button in an off-the-shelf package.

Compliance

INSPIRE or audit log required

Government work calls for a traceable chain: who made which registration, with what accuracy, and is it still valid? INSPIRE-compliant metadata, an immutable audit log and feature versioning are not standard in every package; custom development solves this in one go.

Integration

GIS platform is not the single source

You have your map data in ArcGIS, but your core data sits in an ERP, a BIM server or a specialist application. Standard mobile GIS clients only connect to their own platform. A custom app pulls features from multiple sources and presents them as a single layered map.

Branding

Public or partner experience matters

A citizen reporting app, a walking tour, a property search app or a tour of a nature reserve: when end users (not GIS professionals) use the app, the interface needs to follow your brand identity and avoid technical jargon. A white-labelled version of a GIS platform rarely reads as your brand.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a geo app project works.

1

Introduction and data scan

A conversation in which we map out your workflow and look at the data you already have: which map layers, in which projection, with which metadata. We review your existing GIS environment, tile licences and any PDOK or ESRI subscriptions, and indicate what can be reused and where new layers are needed.

2

Field research and stack selection

Depending on your use case, we spend a day joining a field survey, shadowing a fleet coordinator or following an inspector. Based on that, we choose the mapping stack (Mapbox, Maptiler, Leaflet, ESRI or a combination), the cross-platform approach (Flutter, React Native or native iOS and Android) and the backend architecture. We test the first wireframes with two or three end users before we start building.

3

Building in sprints

Every sprint, we deliver a working version on your own devices. We start with the mapping engine plus one primary flow (for example, a field form attached to a geometry), so you can test on real locations as early as possible. After that, we build out offline tiles, integrations and the associated role-based flows. You test along with us, end users in the field test along with us, and we adjust continuously.

4

GIS integration and rollout

We test the integrations with your GIS platform or database first in a staging environment with representative data, then with a pilot group of a few field workers. We check projections, transformations between RD-New and WGS84, and behaviour when network connections drop. This includes training sessions for planners and GIS analysts, plus a short instruction video for end users.

5

Management and further development

After go-live, we support you with monitoring, OS updates for iOS and Android, security patches, GNSS firmware checks and further development. Many geo apps grow organically, with new map layers, new regions or a second industry use case, and a maintenance contract keeps that running smoothly without you having to start a new project each time.

Frequently asked questions.

The questions clients ask when they are considering a geo app.

Which mapping stack do you usually choose?
That depends on the use case. For consumer and public-facing apps, we often work with Mapbox GL or Maptiler because of their attractive vector styling and reasonable licence costs. For public sector projects, we usually choose Leaflet on top of OpenStreetMap or a combination with PDOK tiles, because that is licence-free and interoperable. For organisations that have already invested heavily in ESRI, we connect to ArcGIS Online or ArcGIS Enterprise. We use Google Maps where recognisability matters more than customisation. We always advise based on your data, target audience and existing contracts, not on what we happen to be used to.
How accurate is the location in the app?
With the standard GPS chip in modern smartphones, you typically get three to five metres of accuracy in the open air, slightly less in urban areas. For field surveys, archaeology or cable and pipeline work, that is sometimes not enough, so we connect external GNSS receivers such as the Trimble Catalyst, Emlid Reach or a Septentrio Mosaic via Bluetooth. With RTK correction via an NTRIP stream, you can then achieve centimetre-level precision. The app automatically falls back to the built-in GPS if the external receiver is not available.
Does the app really work offline in an area without a network?
Yes, and for most of the geo apps we build it is a core requirement. We download tiles and feature data to the device in advance, store all work orders, photos and measurements locally in an SQLite or MMKV store, and synchronise via a queue as soon as the network is back. Conflict resolution for objects touched by several field workers at the same time is part of the design by default. We test this in every sprint in airplane mode and on poor 4G, not just on fast office Wi-Fi.
Can you integrate with our GIS environment?
In practice, almost always. For Esri: ArcGIS Online via REST services, or ArcGIS Enterprise. For open-source stacks: GeoServer with WMS, WFS or WMTS, or a direct PostGIS database. For QGIS publications: an intermediate step via a WFS feed or an exported GeoPackage. For PDOK data: the open WMS and WFS services. We build two-way integrations where that makes sense, so field captures land automatically in your office GIS and vice versa.
What about GDPR when it comes to people's location data?
A person's location is classed as special-category personal data under the GDPR, especially when it is collected continuously or in real time. We build consent flows, data minimisation and retention periods directly into the app, with an audit log of when and why location is collected. For fleet applications with vehicles assigned to individuals, we work with works council agreements and privacy-by-design principles. For projects involving the location of patients, pupils or residents, we carry out a DPIA as standard. We work with your privacy officer or DPO to get the legal details right.
How do you combine a geo app with AI or image recognition?
Organisations increasingly want a photo taken in the field to be categorised or analysed automatically: an ecologist photographs a plant and instantly gets the species back, an inspector registers waste and has the type detected automatically, a property valuer photographs damage and receives a first estimate. We build this as a separate AI layer on top of the geo app, with models running on-device or in the cloud depending on privacy and data volume. For our approach and the possibilities, see our page on AI development.
What is INSPIRE, and do we need to comply with it?
INSPIRE is a European directive that requires public-sector organisations to publish certain spatial datasets in a standardised format with standardised metadata. If you are a municipality, water board, province or regional environmental agency working with public spatial data, it generally applies to you. We make sure your app's data export produces the right GML or GeoJSON formats, with metadata in the ISO 19115 format. INSPIRE usually does not apply to private parties, but interoperability with PDOK datasets is often still desirable.
Can you do indoor positioning without GPS?
Yes. We place Bluetooth beacons (from vendors such as Estimote or Kontakt.io) at fixed positions, and triangulation gives a position accurate to within a few metres. For larger buildings we use Wi-Fi fingerprinting on top of existing access points. For BIM-driven routing, we load an IFC model into the app, so users can navigate through a 3D representation of the building. Indoor positioning works best for organisations with fixed physical infrastructure: warehouses, hospitals, stadiums, car parks.
Native or cross-platform?
For geo apps we usually choose Flutter or React Native, because the mapping libraries (Mapbox GL Native, MapLibre, Leaflet via webview) work comparably on both platforms and you keep a single codebase. For projects with very heavy graphics requirements or very specific hardware integrations, such as deep integration with an external GNSS receiver via a proprietary SDK, we sometimes choose native iOS (Swift with MapKit/CoreLocation) and native Android (Kotlin with the Maps SDK). During discovery we discuss what fits your requirements and existing engineering capacity.
Who manages tile licences and hosting costs?
That is part of the maintenance contract if you take one out. Mapbox, Maptiler and Google Maps use a usage-based model (per map load or per tile request), whereas ESRI works with named users. We monitor usage, scale the plan up or down, and give you monthly insight. For public-sector projects we use PDOK tiles wherever possible because they are licence-free, with a commercial provider as a fallback for specific styles or regions.
Do you also work with our own GIS analysts or developers?
Yes, on geo projects that is the rule rather than the exception. Many clients have a GIS team that handles the data layer and analyses, while we build the mobile layer and, where needed, the APIs in between. We work in the same Git repository, align with your projections and data models, and do pair programming where it speeds up knowledge transfer. By the end of the project, your own team can maintain the codebase completely independently, with no lock-in to us as a supplier.

Talk to us about your geo app.

A no-obligation introductory call of half an hour. We listen to your workflow, look at the map layers and data you already have, and give you direction that is actually useful, even if the advice is to get further with QGIS, ArcGIS Online or a PDOK viewer first, until custom development pays off. For related topics, see our broader app development service, our page on field service apps, our experience with transport software for asset tracking, our projects in software for municipalities and the application of AI development to geo data.

Edit content