London Open Data Publication Requirements - City Policy
London, England requires public bodies and publishers that contribute to city open-data portals to follow the Greater London Authority's open data principles and publisher guidance. This article explains the publication expectations for datasets on official London platforms, outlines enforcement and compliance pathways, and lists practical steps for preparing, licensing, and submitting datasets. It also summarises common violations, actions an organisation should take to reduce legal and privacy risk, and where to get official help from London Datastore and the Greater London Authority.
Penalties & Enforcement
The Greater London Authority (GLA) and the London Datastore set publication standards and guidance for datasets used by city bodies. The cited policy pages describe compliance expectations and contact routes for publisher support but do not set statutory fines on those pages. For specific enforcement processes, contact details and escalation procedures, consult the official policy and publisher guidance linked below.[1]
- Enforcer: Greater London Authority / London Datastore administrators manage policy compliance and publisher support.
- Inspections and audits: not specified on the cited page.
- Monetary fines: not specified on the cited page.
- Court or legal action: not specified on the cited page.
- Complaint pathway: contact publisher support or the GLA open-data contact points listed on the official pages.
Appeals, Review & Defences
Appeal and review routes, including time limits for appeals or formal reviews, are not specified on the cited policy pages. Defences commonly available under policy practice include demonstrating a reasonable effort to anonymise personal data, holding an appropriate licence for third-party data, or using permitted exemptions for security or privacy; specific acceptances and timelines should be confirmed with publisher support.[1]
Applications & Forms
No statutory form number is published on the cited pages for dataset publication; publisher onboarding and dataset submission details are provided through London Datastore guidance rather than a single universal form, and fee schedules for publishing are not specified on the cited policy pages.
Common Violations and Typical Outcomes
- Publishing personal data without proper anonymisation — action: dataset removal or takedown request; monetary penalties not specified on the cited pages.
- Missing or ambiguous licence information — action: required relabelling or licence clarification.
- Poor metadata or format non-conformance — action: correction requests and guidance from publisher support.
- Out-of-date or misleading datasets — action: update notices or removal until corrected.
FAQ
- How do I publish a dataset to London Datastore?
- Follow the London Datastore publisher guidance and contact publisher support for onboarding and dataset submission details; see the official guidance linked below.[1]
- Which licence should I apply to my dataset?
- London public sector data commonly uses an open licence such as the Open Government Licence (OGL); consult the authoritative OGL text for exact terms and attribution requirements.[2]
- What happens if I publish data that breaches privacy?
- The dataset may be subject to takedown or correction and you may need to notify data-protection officers; specific sanctions and time limits are not specified on the cited pages.
How-To
- Prepare the dataset: validate fields, add clear metadata, and confirm formats (CSV, GeoJSON, etc.).
- Sanitise personal data: remove or anonymise personal identifiers and assess privacy risks.
- Choose a licence: select an open licence such as the OGL and document attribution requirements.Open Government Licence v3[2]
- Submit or notify: use the London Datastore publisher guidance and contact publisher support to submit or request publication.
- Maintain and monitor: update datasets regularly and respond to user feedback or takedown requests.
Key Takeaways
- Follow GLA and London Datastore guidance for metadata and licensing to reduce removal risk.
- Always assess and mitigate privacy risks before publication.
Help and Support / Resources
- London Datastore - publisher help and support
- Greater London Authority - Open data policy
- Data.gov.uk - guidance for public sector publishing