We’re almost at the end of the week of Mario on Google Maps. Announced for March 10 (“MAR10” Day), the temporary feature changed the navigator arrow into Mario driving his cart. Announced for both Android and iOS, but for some reason it never turned up in Google Maps on either my iPhone or my iPad, so I didn’t rush to post. [Business Insider]
Public transit navigation now includes wheelchair accessible routes, as of yesterday: “this feature is rolling out in major metropolitan transit centers around the world, starting with London, New York, Tokyo, Mexico City, Boston, and Sydney. We’re looking forward to working with additional transit agencies in the coming months to bring more wheelchair accessible routes to Google Maps.”
Slashgear looks at the new Google Maps APIs for gaming, which, I guess, enable developers to build real-world games on top of Google Maps. Note that Pokémon Go is not built on Google Maps: I suspect this outcome means that Google has noticed that.
The New Yorker‘s Elements blog has a piece about mapcodes. These are short alphanumeric codes assigned to every location on the planet, with short codes reserved for areas of high population density. It’s meant to be a substitute for latitude and longitude, and aimed at parts of the world where there are no formal addresses (which makes directions somewhat interesting): give someone a mapcode, and you’re giving them a very precise location.
The Peace Tower in Ottawa, for example, has an Ontario mapcode of 09W.YK (mapcodes exist within country and state/provincial contexts).
The main problem, as I see it, is that while the Mapcode Foundation is trying to make mapcodes a standard, it still relies on data tables to produce the code, which is to say that there’s some computational overhead. Whereas something like Universal Transverse Mercator coordinates can be derived from topo maps (which have UTM grids on them).