Capture the location and the project context together
Surveyors and rollout contractors need more than a line on a map. Route observations and site records must remain useful when the project moves into measurement, execution and handover. Lumacorp connects geo-tagged capture, network site records and route kilometre surveys to the central GIS record.
A connected survey workflow
- Capture the route and the associated site observations.
- Map field data as it is captured, without a separate re-entry step.
- Measure and review route kilometres against the relevant project scope.
- Generate measurement sheets and KML/KMZ files from the field records.
- Hand the mapped information to execution and inventory workflows.
Documents from the same source record
Measurement sheets support review of surveyed work. KML/KMZ files provide a geographic output that can be shared with tools supporting those formats. These are different outputs from the same capture process; neither should be treated as automatic acceptance of executed work.
Download an illustrative KML route or sample measurement CSV. Both use fictional project identifiers and demonstration values, not customer records. See the KML vs KMZ guide for format differences.
Questions to settle before a survey starts
How are route lengths reviewed?
Agree the measurement method, unit, route boundaries and reconciliation process for the project. Retain the distinction between surveyed length, executed length and commissioned length.
Does capture work offline?
Confirm supported devices and offline or synchronization behavior in your demonstration. Offline operation is not established by the supplied product description.
Can we specify a capture interval?
Discuss the spacing of observations and exception handling for your survey. Record spacing describes how often data is captured; it is not a statement of positioning accuracy.
Workflow schematic. This explains the data handoff; it is not a product screenshot.