e dot dot dot
a mostly about the Internet blog by

October 2019
Sun Mon Tue Wed Thu Fri Sat
   
   


Why Navigation Apps, Working Properly, Can Make Traffic Flows Worse -- And What To Do About It

Furnished content.


Techdirt has just written about how advanced digital technology can be used for less-than-benign purposes, simply because it is a tool that can be applied in both good and bad ways. A fascinating analysis by Jane Macfarlane in IEEE Spectrum explores something similar: how new technology being used as designed, and with only the best intentions, can nonetheless give rise to potentially serious problems. The article is about how the increasingly-popular navigation apps like Waze, Apple Maps, and Google Maps are "causing chaos":

City planners around the world have predicted traffic on the basis of residential density, anticipating that a certain amount of real-time changes will be necessary in particular circumstances. To handle those changes, they have installed tools like stoplights and metering lights, embedded loop sensors, variable message signs, radio transmissions, and dial-in messaging systems. For particularly tricky situations -- an obstruction, event, or emergency -- city managers sometimes dispatch a human being to direct traffic.But now online navigation apps are in charge, and they're causing more problems than they solve. The apps are typically optimized to keep an individual driver's travel time as short as possible; they don't care whether the residential streets can absorb the traffic or whether motorists who show up in unexpected places may compromise safety.
One of the problems is that navigation apps use fairly crude models when working out the best routes. Often, they fail to take into account local details. Macfarlane's article mentions things like extremely steep inclines, and roads where schools are located or that have a larger-than-usual number of pedestrians milling around. Another issue is that navigation apps are selfish -- they don't care if they cause knock-on problems for other drivers elsewhere:
Consider cars crossing a thoroughfare without the benefit of a signal light. Perhaps the car on the smaller road has a stop sign. Likely, it was designed as a two-way stop because traffic on the larger road was typically light enough that the wait to cross was comfortably short. Add cars to that larger road, however, and breaks in the traffic become few, causing the line of cars waiting at the stop sign to flow onto neighboring streets. If you're in the car on the larger road, you may be zipping along to your destination. But if you're on the smaller road, you may have to wait a very long time to cross. And if the apps direct more and more cars to these neighborhood roads, as may happen when a nearby highway is experiencing abnormal delays, the backups build and the likelihood of accidents increases.
Things are made worse because rival services not only don't share traffic data with each other -- leading to incomplete knowledge of flows, and sub-optimal route recommendations -- they also don't share their data with city transportation engineers who are trying to optimize traffic flows and minimize danger for everyone. That's a big problem because the older models used by the authorities to keep everyone safe made assumptions about road use that was based on static factors like nearby population density. Those no longer hold when navigation apps introduce new dynamics -- for example, by sending lots of traffic down residential streets that are normally quiet. Transportation engineers may therefore make decisions about traffic control based on erroneous assumptions that exacerbate problems, rather than relieve them. As MacFarlane points out, these knock-on effects of navigation apps have led neighborhoods and citizens to fight back against the unexpected and unwanted traffic flows:
In the early days of the problem, around 2014, residents would try to fool the applications into believing there were accidents tying up traffic in their neighborhood by logging fake incidents into the app. Then some neighborhoods convinced their towns to install speed bumps, slowing down the traffic and giving a route a longer base travel time.A town in New Jersey, Leonia, simply closed many of its streets to through traffic during commute hours, levying heavy fines for nonresident drivers. Neighboring towns followed suit. And all faced the unintended consequence of their local businesses now losing customers who couldn't get through the town at those hours.
These are clearly unsatisfactory ways of addressing the new problems otherwise benign navigation apps are causing. As the article notes, the way forward is for all the services in this sector to share their information with each other, and with city governments. This would provide more accurate data, and allow optimal routes to be calculated for everyone. Crucially, it would allow city transportation engineers to work with navigation apps, rather than trying to respond to the barely-understood patterns they cause.Of course, there are important privacy issues that must be addressed. This could be achieved by combining individual data points into aggregated flows, perhaps with some obfuscating random elements added as well. Another issue is that larger navigation services might be unwilling to share their data with smaller rivals. One incentive for them is that doing so would be zero-cost way to improve the outcome for their users, not least by allowing better overall coordination. Another is that big Internet services are already being portrayed as greedy and selfish by many. Helping to create a traffic data commons for the public good would not only make them popular with their users, but would also provide them with some respite from their critics.Follow me @glynmoody on Twitter, Diaspora, or Mastodon.

Permalink | Comments | Email This Story


Read more here

posted at: 12:00am on 08-Oct-2019
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



Appeals Court Denies Qualified Immunity For Transit Cop Who Arrested A Journalist For Taking Pictures Of EMS Personnel

Furnished content.


