Query the Data Delivery Network
Query the DDNThe 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 erate_fcc_form_470_tool_data table in this repository, by referencing it like:
"datahub-usac/erate-fcc-form-470-tool-data-jt8s-3q52:latest"."erate_fcc_form_470_tool_data"or in a full query, like:
SELECT
":id", -- Socrata column ID
"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.
"form_pdf", -- Link to download the original submitted FCC Form 470 as a PDF.
"rfp_documents", -- Link to download a copy of the original submission of the Request for Proposal (RFP).
"category_one_description", -- Description of Category One services (Internet Access and/or Telecommunications) the applicant seeks discounts for.
"all_public_schools_districts", -- Indicates that all public schools/districts in the state are included for the FCC Form 470.
"funding_year", -- Funding year for the FCC Form 470.
"installation_initial", -- Indicates if the applicant is seeking installation, activation, and initial configuration for the service requested.
"unit", -- Unit type of the service requested (e.g. circuits, lines, fiber strands.)
"installment_max_range_years", -- Maximum number of years over which the applicant will amortize the costs.
"contact_city", -- City of the application’s main contact.
"service_category", -- Category of service the applicant is applying for.
"installment_min_range_years", -- Minimum number of years over which the applicant will amortize the costs.
"installment_type", -- Applicant can choose to use an installment payment plan for the non-discounted portion of any special construction charges associated with the request.
"rfp_identifier", -- Indicates whether a Request for Proposal (RFP) document was provided for the services requested.
"state_or_local_restrictions_1", -- Description of state or local procurement rules and/or restrictions on how or when service providers may contact an applicant or on other bidding procedures.
"all_non_public_schools", -- Indicates that all non-public schools in the state are included for the FCC Form 470.
"maintenance_technical_support", -- Indicates if the applicant is seeking maintenance and technical Support for the service requested.
"service_type", -- Funding request number service type.
"entities", -- Number of entities served by the service requested.
"form_nickname", -- Nickname given to an application by an applicant when filling their FCC Form 470.
"contact_phone", -- Phone number of the application’s main contact.
"authorized_person_state", -- State of the person authorized to certify the FCC Form 470.
"authorized_person_phone_ext", -- Phone extension of the person authorized to certify the FCC Form 470.
"contact_zip", -- Zip code of the application’s main contact.
"applicant_type", -- Applicant type including: school, school district, library, library system, or consortium.
"fcc_form_470_status", -- Current status of the FCC Form 470.
"contact_address1", -- Street address line 1 for the application’s main contact.
"contact_state", -- State of the application’s main contact.
"technical_contact_phone_ext", -- Phone extension of the technical contact provided by the applicant of the FCC Form 470.
"authorized_person_zip", -- Zip code of the person authorized to certify the FCC Form 470.
"other_function", -- Description of the function the applicant is requesting, if not listed.
"other_manufacturer", -- Name of the manufacturer if it is not included in the drop down list.
"all_libraries", -- Indicates that all libraries in the state are included for the FCC Form 470.
"billed_entity_number", -- Unique billed entity number (BEN) associated with the entity name on the FCC Form 470.
"category_two_description", -- Description of Category Two services (Internal Connections, Basic Maintenance of Internal Connections, or Managed Internal Broadband Services) the applicant seeks discounts for.
"statewide_state", -- Indicates that the FCC Form 470 is for the entire state.
"state_or_local_restrictions", -- Indicates if there are state or local procurement or competitive bidding requirements that apply to the procurement of services sought by the applicant.
"authorized_person_zip_ext", -- Zip code extension of the person authorized to certify the FCC Form 470.
"minimum_capacity", -- "Minimum capacity of units (Mbps) desired for the service requested. "
"authorized_person_email", -- Email address of the person authorized to certify the FCC Form 470.
"website_url", -- Website for the billed entity.
"ben_address_2", -- Applicant street address line 2.
"billed_entity_state", -- Applicant state.
"billed_entity_zip", -- Applicant zip code.
"billed_entity_zip_ext", -- Applicant zip code extension.
"billed_entity_phone", -- Applicant phone number.
"number_of_eligible_entities", -- Number of entities eligible for the services requested through an FCC Form 470.
"technical_contact_name", -- Name of the technical contact provided by the applicant of the FCC Form 470.
"contact_phone_ext", -- Phone number extension of the application’s main contact.
"contact_email", -- Email address of the main contact. This contact is used as the first point of contact through the funding request process.
"authorized_person_employer", -- Employer of the person authorized to certify the FCC Form 470.
"technical_contact_email", -- Email address of the technical contact provided by the applicant of the FCC Form 470.
"authorized_person_title", -- Title of the person authorized to certify the FCC Form 470.
"application_number", -- Unique application number generated at the time applicants begin to file the FCC Form 470. Applicants can request funding for multiple services under the same application number.
"service_request_id", -- Unique service request identifier for each request within a single FCC Form 470 application.
"service_request_rfp_attachment", -- Count of Request for Proposal (RFP) attachments for each service request within a FCC Form 470 application.
"rfp_upload_date", -- The date the Request for Proposal (RFP) document was uploaded to EPC.
"allowable_contract_date", -- Earliest date on which an applicant can sign a contract for contracted services or enter into an arrangement for tariffed (T) or month to-month (MTM) services with a service provider is 28 days after the certified date.
"certified_date_time", -- Exact date and time the FCC Form 470 was certified (EST).
"last_modified_date_time", -- Exact date and time the FCC Form 470 was last modified (EST).
"billed_entity_name", -- Name of the billed entity.
"ben_fcc_registration_number", -- Unique 10-digit number assigned by the FCC to a business or individual that registers with the FCC.
"ben_address_1", -- Applicant street address line 1.
"billed_entity_city", -- Applicant city.
"billed_entity_email", -- Applicant email address.
"billed_entity_phone_ext", -- Applicant phone number extension.
"contact_name", -- Name of the main contact provided by the applicant on the FCC Form 470.
"contact_address2", -- Street address line 2 for the application’s main contact.
"contact_zip_ext", -- Zip code extension of the application’s main contact.
"technical_contact_title", -- Title of the technical contact provided by the applicant on the FCC Form 470.
"technical_contact_phone", -- Phone number of the technical contact provided by the applicant on the FCC Form 470.
"authorized_person_name", -- Name of the person authorized to certify the FCC Form 470.
"authorized_person_address", -- Address of the person authorized to certify the FCC Form 470.
"authorized_person_city", -- City of the person authorized to certify the FCC Form 470.
"authorized_person_phone", -- Phone number of the person authorized to certify the FCC Form 470.
"consulting_firm_data", -- Consultant firm data array that includes the following data points for each consultant firm associated to the FCC Form 470 application: consulting firm's name, consulting firm's Consultant Registration Number (CRN), consulting firm's phone, and consulting firm's email.
"function", -- Indicates the function of the funding request number line item service or product.
"quantity", -- Amount of units of the specific service requested.
"maximum_capacity", -- Maximum capacity of units (Mbps) desired for the service requested.
"manufacturer" -- Requested manufacturer or equivalent.
FROM
"datahub-usac/erate-fcc-form-470-tool-data-jt8s-3q52:latest"."erate_fcc_form_470_tool_data"
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/erate-fcc-form-470-tool-data-jt8s-3q52 with SQL in under 60 seconds.
Query Your Local Engine
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/erate-fcc-form-470-tool-data-jt8s-3q52: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/erate-fcc-form-470-tool-data-jt8s-3q52Checkout 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/erate-fcc-form-470-tool-data-jt8s-3q52:latestThis will download all the objects for the latest tag of datahub-usac/erate-fcc-form-470-tool-data-jt8s-3q52 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/erate-fcc-form-470-tool-data-jt8s-3q52: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/erate-fcc-form-470-tool-data-jt8s-3q52:latestThis 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/erate-fcc-form-470-tool-data-jt8s-3q52 is just another Postgres schema.