Aplicações que usam o Openstreetmap podem ser muito úteis para os municípios, no desempenho das suas habituais tarefas. Após demonstrar o Umap para o Setor de Terraplanagens da prefeitura, eles acabaram desenvolvendo um mapa nele, para controlar as licenças emitidas. Comentaram que ficou muito mais fácil acompanhar as obras e responder a questionamentos quanto a legalidade de alguma intervenção que está ocorrendo na cidade.

A própria comunidade pode acompanhar e verificar se a obra tem licença:

Link: http://u.osmfr.org/m/485541/

Originally, I wrote this post for my blog: http://plepe.at/398

I love mapping for the OpenStreetMap project, it’s a very pleasing thing to do. I especially like to do it as vacation activity, because then I’m exploring new places anyway, but I also like to do it my home town.

Recently I’m concentrating on mapping artwork and memorials. Even in a well-mapped city like Vienna, Austria, there’s still plenty to do. For example, most social housing building complexes (Vienna is famous for it’s social housing) have some kind of artwork, e.g. some murals or statues in the gardens.

Some examples:

I think, having a map feature in OpenStreetMap is not enough though. I want to add pictures and meta data (who made the object, when was it created, …). This is done in cooperation with the Wikimedia Foundation. In this article, I want to explain how I map these objects.

Wikimedia Commons

Often these objects already have photos on Wikimedia Commons. If not, I upload one or a few photos (whatever is reasonable). If there are several photos of the picture (or the object seems important enough), I create a category for the object (if it does not exist yet). Of course, the category should have the relevant categories for the location, the motive, the artist, etc.

Wikidata

Next, each object should have its own Wikidata entry. Haven’t heard of Wikidata yet? It’s a sister project to Wikipedia and Wikimedia Commons. As Wikimedia Commons is the platform for media (which is linked by Wikipedia), Wikidata is a platform for semantic and linked data. E.g. an entry for a city would have values for the population size at specific historic dates, links to the wikidata entry of current and former mayors, link to other data sources (Encyclopedia Brittanica, Library of Congress), link to its Wikimedia Commons category, and so on (e.g. Vienna). Most infoboxes in Wikipedia are now automatically created from Wikidata data.

So, each object should have its own Wikidata entry. Of course, you should check if a Wikidata entry already exists – if yes, check if the data is complete. It should have values for (if available):

• label and description (at least in local language, preferred also in English)
• instance of (e.g. memorial monument, sculpture, …)
• depicts (the entity being depicted)
• dedicated to
• geographic coordinates
• image (link to a Wikimedia Commons image)
• commons category (link to the Wikimedia Commons category for this object)
• country
• administrative territorial entity
• inception (start date; if possible the date of its inauguration)
• material used

When done, edit the Wikimedia Commons category, and add the following line (replace „Q1234“ by the ID of the wikidata entry), so that the category gets a nice infobox on the side:

{{Wikidata Infobox|qid=Q1234}}

OpenStreetMap

Finally, the map feature in OpenStreetMap. This can be a node or an area. If the object is located on the wall of a building I make the node a part of the building contour. The entry should have the following tags:

• tourism=artwork, artwork_type=](https://wiki.openstreetmap.org/wiki/Key:artwork_type) and/or [historic=memorial](https://wiki.openstreetmap.org/wiki/Tag:historic%3Dmemorial), [memorial=
• name=*
• wikidata=Q1234 (the wikidata ID from above)
• subject:wikidata=Q2345 (the wikidata ID of the main subject)
• artist_name=*
• artist:wikidata=Q3456 (the wikidata ID of the artist, resp. the artists separated by „;“)
• start_date=* (the date of the inauguration)
• year_of_construction=* (if there’s information when the object was being built, this can be a range)
• material=*

Further tags like wikipedia=](https://wiki.openstreetmap.org/wiki/Key:wikipedia), [image=, wikimedia_commons=* are not necessary, as this information can be read from the Wikidata entry. I do not remove these tags though, if I find them.

Often, map features already have a wikidata/wikipedia-tag which points to the person which it memorizes. This is wrong, because this should be a „subject:wikidata“ resp. „subject:wikipedia“ tag. Please change this.

Final

How can you test your entries? There’s a list of tools which let you explore wikidata tags. I recommend OpenStreetBrowser, which is an application for OpenStreetMap data written by myself. It will show images of the map features and excerpts of Wikipedia articles.

Examples

Here are some examples of such features:

• Goethe memorial near the Viennese ring road: Wikimedia Commons category, Wikidata entry, OpenStreetMap feature, OpenStreetBrowser
• „Hill arches“ by Henry Moore at Karlsplatz: Wikimedia Commons category, Wikidata entry, OpenStreetMap feature, OpenStreetBrowser
• Mosaic „The tanners as founders of the labour union“ on a building: Wikimedia Commons category, Wikidata entry, OpenStreetMap feature, OpenStreetBrowser
• Mosaic of locomotive „Philadelphia“ on the facade a building: Wikimedia Commons category, Wikidata entry, OpenStreetMap feature, OpenStreetBrowser
• Zirkusgasse 11 (see picture above) – here I haven’t done a Wikidata entry (yet?): Wikimedia Commons image, OpenStreetMap feature, OpenStreetBrowser

21.07.2020-27.07.2020

Eilmeldung

• Dorothea erinnert > uns daran, den 16. Geburtstag von OSM zu feiern und gibt Anregungen, wie das geschehen könnte!

In eigener Sache

• [1] 10 Jahre Wochennotiz! Wir danken allen unseren Lesern für das Interesse und die Treue.

Mapping

• Matthew Woehlke schlägt das neue Tag sport=four_square für eine Sportart mit dem Namen Four square vor.
• Über Michael Montanis Vorschlag > , den neuen tag natural=bare_soil für ein Gebiet einzuführen, das ohne jegliche Vegetation nur von Boden bedeckt ist, kann noch bis zum 7. August abgestimmt werden.
• Nach der Ankündigung der British Geospatial Commission, dass eindeutige Identifikatoren für Adressen und Straßen als offene Daten zur Verfügung stehen werden (wir berichteten bereits früher), wurden Vorschläge erarbeitet für ref:GB:uprn (eindeutige Eigentumsreferenznummer) und ref:GB:usrn (eindeutige Straßenreferenznummer). Es hat eine Diskussion über die Talk-GB- und Tagging-Mailinglisten stattgefunden.
• “Aktuelle Mapillary-Bilder auswerten”. Das ist der aktuelle Schwerpunkt der Woche, noch bis nächsten Freitag. Eigene Ideen und Vorschläge? Einfach ins “Schwerpunktideendepot” auf derselben Seite eintragen.
• JesseFW lieferte > uns eine Erklärung dafür, warum die Küstenlinien auf Carto seit Januar 2020 nicht mehr aktualisiert wurden: Es scheint, dass die Aktualisierung dieser ein weiteres Opfer einer Editierschlacht am Río de la Plata war (über den wir bereits früher berichteten).
• Benutzer mahdi1234 veröffentlichte > eine Anleitung für Anfänger, um Änderungen in OSM im Laufe der Zeit zu visualisieren. Er zeigt im Detail, wie man einen Zeitraffer mit OSM-Daten erstellt.
• Der ADFC Frankfurt a. M. ruft auf Twitter dazu auf, Ghostbikes (engl. Geisterfahrräder) in OSM zu mappen. Diese erinnern an tödlich verünglückte Radfahrer.

Community

• Christoph Hormann wendet sich gegen die Bezeichnung von Befürwortern des craft mappings in OpenStreetMap als Konservative, die gegen Veränderungen sind. Er ist der Meinung, dass dies Teil einer neuen Erzählung ist, die in der OSMF-Politik kommuniziert wird, d.h. der Notwendigkeit einer Änderung von OpenStreetMap und der konservativen Opposition der Craft Mapper gegen OpenStreetMap.
• Steven chattet (Audio auf englisch) mit María Arias de Reyna, leitende Software-Ingenieurin bei Red Hat und ehemalige Präsidentin der Open Source Geospatial Foundation, die kürzlich als Hauptrednerin vor dem FOSS4GUK auftrat. Es geht um María de Reynas aktuelle Arbeit, ihren kürzlichen Vortrag bei FOSS4GUK, aber auch um das Betrügersyndrom und Science Fiction.
• Das deutsch-französisches Kartierungsprojekt Kartodistrict des Eurodistrikt Strasbourg-Ortenau ruft im Rahmen seiner Karto-Challenge zum Mapping bestimmter Themen in OSM bis zum 30. September auf. Als Gewinn winken Geschenkkörbe.
• Øukasz berichtete > über seine Erfahrungen aus zwei kürzlichen Interaktionen mit CartONG zur Entwicklung eines Kennzeichnungsschemas für Flüchtlingslager und zum Import eines Datensatzes aus einem UNHCR-Flüchtlingslager. Léonie Miège von CartONG antwortete > in einem Blog-Kommentar.
• Richard Fairhurst kündigt > einen neuen Leitfaden (*.pdf ) für Dateneigentümer an, der einen Beitrag zu OSM leisten soll. Er ist ein Ergebnis der Zusammenarbeit mit zwei Gemeinden in Großbritannien, die kürzlich vom Open Data Institute finanziert wurden, um die Nutzung und den Beitrag zu offenen Kartendaten wie OSM zu untersuchen. (Automatische Übersetzung der .pdf-Datei nicht möglich.)
• Open Street Map US veröffentlicht > ihren Juli-Newsletter 2020.
• Ein Zeitraffer-Video von IgorEliezer zeigt die 3-D-Modellierung eines Museumsgebäudes in São Paulo (Brasilien). Die 3-D-Animation am Anfang und Ende des Videos nutzt die F4Map und die Modellierung Kendzi3D innerhalb des JOSM-Editors.

Importe

• Alex Hennings hat die von Facebook und ESRI vorgeschlagenen ‘not an import’-Importe (wir berichteten) von ArcGIS-Datensätzen über RapiD oder das JOSM MapWithAI-Plugin geprüft und für unzulänglich befunden. Besonders beunruhigend war das Fehlen der erbetenen Überprüfung durch die Gemeinschaft auf der “imports-us“-Mailingliste.

OpenStreetMap Foundation

• Der OSMF-Vorstand konsultiert > die Gemeinschaft zur geplanten Einstellung eines Senior Site Reliability Engineer. Dies ist die erste Stelle nach dem neuen Einstellungskonzept, welches im osmf-talk vor einigen Tagen diskutiert >
  wurde.

Veranstaltungen

• Ein Tagungsband des akademischen Tracks der State of the Map 2020 wurde veröffentlicht.

Humanitarian OSM

• HOT führt eine Online-Umfrage unter Personen durch, die RapiD verwendet haben. Die Daten werden verwendet um zu verstehen, wie RapiD für eine Vielzahl von Benutzern zugänglicher und nutzbarer gemacht werden könnte.

Karten

• Nuno Caldeira gratuliert (Twitter) der portugiesischen nationalen Notfall- und Katastrophenschutzbehörde zur Verwendung der OSM-Daten und zur korrekten Angabe des Urheberrechtsvermerks auf der Karte zu einem großen Waldbrand, der sich letzte Woche in Portugal ereignete.
• Taiwan hat viele abgelegene Inseln. Die Insel Dadan in Kinmen ist eine der abgelegensten. Der italienische Kartograph MG hat eine Webseite (Kinmen-Rising-Projekt > ) über seine Reise mittels der OSM Basiskarte vorgestellt, bei dem er eine Menge POIs auf der Insel sammelte – und natürlich auch viele Fotos von seiner Reise zeigt.

Programme

• In einem veröffentlichten Paper wird die wachsende Menge frei verfügbarer Informationen (wie Luftbilder) analysiert, um Kartographen bei ihrer Arbeit zu unterstützen und leiten: Künstliche neuronale Netze identifizieren dabei Regionen von Interesse, in denen OSM aktualisiert werden sollte.
• Venkanna Babu Guthula hat Label-Pixels herausgebracht, ein Werkzeug zur semantischen Segmentierung von Luftbildern mit Hilfe von künstlichen neuronalen Netzen (full convolutional networks, FCNs), das für die Extraktion des Straßennetzes entwickelt wurde.

Releases

• Sarah Hoffmann kündigt das Release 1.3.0 von osm2pgsql mit der (noch experimentellen) neuen Flex-Ausgabe an. Diese erlaubt flexibel angepasste Exporte von OSM-Daten. Besonderer Dank geht an Jochen Topf, der den größten Teil des Codes dafür beigesteuert hat.
• Der iD-Editor wurde aktualisiert und verfügt jetzt über Touch-Unterstützung, so dass er auf Tablets verwendet werden kann (Smartphone-Bildschirmgrößen werden noch nicht vollständig unterstützt). Weitere Highlights sind integrierte Qualitätsprüfungen und mehrfach-Selektion.
• Mit der Veröffentlichung der neuesten Version von iD zeigt das “Locator-Overlay” beim Herauszoomen ein halbtransparentes Overlay. Über den OpenStreetMap-Editor-Layer-Index ist das neue Overlay jetzt auf OpenStreetMap.org und bald auch auf dem HOT Tasking Manager und anderen Instanzen von iD verfügbar. Zuvor waren Standorte in der iD schwer zu finden.

Kennst du schon …

• … Finde.cash? Es zeigt Banken und Geldautomaten mit Zugehöhrigkeit zum Automatenverbund auf einer Karte an und bietet Routenplanung zu Fuß, mit Fahrrad oder ÖPNV mit vier Hintergrund-Optionen inkl. Open Cycle Map. Fehlende Geldautomaten lassen sich direkt einfügen.
• … MyOSMatic, den freien Webservice, der es ermöglicht, Stadtpläne unter Benutzung der OSM-Daten zu generieren und in den Formaten PNG, PDF und SVG druckfertig weiter zu verwenden? Menüführung in 25 Sprachen.
• … OSM Quality Ranking (Beta)? Es bewertet 51 US-Städte nach der Qualität ihrer OSM-Daten, indem es Straßengeometrien, Straßen-Tags und Relationen überprüft.

Weitere Themen mit Geo-Bezug

• Die Kartensammlungen der Brooklyn Historical Society umfassen über 1.500 digitalisierte historische Karten vom siebzehnten Jahrhundert bis zur Gegenwart.
• Nathanael Peterlini zeigt anhand des Kosovo und Palästinas die unterschiedliche karthografische Abbildung ihrer nicht durch alle Staaten der Welt anerkannte Unabhängigkeit durch Apple, Google und OSM.
• GPS-Radler berichtet, dass Garmin offenbar Opfer einer Ransomware-Attacke wurde, die auf das Konto der Malware WastedLocker gehen soll. Der Angriff wird einer russischen Hackergruppe zugeschrieben. Inzwischen sind viele Dienste wieder online.
• Zur integrierten Bereitstellung von unterschiedlichen Ortungsdaten aus UWB, BLE, RFID, 5G oder GPS wurde der neue Industriestandard Omlox geschaffen, der alle diese Technologien für zahlreiche Geo-basierte Anwendungen nahtlos verfügbar macht.
• Ein Update in Google Maps ermöglicht es in 10 Städten wie Chicago, Montreal und London, Routen unter Berücksichtigung der verfügbaren Fahrradvermietstationen zu planen. Cities Today erklärt > die Hintergründe.
• Der Tagesspiegel befragte 21.000 Menschen darüber, was ihnen auf der Straße Angst macht und wie Berlins Radwege in Zukunft aussehen sollen. Die Ergebnisse werden mit einer Reihe von Grafiken erläutert.

Wochenvorschau

Wo	Was	Wann	Land
London	London Missing Maps Mapathon (ONLINE)	2020-08-04
Mannheimn	Mannheimer Mapathons – Treffen im Luisenpark	2020-08-04
Stuttgart	Stuttgarter Stammtisch	2020-08-05
San José	Civic Hack & Map Night (online)	2020-08-06
Taipei	OSM x Wikidata #19	2020-08-10
Hamburg	Hamburger Mappertreffen	2020-08-11
Munich	Münchner Stammtisch	2020-08-12
Berlin	146. Berlin-Brandenburg Stammtisch	2020-08-14
Zurich	120. Mapping-Party/OSM Meetup Zurich	2020-08-15
Bonn	130. Bonner OSM-Stammtisch (Online)	2020-08-18
Lüneburg	Lüneburger Mappertreffen	2020-08-18
Cologne	Köln Stammtisch ggf. ONLINE	2020-08-19
Kandy	2020 State of the Map Asia	2020-10-31-2020-11-01

Hinweis:
Wer seinen Termin hier in der Liste sehen möchte, trage ihn in den Kalender ein. Nur Termine, die dort stehen, werden in die Wochennotiz übernommen. Bitte prüfe die Veranstaltung in unserem öffentlichen Kalendertool und korrigiere bitte die Einträge im Kalender, wenn notwendig.

Diese Wochennotiz wurde erstellt von Anne Ghisla, MatthiasMatthias, Nakaner, Nordpfeil, Rogehm, TheSwavu, derFred.

21/07/2020-27/07/2020

Breaking news

• Dorothea reminds us to celebrate the 16th anniversary of OSM on 8 August. She provides some ideas on how that can be done!

About us

• Happy Birthday OSM-Wochennotiz! It was ten years ago this week that the first issue (automatic translation) of the Wochennotiz was published.

Mapping

• Matthew Woehlke has proposed the new tag sport=four_square for a sport called Four square.
• Michael Montani’s proposal to introduce a natural=bare_soil tag for ‘an area covered by soil, without any vegetation’ is currently open for voting until 7 August.
• Following the British Geospatial Commission’s announcement that unique identifiers for addresses and streets would become available as open data (we reported earlier), proposals have been produced for ref:GB:uprn (unique property reference number) and ref:GB:usrn (unique street reference number). Discussion has taken place on the Talk-GB and Tagging mailing lists.
• JesseFW provided us with an explanation as to why the coastlines on Carto hadn’t been updated since January 2020. It seems that the coastline update was another victim of the Río de la Plata edit war (which we reported on earlier).
• User mahdi1234 published a guide for beginners on visualising changes in OSM over time. He shows in detail how to create a time lapse with OSM data.

Community

• Christoph Hormann objects to the framing of craft mappers in OpenStreetMap as conservatives opposed to change. He feels that this is part of a new narrative being communicated in OSMF politics; that is, the need for change in OpenStreetMap, and craft mappers’ opposition to change.
• On the Geomob podcast Steven Feldman chats with recent FOSS4GUK keynote speaker María Arias de Reyna, a senior software engineer at Red Hat and former President of the Open Source Geospatial Foundation. The episode deals with María’s current work, and her recent talk at FOSS4GUK, but also imposter syndrome, and science fiction.
• Øukasz recounts their experience of two recent interactions with CartONG, one with developing a tagging schema for refugee camps and the other with importing a UNHCR refugee camp dataset. Léonie Miège, from CartONG, responded in a blog comment.
• Richard Fairhurst has written a new guide for data owners wishing to contribute to OSM. It is an output of cooperation with two local councils in the UK, which were recently funded by the Open Data Institute to investigate using and contributing to crowdsourced open map data such as OSM.
• OpenStreetMap US has published its July 2020 newsletter.
• Igor Eliezer has made a video showing how the 3D modelling of the Museu Paulista (São Paulo, Brazil) was re-worked in OpenStreetMap using the JOSM editor. The 3D preview at the beginning and end of the video is from the F4Map website and, during modelling, in Kendzi3D within the JOSM editor.

Imports

• Alex Hennings has reviewed Facebook and ESRI’s proposed ‘not-an-import’ imports (we reported earlier) of ArcGIS datasets through RapiD or JOSM MapWithAI plugin and found them wanting. Of particular concern was the lack of solicited community review on the imports-us mail list.

OpenStreetMap Foundation

• The OSMF board would like to consult the community on its hiring plans for a Senior Site Reliability Engineer. This is the first position based on the hiring framework which osmf-talk discussed a few days ago.

Events

• Proceedings of the Academic Track at the State of the Map 2020 have been published.

Humanitarian OSM

• HOT is conducting an online survey of people who have used RapiD to find out what their experience was. The data will be used to understand how RapiD could be made more accessible and usable for a variety of users.

Maps

• Nuno Caldeira congratulated, through Twitter, the Portuguese National Emergency and Civil Protection Authority for using OpenStreetMap data, and correct attribution, in a tweet about a large forest fire that occurred last week in Portugal.
• Taiwan, a nation in the Far East with special political status, has lots of outlying islands. Dadan Island in Kinmen is one of the most remote. MG, the Italian mapper, shares the Kinmen information website he created, The Kinmen Rising Project on the OSM Taiwan Telegram channel, showing photos from his journey with OSM as the base map, and of course he mapped a lot of POIs on the island.

Software

• A research paper analyses the growing amount of freely available spatio-temporal information (such as aerial imagery) to support and guide mappers in their work. Artificial neural networks identify regions of interest where OSM is likely to require updating.
• Venkanna Babu Guthula has released Label-Pixels, a tool for semantic segmentation of remote sensing images using fully convolutional networks (FCNs), designed for extracting road networks from remote sensing imagery.

Releases

• Sarah Hoffmann announced release 1.3.0 of osm2pgsql with the addition of the (still experimental) new flex output. Jochen Topf, the main contributor for this release, explained how this gives more flexibility when exporting data from OSM to PostgreSQL.
• The iD editor was updated and now has touch support, so it can be used on tablets (smartphone sized screens aren’t fully supported yet). Other highlights are integrated quality checks and multi-selection editing.
• With the release of the latest version of iD, the ‘locator overlay’, a semi-transparent overlay when zoomed out, has been rebuilt. Via the OpenStreetMap editor-layer-index, the new overlay is now available on OpenStreetMap.org, and soon on the HOT Tasking Manager and other instances of iD.

Did you know …

• … Finde.cash displays banks and ATMs with the respective ATM networks on a map? It also offers route planning by foot, bicycle or public transport, and four background options including OpenCycleMap. Missing ATMs can be inserted directly. The map is worldwide but the menu is only available in German.
• … MyOSMatic, the free of charge web service to generate city maps using OSM Data, which are available in PNG, PDF and SVG ready to print? Menus are available in 25 languages.
• … the ‘OSM Quality Ranking’ (Beta) assesses and ranks 51 US cities by OSM data quality, checking geometry and tagging for streets, roads, and relations?

Other “geo” things

• Brooklyn Historical Society’s map collection includes over 1,500 digitised historical maps spanning the seventeenth century to the present.
• Nathanael Peterlini examined (automatic translation) difficulties cartographers face when trying to please all of their users’ political views. They look at the cases of Kosovo and Palestine and how they are treated by Apple, Google, and OSM.
• Garmin has been the victim of a ransomware attack. As a result, many of their online services were interrupted or are still down.
• An update to Google Maps has allowed docked bike share riders in cities such as Chicago, Montreal and London to see end-to-end walking and cycling directions for their journey integrated with bike and dock availability. Cities Today gave some background to the new service.
• Tagesspiegel interviewed 21,000 people about what scares them on the street and what Berlin’s bike paths should look like in the future. The results are explained (automatic translation) with a series of graphics.

Upcoming Events

Where	What	When	Country
London	London Missing Maps Mapathon (ONLINE)	2020-08-04
Mannheimn	Mannheimer Mapathons – Treffen im Luisenpark	2020-08-04
Stuttgart	Stuttgarter Stammtisch	2020-08-05
San José	Civic Hack & Map Night (online)	2020-08-06
Taipei	OSM x Wikidata #19	2020-08-10
Hamburg	Hamburger Mappertreffen	2020-08-11
Munich	Münchner Stammtisch	2020-08-12
Berlin	146. Berlin-Brandenburg Stammtisch	2020-08-14
Zurich	120. Mapping-Party/OSM Meetup Zurich	2020-08-15
Cologne Bonn Airport	130. Bonner OSM-Stammtisch (Online)	2020-08-18
Lüneburg	Lüneburger Mappertreffen	2020-08-18
Cologne	Köln Stammtisch ggf. ONLINE	2020-08-19
Kandy	2020 State of the Map Asia	2020-10-31-2020-11-01

Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.

This weeklyOSM was produced by Anne Ghisla, MatthiasMatthias, Nakaner, Nordpfeil, PierZen, Polyglot, Rogehm, SK53, TheSwavu, derFred, richter_fn.

Торговые центры — досадные белые пятна на нашей карте: в них слишком много магазинов. Обычная практика — пройти мимо всех, сфотографировать и записать данные, а потом отрисовать, — для ТЦ не работает, потому что это не одно-два заведения на здание, а сотня-две. Целый день убить на один дом! Поэтому в городе может быть десять магазинов The Body Shop, но вы не найдёте в OpenStreetMap ни одного, потому что все они в торговых центрах, которые лень обходить.

Помня об этом, позавчера я посидел часик и отрисовал две трети магазинов в рижском ТЦ Spice, пользуясь буклетом со схемой, стащенной из этого центра. Порадовался, как удобно это в iD, и почувствовал, как приношу пользу будущим пользователям карты. Прямо захотелось ещё нагуглить схем торговых центров и щедро рассыпать POI по Риге и Минску. К чёрту схемы помещений, были бы сами магазины.

Меня остановил Павел Гаврилов:

Я правильно понимаю, что этот пакет изменений надо откатывать, потому что у нас нет ЯВНОГО разрешения использовать данные с этой коммерческой карты? Аргумент «я там ходил, поэтому имею право перерисовывать чужую карту» с Гуглом и Яндексом почему-то не принимается.

Я сначала разозлился и коротко ответил, что был там и помню все магазины (что правда для большей части внесённого). Потом задумался. Я не сканировал и не подкладывал схемы из буклета, чтобы нарисовать поэтажные планы. Только очень примерно расставил точки магазинов, взяв их название и тип. После того, как прошёл, глядя на карту, и убедился, что более-менее соответствует. Но в картировании пошёл дальше и добавил точки со второго этажа и из соседнего здания. Всем же лучше от этого: и посетителям, и магазину, и карте.

Чем эта аргументация отличается от срисовывания адресов с карты Яндекса, когда контуры зданий уже есть в OpenStreetMap? Проезжали деревню, видели несколько адресов, с яндексом совпадают. Технически это даже не копирование данных: смотрим числа, запоминаем, расставляем на карте уже по памяти.

В нашем проекте есть юридическое слепое пятно, о котором мы стараемся не задумываться: можно ли использовать рекламные и информационные стенды и буклеты для уточнения OpenStreetMap?

Очевидно, что такие материалы публикуются с целью достичь максимального количества читателей. План застройки квартала висит на крупном щите у тротуара. Схема садоводческого товарищества встречает на въезде, чтобы водители не шарахались по проездам, а сразу ехали куда надо. Компании посвящают отдельные страницы сайтов планам проезда: там и адрес, и координаты, и карта, а то и две. Они печатают свои адреса на визитках. В торговых центрах раздают буклеты, чтобы задержать покупателей: вокруг столько интересного!

Присутствовать на картах важно для всех. Поэтому магазины, компании, торговые комплексы сами идут к 2ГИС, яндексу или посредникам, чтобы их можно было найти. За четыре дня до меня в тот ТЦ зашла «рокетдата», добавив в случайные координаты внутри здания аптеку. Аптека заплатила компании, чтобы появиться в OpenStreetMap. Откажется ли ТЦ от того, чтобы кто-то бесплатно перенёс их план на карту, которую используют примерно все? Разве что из подозрительности: обычно это стоит больших денег; бесплатное картирование бывает только в мышеловке.

Сложно понять, где кончается ground truth и начинается копирование чужих данных. Отметить «пятёрочку» по фотографии, не зайдя внутрь и не убедившись, что это продуктовый магазин, нормально? А натолкнуться на дверь с двумя десятками плашек всяких адвокатов и турфирм, не открыть её и внести всё это в OSM? Нарушает ли это права владельца этого бизнес-центра? Прощёлкать панорамы улицы и добавить на карту все POI, что видны на фотографиях, нарушает авторское право фотографа? Можно ли, взяв визитку с адресами филиалов турфирмы, закартировать их?

Фотография © mapfool, Mapillary, CC-BY-SA

Общепринятое мнение опытных участников проекта — нет, без явного разрешения никакие источники использовать нельзя. Как бы все стороны ни хотели появления данных на карте, должен произойти акт разрешения. При этом часто простого согласия голосом недостаточно, и подписи секретаря тоже. Формально, хочешь срисовать план торгового центра — иди к директору и требуй бланк с печатью. Увидел на фотографии пятиэтажный дом и хочешь проставить тег этажности — спрашивай разрешения у фотографа. Подруга говорит, что за углом открылся ресторан, — убедись, что она разрешает использовать эти слова для уточнения карты.

Эти требования кажутся смешными, но обоснования ответов на них определяют будущее OpenStreetMap. Мы уже более-менее разобрались с рисованием геометрически протяжённых объектов: дорог, лесов, городов. С адресами всё тоже более-менее ясно. Есть крупные источники геоданных, которые чаще всего нельзя использовать, есть государственные и открытые данные, есть снимки. Одно разрешение открывает геоданные целого города или страны, поэтому мы продолжаем писать запросы. Ответили отрицательно — не беда, возьмём другие источники или снимки. У нас есть выбор.

Для заведений выбора нет. Никаких крупных баз, которые потенциально могут разрешить использование. Либо обходить ногами и записывать, либо просить миллион разрешений от миллиона источников, в каждом до сотни заведений. Что делать — выделить шкаф для складирования ответов? Или перечитать законы и пересмотреть условия использования информационных материалов?

POI не могут ждать. Дороги пролежат десятки лет и их названия не изменятся, деревни тоже дождутся заблудшего картографа. Рано или поздно мы нарисуем административные границы и все велодорожки, поэтому нет смысла спешить, подключать нейросети и тырить данные из крупных ГИС. Но в случае заведений политика ожидания не работает. Салоны красоты появляются и исчезают; приходит вирус — и торговые центры вычищаются; наносить магазин за углом бесполезно, когда весь квартал ходит в этот магазин уже десять лет.

Легко делать самую актуальную карту в контексте развязок и новостроек, сложнее следить за свежестью магазинов в ближайшем ТЦ. Муторно и трудно увидеть своими глазами и записать все заведения в своём районе, невозможно повторить такой обход во второй, в третий раз. Сообщество OSM с подозрением смотрит на импорты и не уверено, что можно использовать любые сторонние материалы, от списка адресов на сайте компании до плана эвакуации на стене. Даже приложения, которые позволяют добавлять заведения любому, кто проходит мимо, не устраивают многих осмеров. Может ли с такими ограничениями наш проект быть надёжной картой не только улиц, но и заведений?

Я бы хотел порисовать магазины в торговых центрах и сети закусочных по информации с сайтов и буклетов, но не уверен, что это можно. Поэтому я сделал тему на форуме: делитесь в ней мыслями про юридические ограничения и опытом массового рисования заведений. Давайте решим, где факты, а где авторское право на базу данных.

Wenn man als Suchbegriff “Knittelfeld, Freiheitsallee 73” eingibt, dann erscheint im linken Adressfeld unter anderem “Einödhof”. Dieser Begriff ist falsch. Denn er bezeichnet einen Ortsteil, welcher einige km südlich liegt! Bitte “Einödhof” entfernen! Sonst stimmt alles! Gruss Dieter64

นาวา

I learned the basics of OpenStreetMap and began doing things that were cool.

Что это я всё хвалю iD — у него тоже проблем хватает («ахаха» — раздаётся от жосмера в голове). Например, Саймон Пул четыре дня назад заметил, что в некоторых регионах данные не подгружаются, без причин и без ошибок. Какие-то слова про undefined в консоли, и всё.

Позавчера Квинси понял, что выпадают объекты, нарисованные анонимными пользователями до 2009 года. У этих объектов нет поля uid, чего редактор не ожидал. Но тогда вопрос, почему раньше этой пропажи никто не замечал? Ответ — в JSON.

Мало кто любит XML. Это структурированный формат, который может хранить любую структуру данных, но слишком многословен и требует сложных преобразований. С популярностью JavaScript разработчики предпочитают использовать другой формат хранения данных, JSON (JavaScript Object Notation). Формат жёстко регламентирован, но по сути, представляет собой кусок кода, который интерпретатор JS может быстро превратить в объект. Сюрпризов у него никаких, структура очевидная для программистов, в отличие от XML, поэтому формат пихают везде: например, вам может быть знаком GeoJSON.

OSM API всегда отвечал в формате XML. Но в сентябре 2018 года cgimap научился возвращать ответ в формате json. Для этого в запросе нужно указать правильный заголовок Accept или добавить в конец расширение .json (например). Одним из первых новому формату научился важнейший запрос /map (получение всех данных в прямоугольнике), затем пошли остальные. Но, поскольку формат ещё не поддерживал Rails Port (часть API, написанная на Ruby on Rails), json временно отключили.

Разрыв нужно было закрывать: участник Mmd в мае 2019 года сделал пул-реквест в вебсайт, но мы знаем, как у нас проходят пул-реквесты. Второй пул-реквест он создал в декабре. Он был проще, обсуждение сразу пошло: всего через полсотни комментариев, в феврале, правки приняли, и теперь объекты можно получать в любом из двух форматов.

Тут все посмотрели на iD. Для кого ещё писали поддержку json, как не для редактора на JavaScript? И да, всего через неделю соответствующие вызовы заменили — поддержку нового формата тот же Mmd написал ещё год назад. Но свежий релиз редактора готовился-готовился, прошёл один месяц, второй... В общем, строчка про json утонула в списке изменений версии 2.18, вышедшей две недели назад. Отсюда и проблема, найденная Саймоном: формат ответа API поменялся, его обработка тоже, и анонимные правки забыли протестировать. Ошибку починили буквально вчера.

По замерам Mmd, использование json для скачивания данных ускорило iD примерно вдвое. Перемещение карты в редакторе действительно ощущается быстрее, контрастируя с заторможенным интерфейсом редактирования тегов.

Подгрузку данных в редакторе ещё можно ускорить, и даже в несколько раз. Сам запрос /map невыносимо медленный: сервер делает несколько запросов к базе данных на каждый объект в ответе, что, как посчитал Дорофей «Komяpa», ограничивает скорость получения данных до примерно 2000 объектов в секунду. Именно поэтому iD разрешает редактирование от 16 уровня масштаба, а не дальше. В 2016 году Дорофей переписал запрос к карте на чистый SQL, ускорив его на порядок, но его предложение погрязло в комментариях, а после добавления формата json и вовсе устарело. То есть, мы знаем, что скачивание данных можно ускорить, но для поддержки быстрого кода нужны знания PostgreSQL, которых нет ни у кого из админов.

Обновление: Mmd в комментариях замечает, что запрос /map переписали в 2018 году, ускорив его даже лучше, чем это сделал Дорофей. Так что последний абзац уже неактуален.

• https://wiating.pl/mapa/
• https://mapa-turystyczna.pl

On Saturday, 8th of August 2020,
we will celebrate 16 years of OpenStreetMap!

Planning an online party or mapathon?

You can use the BigBlueButton video server of the OpenStreetMap Foundation! To get a free account and your own video room, please signup and send an email to communication@osmfoundation.org with subject: BigBlueButton access.

• You can use your video room even after the birthday, for any OSM-related event.
• Community members in low-bandwidth environments may benefit from using BigBlueButton’s low-bandwidth settings.
• Please add your event to the OSM wiki! If wiki editing isn’t your thing, email communication@osmfoundation.org with your event details and we’ll add it

Other ideas

• Post why you love OpenStreetMap. We will publish a collection of messages later
• Post a photo of yourself holding a written message  
• Use the hashtag #OpenStreetMap16 on social media
• Make/order a birthday cake. See previous examples of OSM cakes for inspiration. Don’t forget the attribution!
• If your photos are accompanied with the text “CC-BY-SA 2.0” (or another open license), we can add them to the OSM wiki (or feel free to add them yourself! ~ register here).
• Do you have more ideas? Share them in the comments

Join us!

Observance of the anniversary of the creation of OpenStreetMap is held on or about the 9th of August, which is the anniversary of the registration of the OpenStreetMap.org domain name. The concept of OpenStreetMap predates the domain name registration, but that seems a suitable anniversary date

Get notified about new blogposts: Subscribe to the RSS feed!

Do you want to translate this and other blogposts in another language..? Please send an email to communication@osmfoundation.org with subject: Helping with translations in [language]

The OpenStreetMap Foundation is a not-for-profit organisation, formed to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. The OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap project, is financially supported by membership fees and donations, and organises the annual, international State of the Map conference. It has no full-time employees and it is supporting the OpenStreetMap project through the work of our volunteer Working Groups. Please consider becoming a member of the Foundation.

OpenStreetMap was founded in 2004 and is a international project to create a free map of the world. To do so, we, thousands of volunteers, collect data about roads, railways, rivers, forests, buildings and a lot more worldwide. Our map data can be downloaded for free by everyone and used for any purpose – including commercial usage. It is possible to produce your own maps which highlight certain features, to calculate routes etc. OpenStreetMap is increasingly used when one needs maps which can be very quickly, or easily, updated.

The error Al Midhnab, Al Qaşīm

Al Midhnab, Saudi Arabia

the correct (Al Mithnab)

Wrong with the translation into Arabic الميدهناب the correct المذنب

Please correct the error and translation

Привет. Это моя первая запись в дневнике. В карантин появилось время заняться OSM. Последние несколько дней занимаюсь правками своего жилого массива. Поставил себе задачу полностью актуализировать все дороги массива Авиасозлар-1. Завтра утром планирую выехать на велосипеде в очередной OSM-поход по массиву.

I’ve done a good amount of work to add basic geometry to Anchorage in the past. Now, I would like to store more data inside the polygons for buildings that have been created.

It is a difficult task to do quality control on the wide number of churches, schools, businesses, etc. in Anchorage because it is just too big. 100’s of buildings in each category where there are also points or multipolgons as well. To accomplish a definitive test of which polygons of a certain type have a data tag, I’ll need to use the overpass API. Fortunately, the work has mostly been done to use it as a tool by relying on R and the library osmdata.

For example, I’ve been able to query all of the amenities with “place_of_worship” to see what tags are available, and map the polygons on top of an osm basemap with the following code.

library(osmdata)
library(leaflet)
library(dplyr)
x <- opq(bbox = c(-150.092146, 61.483194, -148.981596, 60.814537)) %>% 
  add_osm_feature(key = 'amenity', value = "place_of_worship", value_exact = FALSE) %>%
  osmdata_sf()
y <- x$osm_polygons %>% filter(is.na(denomination))
leaflet(y) %>% addTiles() %>% addPolygons(popup = ~y$name)
y %>% as.data.frame() %>% select(name, email, website, phone, denomination) 

…This will show me which places of worship still need to have a denomination added. And I reuse this for different tags I want to add.

theguardian:
“Microsoft’s Flight Simulator is a ticket to explore the world again” ( 30 Jul 2020 )

“Most cities are procedurally generated by the AI, based data from OpenStreetMap and an algorithm that provides architectural rulesets for the program to work from.”

https://www.theguardian.com/games/2020/jul/30/microsoft-flight-simulator-game

Today is System Administrator Appreciation Day and we would like to thank our sysadmins for the awesome work that they are doing!

Get notified about new blog posts: Subscribe to the RSS feed!

J’ai récemment repris l’entreprise de mettre à jour l’intégralité des lignes de transport en commun Ginko à Besançon. Je m’étais chargé de 24 lignes l’été passé sans finir le travail. Une année plus tard, la situation n’a pas été améliorée et j’ai décidé de terminer le travail. Étant seul sur la tâche, des erreurs sont possibles sur le réseau et je m’en excuse d’avance. Ayant bientôt terminé, j’en profite pour donner mon avis sur le modèle actuel autour des transports en commun. Cela pourra s’avérer utile pour quiconque souhaitera apporter des modifications ultérieures sur le réseau Ginko, son propre réseau local, ou s’intéresse aux transports en commun en général.

État de l’art

Au cours de son évolution, la méthode de cartographie des transports en commun a compté quatre propositions majeure à savoir :

• PTv1
• Modèle Oxomoa
• PTv2
• Modèle Affiné

Le wiki dispose d’un portail introduisant du thème. Il semble que les premiers efforts francophones datent de 2010, année de traduction de la page en français. Depuis 2015, la page redirige vers la page du modèle PTv2. Je ne ferai qu’un survol des modèles et vous invite à consulter chacune des pages citées pour plus de détails.

Modèle PTv2

Actuellement, une ligne de transport en commun est construite sur plusieurs échelles emboîtées :

• Les arrêts sont définis par des paires de nœuds pour localiser d’une part le quai où attend le passager et la position où s’arrête le véhicule sur sa voie :

public_transport=platform highway=stop_position

Autant le premier est généralement placé sur la borne indiquant l’emplacement de l’arrêt, autant le second peut difficilement répondre au critère de vérifiabilité sur lequel est basée OSM. Un argument en faveur de l’utilisation des deux attributs est qu’il existe des cas où le lieu d’embarquement, où s’arrête le véhicule, n’est pas situé au même endroit que le quai. Ce qui est entendable mais qui personnellement ne permet pas sa justification.

• Les deux nœuds sont ensuite intégrés au sein d’une relation stop_area, celle-ci a pour but de regrouper les éléments d’un arrêt et il est possible de l’utiliser pour associer des caractéristiques physiques du quai à savoir la présence d’un abri, d’un banc, d’une poubelle, etc. Cette relation est destinée au consommateur qui nécessiterait de renseigner ces informations sans avoir à chercher les éléments autour du quai d’embarquement. Cette relation repose cependant sur l’existence des deux nœuds précédents. Son utilisation reste cependant optionnelle et n’est nullement obligatoire.

type=public_transport public_transport=stop_area

• Une relation route permet de tracer l’itinéraire proprement-dit, en sélectionnant les divers tronçons de route prééxistants ainsi que les arrêts à la fois avec les quais et les positions d’arrêt. De cette manière on renseignerait tout de même le stop_area précédant, pourtant optionnel, ce qui rajoute d’autant plus de complexité lors de la création des itinéraires mais aussi de leur maintenance par la suite.

type=public_transport public_transport=route

• Enfin, toutes les relations route (spécifiques à chaque variation du trajet) sont entrées dans une relation route_master générale où les même informations que précédemment sont requises à savoir le type de véhicule, la référence de la ligne, le nom de ligne (différent de celui utilisé pour les routes), de l’opérateur, du réseau et de la couleur.

type=public_transport public_transport=route_master

Un point mis en avant de ce modèle et qu’il pourrait coexister avec l’ancien modèle. C’est selon moi une erreur, quand bien même on considérerait l’argument de compatibilité puisque rendant inutile un modèle commun pour préférer un environnement mixte où il faut prendre en compte deux méthodes plutôt qu’une qui a pourtant été validée au cours d’un vote. En conséquence, il est usuel de recommander l’utilisation d’un modèle hybride composé à la fois des particularités du PTv2 et PTv1 rajoutant encore en complexité à l’ensemble.

Modèle “PTv1”

Ce premier modèle résulte d’une proposition visant à unifier les méthodes de cartographie des réseaux de transport en commun sur la base du standard Transmodel utilisé à l’échelle européenne. C’est un aspect non négligeable dans l’optique du projet OpenStreetMap à savoir de rendre libres des données, puisque le format est déjà utilisé par de nombreux opérateurs. Transmodel définit des points importants à savoir le type de véhicule et le stop place. Ce dernier se définit simplement par le lieu où un passager pourra monter ou descendre d’un véhicule aux horaires prévus et n’implique aucun aménagement physique spécifique. De cette façon, l’idée colle à l’usage de la relation stop_area bien que pouvant aisément être simplifié à l’usage du stop_positon où le véhicule est à l’arrêt.
Bien que simpliste, ce modèle est un premier pas dans la cartographie des réseaux sous la forme de trois éléments simples et accessibles à la plupart. Il ne nécessite en effet que :

• Le point d’arrêt du véhicule sur la voie

highway=bus_stop

• Un quai d’embarquement

highway=platform

• Une relation les unissant en zone d’arrêt

site=stop_area

On comprend de ce fait comment les deux versions décrites peuvent coexister, bien qu’il y ait une redondance d’attributs différents que ce soit pour le quai ou le point de halte.

Modèle Oxomoa

Ce modèle très proche du PTv2 est aujourd’hui obsolète. Il propose d’étendre le PTv1 notamment autour des véhicules se déplaçant le long de lignes tels que des tramways. En parallèle de quoi la structure des arrêts est revue de manière à intégrer la possibilité qu’un arrêt soit utilisé par plusieurs réseau à l’aide de la relation stop_area_group. Cela ouvre la possibilité de cartographier des échangeurs tels que les pôles à Besançon par exemple en créant une relation unissant les arrêts bus et tram d’un même lieu.

Modèle Affiné

Proposition datant de 2018 pour unir PTv1 et PTv2, certains parlent de PTv3 bien qu’il est à éviter de le préciser dans l’idée que ce soit un consensus et pas une couche supplémentaire. Le PTv2 complète le PTv1 mais met en évidence les limites de la méthode en introduisant des situations à l’utilité discutable tels que la multiplicité des attributs et objets transformant la cartographie des réseaux en une tâche fastidieuse et complexe. Ainsi, l’amélioration majeure serait la création d’un objet centralisant les attributs d’un arrêt. Toutes les informations seraient données à l’aide d’un nœud unique représentant l’idée d’un arrêt, celui-ci n’ayant pas toujours de marqueur physique.

highway=bus_stop

Bien que cela soit contraire au principe de vérifiabilité, cette pratique me semble acceptable et même bienvenue : la multiplicité des éléments d’un arrêt est résolue, il sera toujours possible de placer le nœud sur un marqueur physique et OSM serait rendu accessible aux lieux en développement où on observe une nette différence avec les pays développés, que ce soit au travers de l’infrastructure ou l’accès aux technologies. Ce faisant, la relation stop_area gagnerait en utilité puisque liant l’infrastructure physique à l’usage.
Pour une raison que j’ignore, cette proposition semble avoir été mise de côté et n’a toujours pas été soumise à un vote.

Conclusion

La question des transports en commun est primordiale dans le développement d’OSM. Une telle collaboration permettrait de toucher un large public ce qui ne peut être que bénéfique, mais l’évolution a rendu la méthode actuelle relativement complexe et inaccessible à la fois pour les contributeurs mais également les consommateurs. Ces derniers disposent déjà d’un format structuré de données qu’il n’est pas possible d’importer entièrement sous OSM, on peut néanmoins en capter l’essentiel à savoir les lieux d’arrêts et les horaires.
Le modèle affiné propose de rendre optionnel les tronçons empruntés au sein d’une relation route. Je trouve cela surprenant étant donné l’importance de cette information dans le cadre notamment d’évènements affectant la voirie où il est indispensable de pouvoir dévier la circulation pour maintenir au mieux le service.
Au delà de la simplification de la structure, je souhaite encore une fois appuyer l’importance des termes utilisés. Un quai (ou platform) est une structure physique de la même manière qu’un bâtiment, les attributs doivent être au plus proches de leur sens de manière à rester accessible aux nouveaux contributeurs. Pour cette raison, l’association de bus_stop sous highway me parait inapproprié et ma préférence irait pour public_transport sans que cela ne pose de problèmes de compatibilité avec PTv2.
Plus accessoire, l’attribut name est défini depuis le PTv2 par :

< vehicle type > < reference number >: < initial stop > => < terminal stop >

Cette pratique me déplaît d’une part par la redondance en utilisant des informations déjà renseignées sous la forme :

type, ref, from et to

De plus, elle limite la possibilité d’utiliser le nom officiel de l’itinéraire utilisé par la compagnie de transport. En résumé peut importe la raison, il existe une grande diversité de méthodes actuellement à l’usage ce qui doit être résolu et je suis impatient de pouvoir voter sur le PTv3 et peut être voir de nouveaux contributeurs locaux de manière à ne plus me sentir aussi seul à travailler sur le réseau.

In the last board meeting the OSMF board has revealed specifics of their plans for paying people for software development work. These plans have apparently been in the making for some time - but so far the board had in public been very quiet about the details - it was first publicly mentioned in the June board meeting but just vaguely and without any specifics. That was the same meeting in which the microgrants selection has been approved.

The details were now made available just minutes before the meeting started (deja vue) - the plans amount to about half the volume of the microgrants program - but there are apparently further plans to also get financially involved in iD development - this has been hinted at in the meeting but details of this have not been revealed.

I want to share a few thoughts on the plans that came to light now - both on the procedural/policy side of them based on the perspective of for many years having critically followed OSMF work and also on the practical side and the likely implications this has on volunteer work and volunteer projects in the OpenStreetMap world based on more than five years of volunteer work on one of OpenStreetMap’s core projects - the OSM-Carto map style - and on more than 10 years experience as an entrepeneur in the cartography and geodata world.

On the procedural aspects

My critical view of the OSMF board moving more and more to making and deliberating decisions outside public scrutiny is well known and obviously applies here as well. But even if i accept this as a given and as how the OSMF works these days no matter how sharply this contrasts with OSM community values there is still significant peculiarity in the whole thing. This centers on how the three projects the board has selected now were chosen. There is no substantial communication about this but from context and from what has been communicated i see mainly the following options:

• the projects were chosen from the microgrants applications and were invited to submit a new proposal privately to the board based on that. That seems logical for the osm2pgsql and Potlatch projects for which there were microgrant submissions that got not accepted by the commitee. This however cannot explain the inclusion of the Nominatim project (which is financially the biggest of the three). If this is the case that bears the questions (a) if the board was dissatistied with the selection of the committee - to a committee member this would be a logical conclusion and (b) that willingness to apply to the microgrants program was apparently either a prerequisite or at least a strong plus for being chosen to receive this kind of project support from the OSMF board later. Given the specific constraints of the microgrants program that made it certainly unattractive for quite a lot of people in principle in need for financial support for OSM projects that would be an odd choice. In any case this would have huge implication on any future microgrants programs in the OSMF.

• the projects were invited based on the board members’ personal selection which projects they consider deserving and/or in need for support like this and/or essential for OSM. That would certainly be the board’s prerogative - it is the OSMF’s money and they are the board of the OSMF. But still it would be remarkable that the considerations of the board based on which this choice was made are completely outside broader scrutiny.

• in a similar fashion - and the comments in the June board meeting point in that direction - the selection of these projects might have been meant as a personal stipend/grant to people considered valuable/deserving by the board rather than financing of projects independent of the people involved. This possibility comes with the same issue as the previous one - while the board certainly has the right to do this the lack of public documentation of the criteria and the considerations of selection would be remarkable.

• these projects were not actively chosen by the OSMF board but had actually proactively asked for money and were granted this request. Even if that did not involve a selection by the board that would still bear the question what criteria were used to approve these requests (or if you look at it from a different side: would the board just give money to anyone asking for it?).

That leads me to one other central procedural question: Were there any other projects considered or invited to submit proposals and not chosen?

To be clear - these critical considerations do not mean i find the outcome of the process - however it took place - necessarily questionable. I know Sarah and Jochen and think they are doing good work and although i never used Potlatch i have met Richard and find his views and perspectives on things very valuable. My critical questions are on the procedure and if at all i am concerned that questionable procedure and the possibility of inproprieties involved in that might stain Sarah’s, Jochen’s and Richard’s good work. And i think a well defensible outcome does not justify a questionable procedure to get there. In the same way it does not matter how the board might retroactively justify their decision now that it has been made public - what would have been important to know is how the selection and decision process actually took place (another deja vue).

On the practical effects of financing select projects in the OSM community

What the board has publicly communicated in the meetings is that - independent on the procedural questions discussed above - the justification for supporting these three project is their significance for OpenStreetMap. I think this could have pretty far reaching consequences for volunteer work and the social dynamics around it in the OSM community in the future and this is what i want to discuss in the second part of this post. I try to keep this compact and not go deeply into the overall dynamics of the interaction between paid and unpaid, economically and not economically motivated work in the OSM community. So the following will necessarily be somewhat sketchy.

As i already hinted above when mentioning my own volunteer background in OSM-Carto there are a lot of volunteers involved in projects in the OSM community that were not selected (and probably not even considered) by the OSMF board for receiving financial support and they will all take note of that. For OSM-Carto i can say while i would not have applied for receiving money from the OSMF for OSM-Carto development even when invited to do so there might have been others who might have. The same applies probably for a lot of other projects - think of JOSM or many smaller under-the hood software projects that are not very prominent in public awareness but that none the less play key roles and are often severely underdeveloped.

In projects like OSM-Carto or JOSM of course the problem for the OSMF in financing specific design or development work would have been that they could not be sure that it would actually be accepted by the project maintainers. That is not a problem for the projects that are now supported by the OSMF where decisions are made by the same people who receive the support. Naturally for a centralized organization like the OSMF projects with more centralized control and decision making are more compatible. But that just as a side note.

What will be visible to any voluteers in projects in the OSM community - and to be clear: I am not only talking about software development here - is that the OSMF board now expresses how they value certain activities for the OpenStreetMap project by giving money to them. Many volunteers in the OSM community of course could not care less if their work is valued by the OSMF board but still it is a statement and the OSMF is sitting on quite a lot of money to make this statement with a lot of emphasis - both in where they give money to and where they don’t. Where i think we can already see this clearly foreshadowing is volunteer work directly in the OSMF - the working groups are desperately looking for people to contribute but people naturally will think if they don’t volunteer someone might be able to earn some money for doing the same work. And if not - well, then that work probably was not that valuable after all. No one wants to volunteer for something that is ultimately considered superfluous. That is the situation for hobby contributors - of course for corporate employees that is a bit different since they are not practically eligible for receiving financial support from the OSMF anyway. At the same time volunteering and the potential influence this might result in could be encouraged by their employer. And of course some professional contributors might consider working for the OSMF as a possible alternative to their current job and start viewing their volunteer work as something like an unpaid internship and a possible lead-up to paid employment. All of this massively changes the social dynamics between volunteers in the projects.

Self employed people like me are somewhere in the middle here. I tend to separate my volunteer work on OSM from my professional work quite strictly. And hence as i said i would not be very interested in receiving money from the OSMF for my OSM-Carto work. Like many hobby contributors in OSM i value that in contrast to my day job in my OSM-Carto work i don’t have to make decisions based on economic needs and the wishes of my employer/client. And even if i was willing to make an exception i would not give a discount to the OSMF like Jochen and Sarah do. Because that would mean communicating to my other customers that they are coming up for the balance. Not that the current OSMF board would be willing to give me any money at all even if their life depended on it. ;-)

But if i’d look at it from the entrepreneurial perspective the logical reaction to the board’s decision to start financing projects they deem significant for OSM would be to see the OSMF as a potential customer - which means not providing work for free unless it promises a clear chance for a timely return of investment. And i am not a software developer and the board’s choice to support three software development projects indicates clear priorities here. And of course that would also mean i’d focus my energy on work where i can make myself indispensable and to put emphasis on controlling key parts of projects. Getting down to the nitty-gritty details and working on those in a cooperative fashion, discussing decisions to achieve consensus - all the stuff that traditionally earns you respect and influence in volunteer projects - are of little benefit if your goal is to as an entrepreneur get the OSMF to pay you for OSM related work.

A large number of people will start viewing the OSMF more as a commercial actor with commercial interests now and less as an organization representing the interests of OSM as a social project and acting primarily out of social responsibility. This has the potential to massively change the social mechanisms of volunteerism in the OSM community. Since we don’t know any details about the considerations behind the decision it is hard to tell how much the board is aware of that and how much conscious strategy is behind this.

Página Loja Wikipedia

As part of phase two of the GSoC project, following work has been done.

Server is Online

At the end of phase one, we had a server up and running with nominatim-ui and elasticsearch server. This is from the machine provided to me as part of this project. It currently has the entire planet DB set up. Suggesstions were setup for few smaller DBs, but not for the planet DB as of now. There is constant debugging and changes going on, so the suggestions might not be available at all times. I will post another dairy update once the suggestions are completely available.

