Open Government & Geolocation: Building a Mobile, Location-Based Search for AIDS.gov
1. Sex::Tech 2011 San Francisco, CA Mindy Nichamin AIDS.gov New Media Coordinator Jennie Anderson AIDS.gov Communications Director John Snow, Inc. (JSI) Open Government & Geolocation: Building a Mobile, Location-Based Search for AIDS.gov
AIDS.gov Intro One of the projects I work on is the AIDS.gov web site.
From Morgan Stanley Around 2013, mobile users will surpass desktop internet users (mobile includes email and apps) ***IF YOU ARE NOT DOING SOMETHING WITH MOBILE NOW, YOU’LL NEED TO BE
Find out where you are Find you what’s near you Let other people know you’re here
SMS = lowest common denominator Most phones sold today have a browser Platform specific = drawback
SMS = lowest common denominator Most phones sold today have a browser Platform specific = drawback
Doesn’t include content +marketing +promotion
Touch
New functionality –geolocation request Either/or – entering zip
(permission)
As part of that project, we created a location based search tool to help people living with HIV/AIDS or their caretakers to find service providers near them. Been a trip Might have something useful to share
So, first, let’s look at the problem we wanted to solve. No central repository for them -would have to visit 5 separate websites -websites don’t feature map view
Some are many layers deep in the agency’s hierarchy Finding agency websites is hard Not recognizable URLs
Here is an example URL for the CDC HIV Testing data feed API. It takes a ZIP Code and a distance in miles, and returns… Representation of interface
The crucial bit that makes this GeoRSS is each <entry> element brings along a latitude and longitude with it. RSS Feed Title Author ID Longitude/latitude
So they can be plopped on the map like so. The Google Maps API actually offers a GeoRSS parser, but I found it rather finicky so ended up rolling my own. [anecdote] -issues while implementing -wrote our initial how-to on GeoRSS -made point data, the latitude and longitude, optional. -Bad idea. We were afraid making it mandatory would be a barrier to entry for some agencies We thought it would be simple enough to geocode the addresses on our end. Most of agencies already had geocoded data, or were pretty quick to do so, even though we’d made it optional. one data provider called our bluff Delays between us trying to dynamically geocode and giving up and them adding lat and long on their end. We are not maintaining data ourselves – it’s the most recent Not just enough to make this something at AIDS.gov, but we’re not the only resource out there Someone at risk may not know AIDS.gov but has widget access
Not only did we want to give people one place to search, we wanted to make that tool available anywhere. For people who haven’t heard of AIDS.gov = widget
This is a pure JavaScript widget, which can be placed in a page with a single line of HTML.
A vertical version,
We now are using Omniture through an arrangement with CDC in order to get metrics on the widget. This is more or less out of convenience, it wouldn’t be my preference, also it takes major bank. Also, we’re using Google Analytics on locator.aids.gov itself.
Widget – how many people loaded a page with the widget National HIV Testing Day we created a special look for the locator widgets Asked partners to place the widget on their web sites. loaded ~1.6 million times Meaningless Doesn’t even mean eyeballs (below the fold)
In a year…as of 3/6/11 1600-2000 searches/month of those 1.6 million loads 2000 real searches. Measured by interactions on the widget and GA on locator.aids.gov
Embedded on 70 different websites many of those including the widget on several, or all, pages.
… yet you can’t find my clinic Feedback mechanism
We want to be responsive We can reach out to owners of data to edit info
Atomic release easy rollback, scripts “ Perfection is the enemy of good