add release of project

fcc_funding.qmd

@@ -11,9 +11,9 @@ engine: knitr
 source("R/table_with_options.R")
 ```
 
-Link: https://fundingmap.fcc.gov/home
+Link: [https://fundingmap.fcc.gov/home](https://fundingmap.fcc.gov/home)
 
-Documentation: https://us-fcc.app.box.com/v/bfm-data-downloads-output
+Documentation: [https://us-fcc.app.box.com/v/bfm-data-downloads-output](https://us-fcc.app.box.com/v/bfm-data-downloads-output)
 
 The download page has two tabs:
 
@@ -25,29 +25,29 @@ The download page has two tabs:
 
 ## Program Data 
 
-It is organized by Agency and can be downloaded by program (`fundingdata_projectXXXX`) or for all projects in a program  (`fundingdata_programXX`).
+It is organized by Agency and can be downloaded by projects (`fundingdata_projectXXXX`) or for all projects in a program  (`fundingdata_programXX`).
 
-it will have a `csv` about the program. For example RDOF is just a two rows csv, header included.
+For each download it will have a `csv` about the program. For example RDOF is just a two rows csv, header included.
 
 ## Project Data
 
-They are defining 3 types of projects: 
+FCC is defining 3 types of projects: 
 
 - Defined by Area
 
 - Defined by list of locations
 
 - Defined by Middle Mile (No project representing this one: 07-03-2024)
 
-All of those type of project will have a Project Attribute Information table (`areaattributes_program` or `locationattributes_program`). The structure of those files are close but not similar for example location project has columns related to location (`build_req`, `loc_plan`, `loc_sup`). 
+All of those types of project will have a Project Attribute Information table (`areaattributes_program` or `locationattributes_program`). The structure of those files are close but not similar for example location project has columns related to locations (`build_req`, `loc_plan`, `loc_sup`). 
 
-For example the one for RDOF (`areaattributes_program24_J23_12feb2024.csv`) has 474 rows (inclunding headers ie 473 projects). 
+The one for RDOF (`areaattributes_program24_J23_12feb2024.csv`) has 474 rows (inclunding headers ie 473 projects). 
 
-Area project will have an associated `areapolygons_XXX.gpkg`. A quick glance on the one from RDOF show full valid geometries with an expected number of rows (473).
+Area projects will have an associated `areapolygons_XXX.gpkg`. A quick glance on the one from RDOF show full valid geometries with an expected number of rows (473).
 
-Location projects have, instead, of a `gpkg` a `csv` with location_id and lat/long (and address)!
+Location projects have, instead, of a `gpkg` a `csv` with `location_id` and `lat`/`long` (and address)!
 
-It seems that you can also have buildout data associated which each type of project. 
+It seems that you can also have buildout data associated which each type of project but none of the project available are providing this information(07-03-2024). 
 
 ## List of dataset avalaible: 07-03-2024
 
@@ -113,24 +113,33 @@ fcc_files_tidy <- fcc_files_tidy[fcc_files_tidy[["V1"]] != "programdata",]
 fcc_files_tidy[["program_id"]] <- gsub("program", "", fcc_files_tidy[["V2"]])
 
 fcc_files_tidy[["is_area"]] <- grepl("area", fcc_files_tidy[["V1"]])
+
+first_V4 <- function(x) {unlist(strsplit(x, ".", fixed = TRUE))[1]}
+
+fcc_files_tidy[["file_release"]] <- sapply(fcc_files_tidy[["V4"]], first_V4)
+
 # works for now but will breack if I have the third type of project
 fcc_files_tidy[["type_proj"]] <- ifelse(fcc_files_tidy[["is_area"]], "area", "location")
 
 type_proj_temp <- sapply(split(fcc_files_tidy[["type_proj"]], 
              fcc_files_tidy[["program_id"]]), 
              unique)
+file_release <- sapply(split(fcc_files_tidy[["file_release"]], 
+             fcc_files_tidy[["program_id"]]), 
+             unique) 
 
 type_proj <- data.frame(
   program_id = names(type_proj_temp),
-  type_proj  = type_proj_temp 
+  type_proj  = type_proj_temp, 
+  # a bit lazy and should be a join 
+  file_release = file_release
 )
 
 fcc_all_dat <- merge(fcc_all_dat, type_proj,
       by.x = "program_id", by.y = "program_id", 
       all.x = TRUE, all.y = TRUE)
 
 table_with_options(fcc_all_dat)
-
 ```
 
 

hubb.qmd

@@ -13,6 +13,9 @@ engine: knitr
 ### About
 This dataset serves as the foundation for the Connect America Fund Broadband Map (CAF Map), which displays the geographic areas eligible for CAF support, as well as the specific fixed locations where carriers participating in the program have built out broadband service. The information in the CAF Map comes directly from carriers, which submit broadband deployment data annually through USAC’s High Cost Universal Broadband (HUBB) portal. The current CAF Map is based on data certified in the HUBB as of September 30, 2023. USAC independently verifies deployment to a random sample of reported locations each year to monitor carrier compliance with CAF build-out obligations, but not all data in the map has been subject to this review.
 
+
+ [HUBB](https://www.usac.org/high-cost/annual-requirements/submit-data-in-the-hubb/)
+
 [Source Data](https://opendata.usac.org/High-Cost/High-Cost-Connect-America-Fund-Broadband-Map-CAF-M/r59r-rpip/data_preview)
 
 [About Page](https://opendata.usac.org/High-Cost/High-Cost-Connect-America-Fund-Broadband-Map-CAF-M/r59r-rpip/about_data)