Every week we choose a new OpenStreetMap “featured image”. Here’s our images of April, May and June:

(click to view bigger images and explanations)

An OpenStreetMap Featured Image (otherwise known as “Image Of The Week”) is chosen each week. Recently we’ve been putting them out on twitter and facebook, so you’ll most likely have seen them there. We’re still a little behind on posting them, so consider this a preview! But featured images also appear each week on the wiki main page.

If you come across an image which you would like to put forward as image of the week (either your own image or somebody else’s), head over to “Featured image proposals” and edit that page to make your suggestion there. Anyone can join in with the process of investigating, improving and discussing the suggestions, and picking an OpenStreetMap image of the week each week. If wiki editing is difficult for you, just email CWG with your suggestions.

Announcing the second OpenStreetMap Awards, awarded this August at the State of the Map 2017 conference in Japan!

This is a community award: nominees and winners are chosen by the community. We are now opening the Call for Nominees, to learn more about the amazing contributors to OpenStreetMap. The Awards strive to be a worldwide event for all OpenStreetMap members, including developers, mappers, community leaders, blog writers and everyone else. We need your help to find the best of OpenStreetMap globally.

For the second awards, we added three more categories focussed on Asia, Africa, and Latin America, three continents under-represented in OpenStreetMap. We strive for increasing the diversity and expect to see more great nominees who the larger community has not been aware yet. This is your chance to make yourself or people you admire visible for the entire world. Add your nominees on the awards website!

We’re mostly looking for new innovations, so only projects/works that were announced after August 1st 2016 are eligible. The Ulf Möller Award is an exception to this. Everyone is eligible regardless of the time when they were active in the project. Winners of past awards and selection committee members (in their categories) cannot be nominated.

The call for nominees will close on 9th of July, and shortly after that we will start the second round, choosing the award recipients. Please nominate!

As well as putting out an April fools day joke, there’s another thing we should remember to do when we’re three months into the year. Every three months we roll over to a new page of our archive of OpenStreetMap “featured images”. Here’s our images of January, February and March:

(click to view bigger images and explanations)

An OpenStreetMap Featured Image (otherwise known as “Image Of The Week”) is chosen each week. Recently we’ve been putting them out on twitter and facebook, so you’ll most likely have seen them there. Actually we’re a little behind on posting them, so consider this a preview! But featured images also appear each week on the wiki main page.

If you come across an image which you would like to put forward as image of the week (either your own image or somebody else’s), head over to “Featured image proposals” and edit that page to make your suggestion there. Anyone can join in with the process of investigating, improving and discussing the suggestions, and picking an OpenStreetMap image of the week each week. If wiki editing is difficult for you, just email CWG with your suggestions.

In case you missed the mailing lists announcement from the Operations Working Group, there will be a one hour period of downtime next Sunday (week today) :

We are planning to upgrade the software which runs the main OpenStreetMap database. Unfortunately, we cannot do this without a small amount of downtime. We would like to schedule this at a time which minimises the impact it will have, and plan to conduct the upgrade between 11:00 and 12:00 UTC on the morning of Sunday 12th March.

We expect that the database upgrade will not take the full hour, and we will endeavour to keep the site online for as much of that period as possible, and have it back to normal status as quickly as possible. However, there’s always the chance for things to go wrong, so please plan for the site to be down for the whole period.

The website and editing API will be affected, but other OSM services including the tile server, Nominatim, wiki, help and taginfo should continue to work as normal.

We will keep you updated through the Platform Status wiki page and OSM_Tech twitter account

If you experience any problems with the API after the end of the upgrade, please get in touch with us on the #osm IRC channel, or by email.

Apologies for any disruption this may cause and many thanks in advance for your patience,

Operations Working Group

Google Summer of Code Logo (CC-BY-NC-ND 3.0 Google)

We’re now in preparation for our 10th Google Summer of Code. Over the years many students have participated and have continued to participate in the project beyond GSoC.

Organizations may apply to GSoC to become mentoring orgs until February 9th and of course we already did apply. However, we have to wait for February 27th to know if we’re accepted again. Student applications are due in April and the official coding period will be from May to July this year. For a full plan have a look at the official timeline.

