datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr
Loading...

Query the Data Delivery Network

Query the DDN

The easiest way to query any data on Splitgraph is via the "Data Delivery Network" (DDN). The DDN is a single endpoint that speaks the PostgreSQL wire protocol. Any Splitgraph user can connect to it at data.splitgraph.com:5432 and query any version of over 40,000 datasets that are hosted or proxied by Splitgraph.

For example, you can query the emergency_connectivity_fund_fcc_form_471 table in this repository, by referencing it like:

"datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest"."emergency_connectivity_fund_fcc_form_471"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "monthly_recurring_unit_cost", -- Monthly recurring costs per unit for the FRN line item ID.
    "filing_window", -- Identifies the ECF filing window for the application.
    "invoice_deadline_date", -- Last date an Invoice (BEAR or SPI) can be received.
    "form_pdf", -- Link to download the original submitted ECF FCC Form 471 as a PDF.
    "one_time_unit_cost", -- One-time costs per unit for the FRN line item ID.
    "network_equipment_type", -- When the selected service type is services with new construction or self-provisioned network, this is the network equipment type for the FRN line item ID.
    "recipients_of_service_entity_data", -- For consortium or ESA school district billed entities, the entity data of the selected recipients of service (ROS) on the FRN. The ROS entity data includes entity number, name, entity type, city, and state. If multiple ROS entities are selected in one application, then the entity data is concatenated as a nested array: {Entity Number1| Name1| Entity Type1| City1| State1}, {Entity Number2|Name2| Entity Type2| City2| State2}.
    "service_end_date", -- Estimated end date of services on ECF FCC Form 471 application. Service end date may impact commitment amount as it could adjust the month of services.
    "service_provider_identification_number", -- Unique nine-digit number assigned to identify the service provider. If null, the service provided has not registered in the E-rate program.
    "applicant_subtype", -- The applicant subtype (or subtypes separated by commas if multiple). Examples include: public school, private school, research library, bookmobile, Tribal school, Tribal library, etc.
    "billed_entity_city", -- Applicant city.
    "applicant_name", -- Name of the applicant's organization (also referred to as the billed entity).
    "selected_members_entity_data", -- For consortium or ESA school district billed entities, the entity data of the selected members on the application. The member entity data includes BEN, name, entity type, total student count, total square footage, and urban/rural status. If multiple member entities are selected in one application, then the entity data is concatenated as a nested array: {BEN1| Name1| Entity Type1| Total Student Count1| Total Square Footage1| Urban/ Rural Status1}, {BEN2| Name2| Entity Type2| Total Student Count2| Total Square Footage2| Urban/ Rural Status2}
    "billed_entity_zip_code_ext", -- Applicant zip code extension.
    "new_construction_self_provisioned_network", -- Indicates if an FRN includes a request for funding for new construction, a self-provisioned network, and/or datacasting equipment. This does not include monthly recurring costs for either a leased lit fiber service or wireless services.
    "billed_entity_state", -- Applicant state.
    "line_id_months_of_service", -- Number of months of service entered for the FRN line item ID.
    "contact_name", -- Full name of the main contact provided by the applicant on the ECF FCC Form 471.
    "contact_email", -- Email address of the main contact provided by the applicant on the ECF FCC Form 471. This contact is used as the first point of contact through the funding request process.
    "contact_phone", -- Phone number of the main contact provided by the applicant on the ECF FCC Form 471.
    "application_nickname", -- Nickname given to an ECF FCC Form 471 by an applicant.
    "application_number", -- Unique application number generated at the time an applicant begins to file the ECF FCC Form 471 application. Applicants can request funding for multiple services under the same application number.
    "obligation_file", -- A number that indicates in which obligation file the funding commitment was issued in.
    "funding_request_narrative", -- Narrative for the FRN describing the products and services.
    "invoicing_method", -- Type of invoice to be processed for FRN including "Applicant - FCC Form 472 (BEAR Form)" and "Service Provider - FCC Form 474 (SPI Form)".
    "fcc_registration_number", -- Ten-digit number that the FCC assigns to a business or individual that registers with the FCC.
    "service_delivery_date", -- Services must be installed or product must be delivered on or before this date.
    "funding_request_status", -- Status of the funding request. It includes pending, funded, denied or cancelled.
    "unmet_student_needs_12", -- Count of students provided by applicant in response to the application question: Even after receiving the funding that you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will lack access to both a connected device and a broadband connection that is sufficient to engage in remote learning?
    "network_equipment_make_model", -- When the selected service type is services with new construction or self-provisioned network, this is the network equipment make and model for the FRN line item ID.
    "firewall_included", -- When the selected service type is services, indicates if firewall services are included in the FRN line item ID.
    "product_type", -- When the selected service type is equipment, this is the product type for the FRN line item ID. Examples include: laptops, routers, wi-fi hotspots, etc.
    "frn_one_time_charges", -- Total one-time/non-recurring charge of a funding request. This field can be aggregated at the FRN level to generate metrics across service type, status or entities. This field should not be used to generate metrics at FRN line item ID level.
    "unmet_student_needs_3", -- Count of students provided by applicant in response to the application question: At the start of the pandemic, how many students in your school or school district lacked access to both a connected device and a broadband connection that were sufficient to engage in remote learning?
    "service_type", -- FRN service type including equipment and services.
    "application_status", -- Current status of the ECF FCC Form 471. It can be used to filter the following statuses: Certified and Committed.
    "form_version", -- Indicates whether the form version of the application is "current" or "original." It can be used to aggregate the data between current and original applications. "Current" is the view of the form processed by USAC. "Original" is the view of the form originally submitted by the applicant upon certification.
    "frn_approved_amount", -- Total approved amount for a funding request. This field can be aggregated at the FRN level to generate metrics across service type, status or entities. This field should not be used to generate metrics at FRN line item ID level.
    "product_make", -- Manufacturer of the FRN line item ID product.
    "line_total_recurring_costs", -- Total monthly recurring charges for the FRN line item ID.
    "urban_rural_status", -- Urban/rural status of the billed entity.
    "agreement_contract_type", -- Agreement type for the FRN including non-contracted, contract or tariff.
    "total_student_count", -- Student count for the billed entity based on the entity profile.
    "frn_recurring_charges", -- Total monthly recurring charges of a funding request. This field can be aggregated at the FRN level to generate metrics across service type, status or entities. This field should not be used to generate metrics at FRN line item ID level.
    "frn_total_charges", -- Total charges of a funding request. This field can be aggregated at the FRN level to generate metrics across service type, status or entities. This field should not be used to generate metrics at FRN line item ID level.
    "frn_line_id", -- Funding request line item ID number. This is the lowest level of detail of this dataset.
    "product_model", -- Model of the product on FRN line item ID.
    "bandwidth_download", -- Internet download speed of the connection for the FRN line item ID as megabits per second (Mbps).
    "bandwidth_upload", -- Internet upload speed of the connection for the FRN line item ID as megabits per second (Mbps).
    "one_time_unit_quantity", -- Unit quantity for the one-time costs for the FRN line item ID.
    "billed_entity_number", -- Billed entity number for the ECF FCC Form 471 applicant.
    "total_count_of_selected_members", -- For consortium or ESA school district billed entities, the total count of selected members in the application.
    "certified_datetime", -- Exact date and time (EST) when the ECF FCC Form 471 was certified.
    "funding_request_number", -- Unique funding request number associated with the ECF FCC Form 471.
    "funding_request_nickname", -- Nickname given to an FRN from the ECF FCC Form 471 by an applicant.
    "service_provider_name", -- Service provider name for the FRN.
    "service_start_date", -- Estimated start date of services on ECF FCC Form 471 application. Service start date may impact commitment amount as it could adjust the month of services.
    "frn_total_count_of_recipients_of_service", -- For consortium or ESA school district billed entities, the count of recipients of service in the FRN.
    "fcdl_comment_for_frn", -- Explanation of FCDL decision at the FRN level. MR: modification reason; CR: cancellation reason; DR: denial reason.
    "line_total_cost", -- Total costs for the FRN line item ID.
    "frn_authorized_disbursement", -- Total FRN approved authorized disbursement amount that will be paid to the service provider or applicant.
    "line_total_one_time_costs", -- Total one-time charges for the FRN line item ID.
    "monthly_quantity", -- Unit quantity for the FRN line item ID monthly recurring costs.
    "unmet_student_needs_10", -- Count of students provided by applicant in response to the application question: Even after receiving the funding that you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will lack access to a connected device that is sufficient to engage in remote learning?
    "unmet_student_needs_1", -- Count of students provided by applicant in response to the application question: At the start of the pandemic, how many students in your school or school district lacked access to a connected device (laptop or tablet) that was sufficient to engage in remote learning?
    "total_funding_commitment_request_amount", -- Funding request amount for applicant across all FRNs.
    "unmet_student_needs_9", -- Count of students provided by applicant in response to the application question: With the funding you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will you provide with both a connected device and a broadband connection, because they otherwise would not have had a connected device or a broadband connection that was sufficient to engage in remote learning?
    "last_updated_datetime", -- Exact date and time the ECF FCC Form 471 was last modified (EST).
    "unmet_student_needs_11", -- Count of students provided by applicant in response to the application question: Even after receiving the funding that you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will lack access to a broadband connection that is sufficient to engage in remote learning?
    "unmet_student_needs_4", -- Count of students provided by applicant in response to the application question: During the 2020-2021 school year, how many students in your school or school district did you provide a connected device, because they otherwise would not have had a connected device that was sufficient to engage in remote learning?
    "unmet_student_needs_2", -- Count of students provided by applicant in response to the application question: At the start of the pandemic, how many students in your school or school district lacked access to a broadband connection that was sufficient to engage in remote learning?
    "billed_entity_address", -- Applicant street address.
    "billed_entity_zip_code", -- Applicant zip code.
    "fcdl_date", -- The date of the obligation file that a funding commitment was issued in.
    "window_status", -- Indicates whether the application has been certified during the ECF FCC Form 471 application filing window.
    "applicant_type", -- Applicant type including school, school district, library, library system, or consortium.
    "unmet_student_needs_8", -- Count of students provided by applicant in response to the application question: With the funding you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will you provide with a broadband connection, because they otherwise would not have had a broadband connection that was sufficient to engage in remote learning?
    "unmet_student_needs_7", -- Count of students provided by applicant in response to the application question: With the funding you are requesting from the Emergency Connectivity Fund Program, how many students in your school or school district will you provide with a connected device, because they would otherwise not have a connected device that is sufficient to engage in remote learning?
    "unmet_student_needs_6", -- Count of students provided by applicant in response to the application question: During the 2020-2021 school year, how many students in your school or school district did you provide both a connected device and a broadband connection, because they otherwise would not have had a connected device or a broadband connection that was sufficient to engage in remote learning?
    "unmet_student_needs_5", -- Count of students provided by applicant in response to the application question: During the 2020-2021 school year, how many students in your school or school district did you provide a broadband connection, because they otherwise would not have had a broadband connection that was sufficient to engage in remote learning?
    "consulting_firm", -- Consulting firm entity data associated with the application's billed entity. The consulting firm entity data includes name and the consultant's registration number (CRN) assigned by USAC. If multiple consulting firms are associated with one application, then the entity data is concatenated as a nested array: {Name1| CRN1}, {Name2| CRN2}.
    "connection_type" -- When the selected service type is services, this is the connection type for the FRN line item ID. Examples include: leased lit fiber, cable modem, mobile broadband etc.
