Public Health or Profit? The Rochester Red Light Camera Controversy

Primary tabs

Secondary tabs

... (Array, 12 elements)
- body (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 1
 - #title (String, 4 characters ) Body
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 4 characters ) body
 - #field_type (String, 17 characters ) text_with_summary
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 17 characters ) drupalimc_article
 - #object (Object) stdClass
 
 vid (String, 6 characters ) 149602
 
 uid (String, 3 characters ) 164
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 log (String, 0 characters )
 
 status (String, 1 characters ) 1
 
 comment (String, 1 characters ) 2
 
 promote (String, 1 characters ) 1
 
 sticky (String, 1 characters ) 0
 
 nid (String, 6 characters ) 147495
 
 type (String, 17 characters ) drupalimc_article
 
 language (String, 3 characters ) und
 
 created (String, 10 characters ) 1466081479
 
 changed (String, 10 characters ) 1466170524
 
 tnid (String, 1 characters ) 0
 
 translate (String, 1 characters ) 0
 
 revision_timestamp (String, 10 characters ) 1466170524
 
 revision_uid (String, 3 characters ) 164
 
 body (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 5 elements)
 
 value (String, 33938 characters )  <style type="text/css"> P { margin-bottom...
 
 <style type="text/css"> P { margin-bottom: 0.08in; }</style> According to the National Highway Traffic Safety Administration’s (NHTSA) Traffic Safety Facts Report from the same year, 2.5 million reported intersection accidents occurred in the United States during 2012. In total, the reported crashes resulted in over 680,000 injuries [[{"type":"media","view_mode":"drupalimc_large","fid":"13280","attributes":{"alt":"","class":"media-image","style":"float: right;","typeof":"foaf:Image"}}]]and 2,850 fatalities. Accidents caused by red light running accounted for 100,000 of those accidents and 1,000 of the fatalities (SRF Associates, 2014, p. 1). With 35% of fatalities coming from a mere 4% of all reported accidents, red light running poses a clear threat to all motorists and pedestrians crossing the street at busy intersections. “Red light running” is defined as a vehicle that enters an intersection or crosses the stop line after the light has turned red. This could include not fully stopping before turning right, passing through a red light after it changes from yellow and going through a red light while other movements in the intersection (turn arrows, pedestrian crossings) are being served (SRF Associates, 2014, p. 1). Several studies have found that red light camera programs reduce the number and rate of red light violations. In the last decade, over 400 cities have utilized these programs to combat this public health concern. The theory is that putting Red Light Cameras at intersections with a noted history of red light violations and recording these violations for prosecution will alter motorist behavior; the threat of a ticket will prevent or reduce instances of red light running. In addition, the change in motorist behavior will ultimately reduce overall accidents and injuries thus promoting public safety (SRF Associates, 2014, p. 2). In April, 2009 New York State passed legislation clearing the way for Rochester to implement its Red Light Traffic Enforcement Program (Bortnick, 2009). Since the program went live in November 2010, 48 cameras have been installed at 32 intersections in the city of Rochester (SRF Associates, 2014, p. 1).Description of CommunityAccording to 2010 Census data, there are 1,054,000 million people in the Greater Rochester Area with 210,565 of them residing in the city. The Greater Rochester Area is the second largest economic center in New York State, trailing only New York City. Including Enter City which is primarily downtown, there are a total of 36 neighborhoods in the City of Rochester  (Rochester, NY Neighborhoods, 2016); for a list and color coded map of neighborhoods refer to the Appendix. The yellow block in the middle is Center City, containing what is considered “downtown.” Areas in green are considered high desirability, high safety and low crime neighborhoods. Areas in red are considered to be low desirability, low safety and high crime neighborhoods.The color coded map of Rochester reveals a few startling facts. First, the red neighborhoods on the map are all geographically connected to each other. They form “The Crescent;” an area of concentrated poverty representing the highest proportion of black, Latino and immigrant residents. As of 2015, Rochester had more people living at less than half the federal poverty level than any other American city of comparable size with 16.2% of those living in extreme poverty (Crescent of Poverty, 2015). Second, of the 36 separate neighborhoods listed in the Appendix, 14 of them are color coded red. Two neighborhoods the map codes in green (Susan B. Anthony and Brown Square) are mislabeled. On the map in the Appendix, there are two small areas west of Center City identified as high desirability, high safety and low crime. My experience working in these neighborhoods has shown them to be two of the most economically challenged and dangerous.[[{"type":"media","view_mode":"drupalimc_large","fid":"13284","attributes":{"alt":"","class":"media-image","typeof":"foaf:Image"}}]]The Brown Square area includes the “Fruit Belt;” a grouping of streets named after fruits known for poverty, crime and high immigrant populations (Governale, 2015). Located near Sahlen’s Stadium where the Rochester Rhinos play, this troubled neighborhood also contains Enrico Fermi School #17. New York State test scores consistently show School #17 to be one of the lowest performing schools in the state, firmly entrenched in the bottom 1% of all schools for the last decade (School #17- Enrico Fermi, 2016). The Susan B. Anthony Neighborhood has historically been considered part of the Crescent (Crescent of Poverty, 2015), so I added these neighborhoods to those coded in red. That brings the total number of high crime, low safety and low desirability neighborhoods to 16, or 44% of the 36 identified areas. The Red-Light Camera Traffic Safety Program is contained within the City of Rochester, meaning there are no cameras at any suburban intersections. Of the 36 neighborhoods considered part of the city proper, 16 contain red light cameras. It is important to point out that there are no traffic cameras on Main St. in Center City, and the lack of cameras in one of the highest traffic areas in the County compared to other chosen intersections is alarming. Excluding downtown, 11 of the 15 neighborhoods are considered high crime, low safety and low desirability. Literature Review In the early years of the program, opposition pointed to a lack of statistical evidence proving the program increased public safety or justifying its need in the community. Three years into operations the City hired an independent auditor, SRF Associates, to evaluate the effectiveness of cameras in reducing the frequency and severity of accidents caused by red light violations (SRF Associates, 2014, p. 1). The City hoped the findings of the study, released to the public in November 2014, would provide overwhelming evidence that the program positively impacted public safety and silence critics suggested the only benefits were to the City’s bottom line. While the aggregate numbers appear impressive and overall accidents at red light intersections were down 26%, a deeper dive into the numbers raised questions about just how effective the program is. Of the 32 intersections studied, 8 experienced increases in total collisions while 11 saw increases in rear end crashes and 6 had a higher frequency of right angle crashes. Overall, eleven of the 32 intersections saw increases in violations (SRF Associates, 2014, p. 23); with 35% of intersections seeing increased frequency of red light violations and 25% seeing increased collisions, some questioned if the cameras were affecting driver behavior as intended. One City Council member, Elaine Spaull, stated the cameras were intended to change driver behavior leading to few fines and few collection measures (Fien, 2015). While the cameras improved overall safety through accident reduction, the increase in violations and accidents at several intersections cast doubts on the overall efficacy and effect of the program while failing to silence opponents.Concerns and ControversyOne of the concerns surrounding the Red Light Camera program is where the cameras are placed. According the study on Red Light Camera Effectiveness in Rochester released in November 2014, 207 potential camera locations were reviewed. These 207 locations were identified through recommendations from the Rochester Police Department's (RPD) review of accident data by City staff and traffic volumes. A small camera was placed at each of these locations for a 12-hour period to measure signal compliance. An intersection was recommended for installation if 15 or more red light violations occurred in the 12-hour period, if it exhibited a history of accidents, and if the camera manufacturer determined the intersection was suitable. A team of City staff with representatives from the RPD, Information Technology, Engineering, Law and budget departments made the final decision on where the cameras would be installed (SRF Associates, 2014, pp. 2-3).Several community members, including City Council Members who originally supported the cameras, have expressed concerns over them recently. In June 2015, both Council President Loretta Scott and Council member Adam McFadden expressed concerns that the program focuses on impoverished neighborhoods which disproportionately punishes Rochesterians with less disposable income (Fien, 2015). Further analysis of aggregate of the data from the SRF report suggests these Council members may have a point.[[{"type":"media","view_mode":"drupalimc_large","fid":"13282","attributes":{"alt":"","class":"media-image","style":"float: left;","typeof":"foaf:Image"}}]]While plotting camera locations on the map in the Appendix, I noticed the same geographical pattern as Scott and McFadden. There are high concentrations of cameras in the high crime, low safety neighborhoods that form the Crescent. To see how high, I tallied the number of intersections and overall cameras located in each color coded section. Excluding Center City, 11 of the 15 neighborhoods with cameras are coded red on the map and considered high crime, high poverty areas. Of the 16 multi-camera intersections, 10 are located in those 11 high risk neighborhoods. In total, 53% of the intersections (17 of 32) and 56% of the cameras (27 of 48) are located in 31% (11 of 36) of Rochester Neighborhoods. If you remove Center City and only include neighborhoods with cameras, 61% of the intersections (17 of 28), 63% of cameras (27 of 43) and 67% of the multi-camera intersections (10 of 15) are located in high risk neighborhoods. While these numbers show a disturbing trend, removing one block intensifies the argument the cameras target the poorest neighborhoods. Five cameras and three intersections are located in the same block near Kodak Park where 104 forks into Ridge Rd and Ridgeway Avenue, an area coded green. Removing that 100 sq. ft. area, in conjunction with Center City, the ratios are even more startling. That puts 68% of intersections (17 of 25), 71% of all cameras (27 of 38) and 71% of multiple-camera intersections (10 of 14) in impoverished neighborhoods. Simply put, neighborhoods with cameras located in the Crescent comprise less than one third of the City, but represent 73% of all residential neighborhoods monitored through the Red Light Camera Traffic Safety Program.The concentration of red light cameras in the Crescent raises concerns about the privacy of citizens. License plate numbers and registration data as well as who owns the vehicle and where it’s located are aggregated into large databases creating more opportunities to collect this data thus stockpiling this information (Lederman, Taylor, & Garrett, 2016, p. 118). There are several instances over the last few years of data breaches in the public sector and private industry, and this information could be used by hackers to track the movements of people, identify frequently used routes and compile locations on where to find someone. Private information relating to specific individuals could become widely available to people with ill intentions (Lederman, Taylor, & Garrett, 2016, p. 115)While the current cameras only take photos of red light violations, as the technology associated with traffic enforcement cameras evolves these could turn into surveillance cameras used in broken windows policing. The theory of broken windows policing involves focusing on areas with unattended disorder to maintain public order (Smith & Greenblatt, 2016, pp. 460-461). By focusing on neighborhoods with high crime, high poverty and dilapidated structures with broken windows, controlling the main sources of crime. The neighborhoods with the highest concentration of red light cameras meet these criteria, and are already being watched 24/7. The RPD already has a Police Overt Digital Surveillance System (PODSS) comprised of fifty cameras placed in high crime areas to help police maintain order (PODSS, 2016). Adding the red camera intersections to the PODSS program may be as easy as switching out cameras or updating software, and adding additional surveillance to already struggling neighborhoods falls in line with the current RPD policies and approach to policing these communities.Lastly, concerns are prevalent over how the program is administered from start to finish; in particular, there are no witnesses to the offense and no due process. When a violation occurs, the camera snaps a photo of the vehicle license plate, making it difficult to identify the actual driver or passengers. The recorded footage of the violation is sent to Redflex Traffic Systems in Arizona, the company Rochester contracted for the cameras, where it is reviewed by company auditors. If these civilians determine a violation has occurred, the incident is sent back to Rochester and reviewed by members of the RPD. Notice of the violation is sent to the address attached to the vehicle registration along with a $50 fine (Twietmeyer, 2015).With no witnesses, officer discretion and the circumstances surrounding the violation are discarded in favor of photographic evidence that is often viewed as indisputable. There is no trial or opportunity to defend yourself- you’re sent a document telling you that you are guilty and that you must pay a fine. If the owner wasn’t driving the car when the violation occurred, they are still responsible. While I was unable to find statistics on what percentage of tickets are overturned, the City of Rochester rarely rescinds violations. There are also concerns violations aren’t reported in a timely fashion, and that registered owners don’t find out about the fine until it’s too late. Failure to pay the violation can have extreme consequences, and some enforcement measures used support claims the program is a money grab for the City of Rochester.Since the beginning of the program, unpaid violations were referred to the City’s Collection Agency EOS CCA (City of Rochester, 2016). Unpaid penalties damage credit reports, creating a scenario where the vehicle owner responsible for the violation is notified through their credit report and not the City assessing the fine. The judgments levied by the City stay on credit reports for years and can impact the ability to purchase cars or homes. Frustrated by accumulated unpaid fines, the City of Rochester implemented extreme policy measures to increase the collection of fines as revenue. In May 2015, the City started booting cars with unpaid red light camera violations (Riley, 2015). Many citizens and City Council members saw this as an overly aggressive measure to collect fines on a program advertised as a public safety measure, with McFadden and Scott pointing to the impact and perceived focus on the poorest neighborhoods in the city. Additionally, Mayor Warren has included further punitive measures in her Fiscal Year 2016 Budget. Despite the fact these tickets are a civil matter, Mayor Warren included a plan to report these violations to the Department of Motor Vehicles (Riley, 2015). Reporting these tickets to them could impact the ability to register a vehicle, renew a license and could lead to suspension or revocation of driving privileges. Should this happen to a vehicle owner who is held responsible for another motorist or one who isn’t properly notified, charges like driving without a license, driving on a suspended license and driving an unregistered vehicle become tangible turning a civil fine into a serious criminal matter.Despite the negative public perception of the program and the implications the cameras target low income residents, many argue the financial benefits of the Red Light Camera Traffic Enforcement Program, the City of Rochester will ensure the initiative continues. While estimates range on how much revenue red light fines the City makes, in 2014 the city assessed almost 87,000 citations generating $3.7 million dollars in revenue (Davidsen, 2015). It is not clear much of that money the City got to keep, and the Rochester CAFR doesn’t identify the red light cameras as a specific revenue source. It also doesn’t mention where the money went, or how the revenue generated from the cameras will be used to benefit the City. The fact that the revenue is hidden in other line items and not specifically discussed supports the claims this program is a cash cow for the City of Rochester.One thing that is clear is the cameras aren’t going anywhere in the near future. In November 2014, City Council voted to extend the program through December 1, 2019 by a 6-3 margin. The three council members who voted against continuing the program were Elaine Spaull, Adam Mc Fadden and Loretta Scott (Staff Report, 2014).ConclusionWhile the report from SRF Associates provides data showing some improvements to public health and traffic safety, the benefits do not outweigh the negative impact the Red Light Camera Traffic Safety Program has had on the City of Rochester. These cameras were advertised and implemented as a public safety measure, but when due process is removed and fines are levied with the assumption of guilt, it becomes harder to see them as anything other than a cash cow for a struggling City. Based on the location and quantity of cameras located in the Crescent, there are strong implications this program is in fact targeting the neediest families in our community and some of the poorest neighborhoods in all New York State. The measures the City chooses to ensure payment of these fines are excessive, and inflict damage beyond a $50 fine if not paid promptly. The decision to boot vehicles, send fines to collection and report them to the DMV show how desperate the City of Rochester is to maintain this revenue source, especially when 3 City Council members who initially supported the initiative have raised serious concerns about the equity of the program in an already racially divided community. At the least, the City of Rochester owes its citizens transparency over how much revenue is generated from the program. Hiding the proceeds in vague fund balances does nothing to support claims that the goal of the cameras is to improve traffic safety.If the focus is on profits instead of public safety, then the privacy and security of sensitive information is most likely an afterthought. Part of public health is peace of mind; the ability for the public to feel safe and protected in the community knowing the police and government are protecting your rights. As long as these cameras are part of the City, the lack of trust felt by the residents of the Crescent and vehicle owners who were mistreated or ignored during the violation process will override any feelings of security. The City already uses PODSS as a tool, harming the relationship between the community and the RPD. Until studies show overwhelming reductions in accidents and violations strengthening the public safety stance or due process is added allowing for the application of circumstantial discretion, the harm the cameras cause will continue to outweigh any safety benefits. Angry citizens will continue to feel like the program is nothing more than a cash cow, creating further resentment for a City government more concerned with collecting fines than addressing the blatant racial, procedural and civil right concerns the Red Light Traffic Safety Program leaves in its wake.References Bortnick, C. J. (2009, April 2). Rochester to Get Traffic Cameras. Retrieved from The 9/12 Project: article referenced taken from RNews: http://www.meetup.com/WSR912/messages/boards/thread/6617713City of Rochester. (2016, April 27 2016). Red Light Camera Program- Frequently Asked Questions. Retrieved from Red Light Camera Traffic Safety Program: http://www.cityofrochester.gov/article.aspx?id=8589940922Crescent of Poverty. (2015). Retrieved from RocWiki: The People's Guide to Rochester: http://rocwiki.org/Crescent_of_PovertyDavidsen, B. (2015, November 2). NYS Exposed: The future of red light cameras in Rochester. Retrieved from WHEC Rochester- News 10: http://www.whec.com/article/stories/s3950224.shtmlGovernale, M. (2015, August 26). Help Nurture Rochester's Fruit Belt. Retrieved from RochesterSubway.com: http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fruit-belt/Lederman, J., Taylor, B. D., & Garrett, M. (2016). A private matter: the implication of privacy regulations for itelligent transportaton systems. Transportation Planning and Technology, 39:2, 115-135.Rochester, NY Neighboorhoods. (2016, April 27). Retrieved from Google Maps: https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UTF8&jsv=290a&authuser=1&mid=1iJHDrruEBEwP1yeJKYi-vCNfobsSmith, K. B., & Greenblatt, A. (2016). Governing States and Localities. Los Angeles: CQ Press, an Imprint of Sage Publications, Inc.SRF Associates. (2014). Red Light Camera Effectiveness Evaluation. Rochester: City of Rochester, Monroe County, New York.Voorhees, S. (2015, June 24). Rochester City Councilman Calls for Investigation Into Red Light Camera Program. Retrieved from Time Warner Cable News: http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-rochester-adam-mcfadden.html <style type="text/css"> P { margin-bottom: 0.08in; }</style> Appendix:Camera Placement in Neighborhoods Color Coded by Safety & Desirability[[{"type":"media","view_mode":"drupalimc_large","fid":"13286","attributes":{"alt":"","class":"media-image","typeof":"foaf:Image"}}]] <style type="text/css"> P { margin-bottom: 0.08in; }</style> Contact the author: Robert D. Richardson III, Department of Public Administration, SUNY Brockport. Correspondence concerning this article should be addressed to Robert D. Richardson III, Brockport MetroCenter. 55 St. Paul St., Rochester, NY 14604. Contact: rrich4@u.brockport.eduRead the original paper[[{"type":"media","view_mode":"drupalimc_large","fid":"13285","attributes":{"alt":"","class":"media-image","height":"270","typeof":"foaf:Image","width":"270"}}]][Rochester Indymedia note on profit motive and RedFlex corruption: According to page 49, Exhibit D Compensation & Pricing, of the <a href="http://rochester.indymedia.org/node/15438">contract between the city of Rochester and RedFlex</a>, “The fixed fee shall be $3,740 Per Month per System.” From what Rochester Indymedia can gather from the contract, a “System” simply means a camera at an intersection. Mr. Richardson's paper notes that “48 cameras have been installed at 32 intersections” which means that RedFlex, a private, for-profit company, is raking in $179,520 per month. Over a 12 month period, that's $2,154,240 per year. That's private profit: public money is being used to subsidize a private entity—a corporation—that offers the service of using its technology to penalize drivers in Rochester. The city certainly gets some of the money from the ticket as well. As it is the case that most of the cameras are located in impoverished neighborhoods—71%—as Mr. Richardson notes, then it's reasonable to assume that most of that $2.1 million in private profit is being taken directly from the pockets of the people living in those neighborhoods and shuttled to a privte company in Arizona. That's a bad deal. That's hardworking folks' money being fleeced from them for the benefit of a private corporation—over minor traffic violations. Another thing to consider with RedFlex is the massive bribery scandal officials engaged in to get the system installed in Chicago. See: <a href="http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html" rel="nofollow" target="_blank">http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html</a>. Why does the city continue to do business with a company that is being investigated for crimes where its former CEO has plead guilty to a massive, $2 million bribery scheme? The city found there were no ethics violations, but when $4 million is raked in from the program, one could see why there would be hesitation at finding anything wrong with the program from an economic point of view.]Related: <a href="http://rochester.indymedia.org/node/15438">FOIA Docs: Red-light Camera Contract between City of Rochester and Redflex</a> | <a href="http://rochester.indymedia.org/node/100298">Strike it down! Larry Krieger fights City Hall on red light cameras</a> |<a href="http://rochester.indymedia.org/node/100297"> Larry Krieger's 1st transcribed hearing re: red light camera ticket</a> | <a href="http://rochester.indymedia.org/node/104241">Rochester's Red Light Camera Law Is Bad For Business and Tourism</a> | <a href="http://rochester.indymedia.org/node/7267">Mapping the Police State: Police Cameras, Maps, and You! </a>
 
 summary (String, 0 characters )
 
 format (String, 9 characters ) full_html
 
 safe_value (String, 37076 characters ) <style type="text/css"> <![CDATA[/*...
 
 <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> According to the National Highway Traffic Safety Administration’s (NHTSA) Traffic Safety Facts Report from the same year, 2.5 million reported intersection accidents occurred in the United States during 2012. In total, the reported crashes resulted in over 680,000 injuries <div class="media media-element-container media-drupalimc_large media-float-right"><div id="file-13280" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13280">redlight-program-graphic.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/redlight-program-graphic.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: right;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/redlight-program-graphic.jpg?itok=QyN5uHYb" alt="" title="" /></a> </div> </div> </div>and 2,850 fatalities. Accidents caused by red light running accounted for 100,000 of those accidents and 1,000 of the fatalities (SRF Associates, 2014, p. 1). With 35% of fatalities coming from a mere 4% of all reported accidents, red light running poses a clear threat to all motorists and pedestrians crossing the street at busy intersections. “Red light running” is defined as a vehicle that enters an intersection or crosses the stop line after the light has turned red. This could include not fully stopping before turning right, passing through a red light after it changes from yellow and going through a red light while other movements in the intersection (turn arrows, pedestrian crossings) are being served (SRF Associates, 2014, p. 1). Several studies have found that red light camera programs reduce the number and rate of red light violations. In the last decade, over 400 cities have utilized these programs to combat this public health concern. The theory is that putting Red Light Cameras at intersections with a noted history of red light violations and recording these violations for prosecution will alter motorist behavior; the threat of a ticket will prevent or reduce instances of red light running. In addition, the change in motorist behavior will ultimately reduce overall accidents and injuries thus promoting public safety (SRF Associates, 2014, p. 2). In April, 2009 New York State passed legislation clearing the way for Rochester to implement its Red Light Traffic Enforcement Program (Bortnick, 2009). Since the program went live in November 2010, 48 cameras have been installed at 32 intersections in the city of Rochester (SRF Associates, 2014, p. 1). Description of Community According to 2010 Census data, there are 1,054,000 million people in the Greater Rochester Area with 210,565 of them residing in the city. The Greater Rochester Area is the second largest economic center in New York State, trailing only New York City. Including Enter City which is primarily downtown, there are a total of 36 neighborhoods in the City of Rochester (Rochester, NY Neighborhoods, 2016); for a list and color coded map of neighborhoods refer to the Appendix. The yellow block in the middle is Center City, containing what is considered “downtown.” Areas in green are considered high desirability, high safety and low crime neighborhoods. Areas in red are considered to be low desirability, low safety and high crime neighborhoods. The color coded map of Rochester reveals a few startling facts. First, the red neighborhoods on the map are all geographically connected to each other. They form “The Crescent;” an area of concentrated poverty representing the highest proportion of black, Latino and immigrant residents. As of 2015, Rochester had more people living at less than half the federal poverty level than any other American city of comparable size with 16.2% of those living in extreme poverty (Crescent of Poverty, 2015). Second, of the 36 separate neighborhoods listed in the Appendix, 14 of them are color coded red. Two neighborhoods the map codes in green (Susan B. Anthony and Brown Square) are mislabeled. On the map in the Appendix, there are two small areas west of Center City identified as high desirability, high safety and low crime. My experience working in these neighborhoods has shown them to be two of the most economically challenged and dangerous. <div class="media media-element-container media-drupalimc_large"><div id="file-13284" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13284">city.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/city.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/city.png?itok=GvM9fHSW" alt="" title="" /></a> </div> </div> </div> The Brown Square area includes the “Fruit Belt;” a grouping of streets named after fruits known for poverty, crime and high immigrant populations (Governale, 2015). Located near Sahlen’s Stadium where the Rochester Rhinos play, this troubled neighborhood also contains Enrico Fermi School #17. New York State test scores consistently show School #17 to be one of the lowest performing schools in the state, firmly entrenched in the bottom 1% of all schools for the last decade (School #17- Enrico Fermi, 2016). The Susan B. Anthony Neighborhood has historically been considered part of the Crescent (Crescent of Poverty, 2015), so I added these neighborhoods to those coded in red. That brings the total number of high crime, low safety and low desirability neighborhoods to 16, or 44% of the 36 identified areas. The Red-Light Camera Traffic Safety Program is contained within the City of Rochester, meaning there are no cameras at any suburban intersections. Of the 36 neighborhoods considered part of the city proper, 16 contain red light cameras. It is important to point out that there are no traffic cameras on Main St. in Center City, and the lack of cameras in one of the highest traffic areas in the County compared to other chosen intersections is alarming. Excluding downtown, 11 of the 15 neighborhoods are considered high crime, low safety and low desirability.  Literature Review In the early years of the program, opposition pointed to a lack of statistical evidence proving the program increased public safety or justifying its need in the community. Three years into operations the City hired an independent auditor, SRF Associates, to evaluate the effectiveness of cameras in reducing the frequency and severity of accidents caused by red light violations (SRF Associates, 2014, p. 1). The City hoped the findings of the study, released to the public in November 2014, would provide overwhelming evidence that the program positively impacted public safety and silence critics suggested the only benefits were to the City’s bottom line. While the aggregate numbers appear impressive and overall accidents at red light intersections were down 26%, a deeper dive into the numbers raised questions about just how effective the program is. Of the 32 intersections studied, 8 experienced increases in total collisions while 11 saw increases in rear end crashes and 6 had a higher frequency of right angle crashes. Overall, eleven of the 32 intersections saw increases in violations (SRF Associates, 2014, p. 23); with 35% of intersections seeing increased frequency of red light violations and 25% seeing increased collisions, some questioned if the cameras were affecting driver behavior as intended. One City Council member, Elaine Spaull, stated the cameras were intended to change driver behavior leading to few fines and few collection measures (Fien, 2015). While the cameras improved overall safety through accident reduction, the increase in violations and accidents at several intersections cast doubts on the overall efficacy and effect of the program while failing to silence opponents. Concerns and Controversy One of the concerns surrounding the Red Light Camera program is where the cameras are placed. According the study on Red Light Camera Effectiveness in Rochester released in November 2014, 207 potential camera locations were reviewed. These 207 locations were identified through recommendations from the Rochester Police Department's (RPD) review of accident data by City staff and traffic volumes. A small camera was placed at each of these locations for a 12-hour period to measure signal compliance. An intersection was recommended for installation if 15 or more red light violations occurred in the 12-hour period, if it exhibited a history of accidents, and if the camera manufacturer determined the intersection was suitable. A team of City staff with representatives from the RPD, Information Technology, Engineering, Law and budget departments made the final decision on where the cameras would be installed (SRF Associates, 2014, pp. 2-3). Several community members, including City Council Members who originally supported the cameras, have expressed concerns over them recently. In June 2015, both Council President Loretta Scott and Council member Adam McFadden expressed concerns that the program focuses on impoverished neighborhoods which disproportionately punishes Rochesterians with less disposable income (Fien, 2015). Further analysis of aggregate of the data from the SRF report suggests these Council members may have a point. <div class="media media-element-container media-drupalimc_large media-float-left"><div id="file-13282" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13282">stop-light.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/stop-light.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: left;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/stop-light.jpg?itok=fDU3I99W" alt="" title="" /></a> </div> </div> </div>While plotting camera locations on the map in the Appendix, I noticed the same geographical pattern as Scott and McFadden. There are high concentrations of cameras in the high crime, low safety neighborhoods that form the Crescent. To see how high, I tallied the number of intersections and overall cameras located in each color coded section. Excluding Center City, 11 of the 15 neighborhoods with cameras are coded red on the map and considered high crime, high poverty areas. Of the 16 multi-camera intersections, 10 are located in those 11 high risk neighborhoods. In total, 53% of the intersections (17 of 32) and 56% of the cameras (27 of 48) are located in 31% (11 of 36) of Rochester Neighborhoods. If you remove Center City and only include neighborhoods with cameras, 61% of the intersections (17 of 28), 63% of cameras (27 of 43) and 67% of the multi-camera intersections (10 of 15) are located in high risk neighborhoods. While these numbers show a disturbing trend, removing one block intensifies the argument the cameras target the poorest neighborhoods. Five cameras and three intersections are located in the same block near Kodak Park where 104 forks into Ridge Rd and Ridgeway Avenue, an area coded green. Removing that 100 sq. ft. area, in conjunction with Center City, the ratios are even more startling. That puts 68% of intersections (17 of 25), 71% of all cameras (27 of 38) and 71% of multiple-camera intersections (10 of 14) in impoverished neighborhoods. Simply put, neighborhoods with cameras located in the Crescent comprise less than one third of the City, but represent 73% of all residential neighborhoods monitored through the Red Light Camera Traffic Safety Program. The concentration of red light cameras in the Crescent raises concerns about the privacy of citizens. License plate numbers and registration data as well as who owns the vehicle and where it’s located are aggregated into large databases creating more opportunities to collect this data thus stockpiling this information (Lederman, Taylor, & Garrett, 2016, p. 118). There are several instances over the last few years of data breaches in the public sector and private industry, and this information could be used by hackers to track the movements of people, identify frequently used routes and compile locations on where to find someone. Private information relating to specific individuals could become widely available to people with ill intentions (Lederman, Taylor, & Garrett, 2016, p. 115) While the current cameras only take photos of red light violations, as the technology associated with traffic enforcement cameras evolves these could turn into surveillance cameras used in broken windows policing. The theory of broken windows policing involves focusing on areas with unattended disorder to maintain public order (Smith & Greenblatt, 2016, pp. 460-461). By focusing on neighborhoods with high crime, high poverty and dilapidated structures with broken windows, controlling the main sources of crime. The neighborhoods with the highest concentration of red light cameras meet these criteria, and are already being watched 24/7. The RPD already has a Police Overt Digital Surveillance System (PODSS) comprised of fifty cameras placed in high crime areas to help police maintain order (PODSS, 2016). Adding the red camera intersections to the PODSS program may be as easy as switching out cameras or updating software, and adding additional surveillance to already struggling neighborhoods falls in line with the current RPD policies and approach to policing these communities. Lastly, concerns are prevalent over how the program is administered from start to finish; in particular, there are no witnesses to the offense and no due process. When a violation occurs, the camera snaps a photo of the vehicle license plate, making it difficult to identify the actual driver or passengers. The recorded footage of the violation is sent to Redflex Traffic Systems in Arizona, the company Rochester contracted for the cameras, where it is reviewed by company auditors. If these civilians determine a violation has occurred, the incident is sent back to Rochester and reviewed by members of the RPD. Notice of the violation is sent to the address attached to the vehicle registration along with a $50 fine (Twietmeyer, 2015). With no witnesses, officer discretion and the circumstances surrounding the violation are discarded in favor of photographic evidence that is often viewed as indisputable. There is no trial or opportunity to defend yourself- you’re sent a document telling you that you are guilty and that you must pay a fine. If the owner wasn’t driving the car when the violation occurred, they are still responsible. While I was unable to find statistics on what percentage of tickets are overturned, the City of Rochester rarely rescinds violations. There are also concerns violations aren’t reported in a timely fashion, and that registered owners don’t find out about the fine until it’s too late. Failure to pay the violation can have extreme consequences, and some enforcement measures used support claims the program is a money grab for the City of Rochester. Since the beginning of the program, unpaid violations were referred to the City’s Collection Agency EOS CCA (City of Rochester, 2016). Unpaid penalties damage credit reports, creating a scenario where the vehicle owner responsible for the violation is notified through their credit report and not the City assessing the fine. The judgments levied by the City stay on credit reports for years and can impact the ability to purchase cars or homes. Frustrated by accumulated unpaid fines, the City of Rochester implemented extreme policy measures to increase the collection of fines as revenue. In May 2015, the City started booting cars with unpaid red light camera violations (Riley, 2015). Many citizens and City Council members saw this as an overly aggressive measure to collect fines on a program advertised as a public safety measure, with McFadden and Scott pointing to the impact and perceived focus on the poorest neighborhoods in the city. Additionally, Mayor Warren has included further punitive measures in her Fiscal Year 2016 Budget. Despite the fact these tickets are a civil matter, Mayor Warren included a plan to report these violations to the Department of Motor Vehicles (Riley, 2015). Reporting these tickets to them could impact the ability to register a vehicle, renew a license and could lead to suspension or revocation of driving privileges. Should this happen to a vehicle owner who is held responsible for another motorist or one who isn’t properly notified, charges like driving without a license, driving on a suspended license and driving an unregistered vehicle become tangible turning a civil fine into a serious criminal matter. Despite the negative public perception of the program and the implications the cameras target low income residents, many argue the financial benefits of the Red Light Camera Traffic Enforcement Program, the City of Rochester will ensure the initiative continues. While estimates range on how much revenue red light fines the City makes, in 2014 the city assessed almost 87,000 citations generating $3.7 million dollars in revenue (Davidsen, 2015). It is not clear much of that money the City got to keep, and the Rochester CAFR doesn’t identify the red light cameras as a specific revenue source. It also doesn’t mention where the money went, or how the revenue generated from the cameras will be used to benefit the City. The fact that the revenue is hidden in other line items and not specifically discussed supports the claims this program is a cash cow for the City of Rochester. One thing that is clear is the cameras aren’t going anywhere in the near future. In November 2014, City Council voted to extend the program through December 1, 2019 by a 6-3 margin. The three council members who voted against continuing the program were Elaine Spaull, Adam Mc Fadden and Loretta Scott (Staff Report, 2014). Conclusion While the report from SRF Associates provides data showing some improvements to public health and traffic safety, the benefits do not outweigh the negative impact the Red Light Camera Traffic Safety Program has had on the City of Rochester. These cameras were advertised and implemented as a public safety measure, but when due process is removed and fines are levied with the assumption of guilt, it becomes harder to see them as anything other than a cash cow for a struggling City. Based on the location and quantity of cameras located in the Crescent, there are strong implications this program is in fact targeting the neediest families in our community and some of the poorest neighborhoods in all New York State. The measures the City chooses to ensure payment of these fines are excessive, and inflict damage beyond a $50 fine if not paid promptly. The decision to boot vehicles, send fines to collection and report them to the DMV show how desperate the City of Rochester is to maintain this revenue source, especially when 3 City Council members who initially supported the initiative have raised serious concerns about the equity of the program in an already racially divided community. At the least, the City of Rochester owes its citizens transparency over how much revenue is generated from the program. Hiding the proceeds in vague fund balances does nothing to support claims that the goal of the cameras is to improve traffic safety. If the focus is on profits instead of public safety, then the privacy and security of sensitive information is most likely an afterthought. Part of public health is peace of mind; the ability for the public to feel safe and protected in the community knowing the police and government are protecting your rights. As long as these cameras are part of the City, the lack of trust felt by the residents of the Crescent and vehicle owners who were mistreated or ignored during the violation process will override any feelings of security. The City already uses PODSS as a tool, harming the relationship between the community and the RPD. Until studies show overwhelming reductions in accidents and violations strengthening the public safety stance or due process is added allowing for the application of circumstantial discretion, the harm the cameras cause will continue to outweigh any safety benefits. Angry citizens will continue to feel like the program is nothing more than a cash cow, creating further resentment for a City government more concerned with collecting fines than addressing the blatant racial, procedural and civil right concerns the Red Light Traffic Safety Program leaves in its wake. References Bortnick, C. J. (2009, April 2). Rochester to Get Traffic Cameras. Retrieved from The 9/12 Project: article referenced taken from RNews: <a href="http://www.meetup.com/WSR912/messages/boards/thread/6617713">http://www.meetup.com/WSR912/messages/boards/thread/6617713</a> City of Rochester. (2016, April 27 2016). Red Light Camera Program- Frequently Asked Questions. Retrieved from Red Light Camera Traffic Safety Program: <a href="http://www.cityofrochester.gov/article.aspx?id=8589940922">http://www.cityofrochester.gov/article.aspx?id=8589940922</a> Crescent of Poverty. (2015). Retrieved from RocWiki: The People's Guide to Rochester: <a href="http://rocwiki.org/Crescent_of_Poverty">http://rocwiki.org/Crescent_of_Poverty</a> Davidsen, B. (2015, November 2). NYS Exposed: The future of red light cameras in Rochester. Retrieved from WHEC Rochester- News 10: <a href="http://www.whec.com/article/stories/s3950224.shtml">http://www.whec.com/article/stories/s3950224.shtml</a> Governale, M. (2015, August 26). Help Nurture Rochester's Fruit Belt. Retrieved from RochesterSubway.com: <a href="http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fruit-belt/">http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fr...</a> Lederman, J., Taylor, B. D., & Garrett, M. (2016). A private matter: the implication of privacy regulations for itelligent transportaton systems. Transportation Planning and Technology, 39:2, 115-135. Rochester, NY Neighboorhoods. (2016, April 27). Retrieved from Google Maps: <a href="https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UTF8&jsv=290a&authuser=1&mid=1iJHDrruEBEwP1yeJKYi-vCNfobs">https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UT...</a> Smith, K. B., & Greenblatt, A. (2016). Governing States and Localities. Los Angeles: CQ Press, an Imprint of Sage Publications, Inc. SRF Associates. (2014). Red Light Camera Effectiveness Evaluation. Rochester: City of Rochester, Monroe County, New York. Voorhees, S. (2015, June 24). Rochester City Councilman Calls for Investigation Into Red Light Camera Program. Retrieved from Time Warner Cable News: <a href="http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-rochester-adam-mcfadden.html">http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-r...</a> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Appendix: Camera Placement in Neighborhoods Color Coded by Safety & Desirability <div class="media media-element-container media-drupalimc_large"><div id="file-13286" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13286">cameras-for-ted.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/cameras-for-ted.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/cameras-for-ted.png?itok=NR_YO7YE" alt="" title="" /></a> </div> </div> </div> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Contact the author: Robert D. Richardson III, Department of Public Administration, SUNY Brockport. Correspondence concerning this article should be addressed to Robert D. Richardson III, Brockport MetroCenter. 55 St. Paul St., Rochester, NY 14604. Contact: <a href="mailto:rrich4@u.brockport.edu">rrich4@u.brockport.edu</a> Read the original paper <div class="media media-element-container media-drupalimc_large"><div id="file-13285" class="file file-default file-application-pdf"> <h2 class="element-invisible"><a href="/file/13285">PAD683-Local-Issues-Paper-Final(1).pdf</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/PAD683-Local-Issues-Paper-Final%281%29.pdf" alt="" class="media-image" height="270" width="270"><img width="270" height="270" typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/media_thumbnail/public/media-icons/default/application-octet-stream.png?itok=FJGVP5SF" alt="" /> PAD683-Local-Issues-Paper-Final(1).pdf</a> </div> </div> </div> [Rochester Indymedia note on profit motive and RedFlex corruption: According to page 49, Exhibit D Compensation & Pricing, of the <a href="http://rochester.indymedia.org/node/15438">contract between the city of Rochester and RedFlex</a>, “The fixed fee shall be $3,740 Per Month per System.” From what Rochester Indymedia can gather from the contract, a “System” simply means a camera at an intersection. Mr. Richardson's paper notes that “48 cameras have been installed at 32 intersections” which means that RedFlex, a private, for-profit company, is raking in $179,520 per month. Over a 12 month period, that's $2,154,240 per year. That's private profit: public money is being used to subsidize a private entity—a corporation—that offers the service of using its technology to penalize drivers in Rochester. The city certainly gets some of the money from the ticket as well. As it is the case that most of the cameras are located in impoverished neighborhoods—71%—as Mr. Richardson notes, then it's reasonable to assume that most of that $2.1 million in private profit is being taken directly from the pockets of the people living in those neighborhoods and shuttled to a privte company in Arizona. That's a bad deal. That's hardworking folks' money being fleeced from them for the benefit of a private corporation—over minor traffic violations. Another thing to consider with RedFlex is the massive bribery scandal officials engaged in to get the system installed in Chicago. See: <a href="http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html" rel="nofollow" target="_blank">http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html</a>. Why does the city continue to do business with a company that is being investigated for crimes where its former CEO has plead guilty to a massive, $2 million bribery scheme? The city found there were no ethics violations, but when $4 million is raked in from the program, one could see why there would be hesitation at finding anything wrong with the program from an economic point of view.] Related: <a href="http://rochester.indymedia.org/node/15438">FOIA Docs: Red-light Camera Contract between City of Rochester and Redflex</a> | <a href="http://rochester.indymedia.org/node/100298">Strike it down! Larry Krieger fights City Hall on red light cameras</a> |<a href="http://rochester.indymedia.org/node/100297"> Larry Krieger's 1st transcribed hearing re: red light camera ticket</a> | <a href="http://rochester.indymedia.org/node/104241">Rochester's Red Light Camera Law Is Bad For Business and Tourism</a> | <a href="http://rochester.indymedia.org/node/7267">Mapping the Police State: Police Cameras, Maps, and You! </a>
 
 safe_summary (String, 0 characters )
 
 field_drupalimc_categories (Array, 1 element)
 
 und (Array, 10 elements)
 
 0 (Array, 2 elements)
 
 tid (String, 2 characters ) 16
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 16
 
 vid (String, 1 characters ) 1
 
 name (String, 16 characters ) Police and Jails
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 1 characters ) 1
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 1 (Array, 2 elements)
 
 tid (String, 1 characters ) 4
 
 taxonomy_term (Object) stdClass
 
 tid (String, 1 characters ) 4
 
 vid (String, 1 characters ) 1
 
 name (String, 7 characters ) Poverty
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 1 characters ) 2
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 2 (Array, 2 elements)
 
 tid (String, 2 characters ) 19
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 19
 
 vid (String, 1 characters ) 1
 
 name (String, 20 characters ) Protest / Resistance
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 1 characters ) 3
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 3 (Array, 2 elements)
 
 tid (String, 2 characters ) 10
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 10
 
 vid (String, 1 characters ) 1
 
 name (String, 13 characters ) Miscellaneous
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 1 characters ) 4
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 4 (Array, 2 elements)
 
 tid (String, 2 characters ) 32
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 32
 
 vid (String, 1 characters ) 1
 
 name (String, 22 characters ) Surveillance / Privacy
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 11
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 5 (Array, 2 elements)
 
 tid (String, 2 characters ) 37
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 37
 
 vid (String, 1 characters ) 1
 
 name (String, 22 characters ) Theory and Information
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 13
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 6 (Array, 2 elements)
 
 tid (String, 2 characters ) 35
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 35
 
 vid (String, 1 characters ) 1
 
 name (String, 18 characters ) Cultural Criticism
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 20
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 7 (Array, 2 elements)
 
 tid (String, 2 characters ) 28
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 28
 
 vid (String, 1 characters ) 1
 
 name (String, 20 characters ) Anti-racism / Racism
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 27
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 8 (Array, 2 elements)
 
 tid (String, 2 characters ) 25
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 25
 
 vid (String, 1 characters ) 1
 
 name (String, 11 characters ) Environment
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 35
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 9 (Array, 2 elements)
 
 tid (String, 2 characters ) 26
 
 taxonomy_term (Object) stdClass
 
 tid (String, 2 characters ) 26
 
 vid (String, 1 characters ) 1
 
 name (String, 7 characters ) Economy
 
 description (NULL)
 
 format (NULL)
 
 weight (String, 2 characters ) 36
 
 vocabulary_machine_name (String, 20 characters ) drupalimc_categories
 
 rdf_mapping (Array, 5 elements)
 
 rdftype (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 name (Array, 1 element)
 
 predicates (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 description (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) skos:definition
 
 vid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 13 characters ) skos:inScheme
 
 type (String, 3 characters ) rel
 
 parent (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 12 characters ) skos:broader
 
 type (String, 3 characters ) rel
 
 field_drupalimc_local_interest (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 1 element)
 
 value (String, 1 characters ) 1
 
 field_drupalimc_migrated_images (Array, 0 elements)
 
 field_drupalimc_gallery (Array, 0 elements)
 
 field_drupalimc_author (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 25 characters ) Robert D. Richardson III
 
 format (NULL)
 
 safe_value (String, 25 characters ) Robert D. Richardson III
 
 rdf_mapping (Array, 9 elements)
 
 rdftype (Array, 2 elements)
 
 0 (String, 9 characters ) sioc:Item
 
 1 (String, 13 characters ) foaf:Document
 
 title (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 8 characters ) dc:title
 
 created (Array, 3 elements)
 
 predicates (Array, 2 elements)
 
 0 (String, 7 characters ) dc:date
 
 1 (String, 10 characters ) dc:created
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 changed (Array, 3 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 11 characters ) dc:modified
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 body (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) content:encoded
 
 uid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 16 characters ) sioc:has_creator
 
 type (String, 3 characters ) rel
 
 name (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 9 characters ) foaf:name
 
 comment_count (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 16 characters ) sioc:num_replies
 
 datatype (String, 11 characters ) xsd:integer
 
 last_activity (Array, 3 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 23 characters ) sioc:last_activity_date
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 signature (String, 0 characters )
 
 spaminess (Float) 0
 
 cid (String, 1 characters ) 0
 
 last_comment_timestamp (String, 10 characters ) 1466081479
 
 last_comment_name (NULL)
 
 last_comment_uid (String, 3 characters ) 164
 
 comment_count (String, 1 characters ) 0
 
 name (String, 10 characters ) Knight0440
 
 picture (String, 1 characters ) 0
 
 data (String, 4 characters ) b:0;
 
 entity_view_prepared (Boolean) TRUE
 
 service_links (Array, 9 elements)
 
 service-links-facebook (Array, 5 elements)
 
 title (String, 136 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/facebook.png" alt="Facebook logo" />
 
 href (String, 35 characters ) https://www.facebook.com/sharer.php
 
 query (Array, 2 elements)
 
 u (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 t (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 17 characters ) Share on Facebook
 
 class (Array, 1 element)
 
 0 (String, 22 characters ) service-links-facebook
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-google (Array, 5 elements)
 
 title (String, 132 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/google.png" alt="Google logo" />
 
 href (String, 37 characters ) https://www.google.com/bookmarks/mark
 
 query (Array, 3 elements)
 
 op (String, 3 characters ) add
 
 bkmk (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 28 characters ) Bookmark this post on Google
 
 class (Array, 1 element)
 
 0 (String, 20 characters ) service-links-google
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-identica (Array, 5 elements)
 
 title (String, 137 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/identica.png" alt="identi.ca logo" />
 
 href (String, 18 characters ) https://identi.ca/
 
 query (Array, 2 elements)
 
 action (String, 9 characters ) newnotice
 
 status_textarea (String, 110 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy http://rochester.indymedia.org/node/147495
 
 attributes (Array, 3 elements)
 
 title (String, 22 characters ) Dent this on identi.ca
 
 class (Array, 1 element)
 
 0 (String, 22 characters ) service-links-identica
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-twitter (Array, 5 elements)
 
 title (String, 134 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/twitter.png" alt="Twitter logo" />
 
 href (String, 25 characters ) https://twitter.com/share
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 text (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 21 characters ) Share this on Twitter
 
 class (Array, 1 element)
 
 0 (String, 21 characters ) service-links-twitter
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-digg (Array, 5 elements)
 
 title (String, 128 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/digg.png" alt="Digg logo" />
 
 href (String, 22 characters ) http://digg.com/submit
 
 query (Array, 3 elements)
 
 phase (String, 1 characters ) 2
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 26 characters ) Digg this post on digg.com
 
 class (Array, 1 element)
 
 0 (String, 18 characters ) service-links-digg
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-delicious (Array, 5 elements)
 
 title (String, 140 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/delicious.png" alt="del.icio.us logo" />
 
 href (String, 23 characters ) http://del.icio.us/post
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 33 characters ) Bookmark this post on del.icio.us
 
 class (Array, 1 element)
 
 0 (String, 23 characters ) service-links-delicious
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-reddit (Array, 5 elements)
 
 title (String, 132 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/reddit.png" alt="Reddit logo" />
 
 href (String, 25 characters ) https://reddit.com/submit
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 30 characters ) Submit this post on reddit.com
 
 class (Array, 1 element)
 
 0 (String, 20 characters ) service-links-reddit
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-stumbleupon (Array, 5 elements)
 
 title (String, 140 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/stumbleit.png" alt="StumbleUpon logo" />
 
 href (String, 33 characters ) http://www.stumbleupon.com/submit
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 28 characters ) Thumb this up at StumbleUpon
 
 class (Array, 1 element)
 
 0 (String, 25 characters ) service-links-stumbleupon
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-yahoo (Array, 5 elements)
 
 title (String, 130 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/yahoo.png" alt="Yahoo logo" />
 
 href (String, 49 characters ) https://bookmarks.yahoo.com/myresults/bookmarklet
 
 query (Array, 2 elements)
 
 u (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 t (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 27 characters ) Bookmark this post on Yahoo
 
 class (Array, 1 element)
 
 0 (String, 19 characters ) service-links-yahoo
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 - #items (Array, 1 element)
 
 0 (Array, 5 elements)
 
 value (String, 33938 characters )  <style type="text/css"> P { margin-bottom...
 
 <style type="text/css"> P { margin-bottom: 0.08in; }</style> According to the National Highway Traffic Safety Administration’s (NHTSA) Traffic Safety Facts Report from the same year, 2.5 million reported intersection accidents occurred in the United States during 2012. In total, the reported crashes resulted in over 680,000 injuries [[{"type":"media","view_mode":"drupalimc_large","fid":"13280","attributes":{"alt":"","class":"media-image","style":"float: right;","typeof":"foaf:Image"}}]]and 2,850 fatalities. Accidents caused by red light running accounted for 100,000 of those accidents and 1,000 of the fatalities (SRF Associates, 2014, p. 1). With 35% of fatalities coming from a mere 4% of all reported accidents, red light running poses a clear threat to all motorists and pedestrians crossing the street at busy intersections. “Red light running” is defined as a vehicle that enters an intersection or crosses the stop line after the light has turned red. This could include not fully stopping before turning right, passing through a red light after it changes from yellow and going through a red light while other movements in the intersection (turn arrows, pedestrian crossings) are being served (SRF Associates, 2014, p. 1). Several studies have found that red light camera programs reduce the number and rate of red light violations. In the last decade, over 400 cities have utilized these programs to combat this public health concern. The theory is that putting Red Light Cameras at intersections with a noted history of red light violations and recording these violations for prosecution will alter motorist behavior; the threat of a ticket will prevent or reduce instances of red light running. In addition, the change in motorist behavior will ultimately reduce overall accidents and injuries thus promoting public safety (SRF Associates, 2014, p. 2). In April, 2009 New York State passed legislation clearing the way for Rochester to implement its Red Light Traffic Enforcement Program (Bortnick, 2009). Since the program went live in November 2010, 48 cameras have been installed at 32 intersections in the city of Rochester (SRF Associates, 2014, p. 1).Description of CommunityAccording to 2010 Census data, there are 1,054,000 million people in the Greater Rochester Area with 210,565 of them residing in the city. The Greater Rochester Area is the second largest economic center in New York State, trailing only New York City. Including Enter City which is primarily downtown, there are a total of 36 neighborhoods in the City of Rochester  (Rochester, NY Neighborhoods, 2016); for a list and color coded map of neighborhoods refer to the Appendix. The yellow block in the middle is Center City, containing what is considered “downtown.” Areas in green are considered high desirability, high safety and low crime neighborhoods. Areas in red are considered to be low desirability, low safety and high crime neighborhoods.The color coded map of Rochester reveals a few startling facts. First, the red neighborhoods on the map are all geographically connected to each other. They form “The Crescent;” an area of concentrated poverty representing the highest proportion of black, Latino and immigrant residents. As of 2015, Rochester had more people living at less than half the federal poverty level than any other American city of comparable size with 16.2% of those living in extreme poverty (Crescent of Poverty, 2015). Second, of the 36 separate neighborhoods listed in the Appendix, 14 of them are color coded red. Two neighborhoods the map codes in green (Susan B. Anthony and Brown Square) are mislabeled. On the map in the Appendix, there are two small areas west of Center City identified as high desirability, high safety and low crime. My experience working in these neighborhoods has shown them to be two of the most economically challenged and dangerous.[[{"type":"media","view_mode":"drupalimc_large","fid":"13284","attributes":{"alt":"","class":"media-image","typeof":"foaf:Image"}}]]The Brown Square area includes the “Fruit Belt;” a grouping of streets named after fruits known for poverty, crime and high immigrant populations (Governale, 2015). Located near Sahlen’s Stadium where the Rochester Rhinos play, this troubled neighborhood also contains Enrico Fermi School #17. New York State test scores consistently show School #17 to be one of the lowest performing schools in the state, firmly entrenched in the bottom 1% of all schools for the last decade (School #17- Enrico Fermi, 2016). The Susan B. Anthony Neighborhood has historically been considered part of the Crescent (Crescent of Poverty, 2015), so I added these neighborhoods to those coded in red. That brings the total number of high crime, low safety and low desirability neighborhoods to 16, or 44% of the 36 identified areas. The Red-Light Camera Traffic Safety Program is contained within the City of Rochester, meaning there are no cameras at any suburban intersections. Of the 36 neighborhoods considered part of the city proper, 16 contain red light cameras. It is important to point out that there are no traffic cameras on Main St. in Center City, and the lack of cameras in one of the highest traffic areas in the County compared to other chosen intersections is alarming. Excluding downtown, 11 of the 15 neighborhoods are considered high crime, low safety and low desirability. Literature Review In the early years of the program, opposition pointed to a lack of statistical evidence proving the program increased public safety or justifying its need in the community. Three years into operations the City hired an independent auditor, SRF Associates, to evaluate the effectiveness of cameras in reducing the frequency and severity of accidents caused by red light violations (SRF Associates, 2014, p. 1). The City hoped the findings of the study, released to the public in November 2014, would provide overwhelming evidence that the program positively impacted public safety and silence critics suggested the only benefits were to the City’s bottom line. While the aggregate numbers appear impressive and overall accidents at red light intersections were down 26%, a deeper dive into the numbers raised questions about just how effective the program is. Of the 32 intersections studied, 8 experienced increases in total collisions while 11 saw increases in rear end crashes and 6 had a higher frequency of right angle crashes. Overall, eleven of the 32 intersections saw increases in violations (SRF Associates, 2014, p. 23); with 35% of intersections seeing increased frequency of red light violations and 25% seeing increased collisions, some questioned if the cameras were affecting driver behavior as intended. One City Council member, Elaine Spaull, stated the cameras were intended to change driver behavior leading to few fines and few collection measures (Fien, 2015). While the cameras improved overall safety through accident reduction, the increase in violations and accidents at several intersections cast doubts on the overall efficacy and effect of the program while failing to silence opponents.Concerns and ControversyOne of the concerns surrounding the Red Light Camera program is where the cameras are placed. According the study on Red Light Camera Effectiveness in Rochester released in November 2014, 207 potential camera locations were reviewed. These 207 locations were identified through recommendations from the Rochester Police Department's (RPD) review of accident data by City staff and traffic volumes. A small camera was placed at each of these locations for a 12-hour period to measure signal compliance. An intersection was recommended for installation if 15 or more red light violations occurred in the 12-hour period, if it exhibited a history of accidents, and if the camera manufacturer determined the intersection was suitable. A team of City staff with representatives from the RPD, Information Technology, Engineering, Law and budget departments made the final decision on where the cameras would be installed (SRF Associates, 2014, pp. 2-3).Several community members, including City Council Members who originally supported the cameras, have expressed concerns over them recently. In June 2015, both Council President Loretta Scott and Council member Adam McFadden expressed concerns that the program focuses on impoverished neighborhoods which disproportionately punishes Rochesterians with less disposable income (Fien, 2015). Further analysis of aggregate of the data from the SRF report suggests these Council members may have a point.[[{"type":"media","view_mode":"drupalimc_large","fid":"13282","attributes":{"alt":"","class":"media-image","style":"float: left;","typeof":"foaf:Image"}}]]While plotting camera locations on the map in the Appendix, I noticed the same geographical pattern as Scott and McFadden. There are high concentrations of cameras in the high crime, low safety neighborhoods that form the Crescent. To see how high, I tallied the number of intersections and overall cameras located in each color coded section. Excluding Center City, 11 of the 15 neighborhoods with cameras are coded red on the map and considered high crime, high poverty areas. Of the 16 multi-camera intersections, 10 are located in those 11 high risk neighborhoods. In total, 53% of the intersections (17 of 32) and 56% of the cameras (27 of 48) are located in 31% (11 of 36) of Rochester Neighborhoods. If you remove Center City and only include neighborhoods with cameras, 61% of the intersections (17 of 28), 63% of cameras (27 of 43) and 67% of the multi-camera intersections (10 of 15) are located in high risk neighborhoods. While these numbers show a disturbing trend, removing one block intensifies the argument the cameras target the poorest neighborhoods. Five cameras and three intersections are located in the same block near Kodak Park where 104 forks into Ridge Rd and Ridgeway Avenue, an area coded green. Removing that 100 sq. ft. area, in conjunction with Center City, the ratios are even more startling. That puts 68% of intersections (17 of 25), 71% of all cameras (27 of 38) and 71% of multiple-camera intersections (10 of 14) in impoverished neighborhoods. Simply put, neighborhoods with cameras located in the Crescent comprise less than one third of the City, but represent 73% of all residential neighborhoods monitored through the Red Light Camera Traffic Safety Program.The concentration of red light cameras in the Crescent raises concerns about the privacy of citizens. License plate numbers and registration data as well as who owns the vehicle and where it’s located are aggregated into large databases creating more opportunities to collect this data thus stockpiling this information (Lederman, Taylor, & Garrett, 2016, p. 118). There are several instances over the last few years of data breaches in the public sector and private industry, and this information could be used by hackers to track the movements of people, identify frequently used routes and compile locations on where to find someone. Private information relating to specific individuals could become widely available to people with ill intentions (Lederman, Taylor, & Garrett, 2016, p. 115)While the current cameras only take photos of red light violations, as the technology associated with traffic enforcement cameras evolves these could turn into surveillance cameras used in broken windows policing. The theory of broken windows policing involves focusing on areas with unattended disorder to maintain public order (Smith & Greenblatt, 2016, pp. 460-461). By focusing on neighborhoods with high crime, high poverty and dilapidated structures with broken windows, controlling the main sources of crime. The neighborhoods with the highest concentration of red light cameras meet these criteria, and are already being watched 24/7. The RPD already has a Police Overt Digital Surveillance System (PODSS) comprised of fifty cameras placed in high crime areas to help police maintain order (PODSS, 2016). Adding the red camera intersections to the PODSS program may be as easy as switching out cameras or updating software, and adding additional surveillance to already struggling neighborhoods falls in line with the current RPD policies and approach to policing these communities.Lastly, concerns are prevalent over how the program is administered from start to finish; in particular, there are no witnesses to the offense and no due process. When a violation occurs, the camera snaps a photo of the vehicle license plate, making it difficult to identify the actual driver or passengers. The recorded footage of the violation is sent to Redflex Traffic Systems in Arizona, the company Rochester contracted for the cameras, where it is reviewed by company auditors. If these civilians determine a violation has occurred, the incident is sent back to Rochester and reviewed by members of the RPD. Notice of the violation is sent to the address attached to the vehicle registration along with a $50 fine (Twietmeyer, 2015).With no witnesses, officer discretion and the circumstances surrounding the violation are discarded in favor of photographic evidence that is often viewed as indisputable. There is no trial or opportunity to defend yourself- you’re sent a document telling you that you are guilty and that you must pay a fine. If the owner wasn’t driving the car when the violation occurred, they are still responsible. While I was unable to find statistics on what percentage of tickets are overturned, the City of Rochester rarely rescinds violations. There are also concerns violations aren’t reported in a timely fashion, and that registered owners don’t find out about the fine until it’s too late. Failure to pay the violation can have extreme consequences, and some enforcement measures used support claims the program is a money grab for the City of Rochester.Since the beginning of the program, unpaid violations were referred to the City’s Collection Agency EOS CCA (City of Rochester, 2016). Unpaid penalties damage credit reports, creating a scenario where the vehicle owner responsible for the violation is notified through their credit report and not the City assessing the fine. The judgments levied by the City stay on credit reports for years and can impact the ability to purchase cars or homes. Frustrated by accumulated unpaid fines, the City of Rochester implemented extreme policy measures to increase the collection of fines as revenue. In May 2015, the City started booting cars with unpaid red light camera violations (Riley, 2015). Many citizens and City Council members saw this as an overly aggressive measure to collect fines on a program advertised as a public safety measure, with McFadden and Scott pointing to the impact and perceived focus on the poorest neighborhoods in the city. Additionally, Mayor Warren has included further punitive measures in her Fiscal Year 2016 Budget. Despite the fact these tickets are a civil matter, Mayor Warren included a plan to report these violations to the Department of Motor Vehicles (Riley, 2015). Reporting these tickets to them could impact the ability to register a vehicle, renew a license and could lead to suspension or revocation of driving privileges. Should this happen to a vehicle owner who is held responsible for another motorist or one who isn’t properly notified, charges like driving without a license, driving on a suspended license and driving an unregistered vehicle become tangible turning a civil fine into a serious criminal matter.Despite the negative public perception of the program and the implications the cameras target low income residents, many argue the financial benefits of the Red Light Camera Traffic Enforcement Program, the City of Rochester will ensure the initiative continues. While estimates range on how much revenue red light fines the City makes, in 2014 the city assessed almost 87,000 citations generating $3.7 million dollars in revenue (Davidsen, 2015). It is not clear much of that money the City got to keep, and the Rochester CAFR doesn’t identify the red light cameras as a specific revenue source. It also doesn’t mention where the money went, or how the revenue generated from the cameras will be used to benefit the City. The fact that the revenue is hidden in other line items and not specifically discussed supports the claims this program is a cash cow for the City of Rochester.One thing that is clear is the cameras aren’t going anywhere in the near future. In November 2014, City Council voted to extend the program through December 1, 2019 by a 6-3 margin. The three council members who voted against continuing the program were Elaine Spaull, Adam Mc Fadden and Loretta Scott (Staff Report, 2014).ConclusionWhile the report from SRF Associates provides data showing some improvements to public health and traffic safety, the benefits do not outweigh the negative impact the Red Light Camera Traffic Safety Program has had on the City of Rochester. These cameras were advertised and implemented as a public safety measure, but when due process is removed and fines are levied with the assumption of guilt, it becomes harder to see them as anything other than a cash cow for a struggling City. Based on the location and quantity of cameras located in the Crescent, there are strong implications this program is in fact targeting the neediest families in our community and some of the poorest neighborhoods in all New York State. The measures the City chooses to ensure payment of these fines are excessive, and inflict damage beyond a $50 fine if not paid promptly. The decision to boot vehicles, send fines to collection and report them to the DMV show how desperate the City of Rochester is to maintain this revenue source, especially when 3 City Council members who initially supported the initiative have raised serious concerns about the equity of the program in an already racially divided community. At the least, the City of Rochester owes its citizens transparency over how much revenue is generated from the program. Hiding the proceeds in vague fund balances does nothing to support claims that the goal of the cameras is to improve traffic safety.If the focus is on profits instead of public safety, then the privacy and security of sensitive information is most likely an afterthought. Part of public health is peace of mind; the ability for the public to feel safe and protected in the community knowing the police and government are protecting your rights. As long as these cameras are part of the City, the lack of trust felt by the residents of the Crescent and vehicle owners who were mistreated or ignored during the violation process will override any feelings of security. The City already uses PODSS as a tool, harming the relationship between the community and the RPD. Until studies show overwhelming reductions in accidents and violations strengthening the public safety stance or due process is added allowing for the application of circumstantial discretion, the harm the cameras cause will continue to outweigh any safety benefits. Angry citizens will continue to feel like the program is nothing more than a cash cow, creating further resentment for a City government more concerned with collecting fines than addressing the blatant racial, procedural and civil right concerns the Red Light Traffic Safety Program leaves in its wake.References Bortnick, C. J. (2009, April 2). Rochester to Get Traffic Cameras. Retrieved from The 9/12 Project: article referenced taken from RNews: http://www.meetup.com/WSR912/messages/boards/thread/6617713City of Rochester. (2016, April 27 2016). Red Light Camera Program- Frequently Asked Questions. Retrieved from Red Light Camera Traffic Safety Program: http://www.cityofrochester.gov/article.aspx?id=8589940922Crescent of Poverty. (2015). Retrieved from RocWiki: The People's Guide to Rochester: http://rocwiki.org/Crescent_of_PovertyDavidsen, B. (2015, November 2). NYS Exposed: The future of red light cameras in Rochester. Retrieved from WHEC Rochester- News 10: http://www.whec.com/article/stories/s3950224.shtmlGovernale, M. (2015, August 26). Help Nurture Rochester's Fruit Belt. Retrieved from RochesterSubway.com: http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fruit-belt/Lederman, J., Taylor, B. D., & Garrett, M. (2016). A private matter: the implication of privacy regulations for itelligent transportaton systems. Transportation Planning and Technology, 39:2, 115-135.Rochester, NY Neighboorhoods. (2016, April 27). Retrieved from Google Maps: https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UTF8&jsv=290a&authuser=1&mid=1iJHDrruEBEwP1yeJKYi-vCNfobsSmith, K. B., & Greenblatt, A. (2016). Governing States and Localities. Los Angeles: CQ Press, an Imprint of Sage Publications, Inc.SRF Associates. (2014). Red Light Camera Effectiveness Evaluation. Rochester: City of Rochester, Monroe County, New York.Voorhees, S. (2015, June 24). Rochester City Councilman Calls for Investigation Into Red Light Camera Program. Retrieved from Time Warner Cable News: http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-rochester-adam-mcfadden.html <style type="text/css"> P { margin-bottom: 0.08in; }</style> Appendix:Camera Placement in Neighborhoods Color Coded by Safety & Desirability[[{"type":"media","view_mode":"drupalimc_large","fid":"13286","attributes":{"alt":"","class":"media-image","typeof":"foaf:Image"}}]] <style type="text/css"> P { margin-bottom: 0.08in; }</style> Contact the author: Robert D. Richardson III, Department of Public Administration, SUNY Brockport. Correspondence concerning this article should be addressed to Robert D. Richardson III, Brockport MetroCenter. 55 St. Paul St., Rochester, NY 14604. Contact: rrich4@u.brockport.eduRead the original paper[[{"type":"media","view_mode":"drupalimc_large","fid":"13285","attributes":{"alt":"","class":"media-image","height":"270","typeof":"foaf:Image","width":"270"}}]][Rochester Indymedia note on profit motive and RedFlex corruption: According to page 49, Exhibit D Compensation & Pricing, of the <a href="http://rochester.indymedia.org/node/15438">contract between the city of Rochester and RedFlex</a>, “The fixed fee shall be $3,740 Per Month per System.” From what Rochester Indymedia can gather from the contract, a “System” simply means a camera at an intersection. Mr. Richardson's paper notes that “48 cameras have been installed at 32 intersections” which means that RedFlex, a private, for-profit company, is raking in $179,520 per month. Over a 12 month period, that's $2,154,240 per year. That's private profit: public money is being used to subsidize a private entity—a corporation—that offers the service of using its technology to penalize drivers in Rochester. The city certainly gets some of the money from the ticket as well. As it is the case that most of the cameras are located in impoverished neighborhoods—71%—as Mr. Richardson notes, then it's reasonable to assume that most of that $2.1 million in private profit is being taken directly from the pockets of the people living in those neighborhoods and shuttled to a privte company in Arizona. That's a bad deal. That's hardworking folks' money being fleeced from them for the benefit of a private corporation—over minor traffic violations. Another thing to consider with RedFlex is the massive bribery scandal officials engaged in to get the system installed in Chicago. See: <a href="http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html" rel="nofollow" target="_blank">http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html</a>. Why does the city continue to do business with a company that is being investigated for crimes where its former CEO has plead guilty to a massive, $2 million bribery scheme? The city found there were no ethics violations, but when $4 million is raked in from the program, one could see why there would be hesitation at finding anything wrong with the program from an economic point of view.]Related: <a href="http://rochester.indymedia.org/node/15438">FOIA Docs: Red-light Camera Contract between City of Rochester and Redflex</a> | <a href="http://rochester.indymedia.org/node/100298">Strike it down! Larry Krieger fights City Hall on red light cameras</a> |<a href="http://rochester.indymedia.org/node/100297"> Larry Krieger's 1st transcribed hearing re: red light camera ticket</a> | <a href="http://rochester.indymedia.org/node/104241">Rochester's Red Light Camera Law Is Bad For Business and Tourism</a> | <a href="http://rochester.indymedia.org/node/7267">Mapping the Police State: Police Cameras, Maps, and You! </a>
 
 summary (String, 0 characters )
 
 format (String, 9 characters ) full_html
 
 safe_value (String, 37076 characters ) <style type="text/css"> <![CDATA[/*...
 
 <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> According to the National Highway Traffic Safety Administration’s (NHTSA) Traffic Safety Facts Report from the same year, 2.5 million reported intersection accidents occurred in the United States during 2012. In total, the reported crashes resulted in over 680,000 injuries <div class="media media-element-container media-drupalimc_large media-float-right"><div id="file-13280" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13280">redlight-program-graphic.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/redlight-program-graphic.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: right;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/redlight-program-graphic.jpg?itok=QyN5uHYb" alt="" title="" /></a> </div> </div> </div>and 2,850 fatalities. Accidents caused by red light running accounted for 100,000 of those accidents and 1,000 of the fatalities (SRF Associates, 2014, p. 1). With 35% of fatalities coming from a mere 4% of all reported accidents, red light running poses a clear threat to all motorists and pedestrians crossing the street at busy intersections. “Red light running” is defined as a vehicle that enters an intersection or crosses the stop line after the light has turned red. This could include not fully stopping before turning right, passing through a red light after it changes from yellow and going through a red light while other movements in the intersection (turn arrows, pedestrian crossings) are being served (SRF Associates, 2014, p. 1). Several studies have found that red light camera programs reduce the number and rate of red light violations. In the last decade, over 400 cities have utilized these programs to combat this public health concern. The theory is that putting Red Light Cameras at intersections with a noted history of red light violations and recording these violations for prosecution will alter motorist behavior; the threat of a ticket will prevent or reduce instances of red light running. In addition, the change in motorist behavior will ultimately reduce overall accidents and injuries thus promoting public safety (SRF Associates, 2014, p. 2). In April, 2009 New York State passed legislation clearing the way for Rochester to implement its Red Light Traffic Enforcement Program (Bortnick, 2009). Since the program went live in November 2010, 48 cameras have been installed at 32 intersections in the city of Rochester (SRF Associates, 2014, p. 1). Description of Community According to 2010 Census data, there are 1,054,000 million people in the Greater Rochester Area with 210,565 of them residing in the city. The Greater Rochester Area is the second largest economic center in New York State, trailing only New York City. Including Enter City which is primarily downtown, there are a total of 36 neighborhoods in the City of Rochester (Rochester, NY Neighborhoods, 2016); for a list and color coded map of neighborhoods refer to the Appendix. The yellow block in the middle is Center City, containing what is considered “downtown.” Areas in green are considered high desirability, high safety and low crime neighborhoods. Areas in red are considered to be low desirability, low safety and high crime neighborhoods. The color coded map of Rochester reveals a few startling facts. First, the red neighborhoods on the map are all geographically connected to each other. They form “The Crescent;” an area of concentrated poverty representing the highest proportion of black, Latino and immigrant residents. As of 2015, Rochester had more people living at less than half the federal poverty level than any other American city of comparable size with 16.2% of those living in extreme poverty (Crescent of Poverty, 2015). Second, of the 36 separate neighborhoods listed in the Appendix, 14 of them are color coded red. Two neighborhoods the map codes in green (Susan B. Anthony and Brown Square) are mislabeled. On the map in the Appendix, there are two small areas west of Center City identified as high desirability, high safety and low crime. My experience working in these neighborhoods has shown them to be two of the most economically challenged and dangerous. <div class="media media-element-container media-drupalimc_large"><div id="file-13284" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13284">city.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/city.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/city.png?itok=GvM9fHSW" alt="" title="" /></a> </div> </div> </div> The Brown Square area includes the “Fruit Belt;” a grouping of streets named after fruits known for poverty, crime and high immigrant populations (Governale, 2015). Located near Sahlen’s Stadium where the Rochester Rhinos play, this troubled neighborhood also contains Enrico Fermi School #17. New York State test scores consistently show School #17 to be one of the lowest performing schools in the state, firmly entrenched in the bottom 1% of all schools for the last decade (School #17- Enrico Fermi, 2016). The Susan B. Anthony Neighborhood has historically been considered part of the Crescent (Crescent of Poverty, 2015), so I added these neighborhoods to those coded in red. That brings the total number of high crime, low safety and low desirability neighborhoods to 16, or 44% of the 36 identified areas. The Red-Light Camera Traffic Safety Program is contained within the City of Rochester, meaning there are no cameras at any suburban intersections. Of the 36 neighborhoods considered part of the city proper, 16 contain red light cameras. It is important to point out that there are no traffic cameras on Main St. in Center City, and the lack of cameras in one of the highest traffic areas in the County compared to other chosen intersections is alarming. Excluding downtown, 11 of the 15 neighborhoods are considered high crime, low safety and low desirability.  Literature Review In the early years of the program, opposition pointed to a lack of statistical evidence proving the program increased public safety or justifying its need in the community. Three years into operations the City hired an independent auditor, SRF Associates, to evaluate the effectiveness of cameras in reducing the frequency and severity of accidents caused by red light violations (SRF Associates, 2014, p. 1). The City hoped the findings of the study, released to the public in November 2014, would provide overwhelming evidence that the program positively impacted public safety and silence critics suggested the only benefits were to the City’s bottom line. While the aggregate numbers appear impressive and overall accidents at red light intersections were down 26%, a deeper dive into the numbers raised questions about just how effective the program is. Of the 32 intersections studied, 8 experienced increases in total collisions while 11 saw increases in rear end crashes and 6 had a higher frequency of right angle crashes. Overall, eleven of the 32 intersections saw increases in violations (SRF Associates, 2014, p. 23); with 35% of intersections seeing increased frequency of red light violations and 25% seeing increased collisions, some questioned if the cameras were affecting driver behavior as intended. One City Council member, Elaine Spaull, stated the cameras were intended to change driver behavior leading to few fines and few collection measures (Fien, 2015). While the cameras improved overall safety through accident reduction, the increase in violations and accidents at several intersections cast doubts on the overall efficacy and effect of the program while failing to silence opponents. Concerns and Controversy One of the concerns surrounding the Red Light Camera program is where the cameras are placed. According the study on Red Light Camera Effectiveness in Rochester released in November 2014, 207 potential camera locations were reviewed. These 207 locations were identified through recommendations from the Rochester Police Department's (RPD) review of accident data by City staff and traffic volumes. A small camera was placed at each of these locations for a 12-hour period to measure signal compliance. An intersection was recommended for installation if 15 or more red light violations occurred in the 12-hour period, if it exhibited a history of accidents, and if the camera manufacturer determined the intersection was suitable. A team of City staff with representatives from the RPD, Information Technology, Engineering, Law and budget departments made the final decision on where the cameras would be installed (SRF Associates, 2014, pp. 2-3). Several community members, including City Council Members who originally supported the cameras, have expressed concerns over them recently. In June 2015, both Council President Loretta Scott and Council member Adam McFadden expressed concerns that the program focuses on impoverished neighborhoods which disproportionately punishes Rochesterians with less disposable income (Fien, 2015). Further analysis of aggregate of the data from the SRF report suggests these Council members may have a point. <div class="media media-element-container media-drupalimc_large media-float-left"><div id="file-13282" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13282">stop-light.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/stop-light.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: left;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/stop-light.jpg?itok=fDU3I99W" alt="" title="" /></a> </div> </div> </div>While plotting camera locations on the map in the Appendix, I noticed the same geographical pattern as Scott and McFadden. There are high concentrations of cameras in the high crime, low safety neighborhoods that form the Crescent. To see how high, I tallied the number of intersections and overall cameras located in each color coded section. Excluding Center City, 11 of the 15 neighborhoods with cameras are coded red on the map and considered high crime, high poverty areas. Of the 16 multi-camera intersections, 10 are located in those 11 high risk neighborhoods. In total, 53% of the intersections (17 of 32) and 56% of the cameras (27 of 48) are located in 31% (11 of 36) of Rochester Neighborhoods. If you remove Center City and only include neighborhoods with cameras, 61% of the intersections (17 of 28), 63% of cameras (27 of 43) and 67% of the multi-camera intersections (10 of 15) are located in high risk neighborhoods. While these numbers show a disturbing trend, removing one block intensifies the argument the cameras target the poorest neighborhoods. Five cameras and three intersections are located in the same block near Kodak Park where 104 forks into Ridge Rd and Ridgeway Avenue, an area coded green. Removing that 100 sq. ft. area, in conjunction with Center City, the ratios are even more startling. That puts 68% of intersections (17 of 25), 71% of all cameras (27 of 38) and 71% of multiple-camera intersections (10 of 14) in impoverished neighborhoods. Simply put, neighborhoods with cameras located in the Crescent comprise less than one third of the City, but represent 73% of all residential neighborhoods monitored through the Red Light Camera Traffic Safety Program. The concentration of red light cameras in the Crescent raises concerns about the privacy of citizens. License plate numbers and registration data as well as who owns the vehicle and where it’s located are aggregated into large databases creating more opportunities to collect this data thus stockpiling this information (Lederman, Taylor, & Garrett, 2016, p. 118). There are several instances over the last few years of data breaches in the public sector and private industry, and this information could be used by hackers to track the movements of people, identify frequently used routes and compile locations on where to find someone. Private information relating to specific individuals could become widely available to people with ill intentions (Lederman, Taylor, & Garrett, 2016, p. 115) While the current cameras only take photos of red light violations, as the technology associated with traffic enforcement cameras evolves these could turn into surveillance cameras used in broken windows policing. The theory of broken windows policing involves focusing on areas with unattended disorder to maintain public order (Smith & Greenblatt, 2016, pp. 460-461). By focusing on neighborhoods with high crime, high poverty and dilapidated structures with broken windows, controlling the main sources of crime. The neighborhoods with the highest concentration of red light cameras meet these criteria, and are already being watched 24/7. The RPD already has a Police Overt Digital Surveillance System (PODSS) comprised of fifty cameras placed in high crime areas to help police maintain order (PODSS, 2016). Adding the red camera intersections to the PODSS program may be as easy as switching out cameras or updating software, and adding additional surveillance to already struggling neighborhoods falls in line with the current RPD policies and approach to policing these communities. Lastly, concerns are prevalent over how the program is administered from start to finish; in particular, there are no witnesses to the offense and no due process. When a violation occurs, the camera snaps a photo of the vehicle license plate, making it difficult to identify the actual driver or passengers. The recorded footage of the violation is sent to Redflex Traffic Systems in Arizona, the company Rochester contracted for the cameras, where it is reviewed by company auditors. If these civilians determine a violation has occurred, the incident is sent back to Rochester and reviewed by members of the RPD. Notice of the violation is sent to the address attached to the vehicle registration along with a $50 fine (Twietmeyer, 2015). With no witnesses, officer discretion and the circumstances surrounding the violation are discarded in favor of photographic evidence that is often viewed as indisputable. There is no trial or opportunity to defend yourself- you’re sent a document telling you that you are guilty and that you must pay a fine. If the owner wasn’t driving the car when the violation occurred, they are still responsible. While I was unable to find statistics on what percentage of tickets are overturned, the City of Rochester rarely rescinds violations. There are also concerns violations aren’t reported in a timely fashion, and that registered owners don’t find out about the fine until it’s too late. Failure to pay the violation can have extreme consequences, and some enforcement measures used support claims the program is a money grab for the City of Rochester. Since the beginning of the program, unpaid violations were referred to the City’s Collection Agency EOS CCA (City of Rochester, 2016). Unpaid penalties damage credit reports, creating a scenario where the vehicle owner responsible for the violation is notified through their credit report and not the City assessing the fine. The judgments levied by the City stay on credit reports for years and can impact the ability to purchase cars or homes. Frustrated by accumulated unpaid fines, the City of Rochester implemented extreme policy measures to increase the collection of fines as revenue. In May 2015, the City started booting cars with unpaid red light camera violations (Riley, 2015). Many citizens and City Council members saw this as an overly aggressive measure to collect fines on a program advertised as a public safety measure, with McFadden and Scott pointing to the impact and perceived focus on the poorest neighborhoods in the city. Additionally, Mayor Warren has included further punitive measures in her Fiscal Year 2016 Budget. Despite the fact these tickets are a civil matter, Mayor Warren included a plan to report these violations to the Department of Motor Vehicles (Riley, 2015). Reporting these tickets to them could impact the ability to register a vehicle, renew a license and could lead to suspension or revocation of driving privileges. Should this happen to a vehicle owner who is held responsible for another motorist or one who isn’t properly notified, charges like driving without a license, driving on a suspended license and driving an unregistered vehicle become tangible turning a civil fine into a serious criminal matter. Despite the negative public perception of the program and the implications the cameras target low income residents, many argue the financial benefits of the Red Light Camera Traffic Enforcement Program, the City of Rochester will ensure the initiative continues. While estimates range on how much revenue red light fines the City makes, in 2014 the city assessed almost 87,000 citations generating $3.7 million dollars in revenue (Davidsen, 2015). It is not clear much of that money the City got to keep, and the Rochester CAFR doesn’t identify the red light cameras as a specific revenue source. It also doesn’t mention where the money went, or how the revenue generated from the cameras will be used to benefit the City. The fact that the revenue is hidden in other line items and not specifically discussed supports the claims this program is a cash cow for the City of Rochester. One thing that is clear is the cameras aren’t going anywhere in the near future. In November 2014, City Council voted to extend the program through December 1, 2019 by a 6-3 margin. The three council members who voted against continuing the program were Elaine Spaull, Adam Mc Fadden and Loretta Scott (Staff Report, 2014). Conclusion While the report from SRF Associates provides data showing some improvements to public health and traffic safety, the benefits do not outweigh the negative impact the Red Light Camera Traffic Safety Program has had on the City of Rochester. These cameras were advertised and implemented as a public safety measure, but when due process is removed and fines are levied with the assumption of guilt, it becomes harder to see them as anything other than a cash cow for a struggling City. Based on the location and quantity of cameras located in the Crescent, there are strong implications this program is in fact targeting the neediest families in our community and some of the poorest neighborhoods in all New York State. The measures the City chooses to ensure payment of these fines are excessive, and inflict damage beyond a $50 fine if not paid promptly. The decision to boot vehicles, send fines to collection and report them to the DMV show how desperate the City of Rochester is to maintain this revenue source, especially when 3 City Council members who initially supported the initiative have raised serious concerns about the equity of the program in an already racially divided community. At the least, the City of Rochester owes its citizens transparency over how much revenue is generated from the program. Hiding the proceeds in vague fund balances does nothing to support claims that the goal of the cameras is to improve traffic safety. If the focus is on profits instead of public safety, then the privacy and security of sensitive information is most likely an afterthought. Part of public health is peace of mind; the ability for the public to feel safe and protected in the community knowing the police and government are protecting your rights. As long as these cameras are part of the City, the lack of trust felt by the residents of the Crescent and vehicle owners who were mistreated or ignored during the violation process will override any feelings of security. The City already uses PODSS as a tool, harming the relationship between the community and the RPD. Until studies show overwhelming reductions in accidents and violations strengthening the public safety stance or due process is added allowing for the application of circumstantial discretion, the harm the cameras cause will continue to outweigh any safety benefits. Angry citizens will continue to feel like the program is nothing more than a cash cow, creating further resentment for a City government more concerned with collecting fines than addressing the blatant racial, procedural and civil right concerns the Red Light Traffic Safety Program leaves in its wake. References Bortnick, C. J. (2009, April 2). Rochester to Get Traffic Cameras. Retrieved from The 9/12 Project: article referenced taken from RNews: <a href="http://www.meetup.com/WSR912/messages/boards/thread/6617713">http://www.meetup.com/WSR912/messages/boards/thread/6617713</a> City of Rochester. (2016, April 27 2016). Red Light Camera Program- Frequently Asked Questions. Retrieved from Red Light Camera Traffic Safety Program: <a href="http://www.cityofrochester.gov/article.aspx?id=8589940922">http://www.cityofrochester.gov/article.aspx?id=8589940922</a> Crescent of Poverty. (2015). Retrieved from RocWiki: The People's Guide to Rochester: <a href="http://rocwiki.org/Crescent_of_Poverty">http://rocwiki.org/Crescent_of_Poverty</a> Davidsen, B. (2015, November 2). NYS Exposed: The future of red light cameras in Rochester. Retrieved from WHEC Rochester- News 10: <a href="http://www.whec.com/article/stories/s3950224.shtml">http://www.whec.com/article/stories/s3950224.shtml</a> Governale, M. (2015, August 26). Help Nurture Rochester's Fruit Belt. Retrieved from RochesterSubway.com: <a href="http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fruit-belt/">http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fr...</a> Lederman, J., Taylor, B. D., & Garrett, M. (2016). A private matter: the implication of privacy regulations for itelligent transportaton systems. Transportation Planning and Technology, 39:2, 115-135. Rochester, NY Neighboorhoods. (2016, April 27). Retrieved from Google Maps: <a href="https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UTF8&jsv=290a&authuser=1&mid=1iJHDrruEBEwP1yeJKYi-vCNfobs">https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UT...</a> Smith, K. B., & Greenblatt, A. (2016). Governing States and Localities. Los Angeles: CQ Press, an Imprint of Sage Publications, Inc. SRF Associates. (2014). Red Light Camera Effectiveness Evaluation. Rochester: City of Rochester, Monroe County, New York. Voorhees, S. (2015, June 24). Rochester City Councilman Calls for Investigation Into Red Light Camera Program. Retrieved from Time Warner Cable News: <a href="http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-rochester-adam-mcfadden.html">http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-r...</a> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Appendix: Camera Placement in Neighborhoods Color Coded by Safety & Desirability <div class="media media-element-container media-drupalimc_large"><div id="file-13286" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13286">cameras-for-ted.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/cameras-for-ted.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/cameras-for-ted.png?itok=NR_YO7YE" alt="" title="" /></a> </div> </div> </div> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Contact the author: Robert D. Richardson III, Department of Public Administration, SUNY Brockport. Correspondence concerning this article should be addressed to Robert D. Richardson III, Brockport MetroCenter. 55 St. Paul St., Rochester, NY 14604. Contact: <a href="mailto:rrich4@u.brockport.edu">rrich4@u.brockport.edu</a> Read the original paper <div class="media media-element-container media-drupalimc_large"><div id="file-13285" class="file file-default file-application-pdf"> <h2 class="element-invisible"><a href="/file/13285">PAD683-Local-Issues-Paper-Final(1).pdf</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/PAD683-Local-Issues-Paper-Final%281%29.pdf" alt="" class="media-image" height="270" width="270"><img width="270" height="270" typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/media_thumbnail/public/media-icons/default/application-octet-stream.png?itok=FJGVP5SF" alt="" /> PAD683-Local-Issues-Paper-Final(1).pdf</a> </div> </div> </div> [Rochester Indymedia note on profit motive and RedFlex corruption: According to page 49, Exhibit D Compensation & Pricing, of the <a href="http://rochester.indymedia.org/node/15438">contract between the city of Rochester and RedFlex</a>, “The fixed fee shall be $3,740 Per Month per System.” From what Rochester Indymedia can gather from the contract, a “System” simply means a camera at an intersection. Mr. Richardson's paper notes that “48 cameras have been installed at 32 intersections” which means that RedFlex, a private, for-profit company, is raking in $179,520 per month. Over a 12 month period, that's $2,154,240 per year. That's private profit: public money is being used to subsidize a private entity—a corporation—that offers the service of using its technology to penalize drivers in Rochester. The city certainly gets some of the money from the ticket as well. As it is the case that most of the cameras are located in impoverished neighborhoods—71%—as Mr. Richardson notes, then it's reasonable to assume that most of that $2.1 million in private profit is being taken directly from the pockets of the people living in those neighborhoods and shuttled to a privte company in Arizona. That's a bad deal. That's hardworking folks' money being fleeced from them for the benefit of a private corporation—over minor traffic violations. Another thing to consider with RedFlex is the massive bribery scandal officials engaged in to get the system installed in Chicago. See: <a href="http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html" rel="nofollow" target="_blank">http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html</a>. Why does the city continue to do business with a company that is being investigated for crimes where its former CEO has plead guilty to a massive, $2 million bribery scheme? The city found there were no ethics violations, but when $4 million is raked in from the program, one could see why there would be hesitation at finding anything wrong with the program from an economic point of view.] Related: <a href="http://rochester.indymedia.org/node/15438">FOIA Docs: Red-light Camera Contract between City of Rochester and Redflex</a> | <a href="http://rochester.indymedia.org/node/100298">Strike it down! Larry Krieger fights City Hall on red light cameras</a> |<a href="http://rochester.indymedia.org/node/100297"> Larry Krieger's 1st transcribed hearing re: red light camera ticket</a> | <a href="http://rochester.indymedia.org/node/104241">Rochester's Red Light Camera Law Is Bad For Business and Tourism</a> | <a href="http://rochester.indymedia.org/node/7267">Mapping the Police State: Police Cameras, Maps, and You! </a>
 
 safe_summary (String, 0 characters )
 - #formatter (String, 12 characters ) text_default
 - 0 (Array, 3 elements)
 
 #type (String, 9 characters ) container
 
 #attributes (Array, 1 element)
 
 class (String, 8 characters ) clearfix
 
 0 (Array, 1 element)
 
 #markup (String, 37076 characters ) <style type="text/css"> <![CDATA[/*...
 
 <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> According to the National Highway Traffic Safety Administration’s (NHTSA) Traffic Safety Facts Report from the same year, 2.5 million reported intersection accidents occurred in the United States during 2012. In total, the reported crashes resulted in over 680,000 injuries <div class="media media-element-container media-drupalimc_large media-float-right"><div id="file-13280" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13280">redlight-program-graphic.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/redlight-program-graphic.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: right;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/redlight-program-graphic.jpg?itok=QyN5uHYb" alt="" title="" /></a> </div> </div> </div>and 2,850 fatalities. Accidents caused by red light running accounted for 100,000 of those accidents and 1,000 of the fatalities (SRF Associates, 2014, p. 1). With 35% of fatalities coming from a mere 4% of all reported accidents, red light running poses a clear threat to all motorists and pedestrians crossing the street at busy intersections. “Red light running” is defined as a vehicle that enters an intersection or crosses the stop line after the light has turned red. This could include not fully stopping before turning right, passing through a red light after it changes from yellow and going through a red light while other movements in the intersection (turn arrows, pedestrian crossings) are being served (SRF Associates, 2014, p. 1). Several studies have found that red light camera programs reduce the number and rate of red light violations. In the last decade, over 400 cities have utilized these programs to combat this public health concern. The theory is that putting Red Light Cameras at intersections with a noted history of red light violations and recording these violations for prosecution will alter motorist behavior; the threat of a ticket will prevent or reduce instances of red light running. In addition, the change in motorist behavior will ultimately reduce overall accidents and injuries thus promoting public safety (SRF Associates, 2014, p. 2). In April, 2009 New York State passed legislation clearing the way for Rochester to implement its Red Light Traffic Enforcement Program (Bortnick, 2009). Since the program went live in November 2010, 48 cameras have been installed at 32 intersections in the city of Rochester (SRF Associates, 2014, p. 1). Description of Community According to 2010 Census data, there are 1,054,000 million people in the Greater Rochester Area with 210,565 of them residing in the city. The Greater Rochester Area is the second largest economic center in New York State, trailing only New York City. Including Enter City which is primarily downtown, there are a total of 36 neighborhoods in the City of Rochester (Rochester, NY Neighborhoods, 2016); for a list and color coded map of neighborhoods refer to the Appendix. The yellow block in the middle is Center City, containing what is considered “downtown.” Areas in green are considered high desirability, high safety and low crime neighborhoods. Areas in red are considered to be low desirability, low safety and high crime neighborhoods. The color coded map of Rochester reveals a few startling facts. First, the red neighborhoods on the map are all geographically connected to each other. They form “The Crescent;” an area of concentrated poverty representing the highest proportion of black, Latino and immigrant residents. As of 2015, Rochester had more people living at less than half the federal poverty level than any other American city of comparable size with 16.2% of those living in extreme poverty (Crescent of Poverty, 2015). Second, of the 36 separate neighborhoods listed in the Appendix, 14 of them are color coded red. Two neighborhoods the map codes in green (Susan B. Anthony and Brown Square) are mislabeled. On the map in the Appendix, there are two small areas west of Center City identified as high desirability, high safety and low crime. My experience working in these neighborhoods has shown them to be two of the most economically challenged and dangerous. <div class="media media-element-container media-drupalimc_large"><div id="file-13284" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13284">city.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/city.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/city.png?itok=GvM9fHSW" alt="" title="" /></a> </div> </div> </div> The Brown Square area includes the “Fruit Belt;” a grouping of streets named after fruits known for poverty, crime and high immigrant populations (Governale, 2015). Located near Sahlen’s Stadium where the Rochester Rhinos play, this troubled neighborhood also contains Enrico Fermi School #17. New York State test scores consistently show School #17 to be one of the lowest performing schools in the state, firmly entrenched in the bottom 1% of all schools for the last decade (School #17- Enrico Fermi, 2016). The Susan B. Anthony Neighborhood has historically been considered part of the Crescent (Crescent of Poverty, 2015), so I added these neighborhoods to those coded in red. That brings the total number of high crime, low safety and low desirability neighborhoods to 16, or 44% of the 36 identified areas. The Red-Light Camera Traffic Safety Program is contained within the City of Rochester, meaning there are no cameras at any suburban intersections. Of the 36 neighborhoods considered part of the city proper, 16 contain red light cameras. It is important to point out that there are no traffic cameras on Main St. in Center City, and the lack of cameras in one of the highest traffic areas in the County compared to other chosen intersections is alarming. Excluding downtown, 11 of the 15 neighborhoods are considered high crime, low safety and low desirability.  Literature Review In the early years of the program, opposition pointed to a lack of statistical evidence proving the program increased public safety or justifying its need in the community. Three years into operations the City hired an independent auditor, SRF Associates, to evaluate the effectiveness of cameras in reducing the frequency and severity of accidents caused by red light violations (SRF Associates, 2014, p. 1). The City hoped the findings of the study, released to the public in November 2014, would provide overwhelming evidence that the program positively impacted public safety and silence critics suggested the only benefits were to the City’s bottom line. While the aggregate numbers appear impressive and overall accidents at red light intersections were down 26%, a deeper dive into the numbers raised questions about just how effective the program is. Of the 32 intersections studied, 8 experienced increases in total collisions while 11 saw increases in rear end crashes and 6 had a higher frequency of right angle crashes. Overall, eleven of the 32 intersections saw increases in violations (SRF Associates, 2014, p. 23); with 35% of intersections seeing increased frequency of red light violations and 25% seeing increased collisions, some questioned if the cameras were affecting driver behavior as intended. One City Council member, Elaine Spaull, stated the cameras were intended to change driver behavior leading to few fines and few collection measures (Fien, 2015). While the cameras improved overall safety through accident reduction, the increase in violations and accidents at several intersections cast doubts on the overall efficacy and effect of the program while failing to silence opponents. Concerns and Controversy One of the concerns surrounding the Red Light Camera program is where the cameras are placed. According the study on Red Light Camera Effectiveness in Rochester released in November 2014, 207 potential camera locations were reviewed. These 207 locations were identified through recommendations from the Rochester Police Department's (RPD) review of accident data by City staff and traffic volumes. A small camera was placed at each of these locations for a 12-hour period to measure signal compliance. An intersection was recommended for installation if 15 or more red light violations occurred in the 12-hour period, if it exhibited a history of accidents, and if the camera manufacturer determined the intersection was suitable. A team of City staff with representatives from the RPD, Information Technology, Engineering, Law and budget departments made the final decision on where the cameras would be installed (SRF Associates, 2014, pp. 2-3). Several community members, including City Council Members who originally supported the cameras, have expressed concerns over them recently. In June 2015, both Council President Loretta Scott and Council member Adam McFadden expressed concerns that the program focuses on impoverished neighborhoods which disproportionately punishes Rochesterians with less disposable income (Fien, 2015). Further analysis of aggregate of the data from the SRF report suggests these Council members may have a point. <div class="media media-element-container media-drupalimc_large media-float-left"><div id="file-13282" class="file file-image file-image-jpeg"> <h2 class="element-invisible"><a href="/file/13282">stop-light.jpg</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/stop-light.jpg?width=500&height=500" class="colorbox-load" alt="" style="float: left;"><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/stop-light.jpg?itok=fDU3I99W" alt="" title="" /></a> </div> </div> </div>While plotting camera locations on the map in the Appendix, I noticed the same geographical pattern as Scott and McFadden. There are high concentrations of cameras in the high crime, low safety neighborhoods that form the Crescent. To see how high, I tallied the number of intersections and overall cameras located in each color coded section. Excluding Center City, 11 of the 15 neighborhoods with cameras are coded red on the map and considered high crime, high poverty areas. Of the 16 multi-camera intersections, 10 are located in those 11 high risk neighborhoods. In total, 53% of the intersections (17 of 32) and 56% of the cameras (27 of 48) are located in 31% (11 of 36) of Rochester Neighborhoods. If you remove Center City and only include neighborhoods with cameras, 61% of the intersections (17 of 28), 63% of cameras (27 of 43) and 67% of the multi-camera intersections (10 of 15) are located in high risk neighborhoods. While these numbers show a disturbing trend, removing one block intensifies the argument the cameras target the poorest neighborhoods. Five cameras and three intersections are located in the same block near Kodak Park where 104 forks into Ridge Rd and Ridgeway Avenue, an area coded green. Removing that 100 sq. ft. area, in conjunction with Center City, the ratios are even more startling. That puts 68% of intersections (17 of 25), 71% of all cameras (27 of 38) and 71% of multiple-camera intersections (10 of 14) in impoverished neighborhoods. Simply put, neighborhoods with cameras located in the Crescent comprise less than one third of the City, but represent 73% of all residential neighborhoods monitored through the Red Light Camera Traffic Safety Program. The concentration of red light cameras in the Crescent raises concerns about the privacy of citizens. License plate numbers and registration data as well as who owns the vehicle and where it’s located are aggregated into large databases creating more opportunities to collect this data thus stockpiling this information (Lederman, Taylor, & Garrett, 2016, p. 118). There are several instances over the last few years of data breaches in the public sector and private industry, and this information could be used by hackers to track the movements of people, identify frequently used routes and compile locations on where to find someone. Private information relating to specific individuals could become widely available to people with ill intentions (Lederman, Taylor, & Garrett, 2016, p. 115) While the current cameras only take photos of red light violations, as the technology associated with traffic enforcement cameras evolves these could turn into surveillance cameras used in broken windows policing. The theory of broken windows policing involves focusing on areas with unattended disorder to maintain public order (Smith & Greenblatt, 2016, pp. 460-461). By focusing on neighborhoods with high crime, high poverty and dilapidated structures with broken windows, controlling the main sources of crime. The neighborhoods with the highest concentration of red light cameras meet these criteria, and are already being watched 24/7. The RPD already has a Police Overt Digital Surveillance System (PODSS) comprised of fifty cameras placed in high crime areas to help police maintain order (PODSS, 2016). Adding the red camera intersections to the PODSS program may be as easy as switching out cameras or updating software, and adding additional surveillance to already struggling neighborhoods falls in line with the current RPD policies and approach to policing these communities. Lastly, concerns are prevalent over how the program is administered from start to finish; in particular, there are no witnesses to the offense and no due process. When a violation occurs, the camera snaps a photo of the vehicle license plate, making it difficult to identify the actual driver or passengers. The recorded footage of the violation is sent to Redflex Traffic Systems in Arizona, the company Rochester contracted for the cameras, where it is reviewed by company auditors. If these civilians determine a violation has occurred, the incident is sent back to Rochester and reviewed by members of the RPD. Notice of the violation is sent to the address attached to the vehicle registration along with a $50 fine (Twietmeyer, 2015). With no witnesses, officer discretion and the circumstances surrounding the violation are discarded in favor of photographic evidence that is often viewed as indisputable. There is no trial or opportunity to defend yourself- you’re sent a document telling you that you are guilty and that you must pay a fine. If the owner wasn’t driving the car when the violation occurred, they are still responsible. While I was unable to find statistics on what percentage of tickets are overturned, the City of Rochester rarely rescinds violations. There are also concerns violations aren’t reported in a timely fashion, and that registered owners don’t find out about the fine until it’s too late. Failure to pay the violation can have extreme consequences, and some enforcement measures used support claims the program is a money grab for the City of Rochester. Since the beginning of the program, unpaid violations were referred to the City’s Collection Agency EOS CCA (City of Rochester, 2016). Unpaid penalties damage credit reports, creating a scenario where the vehicle owner responsible for the violation is notified through their credit report and not the City assessing the fine. The judgments levied by the City stay on credit reports for years and can impact the ability to purchase cars or homes. Frustrated by accumulated unpaid fines, the City of Rochester implemented extreme policy measures to increase the collection of fines as revenue. In May 2015, the City started booting cars with unpaid red light camera violations (Riley, 2015). Many citizens and City Council members saw this as an overly aggressive measure to collect fines on a program advertised as a public safety measure, with McFadden and Scott pointing to the impact and perceived focus on the poorest neighborhoods in the city. Additionally, Mayor Warren has included further punitive measures in her Fiscal Year 2016 Budget. Despite the fact these tickets are a civil matter, Mayor Warren included a plan to report these violations to the Department of Motor Vehicles (Riley, 2015). Reporting these tickets to them could impact the ability to register a vehicle, renew a license and could lead to suspension or revocation of driving privileges. Should this happen to a vehicle owner who is held responsible for another motorist or one who isn’t properly notified, charges like driving without a license, driving on a suspended license and driving an unregistered vehicle become tangible turning a civil fine into a serious criminal matter. Despite the negative public perception of the program and the implications the cameras target low income residents, many argue the financial benefits of the Red Light Camera Traffic Enforcement Program, the City of Rochester will ensure the initiative continues. While estimates range on how much revenue red light fines the City makes, in 2014 the city assessed almost 87,000 citations generating $3.7 million dollars in revenue (Davidsen, 2015). It is not clear much of that money the City got to keep, and the Rochester CAFR doesn’t identify the red light cameras as a specific revenue source. It also doesn’t mention where the money went, or how the revenue generated from the cameras will be used to benefit the City. The fact that the revenue is hidden in other line items and not specifically discussed supports the claims this program is a cash cow for the City of Rochester. One thing that is clear is the cameras aren’t going anywhere in the near future. In November 2014, City Council voted to extend the program through December 1, 2019 by a 6-3 margin. The three council members who voted against continuing the program were Elaine Spaull, Adam Mc Fadden and Loretta Scott (Staff Report, 2014). Conclusion While the report from SRF Associates provides data showing some improvements to public health and traffic safety, the benefits do not outweigh the negative impact the Red Light Camera Traffic Safety Program has had on the City of Rochester. These cameras were advertised and implemented as a public safety measure, but when due process is removed and fines are levied with the assumption of guilt, it becomes harder to see them as anything other than a cash cow for a struggling City. Based on the location and quantity of cameras located in the Crescent, there are strong implications this program is in fact targeting the neediest families in our community and some of the poorest neighborhoods in all New York State. The measures the City chooses to ensure payment of these fines are excessive, and inflict damage beyond a $50 fine if not paid promptly. The decision to boot vehicles, send fines to collection and report them to the DMV show how desperate the City of Rochester is to maintain this revenue source, especially when 3 City Council members who initially supported the initiative have raised serious concerns about the equity of the program in an already racially divided community. At the least, the City of Rochester owes its citizens transparency over how much revenue is generated from the program. Hiding the proceeds in vague fund balances does nothing to support claims that the goal of the cameras is to improve traffic safety. If the focus is on profits instead of public safety, then the privacy and security of sensitive information is most likely an afterthought. Part of public health is peace of mind; the ability for the public to feel safe and protected in the community knowing the police and government are protecting your rights. As long as these cameras are part of the City, the lack of trust felt by the residents of the Crescent and vehicle owners who were mistreated or ignored during the violation process will override any feelings of security. The City already uses PODSS as a tool, harming the relationship between the community and the RPD. Until studies show overwhelming reductions in accidents and violations strengthening the public safety stance or due process is added allowing for the application of circumstantial discretion, the harm the cameras cause will continue to outweigh any safety benefits. Angry citizens will continue to feel like the program is nothing more than a cash cow, creating further resentment for a City government more concerned with collecting fines than addressing the blatant racial, procedural and civil right concerns the Red Light Traffic Safety Program leaves in its wake. References Bortnick, C. J. (2009, April 2). Rochester to Get Traffic Cameras. Retrieved from The 9/12 Project: article referenced taken from RNews: <a href="http://www.meetup.com/WSR912/messages/boards/thread/6617713">http://www.meetup.com/WSR912/messages/boards/thread/6617713</a> City of Rochester. (2016, April 27 2016). Red Light Camera Program- Frequently Asked Questions. Retrieved from Red Light Camera Traffic Safety Program: <a href="http://www.cityofrochester.gov/article.aspx?id=8589940922">http://www.cityofrochester.gov/article.aspx?id=8589940922</a> Crescent of Poverty. (2015). Retrieved from RocWiki: The People's Guide to Rochester: <a href="http://rocwiki.org/Crescent_of_Poverty">http://rocwiki.org/Crescent_of_Poverty</a> Davidsen, B. (2015, November 2). NYS Exposed: The future of red light cameras in Rochester. Retrieved from WHEC Rochester- News 10: <a href="http://www.whec.com/article/stories/s3950224.shtml">http://www.whec.com/article/stories/s3950224.shtml</a> Governale, M. (2015, August 26). Help Nurture Rochester's Fruit Belt. Retrieved from RochesterSubway.com: <a href="http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fruit-belt/">http://www.rochestersubway.com/topics/2015/08/help-nurture-rochesters-fr...</a> Lederman, J., Taylor, B. D., & Garrett, M. (2016). A private matter: the implication of privacy regulations for itelligent transportaton systems. Transportation Planning and Technology, 39:2, 115-135. Rochester, NY Neighboorhoods. (2016, April 27). Retrieved from Google Maps: <a href="https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UTF8&jsv=290a&authuser=1&mid=1iJHDrruEBEwP1yeJKYi-vCNfobs">https://www.google.com/maps/d/u/1/viewer?hl=en&oe=UTF8&vps=1&msa=0&ie=UT...</a> Smith, K. B., & Greenblatt, A. (2016). Governing States and Localities. Los Angeles: CQ Press, an Imprint of Sage Publications, Inc. SRF Associates. (2014). Red Light Camera Effectiveness Evaluation. Rochester: City of Rochester, Monroe County, New York. Voorhees, S. (2015, June 24). Rochester City Councilman Calls for Investigation Into Red Light Camera Program. Retrieved from Time Warner Cable News: <a href="http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-rochester-adam-mcfadden.html">http://www.twcnews.com/nys/rochester/news/2015/06/24/red-light-cameras-r...</a> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Appendix: Camera Placement in Neighborhoods Color Coded by Safety & Desirability <div class="media media-element-container media-drupalimc_large"><div id="file-13286" class="file file-image file-image-png"> <h2 class="element-invisible"><a href="/file/13286">cameras-for-ted.png</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/cameras-for-ted.png?width=500&height=500" class="colorbox-load" alt=""><img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/drupalimc_large/public/cameras-for-ted.png?itok=NR_YO7YE" alt="" title="" /></a> </div> </div> </div> <style type="text/css"> <![CDATA[/* ><!]]>*/ </style> Contact the author: Robert D. Richardson III, Department of Public Administration, SUNY Brockport. Correspondence concerning this article should be addressed to Robert D. Richardson III, Brockport MetroCenter. 55 St. Paul St., Rochester, NY 14604. Contact: <a href="mailto:rrich4@u.brockport.edu">rrich4@u.brockport.edu</a> Read the original paper <div class="media media-element-container media-drupalimc_large"><div id="file-13285" class="file file-default file-application-pdf"> <h2 class="element-invisible"><a href="/file/13285">PAD683-Local-Issues-Paper-Final(1).pdf</a></h2> <div class="content"> <a href="http://rochester.indymedia.org/sites/default/files/PAD683-Local-Issues-Paper-Final%281%29.pdf" alt="" class="media-image" height="270" width="270"><img width="270" height="270" typeof="foaf:Image" src="http://rochester.indymedia.org/sites/default/files/styles/media_thumbnail/public/media-icons/default/application-octet-stream.png?itok=FJGVP5SF" alt="" /> PAD683-Local-Issues-Paper-Final(1).pdf</a> </div> </div> </div> [Rochester Indymedia note on profit motive and RedFlex corruption: According to page 49, Exhibit D Compensation & Pricing, of the <a href="http://rochester.indymedia.org/node/15438">contract between the city of Rochester and RedFlex</a>, “The fixed fee shall be $3,740 Per Month per System.” From what Rochester Indymedia can gather from the contract, a “System” simply means a camera at an intersection. Mr. Richardson's paper notes that “48 cameras have been installed at 32 intersections” which means that RedFlex, a private, for-profit company, is raking in $179,520 per month. Over a 12 month period, that's $2,154,240 per year. That's private profit: public money is being used to subsidize a private entity—a corporation—that offers the service of using its technology to penalize drivers in Rochester. The city certainly gets some of the money from the ticket as well. As it is the case that most of the cameras are located in impoverished neighborhoods—71%—as Mr. Richardson notes, then it's reasonable to assume that most of that $2.1 million in private profit is being taken directly from the pockets of the people living in those neighborhoods and shuttled to a privte company in Arizona. That's a bad deal. That's hardworking folks' money being fleeced from them for the benefit of a private corporation—over minor traffic violations. Another thing to consider with RedFlex is the massive bribery scandal officials engaged in to get the system installed in Chicago. See: <a href="http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html" rel="nofollow" target="_blank">http://www.chicagotribune.com/news/watchdog/redlight/ct-red-light-cameras-ceo-guilty-met-20150819-story.html</a>. Why does the city continue to do business with a company that is being investigated for crimes where its former CEO has plead guilty to a massive, $2 million bribery scheme? The city found there were no ethics violations, but when $4 million is raked in from the program, one could see why there would be hesitation at finding anything wrong with the program from an economic point of view.] Related: <a href="http://rochester.indymedia.org/node/15438">FOIA Docs: Red-light Camera Contract between City of Rochester and Redflex</a> | <a href="http://rochester.indymedia.org/node/100298">Strike it down! Larry Krieger fights City Hall on red light cameras</a> |<a href="http://rochester.indymedia.org/node/100297"> Larry Krieger's 1st transcribed hearing re: red light camera ticket</a> | <a href="http://rochester.indymedia.org/node/104241">Rochester's Red Light Camera Law Is Bad For Business and Tourism</a> | <a href="http://rochester.indymedia.org/node/7267">Mapping the Police State: Police Cameras, Maps, and You! </a>
- field_drupalimc_categories (Array, 25 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 2
 - #title (String, 10 characters ) Categories
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 26 characters ) field_drupalimc_categories
 - #field_type (String, 23 characters ) taxonomy_term_reference
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 17 characters ) drupalimc_article
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 10 elements)
 
 0 (Array, 2 elements)
 
 tid (String, 2 characters ) 16
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 1 (Array, 2 elements)
 
 tid (String, 1 characters ) 4
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 2 (Array, 2 elements)
 
 tid (String, 2 characters ) 19
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 3 (Array, 2 elements)
 
 tid (String, 2 characters ) 10
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 4 (Array, 2 elements)
 
 tid (String, 2 characters ) 32
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 5 (Array, 2 elements)
 
 tid (String, 2 characters ) 37
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 6 (Array, 2 elements)
 
 tid (String, 2 characters ) 35
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 7 (Array, 2 elements)
 
 tid (String, 2 characters ) 28
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 8 (Array, 2 elements)
 
 tid (String, 2 characters ) 25
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 
 9 (Array, 2 elements)
 
 tid (String, 2 characters ) 26
 
 taxonomy_term (Object) stdClass
 
 ∞ (Recursion)
 - #formatter (String, 28 characters ) taxonomy_term_reference_link
 - 0 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 16 characters ) Police and Jails
 
 #href (String, 16 characters ) taxonomy/term/16
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 1 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 7 characters ) Poverty
 
 #href (String, 15 characters ) taxonomy/term/4
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 2 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 20 characters ) Protest / Resistance
 
 #href (String, 16 characters ) taxonomy/term/19
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 3 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 13 characters ) Miscellaneous
 
 #href (String, 16 characters ) taxonomy/term/10
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 4 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 22 characters ) Surveillance / Privacy
 
 #href (String, 16 characters ) taxonomy/term/32
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 5 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 22 characters ) Theory and Information
 
 #href (String, 16 characters ) taxonomy/term/37
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 6 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 18 characters ) Cultural Criticism
 
 #href (String, 16 characters ) taxonomy/term/35
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 7 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 20 characters ) Anti-racism / Racism
 
 #href (String, 16 characters ) taxonomy/term/28
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 8 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 11 characters ) Environment
 
 #href (String, 16 characters ) taxonomy/term/25
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
 - 9 (Array, 4 elements)
 
 #type (String, 4 characters ) link | (Callback) link();
 
 #title (String, 7 characters ) Economy
 
 #href (String, 16 characters ) taxonomy/term/26
 
 #options (Array, 3 elements)
 
 entity_type (String, 13 characters ) taxonomy_term
 
 entity (Object) stdClass
 
 ∞ (Recursion)
 
 attributes (Array, 3 elements)
 
 typeof (Array, 1 element)
 
 0 (String, 12 characters ) skos:Concept
 
 property (Array, 2 elements)
 
 0 (String, 10 characters ) rdfs:label
 
 1 (String, 14 characters ) skos:prefLabel
 
 datatype (String, 0 characters )