If you’re an interested student, don’t hesitate and start out today. It’s never too early to make yourself known to our great project and our great community. Our project is big and we have a very broad and diverse set of tasks, and project ideas which require an equally diverse set of skills. But one thing is quite common to all of them: You should learn about our database and how mapping is supposed to be performed. So grab yourself a bit of time and go out and start mapping. Add your local grocery store, your favorite clothes shop or that one bench you love to sit on. No matter what, it’s important to get yourself familiar with OpenStreetMap. Further than that, you can have a look at our ideas’ list to see if there’s anything that you like and we’re also open to your own ideas. The best is to get on IRC or on our developers’ mailing list to introduce yourself and talk about what you want to work on.

If you’re a developer, please consider to add your good idea to our ideas’ list or add yourself as a potential mentor for one of the proposed projects. We’re always seeking for backup admins, just in case. And if you are unsure whether your idea is good enough or if it’s feasible, you know where to find the GSoC admins. Just ask.

Finally, if you’re just interested about the Summer of Code, we have a detailed recap of 2015’s GSoC, but also 2016 was a great success with a number of interesting projects and good students. In 2016 we had a total of six projects accepted, where four of them made it to the end.

Michael Zangl, a student from Germany, worked hard to reorganize the core of JOSM, our most widely used editor. He participated in 2015 as well, and he subscribed as a mentor for 2017. He wrote a detailed summary of his work and we’re happy to have him in our project and as a potential mentor this year.

Darya Golovko improved the JOSM Plugin for Public Transport (pt_assistant) i.e. by validating the public transport routes against a set of criteria, identifying errors and suggesting how to fix them. Her work is described in more detail here. Darya was a great student and it was nice to have her at our annual international conference, State of the Map.

Kushan Joshi applied for adding a visual lane editor to our javascript-based editor iD. Although he was very diligent, he didn’t complete the project as was initially planned, for no less reason than that he fixed several bugs, added features and worked on various other elements to make our editor iD even greater. As we valued his work very much, he passed last year’s Google Summer of Code without a question and you can read a detailed description of his work on his personal blog. While he is continuing his study work, he’s still with our project and contributing code from time to time.

Last but not least there’s Zabot who continued the work on OSM2World, a well known 3D converter in OSM. Although it’s a hard task to get to know all this new technology with OpenGL and shaders he did an impressive work and added several new features to the rendering pipeline, so that you now have reflections on windows and water, colors and reflectance based on the time of day, ripples in water bodies, and multi-light rendering which allows you to have nice renderings at night with illumination coming from street lamps. Even though he didn’t stick with our project, his work is much appreciated and you can read more about it on his personal diary.

Reading all that you really should go out and have a look what you can do to help our project. We’re searching for you and your helping hand. And even without you being a student (in Google Summer of Code) we’ll greatly appreciate your help. Be it as a developer for a specific task or project idea or as a mapper to make our map even greater than it is already now.

Hope to see you soon.

a new year’s firework display hidden in the OpenStreetMap tile viewing data

So yet another year has passed with so many new and exciting things. With a history of more than 12 years we have built a huge community with many success stories, large and small, and we want to share a brief recap of interesting things that happened this year.

The OpenStreetMap Foundation’s board did some small changes that seem to be well received by the community, mainly a significant increase in the board’s transparency; e.g. board meetings are now open to the public and all members are allowed to tune in and even participate in board meetings. Besides that, the Foundation is experimenting with an assistant who was hired to help with a bunch of administrative tasks to support the board and at times the Working Groups. And as mentioned in the manifestos of the two board members that stood for re-election in this year’s board elections, the current board are respectful to each other and are working together very well.

Speaking of the Foundation, there is a new Corporate Membership Program that has been introduced towards the end of 2016. It features different tiers, with fees from €500 per year up to €20,000 per year. The program officially starts in January 2017 and already great interest has been expressed in it with two imminent/upcoming/ gold memberships. Together with the first general successful donation drive that raised €70’000 we’re in good shape for the year 2017 to keep our financial Independence as a community project.

We also need to mention the forming of two new Local Chapters this year. In February the Italian Local Chapter got accepted as officially recognized, and only a few months later the Swiss Local Chapter followed. We’re very happy about the formation of Local Chapters, and we expect there are more to come soon: The German FOSSGIS e.V. is considering applying in 2017.

