Citizen Connect
Schema and Examples

Welcome to Socrata's Citizen Connect (CC) experience. This page is designed to provide documentation that will help your team better understand the Citizen Connect application, and how you'll need to structure your data so that the application can read and display information in meaningful ways.
This page includes: 
  • Introducing Citizen Connect
  • Understanding the Schemas
  • Schema Documentation
  • Customer Examples 
  • Additional Resources

Introducing Citizen Connect

Citizen Connect  is an application that allows your citizens to map and explore incidents, tickets, locations, and many other location-centric aspects of your community.  Users can see a high-level, trend-focused view of incidents, while being able to zoom into individual incidents to see data impacting them and their neighbors.

The data displayed in Citizen Connect falls into two categories: Tickets and Places:

Tickets - Think of these as generally time-bound, line-item entries that will be added or change with some degree of regularity.  For example, 311 incidents or crime reports.  Because they are the most dynamic, "tickets" will likely be the primary focus of your application.

Places - These are relatively static entities within your community that residents can use to learn more about the area and its amenities, or as a geographic marker to provide additional context to some of your Pins/Tickets.  For example, providing a list of police stations alongside a crime reports dataset could help spotlight the relationship between crime levels and police infrastructure.  

There are three datasets used to power Citizen Connect - because each customer will display different types of data, none of the datasets are required, though including data from all three datasets is highly recommended:

Shapes Datasets -  Dataset(s) that defines the geographic boundaries within which your users can filter and explore data.  For example, you can define congressional districts, ZIP Codes, or neighborhood boundaries to help users explore what is relevant to them.

Note: Shapes datasets must be configured as Spatial Lenses  prior to being configured within Citizen Connect.

Tickets Datasets - Dataset(s) that define the incident-level data of your tickets.  Given the nature of the information that will be used in the app, these datasets should be updated as frequently as possible. 

Places Datasets - Dataset(s) that define static places within your application.  These datasets should be updated as regularly as needed given the places you will be tracking.  For example, a dataset containing police stations may not need to be updated more than quarterly, but a dataset showing farmer's market hours and produce availability may need to be updated weekly.

Understanding Schemas

Within the schema documentation for each dataset type, you'll find three field types:
  • Required Fields: These fields are required by Citizen Connect to function. Think of these fields as the data that you simply could not report about your projects without. For example, the location coordinates of a ticket, or the unique identifier for a ticket
  • Recommended Fields: These fields are not required, but including them will allow users to see a richer picture of your projects' information. For example, the status of a ticket, or the date/time of different stages of the ticket's lifetime
  • Optional Fields: These fields are useful for analysts or power-users accessing the information, or for adding a deeper level of hierarchy. For example, additional static text fields for a "Place", or a deeper level of hierarchy for your tickets

Schema Documentation

For the full documentation of the schemas for Citizen Connect  Explorer, which includes all three required datasets, click the link below:
Citizen Connect Schema

Customer Examples

Below are examples of actual customers' Citizen Connect implementations, from both the application-level as well as the data-level. Use the below examples to explore how the data is structured and how it is displayed in the final version of the application.

Metro Nashville, TN
Nashview Datasets

Datasets currently powering the Nashview App

Metro Nashville, TN 
Nashview Application

City of Buffalo, NY
My Neighborhood Datasets

My Neighborhood Buffalo Datasets

City of Buffalo, NY
My Neighborhood Application

City of Baton Rouge, LA
Open Neighborhood Datasets

Datasets powering Open Neighborhood BR App

City of Baton Rouge, LA
Open Neighborhood Application

Additional Resources

Our support team has put together a list of articles to assist with your implementation.
Find additional support articles here
Have questions? Feel free to reach out to your program manager, customer success manager, or our support team at