Problem This Talk Addresses
In many organizations, field collection, photo records, route tracking, map editing, spatial analysis, and publishing are handled in separate tools. Field teams capture location, attributes, photos, and movement paths, while office teams later review, interpret, map, and share the same data again. When that process is split across paper notes, messenger attachments, spreadsheets, standalone GIS tools, and web reports, the same information gets re-entered, updates become slow, and the field context is easily lost. The gap becomes even more visible in unstable network conditions. This talk explains how we reduced that gap by connecting a mobile app, a web workspace, and a platform backend into one practical workflow.

What We Built or Applied
- We built gPocket as a field mobile GIS app for collecting and editing spatial data, with encrypted offline storage, project-based working data, GeoPackage working copies that can be modified in the field and reflected back to the server, and tracking records that can be exported as files and reused in external GIS tools such as QGIS.
- We use PINOGIO platform to describe one connected workflow rather than two separate products: pinogio provides the platform core for projects, datasets, layers, maps, geocoding, analysis, and sharing, while pinogio-studio provides the browser-based workspace where people actually organize data, style layers, build maps, and publish outputs.
- We designed pinogio maps not as a simple map viewer, but as a story-map style output where map layers, explanatory text, photos, and interpretive panels can be combined into something readable and shareable.
- We connected all three through open standards and open-source GIS components so they behave like one operational ecosystem.

Outcomes and Lessons Learned
- Mobile and web should not provide the exact same experience; each works better with a focused role.
- OGC standards and GeoPackage made it possible to design online workflows, offline workflows, and file-based interoperability with external GIS tools together.
- Open-source geospatial components can be combined into a product-grade platform.
- The real challenge was not only the GIS engine, but designing a project-centered experience that non-developers could actually use.

What the Audience Will Gain
- A practical architecture pattern for connecting field apps, web tools, and backend GIS services
- A real-world example of turning open-source geospatial building blocks into an end-user product
- Ideas for combining field collection, offline synchronization, web review, analysis, and publishing in one workflow
- A community-oriented perspective on why open standards matter in product design