Sort
Open311 Inquiry APIPublic FacilitiesServices
OpenPlans
| Version: 1
Open 311's Inquiry API is a standardized protocol for information about public spaces and services. The Open311 Inquiry API consists of a set of content related to the services provided by the city, a city facilities list (concerning meaning not GIS, although there will be geospatial attributes for the facilities), and a RSS feed that contains information about daily status of public services and facilities.
Details
  • License: No information
  • About the Publisher: OpenPlans is a non-profit, technology based organization that aims to open up government data and improve public transportation systems
  • Updated by Publisher: 4/14/2017
  • Level of Use: Standard has only been adopted in NYC
  • Open License: Yes
  • Transferable to other Jurisdictions: Potential to expand. At the moment, version 1 is specific to NYC
  • Stakeholder Participation: Public can contribute to the standard's 'issue tracker' on GitHub
  • Consensus-based Governance: Mailing List for ideas for development, inquiries, and concerns
  • Extensions: Open311 Today is an RSS feed that provides updates on daily schedules for public facilities and services
  • Machine Readable: Retrieves the data in XML format (and support JSON structure when indicated by API)
  • Human Readable: Schema has resource identifiers
  • Requires Real-Time Data: 311 Today consists of a RSS feed that streams data about daily schedules and statuses of government services/facilities
  • Metadata: No information
Added to directory: 7/9/2017
Open311 GeoReport APIPublic FacilitiesService Requests
OpenPlans
| Version: 2
API standardizes service requests, eases coordination, and encourages accountability between the government and the public
Details
  • License: No information
  • About the Publisher: OpenPlans is a non-profit, technology based organization that aims to open up government data and improve public transportation systems
  • Updated by Publisher: 4/11/2017
  • Level of Use: Cities: Toronto, ON, GieBen, Deutschland, Bonn, Deutschland,Helsinki, Suomi, Lamia, Ellada, Baltimore, MD, Bloomington,IN, Boston, MA, Brookline, MA, Chicago, IL, Columbus, IN, Grand Rapids, MI, Peoria, IL, San Francisco, CA, Washington D.C.. Development Stage: Quebec, QC, Surrey, BC, Zurich, Schweiz, Zaragoza, Spain, Lisbon, Portugal,Philadelphia, USA
  • Open License: Yes
  • Transferable to other Jurisdictions: GeoReport API has been adopted in various jurisdictions across the US. The OPEN311 does not specify the codes, making it possible for the API to be applied to whatever civic services specifically offered in that city
  • Stakeholder Participation: Collaboration between developers, government, and nonprofit organizations
  • Consensus-based Governance: The public can contribute to the standard's 'issue tracker' on GitHub
  • Extensions: MySociety has proposed an extension to better update clients about status changes of requests to better serve citizens with platforms such as fixmystreet (in the UK). The extension allows for more communication from the government body to the client. This extension proposes the methods POST/GET Service Updates. See extension's proposal here: https://www.mysociety.org/2013/02/20/open311-extended/
  • Machine Readable: API retrieves the data in XML format and supports JSON format when indicated by the API. The content of the API manages two main resources consisting of services and service requests. Requests are handled over HTTP to retrieve data in XML format, and in JSON when denoted by service discovery. Jurisdiction_ID will be globally unique variable in order to clarify the city implementing the API (required only when entire interface serves more than one jurisdiction). The API employs 7 API methods for services and service requests. These methods include: GET service list, GET service definition, POST Service Request, GET request_id from a token, GET service request(s). The GET service method handles what services are available to the client user based on the unique service_code. The POST service request handles requests posted by the client to the government body. Open311 requires a location when requesting a service. GET service request(s) provides records of service requests based on date thresholds, service codes, service request IDs, and status
  • Human Readable: Open311 follows the REST schema and uses human readable identifiers to label the data
  • Requires Real-Time Data: The API Gets and Posts service requests in real time
  • Metadata: There is a required resource for specifying metadata. The GET service definition method of the API provide description for the service being requested by adding metadata=true to it response
Added to directory: 7/12/2017
Open311 GeoReport BulkPublic FacilitiesService Requests
OpenPlans
| Version: No information
Data format for publishing bulk datasets of service requests; datasets that would otherwise be too bulky for an API request.
Details
  • License: No information
  • About the Publisher: OpenPlans is a non-profit, technology based organization that aims to open up government data and improve public transportation systems
  • Updated by Publisher: 1/2/2017
  • Level of Use: Cities: Bloomington,IN, Louisville, KY San Diego, CA. Development Stage: Raleigh, NC, Kansas City, MO
  • Open License: Yes
  • Transferable to other Jurisdictions: GeoReport has been adopted in various jurisdictions across the US. The OPEN311 does not specify the codes, making it possible for the API to be applied to whatever civic services specifically offered in that city
  • Stakeholder Participation: Collaboration between developers, government, and nonprofit organizations
  • Consensus-based Governance: The public can contribute to the standard's 'issue tracker' on GitHub and edit the open311 Wiki
  • Extensions: It is recommended to adhere strictly to the specification
  • Machine Readable: Bulk datasets are downloadable in CSV or another machine-readable format
  • Human Readable: Open311 follows the REST schema and uses human readable identifiers to label the data
  • Requires Real-Time Data: Full datasets usually published annually, with a current year dataset also available
  • Metadata: No information
