Hampton Road Transit published real time bus data in a text format:
ftp://216.54.15.3/Anrd/hrtrtf.txt

This data needs to be transformed into GTFS-realtime so that any app that understands GTFS will be able to use it. Google Maps is one application that can use GTFS-realtime and there are many others.

I can connect you to Code for America Fellows and other civic hackers who have direct experience transforming the data formats like the one published by HRT into useful map and text messaging applications that riders need to make using the region's bus system more user friendly.

For background, see the CityCampHRVA blog about HRVA Hack Fest:
http://citycamphrva.govfresh.com/2012/03/25/recap-of-hrva-civic-hackfest/

@joannecheng

@synchronouscity a very simple http api for active street closures:

secret-gorge-2345.herokuapp.com/closures

https://github.com/jc-2/denver_streets
If public works maintains a structured data base of work sites & closures that data can be published through an API. Mobile app developers can take the data and do things with it like create mobile optimized maps, alerting services and routing services that are useful to everyone: Public Works field staff, other city workers in the field, planners, commuters, visitors...

It could start by just asking them for this kind of data.

Part of your mobile strategy should be to encourage departments to collaborate with data publishing efforts so that the mobile app ecosystem can be enabled. That's really the win story of the HRT Bus API & App. HRT published the raw data and stopped there. By pursuing the publishing of structured data through web & mobile accessible URIs & APIs you set up greater likelihood of app fulfillment. This is because more people can attack the problem from more customer service/audience perspectives at once. Vendors will be attracted to open data end points. A perfect example is restaurant inspections data. If you publish LIVES data then Yelp & Google will pick it up. Boom: mobile restaurant inspection data (CC our friend at Conventions & Visitors).

A mobile app that consumers can use at the Point of Sale to check the Animal and Plant Health Inspection Service (APHIS) record of the provider. For example, a shopper at a pet store wants to buy a parrot. She asks the cashier for the USDA license of the provider, which is available at any pet store and is legal to provide. Any reputable seller will make this available to their customer. The shopper enters the number, say 48-A-2069 and the query returns a count of all non compliance issues....or returns a 'No Non-Compliance issues found' message. If a count is returned the user is able to drill into the items so as to determine if there is a cause for concern in purchasing the bird. This app would help consumers, reputable breeders, APHIS inspectors, pet stores and of course the animals who are protected by the Animal Welfare Act.

The database is almost complete. It could no doubt benefit from a good hard look by some other DB savvy folks. The interface should be ADA compliant (The APHIS Search tools are not currently in compliance). A simple input box and a button with a format check sends the query. The results needn't be fancy. Just fresh, easy to get to and easily digestible...like any self-respecting taco stand. The data should go back ten years but that's ultimately up to the USDA I guess. I have details on the data elements that would be needed to provide an fair and responsible view of the information.