Mobile GIS Data Collection Training Course

Duration 10 days 19 modules · 65 contact hours
Level Intermediate Certificate on completion
Who attends GIS Analysts, GIS Technicians and others
Fee from USD 2,200 KSh 190,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-GRS-054

Before you join: Participants should be comfortable using GIS software to view layers, inspect attribute tables, edit simple features and work with common vector formats such as GeoPackage, GeoJSON or shapefiles.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Mobile GIS programmes succeed or fail on the reliability of field evidence. Asset teams, survey crews, humanitarian responders, environmental officers and utility inspectors need to capture locations, attributes, photographs and observations where work occurs, often without dependable connectivity. Poorly designed forms, unsuitable coordinate systems, uncontrolled edits and weak synchronisation create duplicate records, incomplete inspections and maps that cannot support operational decisions.

This course develops the practical methods required to plan, configure and govern mobile GIS data collection. Participants define data requirements, select suitable mobile applications, design field forms, configure offline maps, manage GNSS accuracy and establish quality-control rules. The course covers ArcGIS Field Maps, Survey123, QField and QGIS-based workflows, while teaching principles that transfer to other mobile GIS platforms. Participants also address imagery-assisted field validation, attachment management, synchronisation, user roles, data security and deployment planning.

Teaching combines concise technical briefings with sector cases drawn from utilities, local government, environmental monitoring, land administration and humanitarian operations. Participants configure field-ready forms and maps during the first week, then improve them through data-quality reviews, offline collection scenarios and team workflow design. They leave with a reusable mobile GIS collection package: a requirements brief, data model, form specification, offline map plan, quality-control checklist and deployment plan.

The course suits GIS practitioners and technical professionals who already work with spatial data and need to establish dependable field-to-office workflows. It is particularly relevant where staff collect asset condition records, inspections, survey observations, service requests or monitoring data using smartphones and tablets.

What you will be able to do

  • Define mobile GIS requirements using field workflow mapping and data capture specifications
  • Design spatial data models, coded value domains and validation rules for field collection
  • Configure mobile maps, forms and offline areas for smartphone and tablet use
  • Collect location, attribute, photograph and related-record data using mobile GIS applications
  • Assess GNSS accuracy, coordinate reference systems and positional quality metadata
  • Apply quality assurance checks to identify incomplete, inconsistent and duplicate field records
  • Plan synchronisation, user access, data security and incident-handling procedures
  • Produce and present a complete mobile GIS data collection implementation package

Benefits of attending

For you

  • Build a portfolio-ready mobile GIS collection package for a realistic field operation
  • Configure offline forms and maps instead of relying on paper-based inspection processes
  • Diagnose common GNSS, synchronisation and data-quality problems encountered by field teams
  • Translate operational requirements into clear spatial data and form specifications
  • Lead informed discussions with GIS administrators, survey teams and application vendors

For your organisation

  • Reduce incomplete inspections through required fields, domains and validation constraints
  • Improve asset and monitoring records with controlled locations, photographs and timestamps
  • Shorten field-to-office reporting cycles through synchronised mobile data workflows
  • Support field operations in low-connectivity areas using tested offline map procedures
  • Establish repeatable governance for mobile users, edits, quality checks and data publication

Course modules

19 modules over 10 days

Participants can map a field-to-office GIS workflow and identify its control points.

  • Mobile GIS architecture: devices, applications, services, storage and synchronisation
  • Field-to-office workflow mapping using swimlane diagrams and data handoffs
  • Collection scenarios: assets, inspections, surveys, incidents and environmental observations
  • Roles of field users, reviewers, GIS administrators and data owners
  • Paper, spreadsheet and mobile workflows compared through error sources
  • Success measures for completeness, timeliness, positional quality and acceptance

Participants can specify coordinate reference systems and positional quality requirements for mobile collection.

  • Coordinate reference systems selected for local accuracy and organisational interoperability
  • WGS 84 latitude-longitude coordinates versus projected metre-based coordinate systems
  • GNSS accuracy, precision, repeatability and confidence reported correctly
  • Horizontal accuracy metadata captured using estimated accuracy and correction status
  • Datum transformations documented when combining legacy surveys and mobile observations
  • Multipath, canopy and urban canyons assessed before field deployment

Participants can produce a structured requirements brief for a mobile GIS collection service.

  • User stories written for inspectors, surveyors, supervisors and data reviewers
  • Business rules translated into required fields, domains and conditional logic
  • Minimum viable dataset defined using purpose, decisions and reporting needs
  • Field workflow observations converted into functional and non-functional requirements
  • Data sensitivity classified for public, internal, restricted and personal information
  • Acceptance criteria specified for forms, maps, synchronisation and exports

Participants can evaluate mobile GIS platforms against operational, technical and governance criteria.

  • Platform evaluation matrix covering offline capability, licensing, security and integration
  • ArcGIS Field Maps, Survey123 and QField compared against collection requirements
  • Device operating systems assessed for management, peripherals and application support
  • Web maps, feature services and local packages distinguished by connectivity needs
  • Licensing assumptions documented for creators, editors, viewers and contractors
  • Proof-of-concept scope defined before enterprise deployment decisions

