Most of the stuff in that dataset has apis you can use live. They sent notification that they were turning off citysearch towards the end of this year and beginning of next year. The api behind citysearch was the only way I know that an individual could keep a categorized list of places like bars and restaurants under control. I would take their api and convert it to kml to build my own google map of places without all the google ad crap. As well as having a full featured api it would also mark places as closed so your lists could autoremove the old places and you could sometimes find what took over the location. I would also subcategorize places into favorites, new and notable, hidden places, types of bars, etc….

I will miss Foursquare citysearch and its predecessor, a little palmos app known as Vindigo. Google and yelp let you tag places in their apps but don’t have as good of api, so going forward it will be hard to maintain a private list of places that can be categorized, rendered, filtered, maintained, and exported. Google and yelp largely keep your poi info captive.

The angle I can think of is to preserve the legacy of a dwindling operation and share the value that was created at the peak.

90% of Foursquares revenue comes from Enterprise clients. This dataset would not cannibalize that revenue, but it would provide the general population by fixing bugs and finding new use-cases that might put them in a better spot when competing with Google Maps, Yelp, and Facebook Places.