Revue des autres blogs (non sélectionnés)

weeklyOSM 580 - dim 5 sep 2021 - 12:17


prettymaps [1] © Marcelo Prates | map data © OpenStreetMap contributors

  • The speed limit on most Parisian streets has been lowered to 30 km/h (18 mph). Christian Quest tweeted that this has resulted in a major update to OSM that should propagate through to route planners over the next few days.
  • Kontur tweeted a reminder that in the wake of Hurricane Henri, mappers could help by mapping densely populated yet poorly mapped areas (e.g., parts of Connecticut). See the Disaster Ninja app for more details.
  • Jan (user: Lübeck) suggested > adding three additional damage:*=* tags to areas destroyed in the heavy rainfall-induced flooding on 14 July in western Germany.
  • User messpert pondered the most appropriate tagging for historical surface mining sites.
  • A request for comments has been made for currency:crypto:*=yes,no, a proposal to extend the currency key to support cryptocurrencies.
  • The proposal man_made=video_wall, for mapping large digital screens, was approved with 9 votes for, 1 vote against and 2 abstentions.
  • User PlayzinhoAgro wrote about the lack of popularity of OpenStreetMap compared to other market solutions, based on a small survey > of the Brazilian market.
  • Vladislav Kugelevich has added information to the OSM wiki about Latvia’s datasources that are potentially suitable for import into. He plans to import some of this data but is still studying the software and the import guidelines.
OpenStreetMap Foundation
  • The LCCWG moderation subcommittee held two online public meetings on 2 and 3 September about revisions to the current Etiquette Guidelines, which are now open for public comment until Wednesday 8 September.
  • This year’s annual general meeting of the OSMF will take place online on Saturday 11 December 2021 at 16:00 UTC. Voting for the board election will start one week before the annual general meeting and this year there will be at least four positions available. To be eligible to vote you must have been a member or associate member for 90 days prior to the date on which the meeting is held, that is, paid up by Saturday 11 September.
  • The OWG is planning to host vector tiles generated by Tilemaker as an experiment. The goal is to get something others can work with to see where more work needs to be done.
  • User Lübeck was seeking IBIS-Budget Hotels for a trip. They asked > for assistance in writing an Overpass query to find all the variations in naming the hotels have in OSM.
OSM research
  • Afraid of the number 13? DeBigCs looked at the shortfall of houses numbered 13 in Dublin. Andrew Davidson followed up with an analysis that showed a much greater fear of 13 in the USA.
  • It looks like frzbrmnd2 has written to all/many mappers who have mapped in Iran. He is using the data for his dissertation where he is investigating the relationship between participants’ local knowledge and the quality of data collected.
Humanitarian OSM
  • On 27 August, the Open Mapping Hub in Eastern and Southern Africa was launched. The Hub is dedicated to increasing the use of OpenStreetMap tools to power and influence local and regional interventions. Find more information by following them on Twitter or Facebook.
  • [1] Marcelo Prates has created software used to draw pretty maps from OpenStreetMap data. The software, Pretty Maps, is based on the OSMnx, Matplotlib and Shapely libraries.
  • Pierre Béland published a Compare Map Before / After for the Nippes (Haiti) August earthquake, where post-disaster drone footage (2 cm) for five localities can be compared with the CNIGS Haitian Geospatial Agency orthophotos from 2014–2015 (20 cm). Other drone-collected images should be added as they become available. CNIGS official road network, OSM, altitude and relief layers are also available.
Did you know …
  • … the three most important tags for describing tracks? tracktype is used for a rough classification, surface to specify the material, and smoothness to specify the condition.
  • Cartography Playground? A simple and interactive website for explaining cartographic algorithms, problems and other matters. It is aimed at students of cartography who want to refresh and deepen their knowledge.
  • … that the animal rights organisation, PETA, tried to have the name of Fishkill, a town in New York State, changed to Fishsave? -kill or -kil is a common place name element in the area deriving from a Dutch word meaning creek or stream.
OSM in the media
  • Cezch Mappers have finished the mapping of post boxes in the Czech Republic. Miroslav Suchý gave an interview to > about it and OpenStreetMap.
  • Nat Foot reads out weeklyOSM 578.
Other “geo” things
  • Got some spare reading time? Allan Mustard recommends The Address Book by Deirdre Mask. The book looks at the complex and sometimes hidden stories behind street names and their power to name, to hide, to decide who counts, who doesn’t – and why.
  • Ian Dickson talked with Ben Hinze about ‘Ambient Maps’, a company mapping noise and air pollution in Australian and New Zealand major cities and regions. By combining a number of inputs and models they can produce predictions of air traffic noise, road traffic noise, rail noise, air quality and future road noise impacts.
  • Alan McConchie tweeted a link to Kenneth Field’s new book Thematic Mapping: 101 Inspiring Ways to Visualise Empirical Data. Using 101 maps, graphs, charts, and plots of the 2016 United States presidential election data, the book explores the rich diversity of thematic mapping and the visual representation of data.
  • As a test, Anthony Stephens likes to ask ‘anybody under 30 years old who lives in the city’ to name the suburb directly to the north of where they live. Anthony is the owner of ‘The Map Shop’ in Adelaide (Australia) and in an ABC article he discusses the future of paper maps in a world of satnav.
Upcoming Events Where What Online When Country Fortaleza Encontro de usuários OSM do Ceará, Brasil. 2021-09-04 Bogotá Distrito Capital Resolvamos notas de Colombia creadas en OpenStreetMap 2021-09-04 京田辺市 京都!街歩き!マッピングパーティ:第26回 一休寺 2021-09-04 jp OSM Africa Monthly Mapathon: Map Malawi 2021-09-04 – 2021-10-04 Greater London Missing Maps London Mapathon 2021-09-07 DRK Missing Maps Mapathon – JOSM Einführung 2021-09-07 Landau an der Isar Virtuelles Niederbayern-Treffen ✓ 2021-09-07 Stuttgart Stuttgarter Stammtisch (Online) 2021-09-07 OpenStreetMap Michigan Meetup 2021-09-09 Decatur County OSM US Mappy Hour 2021-09-09 Berlin 159. Berlin-Brandenburg OpenStreetMap Stammtisch 2021-09-09 Nordrhein-Westfalen OSM-Treffen Bochum (September) 2021-09-09 München Münchner OSM-Treffen 2021-09-09 Bezirk St. Johann im Pongau 2. Virtueller OpenStreetMap Stammtisch Österreich 2021-09-09 Bogotá Distrito Capital Agreguemos y editemos rutas de transporte en OpenStreetMap 2021-09-11 Arlon Réunion des contributeurs OpenStreetMap, Arlon 2021-09-13 臺北市 OpenStreetMap x Wikidata 月聚會 #32 2021-09-13 Hamburg Hamburger Mappertreffen ✓ 2021-09-14 Karlsruhe Karlsruhe Hack Weekend 2021-09-17 – 2021-09-19 Nantes Journées européennes du patrimoine 2021, Nantes 2021-09-18 Bonn 143. Treffen des OSM-Stammtisches Bonn 2021-09-21 Berlin OSM-Verkehrswende #27 (Online) 2021-09-21 Lüneburg Lüneburger Mappertreffen (online) 2021-09-21 DRK Missing Maps Online Mapathon 2021-09-23 [Online] OpenStreetMap Foundation board of Directors – public meeting 2021-09-24 Düsseldorf Düsseldorfer OSM-Treffen (online) 2021-09-24 Amsterdam OSM Nederland maandelijkse bijeenkomst (online) ✓ 2021-09-25

If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by Lejun, Nordpfeil, SK53, Sammyhawkrad, TheSwavu, YoViajo, derFred.

Uma nova forma de usar o OSM - dim 5 sep 2021 - 1:24

Como já falando no texto anterior o OpenStreetMap não é tão amigável com o usuário comum mas serve muito bem para os cartógrafos, também recebi muitos comentários que o OSM não é um produto final e sim uma base de conhecimento compartilhada e até algumas comparações com linux… Mas usar o OSM não deveria ser difícil ou depender do rebrand de grandes empresas, acredito que tem como atingir o usuário comum e ganhar mercado e sendo opensource e ainda trazer mais mapeadores para a comunidade.

A alguns venho trabalhando no que seria um cliente ideal em que eu realmente usasse e recomendaria para meus amigos e colegas isso venho crescendo desde que eu li o artigo The Mobile Map App Part I: The Void então descidir criar um rascunho:

Só que para tirar essa ideia do papel eu preciso de sua ajuda, caso você tenha alguma experiencia em Flutter ou React e queria levar o OpenStreetMap a um novo patamar por favor entre em contato:

A New Way to Use OSM - dim 5 sep 2021 - 1:23

As already mentioned in the previous text OpenStreetMap is not so friendly to the common user but serves very well for cartographers, I also received many comments that OSM is not a final product but a shared knowledge base and even some comparisons with linux… But using OSM should not be difficult or depend on the rebrand from big companies, I believe that it has a way to reach the common user and win market and being opensource and still bring more mappers to the community.

For some time now I have been working on what would be an ideal client that I would really use and recommend to my friends and colleagues. This has been growing since I read the article The Mobile Map App Part I: The Void so I decided to create a draft:

But to get this idea off the paper I need your help, if you have some experience with Flutter or React and want to take OpenStreetMap to a new level please contact me:

