ippadmin/itpp-infrastructure
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine Forefront broadband map requirements

Browse Source
This commit is contained in:
root
2026-07-21 22:47:27 -04:00
parent a255847e69
commit 0b92e77e1d
1 changed files with 100 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
projects/forefront-broadband-map.md
+100 -32
View File
@@ -1,14 +1,29 @@
# Forefront Broadband Map — ZIP 75154 Broadband Availability # Forefront Broadband Map — ZIP 75154/75146 Broadband Availability
**Status:** Future Project | **Saved:** 2026-07-21 **Status:** Future Project | **Saved:** 2026-07-21 | **Updated:** 2026-07-21
## Concept ## Concept
Build an interactive, searchable broadband availability map for **Forefront Wireless** focused on ZIP code **75154 / Red Oak, Texas**. Build an interactive, searchable broadband availability map for **Forefront Wireless** focused on ZIP codes **75154 / Red Oak, Texas** and **75146 / Lancaster, Texas**.
The app should let a user enter an address and see exactly which qualifying internet services are offered there. Qualifying means broadband plans over **300 Mbps** only. The app should let a user enter an address and see exactly which qualifying internet services are offered there. Qualifying means broadband plans over **300 Mbps** only. Services below 300 Mbps should still be visible but **grayed out / marked excluded**.
Temporary hosting, if needed: **Ops** — likely `ops.itpropartner.com/forefront-broadband-map/` or similar internal path. Temporary hosting, if needed: **Ops** — likely `ops.itpropartner.com/forefront-broadband-map/` or similar internal path. This is an **internal-use project** for now; no password protection requirement yet.
## Confirmed requirements from Germaine — 2026-07-21
| Question | Answer |
|---|---|
| Audience | Internal use |
| Include Forefront as a layer | Yes |
| Residential or business | Either / both if data is available |
| Existing Forefront GIS/tower/customer data | Not yet |
| Provider qualification access | Public web pages only |
| FCC vs provider data | Combination of both |
| ZIP coverage | Include **75154** and **75146** |
| 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 |
## Providers to include ## Providers to include
@@ -17,17 +32,27 @@ Temporary hosting, if needed: **Ops** — likely `ops.itpropartner.com/forefront
- Rise Broadband - Rise Broadband
- Brightspeed - Brightspeed
- Frontier - Frontier
- Forefront Wireless as target/reference layer once data is available
Forefront Wireless should also be added as a target/reference layer if service-area GIS, tower/AP sector data, or customer install data can be obtained.
## Required user experience ## Required user experience
1. Open an interactive map of ZIP **75154**. 1. Open an interactive map of ZIPs **75154** and **75146**.
2. Search by street address. 2. Search by street address.
3. See which providers offer **300+ Mbps** service at that address. 3. See which providers offer **300+ Mbps** service at that address.
4. View provider details: speed, technology, source, confidence, freshness date, and ordering/contact URL if available. 4. Show lower-speed services grayed out as excluded.
5. Toggle/filter providers on the map. 5. View provider details when available:
6. Distinguish authoritative address-level results from broad coverage polygons or third-party/inferred data. - download/upload speed
- technology
- price
- install fee
- contract terms
- order URL
- phone number
- source
- confidence
- freshness date
6. Toggle/filter providers on the map.
7. Distinguish authoritative address-level results from broad coverage polygons or third-party/inferred data.
## Candidate data sources ## Candidate data sources
@@ -35,7 +60,7 @@ Forefront Wireless should also be added as a target/reference layer if service-a
|---|---|---| |---|---|---|
| FCC National Broadband Map | Address-level broadband availability lookup and government baseline | High | | FCC National Broadband Map | Address-level broadband availability lookup and government baseline | High |
| FCC Broadband Data Collection datasets | Bulk GIS/provider coverage and reproducible imports | High | | FCC Broadband Data Collection datasets | Bulk GIS/provider coverage and reproducible imports | High |
| Provider websites: AT&T, Spectrum, Rise, Brightspeed, Frontier | Address-specific qualification | Highest if accessible and allowed | | Provider websites: AT&T, Spectrum, Rise, Brightspeed, Frontier | Address-specific qualification using public pages only | Highest if accessible and allowed |
| Provider coverage pages/maps | Footprint validation | Medium | | Provider coverage pages/maps | Footprint validation | Medium |
| OpenStreetMap / Nominatim | Geocoding, base map, address fallback | Medium for geocoding only | | OpenStreetMap / Nominatim | Geocoding, base map, address fallback | Medium for geocoding only |
| City/county GIS | ZIP boundary, parcels, address normalization | High if available | | City/county GIS | ZIP boundary, parcels, address normalization | High if available |
@@ -47,7 +72,54 @@ Forefront Wireless should also be added as a target/reference layer if service-a
- **Medium confidence:** provider coverage maps/pages or GIS polygons. - **Medium confidence:** provider coverage maps/pages or GIS polygons.
- **Low confidence:** affiliate/comparison/directory sites. Use only for context. - **Low confidence:** affiliate/comparison/directory sites. Use only for context.
Address-level availability must not be treated as certain unless the source actually supports address-level qualification. Address-level availability must not be treated as certain unless the source actually supports address-level qualification. Because provider qualification is limited to public webpages, the first working version should combine FCC/BDC baseline data with sampled provider-page validation and source/confidence tags.
## Forefront data intake format
Forefront can be added as a real map layer once Germaine can provide any of the following. Best format is **CSV, spreadsheet, GeoJSON, KML, or shapefile**.
### Best option — coverage polygons
Preferred fields:
| Field | Example |
|---|---|
| `layer_name` | Red Oak North Sector |
| `geometry` | GeoJSON/KML polygon |
| `max_download_mbps` | 600 |
| `max_upload_mbps` | 100 |
| `technology` | fixed wireless / fiber |
| `status` | active / planned |
| `notes` | good LOS north of tower |
### Good option — tower/AP/sector data
Minimum fields:
| Field | Example |
|---|---|
| `site_name` | Ovilla Rd Tower |
| `latitude` / `longitude` | 32.x, -96.x |
| `sector_name` | North 5GHz |
| `azimuth_degrees` | 0 |
| `beamwidth_degrees` | 90 |
| `estimated_radius_miles` | 3 |
| `max_download_mbps` | 300 / 600 / 1000 |
| `status` | active / planned |
### Acceptable option — address/customer/serviceability list
If tower/GIS data is not ready, a simple address list works for MVP validation. It can be anonymized; no customer names are needed.
Fields:
- address
- city
- ZIP
- serviceable: yes/no/maybe
- technology
- max speed offered
- notes/constraints
## Proposed architecture ## Proposed architecture
@@ -56,38 +128,34 @@ User browser
-> Ops-hosted web app -> Ops-hosted web app
-> address search / autocomplete -> address search / autocomplete
-> interactive provider layers -> interactive provider layers
-> grayed-out sub-300 Mbps entries
-> result panel -> result panel
-> Backend API -> Backend API
-> geocode address -> geocode address
-> resolve to FCC BSL / parcel / coordinate -> resolve to FCC BSL / parcel / coordinate
-> query normalized availability store -> query normalized availability store
-> Data store -> Data store
-> ZIP 75154 GIS boundary -> ZIP 75154/75146 GIS boundaries
-> FCC/BDC availability records -> FCC/BDC availability records
-> provider lookup cache -> provider public-page lookup cache where allowed
-> source metadata and confidence -> source metadata and confidence
``` ```
## MVP roadmap ## MVP roadmap
1. Validate FCC/BDC data access for ZIP 75154. 1. Validate FCC/BDC data access for ZIPs 75154 and 75146.
2. Pull ZIP boundary and base GIS layer. 2. Pull ZIP boundaries and base GIS layers for 75154 and 75146.
3. Filter FCC/BDC data to the five requested providers and speeds over 300 Mbps. 3. Filter FCC/BDC data to the requested providers and mark speeds over 300 Mbps as qualifying.
4. Build address search and map prototype. 4. Build address search and map prototype.
5. Add provider/source/confidence result cards. 5. Add provider/source/confidence result cards with under-300 Mbps services grayed out.
6. Deploy temporary internal prototype under Ops. 6. Deploy temporary internal prototype under Ops.
7. Validate against provider websites using known Red Oak addresses. 7. Validate against provider websites using known 75154/75146 addresses.
8. Add refresh workflow and reporting/export if useful. 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.
## Questions for Germaine ## Remaining questions for Germaine
1. Is this for **internal competitive planning**, **Forefront sales**, **customer-facing public use**, or all three? 1. Which Forefront data can be provided first: coverage polygons, tower/AP/sector details, or address-level serviceability list?
2. Should Forefront Wireless be included as a visible layer alongside competitors? 2. Should the 75146 scope mean the full ZIP, only areas adjacent to Forefront/Red Oak, or all service-relevant addresses?
3. Residential only, or residential and business service? 3. Are there any known addresses in 75154/75146 that should be used as validation test cases?
4. Do you have Forefront service-area GIS, tower coordinates, AP sectors, customer locations, or install database exports? 4. If provider websites block automation, is manual sampled validation acceptable for the first prototype?
5. Do we have permission/API credentials for any provider qualification tools, or are we limited to public webpages?
6. Should FCC data be the baseline with provider websites used for validation, or should provider websites be treated as source of truth?
7. Should address search be strictly limited to 75154, or allow nearby addresses and warn when outside scope?
8. What output fields matter: provider, download/upload, technology, price, install fee, contract, order URL, phone number?
9. Should lower-speed providers be hidden entirely or shown as excluded/grayed out?
10. Should the Ops-hosted prototype be password-protected/internal only?