Accurate utility data on site, triggered by a single scan.
This redesigned page presents the QR-Triggered On-Site Utility GIS Portal in a cleaner, more modern, and more readable responsive interface. It is optimized for desktop review, tablet collaboration, and mobile viewing in the field.
Executive summary
The portal replaces fragmented paper-based utility information access with a controlled digital workflow. Engineers on site scan a QR code, open a mobile-ready page, and immediately see the latest approved utility records, context, and action guidance.
Problem
Utility information is often distributed across drawings, emails, marked-up PDFs, and isolated GIS exports, increasing the chance of errors and outdated references on site.
Proposed solution
A QR-triggered portal connected to a GIS-backed publishing process gives each site team a direct path to controlled, location-specific utility intelligence.
Business value
Better visibility reduces field ambiguity, shortens information retrieval time, and improves traceability from survey capture to web publication.
Solution design
The page has been redesigned for comfort and clarity using a soft neutral background, higher contrast content cards, improved spacing, and a more professional font system. The result is easier to read in web viewers without the harshness of pure black or the glare of pure white.
Responsive presentation
- Flexible grid layout that collapses cleanly on tablets and mobile screens.
- Sticky navigation for fast movement across proposal sections.
- Readable card-based content blocks with comfortable spacing and hierarchy.
Visual language
- Background shifted from black to a balanced light slate-grey palette.
- Typography updated to Inter for a cleaner technical and modern feel.
- Soft glass-style panels improve contrast while keeping the page elegant.
Stage 1 — Utility data capture and structuring workflow
This stage defines how a licensed surveyor-led team should collect, structure, validate, and prepare utility information so it can move cleanly into QGIS for management and Lizmap for web delivery. QField is positioned as the practical field collection companion for QGIS-based mobile workflows, while Lizmap is positioned as the web publishing and controlled editing interface.
Survey control and scope definition
Establish project boundary, coordinate reference system, accuracy requirements, utility classes, and mandatory capture attributes before fieldwork begins. Define whether each feature is verified, inferred, exposed, traced, or supplied from legacy records so downstream users can judge confidence appropriately.
QGIS data model preparation
Build the master geodatabase schema in QGIS with separate layers for point assets, linear utilities, chambers, valves, poles, pits, and survey control. Configure attribute forms, default values, domains, and validation-friendly fields so field teams capture structured data instead of free-text notes.
Field collection package deployment
Publish the prepared project to a field-capable workflow so survey crews can capture observations consistently on mobile devices. QField is specifically designed for QGIS-based field collection and synchronization workflows, making it a strong fit for mobile survey capture linked to the desktop project.
Licensed surveyor capture workflow
At each site, collect utility geometry, depth where available, material, size, status, ownership clues, access condition, surface evidence, photos, and confidence notes. Use standardized pick-lists for utility type, survey method, and verification status to keep QGIS analytics and filtering reliable.
QA and reconciliation
Review incoming data in QGIS against base mapping, surveyed control, previous utility records, and topology expectations. Resolve overlaps, disconnected features, attribute gaps, and naming inconsistencies before approving data for operational publishing.
Lizmap publication and controlled editing
Publish approved QGIS projects through Lizmap for web viewing and, where governance allows, enable controlled layer editing from the web interface. Lizmap’s documentation emphasizes project publication from QGIS and supports configuring editable layers and forms for appropriate storage backends.
Recommended architecture
The operational flow should separate field capture, GIS validation, and web publishing so the organization can preserve data quality and auditability while still delivering a fast site experience.
For governance, treat QGIS as the source-of-truth authoring environment, mobile collection as controlled capture, and the QR portal as the delivery layer for approved site-facing access. Where online editing is enabled in Lizmap, use it selectively for operational updates rather than uncontrolled primary survey entry.
User journey
From the perspective of a site engineer, the interaction must stay extremely simple while preserving survey discipline behind the scenes.
Field team and surveyor
- Prepare project, forms, and utility classes in QGIS.
- Collect and validate features in the field using a structured mobile workflow.
- Review and approve data before web publication.
Open the site-specific utility viewer instantly in the browser.
Inspect utility lines, points, notes, and confidence indicators.
Use a live, structured utility reference instead of scattered paper records.
Ready for Cloudflare Worker deployment
This single-file responsive page is suitable for uploading back into the worker deployment workflow and serves as the updated proposal interface with Stage 1 added.