Fresno Open Data Portal, API & Dataset Requests
The City of Fresno, California provides a public Open Data Portal and related API endpoints to increase transparency and allow residents, researchers, and businesses to access municipal datasets. This guide explains how to find datasets, request records or new dataset exports, use APIs, who enforces access and compliance, and the practical steps to appeal or escalate denials. It summarizes the official channels maintained by the City of Fresno and the City Clerk for public records requests, along with common issues requesters encounter and the administrative contacts to reach for technical or legal questions.
Where to find datasets and APIs
Search the City of Fresno Open Data Portal for published datasets, metadata, and API access. Many datasets include machine-readable endpoints and CSV/GeoJSON exports. For formal public records requests that are not available as datasets, use the City Clerk public records request process.
City of Fresno Open Data Portal[1] and City Clerk public records request page[2] are the primary official entry points for dataset discovery and formal requests.
Access methods and API basics
Most published datasets include RESTful API endpoints, frequently supporting filters, pagination, and format parameters. Typical steps:
- Find dataset metadata and API documentation on the portal.
- Use query parameters to filter fields and reduce payloads.
- Check terms of use and any licensing notes in the dataset metadata.
- Contact the dataset steward listed in the metadata for technical questions.
Penalties & Enforcement
The City does not appear to publish civil fines or criminal penalties specific to accessing published open datasets or using the API on the portal pages cited; fines and enforcement for broader records or ordinance violations are handled by the enforcing department and relevant municipal code. Specific monetary fines or per-day penalties for improper access or misuse of the portal are not specified on the cited pages.[1]
- Enforcer: dataset stewards, City IT/GIS teams, and the City Clerk for public records requests.
- Inspection and compliance actions: technical suspension of API keys or access if misuse is detected; the portal pages do not list formal escalation amounts or schedules (not specified on the cited pages).
- Fines: not specified on the cited pages for open data access or API use.
- Non-monetary sanctions: access restrictions, takedown of dataset exports, administrative orders, or referral to legal counsel (not specified in exact form on the cited pages).
- Appeals/review: follow City Clerk procedures for public records denials; specific time limits for appeals are not listed on the cited portal pages and should be confirmed with the City Clerk.[2]
Applications & Forms
The portal provides dataset export and API access directly for published material; for unpublished records or records requiring redaction, submit a public records request via the City Clerk. The specific form name or code for dataset requests is not specified on the cited pages; use the City Clerk public records request process linked above to submit requests or ask whether a dedicated dataset-request form exists.[2]
Common violations and typical outcomes
- Bulk scraping without authorization — outcome: access throttling or IP blocking (penalty details not specified on the cited pages).
- Requesting non-published or exempt records — outcome: denial with citation to exemption; appeal via City Clerk.
- Misuse of data contrary to posted licensing — outcome: demand to cease use or licensing enforcement actions (specific sanctions not specified).
Action steps
- Search the Open Data Portal for the dataset and check metadata for steward contact and last-updated dates.
- If the dataset is not published, file a public records request with the City Clerk and cite the dataset or records you need.
- If you receive a denial, request the written basis and follow the City's appeal instructions; escalate to the department steward for technical errors.
- Pay any official fees if the City Clerk provides a cost estimate for reproduction of records; the portal does not list standard fees for dataset requests.
FAQ
- How do I request a dataset that isn't published?
- Submit a public records request to the City Clerk describing the dataset, time range, and format desired; include a link or description of the dataset fields if available.[2]
- Are there fees for API access to published datasets?
- Published datasets and API endpoints are generally available without direct API fees; any charges for compiled or specialized extracts are handled through the City Clerk process and are not specified on the portal pages.[1]
- Who do I contact about incorrect or out-of-date data?
- Contact the dataset steward listed in the dataset metadata on the Open Data Portal or submit a technical inquiry through the portal contact link.[1]
How-To
- Search the Open Data Portal for the dataset name, keywords, or geographic filters.
- Open the dataset page and review metadata for API endpoints, field descriptions, and steward contact details.
- Use the API query parameters to filter and request the needed fields; download CSV or GeoJSON if available.
- If the dataset is not available, prepare a clear public records request and submit it to the City Clerk with contact information and desired formats.
- If denied, request the written reason and follow the City Clerk appeal instructions or contact the dataset steward for technical corrections.
Key Takeaways
- Start at the Open Data Portal for published datasets before filing a formal request.
- Unpublished records require a City Clerk public records request; follow their procedure for appeals.
Help and Support / Resources
- City of Fresno Open Data Portal
- City Clerk - Public Records Requests
- City of Fresno Information Technology / GIS
- Planning & Development Department