San Diego Open Data API and Publishing Rules

San Diego, California maintains an official open data portal and API to publish municipal datasets for public reuse. This guide explains how the City manages dataset publication, API access, and the operational rules you must follow when contributing or using San Diego data. It covers responsible offices, how to publish, common compliance issues, enforcement pathways, and practical steps to request, update, or remove datasets.

Overview of the Open Data API and Publishing Rules

The City publishes datasets through its official Open Data Portal, which exposes machine-readable datasets and a Socrata-powered API for programmatic access https://data.sandiego.gov/^[1]. The portal provides dataset metadata, licensing statements, and dataset-level access controls. For API usage, the City relies on the SODA (Socrata Open Data API) conventions and developer documentation for endpoints, rate limits, and authentication https://dev.socrata.com/^[3]. The City's Open Government pages describe the program intent, governance, and contact points for dataset requests and policy interpretation https://www.sandiego.gov/open-government^[2].

• Dataset publishing: submit datasets or requests to the City Open Data team via the portal contact or designated intake process.
• Metadata requirements: title, description, update frequency, contact, license and provenance must accompany each dataset.
• Licensing: datasets are published with a stated license on the dataset page; follow the specific license terms listed per dataset.
• Data sensitivity and exemptions: the City will redact or withhold records exempt under state or federal law, including privacy or security exemptions.

Penalties & Enforcement

San Diego's Open Data Program enforces publishing standards and data-use expectations through administrative oversight by the Open Data team and applicable City departments. Specific monetary fines, escalations, or formal penalties tied to open-data publishing are not listed on the cited program pages and therefore are not specified on the cited page.^[2]

• Enforcer: Open Data team and the City department owning the dataset (contact via the portal or the City Open Government page). https://www.sandiego.gov/open-government^[2]
• Inspection and complaints: data quality or compliance complaints should be submitted to the portal contact or the dataset owner; procedures for formal review are listed on the City pages or dataset metadata.
• Fines/escalation: not specified on the cited page.
• Non-monetary sanctions: removal or restriction of data access, takedown orders, or administrative correction by the dataset owner or Open Data team.
• Appeals/review: if a requester disagrees with a withholding or takedown decision, contact information and next steps are identified by the dataset owner or the Open Data team's published contact procedures; specific statutory time limits are not specified on the cited page.

Applications & Forms

The City does not publish a universal paper form for dataset publication on the program page; dataset submission or request workflows are handled through the portal intake or the Open Data team contact listed on the City pages. If a dedicated intake form is required for a given dataset, it is linked from the dataset's metadata page on the portal https://data.sandiego.gov/^[1]. Fee information for publishing is not specified on the cited program pages.

• Form: dataset submission is through the portal's dataset creation or request interface; see the dataset contact on the portal for department-specific requirements.
• Fee: not specified on the cited page.

How to Publish a Dataset

Publishers must prepare machine-readable files, complete metadata, and confirm licensing. For API access, adhere to SODA conventions and API usage guidelines provided by the platform operator.^[3]

1. Prepare data in CSV, GeoJSON, or other machine-readable format and ensure PII or exempt content is removed.
2. Create metadata: title, description, update cadence, contact department, and license.
3. Submit via the Open Data Portal intake or contact the Open Data team for onboarding.
4. Configure API endpoints and SODA resource identifiers per the platform developer documentation https://dev.socrata.com/^[3].
5. Respond to any City review or requests for redaction before publication.
6. Maintain the dataset: update cadence and corrections as specified in metadata.

Common Violations

• Publishing personal data without redaction — may trigger removal or corrective action by the City.
• Incomplete or misleading metadata — may delay publication or require changes.
• Failure to follow departmental exemptions — dataset may be withheld per legal exemptions.

FAQ

Who manages the City of San Diego Open Data Portal?

The Open Data team in coordination with dataset owner departments manages the portal and publication processes.

Can external users push data to the portal?

External contributions are managed case-by-case; contact the Open Data team via the portal or City Open Government page for procedures.

Are there fees to publish a dataset?

Fees for dataset publication are not specified on the City program pages; check the dataset intake instructions or contact the Open Data team.

How-To

1. Identify the dataset owner department and potential exemptions.
2. Prepare machine-readable data and complete metadata per portal templates.
3. Submit a dataset request via the portal or contact the Open Data team.
4. Work with the City reviewers to address redaction or legal concerns.
5. Once approved, confirm API endpoints and monitoring cadence.

Key Takeaways

• Follow the portal metadata template to speed publication.
• Remove exempt or sensitive data before submission.

Help and Support / Resources

• City of San Diego Open Data Portal
• City of San Diego Open Government
• Socrata Developer Documentation (SODA)
• San Diego Municipal Code (Municode)

1. [1] City of San Diego Open Data Portal
2. [2] City of San Diego Open Government
3. [3] Socrata Developer Documentation