GIS server and network mapping

A shared map for the people delivering the network

Survey teams, project managers and operations teams need to work from the same route and asset context. Separate drawings and spreadsheets can make it difficult to tell which record should inform the next decision. Lumacorp’s central GIS server holds routes, assets and topology, connecting field capture with the rest of the network lifecycle.

From field capture to the mapped record

1. Capture location-linked route and site information in the field.
2. Map the captured data without a separate re-entry step.
3. Use route and asset context to support measurement, execution review and operational work.
4. Maintain the record as installation and network operations progress.

Inputs and outputs

Inputs include surveyed routes, site observations and asset records. The shared map provides the geographic context for route measurement, active and passive inventory, execution tracking and fault location. Measurement sheets and KML/KMZ outputs are part of the connected survey workflow.

The map is the common reference, while individual modules handle the tasks around it. A progress update, an asset record and a fault ticket have different purposes even when they refer to the same location.

What to review in a demonstration

Bring a representative route and the records you need to manage. Review how captured data appears on the map, how teams identify the relevant segment or site, and how the next workflow uses that context.

Can we import an existing network?

Discuss your current formats, coordinate systems, data quality and topology with the team. Supported imports and migration arrangements need to be established for your dataset.

Which hosting and access options are available?

Confirm deployment, permissions, update behavior and retention requirements during scoping. Specific hosting or security guarantees should be agreed for your implementation.