Mapping out bus routes in Anchorage - ven 3 sep 2021 - 23:43

I’ve noticed that Anchorage has several bus routes, yet only one has actually been somewhat put on the map (route 102). I’ve looked into what setting up a bus route would look like and after setting up another one halfway (route 10), I’ve figured out what needs to be done in order to complete a large project like this.

First off, Openstreetmap is not very good with creating a bus line easily, as tagging needs to be in a specific order according to the Wiki page on bus routes (the issue is currently being looked at as of now), so I think the method of mapping bus routes will be most efficient when done this way:

  1. Each bus platform/stop must be mapped and placed into a relation before any route is mapped with ways. If the ways are set up first it can be quite a pain to move the bus stops to the top afterwards. I made this mistake when setting up bus route 10 and it was not fun.
  2. After that is done, the bus routes can finally be placed down. It doesn’t matter as much if every stop in Anchorage has been mapped so long as all the bus stops on that specific line is mapped out.

This is a pretty large project that’s going to take a bit of effort, so any outside help is greatly appreciated. Also, if you’re knowledgeable in creating bus routes and you see any errors in this method or my mapping, please feel free to correct me or the issue.

[OSMOpinion] OpenStreetMap must not be the petri dish of political-driven nonsense - ven 3 sep 2021 - 19:01
OpenStreetMap must not be the petri dish of political-driven nonsense

Yet here we are again, the Chinese Commies just spit on everything they thought was rightful. Yes yes, I explicitly use the term 'Commies' as gallantry since I came from 'the Taipei and environs' by their courtesies. BTW, 'Taiwan' or 'Formosa' is the place if you can't recall.

I was rather indolent to express any political views on the OpenStreetMap as it should be a site to record facts, not a place to be poisoned by political flim-flam. However, the landscape has changed too much from a niche and friendly environment to a colossal and somewhat hostile one.

OpenStreetMap is not and shalln't be the sacrifice in the political struggles

More and more Chinese mappers joined as China rises, but many rather acting irrationally and nonconstructive. These mappers can mainly be categorised into 4 major doctrines:

  1. OSM datasets exploiting: denying the existence of Xinjiang internment camps, the de facto status of Taiwan, Penghu, Kinmen and Matsu, nor the territorial dispute on the South China Sea and Pinnacle Islands;
  2. Invalid notes abusing: creating notes unrelated to data qualities and asserting Chiese political view;
  3. OSM wiki vandalising: improper editing on the page ‘Taiwan’ and clearing OSMTW community early discussions;
  4. Heavily mapping on unrealistic constructions in a forseeing future: e.g. Beijing-Taipei Expressway, China National Highway 319 (Kaohsiung-Chengdu)

Unfortunately, all of them were never cared to listen nor discuss, while the community members try to be friendly and sagacious. Which let me rethink the need to embrace or cope with such gibberish, rather.

Relentless attempts from these resentful Chinese users tried to assert their perspective on the maps and wikis, of which I think were bêtise and nescient, mostly had been reverted time by time with a huge amount of effort. The community now must confront the inconvenient truth for that we were amassed at the centre of a political tug-of-war, action needs to be taken to prevent collateral damage.


Changesets vandalising TW

Changesets claiming the disputed territories or waters as Chinese

Changesets covering up Xinjiang internment camps

Invalid notes asserting political views claims Taiwan is a part of China

Vandalising OSMwiki

Wonderful poppycock from zh-CN users (no offence but yes poppycock)


Mapear vs. Cartografiar - jeu 2 sep 2021 - 23:50

TL;DR: “Mapear” y “Cartografiar” significan lo mismo, pero la primera es más corta y comunica el concepto de “hacer mapas” de manera más sencilla y directa.

Como colaborador de traducciones “crowdsourced”, de vez en cuando me encuentro con algún traductor que reemplaza la palabra “mapear” por “cartografiar”. Esto lo hacen porque creen que “mapear” es un chilenismo o una “traducción de baja calidad” por parecerse a su versión en inglés. Pero, ¿Es realmente así?

En 2014, con la publicación de la 23.ª edición de Diccionario de la lengua española, se incorporó al término “Mapear” la acepción de “Hacer mapas”. Al tratarse de un aporte de la Academia Chilena de la Lengua, quedó etiquetado como si fuera un término dialectal, un chilenismo como “Pichintún” o “Cacharriento”.

No obstante eso, aunque supusiéramos que en 2014 solo se usaba en Chile, “es imposible que una lengua no esté en movimiento”, como dijo José Manuel Blecua, Director de la RAE en aquel momento.

Debido a mi participación en diversos proyectos internacionales de edición de mapas, puedo asegurar que el uso del verbo “mapear” se encuentra extendido a todos los países de habla hispana, incluida España.

“Mapear” ya no es un chilenismo (si es que en algún momento lo fue) ni una traducción de baja calidad, sino una palabra que comunica de manera sencilla el concepto asociado a la elaboración de un mapa y resulta más fácil de manejar que “Cartografiar”.

Por último, otro aspecto a considerar al traducir interfaces de usuario, es el largo de las palabras. En este caso, “Cartografiar” tiene el doble de letras que “Mapear”.

I'll take it as a "yes" then... - jeu 2 sep 2021 - 13:18

Thank you EOS :-)

P.S. The copyright symbol on said tool indeed made me uncomfortable using it straight away, hence I decided to bother EOS (LOL)

#Mes passions : Les réseaux. Rails, énergie, data et bas carbone - mer 1 sep 2021 - 15:00
J’arrive juste de chez Google. Ouf.

J’ai beaucoup “collaboré” dans Google Maps et au décidé cet été de me degoogliser au maximum. En effet, Google a bloqué mon compte agence ads évoquant des raisons floues.

Ils ont perdu ma confiance déjà bien égratignee. En tant que mini agence web, j’évite gafam et consorts pour accompagner mes clients et amis vers des endroits plus sûrs et plus sains.

Goog. M’a fait envoyer deux mois de relevés bancaires pour qu’ils lèvent enfin l’interdiction. Ce qu’ils ont faut après deux mois, sans même envoyer un mail.

Je sais que la privacy et la protection des individus en général est ma raison de vivre (carrément).

Il en découle ce qui permet aux gens de vivre : les réseaux de distribution : data, trains, et énergie particulièrement. Surtout si c’est vert. C’est agréable de trouver des gens ouverts qui pensent un peu comme moi. Cette communauté fait beaucoup de bien à tous.

Vive le libre, vive le web, vive la vie !


Parking_space micromapping JOSM method overview - mer 1 sep 2021 - 10:25
Tag’s use

While the amenity=parking tag is used “de facto”, the amenity=parking_space micromapping oriented tag has been introduced and approved by vote on 2011-05-01. The main reason for it’s introduction is to help people, disabled or not, easily find parking spots inside parking lots without any important downside to it.

Other voted proposals introduced the parking:lane=* and parking=street_side tags and while those are quite useful (I’m still reserved concerning the first), I’d rather map parking spaces directly as those kind of parking’s capacity is generally quite low. The parking:lane proposal even adds:

Consider using parking:lane=* as a simple alternative if the streetside parking spaces are stretched over a longer section of the road and no micromapping of these areas is desired.

Ha! Which fool wouldn’t want some micromapping in its life? Micromapping is love, micromapping is but the purpose of life.

The tag is especially useful in combination with the footway=acces_aisle tag (not to be confounded with service=parking_aisle which is oriented towards vehicular routing) which is used for pedestrian routing in parking lots.


This tutorial makes use of the JOSM editor along with the BuildingsTools and Gridify plugins and the high resolution of aerial imagery in France. Some similar functions may be found on other editors that I don’t know of, feel free to try and find your own workflow in the journey for the slickest parking lot micromapping.


The main difficulty about mapping parking spaces comes from its typology. Up to now I have found four different kinds of geometry and I’ll go through them from the simplest to the hardest to map in my opinion. The overall pattern of those is implicit and it’s recommended to use the parking:orientation key to specify if necessary.

Straight (Parallel or perpendicular)

The simplest of them. Just draw a four nodes’ polygon and split into equal spaces. If feeling finicky, you can align it with the nearby access way and/or the building. To do so, I use the BuildingTools plugin.

One of its function is to create a four nodes’ polygon aligned to another element when at least two nodes are selected. Just select two nodes from the way (the furthest the two are the better for precision) and use the plugin’s tool. Do not forget to remove the building=yes tag before upload and replace with the necessary tag(s).

To split the newly created parking spaces row, I use the Gridify plugin to replace the row with X identical spaces with the added tags, X being the number of spaces I counted from aerial imagery. Do check the count, simply a matter of checking if the spaces are aligned to the painted line on the ground, as it’s easy to lose track after a few hours adding hundreds of them. If necessary I then add specific tags to individual spaces such as parking_space=disabled to indicate a parking space to be used by disabled exclusively. Do note that this way of tagging isn’t part of any approved proposal and is simply “in use”.


This kind add one more step to the straight spaces method caused by the angle relative to the trafic flow. To do so the simplest way is to move two nodes from the row before splitting, or the entire line of nodes after splitting. After eyeballing the angle, I like to use the “line alignment” function from BuildingTools to maintain identical angles between parking row.

Select two nodes from the first angle and use the plugin tool to make similar angled shape to other rows. Place nodes at the intersections and delete both the constructed shape and unecessary nodes.


The method to map an herringbone style parking is similar to the diagonal method. One simply have to move the central nodes or the sides ones before splitting. Personnaly I do prefer the latter as I can make both sides symetrical. As before, I align the overall shape with the central line of the parking spaces and extend it to their depth. Then I create angled shapes after eyeballing one angle. One, pictured on the bottom, symetrical to the left side node, and a second one to have the central node on top. Using these two nodes I can then split each row.


This pattern is the most brainwrecking I encountered to date. While quite pretty, that is for a parking space, I just find it awful to map. The best method I have is to do it “manually” using the tools as alignment helpers. First create the overall shape of the spaces, angle it and split it.

Then manually add middle nodes to every column (JOSM have a function for equal distancing nodes the shortcut being Ctrl+B). Select every other node and move it to one side.

Select every “middle” nodes and move them to the other side as needed and congrats, you now have a kinda accurate seesaw pattern that you can use as a guide to outline every single parking space.

The seesaw pattern on the left side requires supplementary steps to generate. Just use the same method as aforementioned that is the buildingTools plugin to create regularly spaced intersections.


Here is an overview of my method for micromapping individual parking spaces. The method described may lack accuracy, if you know of any better way please do share it in the comments. While not necessarely useful nor groundbreaking, micromapping is possible using existing tools and should be considered not only for routing but as a supplementary way to support OpenStreeMap adoption by organisations.

Análisis de notas - mer 1 sep 2021 - 6:51

Este artículo hace parte de una serie de artículos que he escrito acerca de las notas. En el primero escribí sobre el contexto de las notas frente a la comunidad de OpenStreetMap, y en el segundo sobre cómo crear, ver, y cerrar las notas desde diferentes aplicaciones. Aquí están los artículos:

En este artículo explico cómo analizar las notas y si hay muchas activas en la zona de interés, poder diseñar una estrategia para cerrarlas.

Notas creadas y solucionadas por país

Comencemos con un servicio que ha creado Pascal Neis específicamente para notas. Antes de continuar es importante mencionar que Pascal ha creado una gran cantidad de herramientas para análisis de datos de OSM, lo cual facilita el trabajo o análisis de OSM desde diferentes aristas.

Con respecto a las notas, él nos ha puesto a disposición una página que permite ver las notas de cada país, discriminadas por las abiertas, las cerradas y las totales, donde además hace un cálculo de la tasa de resolución:

Esta página permite inducir cómo la comunidad de cada país está involucrada en el mapa, en la parte de resolución de notas. Además, puede dar una idea de cómo, de manera general, está la comunidad involucrada activamente en contribuir en el mapa. Se puede ver que los países con mayor cantidad de notas resueltas, y los de mejor tasa de abiertas/cerradas, son los países que tienen comunidades de colaboradores más involucradas y activas.

Volviendo al tema de la página, en el listado de países se puede hacer clic sobre cada una para ver los detalles. Ahí abrirá una página de las notas del país seleccionado y mostrará un gráfico en el tiempo de las notas abiertas, cerradas y totales desde el origen de esta funcionalidad (antes del 2013). Debajo, muestra la actividad de las últimas 500 notas, entre nuevas notas abiertas, o notas recientemente comentadas o cerradas, e inclusive las reabiertas. Igualmente, ofrece un feed para recibir notificaciones de nuevas notas abiertas, o notas cerradas. En general, esta página puede ser el mejor lugar donde se puede revisar el conjunto de notas abiertas completo y comenzar a decidir qué tipo de cosas modificar a partir de los datos de las notas.

Basándonos en esa página, para el caso de Colombia se veía que la cantidad de notas abiertas crecía y crecía, y tan solo unas cuantas eran cerradas, principalmente por iniciativas globales que identifican las notas inválidas, como el proceso del usuario Kartonage. Ya en el 2021 se ve el reflejo de la iniciativa de MaptimeBogota de cerrar las todas las notas de Bogotá, y en general de toda Colombia.

Notas de una zona específica

La forma clásica de identificar notas abiertas o cerradas recientemente es haciendo zoom desde un editor e ir buscando las “chinchetas” de notas abiertas (de esto se explicó en el artículo anterior, ya que se puede hacer desde el visor de OpenStreetMap, desde iD y desde JOSM).

Esta estrategia es muy útil si se quieren identificar las notas de una zona geográfica precisa. Por ejemplo, el grupo MaptimeBogota usó esta estrategia para ver las notas en un rectángulo conteniendo el área de Bogotá. Así fue como se identificó por medio de JOSM que se habían creado más de 2000 notas y (al momento de escribir este artículo) ya quedan menos de 50 abiertas.

En un artículo anterior se mostró cómo modificar la parametría de JOSM para que muestre todas las notas cerradas, no solo las recientes. Hay que tener en cuenta esto, ya que la mayoría de los visores y editores muestra solo las notas cerradas en la última semana. Este pequeño rango de días no permite ver el trabajo realizado sobre las notas, por lo que es bueno ampliarlo y poder ver notas cerradas mucho antes, para revisar si se cerraron sin haber traducido toda la información contenida, a datos dentro de OSM.

Antes de continuar con las otras formas de analizar notas, quiero indicar que es práctico visualizar todas las notas cerradas en un área que se está mapeando, ya que es posible que se hayan cerrado notas de forma incorrecta. Esto permite revivir cierta información que puede ser considerada como archivada.

Las notas en las que “he” trabajado

Como parte del perfil de OSM, uno puede ver las notas con las que he interactuado, ya sea porque las abrí, las comenté o las cerré. En mi caso particular se pueden ver en: Cada página tiene 10 notas, por lo que modificando la URL se puede saltar a un grupo de notas más antiguo. Si hacemos esto con mi perfil, se puede navegar en las más de 2000 notas en las que he participado. Esto es práctico si se quieren ver las notas de un usuario, y cómo ha interactuado con ellas.

También esto es práctico si queremos ver notas viejas en las que hemos comentado, pero aún no se han cerrado. Esto se usa para ver la discusión generada sobre una nota.

Notas de una zona específica por antigüedad

Esto se realiza por medio de JOSM, donde nos permite bajar las notas de una gran zona, y por medio de la vista de notas (en la parte derecha), ordenarlas por algún criterio como el id, el cual incrementa de acuerdo con el orden de creación.

Esto es práctico si queremos procesar todas las notas de un área, privilegiando las más viejas. O por el contrario, responder las más recientes para que los usuarios que las acabaron de crear sientan esa rápida respuesta de los contribuidores.


Es una página web enfocada en las notas, y nos permite jugar con ellas filtrándolas por varios criterios. La página es:

La funcionalidad principal es verlas en un mapa, con un mecanismo de filtrado que ofrece muchas opciones:

  • Por palabra en la descripción.
  • Por usuario que la creó.
  • Por rango de fecha de creación.
  • Por estado (abierta, cerrada).
  • Por anonimato (incluir, excluir, o solo anónimas).

Dependiendo de los criterios de filtrado, los resultados los muestra con colores. Si hay varias notas en un mismo lugar, mostrará un círculo y dependiendo de la cantidad, el color del círculo será diferente. Ya cuando muestra la chincheta de una nota dada, el color de esta cambia dependiendo la “vejez” de la nota.

También hay una forma de ver las notas por medio de una lista bastante amigable.

Es una herramienta muy práctica para analizar las notas a lo largo de la historia, tendencias, comportamiento de usuarios, entre otras cosas.

Si crees que la página tiene algún error lo puedes reportar en GitHub o crear tu propio fork.

Notificación de notas por medio de feed

Si quieres monitorear las notas nuevas en un país, y que se te notifique de este hecho, puedes usar un feed sobre RSS para ver las notas recientes. Este servicio lo ofrece OSM al igual que la página de Pascal Neis, donde permite suscribirse al feed de un país determinado. La diferencia es que OSM es basado en un cuadro, mientras que la de Neis Pascal es del área de un país dado.

En mi caso, como es Colombia, yo uso la aplicación feedly con el RSS, y así voy viendo las notas nuevas. Esta es una forma excelente de estar pendiente de las nuevas notas y poder responder rápidamente.

Formas avanzadas

Para una estrategia de resolución de notas como lo que hicimos en Colombia, basta con usar una o varias de las herramientas previamente descritas. Sin embargo, las notas ofrecen muchas funcionalidades y aquí te explico otras formas avanzadas de usarlas.

Uso del API

Como todo lo de este mundo de OSM, las notas también ofrecen un API o interfaz de programación, para que puedan usarse desde otras aplicaciones. Finalmente, las herramientas previamente descritas implícitamente usan el API, y lo que hacen es ofrecernos un mecanismo específico para interactuar con ellas. Pero si ves que las opciones propuestas no son suficientes para manipular esa base de datos de notas, puedes crear tu propio mecanismo y usar el API de OSM.

Aquí está un ejemplo de una consulta por medio del API:

Para más detalles sobre el API puedes consultar la página del Wiki:

Todas las notas

La última forma que propongo para analizar las notas es bajando los extractos de la base de datos. Es un archivo de varios megabytes y contiene todas las notas del mundo. Realmente solo se recomienda bajar si se van a hacer análisis masivos de los datos, donde la API no es suficiente. La puedes descargar de:

