GIS Case Study
A lightweight Flutter field-survey application for capturing, editing and reviewing georeferenced survey points offline and on.
Domain
Field Data Collection / Survey
Role
Mobile Developer

At A Glance
Survey points captured from the device GPS or entered by coordinate
Free-text remarks recorded against every captured point
All collected points plotted on an OpenStreetMap base layer
Firebase-backed accounts so a surveyor's points follow them across devices
Survey teams were recording georeferenced points in notebooks and transcribing them into a spreadsheet at the end of the day: coordinates read off a handheld GPS, remarks written beside them, and a map assembled later by someone else. Transcription errors were common and the map was always a day behind the fieldwork. Sites were often out of mobile coverage, which ruled out anything that needed a connection to work. The brief was deliberately small: a lightweight app that captures a point from the device GPS or a typed coordinate, records a remark against it, shows everything on a map, and works whether or not there is signal. Small briefs are easy to over-build; the discipline on this one was to stay lightweight.
The app is built in Flutter with Firebase behind it and Flutter Map over an OpenStreetMap base layer. Adding a point is one tap to capture the current GPS location, or manual latitude and longitude entry for planned survey targets. A free-text remarks field is stored with every point. The survey point list supports view, edit and delete, and the map view renders every captured point as a marker. Firebase-backed accounts mean a surveyor's points follow them between devices and are available to the office as soon as they sync. Offline capture writes locally and syncs when connectivity returns, so a day in a valley with no coverage produces the same result as a day in town. The application does one thing and it is fast at it.
The end-of-day transcription step is gone. Points are on the map as they are captured, remarks are attached to the right coordinate rather than a notebook line, and the office sees the survey take shape during the day rather than after it. This project is a useful counterexample to the instinct that every field app needs a form builder, a workflow engine and a reporting suite. It needed reliable capture and reliable sync, built once and left alone. Knowing when a mobile app should stay small is part of building it well.
Capabilities
Add point with one-tap 'get current location' capture
Manual latitude / longitude entry for planned survey targets
Remarks field stored alongside each point record
Survey point list with view, edit and delete actions
Map view rendering every captured point as a marker
Zoom to a saved point directly from the list
Email sign-up, sign-in and password reset via Firebase Auth
Technologies
Product



Questions
Yes. Points and remarks are written to local storage immediately and sync to Firebase when connectivity returns. A full day of capture without coverage is normal use, not an edge case.
Yes. Manual latitude and longitude entry supports planned survey targets, so a team can load the points they intend to visit and then capture the actual GPS position on arrival.
Yes. The survey point list supports viewing, editing coordinates and remarks, and deleting points. Edits sync like new captures. Edit history is retained in Firebase for audit.
A single codebase for iOS and Android, fast native rendering for the map view, and a small application footprint suited the lightweight brief. Flutter Map with an OpenStreetMap base kept the mapping dependency simple and licence-free.
Contact Us
Have a project in mind? Tell us what you're building and we'll get back to you within 12–24 hours with a clear plan.
🔒
100% Confidential
⚡
12–24 Hr Response
🛡️
60-Day Bug Fix
✅
Free Consultation
💬
Start Your Project
Fill in the details below or book a call