Every row already carries the county's own tax-delinquency signal. Tick the extra signals you want all present and the search returns only rows that carry them.
| Signal we cannot stack yet | Reason |
|---|---|
| Code violations / building permits | needs_dataset_discovery — Host reachable (HTTP 400 on a bare /resource/ probe -- a real Socrata-family error page, not a connection failure), but this is the STATE of Colorado's portal, not Denver-city-specific, and no dataset id was verified. denver_co has 7,229 lead rows on file (3rd-largest county). Next step: find Denver's own open-data portal (denvergov.org/opendata) and a real dataset id. |
| Neighbourhood context | needs_registration — Reachable; API returned an HTML 'Missing Key' error page for an unauthenticated query (confirms the endpoint is live but requires a key for county-level pulls). A free key is available with no cost at https://api.census.gov/data/key_signup.html -- request one and set CENSUS_API_KEY to activate this source. |
| FEMA flood zone | blocked_network — Both hazards.fema.gov and msc.fema.gov TLS-handshake-reset from apps-box at probe time (curl: 'Recv failure: Connection reset by peer' on hazards.fema.gov; 000/no-response on msc.fema.gov). This is a public, free, no-key ArcGIS REST service (identify-by-point query) -- the block is on THIS box's egress/TLS path, not a source restriction. Re-probe from a box with different egress before concluding FEMA itself refuses us. |
| Agency REO listings | blocked_network — Not independently re-verified this pass. Per the F5124 earlier-work reference in this ticket's brief: no working free feed/API path was found for HUD Home Store listings as of that fork's work -- recorded as blocked per brief instruction ('HUD Home Store / REO feeds only if F5124's earlier work found a working path -- otherwise record as blocked'). Revisit only if F5124's own notes (search for F5124 in this repo's history/memory) surface a working endpoint. |
| Code violations / building permits | blocked_network — Connection failed (000, no response) from apps-box at probe time. cobb_ga has 2,317 lead rows on file. |
| Code violations / building permits | needs_dataset_discovery — Host reachable (HTTP 404 on a bare API-root probe -- a real response, not a connection failure), no dataset id verified. NOTE: our actual Ohio lead counties are cuyahoga_oh (4,134 rows) and clermont_oh (1,535 rows), NOT franklin_oh -- Columbus/Franklin was named in the brief but does not match our warehouse today. Cataloged as requested; a Cleveland/Cuyahoga County portal would be higher-value and was not probed this pass. |
| Code violations / building permits | ok — CONFIRMED WORKING -- fetched 2 real rows (permit_number, permit_type, issued_date, contractor, value, street_address, zip_code). This is a proof-of-concept load only: Dallas is NOT currently one of our lead-warehouse counties (we hold harris_tx, tarrant_tx, williamson_tx -- not dallas_tx), so no w_leads row can be joined to it yet by county. Cataloged and loadable the moment a Dallas County lead source is added. |
| Code violations / building permits | needs_dataset_discovery — Portal host resolves and the ArcGIS-Hub-backed root responded, but the specific dataset id this fork guessed (vksd-fqxb) returned an 'ArcGIS Hub Unsupported' page, not data -- that id was a guess, not a verified dataset. Fort Worth is the seat of tarrant_tx, our LARGEST lead county (96,558 rows) -- highest-value target to fix next: browse https://data.fortworthtexas.gov/browse to find the real permits/code-compliance dataset id, then this becomes an 'ok' socrata_json source with zero code changes (the generic reader already handles it). |
| Code violations / building permits | blocked_network — Connection failed (000, no response) from apps-box at probe time. clark_nv is our 2nd-largest lead county (13,896 rows) -- high value once egress allows a re-probe. |
| Code violations / building permits | blocked_network — Connection failed (000, no response) from apps-box at probe time. sarasota_fl has 232 lead rows on file. |
| Code violations / building permits | blocked_network — Both hosts returned connection failures (000) from apps-box at probe time. Our actual VA lead counties are richmond_va (7,252 rows) and norfolk_va (3,491 rows), NOT Virginia Beach or Fairfax -- named in the brief but not a direct match; cataloged as requested. |
Code violations and FEMA flood zone are the two signals investors ask for most. Neither is loaded for any of our lead counties today: the county open-data portals for Fort Worth, Las Vegas, Cobb, Denver, Columbus, Virginia Beach and Sarasota were each probed and came back blocked or without a verified dataset id, and the FEMA layer TLS-resets from our host. We are not going to fill that gap with an estimate.
back to signals · the same search under /tools
Entity: Elite AI Holdings LLC. Site index · Free vs. pro tools · Open data API · Correction / opt-out · Privacy · Terms · Do Not Sell / Privacy Request · Account.
← Elite AI Empire home