FROM
    "datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest"."emergency_connectivity_fund_fcc_form_471"
LIMIT 100;

Connecting to the DDN is easy. All you need is an existing SQL client that can connect to Postgres. As long as you have a SQL client ready, you'll be able to query datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr with SQL in under 60 seconds.

Query Your Local Engine

Install Splitgraph Locally
bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"
 

Read the installation docs.

Splitgraph Cloud is built around Splitgraph Core (GitHub), which includes a local Splitgraph Engine packaged as a Docker image. Splitgraph Cloud is basically a scaled-up version of that local Engine. When you query the Data Delivery Network or the REST API, we mount the relevant datasets in an Engine on our servers and execute your query on it.

It's possible to run this engine locally. You'll need a Mac, Windows or Linux system to install sgr, and a Docker installation to run the engine. You don't need to know how to actually use Docker; sgrcan manage the image, container and volume for you.

There are a few ways to ingest data into the local engine.

For external repositories, the Splitgraph Engine can "mount" upstream data sources by using sgr mount. This feature is built around Postgres Foreign Data Wrappers (FDW). You can write custom "mount handlers" for any upstream data source. For an example, we blogged about making a custom mount handler for HackerNews stories.

For hosted datasets (like this repository), where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.

Cloning Data

Because datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest is a Splitgraph Image, you can clone the data from Spltgraph Cloud to your local engine, where you can query it like any other Postgres database, using any of your existing tools.

First, install Splitgraph if you haven't already.

Clone the metadata with sgr clone

This will be quick, and does not download the actual data.

sgr clone datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr

Checkout the data

Once you've cloned the data, you need to "checkout" the tag that you want. For example, to checkout the latest tag:

sgr checkout datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest

This will download all the objects for the latest tag of datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr and load them into the Splitgraph Engine. Depending on your connection speed and the size of the data, you will need to wait for the checkout to complete. Once it's complete, you will be able to query the data like you would any other Postgres database.

Alternatively, use "layered checkout" to avoid downloading all the data

The data in datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest is 0 bytes. If this is too big to download all at once, or perhaps you only need to query a subset of it, you can use a layered checkout.:

sgr checkout --layered datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr:latest

This will not download all the data, but it will create a schema comprised of foreign tables, that you can query as you would any other data. Splitgraph will lazily download the required objects as you query the data. In some cases, this might be faster or more efficient than a regular checkout.

Read the layered querying documentation to learn about when and why you might want to use layered queries.

Query the data with your existing tools

Once you've loaded the data into your local Splitgraph Engine, you can query it with any of your existing tools. As far as they're concerned, datahub-usac/emergency-connectivity-fund-fcc-form-471-i5j4-3rvr is just another Postgres schema.

Related Documentation:

Loading...