Mapper of the Month: Constantine Tumwine (Tanzania) - mer 1 sep 2021 - 2:00

His homepage and his contribution page.

Hello Constantine. Would you like to briefly introduce yourself to our readers?

Yes, Well, I’m currently Volunteering at Tanzania Development Trust (TDT) on a crowdmapping project of rural Tanzania in OpenStreetMap and I am mapping rural Tanzania into OpenStreetMap via a remote mapping using satellite imagery. The reason I chose to go for this job is that I saw a call for volunteers on United Nations Volunteers (UNV) portal and I thought I would be able to help add schools, hospitals, roads, buildings and villages to OpenStreetMap so that communities can better navigate, plan their development and progress towards the Sustainable Development Goals (SDGs), and to help activists better protect girls from Female genital mutilation (FGM). One of my key accomplishments in my current role has been helping Tanzania Development Trust achieve their target within a short period of time. I have so far managed to map over 3 193 buildings and over 87 kilometres of roads in the short time I have been mapping.

How and when did you get to know OpenStreetMap?

I got to know OpenStreetMap though Tanzania Development Trust where I started volunteering in May 2021 using Crowd2Map Tanzania to map rural Tanzania into OpenStreetMap. The Tanzania Development Trust is a registered UK charity (charity number 270462) that has funded development projects within Tanzania since 1975. They empower the poorest communities in Tanzania on a village-level. They are all volunteers and pair local Tanzanian representatives with UK-based project officers to support rural development and transform lives through various projects. Tanzania Development Trust has been working with grassroots organizations in the poorest areas of Tanzania for 40 years. TDT was founded as a Charitable Trust by the Britain Tanzania Society (BTS). BTS remains their parent body and pays the small administrative costs of TDT. The people who run TDT and BTS are all volunteers who know the country well. No salaries are paid. Project requests come from Tanzania via their website, from visits, by word of mouth, through the BTS branch in Dar-es-Salaam or from NGOs in the United Kingdom. They have built a safe house for girls refusing FGM and supported over 100 projects including bore holes for villages without water, school resources and solar panels for dispensaries.

How do you use OpenStreetMap?

I have been using Crowd2Map Tanzania to map buildings, roads and points in rural Tanzania into OpenStreetMap to help community development in Tanzania. Crowd2Map Tanzania is an entirely volunteer crowdsourced mapping project putting rural Tanzania on the map. Since 2015, they have been adding schools, hospitals, roads, buildings and villages to OpenStreetMap with the help of volunteers worldwide and on the ground in Tanzania. They do this so that communities can better navigate, plan their development and progress towards the SDGs, and to help activists better protect girls from FGM.

What kind of contributor are you and in which area do you map?

I am a volunteering Casual Mapper working with Tanzania Development Trust, a nonprofit organisation operating in the United Republic of Tanzania and I map the same area. Crowd2Map Tanzania has been mapping rural Tanzania into OpenStreetMap since October 2015. They have trained over 16 000 remote mappers from all over the world to map from satellite images and over 3 000 field mappers to add their local knowledge to these base maps, mostly using the free smartphone app Maps. Having better maps is vital in the fight against FGM and to help community development and am proud to be part of this fight against FGM by mapping.

What are you mapping? Do you have a specialization?

I have been mapping both roads and buildings and I do not have a specialization yet.

What is your greatest achievement as mapper?

Mapping has allowed me to further develop my knowledge competencies and skills.

Why are you mapping? What motivates you?

Having better maps is vital in the fight against FGM and to help community development.

Do you have any ideas to expand the OpenStreetMap community, to motivate more people to contribute?

Yes, I have so for trained over 16 remote mappers from Uganda to map from satellite images and over 10 field mappers to add their local knowledge to these base maps in Tanzania and I will continue doing so.

Do you have contact with other mappers?

Yes, I have contacts with some mappers.

What is in your view the greatest strength of OpenStreetMap?

One of OpenStreetMap’s greatest strength is that it doesn’t just give you a beautiful draggable map. It gives you the data, so you can do what you like with it. With an Export tab joining View and Edit at the top of the screen. It gives you an instant way to get the map data in a format you want.

What are the largest challenges for OpenStreetMap?

In my own experience I think the challenge that I have faced with OpenStreetMap is that some imageries are not clear and this makes it difficult for one to make better maps.

How to do stay on top of news about OpenStreetMap?

Be known for reliability. The definition of reliable is to be consistently good in quality or performance and able to be trusted. You don’t need a detailed explanation as to how having your own name associated with this kind of statement will benefit your reputation and career

To conclude, is there anything else you want to share with the readers?

Respect your own time. Anyone who has ever lost valuable time finger-skipping around Facebook or responding to an overwhelming number of emails knows there is a big difference between being active and being effective. Productivity is the backbone of success and its kryptonite is burnout which, studies have shown, leads to far more than a just a bad day!

Thank you, Constantine, for this interview.

Contributeur du mois: Constantine Tumwine (Tanzanie) - mer 1 sep 2021 - 2:00

Sa homepage et sa page de contribution.

Bonjour Constantin. Voudrais-tu te présenter brièvement à nos lecteurs ?

Oui, je suis actuellement bénévole au Tanzania Development Trust (TDT) pour un projet de cartographie des zones rurales de Tanzanie dans OpenStreetMap. Je cartographie les zones rurales de Tanzanie dans OpenStreetMap par le biais d’une cartographie à distance utilisant des images satellites. La raison pour laquelle j’ai choisi ce travail est que j’ai vu un appel à volontaires sur le portail des Volontaires ONU et j’ai pensé que je pourrais aider à ajouter des écoles, des hôpitaux, des routes, des bâtiments et des villages à OpenStreetMap afin que les communautés puissent mieux naviguer, planifier leur développement et progresser vers les Objectifs de développement durable (ODD), et aider les activistes à mieux protéger les filles contre les mutilations génitales féminines (MGF). L’une de mes principales réalisations dans mon rôle actuel a été d’aider le Tanzania Development Trust à atteindre son objectif en peu de temps. J’ai réussi jusqu’à présent à cartographier plus de 3 193 bâtiments et plus de 87 kilomètres de routes dans le court laps de temps que j’ai consacré à la cartographie.

Comment et quand as-tu découvert OpenStreetMap ?

J’ai découvert OpenStreetMap par le biais de Tanzania Development Trust, où j’ai commencé à travailler bénévolement en mai 2021 en utilisant Crowd2Map Tanzania pour cartographier la Tanzanie rurale dans OpenStreetMap. Le Tanzania Development Trust est une organisation caritative britannique enregistrée (numéro de charité 270462) qui finance des projets de développement en Tanzanie depuis 1975. Il donne des moyens d’action aux communautés les plus pauvres de Tanzanie au niveau des villages. Ils sont tous bénévoles et associent des représentants locaux tanzaniens à des agents de projet basés au Royaume-Uni pour soutenir le développement rural et transformer des vies par le biais de divers projets. Depuis 40 ans, Tanzania Development Trust travaille avec des organisations de base dans les régions les plus pauvres de Tanzanie. TDT a été fondé en tant qu’organisme caritatif par la Britain Tanzania Society (BTS). BTS reste leur organisme de tutelle et paie les petits frais administratifs de TDT. Les personnes qui dirigent TDT et BTS sont toutes des bénévoles qui connaissent bien le pays. Aucun salaire n’est versé. Les demandes de projets proviennent de Tanzanie via leur site web, de visites, du bouche à oreille, de la branche de BTS à Dar-es-Salaam ou d’ONG au Royaume-Uni. L’association a construit une maison sécurisée pour les filles qui refusent les mutilations génitales féminines et a soutenu plus de 100 projets, notamment des forages pour les villages sans eau, des ressources scolaires et des panneaux solaires pour les dispensaires.

Comment utilises-tu OpenStreetMap ?

J’ai utilisé Crowd2Map Tanzania pour cartographier les bâtiments, les routes et les points dans les zones rurales de Tanzanie dans OpenStreetMap afin de contribuer au développement communautaire en Tanzanie. Crowd2Map Tanzania est un projet de cartographie crowdsourcée entièrement bénévole qui met la Tanzanie rurale sur la carte. Depuis 2015, ils ajoutent des écoles, des hôpitaux, des routes, des bâtiments et des villages à OpenStreetMap avec l’aide de volontaires du monde entier et sur le terrain en Tanzanie. Ils font cela pour que les communautés puissent mieux s’orienter, planifier leur développement et progresser vers les ODD, et pour aider les activistes à mieux protéger les filles des MGF.

Quel type de contributeur es-tu et dans quelle région cartographies-tu ?

Je suis un cartographe occasionnel bénévole travaillant pour Tanzania Development Trust, une organisation à but non lucratif opérant en République-Unie de Tanzanie, et je cartographie la même zone. Crowd2Map Tanzania cartographie la Tanzanie rurale dans OpenStreetMap depuis octobre 2015. Ils ont formé plus de 16 000 télé-cartographes du monde entier pour cartographier à partir d’images satellites et plus de 3 000 cartographes de terrain pour ajouter leurs connaissances locales à ces cartes de base, en utilisant principalement l’application gratuite pour smartphone Maps. Il est essentiel de disposer de meilleures cartes pour lutter contre les mutilations génitales féminines et favoriser le développement des communautés. Je suis fier de participer à cette lutte contre les mutilations génitales féminines en cartographiant.