Participants can design a field data model that supports reliable collection and reporting.

  • Feature classes, tables and relationships modelled for assets and inspections
  • Unique identifiers assigned using organisational conventions and lifecycle requirements
  • Coded value domains standardise condition, status, priority and inspection outcomes
  • Subtypes separate asset categories with distinct attributes and validation rules
  • Null values, unknown values and not-applicable values treated separately
  • Field names, aliases and definitions documented in a data dictionary

Participants can build efficient mobile forms with clear validation and conditional logic.

  • Form sections group related observations into logical fieldwork sequences
  • Required fields applied only where operational evidence is genuinely necessary
  • Conditional visibility displays follow-up questions after relevant response selections
  • Constraint expressions prevent invalid dates, ranges, codes and text entries
  • Default values populate inspector identity, dates and recurring observations
  • Choice lists designed for rapid selection and consistent reporting categories

Participants can configure field maps and offline areas suited to a defined collection territory.

  • Operational layers prioritised by field decisions, scale ranges and refresh frequency
  • Basemap selection balances legibility, storage size, licensing and offline availability
  • Offline map areas prepared for districts, routes, sites and survey zones
  • Scale dependencies control layer visibility and reduce mobile rendering load
  • Pop-ups configured to display identifiers, status, history and priority information
  • Map symbology designed for daylight viewing and rapid feature recognition

Participants can collect and edit field records using controlled mobile GIS procedures.

  • Point, line and polygon capture methods matched to real-world feature geometry
  • Location averaging used when stationary observations require improved positional confidence
  • Existing features searched, identified and updated before creating new records
  • Collection statuses distinguish draft, submitted, reviewed, approved and rejected records
  • Field notes record anomalies, access constraints and interpretation decisions
  • Daily operating procedures cover device checks, downloads, backups and charging

Participants can select GNSS collection methods and document accuracy limitations.

  • Integrated smartphone GNSS assessed against task-specific positional accuracy thresholds
  • External Bluetooth GNSS receivers paired, configured and tested with mobile applications
  • Satellite geometry and dilution of precision interpreted for collection decisions
  • Real-time correction services compared with autonomous GNSS positioning methods
  • Occupations repeated where accuracy thresholds or audit requirements demand evidence
  • Metadata records receiver type, correction source, accuracy estimate and collection method

Participants can manage supporting evidence linked to mobile GIS features.

  • Photo capture standards specify framing, orientation, naming and evidence requirements
  • Attachment limits set for file types, sizes, retention and synchronisation capacity
  • Related tables record repeated inspections, repairs, samples and observations
  • Barcode and QR code scanning connect assets with authoritative identifiers
  • Image metadata reviewed for timestamps, location details and privacy risks
  • Evidence chains preserve links between field records, photographs and follow-up actions

Participants can prepare a QGIS project and QField package for offline field collection.

  • QGIS project properties set for coordinate systems, layer paths and metadata
  • GeoPackage layers configured for editable features, domains and related records
  • QField forms created using drag-and-drop widgets and value relation controls
  • Default expressions populate dates, usernames, identifiers and calculated values
  • QFieldCloud synchronisation considered for shared projects and controlled publishing
  • Packaging procedures verify local layers, basemaps, forms and attachments

Participants can establish QA and QC controls for field-collected spatial data.

  • QA plans define standards, responsibilities, checkpoints and acceptance thresholds
  • QC checks identify missing attributes, invalid domains and duplicate features
  • Topology rules test overlaps, gaps, dangles and containment relationships
  • Sampling plans target high-risk records for supervisor review and verification
  • Exception reports classify errors by severity, owner, correction and closure
  • Audit trails retain editor, timestamp, source and status information

Participants can manage synchronisation, edits and review workflows across mobile field teams.

  • Synchronisation patterns distinguish download, upload, bidirectional sync and manual transfer
  • Conflict policies define treatment for concurrent edits and deleted features
  • Versioned editing concepts support controlled review before authoritative publication
  • Submission queues monitored for failed uploads, partial transfers and duplicates
  • Reviewer workflows validate records before status changes and downstream reporting
  • Recovery procedures address lost devices, corrupt packages and interrupted synchronisation

Participants can use imagery and remote sensing products to prepare and validate field collection.

  • Recent imagery used to identify access routes, change areas and priority sites
  • Field maps combine orthophotos, satellite imagery and authoritative reference layers
  • Image dates, resolution and cloud cover assessed before operational use
  • Visual interpretation keys distinguish land cover, infrastructure and disturbance features
  • Ground-truth observations designed to validate image classifications and mapped changes
  • Field evidence linked to imagery interpretations through documented observation codes

Participants can apply security, privacy and safety controls to a mobile GIS operation.

  • Role-based access controls restrict viewing, editing, downloading and administration privileges
  • Mobile device management policies address encryption, passcodes, updates and remote wiping
  • Personal data minimisation reduces unnecessary names, contacts and sensitive locations
  • Retention schedules define archival, deletion and evidence preservation requirements
  • Field safety plans identify communications, check-ins, hazards and emergency procedures
  • Consent procedures document lawful collection of photographs and personal information

