Users' diaries

Recent diary entries

The Ostler Jennings & Scot Grave Farm, Gedling

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

There is a splendidly-named 1903 house & land called Scot Grave Farm (farmhouse, farmyard) on Arnold Lane that I revisited today (on the older maps it is called “Scotgrave Farm”):

Scot Grave Farm house

The owner has both an old BT red phonebox & red Postbox in his yard:

Scot Grave Farm phonebox

I called to try to find more information about the very odd name but, unfortunately, he was unable to help on that score.

The Farm & house were built 1903 & coincide with the establishment of what became Gedling Pit (originally Digby Coal Company — the slopes of the pit spoil heaps can be seen behind the farm in the photo above). According to a U3A pdf Gedling Colliery began in 1899 and the sinking of shafts 1 & 2 were started in 1900. 27 seams of coal of varying — mostly small — thickness were found until they hit paydirt with the 5’ 2” (1.57m) thick Top Hard seam at 1405’ 0” (428.3m) and the earlier 3’ 9” (1.14m) thick Main Bright at 329m. The colliery finally began to commercially produce coal in 1902.

The farm was used by the pit to house the pit ponies, who were walked to & from the pit each day in two different shifts to work there (one returning as the other walked out). The current owner told me of a Mr Jennings (the final Ostler) & his daughter (Mrs Harrison) who moved to Australia, and wrote him a letter informing him of some of her life & the farm history.

Here is a Nottingham Evening Post picture of the Gedling pit ponies, ready for their 2-week holiday in 1960:

gedling pit ponies

