To answer the question: no.
OpenStreetMap is constantly evolving in many dimensions. A fully fledged editor requires a significant investment to remain current (think at least one FTE).
177 karma · joined October 20, 2015
OpenStreetMap is constantly evolving in many dimensions. A fully fledged editor requires a significant investment to remain current (think at least one FTE).
The only businesses that over the years have been able to offer tile hosting as a sustainable business are very small mum and pop shops.
The large players are naturally not interested directly in the money aspect of providing the service, but in synergies with other, actually profitable, parts of their business.
And those in between are always in between pivots.
b) the more sensible approach would be to use pre-generated vector tiles, for example from https://openmaptiles.org/
I don't believe I said anything else, particularly given that I was one of the people most strongly lobbying for iD to become the default editor at the time (the rationale was not quite as you put it but that doesn't matter).
And that there is no misunderstanding: nobody is proposing changing that,
While OSM is similar to Wikipedia in many aspects, it is very different in others. In particular while both movements have a supporting formal body, in the case of Wikipedia the WMF, for OSM the OSMF, that run (fsvo run) the central infrastructure and formally publish the data from a legal pov, in practice they are very very different.
This starts with the size of the budgets (the OSMF is roughly 1/1000 of the WMF one), to the fact that the OSMF is a membership organisation that determines its board in a democratic fashion (coming up soon), and so on.
But the relevant difference for this discussion is that the OSMF has never been involved with developing software (with one small exception) and that all the bits and pieces that make up what you experience as "OSM" have been written and maintained by the community. This has always included commercial entities and major parts of the editing API and the website have been written by developers on the payrolls of companies with an interest in OSM.
Editors (the programs that allow you to add to and change the data in the OSM database) have kind of always been an exception. The 2 in-browser editors Potlatch 1 & 2 that led to the breakthrough of early OSM were for the major part written by Richard Fairhurst, JOSM the most popular desktop editor is developed by a group of volunteers and similar things are true for most of the less known apps.
Back in 2012 it was clear that the Flash based Potlatch 2 had only a very limited remaining life in front of it and Richard started work on an PoC for a JavaScript based replacement that he named iD.
This gave Mapbox the idea that they could repeat what they had already successfully done once with Tilemill, to apply to the Knight Foundation for a grant to improve the OSM website and create a new JS based editor. Naturally this was not just out of the goodness of their hearts, just as with Tilemill this was also an opportunity to scale up the company. In any case Mapbox was awarded half a million $ for this work which led to the release of iD in May 2013.
Note that the current developers and maintainers of iD were not involved at this time, and I'm not even sure of any of the original devs are still with Mapbox.
In due course iD replaced P2 as the default editor on openstreetmap.org, that is the editor you get when you simply click on the "Edit" tab. This is a rather privileged position as for nearly all new contributors this is the point of first contact for OSM and can be formative for ongoing editing behaviour (while from a number of users iD is by far the most popular tool, JOSM outstrips it in the actual volume of edits).
Obviously the $500k didn't last forever and while there was one larger refactoring of the code that was worked on by a team in Mapbox, the involvement of Mapbox was obviously scaled down after the money ran out.
In 2015 (iirc) Mapbox hired the current lead developer and last year he was joined by a further developer employed by a consultancy. There have never been any formal communications from either of the employers as to scope of their current and future engagement, not even as simple as to where the money to finance this rather expensive undertaking is coming from.
Which brings us to the tensions that led to Frederiks blog post.
We've always had a bit of a dictatorship of the developers when it comes to editors, and all of us (including myself) tend to have "good ideas" (that now and then turn out not to be so good and have to be undone :-)) that are not pre-vetted with the community at large.
What is different with iD is its privileged position, and that because OSM has grown so much the much larger, the impact that changes to the default editors behaviour have, the IMHO in-transparent decision processes (who is -actually- calling the shots?) and the easy to offend devs. Combined this is rather an explosive mix.
The latest episode is the decision to start displaying brand logos in the editor and retrieving these online and mainly from Facebook. There are a lot of reasons why this is problematic, not the least that it violates EU privacy regulation without prior consent of the users (this is true regardless of the source of the logos, but obviously using Facebook makes the whole thing even more controversial). Not unexpected this led to complaints which in turn led to the devs locking down issue creation on the iD repo (this has AFAIK now been undone).
Obviously this has to be defused in one way or the other and running a patched version of iD on openstreetmap.org that is under more community control is one possible solution (though not my favourite).
Simon
The "alarm" is caused because concerted action of roughly 10% of the OSMF membership could easily tip the current wobbly balance one way or the other, and there is no guarantee that the current "hands-off, low budget approach of the OSMF would survive such an upheaval.
MapBox is an active and respected participant in the OpenStreetMap project and uses our data in some of its products, but that is it.
Further there are multiple on device routing and rendering solutions available so you don't really have to use an online service if your don't want to.
The other aspect is that the OSMF itself doesn't really produce any software at all (you could argue that the website software might be different in this respect). What you think of as OSM the OSS project is really lots of companies and individuals providing SW that works with OSM, not the result of a centralized effort a la WMF, Mozilla, or whatever ...
Mass mapping buildings is a rather recent phenomenon in OpenStreetMap and you can have a high quality, fully functional map with not a single building outline (as google shows too). Not to mention that we have had a country with full address coverage since ages that only has a small number of buildings mapped (DK).
Now there are certain high detail tasks for which having building outlines make sense: for example adding entrances with addresses, but that is fairly far along on the path of iteratively adding more detail to OSM.
Given reasonable quality aerial imagery (on which automatic detection a la Facebook depends too) the limiting factor for years in OpenStreetMap has been meta data collection (names, road attributes, POIs, addresses and so on). Humans are quite fast and good at tracing roads and the couple of minutes it takes to add a few dozens of streets is just inconsequential compared to the time and effort it takes to go there and actually survey and add the meta data.
Now despite some bloggers, that themselves haven't noticed that OpenStreetMap is very different than in 2007 (but you know xkcd 386), claiming that OSM is standing still, the OpenstreetMap community is quite welcoming to new and better ways of surveying and obtaining data. Mapillary and now OSV have made lots of aspects of meta data collection easier and faster and have found wide spread adoption in OSM including automatic sign detection and so on.
But even with such advances, gathering and entering the meta data is still by the order of magnitudes the dominating time consuming process in OpenStreetMap (and for what it is worth in any mapping activity).
It is true that very large multi-polygons can be hard to edit however they tend to be exclusively used for modelling large landuse areas and administrative boundaries, and tend to have no impact at all on adding and editing roads, buildings, POIs and so on.
The in-browser editor iD is really easy to use, however currently does not work with IE.
Naturally comparing with google is a bit apples and oranges, on the one hand a company that purchases essentially all its data and spends billions on its mapping department, compared to the OSMF with a annual budget of roughly $150k. So it is not a surprise that some things take a bit longer with OSM, but it is tortoise vs. hare....
Mapillary (mapillary.com) offers StreetView similar capabilities, including sign detection and can be used together with the desktop OSM editor JOSM and the in-browser editor iD.