Que cartographies-tu ? As-tu une spécialisation ?

J’ai cartographié des routes et des bâtiments et je n’ai pas encore de spécialisation.

Quelle est ta plus grande prouesse en tant que contributeur ?

La cartographie m’a permis de développer davantage mes connaissances, mes compétences et mes aptitudes.

Pourquoi cartographies-tu ? Qu’est-ce qui te motive ?

Il est essentiel de disposer de meilleures cartes pour lutter contre les mutilations génitales féminines et contribuer au développement des communautés. Je suis fier de participer à cette lutte contre les mutilations génitales féminines en cartographiant la Tanzanie en particulier.

As-tu des idées pour élargir la communauté OpenStreetMap, pour motiver plus de gens à contribuer ?

Oui, j’ai jusqu’à présent formé plus de 16 contributeurs à distance en Ouganda pour cartographier à partir d’images satellites et plus de 10 contributeurs de terrain pour ajouter leurs connaissances locales à ces cartes de base en Tanzanie et je vais continuer à le faire.

As-tu des contacts avec d’autres contributeurs ?

Oui, j’ai des contacts avec certains cartographes.

Quelle est, selon toi, la plus grande force d’OpenStreetMap ?

L’une des plus grandes forces d’OpenStreetMap est que le projet ne se contente pas de vous donner une belle carte à faire glisser. Il vous donne les données, afin que vous puissiez en faire ce que vous voulez. Avec un onglet Export proche des onglets Affichage et Edition en haut de l’écran, il vous offre un moyen instantané d’obtenir les données cartographiques dans le format que vous souhaitez.

Quel est le plus grand défi pour OpenStreetMap ?

Dans ma propre expérience, je pense que le défi auquel j’ai été confronté avec OpenStreetMap est que certaines images satellitaires ne sont pas claires et cela rend difficile la réalisation de meilleures cartes.

Comment restes-tu à jour par rapport à l’actualité d’OpenStreetMap ?

Soyez connu pour votre fiabilité. La définition de la fiabilité est la suivante : être constamment bon en qualité ou en performance et être digne de confiance. Il n’est pas nécessaire de vous expliquer en détail comment le fait d’associer votre nom à ce type de déclaration sera bénéfique pour votre réputation et votre carrière.

Pour conclure, y a-t-il encore quelque chose que tu voudrais dire au lecteur ?

Respectez votre temps. Quiconque a déjà perdu un temps précieux à zapper sur Facebook ou à répondre à un nombre écrasant d’e-mails sait qu’il y a une grande différence entre être actif et être efficace. La productivité est l’épine dorsale du succès et sa kryptonite est l’épuisement professionnel qui, selon les études, mène à bien plus qu’une simple mauvaise journée !

Merci, Constantine, pour cette interview.

Traduit de l’anglais par Pierre Parmentier avec l’aide de

Mapper van de maand: Constantine Tumwine (Tanzania) - mer 1 sep 2021 - 2:00

Zijn homepage en zijn bijdrager pagina.

Hallo Constantine. Wil je jezelf even even voorstellen aan onze lezers?

Ja, nou, ik ben momenteel vrijwilliger bij Tanzania Development Trust (TDT) op een crowdmapping project van het platteland van Tanzania in OpenStreetMap. Ik breng het platteland van Tanzania in kaart in OpenStreetMap via een remote mapping met behulp van satellietbeelden. De reden dat ik deze baan gekozen heb, is dat ik een oproep voor vrijwilligers zag op het portaal van United Nations Volunteers (UNV). Ik heb eraan gedacht dat ik zou kunnen helpen om scholen, ziekenhuizen, wegen, gebouwen en dorpen toe te voegen aan OpenStreetMap, zodat gemeenschappen beter kunnen oriënteren, hun ontwikkeling kunnen plannen en vooruitgang kunnen boeken in de richting van de Sustainable Development Goals (SDG’s), en om activisten te helpen meisjes beter te beschermen tegen vrouwelijke genitale verminking (VGV). Een van mijn belangrijkste verwezenlijkingen in mijn huidige functie is dat ik Tanzania Development Trust heb geholpen om hun doelstelling binnen korte tijd te halen. Ik ben er tot nu toe in geslaagd om meer dan 3 193 gebouwen en meer dan 87 kilometer wegen in kaart te brengen in een korte tijd.

Hoe en wanneer heb je OpenStreetMap ontdekt?

Ik heb OpenStreetMap leren kennen via de Tanzania Development Trust, waar ik in mei 2021 ben begonnen als vrijwilliger met behulp van Crowd2Map Tanzania om het platteland van Tanzania in kaart te brengen in OpenStreetMap. De Tanzania Development Trust is een geregistreerde Britse liefdadigheidsinstelling (liefdadigheidsnummer 270462) die sinds 1975 ontwikkelingsprojecten in Tanzania financiert. Zij versterken de armste gemeenschappen in Tanzania op dorpsniveau. Ze zijn allemaal vrijwilligers en koppelen lokale Tanzaniaanse vertegenwoordigers aan in het Verenigd Koninkrijk gevestigde projectmedewerkers om plattelandsontwikkeling te ondersteunen en levens te veranderen door middel van verschillende projecten. Tanzania Development Trust werkt al 40 jaar samen met basisorganisaties in de armste gebieden van Tanzania. TDT werd als Charitable Trust opgericht door de Britain Tanzania Society (BTS). BTS blijft het moederorgaan en betaalt de kleine administratieve kosten van TDT. De mensen die TDT en BTS leiden zijn allemaal vrijwilligers die het land goed kennen. Er worden geen salarissen betaald. Projectaanvragen komen uit Tanzania via hun website, van bezoeken, via mond-tot-mondreclame, via het BTS filiaal in Dar-es-Salaam of van NGO’s in de Verenigd Koninkrijk. Ze hebben een veilig huis gebouwd voor meisjes die VGV weigeren en meer dan 100 projecten gesteund waaronder boorgaten voor dorpen zonder water, schoolmateriaal en zonnepanelen voor dispensaria.

Hoe gebruik je OpenStreetMap?

Ik heb Crowd2Map Tanzania gebruikt om gebouwen, wegen en punten op het platteland van Tanzania in kaart te brengen in OpenStreetMap om de ontwikkeling van de gemeenschap in Tanzania te helpen. Crowd2Map Tanzania is een volledig door vrijwilligers ondersteund karteringsproject dat het platteland van Tanzania op de kaart zet. Sinds 2015 voegen ze scholen, ziekenhuizen, wegen, gebouwen en dorpen toe aan OpenStreetMap met de hulp van vrijwilligers wereldwijd en ter plaatse in Tanzania. Dit doen ze zodat gemeenschappen zich beter kunnen oriënteren, hun ontwikkeling en voortgang naar de Duurzame Ontwikkelingsdoelstellingen (SDGs) kunnen plannen, en om activisten te helpen meisjes beter te beschermen tegen VGV.

Wat voor soort bijdrager ben je en in welk kaartgebied map je?

Ik ben een vrijwillige Casual Mapper die samenwerkt met Tanzania Development Trust, een non-profit organisatie die werkzaam is in de Verenigde Republiek Tanzania. Ik breng hetzelfde gebied in kaart. Crowd2Map Tanzania is sinds oktober 2015 bezig met het in kaart brengen van het platteland van Tanzania in OpenStreetMap. Ze hebben meer dan 16 000 remote mappers van over de hele wereld opgeleid om kaarten te maken op basis van satellietbeelden en meer dan 3 000 field mappers om hun lokale kennis toe te voegen aan deze basiskaarten, meestal met behulp van de gratis smartphone app Maps. Betere kaarten zijn van vitaal belang in de strijd tegen VGV en voor de ontwikkeling van de gemeenschap. Ik ben er trots op dat ik deel mag uitmaken van deze strijd tegen VGV door kaarten te maken.

Wat ben je in kaart aan het brengen? Heb je een specialisatie?

Ik heb zowel wegen als gebouwen in kaart gebracht en ik heb nog geen specialisatie.

Waar ben je het meest trots op als mapper?

Mapping heeft me in staat gesteld mijn kennis en vaardigheden verder te ontwikkelen.

Waarom breng je het in kaart? Wat motiveert je?

Betere kaarten hebben is van vitaal belang in de strijd tegen VGV en om de ontwikkeling van de gemeenschap te helpen.

Heb je ideeën over hoe we de OpenStreetMap-gemeenschap kunnen uitbreiden of meer mappers kunnen motiveren?

Ja, ik heb tot nu toe meer dan 16 remote mappers uit Oeganda opgeleid om satellietbeelden in kaart te brengen en meer dan 10 field mappers om hun lokale kennis toe te voegen aan deze basiskaarten in Tanzania en ik zal dat blijven doen.

Heb je contact met andere mappers?

Ja, ik heb contacten met sommige mappers.

Naar uw mening wat is de grootste kracht van OpenStreetMap?

Een van de grootste sterktes van OpenStreetMap is dat het je niet alleen een mooie sleepbare kaart geeft. Het geeft je de data, zodat je ermee kunt doen wat je wilt. Met een Export tab die aansluit op View en Edit bovenaan het scherm. Het geeft je een directe manier om de kaartgegevens te krijgen in een formaat dat jij wilt.

Wat is de grootste uitdaging voor OpenStreetMap?

