We've tried to define actual boundaries for the neighborhoods making up the places we call home. We carved Douglas County into nearly 90 neighborhood areas - usually bigger than a single subdivision and smaller than a ZIP code.
The concept is simple: Pass a latitude and longitude, and you get the neighborhood name and some basic stats describing it. Ship a lat/long pair like so:
If that location exists in one of our neighborhoods, you'll get a result. If not, well, you're probably on your own, as we didn't add much by way of helpful errors.
<NeighborhoodResponse> <status>OK</status> - <result> <hoodname>Dundee South (Elmwood Park)</hoodname> - <censusinfo> <total2010>5162<total2010> <total2000>5488</total2000> <white>4574</white> <black>72</black> <hispanic>190</hispanic> <other>326</other> <kids>2651</kids> <kidpct>19.2</kidpct> </censusinfo> </result> </NeighborhoodResponse>
|total2010||The total Census 2010 population|
|total2000||The total Census 2000 population|
|white||The total number of whites, Census 2010|
|black||The total number of blacks, Census 2010|
|hispanic||The total number of hispanics, Census 2010|
|other||The total in other races, Census 2010. Includes Asian, Native American, Pacific Islander and "Other"|
|kids||The total number of residents under 18, Census 2010|
|kidpct||The percent of the population that is under 18, Census 2010|
Building this API (automated programming interface) was an afterthought. We figured developers or fellow stat fans might enjoy it. Given the limited audience, we have left it simple and unassuming. For now.
We'd love to hear what you think of it. So if you use it, tell us. Show us what you've done with it, and let a thousand Omaha-area geoservices bloom.