Skip to content

Latest commit

 

History

History
74 lines (42 loc) · 6.97 KB

README.md

File metadata and controls

74 lines (42 loc) · 6.97 KB
Raw

Open Data Standards

Open Data Standards GitBook

Prepared by:

Azavea - Beyond Dots On A Map

990 Spring Garden Street, 5th Floor
Philadelphia, PA 19123
(215) 925-2600
http://www.azavea.com

Azavea Twitter Azavea Facebook Azavea LinkedIn Azavea GitHub

View and Contribute

The online version of the Open Data Standards Report is available as a GitBook.

You can view and contribute to the project by working on issues and issuing pull requests via the GitHub project.

Executive Summary

This document is an effort to outline the state of open data standards in several civic domains, as well as to suggest domains in which there is strong potential for developing new standards or some nascent work is complete but adoption is not yet widespread.

Why write this report?

Azavea is a B Corp with a mission to apply geospatial technology for civic, social, and environmental impact while advancing the state-of-the-art through research. We work on projects that range from climate change to public transit and from homelessness to public safety. Almost every project we develop relies, at least in part, on open data. We also developed and continue to operate the open data portal for Philadelphia, OpenDataPhilly, and we share much of our work by releasing our software under open source licenses (check out a few examples at OpenTreeMap, GeoTrellis, and DistrictBuilder). We want to encourage and cultivate broad use of open data, open source, open standards, and open algorithms, because we believe it results in better, more functional cities.

Why do open data standards matter?

Data analysis and visualization are important advocacy tools and have been used to help nonprofits acquire funding and government agencies choose priority locations for programming. For these projects to take place, one needs access to open data - but access to data that follows a standard formatting methodology is even better.

Open data is more value when it is formatted according to specified standards. Standardizing open data can improve data quality, compatibility with existing applications, and comparisons of data by location. When combined with open source applications, open data standards support the development of an ecosystem of tools that can be used in several locations.

Success Stories

Since 2005, the General Transit Feed Specification (GTFS) has become the common language for transit. Currently, over 700 agencies worldwide have adopted the GTFS standard for reporting public transit schedules. Open source software like OpenTripPlanner uses GTFS and OpenStreetMap data to enable journey planning and routing. The Network Analyst extension for Esri ArcMap also incorporates GTFS data for transit routing. While mainly used for trip planning, GTFS data can also be used for data visualization and maps, measures of accessibility, and timetable creation.

Local Inspector Value Entry Specification (LIVES) was developed by Code for America in cooperation with Yelp and the City of San Francisco to enable municipalities to publish restaurant inspection information to Yelp. According to Yelp, 20 municipalities have LIVES feeds, to date. The fact that this standard integrates with Yelp, means that the public has easy access to restaurant health score data in the cities that have adopted the standard.

Criteria for Selecting Standards

This report is organized into two sections, one for standards that have been released and are in use in at least a few cities, and a second section for potential new standards.

The criteria used to select the standards includes the following:

  • Location-based - Azavea is a geospatial analysis and visualization company, so we have focused on standards that have a location component; that turns out to not limit us very much as the vast majority of data being released by government has a location component to it.

  • Published standard – Documentation for the specification has been published and is available online.

  • Machine-readable - Based on JSON, CSV, XML, or similar structure that can be consumed by software in a consistent, organized way

  • Adoption - Adopted by at least one large city or heavily used by an aggregator of civic data

What can I do to support open data standards?

There are several ways you can support open data standards.

  • Contact the Open Data Officer for your city to learn about the ways that open data standards are being used in your region.

  • Explore the open data portal for your city. If you see open data that is not published to a standard, use the contact information provided on the open data portal to notify the team or contact the government department that manages data efforts.

  • Find your local elected officials and contact them to tell them about the importance of supporting open data standards.

  • Use open data that is published with a standard in a civic hacking project. Build tools that utilize open data standards - prove their utility!

  • Contribute to OpenStreetMap through the IDeditor, Humanitarian OpenStreetMap Team Tasking Manager, or at a Missing Maps Mapathon. OpenStreetMap uses several open data standards to provide a free and collaborative map of the world.

License

Creative Commons License
The Open Data Standards Report by Azavea is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.