ODK Mobile Spatial Data Collection Training Course

Participants can translate a fieldwork requirement into a structured data model and collection specification.

• Stakeholder interviews identify decisions, indicators, records and required evidence
• Data dictionaries define variables, labels, codes, formats and ownership
• Entity, event and observation records distinguished within field data models
• Unique identifier strategy prevents duplicate assets, households and site records
• Required fields aligned with operational decisions and reporting obligations
• Collection specification documents respondent, location, device and workflow requirements

Participants can create a valid XLSForm using survey, choices and settings worksheets.

• XLSForm workbook structure using survey, choices and settings worksheets
• Question types selected for text, numbers, dates and categorical responses
• List names and choice codes designed for stable data values
• Field labels written for clear enumerator and respondent interpretation
• Form settings configure title, identifier, version and default language
• XLSForm validation identifies structural errors before server publication

Participants can use constraints, relevance expressions and calculations to prevent invalid entries.

• Required responses applied only where missing data invalidates decisions
• Constraint expressions enforce numeric ranges, dates and conditional values
• Relevant expressions control question display through skip logic
• Calculate fields derive totals, ratios, dates and coded classifications
• Constraint messages explain correction requirements in clear field language
• Testing boundary values exposes logic failures before enumerator deployment

Participants can structure complex ODK instruments using groups, repeat sections and controlled workflows.

• Groups organise related questions into readable survey sections
• Field-list appearance places short question sets on one screen
• Repeat groups capture multiple assets, household members or observations
• Repeat counts prepopulate expected records from prior answers
• Nested logic manages conditional sections within repeat structures
• Relevance testing confirms repeat behaviour under alternative respondent pathways

Participants can configure spatial questions and specify appropriate coordinate capture procedures.

• Geopoint questions capture latitude, longitude, altitude and accuracy metadata
• Geotrace questions record linear assets such as roads and pipelines
• Geoshape questions delineate parcels, facilities and affected areas
• Coordinate reference systems explained through WGS 84 mobile positioning
• GPS accuracy thresholds matched to asset type and decision risk
• Location capture protocol addresses sky visibility, averaging and obstruction

Participants can configure map-assisted collection using appropriate basemaps and reference layers.

• Map appearance supports point selection, verification and route awareness
• Offline basemap packages prepared for areas without mobile connectivity
• Reference layers distinguish operational boundaries, assets and collection zones
• GeoJSON layers prepared for compatible mobile map display
• Scale and symbology choices support field interpretation without visual clutter
• Privacy assessment limits exposure of sensitive locations on field devices

Participants can capture supporting evidence and metadata needed for record verification.

• Image questions document asset condition, damage and site evidence
• Audio and video capture assessed against consent and storage requirements
• Barcode questions identify equipment, samples and inventory items quickly
• Device metadata records enumerator, timestamp and submission identifiers
• Audit logs support review of edits, timings and form events
• Media naming conventions preserve links between files and submissions

Participants can create and administer ODK Central projects, forms, users and access controls.

• ODK Central project structure separates programmes, surveys and operational teams
• Form upload process validates XLSForm files and version history
• App users configured for authenticated ODK Collect submissions
• Web users assigned project roles using least-privilege access principles
• Form lifecycle manages draft, deployed, retired and archived versions
• Server settings reviewed for storage, backups and administrative accountability

Participants can configure Android devices and ODK Collect for controlled field deployment.

• ODK Collect project settings connect devices to Central securely
• Blank forms, sent forms and drafts managed on devices
• Device configuration standardises language, time, storage and screen settings
• Managed Android deployment controls application installation and updates
• Battery, power bank and protective case requirements assessed
• Pre-deployment checklist confirms connectivity, forms, maps and permissions

Participants can operate an offline collection workflow and resolve common synchronisation issues.

• Offline workflow plans form downloads, basemaps and delayed submissions
• Submission queue management prevents accidental deletion of unsent records
• Sync procedures address intermittent networks, failed uploads and duplicate attempts
• Device handover logs preserve accountability across enumerator shifts
• Local storage checks prevent media-heavy forms exhausting device capacity
• Incident escalation paths distinguish device, form, server and connectivity faults

Participants can prepare a fieldwork plan that controls collection quality, safety and accountability.

• Sampling frame defines eligible units, selection rules and coverage targets
• Enumerator briefing covers consent, question intent and neutral interviewing
• Daily assignment plans allocate zones, workloads and supervisory checks
• Call-back procedures manage incomplete interviews and inaccessible locations
• Safety protocol addresses travel, communications, weather and incident reporting
• Field supervision plan specifies spot checks, review cadence and escalation

Participants can implement a quality assurance process for incoming spatial submissions.

• Completeness checks identify missing mandatory and conditionally required responses
• Range checks detect implausible measurements, dates and numeric values
• Spatial validation compares locations against expected boundaries and service areas
• Duplicate detection uses identifiers, timestamps, coordinates and respondent attributes
• Outlier review separates valid exceptions from recording or GPS errors
• Review statuses document accepted, corrected, rejected and follow-up records

Participants can export ODK data and prepare it for analysis and GIS use.

• ODK Central exports generate CSV, JSON and media file packages
• Wide and long repeat-group exports selected for analytical requirements
• Data cleaning log records changes, reasons, reviewer and approval
• Codebook maintenance aligns form choices with reporting classifications
• Date, text and numeric fields standardised before downstream analysis
• Sensitive fields removed or pseudonymised before authorised data sharing

Participants can load, inspect and map ODK spatial data in QGIS.

• CSV and GeoJSON imports create spatial layers in QGIS
• Field types and coordinate columns verified before map rendering
• Attribute joins connect submissions with reference boundaries and registers
• Rule-based symbology highlights status, priority and quality exceptions
• Spatial selection identifies records outside assigned collection areas
• Map layouts communicate coverage, findings and outstanding verification tasks

Participants can apply proportionate security, privacy and ethical controls to ODK projects.

• Data minimisation removes fields without a defined operational purpose
• Informed consent wording explains collection, use, retention and withdrawal
• Role-based access limits personal data exposure within Central projects
• Device security applies screen locks, encryption and controlled account access
• Retention schedules define archival, deletion and media disposal procedures
• Risk assessment addresses sensitive populations, locations and field harm

Participants can define reporting outputs that convert collected records into operational decisions.

• Indicator definitions link collected variables to management decisions
• Daily field dashboards track coverage, submissions, errors and productivity
• Exception reports prioritise missing evidence, outliers and unresolved reviews
• Spatial summaries compare results by district, facility, zone or service area
• Data refresh schedule sets responsibilities for exports, checks and reporting
• Feedback loops return findings to enumerators, managers and affected teams

Participants can test an ODK solution, run a pilot and plan controlled scale-up.

• Test cases cover normal entries, edge cases and invalid responses
• User acceptance testing verifies field usability against collection requirements
• Pilot monitoring measures completion time, error rates and GPS performance
• Issue register documents defects, priorities, owners and resolution decisions
• Version control protects deployed forms from untested production changes
• Scale-up plan addresses devices, staffing, support and server capacity

Participants can build, review and present a complete ODK mobile spatial data collection solution for a defined fieldwork case.

• Collection brief defines users, decisions, records, locations and constraints
• XLSForm build combines validation, repeats, media and spatial questions
• ODK Central deployment configures users, form access and project settings
• Device workflow demonstrates offline collection, review and synchronisation procedures
• QGIS quality review maps submissions, exceptions and coverage results
• Presentation defends design choices, controls, outputs and implementation plan