During the year we participated again in the Google Summer of Code, with six very interesting student projects which were worked on during summer. And if we get accepted, we’re sure to participate in 2017 again.

But not everything was good news this year. The German community -no, the global community- had a huge loss with the death of Malenki. He was known to many of us for his kindness, helpfulness, the many projects he worked on and his very active mapping history. RIP.

The Wochennotiz, the German version of the well known weeklyOSM, had an anniversary this year: It’s 300th issue. And as weeklyOSM is translated in different languages and is always seeking to extend its visibility, we might see new languages added in 2017. Right now the issues are released in 8 different languages.

The UK community has continued with actively pursuing its Quarterly Project to have a special mapping task that the community tries to collaboratively work on for three months. A story of success and perhaps a good example for other local communities for 2017?

With a new head of SotM Working Group and a great and active local team we had a great State of the Map. It was a lot of fun to see so many people from our community joining from all over the world. It was a great success, for the community and also financially. Besides the many great talks we had the OSM-Awards for the first time to honor volunteers in our community in different categories and we expect to see a repeat of these awards at another great State Of The Map conference in Japan in 2017.

But there was more than just our international SotM. There have been many local conferences, too, which allow a wider and local audience to participate. We’ve had a SotM Latam in São Paulo, Brazil, a SotM Asia in Philippines, the FOSSGIS-Conference in Salzburg, Austria, a SotM US in Seattle, Washington, a SotM Cz in Brně, a SotM FR in Clermont-Ferrand and a SotM JP in Tokyo.

Normally the work of our Licensing Working Group is not so publicly visible and this year has been tough as four of the seven members have had babies. So less volunteering time for LWG, but new blood for OSM! Anyway, there still have been two achievements that had a bit of a wider audience. After a long history of drafting, collecting feedback, updating, asking for further comments, updating again, the LWG finally managed to publish the new Collective Database Guideline which was approved by the OSMF board. In a similar matter, the LWG updated the Privacy Policy to fix some longstanding shortcomings of the old version. For example the policy now clearly states what gets logged and how that is used and a detail around how the sharing of data with respect to Gravatar profile pictures works.

Of course there are more Working Groups that do volunteer work. Only this year the new Membership Working Group was formed. This group are administering the membership database, answering to membership queries but is also tasked to increase the OSMF membership. Additionally, there is the Data Working Group and the Operations Working Group who are doing great and extensive work. However, you know those groups are doing good work, if you don’t hear too much of them 🙂 And last but not least there’s the Communications Working Group who are writing blog articles like this one for you.

We want to say a huge Thank you to everyone who participated in one of our Working Groups, in the Foundation or in our project in general. You’re the ones that make our project and our map so great and who made this year a story of success like the years before. Happy new year to everyone, keep up the good work and see you in 2017!

Some tips for our new mappers coming from Pokémon GO:

Pokémon Go?

We’ve recently seen a flurry of new map editing activity from “Pokémon GO” players. Although this hugely popular mobile game displays maps from google maps (in fun colours), it seems it may be using OpenStreetMap data (according to some players) to influence “spawn points” within the game.

This is interesting for several reasons. We always like to see creative and unexpected uses of our free and open map data, and this certainly fits into that category! (Note: our open license does require crediting OpenStreetMap)

There is some new interest in editing the map from Pokémon GO players, presumably because the game is found to be bringing in updates when changes are made to OpenStreetMap. It always takes new folks some time to get to know OpenStreetMap, and we hope Pokémon GO players will stick around to contribute some more. We’ve prepared the above guidelines to help understand some aspects of OpenStreetMap related to the game.

OpenStreetMap is a world-wide collaborative project aiming at providing free map data, under an open license, to anyone who wants it. Volunteers all over the planet contribute their local knowledge and their time to build the best map ever.
You can contribute by improving the map, editing or translating the wiki, becoming a member of the volunteer Working Groups, increasing awareness about the project, uploading GPS traces, donating (donate.openstreetmap.org) or joining the OSM Foundation. You don’t have to be a member of the Foundation in order to edit OpenStreetMap.