# Datasets

Ortege Studio, based on Apache Superset 4, provides access to two primary data sources: Lakehouse v2 and Web3 BigQuery.

<figure><img src="/files/y4HZ8ccLvumoPfEPBoJ7" alt=""><figcaption></figcaption></figure>

### Lakehouse v2

Lakehouse v2 is built on Apache Doris and provides access to the following blockchain-related datasets:

* Bitcoin
* Dapps
* Pricing
* Socials
* Stacks
* Stellar

### Web3 BigQuery

Web3 BigQuery integrates with Google's public blockchain datasets. While we support all public datasets in Google's BigQuery, please note that the user experience is currently under development.

#### Supported Networks and Datasets

| Network      | Dataset Path                                                                                     |
| ------------ | ------------------------------------------------------------------------------------------------ |
| Arbitrum     | `bigquery-public-data.goog_blockchain_arbitrum_one_us`                                           |
| Avalanche    | `bigquery-public-data.goog_blockchain_avalanche_contract_chain_us`                               |
| Cronos       | `bigquery-public-data.goog_blockchain_cronos_mainnet_us`                                         |
| Ethereum     | `bigquery-public-data.blockchain_analytics_ethereum_mainnet_us`                                  |
| Fantom       | `bigquery-public-data.goog_blockchain_fantom_opera_us`                                           |
| Aptos        | `bigquery-public-data.crypto_aptos_mainnet_us`                                                   |
| Optimism     | `bigquery-public-data.goog_blockchain_optimism_mainnet_us`                                       |
| Bitcoin Cash | `bigquery-public-data.crypto_bitcoin_cash`                                                       |
| Dogecoin     | `bigquery-public-data.crypto_dogecoin`                                                           |
| Litecoin     | `bigquery-public-data.crypto_litecoin`                                                           |
| MultiversX   | `bigquery-public-data.crypto_multiversx_mainnet_eu`                                              |
| Polygon      | `bigquery-public-data.crypto_polygon`, `bigquery-public-data.goog_blockchain_polygon_mainnet_us` |
| Solana       | `bigquery-public-data.crypto_solana_mainnet_us`                                                  |
| Sui          | `bigquery-public-data.crypto_sui_mainnet_us`                                                     |
| TRON         | `bigquery-public-data.goog_blockchain_tron_mainnet_us`                                           |
| Tezos        | `bigquery-public-data.crypto_tezos`                                                              |
| Theta        | `bigquery-public-data.crypto_theta`                                                              |
| Zcash        | `bigquery-public-data.crypto_zcash`                                                              |
| Zilliqa      | `bigquery-public-data.crypto_zilliqa`                                                            |

#### Current Limitations

* Dataset selection from the Schema in SQL lab is not yet available
* Dataset paths must be manually entered
* Table Schema visibility is limited

#### Working with BigQuery Datasets

To explore available tables and their sizes in a dataset (using Ethereum as an example):

```sql
SELECT 
    table_name,
    creation_time,
    table_type
FROM bigquery-public-data.blockchain_analytics_ethereum_mainnet_us.INFORMATION_SCHEMA.TABLES;
```

To view the schema of a specific table:

```sql
SELECT 
    column_name,
    data_type,
    is_nullable
FROM bigquery-public-data.blockchain_analytics_ethereum_mainnet_us.INFORMATION_SCHEMA.COLUMNS
WHERE table_name = 'decoded_events'
ORDER BY ordinal_position;
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ortege.ai/en/ortege-products/ortege-studio/datasets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.