The server is hosted at http://95.217.117.45/nominatim/ui. This will be available only during the course of this GSoC project (till 31 August 2020). The suggestions are provided from a hug API call. This can be accessed at http://95.217.117.45:8000/pref?q=. This internally queries elasticsearch on the server and returns the results.

Elasticsearch configurations

Elasticsearch provides a lot of configurations, which can be tweaked to obtain optimal performance. For our setup, the requirements include: * Require less space. * Fast indexing

The following are few of the options in elasticsearch that were explored during this phase.

• For Indexing speed
• Setting refresh inteval
• setting number_of_replicas to 0
• Use auto-generated ids

These will be tested out with the planed DB indexing, which will be done soon!

Address formation

The address is being formed in all the languages entered in the Nominatim DB. You can look at all the languages by looking at the tags at http://95.217.117.45:8000/pref. For example: http://gsoc2020.nominatim.org:8000/pref/?q=bangalore%20north has the result: "addr": "Bangalore North, Bangalore Urban, Karnataka", "addr:kn": "ಬೆಂಗಳೂರು ಉತ್ತರ, ಬೆಂಗಳೂರು ನಗರ, ಕರ್ನಾಟಕ", "country_code": "in"

Indexing rate:

The first set of indexing tests had only a single language address formation. For that, the indexing was around 4500 docs per second. With the increase in the languages, this is expected to come down.

