Hacker News new | past | comments | ask | show | jobs | submit login

Does FedEx/UPS have to share package pickup/dropoff data with local governments?

After all, it is a direct competitor to the US Postal Service.




Medallion taxi services in NY have to share pick up and drop off data with NYC's government. Even though each of those cars are privately owned and operated. In NYC, Uber drivers are all required to have taxi licenses. It seems reasonable that a private medallion-competitor should have to share the same information that the private medallion-owners do.


Why? Uber drives aren't using the medallion.


Uber operates in NYC under the City's Taxi and Limousine Commission. No medallion, but drivers and vehicles must be registered to the TLC in order to legally operate.


Except taxi services don't (usually) track detailed GPS info on where they picked me up and dropped me off. Further, if I pay with cash and don't break their rules, they don't know/care who I am.


We're talking about NYC where taxis DO record this information.


"Taxis already share all the data the commission is requesting from Uber."

I think that's the key detail


If the argument really boils down to "everyone else is doing it" or "that's what we've always done!" they should stop and apply some critical thinking.


"everyone else is following city regulations"


Taxis accepted a lot of obtrusive regulations because they were granted a monopoly by the city. I don't see why Uber should obey these regulations when they are not getting any such sweetheart deals.


Who is the monopoly here? Anybody is free to buy a medallion and own a yellow cab.

Besides yellow cabs there are also private livery cabs aka "black cars/car service."

"CURRENT OWNERSHIP: 17 percent of medallions are owned by cab fleets; 54 percent are owned by leasing agents, who delegate management to fleets; and 29 percent are owned by independent drivers"

http://nymag.com/nymetro/urban/features/taxi/n_10292/


Great point but there are some legitimate reasons that the city may want ride data especially if Uber wants to replace multiple forms of transportation (taxis, personal vehicles, frieght delivery, ride services for the elderly/disabled etc).

There are also other municipal needs like collecting utility information from radio systems or pavement management surveys that cities often drive around to collect - Uber could potentially be utilized for data gathering if it was determined that they had sufficient coverage etc.

Every GIS nerd would love a data set like the Uber tracks for analysis and to see what else they could be used for (Uber for mass license plate collection is like something from Black Mirror).


This data could be extremely helpful to planning out public transportation. You would be able to determine the most common areas people go to, where they come from, when they typically go there, etc. All would help in planning bus routes/subway lines/etc.


Thus improving public transport and make people less dependent on Uber :)


They're not in competition with one another. Together they are both in competition with privately owned cars. A transportation system effective enough to compel people to give their cars up is good for both of them. Uber alone is too expensive, and public transit alone can't provide service everywhere all the time cost effectively.


If the city wants to contract with Uber (or FedEx or UPS or...) to do pavement management surveys, that could be an interesting conversation. But that's not what the city is asking for or has proposed.

Instead of imagining uses for their data, let's realize it's their data that we have individually given them and we may not want the city - any city - to have.

Remember Uber's (terrible) "Rides of Glory" post describing how they could detect hooksups - http://www.whosdrivingyou.org/blog/ubers-deleted-rides-of-gl... ?

Now imagine that in your local government's hands.


>Every GIS nerd would love a data set like the Uber tracks for analysis

The same argument can be made about Facebook's data. I don't think that justifies making it public.


For sure. I wasn't implying it should be released to everyone.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: