Users' diaries

Recent diary entries

What's new in OSMCha

Posted by nammala on 11 October 2017 in English (English)

If you have been a daily user of OSMCha, you have already started using the new version. Wille has been working with Mapbox on new developments of OSMCha. We have been testing the stack stability, and collecting feedback from Mapbox data team and community members for few months now.

I would like to use this diary post to introduce few features in the new version of OSMCha and talk about ways we can use them for validation.


The development challenge has been to make OSMCha easier to use, faster to review changesets, and a robust tool for filtering OSM edits. We needed to add contextual information on mappers & changesets, improve the user-friendly UI, add keyboard shortcuts, and a lot more using an API driven frontend.

Along with a brand new design, a lot of things have been improved in the new version. Here are some of the new features.


The sidebar is similar to how the History tab on OpenStreetMap shows a list of changesets. The sidebar on OSMCha also gives a count of changesets in the search, and supports keyboard shortcuts to move through the list.


Many filters correspond to the metadata associated in changesets. To help make this clear, we now have descriptions for each filter that briefly explain what a certain filter does in the search.

Saving personal filters - Area of interest

One key request from OSMCha community users has been ability to save a set of filters for easy sharing, and reuse. This is now possible! You can save a filter with a custom name and share the url with the folks you work with or find it in your profile for future use and reference.

For example: Here is a filter that lets me see all changesets in New York

GeoRSS feed

If you would like to be notified when a new changeset comes into your personalized filter, we now have GeoRSS feed that can do that for you. Here is an example changeset feed link for the New-york filter I have made above

Open a list of changesets by ids

If you need to open a list of changesets by id (for example, returned from Overpass), OSMCha now supports filtering by comma seperated changeset ids.

Size bound BBOX search

The bbox search works by retrieving all changesets whose bboxes have an intersection with the bbox we give. A problem with this method is that global scale changesets can overlap the local search area. This problem has been wonderfully explained here by Athalis. One way to solve this problem is to have a bbox size bound search.

Bbox size bound search limits the retrieval of worldwide edits by taking a multiple from the user that essentially limits the max bbox size in the search. Example: 2 only shows changesets whose bboxes are at maximum twice the size of bbox we have provided.

Keyboard Shortcuts

Keyboard shortcuts enrich user experience. In the new version of OSMCha, we have keyboard shortcuts that allow us to sift through panels, sidebar changeset list and even verify a changeset. Read more about keyboard in the about page for OSMCha

Tag the changesets

Another new feature is the possibility to tag the changesets. This way we can add a little more information about the changesets, besides saying that it’s good or bad. We have some tags to evaluate the severity degree, if the errors were resolved or not and if they were intentional.

It is important for us to review changesets we are reviewing as good or bad, as it indicates other community members that they need not spend time on that particular changeset.


If you have ideas or suggestions on OSMCha, please feel free open an issue in one of the below repositories.

OSMCha frontend -

Backend API repo -

Find all the necessary documentation related to the API here:

API docs -

We are delighted to introduce the new version. This was a collaborative work and we hope you like it just as much as we do.

Happy reviewing!

OSM Contributors Outlook - The Pulse of OpenStreetMap Contributors

Posted by PierZen on 11 October 2017 in English (English)

Pulse Talking of the OSM Contributors, we often see the Big Numbers. In this Diary, my objective is to focus on the OSM Contributor profiles, to try to measure the impact of various groups on the OSM Edit Contributions.

Since 2005, there has been an explosive growth of new OSM Registered members from 500,000 in 2012 to 1 million in 2013 and 4.2 millions at the end of september 2017.

Pascal Neis and Alexander Zipf study in 2012 showed that only 38% of the registered members at the end of 2011 had started editing the database and that only 5% (24,000) of all members actively contributed to the project in a more productive way. published in july 2013 an interesting analysis of contributors «Joining and leaving» as participants. It shows the volatily of OSM contributors with a high volume of contributors starting and stopping contribution shortly after. As we will see below, a high percentage of people that start to contribute stop the first day or after a short period.

