GIS and CAD Data QA
Check map and design data for staleness and conflicts before it reaches the field.
What It Does
The agent checks GIS and CAD layers for stale records, missing attributes, and conflicts, flags each with its location, and prepares them for a person to clear.Without it: Outdated or incorrect map data drives design-to-field mismatches. The errors are hard to catch by eye across large datasets.
- Runs the rule set your data stewards wrote, and names the rule on every flag
- Duplicate geometry across two layers is reported once, with both feature IDs
- Assets missing from the asset register are separated from assets with bad attributes
- Flags queue with a severity and an owning layer; nothing is corrected in place
Illustrative example
A refreshed pole layer is published for the eastern district. The agent runs it against the steward rules and opens flags in three groups: 14 poles with no owner attribute, 9 duplicated between the pole and joint-use layers, and a conduit run carrying a 2019 survey date beside a design from this year. Each flag names its rule and feature ID, and the GIS lead clears the queue before the data reaches the field.
GIS
Published layers, geometry
CAD files
Released design layers
Asset register
Which assets exist
Steward rules
The checks to run
GIS and CAD data QA
WatchStarts when
A dataset is published, or a design is released to the field
How far it goes
it flags and records, and takes no action itself
Quality flags
Raised per rule
Located issues
Pinned to feature IDs
Clearing queue
Queued by severity
More Telecom Agents
Design-to-field reconciliation
Reconcile planned routes against field survey data and flag conflicts before crews build the wrong thing.
Field redline and note interpretation
Read field redlines and notes and structure them into proposed design changes for an engineer to approve.
Survey-correction triage
Process survey corrections, identify the affected route segments, and queue them for revalidation.