Nashville City Bylaws for Publishing Open Data

Technology and Data Tennessee 4 Minutes Read · published February 07, 2026 Flag of Tennessee

Nashville, Tennessee requires city departments to follow defined practices when publishing open data to ensure transparency, privacy protection, and reuse. This guide explains who manages publication, typical approval and metadata workflows, compliance checks, and how departments publish datasets to the City of Nashville open data portal. It is aimed at departmental staff, data stewards, and members of the public who request or reuse municipal data. Where official procedural detail or sanctions are not published on the cited municipal pages, this guide notes that the item is "not specified on the cited page" and points to the authoritative city source for confirmation.

How departments publish open data

Departments prepare datasets with clear metadata, classification, and privacy checks before submitting to the centralized portal. Typical steps include data cleanup, removing personal or sensitive fields, setting an update schedule, and adding licensing or use terms. Submission and publication are managed through the city portal and coordinated with the Information Technology or Open Data team.

  • Prepare dataset files and canonical field definitions.
  • Perform privacy and legal review; remove or redact personal data.
  • Define update frequency and metadata (title, description, tags).
  • Submit dataset package to the city Open Data intake process and assign a steward.
  • Publish to the public portal and monitor datasets for accuracy and requests.
Coordinate early with the IT/Open Data team to avoid rework and privacy issues.

Public publishing generally uses the City of Nashville open data portal as the authoritative catalog and hosting point for machine-readable datasets data.nashville.gov[1]. The portal lists datasets, provides dataset APIs, and links to departmental contacts for each dataset.

Standards, formats, and licensing

Departments are expected to publish data in machine-readable formats (CSV, JSON, GeoJSON where applicable) with clear field names and data dictionaries. Licensing and reuse terms are published with each dataset on the portal; if a formal city open-data license or policy exists, consult that policy for permitted reuse and attribution.

  • Preferred formats: CSV, JSON, GeoJSON for spatial data.
  • Include metadata: contact, update schedule, last-updated timestamp.
  • Privacy checks: redact PII and comply with applicable state and federal privacy rules.
Machine-readable open formats and metadata make datasets reusable by the public and developers.

Penalties & Enforcement

Publication of open data is primarily an administrative process; specific fines or criminal penalties for publishing (or failing to publish) datasets are not commonly listed on the public portal. Where the city has formal enforcement measures for noncompliance with open-data procedures, those measures would be described in the governing policy or departmental procedures.

  • Monetary fines: not specified on the cited page.
  • Escalation (first/repeat/continuing offences): not specified on the cited page.
  • Non-monetary sanctions: administrative orders, corrective requirements, or removal of publishing privileges—specific remedies not specified on the cited page.
  • Enforcer: Information Technology / Open Data team and the dataset steward in the publishing department; use the portal contact for complaints or compliance inquiries data.nashville.gov[1].
  • Appeal/review routes and time limits: not specified on the cited page; consult departmental policy or Metro legal for appeal procedures.
  • Defences/discretion: reasonable excuse, privacy/confidentiality exemptions, or approved redaction processes—detailed grounds not specified on the cited page.
If enforcement or fines are a concern, request formal guidance from Metro Legal or the IT/Open Data office.

Applications & Forms

Submission is typically done through the city open data intake on the portal or by contacting the Open Data/IT team. A formal dataset intake form or template is available on the portal when departments request publishing; if no public form is published, departments use internal submission procedures.

  • Named form or template: use the portal intake or contact the Open Data team for the current template; specific form number not specified on the cited page.
  • Fees: none specified for dataset publication on the cited page.
  • Submission: upload via the portal or email the designated Open Data contact listed on the portal.

How-To

  1. Identify the dataset owner and steward in your department.
  2. Clean the data, remove PII, and create a clear data dictionary.
  3. Choose a machine-readable format and set the update cadence.
  4. Submit the dataset package via the City of Nashville open data portal intake process.
  5. Respond to any privacy or legal review requests and approve publication.

FAQ

Who manages the City of Nashville open data portal?
The Information Technology / Open Data team manages the portal, with datasets stewarded by individual departments; see the portal for departmental contacts.
What formats should datasets use?
Publish machine-readable formats such as CSV, JSON, or GeoJSON and include metadata and update schedules.
How do I request a new dataset be published?
Contact the dataset steward or use the intake process on the City of Nashville open data portal to request publication.

Key Takeaways

  • Use the official portal as the publishing point and include full metadata.
  • Conduct privacy and legal review before publishing.
  • Coordinate with the IT/Open Data team and departmental stewards for intake and updates.

Help and Support / Resources


  1. [1] City of Nashville Open Data Portal