|
|
|
|
|
|
by matthewjames
4108 days ago
|
|
|
That is a great idea, but by crowdsourcing I assume you mean the end-users reporting the accident, the work zone, etc. correct? I love that idea and it is a old/tested one, but from a safety perspective do we want people touching their phones while driving to report the location? If they wait till they reach their destination to report, the accident may be cleaned up or the exact location data of the work zone may become inaccurate. Also, who would be in charge of removing that data, checking if an accident is gone, etc? Just some random questions I am throwing out there. I was going more for a very cheap 3G/4G-enabled device to broadcast live to a "City API". Thoughts? |
|
|
Yes, that's what I mean by crowdsourced data. I agree on the safety concerns while driving. However, even if you could collect data on emotions of people throughout the day in a city... that would be insanely useful for planners... aka knowing when people are angry sitting in traffic, scared in sketchy areas of the city, or where they go for walks often because it's a beautiful park. They can analyze all that data to plan smarter cities. The issue here is: how do you engage the "crowd" enough for them to share this data?
Yes the city API idea is definitely cool. With all the data opening up it's good timing for sure... Only thing is, I heard the API aren't exactly perfect. Depends on what you are working on. I met with a Founder of a Parking App that was building on data like you are talking about.