Fourteen verified products turn messy municipal permits, parcels and procurement files into sellable data

Asked (summary):

What are verified examples of companies or products built on normalized municipal open data in Canada or the United States — building permits, property or parcel data, or government procurement data — and which specific datasets did they have to normalize or clean?

The research verified 14 documented commercial examples — 7 building-permit products, 5 procurement/spending products, 1 parcel/property product, and 1 mixed-municipal-record product — drawn from 14 independent source hosts, one example and one distinct URL per host. “Verified” means the source explicitly identifies a real product, identifiable government inputs, and actual transformation work; most evidence is first-party methodology or product documentation, supplemented by an official SmartProcure patent and a publisher account for Publicus.

What each product had to fix: six transformation layers across 14 products

A filled cell means the source document describes that cleaning layer explicitly. Hover or tap a cell for the exact wording; hover a product name for its named datasets.
building permitsprocurement/spendingparcel/propertymixed municipal recordsnot described in source
Schema and field mapping is the most universal layer — PermitStack alone maps 645 active sources from Socrata, ArcGIS, CKAN, CARTO, EnerGov, Accela, California NEM and NY-Sun feeds into one canonical schema. permit-stack.com
Vendor and contractor identity resolution dominates procurement: NationGraph found one supplier, Municipal Emergency Services, trading under four different names in purchase orders. nationgraph.com
Not every input is open-data licensed: SmartProcure's patented pipeline OCRs purchase files obtained by FOIA and public-records requests, arriving as paper, CDs, DVDs and flash drives in eleven file formats. patents.google.com
PropertyLabs is the only cross-border example, normalizing Socrata, ArcGIS, CKAN and municipal-API permit feeds from 45 Canadian and U.S. city pages into a common permit contract. propertylabs.org

All 14 examples, with exact datasets and cleaning work

ProductNamed datasets / sourcesNormalization and cleaningCommercial outputSource

Method: 14 verified commercial examples of products built on municipal or government data in Canada and the U.S., one row per product, compiled from 14 independent source hosts (one URL each), mostly first-party methodology pages, plus one patent and one publisher account; collected for this report. The matrix marks a transformation layer when the source text describes it explicitly; absence means not described, not necessarily not done. Long source and cleaning descriptions are truncated in the table — hover the matrix for the full cleaning text. Several inputs come via public-records requests or administrative records rather than open-data licences. No coordinates were collected, so no map is drawn.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.

Keenable SELECTAsk your own question
Made with Keenable SELECT