The farm was unoccupied during the strike (probably he was talking about the 1926 General Strike, which was precipitated by the country-wide coal-miners' dispute). Pickets were camped outside the pit & raided the house for it's floorboards as to feed the braziers.

The field next to the farm is being prepped ready for development, as are all the slopes behind the farm (he said 100,000 houses) (that will take a little while to map!).

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

Inserção de dados relacionados a questões de Gênero - Mulheres no OSM

Posted by Camila Mello on 27 November 2016 in Brazilian Portuguese (Português do Brasil)

Olá, pessoal, hoje após a oficina aqui no State of The Map Lab, em São Paulo, as mulheres presentes do evento vão experimentar inserções de dados relacionadas a questões de gênero na América Latina... Hoje começo a navegar e mergulhar na comunidade! Feliz demais por encontrar essa comunidade!! AhÔ! #OSMintegra Camila Mello - São Paulo

"O que é o OSM" e "Como funciona" (PDF apresentação/presentation)

Posted by smaprs on 27 November 2016 in Brazilian Portuguese (Português do Brasil)

por sugestão da comunidade OSM-BR, apresento aqui para toda a comunidade OSM em língua portuguesa o PDF que fiz para apresentação sobre "O que é o OSM" e "Como funciona".
Fiquem à vontade para usá-lo, se lhes for útil para alguma apresentação, divulgação, etc.
O uso em PDF é útil por permitir o acesso direto aos links explicativos durante uma apresentação.


DOCX original:

(Livre para usar, fazer download, adaptar, distribuir)

Weekly roundup - common errors and unexplained edits observed

Posted by nammala on 27 November 2016 in English (English)

Here are the few observations from the OpenStreetMap edits between 11 November - 25 November. We looked into the filters like mass deletions, iD editor + mass deletions, possible imports, edited a name tag, mass modifications using OSMCHA for reviewing the changesets.


  • Deleted tracks: changeset
  • Added random pedestrian highways and buildings: changeset
  • Deleted highways and few buildings: changeset 1, 2, 3
  • Deleted buildings and some amenities: changeset 1, 2, 3
  • Incorrect tagging: changeset
  • Changed road classification: changeset
  • Deleted neighborhood tags: changeset
  • Added Korean names in name:en tag: changeset
  • Deleted streams: changeset

Community members commented on the following changesets:


  • Added province tags to address: Community member commented and reverted the changeset
  • Undiscussed import: Community member commented and reverted the changeset 1, 2
  • Deleted houses and residential roads: Reverted the changesets with a comment 1, 2, 3
  • Deleted buildings and roads. Community member commented and reverted the changeset.
  • Added orphan nodes over buildings and highways. we reverted the changeset with a comment

These were some of the inconsistent data for this week. Do keep an eye out and comment on changesets, which will make us maintain the quality of data in OpenStreetMap.

Look forward for another roundup next week.

New User Edits

Posted by Glassman on 26 November 2016 in English (English)

One of my goals is to increase the number of mappers in Washington State by contacting them after their first edit with suggestions to help them get involved. My message was taken from the Brussels community. I can't say it helps keep people mapping but it certainly doesn't hurt. At least no one has asked me not to send them messages. (Most just ignore me.)

Because my process is manual, I look at every first edit and fix many of them. Those first edits often have common quality errors. I don't believe they are from bad users, but from a process that could use improvement. We could insist that new users complete a course before they are allowed to edit. But that isn't going to get us new mappers. Having existing mappers validate new users edits takes time away from their normal mapping.

When I do fix an edit, I include the change in the Welcome message. Occasionally I'll leave a changeset message when I'm not sure what they were intending. Originally I was leaving a message and not fixing them, but after realizing that many didn't go back to fix the problem I just started to do it myself.

I tried to look at this from a quality improvement perspective. First collect data then define the problem and finally look at solutions. My new mapper process has been running for over a year. While I haven't done a proper job of documenting errors, something I'd like to do, some just keep reoccurring. Today I'm just focusing one one.

Problem Statement

New users edits do not include the lack of a tag to describe the business. For example, someone added an insurance office. The tag included the name, address, and phone number. Occasionally they will add a tag keyword to indicate what the business does. But no office=insurance. To the editor, this looks a good edit.

The developers did fix the problem of tags with just name=. It now notifies the user that they need to enter more information. We now need to take this to the next level.

Below are two possible solutions. The solutions are for iD since that is the editor most new users use.


  1. If the object is an area, provide two name fields, a building name and a business name. The text field should have appropriate tools tips to help the user select the right box for the name. If the business name is populated, then the user should be prompted to add an appropriate tag to the feature (besides the address.) Address point objects should not have a name field. Name fields should be only be provided with objects that have names such as businesses, places, etc.
  2. is a website to add businesses to OSM. The process doesn't actually add businesses to OSM but leaves a note for a mapper to add the business. The code is on github. I'd like to see the user interface enhanced to help select the correct tags for the business with a version of iD to have the user actually add the business. To move the website out of obscurity, include add business under the edit menu on the main website.

How you can help

  1. Look at new editors in your area. Determine the common errors in their edits.
  2. Is the problem correctly stated?
  3. What other improvements to the process would help?
  4. Are you or your company willing to fund development to improve the process?
  5. What would be a good tool to capture new edit quality errors?

Clifford Snow

OSM go on - Colours, Models and Shadow (EN)

Posted by -karlos- on 26 November 2016 in English (English)

Work is in progress, features are improved and added. See the OSM Wiki page for more details and read some background infos below.

There is an Twitter-Feed: @OSM__go (two underscores!). You may follow the latest activities, upcoming ideas and related things.

Tile processing

Overpass seemed to be slow but my measurement was wrong because Javascript even delays console.log while callback code is running. A close inspection showed: Overpass is great, my code with a lot of string copy was slow and is now replaced by jQuery.js and getJSON. Much better, much faster but there was still that “wait-cursor”. Again it was me. I had simple linear searches for already existing nodes or ways. I replaced them by arrays with the OSM-ID as index. Odd to debug but fast. Now, the default load radius is set up to 800m and still fast. Or fine, if you are in a dense city. Old hardware devices may have trouble and get slow. Now the download will stop.

Thats was not the end. I move the tile/tag decoding and the 3D object placing (not yet parseJSON) away from the callback into the render cycle, sliced in fast steps. Now, the default load radius is set up to 800m and still fine in a dense city. Old devices may break downloading. And you may even move already during the download. - One more thing: The first load will be more slow than thereafter of curse - because of the just in time compiling.

Overpass gives an array of elements, first all node-types, then all ways etc. “parseJSON" can only convert this to an single array with mixed types. Is this good? Building tags may be placed at ways or relations(multipoligon). Decoding code would be the same. So it may be good to have all types in one array. But OSM does not have ONE set of IDs!

What about an “overparseJSON" ?: It should convert to separate arrays, one for notes, ways, and relations. It shouldn’t be hard to morph the jquery-code. And there could be a callback for each node, way, etc. So I could immediately extend the node- and way-instances to my needs like adding the three-ja-mesh.


Even if the shape of buildings are fine, paint makes them more realistic. Handling the tags building:colour and roof:colour was easy. Chroma.js does convert the color tag strings and Three.js ExtrudeGeometry also handles different colours for the sides and the ends. So after 10 lines of code and 1-2h test it was done. But soon Murphy's law strikes back: There are quite a view named colours, not known form three (see wiki). Tags like light_brown or yellow-brown may be handled automatically. But what about spelling errors and unknown colours? That may be a task for the validators like Keepright.


Jan (OSMBuildings) asked me, how fast Three handles shadows: about 20% more rendering time. When you start now, the place around that point has shadows. To show the effect even more, a big disk flies over you. There are still some shadow options to investigate. In the Code, a virtual camera is placed at the shadow casting light. Mostly the graphic card is doing the hard work. This “camera” analyses the shapes, if they cast shadow and if this shadow is seen by the “real” camera. A greyscale bitmap is generated and placed between before the virtual world. Looks good. Todo: move the virtual with the real camera.

Placing Modells

For quite a view buildings, extruding doesn’t make much sense, especially for famous buildings like churches or monuments like the Eifel Tower. There are 3D-models of many of them. To place them in a virtual 3D OSM world doesn’t help for data visualisation but for an realistic view. And it’s cool anyway, if you move around by mouse or with VR glasses.

What to render: Where to store and get the model files?

  • I like the Idea of, but its offline :-( I got in contact, may be we will have the files and set up them on a new server and even extend the service to other formats.
  • Meanwhile I did the two models, OSMBuildings uses. (They are not perfect yet)
  • OSM2WORD and other 3D-viewer seems to have a lot. Who do the to that?
  • What about Google Scetchup? I will try to get and dynamically convert all the models. Three.js does have loaders for many file types, that seems to be no limit. But I am sure there is a copyright prohibiting a use.

How to place: My first answer to the following questions was an OSM relation for each model to place with special tags.

  • First the model file. The concept of OpenBuildingModels is great. A reference to an external server with the file. (server-code, model-name/ID and may be file type.
  • The model may be directed correctly already or we need a tag to do it, useful if a model is used more than once.
  • There may be a tag for scale to, and even a hight-offset.
  • Now we need the place. if there is no existing node to reference to, it has to be placed.
  • Usually there is one ore more building-ways in OSM, representing the building in a 2D map. They have to be removed/skipped by the 3D renderer. So wee need a reference list to them. The solution used by OpenBuildingModels is simpler: One Tag with Server and Model. No direction, size and height. And this tag is added to each building to be replaced by the model. I like that.

Other changes

  • The debug output now shows the FPS (add &hud=1 to the url) Disappointing: 40 down to 10 FPS with 3D models displayed. Strange: it doesn't feel slow.
  • Added new URL parameter: “&keep=1 or 0 for show/don’t Keepright error markers. Default is don’t
  • Level & Layer: Underground objects shouldn’t be seen above, bridges should be raised. Now the tags level and layer are used.
Location: Holborn, St Giles, London Borough of Camden, London, Greater London, England, WC1B, United Kingdom


Posted by Kalina fglizabeth on 26 November 2016 in Indonesian (Bahasa Indonesia)

sex sii

Location: Seumantok, Aceh, Indonesia


Posted by 黒猫ぽち on 26 November 2016 in Japanese (日本語)

今日、某Webアプリケーションからリンクを辿ってこのOpenStreetMapにたどり着きました。 地図版のWikipediaみたいなものだと考えればいいのかなぁ?



State of the Map Asia 2016參與記實

Posted by Supaplex on 26 November 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

這次去馬尼拉,參與 State of the Map Asia 其實是很倉促的決定,看到有 scholarship 可申請,就想說談談臺灣社群狀況,順便會會一些相關公司、社群的人。這次決定並沒有讓我失望,除了見到朋友 Wular,還碰到 Mapbox data team印度團隊的人,以及久聞大名的 Manning。

Manning Opening

Mapbox 的團隊最近在幫忙對齊臺灣的道路網路,採用新出爐的 Mapbox 衛星影像,還有 Strava GPS 軌跡。先前我只有跟 Manning 和 Mapbox data team 線上打過交道而已,見到面感謝他們的貢獻,發聲說說臺灣的狀況,能夠配合遠端鍵盤繪圖的人做些什麼事情。


My slide

臉書使用 OSM 資料對臺灣的影響

我談到臉書採用 OSM 資料的部分沒講太清楚,蠻多人在演講後有疑問有跑來跟我聊聊。臉書在兩個地方用 OSM 資料:用 OSM 資料訓練 AI 畫地圖;用 OSM 資料當地標資料的底圖。前者不少關心 OSM 的人都知道,也觀察到臉書的 AI 有重覆畫既有的道路網,這麼就不累敘了。

Facebook landmark page

臉書目前在日本、南韓都有用 OSM 當地標資料的底圖,而地標位置則在臉書手上,當然是使用者給他們的資料。但在去年臉書有在中國、臺灣、越南試驗把地標點底圖換成 OSM,結果在臺灣引起相當大的風波。一來是 OSM 未必在每個地方每條巷弄都畫出來,給人一種地圖很不精細粗糙的使用體驗;二來是很多人搞不清楚地標的位置由使用者建立,所以如果當初建立時輸入錯誤的訊息,那臉書拿到的資料也就錯誤了。建錯的地標連同被換掉的底圖,被怪罪到OSM,其實就不是 OSM 的問題,地標放錯位置是Facebook問題。

有一個最誇張的例子是有人興沖沖的回報他們地標位置標錯了,而且指責附近一帶的地圖上沒畫出多少巷弄,語言用詞相當的沒禮貌。當時臉書有把使用者回報導向 OSM 的 Note 系統,所以許多大大小小的抱怨湧入,有些可能是 OSM 問題,有些臉書的問題,像地標位置設錯了。這些回報包括這位沒禮貌的回報者,也就沒意識到寫出來的內容是公開的,永遠存在網路上。

Complain from Facebook user

最後臉書大概也煩了,沒人力可以處理本來他們應該處置的使用者抱怨,臺灣這邊的地標底圖改用 Here 圖資,也結束臺灣OSM社群的困擾。


OSM 強調可以實作多語言地圖,照顧不同語言使用者的需求。於是我們看到除了 name 欄位填入在地社群的慣用名,其他像是 name:en、name:de、name:ja、name:fr、name:zh 表示對應的語言名稱,採用 alpha-2 code of ISO 639-1 的語言代碼後綴。

但儘管有辦法能夠實現多語言共存的狀況,仍然要先制訂標準出來。實際上在中文世界這邊,OSM 目前訂定的name:zh並不夠,不能妥善涵蓋用到繁體、簡體中文字的人,需要另行制訂繁體中文、簡體中文對應的 tag。


於是 Rex 大大依據 IETF language tag  (BCP 47) 的語言規範,制訂適用臺灣、中國、香港、澳門,以及其使用中文的地方,或者有用到中文譯名的地方。

Chinese name tag proposed

除了字體之外,把地區不同用詞也考量進去。比如說,在臺灣、中國各自用慣用的繁體、簡體在name:zh欄位沒什麼大問題,但在這兩個地方以外,有些地方不只簡繁體的差異,而是用詞完全不同,像是Mt. Everest,臺灣用的是聖母峰,而中國那邊採用喜马拉亚山。

也許提 Mt. Everest 對菲律賓人來說很遙遠,因此在演講時反應不強。我應該提一些菲律賓的知名地名或旅遊景點,比較讓菲律賓和外國人有點印象,像是民答那峨 (Mindanao)、薄荷島 (Bohol)。兩者在臺灣和中國分別是如下稱呼:

  • 英文 臺灣繁體中文 中国简体中文
  • Mindanao 民答那峨 棉兰老
  • Bohol 薄荷 保和

由此可見,除了繁簡體中文字問題,還有不同的慣用翻譯,影響 OSM 的在地化和體驗。


Tagging for the Formosan language of Taiwan Aborigines

對臺灣的社群來說,長期目標是希望各個使用 OSM 圖資的開發者,能夠逐步採用這套語言標示服務各地中文使用者,解決臺灣、中國等地繁、簡字體差異,還有用詞不一的問題,提供各地用戶更客製化、在地化的體驗。未來臺灣的 OSM 社群在提出這套方案之後,也將通知各個用到 OSM 資料的地圖 app 開發者,希望他們能夠採用。


現行在 OSM 的宗教教派標示方式,像是佛教、基督教、天主教、道教、回教的分別,對於標示臺灣的宗教和民間信仰並不精確,容易帶來誤解。臺灣很多廟宇祭拜的對象以歷史人物為主,分辦是屬於那個宗教教派其實沒意義。應當更聚焦在這間宗教崇拜場所是供奉那位神祗。


Taiwan traditional religion tagging

因此Rex提出傳統信仰標注方式 (草案),希望提出一套標準來解決前面提到如何標示臺灣多元宗教教派的面貌,解決現行OSM上臺灣宗教歸類的亂像。除了前面提到應當用主祠神為主要區別,應該另立獨立的臺灣傳統宗教信仰標籤,下面有例子解釋。


  • religion=folk
  • denomination=TaiwaneseFolkReligion


  • religion=folk
  • denomination=SirayaFolkReligion


慈惠堂 (仍須依據其運作模式來判斷)

  • religion=folk
  • denomination=TaiwaneseFolkReligion
  • dedication:principal=瑤池金母
  • dedication:principal:wikidata=Q1064059


其他還有其他問題,像是中文地址書寫習慣,在線上編輯器iD欄位設計時主要考慮英文地址書寫方式,造成中文排列問題,會在 iD 2.0 版獲得改善。


我在演講時刻意提到 Mapbox 團隊在臺灣依據 Strava GPS 軌跡,重新對齊臺灣道路網。演講完也與他們團隊有相當密切的交流。原先只有在網路平臺交換意見,能在實體空間碰面交談,類似第一次面對面見到網友的體驗,相當新奇。

Mapbox works

我也遇到 CEO,跟他交換不少意見。他在演講時提到 OSM 需要輕量的參與者,增加在地的商家,因此就需要能夠很簡單就能增加資訊的 App,他們的 Maps.me就是這樣一套工具,不然靠重量級的圖客觸腳永遠都碰不到所有地方。

我跟他說有些用戶有很有創意的使用 的方法:除了加店名,還用 $ 符號的數量表示該店家的價位區間,$$$$ 表示貴,而 $ 是便宜。不得不說選餐廳時這價位區間是重要資訊,但到底在 OSM 要怎麼標示。他提到未來改版會加入增加道路名稱的功能,讓 廣大的使用群眾,貢獻最在地也最基本的資訊,那就是用戶活動地區的道路名稱,聽他說我覺得這很重要。

Eugene talk from Mapbox


尼伯爾的Nama博士說他被念煩了,一直被人詢問,或是被邀請談論尼泊爾地震的急難繪圖經驗,該來辦個活動完整記錄這事情,免得過個幾年記憶模糊,細節沒記下來。另外就是很多當時的要角沒辦法輕易出國談那次經驗。下一年 2017 年,State of the Map Asia 大會,有極高可能在尼泊爾舉行,大家可以來參加會議,然後去登喜馬拉雅山。

Nama talk


Location: Xavierville III, Loyola Heights, Quezon City, District III, Quezon City, Metro Manila, 1108, 菲律賓

indoor におけるOSMの用途、道具、展望

Posted by くどー on 26 November 2016 in Abkhazian (Аҧсуа)


#ここでいうindoorとは?                               室内で作業するから?室内のデータを作成するから?室内のデータを利用するから?     

#講演の内容                                      講演者たちが所属するグループはフランスで約2年間の間多くの活動をしてきた。例えばフランス、パリにおいて室内マッピングが広く伝わった。パリ内の、すべての駅、ショッピングモール、博物館、大学などのデータが詳細にマッピングされている。この活動の背景にはいくつかのツールや技術の開発がある。これらのことについて解説されていたのでいくつか紹介する。  

#マッピング                                      大学内でいうと、パソコンなど私たち自身でマッピングを行ったり編集したりできるようなツールが多数設置されている。大学やショッピングモール、その他の建物は「建物」として簡単に考えることができるが実際は階層や部屋の高さ、幅が存在する。これを考慮すると大変なことである。そこで用いられたツールが360°カメラである。これを用いて大量の写真、データを集めることでより詳細で分かりやすいデータとすることを可能にした。

#データの活用                                     これらのデータは主に建築に用いられている。上記のように、問題は建築物の水準、階層、部屋をどう考慮していくかということである。これを解決していくために、技術を発展させより詳細なデータをとっていく必要がある。

#将来的な活用                                     より多くのデータを活用していくためにSLAMという考えを用いていく。これはマッピングを地域化していくことで都市などの密集地だけでなくより広くデータを収集することができ、またそれを利用したビジネスを行っていくことができるというものである。

#感想                                         より広く利用するために、私たちは私たち(エディタ)のリンクを増やしていく必要があると考える。

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

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

Опубликован ЕженедельникОСМ 331 - краткие новости о происходящем в мире ОСМ, можно прочитать на русском языке на сайте.

Замечания по переводу оставляйте в комментариях, исправьте в вики, напишите на форуме, сообщите в телеграмм



  • Пример страницы wiki с новыми фичами Taginfo Taginfo расширил возможности по визуальному отображению значков, сопоставляемых с тегами на wiki-страницах ^1^ | Screenshot from OSM-Wiki under CC-BY-SA 2.0


  • [1] Jochen Topf расширил возможности Taginfo, теперь сервис умеет показывать примеры отрисовки в списках тегов в Wiki. Matthijs Melissen протестировал новую функцию на некоторых страницах. Если у вас есть желание поучаствовать, пожалуйста напишите ему!

  • ImproveOSM теперь использует редактор iD.


  • Пользователь PlaneMad объяснил преимущество идентификаторов wikidata в OpenStreetMap и сослался на способ добавления таких идентификаторов, который использует Mapbox. Другим же пришлось их обсуждать, так как они были сделаны автоматически.

  • Пользователь Joost Schouppe отметил важность активности сообщества, при которой можно указать на отдельные проблемы, не считавшиеся приоритетными у команды разработчиков. Организаторы сообществ по всему миру были опрошены об основных проблемах при организации сообществ, инструментах, необходимых для их создания, и что работает на данный момент. Один из таких инструментов, это Belgian Welcoming Tool, который используется в Испанском сообществе. (о котором мы писали на прошлой неделе)

  • В октябре 2017 в Аргентине в National Geographic Institute при поддержке OSGEO 2017 пройдут одновременно FOSS4G и State of the Map .

  • Chris Hill объясняет как использовать стек технологий OpenStreetMap для создания наглядной карты фестиваля музыки и искусств Clockenflap в Гонконге без использования лучшего, что есть в ОСМ – данных.

  • Блог OpenStreetMap сообщил о выпуске редактора iD версии 2, и том, что он теперь доступен с главной страницы. В блоге Mapbox, Bryan Housal подробно описал новый функционал.

  • Sebastian задумался о значении всех тегов place=locality, найденных в сельской местности Испании.

  • Nelson просит помощи у сообщества с тегированием "опасных дорог". Сообщество Бразилии не может придти к компромиссу по тому какие теги использовать для дорог, например в фавелах, чтобы маршрутизаторы не вели через такие "опасные" территории.

Фонд OpenStreetMap

  • В интервью OpenCage Data член правления OSMF Martijn van Exel рассказал о стартовавшем сборе пожертвований и о том, почему это важно. Финансирование имеет важное значение для того, чтобы оставаться независимыми и не полагаться исключительно на корпоративные взносы, оно также даёт возможность любому участнику принять участие в поддержке OSMF.


  • 24-го ноября перед State of the Map Latam прошла встреча 'только для девушек' для участниц OpenStreetMap, чтобы они могли познакомиться, поговорить и обсудить участие в проекте.

  • Открыт приём заявок на FOSSGIS 2017, который будет проводиться в Passau 22-25 марта. Приглашаются докладчики с идеями или проектами для начинающих и опытных пользователей. Доклады про геоданные и их обработку тоже приветствуются.

  • С 11 по 20 ноября в Абиджане прошёл первый "SysInfoLibre Abidjan 2016 (автоматический перевод): Yunohost, SI Libre SI Libre for librist collectives, по открытым данным и OpenStreetMap Западной Африки" при участии команды LesLibresGéographes, проекта EOF и Direction Francophonie Économique et Numérique of the International Organization of Francophonie (DFEN-OIF).

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

  • HOT объявил о получении гранта от Gates Foundation для борьбы с малярией в Африке при помощи анализа данных OpenStreeMap.

  • Séverin Ménard в блоге на EOF Project рассказал про свою волонтёрскую работу (Französisch) (автоматический перевод) по оценке доступности дорог в зоне последствий урагана Мэтью (Matthew) на Гаити.


  • Отметив второй день рождения маршрутизатора Valhalla, Mapzen рассказала об основных новостях, представила команду разработки и анонсировала версию 2.0.


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

  • Cruiser for Android * 1.4.14 2016-11-15 Различные улучшения.

  • Cruiser for Desktop * 1.2.14 2016-11-15 Различные улучшения.

  • Mapillary Android * 3.0.6 2016-11-15 Исправлен текст и даты изображений на некоторых устройствах.

  • Komoot Android * var 2016-11-16 Небольшие улучшения.

  • PyOsmium 2.10.2 2016-11-16 Три расширения, два исправления ошибок и использование libosmium.

  • iD 2.0.1 2016-11-17 Исправления ошибко 2.0.0.

  • Mapbox GL JS v0.28.0 2016-11-17 Три новых функции и улучшения, шесть исправленных ошибок.

  • Vespucci 0.9.8r1214 2016-11-18 Читайте полный отчёт.

  • Traccar Server 3.8 2016-11-19 Нет данных.

  • libosmium 2.10.3 2016-11-20 Читайте полный отчёт.

  • Osmium Tool 1.4.1 2016-11-20 Два расширения, четыре изменения и три исправления.

  • Leaflet 1.0.2 2016-11-21 Читайте полный отчёт.

  • iOS * 6.5.3 2016-11-21 Исправления ошибок.

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

(*) несвободный софт. Определение открытого/свободного программного обеспечения.

OSM в прессе

  • * На сайте Routefifty рассказали о городе Санта-Каталина, находящегося к юго-западу от Лос-Анджелеса, который обошли вниманием на Google Maps. Routefifty рассмотрел проблемы и судьбы локаций, не появившихся на коммерческих картах, и ​о том, как он чувствуют себя в проектах OpenStreetMap и Mapillary.

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

  • Ричард Харрис (Richard Harris) взял интервью у Энтони Каламито (Anthony Calamito), который является главным разработчиком Boundless - ГИС платформы с открытым исходным кодом.

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

  • Университет Мэйнус (Ирландия) предлагает новый протокол для сбора географических данных краудсорсингом.

  • Кэтрин Андерсон (Katherine Anderson) рассказала о 13-м пленарном заседании прошедшем в Российской Федерации и посвящённом, помимо других событий, запуску нового портала GEOSS.

  • Процедура создания карты AuthaGraph (о которой мы писали на прошлой неделе) так и не была опубликована. Марцин Циура (Marcin Ciura) изложил в своём блоге математическую основу разработки псевдо-аутаграфов. Исходный код был опубликован на Bitbucket. Для полноты информации так же упомянем проекцию Димаксион бразильского архитектора Серхио Волкмера (Sérgio A. J. Volkmer).

  • Южная Корея отвергла просьбу компании Google использовать локальные картографические данные в глобальной карте из-за опасений по поводу национальной безопасности после добавления данных в Google. Южная Корея запрещает продажу геоданных о стране иностранным компаниям, которые не держат сервера внутри страны.

  • На курсе комбинаторной оптимизации в Университете Бонна в рамках изучения проблемы комивояжера занялись поисками кратчайшего маршрута для посещения 24,727 пабов Великобритании. Студенты использовали Google Maps и данные о пабах от Pubs Galore. На получившейся интерактивной карте можно посмотреть рассчитанный маршрут для посещения всех пабов.

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

Divulgando Openstreetmap

Posted by Tomio on 25 November 2016 in Brazilian Portuguese (Português do Brasil)

Sempre que a oportunidade é dada, tenho feito a divulgação do Openstreetmap.
Demonstrando as vantagens, benefícios, oportunidades, potencialidades, entre outras coisas, de contribuir com informações neste Projeto mundial.
Há dois anos atrás, estive com Inspetores do CREA da nossa cidade, fazendo uma apresentação:

Mapeando Arequipa (Noviembre 2016)

Posted by rdacardenas on 25 November 2016 in Spanish (Español)

Hola a todos, como comentaba anteriormente he proseguido el mapeo de las zonas de cultivo en Arequipa (chacras como les decimos por aquí). En detalle he estado mapeando por los distritos de Uchumayo, Cerro Colorado, Congata, y Tiabaya. También he mapeado algunas chacras por el distrito de Pocsi y alrededores, pero aún queda trabajo pendiente por esa zonas.

Más cerca a la ciudad he encontrado zonas de cultivo no mapeadas cerca a la Av. Aviación (distrito de Cerro Colorado) como también zonas residenciales, las cuales he mapeado. Esto a su vez me han llevado a preguntarme cuantas de las áreas cultivables (en los alrededores de la ciudad) que aparecen en las imágenes satelitales ya están convertidas actualmente en zonas residenciales. Por el boom inmobiliario que sufre la ciudad no me sorprendería que su extensión sea mucho mayor a lo que actualmente se puede ver en las imágenes satelitales...

Por último, leyendo las noticias me enteré de un poblado llamado Quiscos que podría verse afectado por la actividad del volcán Sabancaya (emanaciones de ceniza, etc.) y revisando la zona encontré que faltaban mapear las áreas de cultivo así que me puse manos a la obra. Un poco más al sur llegando al distrito de Yura también hay zonas pendientes donde he visto que otro colega ha estado avanzando y eso es muy bueno. :D

Numeri civici in Italia: confronti fra città

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

Viste le enormi differenze all'interno del territorio della maggior parte delle regioni italiane sul livello di mappatura, ho ripetuto le analisi sui civici a livello comunale per 12 comuni.

La selezione può apparire peculiare, però ha diversi vantaggi. Alcuni li elenco nella sezione "Rilevanza dell'analisi", comunque sono andato a selezionare le grandi città e una serie di realtà per dare una panoramica. Ho unito infatti comuni molto ben mappati a comuni mappati molto meno bene (a volte nella stessa regione), inoltre comuni di varie zone d'Italia.

Metodi e precisazioni

  • sono considerati solamente i civici inseriti come nodo
  • i dati sono del 24 novembre 2016
  • i dati della superficie e popolazione delle regioni sono presi da


  • Acireale
  • Arenzano
  • Cagliari
  • Catania
  • Genova
  • Milano
  • Napoli
  • Padova
  • Palermo
  • Roma
  • Torino
  • Udine

Rilevanza dell'analisi

  • Totale abitanti considerati: 8178968
  • Percentuale della popolazione italiana: 13,5 %
  • Totale Superficie considerata: 2600,03 km quadri
  • Percentuale della Superficie italiana: 0,86 %

sono inoltre presenti le prime 6 città italiane per numero di abitanti:

  1. Roma
  2. Milano
  3. Napoli
  4. Torino
  5. Palermo
  6. Genova

e anche la decima (Catania)


|Regione  | indirizzi| Superficie| Abitanti| abitantiXindirizzo| superficieXindirizzo| OrdineAbitantiXIndirizzo| OrdineSuperficieXindirizzo|
|Arenzano |      5386|      24.30|    11519|           2.138693|            0.0045117|                        1|                          3|
|Cagliari |     46789|      85.01|   154507|           3.302208|            0.0018169|                        2|                          1|
|Udine    |     25119|      57.17|    99094|           3.944982|            0.0022760|                        3|                          2|
|Catania  |     34133|     182.90|   314318|           9.208625|            0.0053585|                        4|                          4|
|Acireale |      3509|      40.43|    52591|          14.987461|            0.0115218|                        5|                          6|
|Genova   |     26699|     240.29|   585407|          21.926177|            0.0090000|                        6|                          5|
|Milano   |     12396|     181.67|  1350387|         108.937319|            0.0146555|                        7|                          7|
|Torino   |      5750|     130.01|   888934|         154.597217|            0.0226104|                        8|                          8|
|Padova   |      1332|      93.03|   211215|         158.569820|            0.0698423|                        9|                          9|
|Roma     |      7926|    1287.36|  2867078|         361.730759|            0.1624224|                       10|                         10|
|Palermo  |       628|     160.59|   671696|        1069.579618|            0.2557166|                       11|                         11|
|Napoli   |       162|     117.27|   972222|        6001.370370|            0.7238889|                       12|                         12|

(Enormi) differenze intraregionali dei Numeri civici in Italia. Il caso Liguria

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

Giorni fa ho fatto una analisi sullo stato dei civici nelle varie Regioni italiane.

L'utente Ale_Zena_IT faceva osservare che la Liguria (la cui "posizione in classifica" la migliore tra le regioni considerate) aveva in realtà enormi differenze regionali: due comuni ben coperti (Genova e Arenzano) e il resto desolato.

Utilizzando dati del 24 11 2016 emerge il seguente quadro: il numero totale di indirizzi in Liguria è 36281; l'88,43 % è però concentrato in due soli comuni:

  • Genova, con 26699 indirizzi (73,59 % % del totale regionale)
  • Arenzano, con 5386 indirizzi (14,85 % del totale regionale)

Segue la tabella con il dettaglio sui civici in rapporto alla popolazione e alla superficie

|Regione                        | indirizzi| Superficie| Abitanti| abitantiXindirizzo|superficieXindirizzo |
|Arenzano                       |      5386|      24.30|    11519|           2.138693|0.00451169699220201  |
|Genova                         |     26699|     240.29|   585407|          21.926177|0.00899996254541368  |
|Liguria                        |     36281|    5416.21|  1566992|          43.190000|0.15                 |
|Liguria meno Genova e Arenzano |      4196|    5151.62|   970066|         231.190000|1.23                 |

Risulta che, sia considerando il numero di abitanti per indirizzo, sia la superficie per indirizzo, Arenzano è meglio mappato. Per dire: gli abitanti per ogni civico a Genova sono circa 10 volte quelli ad Arenzano. Se si considera il resto della Liguria, la situazione è ancor più lontana: gli abitanti per ogni civico sono più di 10 volte quelli a Genova e più di 100 volte quelli ad Arenzano.

ricordo che

  • sono considerati solamente i civici inseriti come nodo
  • i dati sono del 24 novembre 2016
  • i dati della superficie e popolazione delle regioni sono presi da

Adding height to City of San Francisco buildings

Posted by Chetan_Gowda on 25 November 2016 in English (English)

The import team is working to add height data for buildings in the City of San Francisco.

Our goal is to add ONLY height tag to the existing OSM building footprints.


Why we are adding height tag?

Adding height to existing buildings will enhance the data especially when used with popular renderers like OSM Buildings and Mapbox GL JS.

What is the source of data?

We are using raw LIDAR derived building height data released by SF local government under a CC0 (Creative Commons) license (data download here).

How are we combining the height to existing buildings?

For each building in OSM, we compare the footprint from SF goverment buildings, if there is 70% overlap, we add the height. Buildings with existing height tag won't be touched.

The task is hosted in OSM-US. The importing has begun at

Note: Before jumping into the task, please read all the instructions carefully.

To know more about the project, or if you have ideas please post them here:

Fixing the invalid areas of the map

Posted by BharataHS on 25 November 2016 in English (English)

A previous diary post-The invalid areas of the map introduced us to invalid relations formed due to multipolygon relation being broken due to various errors. The post has a comprehensive discussions on different errors, its severity and respective simple fixes. It also has these interesting open questions which needs to be debated.

It seems like a huge majority of the issues need to be carefully reviewed by hand and cleaned up. What does a realistic approach to clean the map look like?

The flexibility of the current map editors allows mappers to continue to create features that don't make sense like a way tagged as a forest. Is it time for stricter validity checks on uploads?

The current diary post walks through the tools which aids in fixing these invalid multi polygon relations which not only remains erroneous part of the map but also affects the map rendering.

Start by reading this documentation on multipolygons if you are trying to understand the basics.

How to identify invalid multipolygons ?

An error debugging tool from Geofabrics - OSM Inspector tool aids in identifying these invalid relations in OpenStreetMap. The tool can be either used in a web browser interface or as a layer in JOSM editor.

To use OSM inspector in a web browser,

  1. Go to
  2. Select Areas from 'View' menu.
  3. Left panel contains the list of all possible errors which enables user to toggle between errors.
  4. The map window highlights the node causing error and allows user to pan, zoom over the map in order to inspect the affected portion of the relation.
  5. The Selection panel at the right edge of the page displays the selected object and the small icons on the top leads you to map editors where one can fix the issue and also to open OpenStreetMap.

screen shot 2016-11-24 at 7 33 41 pm Elements in OSM Inpector tool page

To use it the tool JOSM editor,

  1. Open Imagery preferences from the menu bar.
  2. Find OSM Inspector: Area and activate the layer from the list of available layers or add this as a WMS layer in JOSM
  3. Now, the layer will be listed under the imagery menu.
  4. Load the layer and you will have a layer showing all the broken geometries with nodes highlighting at the region of errors and also a text label which mention the error around the node.

Once the error is rectified, make sure to check the roles and sorting order of the relation from the relation window before uploading the data to OpenStreetMap. Along with the tool, JOSM validator can be used to validate the geometry once it has been fixed.

adding_osmi_josm4 Adding OSM Inspector layer to JOSM

This guide runs through a short tutorial on enabling the OSM Inspector 'Areas' layer and its usage in JOSM. Combination of both these validators results for a powerful error debugging tool to identify and fix errors in invalid relations.

Fixes by Mapbox team

The data team at Mapbox reviewed about 1024 invalid multipolygons and fixed around 70% of them with help of OSM inspector. Out of the rest, about 16% of them were unfixable issues. (Ex. Administrative boundaries of type=boundary and disputed borders; Segment missing in the relation causing ring not closed issues). 6% of them had a number of minor errors (Ex. Touching rings) which were not serious issues as it did neither harmed other data nor affect rendering of the map. Check out more at the fixing broken multipolygon issue.

There exists a huge number of broken/ invalid relations which needs to be fixed. These invalid areas of the map can only be fixed by the local community mappers. Would love to hear any suggestions or feedbacks and other tools that can be utilised to identify the broken multi polygon relations. Have any questions, leave a comment below.

Mapillary Have a Special Hell Reserved Just For Me

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

Mapillary is a Swedish organisation that, like Marvin the Paranoid Android in Hitchhiker's Guide to the Galaxy, has a Data Centre for storing photographs as big as the planet. When you Register with them you can store GPS-registered photos on their site (really useful when surveying for later mapping).

My profile on Mapillary shows that I've uploaded 3,500 photos and have travelled 179.6 km whilst doing that. It also shows that I've uploaded the last 81 photos 6 times (making 486 total uploads in that sequence).

I'm currently mapping in the north of Nottingham in a district called ‘Gedling’ (south of Arnold Lane and north of Westdale Lane). 81 is a very typical number for me to shoot in a morning or afternoon whilst mapping. I used to use the Mapillary app in JOSM to upload, but tend to upload directly from a browser these days (the JOSM app requires a confirmation within a browser, so I cut out the middleman).

The sequence went very normally with those 81 photos, except that the Mapillary browser did not confirm the uploads within my profile. At first, I also got zero reply from Mapillary support. I kept trying to upload...

I eventually got an email from Katrin at Mapillary support, and she copied the email to Peter. According to the email that Peter sent this morning, the issue was because the “harvester for manually uploaded images has not been running” (he restarted it, so all 6 identical sets of images were harvested at once). Problems with a Harvester seem the correct kind of issue for this time of year.


I sent an email to Peter saying “So, no-one could manually upload photos? And I'm the only one that manually uploads photos?? Good lord.” Fortunately, he seems to have a sense of humour. He replied that:

  • no web-uploaded images have been processed in the last 2 days
  • that affected ~200 people
  • it involved ~500k images
  • mobile apps use another method, so uploads did not actually stop
    (they halved, hence no-one at Mapillary noticed)


A Medical Doctor gets called out to a Sawmill. He has to push through a large crowd of sawmill workers all busily gawping at some scene occurring in the middle. As he gets closer the noise of the mechanical circular saw gets louder & louder...

At the centre is a man with the stump of his left arm wrapped in a bloody cloth. He is stood near the circular saw, whilst being comforted by some colleagues. His hand lies amidst the sawdust at the base of the saw.

The doctor: “Good lord, man, what happened to you?”

The man (a little unsteadily): “Well, doctor, I was working at the saw, and I went like this...” (gestures) “...and GOOD GOD! THERE GOES THE OTHER ONE!”

Coda: 100 million Mapillary Photos Uploaded

An email from Mapillary boasts that they now have 100 million photos on Mapillary. The link says that it has taken 2½ years & 2.1 million km, and was 10m photos last year. My calculation based on the numbers given earlier suggest that it is currently 500k uploads/day (from both mobile apps & web-uploads) = 182.5m/year.

This all suggests a large speed-up in the last year.

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

Editei alguns pontos que achei importante no Bairro Jardim Fernanda em Capinas.

Posted by Carlos Alberto Figueredo on 25 November 2016 in Brazilian Portuguese (Português do Brasil)

Editei alguns pontos que achei importante no Bairro Jardim Fernanda em Campinas. Logo que puder tentarei postar e editar mais para contribuir com a comunidade. Adicionei posto de saúde;mercado rotatória em frente ao bairro. espero ter ajudado pois sou novo na comunidade , se pósivel mandem algumas dicas de como usar melhor o Map e outros aplicativos para edição. Obrigado.


Posted by rtjert468 on 25 November 2016 in Chinese (China) (‪中文(中国大陆)‬)


Older Entries | Newer Entries