subimpact WhatsApp us

Australia Open Data Studio: Gov Data Joins

The Australia Open Data Studio pulls several data.gov.au datasets, aligns them on a shared year key and delivers one flat file as JSON, CSV or XLSX, with attribution, verification and an AI-ready package. Six presets cover energy and climate, material consumption, innovation, tourism and aid, society and road safety, and threatened species. A joined pull costs $0.02, a raw extraction $0.01. Run it from Apify Console or the API.

from $0.02 per joined pull, $20.00 per 1,000 · Updated Nov 2026, version 0.1.9

Key facts

Price
from $0.02 per joined pull, $20.00 per 1,000
Pricing model
Pay per event
Output
JSON, CSV, Excel, XML, RSS via Apify datasets
Access
Apify Console, REST API, Python and JS clients
Version
Updated Nov 2026, version 0.1.9
Usage
96.4% successful runs (30 days)
Actor
subimpact/au-open-data-studio

Who it is for

  • Policy analysts joining Australian indicators without writing ETL code
  • Journalists needing one clean CSV for an environment or transport story
  • Researchers comparing Australian sustainability and R&D series
  • Consultants building country fact packs from official sources

Use cases

Join energy and emissions indicators

Run preset A1, Energy & Climate by Year, to align renewable energy share, energy intensity and CO2 emissions per capita from SDG indicators across 1990 to 2015. The output is one row per year with all three series side by side, which is what a chart or a correlation needs, and verification.json reports row counts per source and the year range.

Read material consumption by category

Preset A2 returns domestic material consumption as a total and per capita, split by biomass, fossil fuels, metal ores and non-metallic minerals for 1970 to 2017. Set format to xlsx for a working file or csv for a database load, and keep includeAttribution on so the CC BY 4.0 source note travels with the data.

Pair innovation and industry series

Preset A3 joins R&D expenditure as a share of GDP, manufacturing value added as a share of GDP and manufacturing employment share for 1981 to 2015. That combination answers whether Australian manufacturing employment fell while output share held, which is hard to see from three separate downloads but obvious in one joined table.

Track tourism against overseas aid

Preset A4 aligns tourism direct GDP share with net ODA as a share of GNI for 2000 to 2016. Because both series land on the same year rows, a scatter or a dual axis chart takes minutes rather than a spreadsheet merge, and the attribution file records which data.gov.au records each column came from.

Bring your own datasets

Set preset custom, list 2 to 6 data.gov.au datastore resource ids in customDatasets, choose customKey year to auto-extract from year, Date or FY fields, and pick inner or left plus customAgg of none, sum or mean. customParams passes API filters to every dataset, so a join can be scoped before rows are merged.

Output fields

FieldTypeDescription
mode any
preset any
rows any
format any
files any
year_range any
run_url any

Sample output

From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.

2 rows, first 3 shown

[
  {
    "year": 1990,
    "renewable_share_pct": 8,
    "energy_intensity_toe_per_1k_usd": 0.177,
    "co2_emissions_per_capita": 33.6
  },
  {
    "year": 1991,
    "renewable_share_pct": 8.2,
    "energy_intensity_toe_per_1k_usd": 0.174,
    "co2_emissions_per_capita": 31.8
  }
]

Input

FieldTypeRequiredDescriptionDefault
mode string No studio = value layer (presets, joins, AI-ready package). extract = raw data pull of 1-5 datasets by ID (cheaper per-pull event). studio
datasetIds array No For mode=extract: list of data.gov.au datastore resource ids (UUIDs) to pull raw (1-5). Leave empty to use studio mode. -
preset string No Join bundle. A1 = Energy & Climate by Year. A2 = Material Consumption by Year. A3 = Innovation & Industry by Year. A4 = Tourism & Aid by Year. A5 = Society & Road Safety by Year. A6 = Threatened Species by Year. custom = bring your own d... A1
customDatasets array No For preset=custom: list of data.gov.au datastore resource ids (UUIDs) to join (2-6). Leave empty to use a preset. -
customKey array No For preset=custom: key parts to join on. Use 'year' (auto-extracted from year/Calendar year/Date/FY fields) or raw field names. All datasets must share these keys. ["year"]
customJoinType string No inner keeps only keys present in every dataset; left keeps all keys from the first dataset. inner
customParams string No For preset=custom: JSON object of extra API params applied to every dataset, e.g. {"filters": {"Servicetype": "LDC"}}. -
customAgg string No none = keep raw rows (last value per key). sum = aggregate numeric values per key. mean = average numeric values per key. none
format string No File format delivered to the key-value store (dataset records are always JSON). json
webhookUrl string No POST the result file to this URL after the run (3 retries with backoff). Leave empty to skip. -
aiReady boolean No Also emit JSON Schema + data dictionary + sample rows for LLM/RAG ingestion. true
includeAttribution boolean No Attach source/licence metadata sidecar to every output (CC BY 4.0). true

Example input

{
  "mode": "studio",
  "preset": "A1"
}

Pricing

EventWhat it meansPriceLowest tier
joined-pull One cross-dataset join delivered as flat CSV/JSON/XLSX (studio mode). $0.02 $0.02
extract-pull One raw dataset pull (1-5 datasets by ID, no join). $0.01 $0.01