In mijn eigen ervaring denk ik dat de uitdaging die ik ben tegengekomen met OpenStreetMap is dat sommige satellietbeelden niet duidelijk zijn en dit maakt het moeilijk voor iemand om betere kaarten te maken.

Hoe blijf je op de hoogte van het OpenStreetMap-nieuws?

Sta bekend om betrouwbaarheid. De definitie van betrouwbaar is: constant goed zijn in kwaliteit of prestatie en te vertrouwen zijn. Je hoeft niet in detail uit te leggen hoe het je reputatie en carrière ten goede komt als je eigen naam met zo’n uitspraak geassocieerd wordt.

Om af te sluiten, is er nog iets dat je zou willen vertellen aan de lezer?

Respecteer uw eigen tijd. Iedereen die ooit kostbare tijd heeft verloren met het vingeren op Facebook of het beantwoorden van een overweldigend aantal e-mails weet dat er een groot verschil is tussen actief zijn en effectief zijn. Productiviteit is de ruggengraat van succes en de kryptonite ervan is burn-out, die, zo hebben studies aangetoond, leidt tot veel meer dan alleen een slechte dag!

Hartelijk dank, Constantine, voor dit interview.

Bilan de mes devoirs de vacances... rendu FR, nouveaux serveurs, tests, tests ! - mer 1 sep 2021 - 0:23

J’ai profité de l’été pour me (re)-lancer dans le chantier “serveurs de tuiles”.

Petits rappels

OpenStreetMap France héberge génère plusieurs fonds de carte à l’aide de ses “serveurs de tuiles”:

  • rendu “FR”, une adaptation commencé en 2012 du style OSM de l’époque, destinée à un public francophones (noms en français en priorité, icône plus parlantes en France, etc) avec des ajouts originaux (terrains de sport, etc)

  • le rendu “humanitaire” largement utilisé par HOT et disponible aussi sur

  • le rendu “CyclOSM” , le petit dernier, lui aussi disponible sur

À cela s’ajoute aussi OpenRiverBoat, un rendu adapté à la navigation fluviale, des rendus en langues régionales, des rendus techniques.

Les trois premiers sont assez fortement utilisés et complexes. Le rendu “FR” contient par exemple 82 couches différentes parfois multiples ce qui donne au total plus de 170 couches de dessin pour arriver au rendu final avec plus de 10000 règles qui servent à décider comment représenter graphiquement tel ou tel objet.

Les outils utilisés

Le cœur est une base postgresql/postgis, qui contient les données OSM utiles à la fabrication du fond de carte et à sa mise propre mise à jour.

Les données OpenStreetMap brutes sont importées dans postgresql puis mises à jour régulièrement à l’aide d’osm2pgsql. Typiquement la base résultat occupe environ 1To.

La génération du fond de carte est faite par renderd qui utilise la librairie mapnik pour transformer les données vectorielles issues de postgresql en images en appliquant une feuille de style.

Cette feuille de style au format XML utilisée par mapnik, est générée à l’aide de kosmtik à partir un code source écrit en cartocss, une sorte de CSS adaptée à la cartographie.

renderd interagit avec apache via mod_tile qui gère un cache de “méta-tuiles” contenant 8x8 tuiles telles que demandées par les navigateurs, de 256 ou 512 pixels de côté (version “retina” en double résolution).

Un cache est en effet nécessaire car le calcul d’une méta-tuile peut prendre plusieurs secondes (parfois plusieurs dizaines de secondes).

Besoin grandissants et saturation

Depuis plusieurs années, nos serveurs de tuiles saturent régulièrement et ont du mal à suivre les demandes pour mettre à jour le fond de carte sans trop de délais.

En effet, la base de données OpenStreetMap est en perpétuelle évolution, et le fond de carte produit avec a besoin d’être mis à jour en permanence, surtout quand ceux-ci sont consultés par des contributeurs qui veulent vérifier que leurs contributions ont bien été prises en compte et sont correctes.

Lors de chaque mise à jour faite par osm2pgsql, une liste des tuiles impactées par les changements et générée, or, le nombre de contribution augmente au rythme du nombre de contributeur qui de fait que croître (tant mieux !).

La quantité de données dans la base de données augmente elle-aussi, ce qui fait plus d’objets à récupérer dans la base de données et à dessiner sur une zone donnée.

Et troisième phénomène, les consultations elles aussi ont fortement augmenté… donc tout mis bout à bout, la charge sur les serveurs n’est plus du tout la même que lorsque nous les avons mis en place il y a bientôt 10 ans pour certains !

L’ajout de RAM ou de SSD toujours plus rapides et volumineux ne suffit plus… il faut changer aussi les serveurs.

Tests et optimisations Revoir la stratégie de mise à jour du cache

À chaque contribution, à un endroit donné, toutes les tuiles sont potentiellement impactée à tous les niveaux. osm2pgsql ne sait pas en effet déterminer si tel objet figure bien sur le rendu niveau de zoom par niveau de zoom.

L’ajout ou la modification d’un banc qui ne sera visible que sur les plus forts zoom, n’a pas d’impact sur les zooms plus faibles… mais c’est très complexe à déterminer.

Recalculer une tuile de niveau 13 ou 14 est bien plus coûteux car elles contiennent typiquement plus d’objets que les tuiles de zoom 19 ou 20. Sur Paris par exemple, c’est de l’ordre de 100 000 objets en zoom 13/14 contre quelques milliers en zoom 19/20.

Il faut donc limiter le recalcul coûteux et souvent inutile à certains zoom.

Pour les zoom 0 à 12, ce recalcul est fait une fois par semaine, en plein nuit, pendant les heures creuses (qui étaient bien rares).

Jusqu’à maintenant, à chaque mise à jour de la base, toutes les tuiles à partir du zoom 13 était “invalidéee”, c’est à dire marquées dans le cache comme obsolètes et devant être recalculées. Dès qu’elles étaient demandées pour être vue par un internaute, mod_tile demandait à renderd de la recalculer

J’ai remplacé cette invalidation systématique, par une invalidation zoom par zoom. Le zoom 13 est (au moment ou j’écris ce billet) invalidé une fois par jour, puis le 14 deux fois par jour, le 15 et le 16 quatre fois par jour, mais pas en même temps, et à partir du 17 il n’y a pas de changement. Cela va sûrement évoluer.

Un pic de charge est visible sur les graphes du serveur suite à l’invalidation, mais tout cela reste assez lissé pour éviter les saturations tout en favorisant le recalcul des zooms les plus élevés, là où un contributeur voudra vérifier sa contribution.

Nouveaux serveurs

Cela faisait longtemps qu’on devait le faire suite à un appel aux dons de fin 2018 et un nouveau serveur a été acheté cet été. Une machine d’occasion, donc à prix très raisonnable comparé à du neuf, mais d’une génération pas trop ancienne.

Il s’agit d’un rack Fujitsu Primergy CX400M1, contenant 4 lames avec chacune 2 Xeon avec 12 cœurs… 96 cœurs au total !

Ajout de RAM (256Go, mais chaque lame peut avoir jusqu’à 1To de RAM) de SSD NVMe et SATA (2To chacun)… et on peut démarrer les tests.

ZFS or not ZFS ?

ZFS est un système de stockage très complet, qui aligne plein de fonctionnalités intéressantes. J’ai voulu vérifier que ceci ne se faisait pas (trop) au détriment de la performance…

J’ai donc testé l’import de la base monde (alias “planet”) en ZFS, avec et sans compression, avec de petits blocs de 8K ou des gros de 128Ko, etc… au final ça ne change presque rien, mais l’espace occupé sur disque par la base de données peut être divisé par 2 !

Ceci a aussi pour conséquence qu’une part plus importante de la base peut reste en RAM dans le cache de ZFS (l’ARC) qui reste compressé lui aussi… et donc on limite encore un peu plus les I/O en utilisant un peu de CPU pour la décompression à la volée… et avec 24 cœurs il y a de quoi faire :)

ZFS validé !

Tuning de postgresql

Postgresql et postgis ont eux aussi évolué (versions respectives 13 et 3.1)… de nouveaux types d’index sont venus compléter les index GIST, il s’agit des SP-GIST.

Passer de GIST à SP-GIST permet de diviser par 3 la taille des index sur les objets linéaires et surfaciques, un peu moins sur les ponctuels.

Des index plus petits, c’est plus d’index en cache, et là encore plus de performances au final.

Un autre progrès vient d’osm2pgsql qui utilise un nouvel index bien plus compact pour retrouver les way passant par un node.

Couplé à la compression de ZFS, c’est au final près de la moitié de la base de données (data+index) qui peut tenir désormais dans les 256Go de RAM du serveur ce qui accélèrent grandement les requêtes en évitant les accès au SSD qui bien que rapide est quand même bien plus lent que la RAM.

Tuning de renderd/mapnik

Là cela se passe à plusieurs niveaux :

  • simplifier la feuille de style, par exemple en réduisant le nombre de “couches”

  • améliorer les requêtes postgresql pour retourner uniquement les données utiles afin de réduire tous les traitements en aval

  • bien exploiter les index de postgresql

  • optimiser les appels de mapnik à postgresql

J’avais déjà passé mon été dernier sur les 3 premiers points, cette fois-ci j’ai attaqué le 4ème et là grande surprise !

cache CACHE !