The major bottleneck in indexing is the address formation. The elasticsearch bulk indexing has rate of more than 25000 docs per second.

Language support

The final suggestions will be placed in such a way that the suggestions will be available in all supported languages. The current setup fetches all languages, but displays only the default field. So you can expect the rest of the languages to appear soon.

Next steps

The next steps include:

• For elasticsearch
  1. Add typo tolerance for suggestions.
  2. Tokenization of words to allow different order of words.
  3. Try storage optimization tehniques.
• For the project code
  1. Finish the code.
  2. Documentation.
  3. Add this API for OpenStreetMap.

Quelques commentaires sur l’application Android StreetComplete

K08071986r

Today I learned that there’s a diary function in OSM. Huh. I would hardly refer to my region as “undermapped”, given that streets and addresses are all where they should be, but the wiki says that diary entries help in such regions, and my changes seem to be the most common ‘round these parts.

Since I’m new to this, I’ll explain my rationale for some changes so that the poor innocents that come after me have a reason behind the madness.

Several of the places I’ve been making changes to are just random additions to existing things, such as adding pavement types to roads and footpaths, adding the number of levels and roof types to buildings, and other small stuff like that. That all started months ago when I first learned about the Street Complete app. I liked adding detail to my neighborhood, but I wondered why my options for making changes were so limited.

Months pass, and one of the achievements in Street Complete pointed me towards a browser-based editor that I could use to make changes when I wasn’t walking around. One glance at my changesets as of a few weeks ago shows how well I took to the new editing tools.

Lacking any sort of guidance other than the brief tutorial, I started by adding “house” areas to houses in the area, but didn’t remove the existing address pins for fear of stepping on toes. Aerial images, my frequent walks, and plenty of COVID-19-induced alone time have led me to making more changes in the city, however.

Side note: read the documentation. It’s good for the soul.

More editing has taught me more about how the different parts of the map work together, and seeing those edits being uploaded to the other projects that take advantage of the OSM database is a very nice feeling.

I’ve recently added a new feature to https://map.atownsend.org.uk , prompted by the dreaded lurgi that is affecting everyone at the moment - the ability to show pubs with either outdoor seating or a beer garden.

Outside seating is shown like this:

with a black line at the bottom right of the icon.

Here’s a beer garden:

with a green underline instead of black

For the rest of the map legend see here.