There are also various studies that show the contribution inequality with most of the data produced by a minority (see Anran Yang, Hongchao Fan, Alexander Zipf, 2016 and Ding Ma, Mats Sandberg and Bin Jiang, 2015). Statistics and analysis presented by Pascal Neis and Simon Poole over the last years did also show various aspects of the contributions, with the concentration of Contributions by a minority and the volatility of contributors participation.

The OSM Changesets Dump File contains metadata about each changeset edition. Like others, our analysis comes from this file. If we dig in and analyze the OSM changesets database, this shows that for the 13 years from 2004 to end of september 2017, 953,200 contributors edited at least one object and 108,800 edited more then 1,000 objects (ie. node, ways or relations). This is an indication that there are massive inflows of new participants that contribute minimally. The analysis below will confirm this hypothesis.

The Pulse of OpenStreetMap Contributors

Cohort analysis let’s break a dataset into related groups that share common characteristics or experiences. For OSM, we can group contributors by the year they started to contribute and compare the various cohorts to see patterns of contribution.

The graph 1 reveals what I call the «Pulse of OpenStreetMap Contributors». Rodolphe Quiedeville OSMPulse website did also illustrate the beat of contributions. While his real-time graphs (Last update in 2014) did focus on the number of objects edited minutely, we focus on the contributors with the same year of experience. For each calendar year, this is like if we did organize a marathon will all the contributors aligned on the same start line, looking at their progression month by month. We could also follow them for even longer periods and compare their long term behavior.

Graph 1
Note that this graph do not show a long timeserie. These are 
individual graphs for each yearly cohort.  For each year,
we follow for 12 months the new contributors that start editing. 

Graph 1

Here for each calendar year, we follow OSM new contributors and participation from their month 1 to month 12 of contribution (it does not matter if one started in january, feb. etc). With such cohort analysis, we can see all the new entries for the year. This reveals what I call the Pulse of «Discovery contributors» with the great majority that do not participate more then 1 month. The high rate of departure at month 1 confirms the volatility of contributors participation. It shows what is called the lower tail of Contribution with a high number of Contributors with a minimal impact on the OSM edits. There is a lot more to say from such analysis and I will come back in an other Diary with more profile analysis from the cohort trajectory statistics.

Simon Poole published in his OSM Diary various examples that show the variability of inflows of new contributors and how it is not always related to significative edits. The sudden increase of contributors in early 2016 that we can observe on graph 2 below comes from Maps.Me editors where many of them did map personal infos. At the end of 2016, thousand of faked accounts were created in USA by SEO companies. OSMstat for 2017-09-30 shows also indications of various profiles with 5,413 active contributors and 3,301 with node edits > 15.

Graph 2

Graph 2

Monthly Statistics – Let’s color with Contributors Profiles

Lets’ now add Days profiles to the monthly statistics and help better see the heterogeneity between the Contributors and the Contributions. Pascal Neis OSMstat website and Simon Poole stats on the OSM wiki OSM wiki let us observe monthly statistics of contributions. We observe since the beginning of 2016 an average of 25,000 to 50,000 active contributors per month.

Graph 2 combines the monthly statistics of Contributors (ie. have edited in the month) and Contributions (ie. number of objects edited node, way or relation) from the OSM stats wiki. We color these charts with the Contributors profiles based on cumulated days of participation since the first edit to OSM (Pascal Neis classification). The comparison of the two graphs let’s observe the concentration of Contributors in the first two classes and the concentration of the Contribution in the last class.

Profiles of Contributors and Contributions by month for 2017 up to september on Graph 3 let’s measure the respective percentage of each class based the cumulatives days of contribution. For 2017-08, the first two classes «Discover 1-2 days» (19,186 contributors) and «Rarely Active 3-14 days» (12,845 contributors) represent 66% of the share of Contributors. In comparison, their share of Contributions (13%) is relatively minimal. The «Discover» class with 3.5% of Contributors corresponds more or less to the «Pulse» we observe on the cohort analysis.

