Over the weekend I made another map. While I don't think for one moment this one will be as wildly popular as my last map was, this one is just as satisfying and a whole lot more personal.

At 8.01 PM on the 11th. of October 2009 I checked into Sushi Tomi in Mountain View, California. This was my very first Foursquare check-in. Since then I've checked-in on this particular location based service a further 12,394 times. Each check-in has been at a place I've visited. As this is a location based service, each check-in comes with a longitude and latitude.

This sounded to me like an ideal candidate for a map. But how to go about making one?

Today I contributed to a map. I did this yesterday as well. I even did this last week. In fact I've been doing this since the end of July 2009. As of right now I've done this 11,880 times. I'll probably end up contributing to this map again later on today and will almost definitely do it again tomorrow.

But this isn't your average user contributed or crowd sourced map. It's not one of the usual suspects; it's not OpenStreetMap, or Google MapMaker or Nokia MapCreator. It's none of these, but it's a map nonetheless and it looks like this.

Warning. This post contains a sweeping generalisation. Yes, I know that Places are not just part of today's digital maps; see the James Fee and Tyler Bell hangout The One Where Tyler Bell Defines Big Data as a proof point. But for the sake of this post, just assume that Places and maps are synonymous.

It's never been easier to make a map. Correction. It's never been easier to contribute to a map. Today we seem to be makingcontributing to maps everywhere, even underground, or should I say Underground?

To makecontribute to a map, you used to have to be a professional map maker, with easy access to an arsenal of surveying or an industrial grade GPS.

Maps and map imagery seem to be back in the news. Google's recent map update and immense speculation about Apple's "will they, won't they" replacement for the current Google Maps app on iOS seems to be spilling over from the usual tech media into mainstream news.

Firstly, the UK's Daily Telegraph, a "quality broadsheet" seems to have just discovered that today's digital maps also have satellite imagery. It's not entirely clear how this is news, let alone current news. Navteq has had satellite imagery as part of its' maps since the mid 1980's and Google has also included satellite imagery in Google Maps since the mid 2000's. But linked to Apple's recent acquisition of 3D imagery specialists C3, we're told to anticipate a "private fleet of aeroplanes equipped with military standard cameras to produce 3D maps so accurate they could film people in their homes through skylights". The middle market tabloid Daily Mail has also picked up on this story, running with the headline "Spies in the sky that no one will regulate".

With the benefit of hindsight, it was probably inevitable but 5 years after the location based, check in social network we know as Gowalla launched and 3 months after they were acquired by Facebook, Gowalla is no more.

Despite launching in 2007, 2 years prior to Foursquare, Gowalla never seemed to be able to capture attention from either users or from the media in quite the same way as Foursquare. The similarities were many; both social networks used location as a key facet, allowed users to check in to locations they were at or near and to share those locations with other users and other social networks. But while Foursquare's game mechanics of badges and Mayors seemed to hit the right note with users, Gowalla's ill explained and ever morphing system of virtual items, spots and trips never seemed to make sense. No-one I've ever spoken to could explain exactly what the point of Gowalla was, whilst Foursquare's mechanics were simplistic and easy to grasp.

After loosing ground to Foursquare, Gowalla tried to act less as a sole source of checkins and more as a central aggregator of the disparate checkins from itself, Foursquare, Facebook and Twitter, amongst others, but this move did little to slow Foursquare's ascendancy.

In web and location circles, much has been made of Foursquare's recent "little announcement" of the location based, check-in, company's decision to oust Google Maps and instead to go with OpenStreetMap data, by way of MapBox.

From reading a lot of the coverage you'd be forgiven for thinking that Foursquare has completely severed ties with Google's mapping APIs, but this isn't quite the story. As ReadWriteWeb notes in the last paragraph of its coverage, "Foursquare's iPhone and Android apps won't be affected" as the move is for Foursquare's home on the web, foursquare.com, only.

In my recent talk to the British Computer Society's Geospatial Specialist Group, I touched on the "race to own the Place Space". While the more traditional geographic data providers, such as Navteq and Tele Atlas are working away adding Points Of Interest to their data sets, it's the smaller, social location startups, that are getting the most attention and media coverage. With their apps running on smartphone hardware, Foursquare, Gowalla and Facebook Places, amongst others, are using crowd sourcing techniques to build a large data set of their own.

For them to do this, the barriers to entry have to be very low. Ask a user for too much information and you'll substantially reduce the number of Places that get created; and thereby hangs the biggest challenge for these data sets. Both the companies and their users want the Holy Grail of data, quantity and quality. But the lower the barriers to entry, the more quality suffers, unless there's a dedicated attempt to manage and clean up the resultant data set.

Back in March of this year I wrote about deliberately tracking my journey by using Google's Latitude and unexpectedly tracking the same journey by looking at the history of my Foursquare and Gowalla check-ins.

By using the history function from Google Latitude I was able to put together a quick and dirty visualisation of the locations I'd been to but my check-in history added not only the location but also the place that was at each location.

During last week's Geo-Loco conference in San Francisco, Fred Wilson (no, not the guy from the B-52's) mentioned that you could feed your Foursquare check-in history into Google Maps and produce another quick and dirty visualisation of not only the places you'd checked into but also where those places were.

I've been tracking my journey and in doing so inadvertently uncovered a sea change in the way in which we view the whole thorny issue of location tracking.

Yesterday, Ed Parsons and I drove from London to Nottingham and back to attend the one day Supporting the Contextual Footprint event run by the Horizon Digital Economy Research institute at the University of Nottingham and I had Google Latitude running on my BlackBerry, with location history enabled, as I usually do.

Using the pre smartphone, pre GPS, pre Latitude method of writing it down, the journey went something like this: