Users' diaries

Recent diary entries

My talk for State of the Map 2016: Building large-scale crowdsourcing communities with the Humanitarian OpenStreetMap Team

Posted by dekstop on 21 November 2016 in English (English)

I just saw that the video for my SotM16 talk has already been online for a month... many thanks to the organisers and video team in Brussels for making this happen so quickly, and in such a high quality! You can find some summary notes further below, along with recommendations to HOT organisers.

The recording: Youtube: Building large-scale crowdsourcing communities with the Humanitarian OpenStreetMap Team

You can get the slides here: Slides: Building large-scale crowdsourcing communities with the Humanitarian OpenStreetMap Team

(This was recorded at the tail end of an unusually busy summer, after a couple of weeks of deadlines on little sleep, in a morning slot, with little time for rehearsal... throughout these short 30 mins I really, really wanted to go back to bed. If you know me a little you might notice it in the recording, everyone else may simply think I'm a little slow :)

Among the key observations to date

The talk summarises much of my research to date. It includes updated statistics and visualisations, and the results of three studies of HOT community engagement.

Over the course of this work, I've stopped thinking about community engagement as a process of "converting" people. Instead I now also think of it as a process of discovering and activating the right people: many of our most prolific contributors were already prepared to be engaged. Maybe they were looking for community, for a spare-time activity that has a bigger impact than just watching TV; maybe they already had some GIS experience and didn't know they can use it for a social purpose. In this sense, fostering community engagement is as much about the initial recruiting process as it is about the actual contribution process.

Among the key observations to date:

  • HOT is now a key source of community growth for OSM: among the 32,000 HOT contributors to date, 80% are newcomers to OpenStreetMap! (I have not yet investigated whether they then also contribute to other parts of the map.)
  • Over their contributor lifetime, 50% of HOT mappers dedicate at least 65 minutes to their contributions. This may sound like a small average for a volunteering organisation, but for an online platform it's a massive achievement.
  • Emergency response events can also be key recruiting moments: during HOT activations for Typhoon Haiyan, the Nepal earthquake in 2015, the earthquake in Ecuador in 2016, and others, many new volunteers joined HOT.
  • ... and much, much more.

Recommendations to organisers

In the talk I also make some recommendations to HOT organisers, based on study findings, and informed by my interactions with the wider community:

  • During large disaster events, carefully manage the tasking manager task listing. People who join during these events don't tend to stay active for long, and their contributions tend to have a lower quality. Point them towards newcomer-friendly projects where they can make some early experiences.
  • At the same time, HOT can likely benefit greatly from a notification mechanism for contributors who are interested in future campaigns. Currently there is no good means of reactivating mappers who have already made some early experiences. Instead we rely on our volunteers to discover new campaigns on the mailing list or on social media. While this may work for the core community, there is likely a larger number of mappers who may be willing to help out again. How can we best inform them when they're needed?
  • Generally, try to connect newcomers to the existing community as soon as possible, and do so in a setting that is appropriate for absolute beginners. The mailing list works well for a few hundred core contributors. Yet as we grow, is it still the best default location for a newcomer who has a question for an expert?

Homemade globe

Posted by Skippern on 21 November 2016 in English (English)


My son have just completed a globe based on Sérgio's map. Still some minor flows in our work process, but watching how he enjoyed it, and how satisfied he was with the result, I guess there will be more of these. Probably need to look into thicker paper, and a more suitable glue. First round kept my kids busy for one weekend. I had to interact at several stages, i.e., he needed help with the outline of Russia and Canada, he was not sure he was able to cut the lines himself, and with the glue we used, I had to do the gluing while he watched.

Location: Parque Areia Preta, Centro, Guarapari, Microrregião Guarapari, Greater Vitória, Mesorregião Central Espírito-Santense, Espírito Santo, Southeast Region, 29200260, Brazil

Indoors at Wherecamp Berlin 2016

Posted by SimonPoole on 21 November 2016 in German (Deutsch)

Two weeks back I was invited to Wherecamp Berlin, on the one hand to participate in the opening panel and on the other to have a short talk on the state of indoor mapping, more about that later.

Naturally the foreseeable impact of self-driving vehicles and machine learning in general was the, obvious, main topic of the opening panel. But outside of “things are going to change” I’m not sure that there was any other conclusion from a couple of oldish men without crystal balls.

From an OpenStreetMap point of view it was encouraging to see so many OSM based projects and operations presenting at the event mingling with essentially all the big names in geo-business.

Stefan from GraphHopper presenting Stefan from GraphHopper presenting at Wherecamp Berlin.

From a bit of a nerdy view, the first day presentations from Qualcomm, Broadcom and Google on what we will likely be getting in the way of GNSS support in upcoming mobile phones was quite interesting.

At the conference the first phone (the Aquaris X5 Plus) officially supporting the Galileo system was presented together with hackathon arranged around it. I didn’t get to actually testing one, so no further comment on if it actually worked and if there was any noticeable improvement. This seemed to be part of a marketing campaign that will lead up to Galileo being declared operational this December if all goes well. This probably doesn’t really mean much from a practical point of view as the number of working and commissioned satellites will still be rather low, but it probably does indicate that Galileo is slowly becoming real.

Qualcomm however did announce in their talk that all phones based on a current Snapdragon processor should support Galileo, naturally likely needing a corresponding firmware upgrade first. Slightly humorous was numerous of the presenters referring to the Samsung Galaxy S7 as an example of such a phone, even though in Europe the S7 uses a Samsung Exynos processor (which however, even though not documented, I suspect will support Galileo too).

Perhaps the most interesting talk in the series was from Broadcom on their project to develop a dual frequency consumer grade GPS chip. Dual frequency GPS chips have up to now been the domain of survey equipment manufacturers and the military. Naturally it is questionable if this technology will actually make its way in to real consumer devices, but if it does, we will get significant better GPS data without resorting to using DGPS with external reference stations.

This brings us to the last of the three GPS related topics: as you may have heard google will be supporting receiving “raw GPS data” from your mobile phones chip set (if it supports in the 1st place) from Android Nougat on. This implies that you could use your phone as a “rover” in a typical RTK setup or simply post process GPS data for better results. But this really all only makes sense if you have access to reference data and if google is going to provide something in the way of that is currently completely unclear.


Besides inviting me to the opening panel, the organizers had twisted my arm a bit to participate in the afternoon session on indoor mapping in OSM. Background: slightly over two years back I was involved in the effort to devise a reasonably consistent and simple tagging scheme (see: ) to replace the previous IndoorOSM tagging that was a bit popular at the time, but had a couple of technical problems and was in general rather complicated. The result of that work is SIT, but when we were working on the scheme we had one big problem: we really didn’t have any working code and only a small number of examples to work with and so when we finished the first version of the specification in 2014 it was not really clear if everything we had designed would work.

IndoorOSM blue vs SIT red Floor plan elements in OSM, IndoorOSM blue vs. SIT red.

Fast forward to 2016, those of you that participated in SOTM 2016 may have seen by the talks by Cynthia Gutton. Antoine Riche and Adrien Pavie on the SNCF mapping 388 french train stations. The tools (among others iD-indoor and openlevelup) developed in parallel and for this project, brought indoor mapping large steps towards being, even if not completely mainstream, something that can be reasonably done in OSM. Antoine and Adrien repeated their SOTM talk in Berlen, and additionally we saw presentations from DB (Deutsche Bahn), Mentz, and OpenStationMap on their mapping of train stations in Germany and elsewhere.

One point that I stressed in my talk at the end of the session, is that while from a number of aspects indoor mapping is a good fit for OSM, for example because we can seamlessly integrate pedestrian and accessibility routing outdoors and indoors, if comes at the cost of extreme amounts of details that make editing essentially impossible without dedicated editor support. Adrien has already proved that this can be done in a reasonable fashion with iD-indoor, not to be outdone I threw together a proof-of-concept for Vespucci for the conference (in the mean time this has reached a quite stable status).

Main station Berlin

Berlin main station in Vespucci indoor mode.

In other News

One of the more intriguing presentations on Sunday was from the company TerraLoupe “Aerial large scale landmark detection via deep learning". While who is actually the contractor remains in the dark, the interesting aspect was using machine learning to identify objects (for example emergency phones), text on street signs etc. along German motorways by using high resolution oblique aerial imagery.

Also of note was the presentation by Holger Dietrich on a version of the Wheelmap app with support for google Tango devices (currently the only such non-developer device is the Lenovo Phab 2 Pro), which allows surveying 3D objects, in the case for Wheelmap for example the width of an entrance and step heights.

Slides from the talks are available from the conference webssite.

Чи настав час позбутись теґів wikipedia:xx?

Posted by andygol on 21 November 2016 in Ukrainian (Українська)

Це переклад допису Time to cleanup the wikipedia:xx tags? від PlaneMad

На поточний момент в даних присутні більш ніж 40 000 об'єктів, які позначені теґом wikipedia:lang=* який треба замінити на більш популярний теґ у форматі wikipedia=lang:*. Чи повинно це бути автоматизованим виправленням? Або потрібен загальний всесвітній проект, до якого будуть залучені всі учасники спільноти, щоб перевірити їх всі один за одним?


Перевіривши застосування теґу wikipedia:ru до об'єктів, виявилось, що основним місцем їх застосування є Україна. Більше ніж 28 тис об'єктів тут вже позначені теґом wikipedia, значення якого — переважно посилання на україномовні статті, тож перехід лише на використання лише теґу wikipedia не надасть жодної вигоди.

Отже тепер питання в іншому, можливо варто позбутись тегів wikipedia та wikipedia:lang та використовувати лише wikidata? Яку інформацію ми можемо втратити?

ви можете залишити вашу думку в коментарях до оригінального повідомлення. Якщо ви не володієте англійською, будь ласка, залишить ваш відгук тут.

Numeri civici in Italia

Posted by FraMauro on 21 November 2016 in Italian (Italiano)

Piccola analisi sui numeri civici in Italia, o almeno in gran parte di essa.

Metodi e precisazioni

  • mancano alcune Regioni, le più pesanti da estrarre
  • sono considerati solamente i civici inseriti come nodo
  • i dati sono del 13 novembre 2016
  • i dati della superficie e popolazione delle regioni sono presi da


Regioni considerate:

  1. Abruzzo
  2. Basilicata
  3. Calabria
  4. Campania
  5. Lazio
  6. Liguria
  7. Marche
  8. Molise
  9. Piemonte
  10. Puglia
  11. Sicilia
  12. Umbria
  13. Val d'Aosta
  14. Veneto

Regioni escluse

Le regioni escluse sono sei:

  • Lombardia
  • Trentino Alto Adige
  • Friuli Venezia Giulia
  • Emilia Romagna
  • Toscana
  • Sardegna

sono tutte regioni molto ben mappate, eccetto la Sardegna il cui unico motivo di esclusione è una dimenticanza


per ogni regione sono forniti i seguenti dati:

  • indirizzi: numero di indirizzi in valore assoluto
  • Superficie: superficie in km quadri
  • Abitanti
  • Comuni: numero di comuni della Regione
  • abitantiXindirizzo: letteralmente Abitanti/indirizzi, quanti abitanti sono presenti per ogni indirizzo inserito in OSM
  • superficieXindirizzo: letteralmente Superficie/indirizzi, quanti km quadri ha la Regione per ogni indirizzo inserito in OSM
  • indirizziXcomuni: letteralmente indirizzi/Comuni, quanti indirizzi inseriti in OSM ha la Regione per ogni comune
  • OrdineAbitantiXIndirizzo: L'ordine in classifica che ha la Regione in base alla variabile abitantiXindirizzo. La Regione con il valore minimo è la prima. Questa è la variabile in base alla quale è ordinata la tabella
  • OrdineSuperficieXindirizzo: L'ordine in classifica che ha la Regione in base alla variabile superficieXindirizzo. La Regione con il valore minimo è la prima.
  • OrdineIndirizziXcomuni: L'ordine in classifica che ha la Regione in base alla variabile indirizziXcomuni. La Regione con il valore minimo è la prima.


prima parte

|Regione    | indirizzi| Superficie| Abitanti| Comuni|
|Liguria    |     36132|    5416.21|  1566992|    235|
|Sicilia    |     67645|   25832.39|  5059917|    390|
|Veneto     |     36947|   18407.42|  4907883|    579|
|Piemonte   |     32308|   25402.00|  4397069|   1207|
|Val d'Aosta|       811|    3260.90|   126935|     74|
|Molise     |       543|    4438.00|   311004|    136|
|Lazio      |      9977|   17242.29|  5889168|    378|
|Marche     |      2468|    9401.38|  1543752|    236|
|Umbria     |      1302|    8464.33|   902475|     92|
|Campania   |      7111|   13670.95|  5842303|    550|
|Puglia     |      4067|   19540.90|  4068544|    258|
|Abruzzo    |      1011|   10831.84|  1326513|    305|
|Basilicata |       420|   10073.32|   571774|    131|
|Calabria   |      1221|   15221.90|  1967294|    409|

seconda parte

|Regione     | abitantiXindirizzo| superficieXindirizzo| indirizziXcomuni|
|Liguria     |              43.37|                 0.15|           153.75|
|Sicilia     |              74.80|                 0.38|           173.45|
|Veneto      |             132.84|                 0.50|            63.81|
|Piemonte    |             136.10|                 0.79|            26.77|
|Val d'Aosta |             156.52|                 4.02|           10.96|
|Molise      |             572.75|                 8.17|             3.99|
|Lazio       |             590.27|                 1.73|            26.39|
|Marche      |             625.51|                 3.81|            10.46|
|Umbria      |             693.15|                 6.50|            14.15|
|Campania    |             821.59|                 1.92|            12.93|
|Puglia      |            1000.38|                 4.80|            15.76|
|Abruzzo     |            1312.08|                10.71|             3.31|
|Basilicata  |            1361.37|                23.98|             3.21|
|Calabria    |            1611.22|                12.47|             2.99|

terza parte

|Regione   | OrdineAbitantiXIndirizzo| OrdineSuperficieXindirizzo| OrdineIndirizziXcomuni|
|Liguria   |                        1|                          1|                     13|
|Sicilia   |                        2|                          2|                     14|
|Veneto    |                        3|                          3|                     12|
|Piemonte  |                        4|                          4|                     11|
|Val daosta|                        5|                          8|                      6|
|Molise    |                        6|                         11|                      4|
|Lazio     |                        7|                          5|                     10|
|Marche    |                        8|                          7|                      5|
|Umbria    |                        9|                         10|                      8|
|Campania  |                       10|                          6|                      7|
|Puglia    |                       11|                          9|                      9|
|Abruzzo   |                       12|                         12|                      3|
|Basilicata|                       13|                         14|                      2|
|Calabria  |                       14|                         13|                      1|


I numeri mostrano ancora serie lacune nella copertura dei civici. Mostrano anche una enorme differenza tra le Regioni.

Per la Liguria abbiamo 36.132 civici che corrispondono a 43,37 abitanti per indirizzo e a 0,15 km quadri per civico. Questi sono numeri che sicuramente mostrano delle lacune, ma che sono abissalmente migliori di quelli della Calabria: 1.221 civici che corrispondono a 1611,22 abitanti per indirizzo e a 12,47 km quadri per civico.


Se qualcuno ha spunti o osservazioni, sarei molto interessato a leggerli. Anche una spiegazione su come inserire tabelle nei diari sarebbe molto interessante!

Time to cleanup the wikipedia:xx tags?

Posted by PlaneMad on 21 November 2016 in English (English)

There are over 40,000 features with old style wikipedia:lang=* tags that need to be migrated to the more popular wikipedia=lang:* format. Should this just be a mechanical edit? Or should we have a worldwide campaign of community members checking each and every one?

screenshot 2016-11-21 11 48 22



Looked into the features with wikipedia:ru and the majority seem to be place nodes in Ukraine. Around 28k of them already have a wikipedia (mostly Ukranian) tag, so maybe migrating them may really not have any added benefit.

So the question now is, if its better now to discard the wikipedia and wikipedia:lang tags and just have a wikidata tag? What information would we lose?

screenshot 2016-11-21 14 47 22

App wanted: Collect opening hours by place automatically, and easier user notes

Posted by CloCkWeRX on 21 November 2016 in English (English)

Right now I am sitting very close to a place in Adelaide - San Churro. I know its mapped, at least with name.

However if I search for "openstreetmap san churro", I see:

  • Very rich data on opening hours (google), how long people spend at a location
  • A business listing and map (google)
  • A prompt to claim this business (google)

Contextually, my android phone already knows where I am so is potentially limiting the search to nearby businesses.

Previously I've been keen on a foursquare 'checkin' app to write to OSM and ask smart questions, as well as RDFa/ markup to render useful results.

I'd like to go further and throw out a few feature requests with a bounty attached ($100 AUD each):

  • On android or ios, add a plugin to Owntracks to allow check-in to an Openstreetmap location, publishing Lat/Lon, OSM id or new place name(suitable for a note)
  • A way to connect to an Owntracks/Mqtt server and match user location/time to a 30 minute time slot (ie: indicating a likely valid opening hour)
  • A public owntracks server for interested OSM users (worldwide? Or just country based)?
  • An owntracks plugin for OSMand.

Заготовки тегов POI для JOSM: версия 2.0

Posted by literan on 20 November 2016 in Russian (Русский)

Серьезно проапгрейдил набор заготовок тегов для JOSM (о предыдущей версии см. здесь Помимо ряда новых магазинов, кафе и т.п. добавлено следующее:

  • Типичные для России медицинские учреждения (больница, роддом, санаторий, травмпункт и т.п.), с учетом схем тегирования Healthcare и Healthcare 2.0.

  • Типичные для России образовательные учреждения (школа, детский сад, спорт.школа, муз. школа и т.п.), с учетом схем тегирования Education и непринятой Education 2.0.

  • Основные государственные учреждения (пенсионный фонд, прокуратура, следственный комитет, налоговая, центр занятости и др.)

  • Основные микрообъекты городской инфраструктуры (тепловые пункты, паркоматы, почтоматы, велопарковки и т.д.).

Например, при выборе художественной школы добавляются следующие теги: amenity=training education=facultative_school education_form:parttime=yes education_level:primary=yes education_profile:visual_art=yes education_system:ru_standard=yes name=N-ская художественная школа ownership=state training=art

Файл заготовок находится по ссылке:

Как установить - описано здесь

UPD: теперь эти заготовки есть в списке добавляемых пресетов в редакторе JOSM (Настройки - третья кнопка сверху (с глобусом) - вкладка "Заготовки тегов" - пресеты "Московские заведения" и "Русские заведения"), спасибо Zverik.

pilates center cadiz

Posted by Ale lopez on 20 November 2016 in Spanish (Español)

lugar de referencia en el casco antiguo de cadiz para practicar pilates en maquinas y suelo

Location: Calle Antonio López, Cádiz, Andalucía, 11004, España

ЕженедельникОСМ 330

Posted by Sadless74 on 20 November 2016 in Russian (Русский)



О нас

  • Организации OSM Foundation необходимо набрать € 70.000 для покрытия основной части операционных издержек. Поэтому Mapbox объявил в прошедшую пятницу о паритетном сборе пожертвований: "Mapbox будет удваивать следующие €10,000, поступивших от участников“ для достижения цели. На сегодняшний день осталось собрать €18,028. Пожалуйста, помогите сохранить ОСМ "на плаву" (в рабочем состоянии).


  • Adrien Pavie представил Pic4Carto, веб-сайт который совмещает недавние фото из Mapillary, Flickr и Commons чтобы картографы могли с лёгкостью просматривать фото со всех трёх сайтов. Он также выложил исходный код к нему.

  • CartInnov (автоматический перевод), совместная и открытая карты движителей прогресса во франкоговорящем мире.

  • [1] Отладочная карта OSRM (о которой мы уже писали) теперь также отображает штрафы за повороты.

  • Markus Schalke отметил запрос на добавление башен для птиц в email рассылке о тегах.

  • Daniel хочет добавить тег для "разворот запрещён" для улучшения навигации при прокладке маршрутов, и объясняет в подробностях зачем это нужно.

  • Warin предложил в email рассылке о тегах расширить возможности картографирования футбольных полей.

  • Joost Schouppe предложил тег для собачьих туалетов. Там есть несколько предложенных названий для тега на выбор.

  • James открыл задачу в менеджере задач канадского сообщества ОСМ, чтобы перенести wikidata в OSM. LogicalViolinist объясняет что это такое в своём блоге. Пожалуйста ознакомьтесь с тем, что написал James о is_in:.

  • Tbsprs дал ссылку в твитере на OpenLevelUp!, инструмент для картографирования в помещении.


  • Голландский журнал Computerworld перечисляет список (автоматический перевод) из четырёх проектов, которые вот-вот "пойдут по миру". OSM является одним из них, так как цель собрать €70,000 пожертвований ещё до конца не достигнута. Время сделать добровольный взнос.

  • На GitHub в обсуждении "стандартного" стиля OpenStreetMap Carto (который красуется на веб-сайте озадачиваются вопросом: почему сравнительно мало вкладчиков, и интересно, почему некоторые функции (например, придорожные святилища) всё никак не могут появиться.

  • При непосредственном содействии Gonzalo Pérez из аргентинского сообщества OSM, был проведён семинар по составлению карт и практические занятия, организованные Santalab и научно-исследовательским центром Mediatizations, в городе Росарио, Санта-Фе.

  • Santiago Crespo сообщает, что испанское сообщество ныне так же использует приветствие осмерам по-бельгийски, штуку, придуманную бельгийским сообществом (а точнее M1dgard). Pascal Neis уже зарегистрировал новых пользователей.

  • "kaxtillo" в своём дневнике подводит итоги (перевод) об участии OSM-а в 3-ей лаборатории гражданских инноваций в Колумбии - Labicco (перевод), целями которой были содействие инициативам граждан в Латинской Америке для изменения социальной сферы, демократического управления и социального, культурного и экономического развития.

  • "Парковка велосипедов не проблема, а часть решения: в Амстердаме 265 000 машиномест, и на них можно разместить 2 100 000 байков!", как говорит "профессор велосипедных наук" из Urban Cycling Institute. Он иллюстрирует предлагаемое (автоматический перевод) решение этой проблемы с помощью карт OpenStreetMap.

  • Pascal Neis обновил свой анализ деятельности членов OpenStreetMap в течение этого года.


  • Неделя Просвещения Географии с OSM (OSMGeoweek на Github) направлена на то, чтобы восславить географию и OSM с помощью более чем 136 событий по всему миру. Это дополняет инициативу Национального географического общества со многими местными и гуманитарными проектами картирования.

Гуманитарный OSM

  • "Погодный центр Красного Креста" в Дар-эс-Саламе, Танзания, сообщает о следующем семинаре с несколькими партнёрами. На втором этапе запланированы мероприятия при поддержке OSM по созданию планов застройки, защиты от наводнений и развития инфраструктуры.

  • HOT просит у сообщества оставить отзыв о вашем выборе платформы, которая бы лучше подошла для тренировок вживую. Пожалуйста, ответьте на три вопроса!

  • Mapathon устроенный в Ivry-sur-Seine (Париж, Франция) при поддержке cartONG объединил картографов и членов местного сообщества в Мали. Вместе они сделали карту Dianguirdé, Мали, добавив около 337 км дорог.


  • Французское министерство по окружающей среде, энергетике и морю организуют хакатон под названием #HackRisques. Его цель предотвращать природные опасности. Помимо Meteo France, сообщество OSM также приглашено к участию как отметил Sebastian Dinot в OSM-talk-fr.


  • Thomas Konrad опубликовал austriaaddresshelper, плагин для Java OpenStreetMap Editor (JOSM). Он автоматически присваивает адреса объектам, используя обратный адресный геокодер, основанный на данных, опубликованных австрийским федеральным бюро метрологии и геодезии.

  • Frederik Ramm ищет разработчиков и администраторов заинтересованных в настройке и обслуживании песочницы для тестирования API OSM.

  • OSRM RC версии 5.5 включает в себя множество интересных изменений. Теперь он поддерживает oneway=reversible вместо oneway=alternating, направления для тега destination и содержит эвристику для углов поворота.

  • В списке рассылок, Martijn van Exel рассказал как OpenStreetView попросили сменить имя "широко известной компанией со схожим названием продукта". И как обычно anonymaps быстро выдвинули своё мнение о "расширенном уважении к торговым маркам" Google.


  • Mapzen описывает новую функцию import движка Tangram и использование GLSL шейдеров на примере стиля TRON 2.0.

  • Railnialtial представил библиотеку для Python OSMnx. Которая была написана к его диссертации, и позволила визуализацию и анализирование данных об улицах.


  • Программа Версия Дата релиза Комментарии

  • OSRM Backend 5.4.3 2016-11-08 Исправлены ошибки.

  • Mapillary iOS * 4.5.5 2016-11-10 Исправлены ошибки.

  • libosmium 2.10.0 2016-11-11 Слишком много изменений, читайте списки изменений.

  • Mapbox GL JS v0.27.0 2016-11-11 Множество улучшений и исправлений, читайте списки изменений.

  • Komoot iOS * 8.4.2 2016-11-13 Переработана галерея.

  • Komoot Android * var 2016-11-14 Малые изменения.

  • Android * var 2016-11-14 Исправления ошибок и новые данные карты.

список предоставлен OSM Software Watchlist.

(*) не свободный софт. Определение не свободности.

А вы знаете …

  • ... Liberland, это новая "страна" которую никому нельзя посещать? Hacker News написали о ней более подробно и Википедия описала конфликт границ который привёл к её "созданию".

  • ... Framacarte, использует uMap как часть направления по обезGoogleиванию интернета?

  • ... что Comenius поддерживает проект MychOSM? В этом проекте есть много идей как можно использовать OpenStreetMap в школах.

OSM в прессе

  • Генеалогическое сообщество Ирландии отчиталась в его втором издании (PDF - смотреть страницу 2): "В начале октября соревнование по отрисовке городских земель на острове Ирландии было проведено в Берлине. Оно было на ежегодной всемирной конференции сообщества OpenStreetMap". "" их главный веб-сайт.

Другие “гео” события

  • Archdaily сообщает о коллекции карт David Rumsey в высоком разрешении (о которой мы уже писали раньше) теперь включает в себя более чем 71,000 карт для загрузки.

  • Компания Apple получила патент на карты с дополненной реальностью.

  • Hajime Narukawa, японский архитектор придумал проекцию карты, такую, что напечатанную карту можно превратить в идеальный 3D глобус. За его работу он получил Good Design Award. Мы уже писали на прошлой неделе о OSM Dymaxion Projection сделанной Бразильским архитектором Sérgio A. J. Volkmer.

  • Google закрывает Map Maker 31 марта 2017, перенеся редактирование POI в Google Maps, и пользователи больше не смогут изменять геометрии. Интересно, станет ли это новым скачком для нашего сообщества.

  • В порыве создания и поддержки машинного обучения используя спутниковые снимки, DigitalGlobe, CosmiQ Works и NVidia запустили SpaceNet Challenge. В первом раунде, нужно добиться автоматизации извлечения 2D зданий со спутниковых снимков. На кону стоят призы стоимостью $34,500.

  • Surveillance under Surveillance проект по визуализации данных по наблюдению. Проект, на данный момент доступен на Немецком, Английском и Испанском, и ищет (автоматический перевод) переводчиков для расширения на другие языки.

  • Google Street View против Mapillary: Greg Oates, Skift Digital, описал - используя примеры - цели, возможности и ноу-хау обоих противников.

Предстоящие события

Османд испортился

Posted by Shoorick on 20 November 2016 in Russian (Русский)

После того, как телефону был сделат factory reset, туда удалось поставить свежий OsmAnd 2.5.3 вместо прежнего 1.9.*

Новый османд выглядит симпатично и кое-что в нём улучшили, но толку в этом нет, потому что пользоваться таким османдом совершенно невозможно: на моём «Катерпиллере» он нещадно тормозит, а вместо мелкомасштабных карт рисует пустоту.

Видимо, придётся снова пробовать

A Good Walk, Mapping

Posted by alexkemp on 20 November 2016 in English (English)

To distract me from the difficulties of mapping the houses within Manderley (a recent development of £400,000 GBP houses ($494,000 USD, €467,000 Euro), half of which do not yet appear on Bing) here is a useless challenge for you:–

Find the Tree Rat

Non-golfers are warned of the danger of death from hi-speed golf-balls, and therefore not to trespass on to Mapperley Golf course. However, I walked all around the perimeter of the course, and took pictures every few seconds the whole way. At one point I came across some of the local wildlife; it tried to hide from me but I did manage to get a single frame with it in view.

Your mission, should you choose to accept it, is to (virtually) walk the perimeter of the Golf Course. As a virtual walk protective head-, elbow- & knee-gear are optional.

So, starting at the first frame of the walk, find the tree rat (sorry, squirrel). Be warned that the only way I could get it in shot was to photograph from a distance, so it is small & well blended in with the tree trunk as it rushes to get away from me. If you reach the houses then you have missed it (although the walk continues after the houses are mapped until we reach the clubhouse).

Golf:– a good walk, spoiled

words — wrongly — attributed to Samuel Langhorne Clemens (Mark Twain)

After surveying the desert of Manderley — it was midday Wednesday, 16 November & the place was almost entirely devoid of human life — I walked clockwise around Mapperley Golf course starting at the traffic lights at the top of Arnold Lane (having bought Pink Floyd's single + LP as a young man I love that road just for it's name), passing through Digby Park along the way (check out the Alphabetical Arboretum if you think that you can identify every tree & bush from it's leaves) & finishing at Mapperley Golf Club-house. The Golf Course is full of dire signs warning walkers of imminent death, so the walk does not dare trespass upon the course but instead circumnavigates the perimeter.

It is late autumn, far too warm for the season & too many leaves on the trees. There are many fine views across the golf course from the walk. Here is one; you can spot the Manderley houses at the top right-hand side:–

gedling golf course

The land is owned by Gedling Borough Council but run as a golf course by a private body, so there is a small chance that it will not be redeveloped in the next 10 years (I bet that they have talked about it).

All the land south of Plains Road was probably originally owned by the Digby Coal Company, who operated Gedling 1 & 2 until 1937 (Top Hard, Main Bright & High Hazels seams), when it was taken over by B.A. Collieries, Ltd., then nationalised in 1947. I was told by a householder early in my walk, shortly after the Mapperley Top shops, that his land was originally purchased in 1934 from Digby. That becomes even more clear as you pass the Colliery football & cricket pitches.

Gedling Shafts were finally closed in 1991, even though in 1980 it was said to have a “long-term future”. Thanks, Maggie. This is a Nottingham Evening Post picture of the Gedling Headstocks:–

gedling colliery headstocks

...and these are the spoilheaps today from the other side of Arnold Lane (the council is planning to redevelop those green hills (pdf)):–

gedling pit land


This is the squirrel-frame, if you cannot find it.

Location: Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Currently working on...

Posted by jpennycook on 20 November 2016 in English (English)

I'm currently working on corridors for walking and cycling:- 1. North/northwest of Peterborough, cycle routes to avoid the A15 2. Reading/Wokingham/Bracknell/Ascot, including the proposed route of the NCN422 3. Farnborough/Frimley/Camberley to Bagshot/Lightwater/Woking

I've got about 3 months worth of backlog data

Serving Vector Tiles

Posted by pnorman on 20 November 2016 in English (English)

This is a repost from my blog because there's been a fair amount of interest from OSM people on what I wrote.

If you want to serve vector tiles, there are a few server options that have developed, each with different strengths and weaknesses.

node-mapnik based

Language: nodejs
Layer definitions: Mapnik layer definitions in XML, typically preprocessed from YAML
Vector tile formats: Mapbox Vector Tiles
Data source support: PostGIS

Kartotherian, tessera, and other servers based on tilelive all rely on Node bindings to Mapnik to produce vector tiles. They all work with Mapnik layer definitions. This is a reasonably well understood language and consists primarily of a SQL statement for each layer. This is reasonably flexable and it's possible to do proper code review, git conflict resolution, and other processes you need with an open style.

Some servers can turn the Mapbox Vector Tiles into GeoJSON, but not all do. There are other minor differences, but they all have the same major advantages and disadvantages.

The biggest problem with these options is that you have to either use the exact same versions of everything as the Mapbox developers while hoping their changes work with your code, or lock down your versions to a set of known good versions and periodically update when you need new features, retesting all your code. Neither of these is practical for an open-source style which wants to involve others.

If you don’t do this, you’ll find parts of your server failing with different combinations of Mapnik and node-mapnik.

Tilezen tileserver

Language: Python
Layer definitions: SQL in jinja2 templates, YAML
Vector tile formats: Mapbox Vector Tiles, TopoJSON, and GeoJSON
Data source support: PostGIS

Tilezen tileserver was written by Mapzen to replace their TileStache-based vector tile generation. Having been written by developers who wrote previous vector tile servers, it combines ideas and functionality other options don't have.

The datasource definitions are written in SQL + YAML, a common choice, but unlike other options, the SQL is in its own files which are preprocessed by the jinja2 templating engine. This adds some complexity, but a great deal of power. Selecting different features by zoom level normally requires repetative SQL and lengthy UNION ALL queries, but the preprocessing allows queries to be written more naturally.

Tileserver's unique feature is the post-processing capabilities it offers. This allows vector tiles to be operated on after the database, altering geometries, changing attributes, and combining geometries. Post-processing to reduce size is a necessary feature if targeting mobile devices on slower connections. Mapbox had been working on this in the open, but now that they no longer use node-mapnik it's not clear how they do so. MapQuest had developed Avecado to specifically target this, but it became abandoned when they stopped doing their own map serving.

You don't need any AWS services for a basic Tilezen tileserver deployment, but there might be some dependencies in the more advanced features needed to set up a full production environment.


Language: Go
Layer definitions: SQL in TOML
Vector tile formats: Mapbox Vector Tiles
Data source support: PostGIS

Tegola is a new server written in Go. It operates with multiple providers which supply layers to maps, allowing them to be assembled different ways. It looks like it has most of the features needed for vector tiles for a basemap, but might be missing a few needed for changing data as zoom changes.

SQL in TOML is similar to SQL in YAML for layer definitions, and like this it is reasonably flexable and makes it possible to do proper code review, git conflict resolution, and other processes you need with an open style.

I haven't had a chance to deploy it yet, so I'm not sure what difficulties there are.


Language: Rust
Layer definitions: SQL in TOML
Vector tile formats: Mapbox Vector Tiles
Data source support: PostGIS

t-rex is a new server written in Rust. It's unique feature it that it can auto-configure layers from PostGIS tables. It does have all the required features for selecting appropriate data in a basemap.

It's layer definitions are different than Tegola's, but they are both SQL in TOML, and share the same strengths.

Like Tegola, I haven't had a chance to deploy it.


Language: Python
Layer definitions: SQL in JSON Vector tile formats: Mapbox Vector Tiles, TopoJSON, GeoJSON, and Arc GeoServices JSON Data source support: PostGIS

TileStache is a general-purpose tile server which Mapzen used to use a fork of to serve their Tilezen schema. They've switched to Tilezen tileserver, but the functionality they added has been merged back into TileStache. Unfortunately, the documentation hasn't caught up yet, so there's not too much information about all of its functionality.

Deploying TileStache tends to be reasonable - particularly compared to node-mapnik - but the language of SQL in JSON is one that's a problem for open projects with multiple authors and prevents proper code review and git conflict resolution.


Language: C++
Layer definitions: Lua
Vector tile formats: Mapbox Vector Tiles
Data source support: OSM PBF and shapefiles

Tilemaker is built around the idea of vector tiles without a serving stack. It does this by doing an in-memory conversion directly from OSM PBF data to pre-generated vector tiles, which can then be served using Apache, a S3 bucket, or any means of serving files from disk. This vastly simplifies deployment and reduces sources of downtime.

For serving a city or most countries this can be the ideal method, but the same strengths that make it good for this are a problem for processing the planet. It takes large amounts of RAM, can’t consume minutely changes, and has to create vector tiles for the entire PBF at once.

Tilemaker is also the only server to support directly using shapefiles for low zoom data and OSM for high zoom. Other options require loading into PostGIS and using SQL that selects the appropriate data based on zoom.


Language: Python
Layer definitions: osmfilter options
Vector tile formats: o5m
Data source support: OSM PBF and other raw OSM data

VectorTileCreator is part of KDE Marble and takes the unique approach of creating tiles of raw OSM data. It uses osmfilter's language for filtering OSM data, but lacks the means to use other data sources, something most maps will need. The support of o5m vector tiles is also limited. Like tilemaker it runs from the command line and produces a set of vector tiles.

Which should I use?

What you should use depends on your needs. First figure out what support you need for the full planet, updates, data sources, and output formats. If you need diff update support, then you need something that can create a single vector tile and Tilemaker won't work. If you need TopoJSON support, node-mapnik won't work.

For a table showing features supported, see the original blog post

Location: Uptown, New Westminster, Greater Vancouver Regional District, British Columbia, Canada

Pico y Placa = motorcar:conditional no @ (lastdigit_license_plate:1-2 AND Mo 7:00-19:00)

Posted by German C on 20 November 2016 in Spanish (Español)

¿Qué es pico y placa?

A las restricciones vehiculares en ciertas vias arterias de capitales de departamento en Colombia le llaman "pico y placa", es decir, no se pueden usar carros (coches) cuando el dígito menos significativo de la placa (número que esta en la derecha de la placa) cumple con la condicion del dia pico y placa.

¿Cómo son las placas en Colombia?

Las placas de carros en Colombia cumplen con la siguiente expresión regular [A-Z]{3}[- ][0-9]{3}, es decir inician con 3 letras del alfabeto gringo (nunca he visto una placa con la Ñ) y terminan con tres digitos decimales.

¿Cómo es un pico y placa en la mayoria de ciudades de Colombia?

Pico y placa Tunja

Disección de un tag (key=value) pico y placa en OSM

motorcar:conditional = no @ (lastdigit_license_plate:9-0 AND Mo 7:00-19:00) Traduce: Carros no pueden transitar si la placa termina en 9 a 0 y además es Lunes de 7am a 7pm.

Para construir la anterior condición me base en: Restricciones Condicionales, en Horas de apertura y en Acceso

Para poder aplicar esa condicion completa seria, dar un clic en una de las calles -la tarea seria en todas las calles- donde esta la zona en rojo (donde hay pico y placa) y agregar el tag: key -> motorcar:conditional value -> no @ (lastdigit_license_plate:9-0 AND Mo 7:00-19:00); no @ (lastdigit_license_plate:1-2 AND Tu 7:00-19:00); no @ (lastdigit_license_plate:3-4 AND We 7:00-19:00); no @ (lastdigit_license_plate:5-6 AND Th 7:00-19:00); no @ (lastdigit_license_plate:7-8 AND Fr 7:00-19:00);

Tag lastdigit_license_plate no existe

Como se observa el tag lastdigit_license_plate no existe, también había pensado en license_plate_lastdigit ó incluso un tag compuesto license_plate:lastdigit pero de acuerdo a uso, utilidad y popularidad el tag puede entrar en modo proposal y en un futuro ver los pico y placa implementado en aplicaciones OsmAnd o usando las API de OMS para crear un webapp.

On the corner of $FIRSTNAME and $LASTNAME

Posted by scruss on 19 November 2016 in English (English)

My name is a problem. Not merely is my first name often misspelled (and, where I now live, almost universally mispronounced) it's often assumed to be my family name. While it's pretty common for Scottish guys to go by their middle name, since they'll often have the same first name as their father¹, my first name really is my given name. It's just my luck that my family name is more common as a first name. Also, my name is really long; with my middle name, it's too long for Canada's ID system, so I have an “official” name² that's my real name minus a letter or two. I should just add LLC on the end and be my own legal partnership. Hence, it's a lot easier to go by my nickname.

A friend's rather odd quest to see how many of his Facebook friends had their names mentioned in Milwaukee streets led to me creating a list derived from OSM data³ for him. That got me wondering further: is there a city in the world where Stewart Street/Road/Avenue/… intersects with Russell Road/Street/Avenue/…?

Before I get preemptively banned from Overpass Turbo for life for thinking up the most futile way to heat up a server, I'll probably never do this. If I did, I should probably just look in New Zealand⁴, because it often seems — in place names, at least — to be more Scottish than Scotland.

¹: This can make lowland Scottish genealogy an interesting challenge. I think I've got something like five consecutive generations of Roberts marrying Agneses in my ancestry; imaginative we ain't. I do have to keep reminding myself that my lot were the ones who didn't have the get-up-and-go to become hillbillies.

²: no, I'm not getting all Freemen-on-the-Land nonsense on you here. Just in case you were getting worried.

³: it's here, along with instructions on how I did it: Milwaukee Street Names from OSM for Jeff

⁴: My ancestry does have a slightly more Highland branch, of whom I've written here before. My grandfather remembered his grandmother describing seeing the boats leaving to take the Stewarts of Appin to New Zealand during the Clearances.

Location: Bay View, Milwaukee, Milwaukee County, Wisconsin, United States of America

Aménagements cyclables à Pau et son agglomération

Posted by Jean Yves DEYRIS on 19 November 2016 in French (Français)

Je suis en train de mettre à jour les aménagements cyclables sur Pau te l'agglo...Je cherche de l'aide. Il y a t il des contributeurs palois qui travaillent sur le sujet. Me joindre à eux ou se joindre à moi ? Merci de vos réponses Lasser un commentaire sur le blog

Dandot RS ڈنڈوٹ آر ایس

Posted by Dandot RS Dalmian on 19 November 2016 in English (English)

Dandot RS (Urdu ڈنڈوٹ آر ایس) is a village, union council, and administrative subdivision of Jhelum District (Urdu جہلم) in the Punjab Province of Pakistan. It is part of Pind Dadan Khan Tehsil.

Location: Dandot RS NCI Man RD, Dandot RS ڈنڈوت آر ا یس, Sargodha District, Punjab, Pakistan

A Tale of 4 Seasons

Posted by alexkemp on 18 November 2016 in English (English)

Test out your detection faculties: what is wrong with this picture of the 4 Seasons?

3 Seasons

It was shot last Wednesday with the kind permission of the householder on Plains Road, Mapperley. Try to ignore the fact that the camera is within a cheap smartphone & that the operator still does not know how to manually control the contrast whilst mapping.

The answer, of course, is that one of the Seasons is missing (stolen!).

Although they look like marble, they are in fact made of fibreglass, and are thus nice & light. That is exactly what some youths discovered many years ago when first put in place, just before those youths absconded with the statues. The police discovered the abductors, but only three of the Seasons. The statues returned are now concreted into position (whilst they yearn & mourn for their sister, of course).

Location: Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Progress Report: Railway Crossings challenge for MapRoulette

Posted by MikeN on 18 November 2016 in English (English)

As previously mentioned in diary entry , the MapRoulette Rail challenge uses topological analysis of the rail network to generate the task list. Many tasks land on a multi-track crossing or include a rail yard, so many tasks correct fix more than 1 crossing per edit session. Also, anyone routinely reviewing an area might correct rail crossings outside of MapRoulette By re-analyzing current OSM data, finished tasks were marked off. Some findings for the last interval:

  • 1221 tasks marked complete in Map Roulette
  • 5468 tasks auto-marked complete after detection as fixed
  • 4.5:1 node correction per task ratio
  • Overall topological rail challenge 16% complete 10925 / 68758 tasks

Because the first MapRoulette tasks are more likely to land on in a 'busy' area, future fix rates and node correction to task ratio will probably fall as each task is more likely to point to an isolated crossing.

Many tasks end up making geometric corrections to the rails and surrounding roads.

The links to these challenges are:

[Crossing Ways: Highway-Railway, US]

[Crossing Ways: Pedestrian-Railway, US]

[Crossing Type: Highway-Railway, US]

[Crossing Type: Pedestrian-Railway, US]

There was a moment of panic as the analysis also discovered thousands of new tasks! This had 2 causes:

  • An abandoned rail line / cycle trail was changed to be a railway. I have commented on that changeset asking for more information.
  • A node from changeset was moved across the country near the following changeset in JOSM. From a history examination, I'm not sure if the rail node was attached to Benton Street. Maybe there is a JOSM hotkey that does this. To try to avoid this in the future, I have changed MapRoulette to open JOSM in a new layer.
Older Entries | Newer Entries