Christchurch Open Data Publication Checklist - Bylaw Guide

Technology and Data Canterbury 3 Minutes Read ยท published February 12, 2026 Flag of Canterbury
Christchurch, Canterbury organisations publishing open datasets or APIs must align technical publication with council policy, privacy rules and public request procedures. This checklist summarises council guidance, the municipal data portal and operational steps to prepare, licence and publish datasets so they are discoverable, reusable and compliant with Christchurch City Council expectations. Use the checklist to verify metadata, licensing, privacy screening, versioning and complaint pathways before public release. The guidance here is practical and tailored for council staff, contractors and local service providers working in Christchurch and the wider Canterbury region.

Requirements and standards

Follow Christchurch City Council standards for metadata, accessibility and formats before publishing. Reference the council open data guidance and publication portal when preparing datasets and APIs: Christchurch Open Data guidance[1] and the official data portal at data.ccc.govt.nz[2].

  • Prepare a clear dataset title, description and machine-readable metadata (CSV, JSON, GeoJSON).
  • Include provenance and update frequency, with changelog or version tags.
  • Confirm there are no commercial restrictions or third-party fees on redistribution.
  • Conduct a privacy and confidentiality review to remove or aggregate personal or sensitive data.
  • Provide API documentation, rate limits and example requests for developers.
  • Document retention and archival plans for published datasets.
Register dataset landing pages on the council portal to improve discoverability.

Publication checklist

  • Metadata file (title, description, contact, licence) attached to dataset or API.
  • Licence selected (e.g., CC BY or council-preferred licence) and licence text included.
  • Privacy impact assessment completed and PII removed or protected.
  • API endpoints documented, with example payloads and error codes.
  • Dataset owner and technical contact listed for user queries and corrections.
  • Publication schedule and update cadence published on the dataset landing page.
Add a contact point for data corrections to reduce repeat takedown requests.

Penalties & Enforcement

The Christchurch City Council open data pages and portal do not list specific monetary fines or statutory penalties for publishing datasets or APIs incorrectly; fines and enforcement for breaches are not specified on the cited council pages. For matters of non-compliance, the council relies on internal remediation, takedown requests and formal complaints processes administered by council teams rather than a fixed bylaw fine schedule.[1]

  • Enforcer: Information Management together with Legal Services and relevant operational teams in Christchurch City Council.
  • Inspection/complaint pathway: submit a complaint or data issue to Christchurch City Council via the official complaints page.
  • Appeal/review: internal review by council, then external complaint to the Office of the Ombudsman under LGOIMA where applicable; specific statutory time limits for access and review derive from central government legislation (see resources).
  • Defences/discretion: council may accept a reasonable excuse, apply exemptions or require redaction; formal variances are managed case-by-case.
If a dataset contains personal information, pause publication and consult Legal Services immediately.

Applications & Forms

No specific publishing application form is required on the council open data page; submission and complaint channels are available for issues or takedown requests via the council contact/complaints route.[3]

Data licensing, privacy and quality checks

  • Choose an open licence and record it on the dataset landing page.
  • Run automated validation for schema conformance and sample records for PII.
  • Publish machine-readable metadata (DCAT or similar) for catalogue integration.

How-To

  1. Identify dataset owner, scope and licence; complete privacy screening and metadata draft.
  2. Validate formats and prepare machine-readable files or API endpoints with documentation.
  3. Upload to the council data portal or coordinate with Information Management for publication.
  4. Monitor feedback, correct errors and update the changelog on each release.
  5. Respond to complaints via the council complaints page and follow internal remediation steps.
Keep a public changelog to document corrections and release notes.

FAQ

Who manages Christchurch open data?
The Information Management and Data teams at Christchurch City Council manage publication and the city data portal.
Are there fines for publishing data incorrectly?
Specific fines or penalty amounts are not specified on the council open data pages; enforcement is handled through remedial actions and complaints processes.[1]
Do I need a licence to publish council data?
Yes, apply a clear open licence and document it on the dataset landing page; if unsure, consult Legal Services before release.

Key Takeaways

  • Complete privacy screening and attach clear machine-readable metadata before publishing.
  • Use the council data portal and follow council guidance to ensure discoverability.
  • Report issues via the official complaints channel for remediation and review.

Help and Support / Resources

  1. [1] City of Christchurch Open Data guidance
  2. [2] City of Christchurch data portal (data.ccc.govt.nz)
  3. [3] City of Christchurch complaints and reporting

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data