Participants can plan a controlled rollout of a mobile GIS collection service.

  • Pilot deployment plans define users, geography, duration, measures and decision gates
  • Training materials separate field-user, supervisor, reviewer and administrator responsibilities
  • Standard operating procedures document collection, review, correction and escalation steps
  • Change requests assessed for data-model, form, map and reporting impacts
  • Release management schedules testing, approval, publishing and user communications
  • Support models define service desk routes, response targets and knowledge articles

Participants can define monitoring measures and reporting outputs for mobile GIS operations.

  • Collection dashboards track submissions, completion rates, backlog and geographic coverage
  • Data-quality indicators measure missing values, invalid codes and review rejection rates
  • Field productivity measures distinguish travel time, collection time and revisits
  • Service-level metrics monitor synchronisation latency, outages and support incidents
  • Management reports connect field evidence with maintenance, compliance and budget decisions
  • Continuous improvement reviews convert recurring errors into configuration changes

Participants can evaluate whether a mobile GIS configuration is ready for operational deployment.

  • Readiness checklist reviews requirements, forms, maps, devices, users and support
  • Test scripts verify expected workflows, validation rules, attachments and offline behaviour
  • Usability reviews identify unclear labels, excessive steps and fieldwork bottlenecks
  • Risk registers assess technical, operational, security and adoption exposures
  • Deployment decisions documented as approve, revise, pilot extension or defer
  • Implementation roadmaps sequence configuration, testing, training and operational handover

Participants can build, review and present a complete mobile GIS data collection package for a defined operational case.

  • Operational case requirements translated into a field collection service specification
  • Spatial data model, domains, relationships and identifiers documented for approval
  • Mobile form and map configuration prepared for online and offline collection
  • Quality-control plan defines validation rules, review stages and exception handling
  • Deployment plan addresses users, devices, training, security and support arrangements
  • Peer review tests workflow fit, data quality and implementation risks
  • Final presentation justifies design decisions using operational requirements and evidence

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Mobile GIS requirements brief template
  2. Field data model and data dictionary
  3. Mobile form specification with validation rules
  4. Offline map preparation checklist
  5. Field data QA and QC plan
  6. Mobile GIS deployment roadmap

Who should attend

  • GIS Analysts — configure mobile collection workflows and maintain authoritative spatial datasets
  • GIS Technicians — build forms, maps and validation rules for field teams
  • Survey Supervisors — improve positional accuracy, inspection consistency and field productivity
  • Asset Management Officers — capture reliable condition and maintenance records for infrastructure
  • Environmental Monitoring Officers — standardise site observations, photographs and sampling locations
  • Humanitarian Information Managers — establish offline-ready field data collection for response teams

Skills and tools covered

Mobile GIS configurationField form designOffline map managementGNSS quality controlSpatial data validationField workflow planning

Tools and standards

ArcGIS Field Maps, ArcGIS Survey123, QGIS, QField

How the course runs

Training methodology

The course uses short instructor briefings followed by configuration tasks, case analysis and structured group reviews. Participants work with realistic inspection, asset inventory, environmental monitoring and field survey scenarios. They design forms, prepare offline maps, collect sample records, review positional quality and resolve synchronisation issues. Facilitated simulations address field constraints such as weak connectivity, conflicting edits and incomplete submissions. Each participant develops an application plan that can be adapted to their own collection process after the course.

Requirements and prerequisites

Participants should be comfortable using GIS software to view layers, inspect attribute tables, edit simple features and work with common vector formats such as GeoPackage, GeoJSON or shapefiles. Familiarity with basic coordinate reference system concepts and spreadsheet data is expected. Previous exposure to QGIS, ArcGIS Pro or ArcGIS Online is useful, but expertise in every platform is not required. No programming, database administration, advanced remote sensing, surveying licence or prior mobile application configuration experience is required. Participants should bring examples of a field collection process where possible.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

Participants should already be able to use GIS software for basic mapping, layer inspection and simple editing. The course explains mobile configuration methods from first principles, so previous Field Maps, Survey123 or QField experience is not required.

A laptop capable of running the selected GIS software is recommended for classroom delivery. Participants may also bring an Android or iOS smartphone or tablet, although trainer-provided demonstrations and shared scenarios can be used where devices are unavailable.

It is intended for GIS analysts, GIS technicians, survey supervisors, asset managers and monitoring officers responsible for field data processes. It is also suitable for managers who need to commission or govern a mobile GIS implementation.

General GIS courses focus on mapping, spatial analysis and desktop workflows, while remote sensing courses focus on interpreting imagery and derived products. This course concentrates on configuring and governing field-to-office data collection using mobile applications.

Participants can adapt the requirements brief, form specification, offline map checklist and QA plan to an existing inspection, survey or monitoring process. The methods apply to assets, environmental observations, land records, humanitarian assessments and service-request capture.

The first week establishes requirements, data models, forms, mobile maps, offline collection and GNSS procedures. The second week covers quality control, synchronisation, imagery support, security, deployment, operational monitoring and the final capstone presentation.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.