What we do
Services
Parcel and cadastral GIS, data engineering, broadband compliance, emergency response data, and the governance that holds it all together.
Most of our work starts the same way: an agency has data it depends on, a requirement it has to meet, and no clear line between the two. We build that line, and we document it well enough that you can defend it.
Featured
BEAD subgrantee compliance
Why it is hard: a BEAD subgrant is a four-year construction project wrapped in a fourteen-year compliance obligation, and most Idaho subgrantees have never administered a federal subaward. The obligations that block construction outright are all environmental, and the guidance for them is still thin.
What we do: ten service families covering permitting and right-of-way, environmental and historic preservation, pole attachment and make-ready, location evidence and BSL assurance, financial and BABA compliance, reporting and program management, network performance testing, records and closeout, platform and data, and ongoing advisory. Take the whole thing or take one piece.
Parcel & cadastral GIS
Why it is hard: parcel data is the county’s most-used and least-maintained asset. Legal descriptions do not close, splits and merges arrive faster than they can be drawn, and the public viewer shows whatever was last published — which may be a mistake nobody has caught yet.
What we do: COGO from legal descriptions, parcel maintenance workflows, automated quality control that flags problems before the public sees them, delayed-publish pipelines that give your office a review window, change archives so you can prove what the map said on any given date, and internal review tools your staff will actually use.
Data engineering & warehousing
Why it is hard: agency data lives in a case management system, a spreadsheet somebody maintains, a workflow platform, and three shared drives. Every question that spans two of them becomes a manual project. And whoever built the last integration has usually left.
What we do: layered Snowflake warehouses with staging, master and reference tiers; ETL pipelines that run unattended and tell you when they fail; role-based access built to survive an audit; reporting applications your staff can use without a licence; and privacy-preserving record linkage where two agencies need to count the same people without sharing identities.
Emergency response & address data
Why it is hard: NG9-1-1 routes calls on GIS data instead of a tabular database, which means the quality of your address points and road centrelines is now an operational risk rather than a mapping preference. Getting to NENA standard is not a conversion, it is a program.
What we do: NENA-standard address point and centreline development, provisioning workflows, quality control against the standard, county data migration onto statewide platforms, and the governance to keep it current after go-live. Our founder led Idaho’s statewide NG9-1-1 GIS program.
Data governance & sharing
Why it is hard: cross-agency data sharing fails on governance, not technology. Who approves a release, who can publish a finding, what happens when two agencies disagree about a number in public — these get decided badly under deadline pressure if they are not decided deliberately first.
What we do: master data-sharing agreements and governance charters, federated architectures where each agency keeps its own system of record, data catalogues and dictionaries that stay current because they are generated rather than maintained, and stakeholder facilitation that surfaces the disagreements early enough to resolve them.