Burghs Eye View - Places

External Burgh's Eye View displaying City Places such as; Facilities, Parks, Steps, Bridges, Playgrounds and Pools.

Introduction

Authors:

Geoffrey Arnold
Maxwell Cercone

Collaborators:

Tara Matthews
Nicholas Hall
Robert Burrack
Dee Jones

Acknowledgements & Thanks

This application was made possible by a wide number of individuals within and throughout the City of Pittsburgh. First, Laura Meixell for her leadership in seeing this application through to public release and beyond. To Former Chief of Police Cameron McLay for his commitment to Open Data and ensuring the Police are one of our biggest contributors. To Former Chief Innovation Officer for the City of Pittsburgh Debra Lam for her executive sponsorship. To Director Finance Paul Leger for his trasnformative leadership and vision. To our primary funder, the Heinz Endowements for their ongoing support. To all of our friends and family for their compassion and understanding through our late nights and frenzied mornings. To Mayor William Peduto for making the City of Pittsburgh a place where innovative work like this is possible. Finally to the Citizens of Pittsburgh for their generous support of this application since release and their feedback through the 32 Community Meetings our team was able to attend.

Installation & Configuration

Burgh's Eye View is a Shiny application built on a single app file, and therefore only requires R Shiny Server and its dependencies to run. It is hosted through RStudio's shinyapps.io platform but can be run on a local device. The repository as currently configured is ready to deploy minus a few necessary variables supplied by the user.

www: Various images required for the application
icons: Icons used on the application
- egg: Icons used for the various season easter eggs on the application.
about.html: About Page tab html content
app.R: Main application
parks.csv: Centroid locations of City parks for easter egg icons.
key_example.json: Example file for users to input their own credentials for the WPRDC and a CouchDB of their choice.
MISSING: tag-manager-header/body.js and google-analytics.js

DOMI request: display traffic counts on map

Display traffic counter data on BEV map in conjunction with speed humps

submit traffic count data to WPRDC after sign-off from DOMI + Law that this can be made public
speed humps are already on BEV as an asset type
traffic counters are also in cartegraph as an asset type
within traffic counter recorders, there are child records with actual traffic count data

From Matt:

For traffic count data, we would need to make both the Traffic Counter Asset and Traffic Count Data child records open data. The Traffic Counter asset would give us the location of the count where as the associated child Traffic Count Data record would give us the traffic count information. DOMI only wants to display specific fields from the Traffic Count Data records. Ideally this would be added to BEV Places:

https://pittsburghpa.shinyapps.io/BurghsEyeViewPlaces

Geoffrey had this organized in a way that sometimes separates out the assets with their own section (like facilities) or combines them into one searchable section (like "Recreation" is a combination of Court, Playing Field, Park, Playground, etc Asset Types). I don't really have a preference we could either give traffic counts their own section or put them in the Traffic Section:

If possible, it would be good for it to work like other records in BEV so that a locaiton appears on the map and when you click on it a pop up text box displays the traffic count data similar to this where the crosswalk displays on the map and when you click on it you get some info about the crosswalk:

There could be some traffic counter assets with numerous traffic count records. I think we could just display the most recent.

cityofpittsburgh / burghs-eye-view-places Goto Github PK