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 secopii_plan_anual_de_adquisiciones_detalle table in this repository, by referencing it like:
"datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx:latest"."secopii_plan_anual_de_adquisiciones_detalle"or in a full query, like:
SELECT
":id", -- Socrata column ID
"seleccion_abreviada_o_acuerdo", -- Determina si la adquisición se hace a través de acuerdo marco
"duracion_esperada", -- Valor de la duración esperada del desarrollo del proceso de compra
"valor_esperado_de_presupuesto", -- Valor Estimado del proceso, cubierto por la vigencia actual
"correo_del_contacto", -- Correo electrónico del contacto responsable de la adquisición en la entidad
"unidad_de_duracion_esperada", -- Unidad en la que se calcula el valor de duración esperada
"fecha_esperada_de_inicio", -- Fecha Esperada de inicio de desarrollo del proceso de compra pública
"id", -- Identificador único del Item del PAA, numérico
"tipo", -- Si es una adquisición o una necesidad.
"annio", -- Año del PAA
"valor_total_esperado", -- Valor estimado del proceso de compra
"origen_recursos", -- Origen de los recursos para la adquisición, entre otros, pueden definirse los recursos propios, empréstitos, regalías o Sistema General de Participaciones
"requiere_vigencias_futuras", -- Indica si se requiere contar con vigencias futuras para la ejecución del PAA. Esta columna antes se llamaba "Valor Esperado de Vigencias Futuras"
"identificador_unico", -- Identificador único del Item del PAA, propio de la plataforma
"estado_de_solicitud_de", -- Estado, a nivel de interoperabilidad, de la solicitud de vigencias futuras
"procesos_relacionados", -- Procesos relacionados con el PAA
"descripcion", -- Descripción del Item a adquirir en el proceso registrado
"codigo_entidad", -- Codigo de la entidad en la plataforma SECOPII
"nombre_del_contacto", -- Nombre del Contacto responsable de la adquisición en la entidad
"causal_de_contratacion", -- Se refiere al tipo de necesidad para ejecutar la contratacion
"fecha_esperada_de_recepcion", -- Fecha Esperada de inicio de la fase de recepción de ofertas para el proceso
"fecha_version", -- Fecha en que se publicó la versión del PAA
"fecha_de_carga_del_paa", -- Fecha de carga del PAA
"categorias_unspsc", -- Codigo de identificación de Naciones Unidas para el bien o servicio que se busca conseguir con la adquisición
"id_plan_anual_de_adquisiciones", -- Relación al Indentificador del Plan Anual de Adquisición registrado en el conjunto de datos de Encabezado - https://www.datos.gov.co/Gastos-Gubernamentales/SECOP-II-PAA-Encabezado/b6m4-qgqv
"version_del_paa", -- Versión del PAA
"telefono_del_contacto", -- Número de teléfono del contacto responsable de la adquisición en la entidad
"modalidad" -- Mecanismo de Selección utilizado en el proceso de Compra Pública
FROM
"datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx:latest"."secopii_plan_anual_de_adquisiciones_detalle"
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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx 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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx: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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhxCheckout 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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx:latestThis will download all the objects for the latest tag of datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx 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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx: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 datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx: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, datos-gov-co/secopii-plan-anual-de-adquisiciones-detalle-9sue-ezhx is just another Postgres schema.