In response to the latest round of flash floods in France, The Local has a piece looking at natural disasters in France that points to a set of interactive maps from France Info (in French; page doesn’t work well in Safari) that show the number of natural disasters, by commune, since 1982, as well as the number of disasters due to flooding and drought. The maps indicate where the disaster hot spots are in France and (to some extent) where they aren’t: only 3.5 percent of French communes have never had a disaster declaration in that period. Sixty percent of the disasters were due to flooding; The Local also points to the Global Flood Map: zooming in sufficiently shows the zones for high and moderate risk of flooding. [Gretchen Peterson]
Here Maps is still around, and they’ve announced the public beta of Here XYZ, a set of tools for developers to create online and interactive maps. There are several levels of said tools: Here XYZ Studio is a web-based application designed for non-developers; there are more advanced tools and APIs available, up to and including a command-line interface. Documentation is here. [Maps Mania]
Previously: Google Maps Changes API Pricing, Competitors Respond.
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]
Google is assigning names to neighbourhoods that, the New York Times reports, have little basis in reality—but once on Google Maps, those names swiftly come into a popular usage they never had before. The East Cut, in San Francisco, was the product of a branding agency; Fiskhorn, in Detroit, is actually a misspelling of Fishkorn, taken from a typo in the source map. (Searching for “Fishkorn” works just as well, though.) How such names end up on Google Maps, and therefore get a certain canonicity, is what’s interesting: it seems to be the result of a tech giant processing diverse data with remote fact checkers and not much in the way of local knowledge. [Boing Boing]
Web mapping uses Web Mercator. As Kenneth Field points out, this is fine at large scales, but at small scales you end up replicating the problem of using the Mercator projection on a wall map of the world.1 Zoom out in Apple Maps: using the map layer you get a Mercator; using imagery you get a virtual globe (basically, an orthographic projection you can spin). Ditto in Google Earth. But Google Maps, after some tests and starts, now does this in its map layer—and not just in Chrome, either. This means, among other things, that Antarctica is usably visible, as are the Arctic regions—and, of course, Greenland is its proper size at small scales.
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]
An Ottawa city councillor wants take a page out of Los Angeles’s playbook and create a real-time interactive map of the city’s road conditions. L.A.’s street assessment map rates road conditions as good, fair or poor. Since Ottawa’s roads are on balance between fair and poor, it might be revealing, if uncomfortable, to have all that road data easily accessible; at the moment it can only be accessed by asking city officials about the state of a given street.
When I started contributing edits to OpenStreetMap in earnest, I couldn’t help notice certain idiosyncrasies in its tagging: for example, there was a tag for brothels, which I didn’t need to use, but there wasn’t one for daycares, which in Quebec there are rather a lot of. That seemed odd. And it was indicative of a project whose contributors were overwhelmingly male. On CityLab, Sarah Holder examines OSM’s abysmally low female participation rate (only two to five percent of contributors are women), makes the case for better representation, and looks at where women are making a difference to the map. Because a map built overwhelmingly by men can have some massive blind spots.
When it comes to increasing access to health services, safety, and education—things women in many developing countries disproportionately lack—equitable cartographic representation matters. It’s the people who make the map who shape what shows up. On OSM, buildings aren’t just identified as buildings; they’re “tagged” with specifics according to mappers’ and editors’ preferences. “If two to five percent of our mappers are women, that means only a subset of that get[s] to decide what tags are important, and what tags get our attention,” said Levine.
Sports arenas? Lots of those. Strip clubs? Cities contain multitudes. Bars? More than one could possibly comprehend.
Meanwhile, childcare centers, health clinics, abortion clinics, and specialty clinics that deal with women’s health are vastly underrepresented. In 2011, the OSM community rejected an appeal to add the “childcare” tag at all. It was finally approved in 2013, and in the time since, it’s been used more than 12,000 times.
Interestingly, when you look at crisis mappers, the female participation rate jumps: to 27 percent, based on a survey of the Humanitarian OpenStreetMap Team community.
Much chatter on Twitter about a blog post criticizing OpenStreetMap that made it to the front page of Hacker News; problem is, said chatter hasn’t been linking to said blog post. Here it is: “Why OpenStreetMap is in Serious Trouble,” in which Serge Wroclawski argues that OSM has lost its way on a technical and management level:
Before I criticize the project, I want to state emphatically that I still believe wholeheartedly in the core principles of OpenStreetMap. We need a Free as in Freedom geographic dataset just as much today as we did in the past. When I wrote my article about OSM in 2012, self-driving cars and other services were still a dream. Today the importance of having a highly accurate, libre geographic dataset is more important than ever, and I support those working to make it happen.
That said, while I still believe in the goals of OpenStreetMap, I feel the OpenStreetMap project is currently unable to fulfill that mission due to poor technical decisions, poor political decisions, and a general malaise in the project. I’m going to outline in this article what I think OpenStreetMap has gotten wrong. It’s entirely possible that OSM will reform and address the impediments to its success—and I hope it does. We need a Free as in Freedom geographic dataset.
I do love me a good rant; and as an OSM contributor myself, I do recognize some of the problems Serge highlights, particularly the difficulties in importing data, moderating edits, and vandalism.
Since getting linked there is what drew attention to it, Hacker News comments (I know, I know) are here.
Previously: OpenStreetMap at the Crossroads.
NASA’s Socioeconomic Data and Applications Center (SEDAC) has produced a population estimation service “for estimating population totals and related statistics within a user-defined region.” Basically, it provides a population estimate for an area drawn on a map. Available as data via map and GIS clients, it’s also accessible via a web app. I’ve noodled about with it; its population estimates are generally not insane. [Kottke]
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]
Yesterday I told you about Mapzen’s announcement that it would be closing down at the end of the month. So it’s bittersweet that I find, in my to-do list of links to post here, a Mapzen project. Morphology is a tool that abstracts the map into an unlabelled set of lines, patterns and forms. The default view combines several different features, but you can isolate single features: airports, roads, parks, bodies of water, and more. The work of Mapzen cartographer Geraldine Sarmiento, it was first presented as a NACIS talk last October. [Atlas Obscura]
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.
Justin O’Beirne’s lengthy analyses of Google Maps and Apple Maps are always worth reading,1 and his latest is no exception. Looking at the rapid proliferation of buildings, areas of interest and other examples of Google’s Ground Truthing program, Justin discovers that Google’s buildings data are a product of its satellite imagery, its places of interest are a product of its Street View data, and its areas of interest (the orange-shaded areas that indicate business districts) are the result of combining those stores of data.
…so this makes AOIs a byproduct of byproducts[.]
This is bonkers, isn’t it?
Google is creating data out of data.
This is slightly more than Google’s competitors are able to match. As always, Justin’s analysis is worth reading in full, and comes complete with before/after animations that make his point visually clear.