Added to directory: 6/19/2017
Land and BuildingPublic FacilitiesBuildings
Local Government Association (LGA)
| Version: 1.4
The Local Government Transparency Code requires that local authorities publish details of all their fixed (land and building) assets. This includes all properties owned or used by local government, including those where contractual work takes place, public parking facilities, and social housing.
Details
  • License: Data providers are encouraged to publish under the Open Government Licence. While the LGA maintains a copyright to the documentation, the standard does not appear to be licensed
  • About the Publisher: The Local Government Association represents the interests of English and Welsh municipal councils in national government. The LGA also promotes communication between local government authorities and develops best practices. LGA standards have been developed in response to the UK's Local Government Transparency Code, which encourages the publication of government data in standardized machine-readable formats.
  • Updated by Publisher: 6/5/2015
  • Level of Use: 374 District and County Councils are members of the LGA
  • Open License: Yes
  • Transferable to other Jurisdictions: Fields require unique codes specific to British property ownership
  • Stakeholder Participation: The Local Government Association consists of local government officials who collaborate to develop best practices for local authorities, the would-be stakeholders.
  • Consensus-based Governance: Although schemas and documentation are held on GitHub, changes can only be decided by the LGA
  • Extensions: The schema contains many optional fields, but additional fields are not supported.
  • Machine Readable: CSV format required
  • Human Readable: CSV template has readable headers
  • Requires Real-Time Data: Asset reporting typically happens annually
  • Metadata: No information
Added to directory: 8/20/2017
Public ToiletsPublic FacilitiesSanitation
Local Government Association (LGA)
| Version: No information
A CSV template for describing details of toilet services where local government is responsible for cleaning and maintenance. Details include location, accessibility, hours of operation, and additional amenities
Details
  • License: Data providers are encouraged to publish under the Open Government Licence. While the LGA maintains a copyright to the documentation, the standard does not appear to be licensed
  • About the Publisher: The Local Government Association represents the interests of English and Welsh municipal councils in national government. The LGA also promotes communication between local government authorities and develops best practices. LGA standards have been developed in response to the UK's Local Government Transparency Code, which encourages the publication of government data in standardized machine-readable formats.
  • Updated by Publisher: 11/14/2014
  • Level of Use: 378 District and County Councils are members of the LGA
  • Open License: Yes
  • Transferable to other Jurisdictions: While some fields take URIs that are specific to UK locations, these fields are not required
  • Stakeholder Participation: The Local Government Association consists of local government officials who collaborate to develop best practices for local authorities, the would-be stakeholders.
  • Consensus-based Governance: Although schemas and documentation are held on GitHub, changes can only be decided by the LGA
  • Extensions: The LGA provides a CSV template, and extensions are not supported by the LGA data portal
  • Machine Readable: CSV format required
  • Human Readable: CSV template has readable headers
  • Requires Real-Time Data: Dates included in the applications are noted, but there is no requirement for consistent publication
  • Metadata: No information
Added to directory: 8/20/2017
Urban StructuresPublic FacilitiesOntology
The Ontology Engineering Group
| Version: 0.1
Vocabulario para la representación de equipamientos is an ontology for describing public infrastructure such as parking facilities and their accessibility
Details
  • License: Creative Commons Attribution License 4.0 International
  • About the Publisher: The Ontology Engineering Group is based at the Computer Science School at Universidad Politécnica de Madrid. It is widely recognised in Europe in the areas of Ontology Engineering, Semantic Infrastructure, Linked Data, and Data Integration. Oscar Corcho has collaborated with members of Spanish city councils and other Spanish organizations to draft vocabularies for linked open data
  • Updated by Publisher: 6/25/2015
  • Level of Use: No information
  • Open License: Yes
  • Transferable to other Jurisdictions: This vocabulary is intended to be used by municipalities across Spain, but could be transferable. Data class and property names that are not inherited are in Spanish
  • Stakeholder Participation: The contributors to this vocabulary includes members of Spanish city councils as well as a member of Localidata, a Spanish start-up specializing in open data
  • Consensus-based Governance: No way for the public and interested parties to contribute to the development of vocabularies
  • Extensions: No information
  • Machine Readable: Although no OWL schema is provided, this vocabulary is cross-referenced with existing ontologies according to its documentation
  • Human Readable: An HTML documentation page makes the ontology schema human-readable
  • Requires Real-Time Data: No information
  • Metadata: Namespaces used are declared in section 1.1 of the documentation. This vocabulary extends schema.org, GeoNames, and other OEG Ontologies
Added to directory: 8/30/2017
Open511Public FacilitiesRoad Construction
Open North
| Version: 1
Open511 intends to make road event data lightweight and accessible to the public. The specification intends to facilitate communication among transportation agencies and other government bodies. Open511 format provides a level of transparency, interoperability, and simplicity that exceeds current intelligent transportation systems. The API retrieves the data in XML format
Details
  • License: Open Government License
  • About the Publisher: Open North, a Canadian non profit organization, aims to creates online tools that encourage civil society to engage more openly and actively with their government. For the Open511 specification, Open North teamed up with transportation bodies in British Columbia and the San Francisco Bay Area
  • Updated by Publisher: 9/3/2016
  • Level of Use: Level of adoption is low. Demos of the versions have been implemented but are incomplete. DriveBC provides Open511 API
  • Open License: Yes
  • Transferable to other Jurisdictions: Open North is working with Open511 to develop an open source software to ease implementation of the API
  • Stakeholder Participation: Stakeholders can communicate and collaborate with Open North
  • Consensus-based Governance: The standard provides a mailing list and 'issue tracker' on GitHub to contribute to the development of the API. It also mixes authoritative government data with crowdsourced verification
  • Extensions: Open511 uses a map based interface filter for the data.
  • Machine Readable: Retrieves the data in XML (supports JSON when indicated by API)
  • Human Readable: Easily readable for users
  • Requires Real-Time Data: Standard can be conducted over the web feed. Data is updated in the XML feed in real time
  • Metadata: Jurisdiction resource acts as a form of metadata and links to the description of the government entity that is publishing the data.
Added to directory: 7/12/2017