Engineering case 2024 — 2026
Offline-first fieldwork & GIS
The connection ends. The work continues.
An Android application that brings spatial data into the field, combining maps, layers, and inventory workflows with offline operation.
The stack on record
Client data and source code are private, so there are no screens. The stack below is drawn only from the project record's technology list, grouped by known categories.
- PlatformAndroid
- LanguageJava
- DataSQLite
- IntegrationREST API
- MapsOSM / OSMdroid
- Backend.NET
The problem
Field teams need to work with large volumes of GIS data under limited connectivity. Presenting different data layers clearly on a map is one of the core requirements.
My role
I handled technical analysis, development, and performance optimization for the Android application. I developed drawing, pin placement, custom marker, and KML/Shape processing workflows with OSM/OSMdroid and Google Maps.
Data and connectivity
SQLite and an offline-first structure supported continued work in the field when connectivity was limited. I also worked on mobile-to-backend data flows through .NET REST APIs and Oracle PL/SQL procedures.
Managing complexity in the interface
Underground layer visibility, inventory tags, and layer controls focused on making spatial data usable.
Boundaries
Internal datasets, coordinates, and screenshots are not shared. No unverified claims are made about the synchronization algorithm or measured latency. The map shown here is an illustration containing no real field data.
Let's work on a system like this.
Nihat Akbuğa · Senior Mobile Software Engineer