Sydney Open Data Publication Requirements - Council Guide
Sydney, New South Wales requires council datasets to meet publication standards that support reuse, transparency and interoperability. This guide summarises the City of Sydney's open data publication expectations, dataset format and metadata standards, licensing guidance and how to request or publish datasets as an authorised council officer or contractor. It highlights enforcement, reporting routes, applications and practical steps for preparing datasets so they are discoverable on the City of Sydney open data portal.
Scope & applicable instruments
The City of Sydney publishes datasets through its official open data portal and follows council-level open data guidance for dataset formats, metadata and licensing. For the City of Sydney's published policy and detailed portal requirements see the council pages referenced below [1] and the City of Sydney data portal [2].
Standards for datasets
Key dataset standards the council expects when publishing open data are: consistent machine-readable formats, clear field-level metadata, spatial references for geodata, and an explicit licence. Publication workflows typically require validation, metadata completion and an assigned dataset owner within the council.
- File formats: prefer CSV, GeoJSON, JSON or other machine-readable formats where appropriate.
- Metadata: include dataset title, description, owner, update frequency, fields and coordinate reference system for spatial data.
- Licence: clearly state the licence used for reuse (see council policy for the exact licence applied).
- Privacy and redaction: remove or aggregate personal or sensitive information before release.
Penalties & Enforcement
The council open data guidance and portal pages do not publish criminal or civil fine schedules specifically tied to dataset publication on the visible pages cited; where numeric penalties or statutory offences apply they are lawfully determined under separate legislation or council enforcement policies and are not specified on the cited open data pages [1].
- Enforcer: City of Sydney (open data or information management team) and applicable regulatory departments; specific enforcement office is not specified on the cited page.
- Inspection and complaints: report issues or suspected non-compliance via the City of Sydney contact or portal report routes (see Help and Support / Resources below).
- Monetary fines: not specified on the cited page.
- Escalation: the cited open data policy pages do not list escalation monetary ranges for first, repeat or continuing offences.
- Non-monetary sanctions: likely orders to remove or correct data, access restrictions or administrative actions; specific sanctions are not specified on the cited page.
Appeals, review and time limits
The open data guidance pages do not set out a formal appeals or review tribunal for publication decisions; appeals or reviews of council administrative decisions follow standard City of Sydney review or complaint procedures and applicable provisions under New South Wales administrative law (not specified on the cited open data pages) [1].
Defences and discretion
Council discretion may apply for exemptions on grounds of privacy, security or commercial confidentiality; the open data pages reference assessment and exemption processes but do not publish an exhaustive list of permissible defences on the cited pages [2].
Common violations and typical outcomes
- Publishing identifiable personal data: outcome—dataset removal and remediation, contact the information governance team.
- Incomplete metadata or missing licence: outcome—dataset not accepted or returned for correction.
- Incorrect spatial reference or format: outcome—technical rejection until corrected.
Applications & Forms
No specific public dataset publication application form is published on the cited open data pages; dataset publication is normally managed through internal council workflows and the City of Sydney data portal submission channels, and no standalone public form number is specified on the cited pages [2].
Operational steps to publish a dataset
- Prepare: confirm dataset owner, check for sensitive data and select machine-readable format.
- Document: complete full metadata and choose the licence consistent with council guidance.
- Validate: run format and CRS checks for geospatial files.
- Submit: publish via the City of Sydney data portal or contact the Open Data team for assistance.
FAQ
- Who decides whether a dataset can be published?
- The dataset owner together with City of Sydney information governance or the open data team make publication decisions based on council policy and privacy obligations.
- What licence does the City use?
- The council open data pages indicate a clear licence is required but the cited pages should be consulted for the exact licence text and selection [1].
- How long does publication take?
- Publication timing depends on dataset complexity and review; exact standard timeframes are not specified on the cited open data pages.
How-To
- Identify dataset owner and check for personal or sensitive information.
- Choose an appropriate open format (CSV, GeoJSON, JSON) and prepare field-level metadata.
- Run validation checks and convert spatial data to a standard CRS if needed.
- Submit dataset to the City of Sydney data portal or contact the Open Data team for publication support.
- Monitor the portal listing and respond to any council feedback for correction.
Key Takeaways
- Remove personal and sensitive data before publishing.
- Use clear metadata and an explicit licence to maximise reuse.
Help and Support / Resources
- City of Sydney contact and customer service
- City of Sydney open data portal
- City of Sydney official site