For the city of Los Angeles, I would love an API that takes a street address and an array of options and returns the street parking restrictions that apply. There are lots of places with confusing signage (e.g. http://www.wreckedmagazine.com/images/joeyredmond/typicalpar...), and it would be nice to get a boolean response to the question "Can I park here now?"
My god I would love that. Can it have a guarantee that you won't get a parking ticket? Just kidding.
That said with a tool like that wouldn't the # of parking tickets issue by any city go down and thus they would have an incentive not to allow such a tool to be widely deployed?
I swear that parking signs are deliberately put up to confuse people so they can get more revenue!
Well, according to their mission statement, their goal is not to generate revenue, but "to ensure transportation routes in Los Angeles flow safely and are not blocked" (http://ladot.lacity.org/tf_Parking_Enforcement.htm)
Of course we know the real reason is $$$. But if we take them at their word, providing access to this data would help them achieve their goal by helping motorists park properly and legally.
Agreed; having something like this tied to your GPS would be a great service. It would also be useful to quickly know the time the spot becomes illegal again.
I can imagine, too, this would be incredibly useful if self-driving cars ever become a reality (or in helping them become a reality). After one drops you off at the show downtown, it could then check for nearby parking. But maybe this is dreaming too far down the road...
The answer was not "no", it was "We won't discuss the private details of a client's (the municipal government) system, please contact the client directly."
Original Text
"We value our relationship with our clients and are committed to protecting their privacy and security protocols. I have shared your request with the town and would direct you to the Town of Watertown for information regarding your request."
And this is a proper response from the vendor. The vendor should not attempt to get involved with political decisions about what should be available and what should not be available. They honor their contract, they stay out of trouble.
If the town officially holds the position that the information is "non-public" or "secret," then you go to the courts, not to the vendor.
Now, if the town agrees and goes to the vendor and the vendor says "no" or "that'll be a 10x increase in fees," it becomes the town's responsibility to find a compliant vendor.
It's a slow process, for sure. It's difficult to even explain the utility of an API to the non tech-savvy until you show them an app that uses the data.
I live in NYC and they're doing a great job- but change isn't immediate. I'm really interested in the area of governmental data- I feel like there's a need/use for an open wiki style directory of info, but http://opengovernmentdata.org/ is already a good resource.
I agree that it's a slow process, but it's happening. At the city level, it's good to have someone within the Mayor's office or City Council that really cares about it. It's starting to happen here in Philly with http://www.opendataphilly.org
The worst part of that isn't that they don't know how to set up their own technology - it's that they get sold on whatever snake oil salesman takes them out to the most dinners, and overpromises the most while keeping it plausible.
I've wanted to do something similar except with Real Estate transaction data in the state of MA. Most residential real estate transaction data is available via each counties registry of deeds website (http://www.masslandrecords.com/malr/controller). The challenge is much of this data is stored using proprietary systems with limited (or no) APIs and different counties use different systems.
Much like with Real Estate data, the biggest hurdle with this initiative is there is no standardized convention from one city to another. With data being all over the place it makes developing a community driven data gathering platform "wicked hard". What I think would be a good starting point is define some standards so that when the ad-hoc data is transformed it follows an agreed upon convention. This approach would allow for a centralized data sharing platform to be developed making data available via all kinds of different formats(RDF,JSON, etc).
tl;dr: Awesome idea but comes with some difficult challenges.
I did this, but for a specific city service in Madison, WI. I built an API for the Madison Metro bus service that provides a nice web service for developers, but does ugly screen scraping behind the scenes.
Max Ogden (a fellow at Code for America) has been working on a site to help turn Excel spreadsheets and CSV files into usable JSON APIs for developers. You should check out datacouch.com — might be of interest.