GIS consulting for local government, utilities and engineering firmsServing clients across the United Statesinfo@infraspatialsolutions.com

GIS Data Quality & Workflow Automation

Check your GIS data.
Know what needs attention.

InfraSpatial Solutions automates the checks your team repeats when GIS data is updated or delivered. We identify records that need review and provide a clear report showing what was flagged, why, and where to find it.

See a working example
Public-data demonstration · Salisbury area, North Carolina
U.S. Census Bureau road features. No client data or simulated defects.

Less time searching.
A clear starting point
for review.

The problem

Each new GIS data delivery can mean checking hundreds or thousands of records again. Staff need to find missing information, repeated identifiers and records that do not meet the requirements of the job.

What we do

We agree the checks with your team, build a repeatable script or tool, and test it against representative data. Each run identifies the records that match those rules and explains why they need attention.

What your team receives

A reusable checking tool, a record-by-record review report, and instructions for running the checks on the next delivery. Your team reviews the findings and decides what to correct or accept.

A working example: reviewing road data.

Suppose a team needs a road layer with names for its map. Before using a new dataset, it needs to find the features without names and decide whether those features belong in that layer.

We ran the check on 402 public Census road features. It identified 5 local roads without a name and produced a review list linked to their locations. Another 11 unnamed features are ramps, alleys, service drives and internal Census lines, where a blank name is normal, so they were counted but not flagged. The map below lets you inspect the actual records.

An unnamed road may be valid, so nothing was corrected automatically; each flagged record waits for a person to decide.

From public source to reviewable output.

  1. 01

    Capture

    Save the source response, query extent and file fingerprint.

  2. 02

    Check

    Inspect identifiers, names on road classes that need them, classification presence and basic line geometry.

  3. 03

    Review

    Locate flagged records and decide whether each is suitable for the intended use.

  4. 04

    Deliver

    Export the review queue and retain the script and source snapshot.

The capture, check and delivery steps ran for this demonstration; the review step is left to the data owner.

Executed Python check / saved public-data snapshot

See which records need review.

Choose a review group or road class. Select a record to see its original attributes and location.

402features checked
5name-review candidates
397records with no flags under these rules

Loading saved results…

Salisbury areaNorth
Context roadsFiltered recordsSelected record

Source geometry in the query area; map view clipped to the study box. This is not a routing or navigation map.

The browser explores results computed by the downloadable Python script. It does not run ArcGIS or change the source data.

What this example found.

Names

5 local roads have an empty NAME value and are listed for review. Names are checked only on road classes that normally carry one (S1100, S1200, S1400), so 11 unnamed ramps, alleys, service drives and internal Census lines were not flagged. No replacement names were invented.

Identifiers & classification

No missing or repeated OID values and no empty MTFCC values were found in this extract. Classification codes are retained as supplied; this is not a full domain-compliance check.

Basic geometry

No empty paths, invalid coordinate ranges or zero-length lines were found by the script. Network connectivity, positional accuracy and road topology were not tested.

Inspect the source. Reproduce the result.

Save the source snapshot, source record and Python script into one folder, then run python check_roads.py. The script verifies the source fingerprint and writes results.json and review.csv. It uses Python’s standard library.

To reproduce the run, the required inputs are source.json, provenance.json and check_roads.py; the CSV is the existing output for comparison.

Source, scope and reproducibility

The query selects features intersecting a bounding box, not the administrative city boundary. Features retain their original, unclipped geometry in the saved response. Identifiers locate records in this snapshot; stability across future Census releases is not assumed.

Census TIGERweb source layer · Census classification definitions

Which GIS checks does your team repeat?

InfraSpatial Solutions can turn an agreed set of data rules into a repeatable workflow, with clear exception reports and documented handover.

Discuss a workflow