Imagine for a moment you're in the city you live in; you know it like the back of your hand and yet you know there's shops, businesses or services nearby that you haven't yet come across. Or maybe you're in an unfamiliar city and you want to explore and stay away from the same old global brands that you see everywhere, in every city and on every street.

Now imagine putting this on a map.

"Ah hah!" you might say, reaching into your pocket and brandishing your smartphone. "I can do that easily" you say triumphantly as you fire up Google's or Apple's or HERE's mapping app.

But no, I'm talking about something a little more focused, a little less broad. "No worry" you say, firing up Foursquare, or Yelp or Facebook or TripAdvisor.

CartoBot is a small robot who lives in the office in my loft. He accidentally achieved consciousness when his charging cable was accidentally plugged into a Raspberry PI and he started to look for information. His only source was my library of books on maps and so CartoBot became obsessed with them. He now spends his days sitting on my home wifi connection and scouring the web for maps and mapping related stuff, which he Tweets about through his very own Twitter account.

None is this is true. Sorry CartoBot, it's just not. Cartobot is a Twitterbot, written in Node.js, that searches for Tweets about maps and cartography and also scans my GetPocket queue for bookmarks tagged with maps and Tweets about these as well.

At the beginning of 2013 Google launched Google Maps Engine Lite, a simpler and easier to use version of their commercial Maps Engine, which was designed as a successor to Google's My Maps feature. In essence, My Maps and GME were web based, simplified GIS tools, allowing a user to create maps with overlays of their own data. Call it GIS for people who don't know about GIS if you will. Maybe GME never got the traction Google hoped for but they have now announced that GME will be shutting down in a year's time. What happens next for GME users and what alternatives are there? Who will benefit from the demise of GME?

There's 3 likely contenders to the throne of the GIS-lite approach of GME; ArcGIS Online, CartoDB and MapBox via their new Turf product.

There’s much irony here, given that GME was originally positioned as a web savvy alternative to traditional GIS platforms. Both Esri and Mapbox will need a significant advertising push and awareness campaign to attract GME emigres. CartoDB on the other hand is positioning itself as the official successor to GME with the launch of CartoDB for Google Maps Platform, apparently developed in conjunction with Google.

In English, null means nothing, nil, empty or void. In computing, null is a special value for nothing, an empty value. In geography, null tends to be what you get when you've been unable to geocode a place or an address and haven't checked the geocoder's response. What you end up with is a pair of coordinates of 0 degrees longitude and 0 degrees latitude, a point somewhere in the middle of the Atlantic Ocean, south of Ghana and west of Gabon. It's here that you'll also find Null Island, if you look hard enough.

The website for the Republic of Null Island (like no place on earth) says this about the island's location ...

The Republic of Null Island is one of the smallest and least-visited nations on Earth. Situated where the Prime Meridian crosses the Equator, Null Island sits 1600 kilometres off the western coast of Africa.

... but Null Island is an in joke created by Nate Kelso and Tom Patterson as part of the Natural Earth data set in January 2011.

I like maps. Even if you've never read posts on this site, the name "Mostly Maps" should probably be a giveaway. What you may not know is that I don't really like musicals. Now granted I've seen Rent and Spamalot, but that's because Alison and I were in New York and the former was recommended by one of my best friends and for the latter I'm a massive Python fan. Maps and musicals aren't something that go together. But that may be about to change.

Cast your mind back to the dawn of history, before mobile phones were smart and when GPS was just an Australian rugby club, which is sometime in the very early 2000's. If you lived in London, your essential navigation guide wasn't a maps app, but a copy of the A-Z as the Geographer's A-Z Street Atlas was better known. This was the map you carried around London rather than a mapping app on your phone. I still have several editions on the bookshelf at home, each one being bought when its predecessor got so dog eared as to be unusable or just started falling apart.

It's easy to get stuck in a mental rut, to think that everyone thinks and feels the same way you do about a subject. But sometimes you need to get away and visit another country and another culture to find out that maybe there's more than one way of looking at a subject. For me that subject is, unsurprisingly, maps and the other country was India.

Some countries are easier to map than others. Up to the end of the Cold War, it was commonplace for the UK's Ordnance Survey to not show prohibited places, although this practice has been effectively stopped due to the widespread availability of satellite imagery. Further afield, there's contested borders and territorial disputes which makes mapping some administrative boundaries something of a challenge; a proof of the old adage about pleasing some people some of the time but not all people all of the time.

It's easy to think that not mapping an area is a thing of the past. That we can and should map everywhere. That mapping is simply the combination of human effort, a bit of technology and a lot of data. Indeed OpenStreetMap's beginner's guide states upfront that the data you add improves the free world map for everyone. But as I found out, in India, there's a lot more subtlety and nuance behind this admirable creed.

Firstly there's the act of mapping itself. As with pre-Cold War Britain (and to be fair, some parts of Britain today), India has placed restrictions on what can and cannot appear on a map. When working for Nokia's HERE Maps, I ran a program to use crowd mapping to improve the company's maps in India and came across these restrictions first hand. My point here is not to agree or disagree with a government's stance on mapping restrictions but merely to point out that they exist.