Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

ground-truth-diff

Estrelas1

Forks0

Atualizado10 de maio de 2026 às 19:45

Diff OSM geometry and attributes against TIGER/Line 2024 to identify import drift, new roads, and name-field artifacts in MetroNow zones.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

AICincy

AICincy/MetroNow

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	ground-truth-diff
description	Diff OSM geometry and attributes against TIGER/Line 2024 to identify import drift, new roads, and name-field artifacts in MetroNow zones.
when_to_use	User mentions TIGER 2024, geometry drift, name artifacts, new roads, comparing OSM to Census data, or Mac Donald / O Toole style name errors
allowed-tools	Read Grep Glob Bash(python ) Bash(curl )
argument-hint	[zone]
arguments	["zone"]

Ground-Truth Diff Against TIGER 2024

Compare OSM against TIGER/Line 2024 for zone: $zone

TIGER/Line 2024 source

File: tl_2024_39061_roads.zip (Hamilton County, FIPS 39061)
Download: Census Bureau TIGER/Line Shapefiles (released September 26, 2024)
Data currency: Through May 2024
2025 vintage adds augmented fullname fields and address ranges

What the diff reveals

Geometry drift

Ways that were imported in 2007 from TIGER 2005 but have since been updated in the Census Bureau's data. Differences indicate either:

OSM was corrected (good — confirms human review happened)
OSM was NOT corrected and the road has actually moved/changed (cleanup candidate)

New roads

Roads in TIGER 2024 that have no OSM equivalent — genuinely new construction since 2005. Particularly relevant for the MetroNow zones where suburban development is active.

Name-field artifacts (RESEARCH-FINDINGS Section 2 Item 3)

The 2007 import introduced systematic name errors:

USPS abbreviation spacing: "Mac Donald St" → should be "MacDonald Street"
Stripped apostrophes: "O Toole Avenue" → should be "O'Toole Avenue"
Stripped diacritics: "Canada Road" for "Cañada Road" (the ñ was lost in the 2007 import)
ALL CAPS remnants: Some ways still have uppercase names from TIGER

TIGER 2024 has corrected many of these. Diffing reveals which OSM ways still carry the 2005-era name.

Highway classification drift

The original import mapped CFCC A4x → highway=residential by default. TIGER 2024 uses updated MAF/TIGER Feature Class Codes (MTFCC) that better distinguish:

S1400: Secondary road → highway=tertiary or unclassified
S1740: Private road → highway=service + access=private
S1200: Secondary road (named) → highway=secondary

Cross-referencing TIGER 2024 MTFCC against OSM highway=* reveals misclassifications.

Diff workflow

Download tl_2024_39061_roads.zip from Census Bureau
Extract and load into a spatial format (GeoJSON, PostGIS, or Shapefile)
Clip to zone bbox from src/osm/zones/__init__.py (the ZONES dict)
For each TIGER 2024 road segment:
- Find matching OSM way(s) by proximity + name similarity
- Compare: geometry (Hausdorff distance), name, MTFCC vs highway tag
- Flag mismatches as correction candidates
Output: CSV of candidates with OSM way ID, TIGER LINEARID, and specific mismatches

Mais deste repositório

mesmo repositório

zone-audit

AICincy/MetroNow

Run the full TIGER defect audit pipeline for a MetroNow service zone — fetch from Overpass, classify defects, analyze history, generate reports.

2026-05-101

maproulette-challenge

AICincy/MetroNow

Generate a MapRoulette challenge from scan results for defect classes with high false-positive rates. Creates GeoJSON tasks constrained to MetroNow zone polygons.

2026-05-101

tiger-history-deep

AICincy/MetroNow

Deep revision history analysis for specific OSM ways — fetches full version history from OSM API v0.6, identifies import bot vs human edits, classifies review status with confidence scores.

2026-05-101

changeset-submit

AICincy/MetroNow

Submit corrections to OSM API v0.6 with full community compliance — proper changeset tags, size limits, rate-limit awareness, and dry-run support.

2026-05-101

metronow-explainer

AICincy/MetroNow

Decompress MetroNow docs so future-you (and fresh AI sessions) can pick the project back up cold without re-deriving everything. Use when the user says docs are confusing, plain, dense, hard to follow, missing context, jargon-heavy, jump straight to conclusions, or are hard to come back to after time away; asks why something is the way it is; says they can't tell what a term means; asks for a walkthrough, explainer, primer, or context refresher; says a section assumes too much; or wants visual aids. Diagnoses missing-middle gaps (undefined jargon, unstated WHY, skipped bridge steps, prose where a picture is needed) and rewrites sections using a fixed template — definition first, then bridge steps, then a load-bearing diagram, then code citations. Outputs to docs/explainers/<topic>.md or in-place edits. No VitePress, no static-site generator — just markdown that GitHub renders.

2026-05-101

metronow-code-review

AICincy/MetroNow

Unified code review and audit standards for the MetroNow Atlas TIGER Audit Console (https://github.com/AICincy/MetroNow.git). Use this skill when auditing any code in the MetroNow project, doing a PR review, checking code quality, validating accessibility, reviewing Docker config, or when someone asks "review this code," "audit the frontend," "check my PR," "what's wrong with this file," or "does this meet our standards." The codebase is vanilla JavaScript (IIFE pattern, no framework), single-file HTML with inline CSS/JS, IBM Plex typography, Leaflet maps, and an Express.js backend on port 3000 that shells out to the Python `osm` CLI. Covers JS, HTML, CSS, and Dockerfile review with severity-classified findings.

2026-05-091

name	ground-truth-diff
description	Diff OSM geometry and attributes against TIGER/Line 2024 to identify import drift, new roads, and name-field artifacts in MetroNow zones.
when_to_use	User mentions TIGER 2024, geometry drift, name artifacts, new roads, comparing OSM to Census data, or Mac Donald / O Toole style name errors
allowed-tools	Read Grep Glob Bash(python ) Bash(curl )
argument-hint	[zone]
arguments	["zone"]

Ground-Truth Diff Against TIGER 2024

Compare OSM against TIGER/Line 2024 for zone: $zone

TIGER/Line 2024 source

File: tl_2024_39061_roads.zip (Hamilton County, FIPS 39061)
Download: Census Bureau TIGER/Line Shapefiles (released September 26, 2024)
Data currency: Through May 2024
2025 vintage adds augmented fullname fields and address ranges

What the diff reveals

Geometry drift

Ways that were imported in 2007 from TIGER 2005 but have since been updated in the Census Bureau's data. Differences indicate either:

OSM was corrected (good — confirms human review happened)
OSM was NOT corrected and the road has actually moved/changed (cleanup candidate)

New roads

Roads in TIGER 2024 that have no OSM equivalent — genuinely new construction since 2005. Particularly relevant for the MetroNow zones where suburban development is active.

Name-field artifacts (RESEARCH-FINDINGS Section 2 Item 3)

The 2007 import introduced systematic name errors:

USPS abbreviation spacing: "Mac Donald St" → should be "MacDonald Street"
Stripped apostrophes: "O Toole Avenue" → should be "O'Toole Avenue"
Stripped diacritics: "Canada Road" for "Cañada Road" (the ñ was lost in the 2007 import)
ALL CAPS remnants: Some ways still have uppercase names from TIGER

TIGER 2024 has corrected many of these. Diffing reveals which OSM ways still carry the 2005-era name.

Highway classification drift

The original import mapped CFCC A4x → highway=residential by default. TIGER 2024 uses updated MAF/TIGER Feature Class Codes (MTFCC) that better distinguish:

S1400: Secondary road → highway=tertiary or unclassified
S1740: Private road → highway=service + access=private
S1200: Secondary road (named) → highway=secondary

Cross-referencing TIGER 2024 MTFCC against OSM highway=* reveals misclassifications.

Diff workflow

Download tl_2024_39061_roads.zip from Census Bureau
Extract and load into a spatial format (GeoJSON, PostGIS, or Shapefile)
Clip to zone bbox from src/osm/zones/__init__.py (the ZONES dict)
For each TIGER 2024 road segment:
- Find matching OSM way(s) by proximity + name similarity
- Compare: geometry (Hausdorff distance), name, MTFCC vs highway tag
- Flag mismatches as correction candidates
Output: CSV of candidates with OSM way ID, TIGER LINEARID, and specific mismatches