From bdb904ca5bcf506ed9bc74b695f4386d29cc51fc Mon Sep 17 00:00:00 2001 From: root Date: Tue, 21 Jul 2026 22:56:10 -0400 Subject: [PATCH] Add Forefront map validation answers --- projects/forefront-broadband-map.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/projects/forefront-broadband-map.md b/projects/forefront-broadband-map.md index 104fcdb..f33e0ae 100644 --- a/projects/forefront-broadband-map.md +++ b/projects/forefront-broadband-map.md @@ -21,9 +21,13 @@ Temporary hosting, if needed: **Ops** — likely `ops.itpropartner.com/forefront | Provider qualification access | Public web pages only | | FCC vs provider data | Combination of both | | ZIP coverage | Include **75154** and **75146** | +| 75146 scope | Full ZIP | +| Initial validation address | `927 Pierce Road, Red Oak, TX 75154` — geocoded via OpenStreetMap/Nominatim to `32.5177279, -96.7677135` | | Desired fields | Include speed, technology, price, install fee, contract, order URL, phone number when available | | Under-300 Mbps providers | Show grayed out / excluded, not hidden | | Prototype access protection | Not needed now | +| Manual sampled validation if provider sites block automation | Yes | +| Forefront source data format | Still needs specific format; Germaine answered yes but not which type. Accept polygons, tower/AP/sector data, or address-level serviceability list. | ## Providers to include @@ -36,7 +40,7 @@ Temporary hosting, if needed: **Ops** — likely `ops.itpropartner.com/forefront ## Required user experience -1. Open an interactive map of ZIPs **75154** and **75146**. +1. Open an interactive map of ZIPs **75154** and **75146**. Scope for **75146** is the full ZIP. 2. Search by street address. 3. See which providers offer **300+ Mbps** service at that address. 4. Show lower-speed services grayed out as excluded. @@ -149,13 +153,16 @@ User browser 4. Build address search and map prototype. 5. Add provider/source/confidence result cards with under-300 Mbps services grayed out. 6. Deploy temporary internal prototype under Ops. -7. Validate against provider websites using known 75154/75146 addresses. +7. Validate against provider websites using known 75154/75146 addresses, starting with `927 Pierce Road, Red Oak, TX 75154`. 8. Add Forefront layer when Germaine provides polygons, tower/AP/sector data, or address-level serviceability data. 9. Add refresh workflow and reporting/export if useful. +## Validation addresses + +| Address | ZIP | Coordinates | Source | Purpose | +|---|---|---|---|---| +| `927 Pierce Road, Red Oak, TX 75154` | 75154 | `32.5177279, -96.7677135` | OpenStreetMap/Nominatim geocode, checked 2026-07-21 | First known address for provider-availability validation | + ## Remaining questions for Germaine -1. Which Forefront data can be provided first: coverage polygons, tower/AP/sector details, or address-level serviceability list? -2. Should the 75146 scope mean the full ZIP, only areas adjacent to Forefront/Red Oak, or all service-relevant addresses? -3. Are there any known addresses in 75154/75146 that should be used as validation test cases? -4. If provider websites block automation, is manual sampled validation acceptable for the first prototype? +1. Which Forefront data format can be provided first: coverage polygons, tower/AP/sector details, or address-level serviceability list?