Record FCC token status for Forefront map
This commit is contained in:
@@ -199,7 +199,7 @@ Steps:
|
||||
|
||||
1. Create/use FCC CORES/BDC login.
|
||||
2. Generate NBM API token from `https://broadbandmap.fcc.gov/login` → Manage API Access.
|
||||
3. Store username/token in server `.env`.
|
||||
3. Store username/token in server `.env`. Current state: token is stored as `FCC_HASH_VALUE`; `FCC_USERNAME` is still needed.
|
||||
4. Call `listAsOfDates` to discover newest availability date.
|
||||
5. Call `listAvailabilityData/{as_of_date}` with filters:
|
||||
- category: State or Provider
|
||||
@@ -299,7 +299,7 @@ Confirmed by Germaine:
|
||||
|
||||
Still needed before build:
|
||||
|
||||
1. FCC BDC username/token, or approval to create/request one.
|
||||
1. FCC BDC username/token, or approval to create/request one. Current state: token received and stored as `FCC_HASH_VALUE`; FCC username still needed.
|
||||
2. Decision on whether to pursue FCC/CostQuest Fabric access.
|
||||
3. Any Forefront coverage/install data when available.
|
||||
4. Confirm temporary URL if/when deployed; default assumption remains `ops.itpropartner.com/forefront-broadband-map/`.
|
||||
@@ -311,7 +311,7 @@ Still needed before build:
|
||||
|
||||
Tasks:
|
||||
|
||||
1. Build FCC API client.
|
||||
1. Build FCC API client using `.env` values `FCC_USERNAME` and `FCC_HASH_VALUE`.
|
||||
2. Pull latest availability vintage list.
|
||||
3. List Texas fixed broadband downloads.
|
||||
4. Download target files.
|
||||
|
||||
Reference in New Issue
Block a user