The “Heatmap” in your profile is now called “Contribution Calendar”, to avoid confusion with the sort of “maps” we normally deal with here. (Arpan200502)
OSM is for everyone and it speaks your language The website is currently available in 111 languages and counting! This would not be possible without the work of our team of translators, which this month saw the first contributions by FL2226 (Italian) Moonborn (Cyrillic Kazakh), Neriah (Hebrew), Serieminou (French), Tuwewanzi (Lakota), @wouterko (Dutch), Sikmir (Finnish, Russian), @MaliMrav (Serbian), and Mo.Hajeer (Arabic). You can help too! Visit Translation - OpenStreetMap Wiki to learn about it.
We found and fixed a couple of strings that were not translatable yet (one, two) (@pablobm, @hlfan)
And finally, we merged a lot of work around cleaning up icons and illustrations, including making more efficient reuse of existing assets (one, two), reducing their size (one, two, three), tweaking the SVG pipeline, and de-duplicating code. (titanic effort by @hlfan!)
When opening the data view of a feature, you may have noticed that you can click on the opening hours to see them on an evaluation tool. However this wasn’t working correctly. Well, it is now! (GA-Kevin-Codes)
In a quirk of OSM English, we referred to fishmongers as selling “sea food”, which although not entirely incorrect, was a bit unexpected. We have now adopted the spelling “seafood”. (@amire80)
Like many projects out there, we have some automated tests that fail randomly. We continue work for them to behave consistently, sometimes successfully, sometimes less so If anyone has ideas please let us know! (@hlfan)
Notification preferences, Summer conferences, and upcoming changes to trace uploads
One more month about to go by, time to recap the latest changes to the website!
Interface
You may remember that recently we reworked the underlying code for user notifications. Today we present the first visible result: a screen to set your notification preferences. Not a huge deal at the moment (email is still the only option), but more is on the way. (@pablobm)
The iD editor was upgraded to v2.40.0, with changes such as a new rendering style for shared bike and foot paths, and dynamic level of detail for created circular objects. (@tyr_asd)
App developers please note a new API error response for the endpoint POST /api/0.6/notes. See the API documentation for details.
This also introduces a new change through the back door: the main database now supports geospatial data via PostGIS. This is not to say that OSM will change its data model to use PostGIS, but rather that some features might take advantage of it in the future.
Under the bonnet
We discovered a bug in an underlying library we use to render forms, and changed a setting to fix it. As a happy accident, this should produce slightly more accessible HTML. (@pablobm)
We have a new section in this recap! The aim is to keep you up to date not only with recent changes, but also with important changes to come.
The focus this month is on a project to improve how we store and render GPS traces. This is led by @Rub21, who among other things is currently discussing the simplification (perhaps elimination?) of the four different “visibility levels” that uploaded traces can have. Not only they make things complex for our systems, but also they are misleading to users. Did you know a “private” trace still publishes location data for other mappers to trace from? We want to fix this.
I would point out, even though nobody has ever read it and the OSMF probably disowns ever publishing it, that the privacy policy does have a section on GPX uploads Privacy Policy - OpenStreetMap Foundation (it is one of the weirder things that OSM uses “GPS Trace” for this).
Shortbread style, JS cleanup, upcoming changes to anonymous notes
The June solstices are now behind us, and it’s time to recap what the OSM Website contributors have been up to!
User interface
We fixed a bug in the way we create links from pieces of text in comments, such as “way 12345”. Some linking rules were too liberal and were causing issues in languages such as Polish. Hopefully no more, but please let us know if this is a problem in your language too. (@pablobm)
If you ever had an error when creating a note, you probably didn’t get much in the way of an explanation We have now added a facility to show error messages when creating notes, so that even if we can’t fix everything at least you should get an idea of what’s wrong. (@pablobm)
We updated iD to version 2.41 (patch versions v2.41.0, v2.41.1, v2.41.2), with new features such as offering to download more data automatically in situations when it doesn’t have enough detail to perform an operation, or new rendering for embankments and cuttings. See all in the release notes. (@tyr_asd)
Apart from what’s new, here’s a feature currently in the works: moderators will soon be able to define “Moderation Zones”, where anonymous notes won’t be allowed. These will be in place for a finite period of time, similar to how User Blocks work.
This can be particularly important to application developers, who need to be aware of a new reason why creating a note might fail. Although again: this this will only apply to anonymous notes. Be sure to check the API documentation.
Depending what we learn with this feature, there might be a future where other moderation measures can be taken on these Moderation Zones. But for now, it’s limited to anonymous notes.
How should updates to that be sent through? There have been a few improvements to the underlying style in the last couple of weeks (see June onwards here; map showing new version here). Do you want me to just tag a release, or create an (untested) PR (and if so to what)?
If you’re able to tag releases with release notes, as OSM Carto does, that would be very helpful to this community and to other end users. I think the OWG is hosting their own copy of your style. Have you all worked out how to keep it in sync?
I don’t think we’re able to cover changes to all the featured layers as granularly as we do for changes to the website proper. Unlike a dependency such as iD, each feature layer deploys independently of the site. It’s probably easier for you to post updates to the forum yourself, but if you like, we can add a periodic reminder to this thread to have a look at your changelog.
The website is currently available in 111 languages and counting! This would not be possible without the work of our team of translators, which this month saw the first contributions by 
(
If anyone has ideas please let us know! (
)
We have now added a