
Asheville's City Council used Resolution No. 15-189 in October 2015 to direct the City Manager to adopt an open data policy, setting deadlines for technical standards, a release plan, a public data catalog and community feedback.
What the resolution does
Resolution No. 15-189 is a directive rather than a finished rulebook. The council told the City Manager to put an open data policy in place and spelled out the order in which the pieces had to arrive: technical publishing standards first, then public feedback on those standards, then a citywide release plan and an ongoing catalog of available datasets.
The preamble frames open data as proactive disclosure, a natural extension of residents' right to public information, and as a platform for local software developers, entrepreneurs and civic groups.
Adoption context
Asheville had been active in the civic technology community for several years before the vote; the resolution itself points back to the city hosting an Open Data Day event in October 2012. By 2015 a number of mid-sized cities were formalizing informal open data practices, and a council resolution that delegates the details to staff was a common, low-friction way for local government to do that.
Key provisions
- Within 180 days, the IT Services department publishes technical standards for releasing public datasets in raw form through a single portal.
- The communications and public engagement division gathers feedback on the implementation plan within 60 days and coordinates yearly community collaboration.
- Within twelve months, IT works with departments on an initial open data release plan.
- New software systems should, where practical, be chosen so they make open data release easier.
- The city maintains an open data website that doubles as a catalog of what is available.
Guidelines this policy reflects
Annotators of the original collection tagged this text against a wide spread of guidelines. The strongest matches are proactive release, lists of holdings, open formats, data portals and websites, timelines and data quality, with public participation and future review built into the schedule.
What happened next
The resolution handed implementation to city staff, who went on to run a public open data portal and publish data through it. Readers researching the current state of Asheville's program should check the city's own website, since portal platforms and dataset lists have changed over time.
Why this matters for your business data
The resolution's sequence (standards, then a release plan, then a catalog) is the same order a private company should follow before putting operational data in front of buyers. Knowing what you hold and in what format is what turns raw records into an asset with a price. Our guide on moving from open data policy to data value walks through that shift, and the valuation calculator gives a first estimate.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Is Asheville's 2015 resolution itself the open data policy?
Not exactly. It is a council directive instructing the City Manager to adopt and run a policy, with deadlines for technical standards, public feedback and a release plan. The operational detail was left to staff, which is a common pattern for council resolutions on open data.
Does the resolution require new software to support open data?
It asks the IT department to work, whenever practical, toward new software systems that make releasing open data easier. That is a soft requirement, but it pushes procurement decisions toward systems that can export clean, structured data.
How does the public take part?
The resolution assigns the communications and public engagement division to collect comment on the implementation plan within 60 days and to organize yearly opportunities for community collaboration around the open data program.
Guidelines this policy reflects
- 1. Proactive Release
- 3. Goals and Values
- 4. Lists of Holdings
- 8. Open Formats
- 9. Thoughtful Formats
- 10. Open Access
- 11. License-Free
- 18. Data Portals and Websites
- 21. Data Collection
- 22. Real-Time Updates
- 23. Permanent Access
- 24. Oversight Authority
- 25. Binding Regulations
- 26. Public Participation
- 27. Timelines
- 28. Data Quality
- 30. Partnerships
- 31. Future Review
Other policies in NC
Sources
Updated December 31, 2024.