KMZ outreach
Carrier-supplied geometry always supersedes inferred FCC geography. When a KMZ arrives, its routes are intersected with ZCTA polygons and those ZIP rows are upgraded to confidence A1 with route_confirmed set.
source datacalculateduser-maintainedneeds reviewconflict
0 of 0 without a known contact“We are building a national transport-provider database for site and data-center interconnection planning. Could you provide your current fiber network KMZ/KML, including metro and long-haul routes where available? We are particularly interested in locations where you can provide 10G, 100G, 400G+, wavelength services, or dark fiber. If detailed route data requires an NDA, please let us know.”
Not started0
Contacted0
Awaiting reply0
NDA pending0
Received0
Declined0
| Carrier | Contacts | Dates | Status | Artifact |
|---|
Add carrier to pipeline
Sending mints a per-carrier reply-to token and records the outbound attempt; replies posted to the inbound webhook thread back into the Reply inbox.
Accepted artifacts: KMZ · KML · SHP · GeoJSON · Network map PDF · GIS portal link · API · Lit-building list · POP list · Market list
- BDC reflects broadband availability, not wholesale dark fiber.
- Market presence does not prove fiber at a specific building.