Earlier this year Google Maps changed the terms of its API and in the process jacked up its prices, leaving web developers to consider other alternatives. These include (among others) OpenStreetMap, which posted a switching guide in June; Apple, which announced its API for websites that same month; and Here Maps, which (a) is still around1 and (b) has announced a freemium plan with reasonably generous transaction limits. As Engadget points out, Google’s trying to profit off its market dominance; its competitors, seeing an opening, are making their move. [Engadget]
Video and presentation slides from Apple’s “Introduction to MapKit JS” session at WWDC yesterday afternoon. MapKit JS is, as I mentioned Tuesday, a method for developers to embed Apple’s maps on their websites. Apple is pitching it as a way for developers who use Apple Maps in their iOS apps to use the same maps on their websites: continuity of look and feel and all that.
MapKit has been around for a few years as an API to allow iOS developers to embed Apple’s maps into their apps. What seems to be new this year is MapKit JS, which enables developers to do with Apple Maps that they’ve been able to do for years with Google Maps, OpenStreetMap, MapBox and even the Ordnance Survey: embed the maps on their websites. Keir Clarke runs through the services and limitations of the API: notably, it requires an Apple Developer account ($99/year) to use. It’s still in beta, so everything is subject to change; in the meantime, Vasile Coțovanu has whipped up a demo. [Maps Mania]
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]
Something that is turning up on my iPhone: plus codes, which appear to be Google’s homegrown solution to location codes, map codes and the like: a short string of characters that indicate a specific location on the globe. They were announced back in August 2015, but last month Geospatial World made note of their rollout.
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.
Inevitable, and surprisingly not before now: Disney’s parks in Street View.
The good news is that, in some ways, Mapzen’s founders built it to fail. “Part of the rules with Mapzen is that everything is open source and we only deal with open data,” says CEO Randy Meech. “Luckily, we’re staffed to help people stand things up on their own.” Users now have T minus 28 days to grab the info they need (or get Mapzen’s help to do it) and upload it to their own data portals, keeping it free and accessible.
The reason for the shutdown is still elusive:
At this point, the company’s coroner’s report is thin. Meech would not comment on the reason for the shuttering. The company is owned by a Samsung subsidiary focused on research and is funded by the South Korean company’s incubator. We do know that running a mapping company ain’t cheap. While Mapzen’s products are built on openly licensed data from OpenStreetMap, it adds valuable software tools to the mix for those who don’t know how to build their own or don’t have the time. Its tools help developers build aesthetically pleasing maps and equip them with search and routing services, while its staff curates, publishes, and creates data. It’s possible Samsung simply decided it didn’t have the money to compete or that it wasn’t worth the price tag.
The article goes on to point out that, Mapzen’s death notwithstanding, the mapping biz continues to be a hot, albeit expensive, sector. [Tyler Bell]
Mapzen announced today that they were shutting down at the end of January 2018.
Our hosted APIs and all related support and services will turn off on February 1, 2018. You will not be charged for API usage in December/January. We know this is an inconvenience and have provided a migration guide to similar services for our developer community. Our goal is to help as much as possible to ensure continuity in the services that you have built with us.
Fortunately, the core products of Mapzen are built entirely on open software and data. As a result, there are options to run Mapzen services yourself or to switch to other service providers.
No reason was given for the move.