The Landscape Archive Foundation · open metadata standard · v1.1.0 draft

Global data layer and governance standard for living digital twins.

185 open landscape metadata standard

The public reference specification for Australian landscape architecture — botanical taxonomy, site context, mid-century climate screening, environmental risk, sustainability disclosure, cultural protocol, and BIM interoperability. The 169 profile remains supported for legacy exchange records. The published layer comprises structural definitions only; it does not include species inventories or client records.

Standards
185 (current) · 169 (supported)
Exchange profiles
1.1.0 (185) · 1.0.0 (169)
Licence
CC BY-NC-ND 4.0
Canonical source
Schema portal (GitHub temporarily unavailable)

The public GitHub repository is temporarily unavailable while we review access controls and security posture. The TLA-185 specification remains documented on this portal and at landscapearchive.org.

Adoption quickstart Validate a bundle Download open pack Browse the Data Dictionary Field registry Schema manifest 185 example 169 example Badge criteria CLI validator 185 crosswalk AASB S2 crosswalk Built environment exports

Reference adoption path

  1. Download the open pack — the schema manifest lists JSON modules, examples, and crosswalks. No login required.
  2. Validate an example — open the reference validator with the NSW coastal schoolyard 185 bundle.
  3. Cite in one deliverable — add the procurement sentence from landscapearchive.org/adopt to a studio brief, RFQ, or methods section.

Interim stewardship — The Landscape Archive Foundation is not yet incorporated. The specification and reference tooling are public infrastructure; this is not an ISO standard claim.

Recently published

Draft governance and consultation only — The Landscape Archive Foundation is not yet an incorporated entity.

International founding alliance — draft consultation

Independent organisations worldwide — practices, universities, public bodies, Traditional Owner and Indigenous protocol authorities, nurseries, and implementation partners — are invited to review draft charter language for the open landscape metadata standard. Participation is consultation only: no binding membership, no joint liability, and no obligation to adopt commercial Archive products. Affiliate partner referrals are unrelated.

Contact details submitted through charter consultation are used only for Foundation standard correspondence — not for marketing list sharing.

How it works

  1. Independent organisations (practices, universities, councils) keep full control of operations.
  2. The open standard provides shared JSON fields any BIM, CAD, or GIS tool can read.
  3. Validators check exports locally (browser or CLI); qualifying projects earn a Foundation Approved badge.
  4. Commercial tools (e.g. The Landscape Archive) implement the standard and may sell BIM assets on top.

See also how the standard works and commercial separation.

Schema modules

Built environment exports

Interchange profiles for architectural (IFC/BIM), civic (GeoJSON/GIS), and real-time (USD) pipelines — plus spreadsheet crosswalks. These are export bindings of the public field registry, not separate standards. Schema definitions live under /schema/built-environment/; worked examples at /examples/built-environment/. JSON schemas and validated emitters are the published baseline; native IFC STEP and USD file writers are scheduled for pipeline release.

Interchange profile Target format Purpose Status
IFC property sets IFC4 property sets (JSON) Map botanical and delivery fields to Pset_TLABotanical and environmental indicator subsets. MVP
GeoJSON civic registry GeoJSON FeatureCollection Civic registry — point placement, 2D canopy footprint, taxonomic identity, maintenance fields. MVP
USD metadata sidecar USD customData sidecar (JSON) LOD mesh references, seasonal asset paths, and tracking metadata for visualisation pipelines. MVP
Spreadsheet crosswalks Spreadsheet column mapping Nursery stock and maintenance headers mapped to canonical field-registry JSON paths for civic stock lists. Draft

Worked example: archive-gum.geojson, ifc-pset.json, usd-metadata.json, crosswalk row, TLA-185 bundle (Foundation Approved exemplar). See also awards data architecture alignment.

Selling plants & families

The open standard is open and free. Landscape Archive and other vendors can still sell Revit families, shop packs, and Library subscriptions — commerce sits in the implementation layer, not in the public vocabulary.

Independent stewardship

This portal is hosted separately from landscapearchive.com.au, so the community standard stays neutral while commercial products evolve. The Foundation holds the open schema; vendors compete on implementation quality.

Open source & licence

The 185/169 specifications and schema documentation are published under CC BY-NC-ND 4.0 — free for attribution, non-commercial reference, without modification. Commercial implementation requires a separate licence from The Landscape Archive Pty Ltd.

Landscape Archive application code, connectors, TLA Brain automation, and canonical species datasets remain under separate commercial terms. The Foundation standard layer is explicitly carved out from commercial IP.

How the standard is governed

The Foundation is the intended independent steward of the open standard — not a software vendor. The draft charter encodes four mechanisms:

  1. Written charter — the constitution every supporter signs.
  2. Two-tier power split — explicit reserved powers; anything unlisted stays with members.
  3. Council & voting — representatives vote; super-majority for schema 2.0 and charter changes.
  4. Independent arbitrator — neutral, binding dispute resolution over the charter.

It starts as an unincorporated working group — no new company — stepping up to an incorporated association only later, and only if it needs to hold assets or take grants.

Downloads

v1 JSON field names retain a legacy federation prefix for compatibility; Foundation branding applies to governance and public documentation.