The other tail of distribution is represented by the 4,000 contributors that are part of the «Mega Active» class (271 days and more). They represent 8% of Contributors and 37.6% of Contributions.


Graph 3

Pascal Neis Contributions of the yearly cohorts graph on his 2016 yearly Statistic Blog, shows the respective importance of each yearly cohort on the level of monthly Contributors. In this case, the cohorts are not aligned from month 1 but colors let's see stratas of contributors by the year they started to edit. With this representation, the peak of the yearly new contributors is less acute, being spread in the month they started editing. The top of Graph 4 reproduces Pascal chart. Every year, we observe the jump in the number of contributors, and their relative importance that reduce gradually in the next years. Again, we see the rise of Contributors from 2016.

The Contributions Profile at the bottom of the Graph (ie.Percentage of Contributions by months) reveals that the first year of participation, the yearly cohort of new contributors represents nearly 40% of contributions, that share reducing in the following years. With the rise of Contributors in 2016 and 2017, we observe also a rise in the share of Contributions. Simon has measured that the rise of Maps.Me Contributors had a minimal impact on the share of Contributions. More analysis will be necessary to explain which categories are responsible of this jump.

Graph 4

Graph 4

I hope that this different angle on the Contributors data will hep to better understand the various contributions to OSM. Do not hesitate to comment. And I plan to continue such analysis in other Diaries.

