Open data

Everything behind Learning Map is downloadable, machine-readable and openly licensed. Build something with it.

Downloads

Schemas at a glance

topics.json → {"topics": [{id, name, subject, domain, ageRangeStart, ageRangeEnd, description, evidence[], assessmentPrompt, centrality}]}

dependencies.json → {"dependencies": [{topicId, prerequisiteId, strength, reason}]}

Crosswalks → {meta, acara|nesa: {code: {…}}, map: {topicId: {topic, subject, ages, status, matches: [{code, confidence, score}]}}}. Statuses: mapped, no_f6_match/no_k6_match, beyond_f6/beyond_k6, general_capabilities.

Licences

Skill data: Marble Skill Taxonomy © Generative Spark, Inc., CC BY-SA 4.0 / ODbL 1.0. Curriculum text: © ACARA, CC BY 4.0. NSW outcome codes appear as reference labels only; official syllabus content is © State of NSW (NESA) and is not included in these files. Full details on the licensing page.

All alignments are candidate alignments — machine-suggested and unreviewed (v0.1).

Analytics

This site uses Plausible, privacy-friendly and cookieless — it counts visits in aggregate so we know which pages help, with no personal data collected and nothing sold.

Progress tracking ("Where we’re up to")

The optional tick-off feature on topic pages stores everything in the browser's localStorage, under one key, lm-progress. Nothing is transmitted anywhere — there's no server component, no API call, and no account. The schema is versioned ({"v": 1, "active": ..., "profiles": [{"id", "label", "ticks": {"<slug>": [state, evidenceMask, "YYYY-MM-DD", flags]}, "updated"}]}), keyed by the same stable skill slug used throughout this dataset, so a site rebuild never orphans a parent's data.

Export produces a plain JSON file in the same shape (learningmap-progress-YYYY-MM-DD.json), which can be re-imported on any device — imports merge by most-recent edit per skill and never delete anything. A future "share a snapshot" link (not yet built) will encode state only in the URL fragment, which browsers never send to a server, so even that never touches this or any other site's backend.

The generator's QA suite statically checks the shipped script for network calls (generator/qa.py, gate c13) — a build fails if it ever tries to send progress data anywhere.

How to cite this

Or in prose: “Learning Map (learningmap.au), an open map of 1,590 Australian primary-years skills by Ape Labs, built on the Marble Skill Taxonomy.”