I suggest you ...

API or data feed of road closings and construction (do these already exist, does google get them?)

@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).

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Bret FisherBret Fisher shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base