Last year, a federal court offered its sympathies -- but only limited recourse -- to a photographer who suffered a bogus "stop photographing us" arrest at the hands of a Dallas Area Rapid Transit (DART) cop.Avi Adelman, a freelance journalist, was photographing EMS personnel responding to an apparent overdose. DART officer Stephanie Branch decided this just wouldn't do. She approached Adelman and got between him and the scene he was photographing. The officer then started laying down bullshit about "establishing a perimeter" and how his documentation was violating the HIPAA rights of person being attended to.(If this crap about "HIPAA violations" sounds familiar, it's because law enforcement officers either don't understand how HIPAA works or they hope the person whose Constitutional rights they're violating doesn't understand how HIPAA works. This was the same excuse used by a Denver cop to detain a journalist who was recording the apparent arrest of a naked mentally-ill person in the middle of a public street. Just in case there are any cops lurking here, HIPAA violations occur when someone releases private medical info to unauthorized parties. It never happens when someone is suffering a medical emergency in a public area.)Back to the DART case: despite Officer Branch including twenty-three false or inaccurate statements in her account of the arrest, she managed to dodge being directly held responsible for her violation of Adelman's First Amendment rights. Since the Fifth Circuit didn't clearly establish a right to record public servants until 2017, Adelman's 2016 arrest happened too soon for him to use that precedent to pierce Branch's qualified immunity. But Officer Branch was still on the hook for the Fourth Amendment violation. She appealed, but going up a level hasn't changed anything for the officer.On appeal, the Fifth Circuit has upheld the lower court's decision, preventing Branch from eluding responsibility for violating Adelman's Fourth Amendment rights. Branch claimed she was unaware of the photography policy DART had put in place in 2014, which expressly permitted the actions Adelman was engaged in when Branch decided to arrest him.But Officer Branch's actions were so obviously unreasonable, another officer and an EMT had this conversation while Branch was hassling the journalist. From the decision [PDF]:

DFR 1 – He was just taking pictures right?
Officer Cannon – Yea[h] that’s why I don’t know why she’s giving him a hard time[.]
DFR-1 – Why is she going crazy?
Officer Cannon – I don’t know[,] that’s going to be on her[.] [H]e can take all the pictures he wants[,] that’s why I’m not getting involved in that. . . .
DFR-1 – He knows he wasn’t doing nothing wrong so. . .
Officer Cannon – I don’t know why she . . . . There was no need for that[.]
DFR-2 – Yea[h] I don’t know where that idea came from but this is . . . because there is freedom of the press[.]
Her own agency came to this conclusion after an internal investigation:
“Adelman was not breaking any laws and would not lead a reasonable person to believe that he was committing a crime or had committed a crime or [was] about to engage in committing a crime. . . . [T]herefore the arrest of Adelman for criminal trespass was not based on sufficient probable cause.”
It also had this to say about Branch's actions:
“The evidence indicates that Officer Branch did violate the DART Administrative Employment Manual and did not refrain from activity which was illegal or could reflect negatively on DART when she made various inconsistent or mistaken statements on her DART Police [I]ncident Report . . . and made the arrest of Avi Adelman for criminal trespass.”
The court points out in a footnote that even if Branch was not present when the 2014 policy permitting photography was instituted, this failure to familiarize herself with DART policies is on her.
Branch asserts that she was reasonable in believing she had authority to order Adelman to leave because she was on sick leave when DART implemented the new Photography Policy that permits the public to take photos on DART property. [Branch was on sick leave from May 2014-January 2016. The policy was enacted June 2014.] The old policy apparently would have prohibited Adelman from being on DART property if he wasn’t using it for “transportation purposes.”[...]But Branch’s mistake was not reasonable. She didn’t misinterpret an unclear policy or law; she simply failed to learn about DART’s updated policy. And “an officer can gain no Fourth Amendment advantage through a sloppy study of the laws [s]he is duty-bound to enforce.” Heien, 135 S. Ct. at 539–40.
The case now goes back to the lower court where it seems likely Officer Branch won't be able to talk a jury into siding with her should the litigation reach that point. The established right to photograph public servants came along a little bit too late to help Adelman on his First Amendment claims, but at least he can still go after Branch for her bogus arrest and the night he spent in jail.

Permalink | Comments | Email This Story


Read more here

posted at: 12:00am on 08-Oct-2019
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



October 2019
Sun Mon Tue Wed Thu Fri Sat
   
   







RSS (site)  RSS (path)

ATOM (site)  ATOM (path)

Categories
 - blog home

 - Announcements  (0)
 - Annoyances  (0)
 - Career_Advice  (0)
 - Domains  (0)
 - Downloads  (3)
 - Ecommerce  (0)
 - Fitness  (0)
 - Home_and_Garden  (0)
     - Cooking  (0)
     - Tools  (0)
 - Humor  (0)
 - Notices  (0)
 - Observations  (1)
 - Oddities  (2)
 - Online_Marketing  (0)
     - Affiliates  (1)
     - Merchants  (1)
 - Policy  (3743)
 - Programming  (0)
     - Bookmarklets  (1)
     - Browsers  (1)
     - DHTML  (0)
     - Javascript  (3)
     - PHP  (0)
     - PayPal  (1)
     - Perl  (37)
          - blosxom  (0)
     - Unidata_Universe  (22)
 - Random_Advice  (1)
 - Reading  (0)
     - Books  (0)
     - Ebooks  (0)
     - Magazines  (0)
     - Online_Articles  (5)
 - Resume_or_CV  (1)
 - Reviews  (2)
 - Rhode_Island_USA  (0)
     - Providence  (1)
 - Shop  (0)
 - Sports  (0)
     - Football  (0)
          - Cowboys  (0)
          - Patriots  (0)
     - Futbol  (0)
          - The_Rest  (0)
          - USA  (0)
 - Technology  (1192)
 - Windows  (1)
 - Woodworking  (0)


Archives
 -2024  April  (128)
 -2024  March  (179)
 -2024  February  (168)
 -2024  January  (146)
 -2023  December  (140)
 -2023  November  (174)
 -2023  October  (156)
 -2023  September  (161)
 -2023  August  (49)
 -2023  July  (40)
 -2023  June  (44)
 -2023  May  (45)
 -2023  April  (45)
 -2023  March  (53)


My Sites

 - Millennium3Publishing.com

 - SponsorWorks.net

 - ListBug.com

 - TextEx.net

 - FindAdsHere.com

 - VisitLater.com