Certaines couches de dessin utilisent les mêmes données, c’est à dire qu’une seule requête est faite dans la base de données mais qu’on applique ensuite plusieurs passe de style dessus.

Le fonctionnement pas défaut de mapnik est étonnant… il ré-exécute la requête. Une option (cache-features) permet de conserver le résultat et de ne pas répéter la requête plusieurs fois, mais ce n’est pas le fonctionnement pas défaut !

Là, je comprends enfin quelque chose… un “problème” constaté depuis plusieurs années que je n’expliquait pas: une perte énorme de performance. En fait mapnik, a sûrement changé son mode par défaut (je n’ai pas vérifié)… sans trop prévenir.

L’ajout de cette simple option a eu un effet radical sur notre serveur osm25 qui s’occupe essentiellement du rendu “FR”:

  • 53% des tuiles retournées par le serveur étaient expirées, c’est à dire non mises à jour, c’est maintenant moins de 4%

  • le CPU utilisé a très fortement baissé

  • le nombre de tuiles calculées par seconde a été multiplié par 4

C’est comme si on avait retiré le frein à main :)

D’autres améliorations ont aussi été faites en lisant mieux la documentation du fonctionnement de mapnik avec postgresql, comme l’utilisation de curseurs. J’avais loupé cette évolution, car on n’a pas toujours le temps de lire en détail les nouveautés lors des mises à jour de nos outils… un tort !

La suite…

Il reste à finaliser des modifications de la feuille de style “FR”, pour la déployer sur le nouveau serveur.

En attendant, la version en développement est visible ici:

Harmoniser les index utiles aux 3 principaux rendus sera aussi un chantier à faire, c’est déjà largement le cas entre le rendu FR et humanitaire.

A deep dive into the OSM Wiki for service=driveway, the proposal service=Driveway2 and lack of professionalism by one OSM Wiki administrator - mar 31 aoû 2021 - 23:07

This diary explores the problems with the OSM Wiki entry for service=driveway, and why is there a need for service=driveway2. In the process, it also describes the headaches encountered while trying find a optimal solution. However, deeply entrenched opinions makes this process untenable.

Need for clear indication of classified service way type

The topic of discussion will need to begin on how OSM tags are designed in an hierarchy, which begins with initial key-value pair of highway=service, followed by classifier tags service=driveway or service=parking_aisle. Note that highway=service without any service=* does not tell the data consumer if this is simply a minor way that is un-classified (not yet assigned a classification type such as parking_aisle or alley or driveway), or if this minor way is an implicit driveway. In general, a data consumer will assume that the way is un-classified, instead of assuming that it is an implicit driveway.

The classifier issue is the first issue present in the service=driveway Wiki entry - that suggests that minor ways linking from major roads to parking_aisles should be tagged as an implicit driveway with no classifier tags.

  • This means that data consumers are unable to determine if the way segment is un-classified, or if it is indeed an implicit driveway when such minor service way connected to parking_aisles are encountered..
  • Similarly, a user whom just want to quickly add minor service roads but does not perform classification will mean that data consumers cannot identify if such ways are classified or un-classified, and therefore prevents accurate assessment if further classification is required.
Definition of driveway

This leads to the second problem of what is meant by a driveway, and what is the problem with the Wiki entry. The problem lies with the “classical” definition of driveway, which in the early days of OSM defines it as “a short private road that leads from a street to a person’s house or garage”, sourced from the “American” section of Cambridge’s dictionary. Oxford/Lexico US likewise provides a similar definition “a short road leading from a public road to a house or garage”. This was the original argument by some Wiki participants on what is meant by driveway - mainly based on US English dictionary definitions.

Nevertheless, let’s dive into history where driveway was first defined - ironically in the US California Streets and Highway Code (SHC), which first introduces the driveway term in 1971. In this law stature, driveway “means a paved portion of a public street providing an unobstructed passage from the roadway to an offstreet area used for driving, servicing, parking, or otherwise accommodating motor vehicles.” This part here is significant because this definition predates the introduction of UK highway codes, and describes general use of minor ways as driveways. Note that California laws are very influential in the auto-industry, and drives formation of rules across the US and beyond (impacts globally). Moving to UK law statures (remember the part of OSM being of UK origins?), the term driveway is itself not defined in the law statures. This strongly suggests that usage of this term is strongly linked to “American” usage of this term, which is something pushed by members of the OSM US chapter.

We will further focus on the UK definitions of the term, which is likewise defined in Cambridge’s UK definition as “a private area in front of a house or other building onto which you can drive and park your car”, and similarly Oxford/Lexico UK’s definition of “a short road leading from a public road to a house or other building”. Note that in both UK dictionary definitions, it never suggests that driveway only links to residential properties which routing engines should avoid routing through, but instead is a more general definition similar to the California SHC where it is a minor way going to any property (I.e. no destination access to residential as contrast to US definition).

The difference in understanding is also why despite the Wiki proclamations of such “rules”, there are a large group of users whom are still tagging wrongly - being that they follow the UK definitions or the SHC definitions instead of the US definitions that should be more appropriately tagged as service=residential_driveway (which should apply a routing penalty). This incorrect Wiki definition is the second problem of the existing service=driveway page, where the optimal and most generic classifier used in SHC cannot be defined under service=driveway tagging.

Implications Implications to routing

Maybe you may get the implications to routing at this point, but what is meant by service=driveway in the existing Wiki is meant to apply routing penalties such that routing engines do not route through such driveways. However, this is of the mistaken belief that these ways mostly represent destination minor ways whereby most of such ways are of private access to residential buildings. The more correct representation for such ways is the more appropriate service=residential_driveway, to ensure routing penalty is applied to such ways while allowing service=driveway to be routed through at a significantly lower speeds. This is because in most cases, such minor ways are meant to be publicly accessible to gain access to a property, but is not of a major road type such as highway=residential/unclassified which is a major road class.

Implications to “correct tagging” of driveway (using SHC/UK definitions), and proper use of classifier service=driveway

Well, so far so good, but why is there a need to change the current behaviour? Well, other than people tagging using both types of definition, there are often zealous users whom attempt to “correct” such incorrectly tagged ways such that any classifiers such as service=driveway on minor ways linking to service=parking_aisles are removed.

In essence, useful information detailing the minor way type is removed to an un-classified state, leaving the data consumer left guessing if this is an implicit driveway, an un-classified driveway or a residential_driveway as in problem (1). When you attempt to stop them from removing such details, such users typically will just refer to the Wiki as the source-of-truth, despite that fact that the Wiki itself is also not authoritative and is simply meant to document tag usage for the goal of harmonising tags used. This causes problems whereby correct tagging by natural language understanding falls prey to differently defined Wiki entries.

Proposal Proper Resolution

The most correct way to resolve this problem is to tweak the Wiki to…

  1. Remove the restriction whereby ways connecting minor ways to parking_aisles should be tagged without the service=driveway classifier. In general, it should be assumed that highway=service without service=* means that the way is un-classified but of minor way, and highway=service with service=* are correctly classified ways.
  2. Introduce service=residential_driveway for the purpose of private access and destination driveway to residential properties, which is what Amazon and various entities likes to map. In this way, service=driveway can take on its oldest SHC and UK origins definition which is minor road that is meant for motor vehicles and public access, but does not satisfies other classifications such as service=parking_aisle/alley/e.t.c.
Status Quo

In the absence of such changes, we can only continue to tag the SHC and UK definition of driveway as service=driveway2. However, one will typically still run into zealous mappers whom insist on removing classifier tags such as (1).

Notable Problems when discussing with community Community

The general sense of trying to have a fruitful discussion with various communities is don’t bother. Despite trying to argue the merits and cons, you will have people insisting on schematic definitions (insisting that US dictionary definitions are correct), insisting that other usages of driveway is wrong, insisting that the definition is local/globally used with consensus reached (and thus dismissing local concerns which actually arise from problems with the Wiki entry), insisting that SHC/UK definitions do not matter, do not recognise the problems faced due to a non-authoritative Wiki entry, and in general dismisses your arguments.

Unprofessional behaviour

Worse, there is one OSM Wiki administrator exhibiting appalling and un-professional behaviour whom insist that this is a user problem. Not only that, this OSM Wiki administrator had to put in his personal opinion by stating that the solution of documenting tag use in the Wiki is the proposal one of user (and that is me). This is something I am proud of, because we are following the process to document tags use instead of trying to fix the service=driveway Wiki page which we have already accepted will be left in the US definition. Indirectly, this becomes a form of personal attack which is uncalled for.

Community Consultation - Etiquette Guidelines and Moderation for OSM /OSMF - mar 31 aoû 2021 - 7:52

We seek your community input - please help us by sharing the Etiquette guidelines and giving input on the OSM wiki by September 8, 2021. We also have some upcoming consultation meetings to hear your views. ## Announcement

The LCCWG moderation subcommittee is holding two online public meetings about the revisions to the current Etiquette Guidelines, which are now open for public comment.

The draft guidelines are found here, with comments open to Sept 8:

Both public online meetings will be held via Big Blue Button in this room:

Two timeslots to accommodate a global audience.

Meeting #1: Thursday September 2; 1400 UTC (your time zone)

7 AM Pacific Time (US) 10 AM Eastern Time (US) 2 PM UTC 4 PM Central European Time

Meeting #2: Saturday, September 4; 06:00 UTC (your time zone)