(يمكنك مساعدة (العراق

Posted by Øukasz on 10 October 2017 in Arabic (العربية)

وقد وضعت العديد من المدن والبلدات والقرى في العراق على الخريطة عن طريق الاستيراد التلقائي من مصادر البيانات القديمة وليس من قبل الناس الذين يعرفونها. وبسبب ذلك، فإنها غالبا ما تكون اما خاطئة، او توجد في غير مكانها، او هناك خطْـأ بالكتابة او ذات تاريخ قديم غير مستخدم او غير ذلك. يجب التحقق من جميع الأسماء من قبل أشخاص لديهم معرفة محلية بالقرى.


المدن هي مستوطنات كبيرة و عادة لا يوجد فيها زراعة. اما البلدات هي أصغر من المدن و فيها بعض الزراعة. اما القرى هي مكان زراعي.

يوجد كثير من القرى القديمة أو المهجورة. يجب اختيار (abandoned:place=village) لهم.


يجب أن نضع اسم المكان المستخدم حاليا في (name = tag) و يجب ان نكتب الاسم الاصلي باللغة العربية. و يجب وضع الأسماء القديمة (على سبيل المثال الاسماء المستخدمة قبل إعادة التسمية في 2003) في old_name = tag للسماح لها بالتقاطع مع الوثائق التاريخية. الأماكن التي ليس لها أسماء محددة باللغة الإنجليزية، ولكن يمكن أن يكون لها أسماء عربية مكتوبة في الأبجدية اللاتينية يجب استخدام (name:en-Latn= tag). الإنجليزية واللغات الأخرى (الفرنسية والألمانية والإسبانية ...) يمكن أن توضع في (=name:en) ، الاسم: (=name:fr) وهكذا على العلامات.


يجب ربط جميع القرى بطرق فرعية إلى الطريق الرئيسي - عادة (highway=tertiary) أو (highway=unknown) كافية.

Location: العامرية, الأنبار, العراق

Proposed Troll Head Sculpture with 'worms for brains' vermiculture internals.

Posted by Loc8 dot Space on 10 October 2017 in English (English)

ned compost related support for drop off, community outreach, collaboration, greenhouse and cold frame design and vermiculture.

Location: East 2nd Street, Nederland, Boulder County, Colorado, 80466, United States of America

UPDATE: number of keys grows, and grows, and grows ...

Posted by Harald Hartmann on 10 October 2017 in English (English)

just an update of number of keys grows, and grows, and grows ...

number of keys

since the last post one week ago, the graph is now in a sideways motion ... great.

thanks guys, and keep up.

Hello world!

Posted by Victor Curalea on 10 October 2017 in Romanian (Română)

Nice to be here, OpenStreetMap!

Travail de sabotage

Posted by AV31 on 9 October 2017 in French (Français)

Je viens de constater que "Yan Tremblay" a fait un gros travail de sabotage. Il a transformé toutes les voies de service des autoroutes de la région de Montréal (A-15, A40, A-520, A-25) en "motorway_link". Voici quelques numéros de groupe de modifications que j'ai pu trouver : 52317852, 52316945 et 52332790. Ces voies de service sont en réalité des rues où il y a des accès direct à des commerces et des industries.

Location: Notre-Dame-de-Grâce, Montréal, Montréal (06), Québec, H4B 1G8, Canada

Hurricane Maria, Puerto Rico- Mapathon at Massachusetts Institute of Technology

Posted by Alan Bragg on 8 October 2017 in English (English)

Approximately 50 MIT students and OSM'ers from the Boston area participated in a 4 hour Mapathon on Sunday afternoon 10/8/2017.

The task was to map buildings from satellite photos taken before Hurricane Maria

Dewey Library

The event went off without a hitch. The facilities at the Dewey Library were fantastic. I was surprised that this event, organized just a couple of days ago was so well attended. The student organizers spread the word and the community responded.

The organizers were pleased at the turnout and hope to hold more mapathons in the future.

Location: East Cambridge, Cambridge, Suffolk, Massachusetts, 02114, United States of America

Géocodage d'établissements scolaires

Posted by Cdrik_69 on 8 October 2017 in French (Français)


Cette méthode a été utilisée, à défaut de mieux. Au préalable, j'ai consulté la liste nationale des contributeurs OpenStreetMap. Peut-être existe-t-il une solution bien plus simple...? Merci de me dire cela en commentaires.


Faire une géolocalisation de stagiaires venant à une formation sur Lyon afin de faciliter le co-voiturage. Le stagiaire étant associé à son établissement.


  • Nous disposons uniquement du nom de l'établissement et de sa commune.
  • Nous ne disposons pas des coordonnées GPS des établissements, ce qui est indispensable avec uMap

La solution simple aurait été de faire une carte GoogleMaps...

Mise en place

Je dispose d'un fichier .csv de la forme : nom_etablissement,commune,Nom,Prenom,Courriel

Site permettant de récupérer les coordonnées GPS

Je trouve un site internet qui dispose d'une API et qui permet, grâce à une requête sur le nom et la commune, de récupérer un fichier JSON. Au départ, quelques requêtes ne donnaient aucun résultat, pourtant sur OpenStreetMap, c'était ok. Après contact avec l'administrateur du site, toutes mes recherches aboutissent normalement !

Exemple de requête

Ma requête sur le lycée Récamier à Lyon :

Le fichier JSON en retour

Le fichier JSON en retour comporte les coordonnées GPS : {"features":[{"geometry":{"coordinates":[4.830498683911657,45.7495013],"type":"Point"},"type":"Feature","properties":{"osm_id":258128918,"osm_type":"W","extent":[4.8298975,45.7499687,4.8311069,45.7491155],"country":"France","osm_key":"amenity","city":"Lyon","street":"Cours Verdun Recamier","osm_value":"school","postcode":"69002","name":"Lycée Juliette Récamier","state":"Auvergne-Rhône-Alpes"}}],"type":"FeatureCollection"}

Avec cela, je vais pouvoir donc extraire la Latitude et la Longitude de chaque établissement.

Script Python

Ayant un peu de connaissances en Python3, je crée un script, pas bô mais fonctionnel, mes excuses..., qui me permet de générer un nouveau fichier .csv avec les coordonnées de chaque établissement. Je ne touche pas au fichier initial.

Avec ce nouveau fichier, il ne me reste plus qu'à générer une nouvelle carte uMap en important ces données.


Cette même méthode m'a permis de créer une carte de tous les établissements de l'académie de Lyon.

Si vous connaissez une méthode plus simple, n'hésitez pas à me la communiquer en commentaires :)

Rosenheim OSM-Daten Vergleich 04/2010 mit 10/2017

Posted by Andreas Binder on 7 October 2017 in German (Deutsch)

Vergleich OSM 04/2010 10/2017 Rosenheim

Location: Innenstadt, Rosenheim, Oberbayern, Bayern, 83022, Deutschland

Meine bisherigen Geräte mit OpenStreetmap-Karten

Posted by Andreas Binder on 7 October 2017 in German (Deutsch)

Nachdem auch meine Hardware vergänglich ist, fange ich hier mal an ein paar Erinnerungsfotos zu sammeln. Alle dargestellten Kartendaten stammen aus Openstreetmap-Daten, d.h. "(c) OpenStreetMap-Mitwirkende"

Nokia E50

  • Nutzung: von 2008 bis 2014
  • Hardware: Nokia E50 in Verbindung mit einer Bluetooth-GPS-Maus (Haicom BT-401, Route 66 Bluetooth/Royaltek RBT 2010 und TomTomGo910) NokiaE50_AFtrack1.11_Route66_P1130022.JPG
  • Hauptanwendung: AFTrack 1.1 (c) A. Fischer NokiaE50_AFtrack1.11_Route66_Screenshot.jpg
  • Nebenanwendung: GpsMid 0.6 NokiaE50_GpsMid0.6_Route66_Screenshot.jpg


  • Nutzung: 2011 bis 2016 (ab 2007 auch als GPS-Tracker) TomTomGo910_Navit5996_P1130004.JPG
  • Hauptanwendung: Navit 5996 TomTomGo910_Navit5996.png

iPhone 5s

  • Nutzung: Ab 2014 (von 2011 bis 2014 als iPhone 4) iPhone5s_GPS-Tracks_P1130026.jpg
  • Hauptanwendung: GPS-Tracks iPhone5s_GPS-Tracks_IMG_8454.PNG

Garmin Dakota 20

  • Nutzung: Ab 2014 Garmin_Dakota20_P1120997_P1130028.jpg Garmin_Dakota20_screenshot.png

Why I joined

Posted by philm12345 on 7 October 2017 in English (English)

I saw a write up in the Baltimore Sun about students at JHU hosting mapping parties. That was the first I heard about this fantastic project. Contributing in my spare time and trying to encourage my friends and co-workers to join the effort!

Trunk in a funk

Posted by mvexel on 6 October 2017 in English (English)

Here is how Wikipedia defines "Trunk road":

A trunk road, trunk highway, or strategic road is a major road, usually connecting two or more cities, ports, airports and other places, which is the recommended route for long-distance and freight traffic. Many trunk roads have segregated lanes in a dual carriageway, or are of motorway standard.

'usually'.. 'many'.. Adverbs that serve to muddle the definition: I still don't know whether a specific road can be classified as a trunk or not.

The OSM wiki has this to say:

Use highway=trunk for high performance or high importance roads that don't meet the requirement for motorway. In different countries, either performance or importance is used as the defining criterion for trunk – see #International equivalence and Highway:International equivalence for guidance on road classification in different countries.

Hmm. Equally noncommittal. But there are reference to places where more specific references are to be found. I am interested in the United States. So let's look there. The 'International Equivalence' section on the highway=trunk page says:

Surface expressway: A relatively high-speed divided road (at least 40 MPH with a barrier or median separating each direction of traffic), with a limited amount of intersections and driveways; or a major intercity highway. This includes many U.S. Highways (that do not parallel an Interstate) and some state highways. Wikipedia reference

..whereas the separate 'International Equivalence' page says for trunks in the United States:

Limited access highway with occasional grade level intersections, or major intercity highway where no motorway exists.

Not precisely the same, but I am starting to see a pattern. The definition of trunk, according to the people who wrote the wiki pages, seems to be a mix of technical and functional road classification:

  • Technical: Designed for speeds > 40 MPH, limited at-grade intersections.
  • Functional: Major inter-city highway where no motorway exists.

Let's try and apply this to some major roads in Utah that I know well and are currently at least partly marked as trunk. (This Overpass query shows all trunk ways in Utah.)

US Highway 6 between Spanish Fork and I-70, currently marked as trunk in OSM. This is a two lane road with a speed limit of 65 MPH, with some exceptions in places. It is the main connection between the Wasatch Front and southeast Utah and southwest Colorado. There is no freeway alternative. **Conclusion: proper trunk.

State Route 154 or Bangerter Highway as it is known locally. Currently marked as trunk but some stretches are marked motorway as well. It is a 4-6 lane divided highway. Some sections have at-grade intersections (Continuous Flow Interchanges among them) but they are spaced pretty far apart. SR 154 is not a major inter-city highway, and there is a reasonable freeway alternative available. However, SR 154 does serve an important connector function between cities and towns west of Salt Lake City and the SLC International Airport. Conclusion: trunk is OK, but motorway sections should be downgraded.

US Highway 89. Currently only marked trunk between Farmington and I-84, where it meets the technical (if not the functional) definition of trunk. Most of the rest of US-89 is two-lane road with a speed limit of 65 or 70 MPH, with local exceptions. If you look at it purely from a functional perspective, only the stretch between Brigham City and the WY border in the North, and the (long) stretch from Provo south to the AZ border can be considered trunk. The section actually marked trunk currently is not part of either of these two. To my mind, the sections that serve important long distance connecting functions should be trunk as well. Conclusion: more sections should be trunk.

Looking at a few of the roads I know and their current tagging in the context of the current wiki definitions, my overall conclusion is:

A road should be tagged trunk in the United States if either of the following conditions are met:

  1. The road is designed for speeds > 50 MPH and has limited at-grade intersections.
  2. The road is a serves an important inter-city connector function, and there is no freeway alternative.

Small stretches where condition 1) is not met, for example a reduced speed limit in a built up area, should be tagged trunk to maintain a continuous classification.

Pretty? No. Works for me? I think so. What do YOU think?

10 years of OSM data history

Posted by tyr_asd on 6 October 2017 in English (English)

Tomorrow is the 10 year anniversary of OSM's API version 0.5. This is the version of the OSM-API that first exposed (among other things) the version number on all OSM objects, making it possible to access the full history of every object modification from this point onward.

This means that very soon, the full history planet file published on will contain more than 10 years of editing history which can be investigated, evaluated and analyzed (using tools like the OSM history database oshdb that's currently under development at HeiGIT on the University of Heidelberg, which I presented earlier this year at the State of the Map).

Of course, OpenStreetMap as a project exists for a bit longer than that (about 13 years now) and there was already quite some data mapped before the OSM API 0.5 was introduced 10 years ago.

Here's an interesting side note: There already existed a history call in OSM's API 0.4 (and apparently even in 0.3, see the comments below), but unfortunately this historic data apparently hasn't been preserved in the newer versions of the OSM API, meaning that it is also not available in the (relatively) easy to use full-history planet dumps which are available nowadays. As far as I can tell, this "prehistoric" OSM data has basically been lost (though some of it might be reconstructible by analyzing the list of very old planet dumps on Does someone of you perhaps know what exactly happened to that data back then?

(Cake made by Liz LeBreuilly, picture uploaded by Blackadder, CC-BY-SA-2.0.)

Location: Neuenheimer Feld, Neuenheim, Heidelberg, Regierungsbezirk Karlsruhe, Baden-Württemberg, 69120, Germany

2017 Sichuan landslide aftermath

Posted by ff5722 on 6 October 2017 in English (English)

On 24 June 2017, a big landslide occured in China's Sichuan province, burying dozens of villagers alive. Although pictures from the ground clearly showed that most victims didn't have a chance for survival, satellite imagery shows the scale in one glance: (source: ESA Copernicus Sentinel 2. 19 February 2017 and 7 September 2017.)

Some OSM users started mapping buildings in the area immediately afterwards. Pretty much the entire built-up area of one village was buried.

Thanks to the freely available Sentinel-2 data, you can map objects as recent as a month old. It's a shame not much of the data is available in a readily usable image format, for now, processing it can be a time consuming job.

Location: 104乡道, Diexi, Mao County, Ngawa Tibetan and Qiang Autonomous Prefecture, Sichuan, China

Krutspils, Jēkabpils

Posted by Jay May on 6 October 2017 in English (English)


Just corrected a couple of things in Krutspils (Latvia), but that area is a catastrophy.

Could you please help me?

Kind regards,


Posted by haqeroo on 6 October 2017 in Spanish (Español)

en estos momentos me encuentro actualizando la cartografía de Babahoyo, he notado que hay conflicto con otros usuarios, y no me deja corregir bien

Location: callejón 4, Babahoyo, Los Ríos, EC120150, Ecuador

Ipsden, Oxfordshire

Posted by silver mapper on 5 October 2017 in English (English)

Walked the northern half of Ipsden today on the latest stage of my parish-by-parish walks in the Oxfordshire Chilterns. It was magnificent, with a mixture of woodland and superb open views on a gloriously sunny October day. It surpassed anything I had walked to date. We are blessed in this part of Oxfordshire with the sheer number of Public Rights of Way that give us an endless choice of walks. It caused me to think as I roamed: I remember the road atlases that displayed a green ribbon alongside roads considered to be scenic. I imagined such a feature in OpenStreetMap, seeing the views along the various paths today. I have to satisfy myself with viewpoints, perhaps. I express my gratitude to the Chiltern Society for the work its officers, path representatives and maintenance teams do in helping to provide such a beautiful environment. I offer my thanks, too, to Woodhouse Farm for making available a permissive footpath and bridleways that so enhanced my walk today. I invite anyone who can access this area to do so. You will not be disappointed.

Location: Ipsden, South Oxfordshire, Oxfordshire, South East, England, United Kingdom

When do people map in Poland?

Posted by RicoElectrico on 4 October 2017 in English (English)

Here's another analysis made with ChangesetMD. I looked at average changeset count in each hour of the week for Poland. Week begins on Monday (pn).

Some trends are quite interesting. For instance, on Friday evenings people would rather party than map ;)

Also, we can see a little drop on business days around 17. I guess that people are going back from work? Does this imply they're mapping at work shortly before? :>


Cycle node networks and mountain passes

Posted by Richard on 4 October 2017 in English (English)

I've just added support for a couple more tags to's directions and thought it worth mentioning - everyone likes seeing their mapping being used.

First up, now includes 'knooppunten' (cycle node networks) in turn-by-turn directions. These are found in the Netherlands, Belgium and parts of Germany, and help you navigate dense cycle route networks. Here's an example:

Knooppunten example

This picks up rcn_ref= or lcn_ref= tags on nodes. also includes mountain passes in the turn-by-turn directions, for people who like riding somewhere hillier:

Mountain pass example

These are nodes (on highways) tagged natural=saddle or mountain_pass=yes with a name tag. If there's an ele tag, this will be output too.

Live in Western Europe now; will be in North America in the next update in a week or so's time. mapping and routing is updated from OSM roughly once a month. And thanks to everyone who has added knooppunten and mountain pass info to OSM!