There's a community of us who are playing around with using OpenStreetMap as a venues database for checking into our own sites as part of the "indie web" movement.
We have a page about it on the indieweb camp wiki: http://indiewebcamp.com/checkin I've got a few checkin posts on my own site that are drawn from OpenStreetMap data: http://tommorris.org/posts/8073 http://tommorris.org/posts/8074 http://tommorris.org/posts/8381 http://tommorris.org/posts/8135 I'm using Cloudmade's API per the recommendation here - http://stackoverflow.com/questions/1384397/search-within-distance-api-for-openstreetmap I'm in the middle of writing a long post about how to use MongoDB to make a super-quick venues database using OpenStreetMap data, which is something I was working on last week. I'll post it to this list when it's written and published. It'd be lovely if Overpass supported the type of query that would make this kind of venue checkin thing easy for those of us who are just individuals rather than having the resources of one of the OSM reusers. I've requested as much here - https://wiki.openstreetmap.org/wiki/Talk:Overpass_API#Wishlist:_nearest_n_objects_that_satisfy_predicate_to_point The great thing about enabling this kind of service on top of OSM is that it'd expose more of the underlying metadata of OSM to the public who could then find and hopefully fix bugs with the data. Currently, if, say, the opening_hours of a bar aren't correct, we probably won't find out. Finding ways of surfacing and exposing that data means that we'll have more eyes to find problems with it. -- Tom Morris http://tommorris.org/ On 10 July 2013 at 18:15:47, Paul Johnson ([email protected]) wrote: https://support.google.com/gmm/answer/3001634?p=maps_android_latitude&rd=1 Thinking it might be time for an OpenStreetMap based Latitude alternative now that Latitude ie going away next month. _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