- field_drupalimc_author (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 0
 - #title (String, 6 characters ) Author
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 22 characters ) field_drupalimc_author
 - #field_type (String, 4 characters ) text
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 17 characters ) drupalimc_article
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 25 characters ) Robert D. Richardson III
 
 format (NULL)
 
 safe_value (String, 25 characters ) Robert D. Richardson III
 - #formatter (String, 24 characters ) drupalimc_article_author
 - 0 (Array, 3 elements)
 
 #prefix (String, 23 characters ) <div class="submitted">
 
 #suffix (String, 6 characters ) </div>
 
 #markup (String, 63 characters ) Submitted by Robert D. Richardson III on Thu, ...
 
 Submitted by Robert D. Richardson III on Thu, 2016-06-16 08:51
- #pre_render (Array, 1 element)
 - 0 (String, 30 characters ) _field_extra_fields_pre_render | (Callback) _field_extra_fields_pre_render();
- #entity_type (String, 4 characters ) node
- #bundle (String, 17 characters ) drupalimc_article
- links (Array, 5 elements)
 - #theme (String, 11 characters ) links__node
 - #pre_render (Array, 1 element)
 
 0 (String, 23 characters ) drupal_pre_render_links | (Callback) drupal_pre_render_links();
 - #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
 - node (Array, 3 elements)
 
 #theme (String, 17 characters ) links__node__node
 
 #links (Array, 9 elements)
 
 service-links-facebook (Array, 5 elements)
 
 title (String, 136 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/facebook.png" alt="Facebook logo" />
 
 href (String, 35 characters ) https://www.facebook.com/sharer.php
 
 query (Array, 2 elements)
 
 u (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 t (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 17 characters ) Share on Facebook
 
 class (Array, 1 element)
 
 0 (String, 22 characters ) service-links-facebook
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-google (Array, 5 elements)
 
 title (String, 132 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/google.png" alt="Google logo" />
 
 href (String, 37 characters ) https://www.google.com/bookmarks/mark
 
 query (Array, 3 elements)
 
 op (String, 3 characters ) add
 
 bkmk (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 28 characters ) Bookmark this post on Google
 
 class (Array, 1 element)
 
 0 (String, 20 characters ) service-links-google
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-identica (Array, 5 elements)
 
 title (String, 137 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/identica.png" alt="identi.ca logo" />
 
 href (String, 18 characters ) https://identi.ca/
 
 query (Array, 2 elements)
 
 action (String, 9 characters ) newnotice
 
 status_textarea (String, 110 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy http://rochester.indymedia.org/node/147495
 
 attributes (Array, 3 elements)
 
 title (String, 22 characters ) Dent this on identi.ca
 
 class (Array, 1 element)
 
 0 (String, 22 characters ) service-links-identica
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-twitter (Array, 5 elements)
 
 title (String, 134 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/twitter.png" alt="Twitter logo" />
 
 href (String, 25 characters ) https://twitter.com/share
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 text (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 21 characters ) Share this on Twitter
 
 class (Array, 1 element)
 
 0 (String, 21 characters ) service-links-twitter
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-digg (Array, 5 elements)
 
 title (String, 128 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/digg.png" alt="Digg logo" />
 
 href (String, 22 characters ) http://digg.com/submit
 
 query (Array, 3 elements)
 
 phase (String, 1 characters ) 2
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 26 characters ) Digg this post on digg.com
 
 class (Array, 1 element)
 
 0 (String, 18 characters ) service-links-digg
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-delicious (Array, 5 elements)
 
 title (String, 140 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/delicious.png" alt="del.icio.us logo" />
 
 href (String, 23 characters ) http://del.icio.us/post
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 33 characters ) Bookmark this post on del.icio.us
 
 class (Array, 1 element)
 
 0 (String, 23 characters ) service-links-delicious
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-reddit (Array, 5 elements)
 
 title (String, 132 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/reddit.png" alt="Reddit logo" />
 
 href (String, 25 characters ) https://reddit.com/submit
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 30 characters ) Submit this post on reddit.com
 
 class (Array, 1 element)
 
 0 (String, 20 characters ) service-links-reddit
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-stumbleupon (Array, 5 elements)
 
 title (String, 140 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/stumbleit.png" alt="StumbleUpon logo" />
 
 href (String, 33 characters ) http://www.stumbleupon.com/submit
 
 query (Array, 2 elements)
 
 url (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 title (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 28 characters ) Thumb this up at StumbleUpon
 
 class (Array, 1 element)
 
 0 (String, 25 characters ) service-links-stumbleupon
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 service-links-yahoo (Array, 5 elements)
 
 title (String, 130 characters ) <img typeof="foaf:Image" src="http://rochester....
 
 <img typeof="foaf:Image" src="http://rochester.indymedia.org/sites/all/modules/service_links/images/yahoo.png" alt="Yahoo logo" />
 
 href (String, 49 characters ) https://bookmarks.yahoo.com/myresults/bookmarklet
 
 query (Array, 2 elements)
 
 u (String, 42 characters ) http://rochester.indymedia.org/node/147495
 
 t (String, 67 characters ) Public Health or Profit? The Rochester Red Ligh...
 
 Public Health or Profit? The Rochester Red Light Camera Controversy
 
 attributes (Array, 3 elements)
 
 title (String, 27 characters ) Bookmark this post on Yahoo
 
 class (Array, 1 element)
 
 0 (String, 19 characters ) service-links-yahoo
 
 rel (String, 8 characters ) nofollow
 
 html (Boolean) TRUE
 
 #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
 - comment (Array, 3 elements)
 
 #theme (String, 20 characters ) links__node__comment
 
 #links (Array, 1 element)
 
 comment_forbidden (Array, 2 elements)
 
 title (String, 168 characters ) <a href="/user/login?destination=node/147495%23...
 
 <a href="/user/login?destination=node/147495%23comment-form">Log in</a> or <a href="/user/register?destination=node/147495%23comment-form">register</a> to post comments
 
 html (Boolean) TRUE
 
 #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
- comments (Array, 0 elements)
- #view_mode (String, 4 characters ) full
- #theme (String, 4 characters ) node
- #node (Object) stdClass
 - ∞ (Recursion)
- #language (String, 2 characters ) en
Krumo version 0.2.1a
| http://krumo.sourceforge.net
Called from /home/members/rochindymedia/sites/rochester.indymedia.org/web/includes/menu.inc, line 527

Upcoming Events

Public Health or Profit? The Rochester Red Light Camera Controversy

Primary tabs

Secondary tabs

Krumo version 0.2.1a

Local News

Recent Comments

Syndication

Account Creation Policy Change

Editorial Meeting Times / Locations

Upcoming Events

Public Health or Profit? The Rochester Red Light Camera Controversy

Primary tabs

Secondary tabs

Krumo version 0.2.1a

Search form

Local News

Recent Comments

Syndication

Account Creation Policy Change

Editorial Meeting Times / Locations