Roadmap

Roadmap

Where are we now? (Shareabouts 2.0)

• Map interface to explore submitted locations and add your own
• Activity ticker showing recently added points, comments, and support
• Split architecture between the API and Client
• Flexible data storage to future-proof Client needs
• Simplification of Client add-a-point workflow (no more “Confirm Location” button)
• Flexible text and internationalization
• Geospatial database
• Admin interface
• Map and location configuration
• Export for GIS or spreadsheet analysis

Where are we going? (Shareabouts infinity and beyond!)

Ideas for Shareabouts core:

• Analytical tools (some possible examples)
  • What are the most recent places? Survey submissions?
  • What are the most supported places?
  • What is the average income of people in a place?
• Client Flavors (some possible examples)
  • Suggest, support, and comment on places
  • Complete a survey about predefined places
  • 311 ticket inputs
  • Election poll monitoring
  • Travel surveys (origin and destination)
  • Transit Options Map (comment on these three options for this route)
• Add locations & comments via SMS
• Social media integration (what are my friends doing on Shareabouts?)
• Integrate custom map layers in Client
• Support for non-point places
• Add geographic context to map submissions
  • Assign neighborhood names
  • Limit contributions to within boundaries
• Data exports, including GIS
• Data filtering in Client (own points, recent points)
• Configurable survey form for new points
• Store rich media on places (video, audio, images)
• Client Starter Templates (create new Clients in your favorite programming language)

Ideas for Shareabouts - Participatory Budgeting flavor:

Ideas for Shareabouts Recovery Mapping flavor

Sharebouts Recovery Mapping flavor will assist in gathering citizen reports after a major storm. Residents will be able to submit reports using desktop and mobile web interfaces. Administrators will have access to reports and other management views.

Existing features that are useful for Recovery Mapping:

• Desktop browser view of issues, mobile web-optimised view of the map.
• Functionality for users to add issues.
• Functionality for users to comment on existing issues.

Additional features:

• Map management tools to support activation a map and close it down when no longer needed.
• Content management tools to monitor, review, moderate and export submitted locations as needed.
• complex data filtering
• customized information displays for different users, including analysis staff and management
• custom ‘watch areas’ on maps
• velocity indicators to show trending issues as they are reported
• integration with Open311 - citizens can directly submit their issue as a 311 request simply by adding it to the map
• user-verification tools -- submitting reports does not need to be the end of citizen involvement in storm or recovery mapping. Process tools can engage citizens in verifying reports and providing additional details as needed. The rewards of participation can be accentuated, to encourage repeat involvement from reliable data checkers.

Glossary

• Client - a user facing web or mobile front end that relies on the Shareabouts API for data storage.
• API - an API for storing data about places
• API Admin - the web admin interface for managing the data in the user’s API account