$20.00 for 1,000 joined pull units at the listed price.

Prices from the Apify Store on 20 November 2026. Apify shows the final price before each run.

How it compares with other Apify actors

Price per 1,000 joins at Apify Store list prices. Every row is a live listing on the Store, read on 20 Nov 2026, so a buyer can check each number at the source.

Actor Price per 1,000 joins (Free plan) Higher plans (Gold) Start fee per run Platform usage Users Rating Last build
Australia Open Data Studio — Gov Data Joins This API Pay per event $20.00 $20.00 None Included 2 No reviews yet 18 Nov 2026
Data Gov Au Dataset Scraper Partial match, pay per event Charges per catalogue result item, one dataset or resource record per item. None Included 2 No reviews yet 15 Oct 2026
CKAN Open Data Exporter: Government Datasets & Files Partial match, pay per event Charges per dataset item, either a catalogue record or an exported resource row. $0.01 Included 3 No reviews yet 3 Jul 2026
Where Data Gov Au Dataset Scraper is stronger

Where Data Gov Au Dataset Scraper is stronger

  • Returns catalogue metadata for every dataset, including publisher, licence and contact fields
  • Filters by organisation and lists resource download links for each dataset
  • Plain CKAN API calls with no join configuration to set up

Where this API is stronger

  • Joins records across several datasets into one flat table
  • Delivers CSV, JSON or XLSX files with the covered year range recorded
  • Presets cover six policy themes such as energy, tourism and road safety
Where CKAN Open Data Exporter: Government Datasets & Files is stronger

Where CKAN Open Data Exporter: Government Datasets & Files is stronger

  • Works across any CKAN portal, not only the Australian one
  • Can export the data rows of a single resource by its ID

Where this API is stronger

  • Combines several datasets on a shared key and returns one joined pull
  • Preset joins cover six public policy themes, so no schema work is needed
  • Output is written with attribution and is ready for AI pipelines

No actor here performs cross dataset joins, so these are adjacent tools rather than direct substitutes. The catalogue actors suit teams that want to find datasets and pull one resource, which is a simpler job. Buyers who need several datasets merged on a shared key, with presets and flat file delivery, will need something like this studio actor instead.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

How to run it

  1. Choose a preset from A1 to A6, or set preset to custom and supply your own dataset ids.
  2. Set format to csv, json or xlsx, and leave aiReady and includeAttribution on unless you want a bare file.
  3. Add a webhookUrl only if the joined file should be posted to your own endpoint after the run; the actor retries the post three times with backoff.
  4. Run the actor, then download preset_join files plus preset_verification.json from the run's key-value store.
  5. For raw data instead of a join, set mode extract and list 1 to 5 datasetIds UUIDs.

cURL

curl -X POST "https://api.apify.com/v2/acts/subimpact~au-open-data-studio/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"studio","preset":"A1"}'

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/au-open-data-studio").call(run_input={"mode":"studio","preset":"A1"})

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/au-open-data-studio').call({"mode":"studio","preset":"A1"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);

n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/au-open-data-studio
Input JSON: paste the example input above.

Limits

  • Preset coverage ends at the last year each official series publishes, so the newest years are often missing.
  • Presets join on year only, so a monthly or quarterly analysis needs a custom join with raw field keys.
  • Custom joins need datastore resource UUIDs, not dataset page URLs.
  • Attribution under CC BY 4.0 is required when you republish the output.

Questions people ask

What does a joined pull cost?

One joined pull costs $0.02, which is $20.00 per 1,000 joins, and a raw extraction pull of up to 5 datasets costs $0.01. The joined file, attribution sidecar, verification file and AI-ready package all come from that single event, so there is no extra charge per output file.

Do I need a data.gov.au API key?

No. data.gov.au's public API is keyless, and the actor paces its fetches to stay within a comfortable rate. Large datasets take longer to assemble, but a slow pull does not fail because of rate limits.

Which Australian datasets are in the presets?

The presets draw on official data.gov.au records: SDG indicators for energy and emissions, material consumption totals and per capita figures, R&D and manufacturing shares, tourism GDP and ODA, road fatalities with youth NEET rates, and EPBC Act species listings by taxonomic group, each with its own year coverage.

What is in the AI-ready package?

With aiReady on, the actor also writes a JSON Schema, a data dictionary and sample rows for the joined file, which is what an LLM or RAG pipeline needs to read the table without guessing column meanings. It is turned on by default and can be switched off for a minimal output.

Can I join my own datasets?

Yes. Choose preset custom, pass 2 to 6 datastore resource ids as UUIDs in customDatasets, set customKey to year or to raw field names that every dataset shares, then pick customJoinType inner or left and customAgg none, sum or mean.

What licence applies to the output?

Datasets on data.gov.au are licensed under CC BY 4.0 unless the source record says otherwise, so attribution is attached to every output. includeAttribution writes a licence and source sidecar file that names the underlying records, which keeps a published chart or report compliant.

How do I get the file out of a run?

Files land in the run's key-value store as preset_join with your chosen extension, plus preset_attribution.json, preset_ai_ready.json and preset_verification.json. Dataset records are always JSON. You can download them from the Console, fetch them through the API, or set webhookUrl to have the file posted to your endpoint.

Need a data source that is not here?

We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.