11:00 PM Pacific Time (US; evening of Sept 3) 02:00 AM Eastern Time (US) 06:00 AM UTC 08:00 AM Central European Time 09:00 Nairobi 11:45 Kathmandu 1300 Jakarta 1400 Manila 1600 Sydney

Give input on the OSM wiki by September 8, 2021

See full details for the Etiquette and moderation process on the wiki -. The draft guidelines are found here, with comments open to Sept 8th, 2021

With thanks on behalf of the subcommittee

Gerbang Hutan Kota Kaombona - dim 29 aoû 2021 - 20:57

Hutan Kota Kaombona Kota Palu

Historic surface mining. - dim 29 aoû 2021 - 20:33

I have mapped areas of Bodmin Moor especially around Minions which was originally a mining settlement. Large parts have been mined until around 1900, but it is likely that there has been mining since prehistory.

Early mining, as least medieval, was largely based on streamwork. This is described here ( That describes a particularly large example near Minions. This website ( includes some photographs.

As seen in those pictures, the ground is heavily disturbed. That case is fairly extreme. Often the area is smaller, but usually following a stream, and only a few metres deep. Frequently the ground is sandy with fine gravel, presumably from the extracted waste. Actually that is true in places at Gonamena, and it is also true of other smaller workings around Minions.

We don’t (yet) have any good tagging for these places, but I had used landuse=surface_mining which I think captures these distinctive areas quite well. Together with disused=yes. Unfortunately another mapper decide to change that tagging to landuse=quarry which is just plain wrong.

I have now changed to historic=mine (I am not keen on that) and landuse=disturbed (also not really a landuse) until someone comes up with better ways of capturing these special places. Perhaps I might change historic from mine to surface_mining.

There is a thread on about this.

فروشگاه اینترنتی سی سی نت شاپ - dim 29 aoû 2021 - 16:36

لطفا به وبسایت فروشگاه اینترنتی سی سی نت شاپ مراجعه نمایید که می توانید اینجا کلیک کنید.

weeklyOSM 579 - dim 29 aoû 2021 - 11:06


How old is that building in Penza (Russia)? [1] map data © OpenStreetMap contributors | © 2021, data sources: Росреестр, Минкультуры, «МинЖКХ», Викигид, Викиданные, Викимапия

Mapping campaigns Mapping
  • Anim Mouse noticed a changeset that spans four continents and contains only a single change. Although it was pointed out in the discussion that a changeset should contain as small an area as possible, sometimes it is not possible when the element itself is very large, in this case France, including its overseas territories and départements.
  • Bora Can wrote > about his efforts to clear up divergent district boundaries in Turkey.
  • Russ Garrett summarised his thoughts on how various recently released government open datasets might be used to improve address mapping the UK.
  • State of the Map Africa 2021 is happening online on 19 to 21 November. Listen to the July episode of the Geospatially podcast, featuring Geoffrey Kateregga who discussed SotM Africa and how they will bring OSM communities in Africa together.
  • Manoj, Ark, and Awantika took a look at the history of OSM Kerala and its continued efforts to strengthen the use of OSM in Kerala (India) for disaster response and community development.
  • One has learnt that Christoph Hormann’s ‘couple of words’ tend to be a bit longer than the phrase implies. His theme discussed this time is the implications of the draft OSMF Etiquette Guidelines. Although a DeepL translation to English is provided, he emphasises that this will lack nuances of the original German text: an issue which he feels affects any contributor needing to use English when it is not their native language.
OpenStreetMap Foundation
  • weeklyOSM strives to notify you, our readers, about upcoming OSMF board meetings. Unfortunately, at present announcements of upcoming meetings are being made within a week of the meeting, so it is not possible for us to announce them accordingly. If you are interested in the public board meetings, you should follow the OSMF mailing list, subscribe to the Board’s iCalendar feed, or keep an eye out for them in our Upcoming Events section.
  • Former OSMF Board member Peter Barth expressed his concern about the attribution of OSM on maps provided through Mapbox services.
  • The Community Working Group (Humanitarian Open Mapping) organised by HOT invites local OSM community organisers, leaders and members (new and old) to come together and share their tips, tricks and challenges related to starting and sustaining local OSM communities. Two Zoom meetings will be held on Friday 3 September at 06:00 UTC and 16:00 UTC. Register if you wish to participate.
Humanitarian OSM
  • HeiGIT is working on routing that incorporates current data from disaster areas, such as areas subject to flooding or destroyed streets. To help with the current flood disaster in Germany and neighbouring countries, HeiGIT has taken up-to-date flood data derived from satellite images by the European Copernicus Emergency Mapping Service (EMS) and integrated them into the routing services developed by HeiGIT.
  • In mid-August HOT, in collaboration with local communities in the respective regions, activated two disaster response campaigns: Haiti Earthquake 2021 and Mediterranean Fires 2021. You can check the updates here and see other active responses.
  • The Humanitarian OpenstreetMap Team (HOT) Summit 2021 Call for Proposals has been extended. The new deadline is Tuesday 31 August.
  • The finals of the 2021 HOT Staff OSM FIGHT Heavyweight Championship were held at a recent HOT all staff meeting.
  • [1] Ever wondered how old that building in Penza (Russia) is? Then this is the website for you. In addition to OSM, data from wikivoyage, wikidata and wikimapia, among others, have been used.
  • Nicolelaine is still having trouble getting their uMap of world post boxes to work, due to Overpass timeouts. Any help would be appreciated.
  • PlayzinhoAgro shared > the results of a survey of online map use and knowledge of OpenStreetMap in Brazil.
  • Recently we covered the KGeoTag application. There is a similar application called geotagging, a tool for manipulating the geographical information stored in JPEG images (Exif metadata). The geographical information could be obtained from GPX or manually by drag-and-drop. The application is packaged as an EXE or as a flatpak. Feel free to contribute translations or code.
  • Trufi’s OSM-powered bike app will put bikes at the centre of multi-modal journeys like no other app. The app will launch in Hamburg at the ITS World Conference.
  • The final reports for projects that were part of the 2021 Google Summer of Code are in:
    • Vuong Ho’s opening hours tag evaluator
    • Zohaib Ansari’s stand-alone library to display multiple versions of any selected OSM element and allow comparison between different versions
    • Antonin Jolivat’s Nominatim QA reports extraction tool.
Did you know …
  • The Panorama of the River Thames? This is a website which shows panoramic views of parts of the River Thames through Greater London both from watercolours of 1829 and photographs from the present day.
  • … that you can use OSM Smart Menu in Google Chrome or Mozilla Firefox to open links related to OpenStreetMap, based on parameters from the current page? It helps OpenStreetMap contributors to easily switch between different maps and analysis tools.
  • … that LearnOSM is dedicated to helping people learn how to map in OpenStreetMap? The guides start from the basics of what OSM is and how to get mapping, through to advanced topics such as osm2pgsql and manipulating data with Osmosis.
  • … you can check out who is the busiest on MapRoulette by viewing the leaderboard?
OSM in the media
  • Woxx carried a couple of articles on OpenStreetMap. The first > is an introduction to OpenStreetMap and features an interview with OSMF Board member Guillaume Rischard. The second > article describes to readers a number of ways that they can also participate in OpenStreetMap.
Other “geo” things
  • Médecins Sans Frontières (MSF) is seeking a Geographical Information Systems Advisor. Based preferably in Amsterdam, Berlin, London, or Nairobi. Other locations where MSF has offices will also be considered.
Upcoming Events Where What Online When Country 潍坊市 OpenStreetMap(中国大陆)第一次线下聚会 2021-08-20 – 2021-08-30 Autrans-Méaudre en Vercors WikiCamp L’Escandille 2021-08-28 – 2021-08-29 Bogotá Distrito Capital Resolvamos notas de Colombia creadas en OpenStreetMap 2021-08-28 OSMUS Slack Summer mapping party 2021-08-28 – 2021-08-29 Hlavní město Praha Missing Maps CZ Mapathon 2021 #5 2021-08-31 cz San Jose South Bay Map Night ✓ 2021-09-03 Kurmin Musa Community Webinar: Local OSM community building: Tips, tricks and challenges 2021-09-03 ng Fortaleza Encontro de usuários OSM do Ceará, Brasil. 2021-09-04 Bogotá Distrito Capital Resolvamos notas de Colombia creadas en OpenStreetMap 2021-09-04 京田辺市 京都!街歩き!マッピングパーティ:第26回 一休寺 2021-09-04 jp OSM Africa Monthly Mapathon: Map Malawi 2021-09-04 – 2021-10-04 Greater London Missing Maps London Mapathon 2021-09-07 Landau an der Isar Virtuelles Niederbayern-Treffen ✓ 2021-09-07 Stuttgart Stuttgarter Stammtisch (Online) 2021-09-07 OpenStreetMap Michigan Meetup 2021-09-09 Nordrhein-Westfalen OSM-Treffen Bochum (September) 2021-09-09 Arlon Réunion des contributeurs OpenStreetMap, Arlon 2021-09-13 Hamburg Hamburger Mappertreffen ✓ 2021-09-14 Karlsruhe Karlsruhe Hack Weekend 2021-09-17 – 2021-09-19

If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by Nordpfeil, SK53, Sammyhawkrad, TheSwavu, derFred, s8321414.