[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:dc="" xmlns:geo="" xmlns:georss="">
  3.  <channel>
  4.    <title>OpenStreetMap diary entries</title>
  5.    <description>Recent diary entries from users of OpenStreetMap</description>
  6.    <link></link>
  7.    <image>
  8.      <url></url>
  9.      <title>OpenStreetMap diary entries</title>
  10.      <width>100</width>
  11.      <height>100</height>
  12.      <link></link>
  13.    </image>
  14.    <item>
  15.      <title>OpenStreetMap 13th Aniversary mapathon in Latin America</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;The OpenStreetMap Latin American community communicates constantly in a Telegram chat in addition to other social networks, on technical issues, methodological challenges or local communities dynamics, projects, achievements, sometimes opinion debates, etc. The dialogue has led subgroups to form, as &lt;a href="" rel="nofollow"&gt;Geochicas&lt;/a&gt; last fall 2016, and collective projects to emerge around a conjuncture or a shared interest. A chat allows everybody to join a dynamic in process. Integrating, learning along the way or just observing, soaking up, and also identifying as a community.
  19. I think the anniversary mapathon was a great opportunity for this in the LATAM community.&lt;/p&gt;
  21. &lt;p&gt;A happy coincidence led this community to plan a continental scale mapathon, on the occasion of the 13th anniversary of OpenStreetMap.&lt;/p&gt;
  23. &lt;p&gt;From Mexico, after 2 years of repeated massive training efforts in universities and other civil and government communities, the tendency of the OSM Mex group is to make a pause and dedicate more, for a time, to the improvement of the map through remote mapathon promoted in the existing community.&lt;/p&gt;
  25. &lt;p&gt;On the other hand the group &lt;a href="" rel="nofollow"&gt;Geochicas&lt;/a&gt;, from their debates on the different ways to produce information and improve the database of OpenStreetMap in a sense that benefits women, and taking advantage of these activities to empower women in the community, we also decided a few months back to organize at some point a large remote mapathon on areas where women experience an acute level of vulnerability. Vulnerable areas, in general, would benefit from mapping and women, in particular, would receive an even greater impact as a result of overall improvement of information, as well as promoting a parallel and permanent mapping of equipment and points of interest considered useful for women. This second category of data, being more difficult to collect without a fine local knowledge, it seemed more feasible to organize a general mapathon of vulnerable settlements.&lt;/p&gt;
  27. &lt;p&gt;We started in the LATAM chat to talk about the 13th anniversary of OpenStreetMap. Several people, among whom Humberto Yances and the women of Geochicas, mentioned the possibility of making a LATAM mapathon where the communities of all the active countries would be coordinated during August.&lt;/p&gt;
  29. &lt;p&gt;Due to the inclination of some participants towards the humanitarian dimension, also worried from Mexico by the great lag in the map of the South of this country, regularly affected by cataclysms, we agreed to promote the topic of vulnerable irregular settlements, among others.&lt;/p&gt;
  31. &lt;p&gt;Humberto Yances took a proactive role in the methodology and coordination of this mapathon, guiding groups in the collection of priority polygons using pre-existing links with specialized organizations in the continent and in countries, in housing or in vulnerable areas, such as in particular Techo Internacional; Organizing and guiding the participants to construct a series of Wikis (see list below) to carry out the operation in an articulated way and with a systematic documentation; And also training us in the use of the &lt;a href="" rel="nofollow"&gt;Tasking Manager Colombia&lt;/a&gt; so that each group could realize its projects and will drive the mapping in their respective communities.&lt;/p&gt;
  33. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  34. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  36. &lt;p&gt;In Mexico, we used information from Techo México as well as from the IMPLAN of Ciudad del Carmen that represents an area of high vulnerability to hurricanes, with rapid and disorganized urban growth affecting natural areas of mangroves, where @Mapeadora has direct contact. For the long term, we added another project with the municipalities of the country with a high level of social marginalization, established from CONEVAL (National Council for the Evaluation of Social Development Policy) in 2010. Cuauhtémoc (@eldesbastemap) worked hard to prepare the information and @mapeadora created and manages the &lt;a href=";direction=desc&amp;search=%23Mexico" rel="nofollow"&gt;Tasking Manager&lt;/a&gt;.&lt;/p&gt;
  38. &lt;p&gt;During August, the projects of the whole region were promoted in the networks and also through face-to-face mapping activities with students and other communities.
  39. &lt;a href=";src=typd&amp;lang=es" rel="nofollow"&gt;Thread on twitter&lt;/a&gt;&lt;/p&gt;
  41. &lt;p&gt;In Mexico, we started August with a &lt;a href=";src=Typd&amp;lang=es" rel="nofollow"&gt;mapathon at the Autonomous University of the State of Mexico&lt;/a&gt; with which we have a solid collaboration, and we reached the participation of 90 students, guided by @Mapanauta and @Beny Carbajal.
  42. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  44. &lt;h2&gt;Results&lt;/h2&gt;
  46. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  47. &lt;img src="" alt="Alt text"/&gt;
  48. &lt;a href="" rel="nofollow"&gt;Missingmaps leaderboards&lt;/a&gt;&lt;/p&gt;
  50. &lt;h2&gt;Learning&lt;/h2&gt;
  52. &lt;ol&gt;
  53. &lt;li&gt;&lt;p&gt;In terms of community and networking, learning is invaluable. The mapathon represents a collective project that strengthens ties and is a powerful vector of knowledge transmission.&lt;/p&gt;&lt;/li&gt;
  54. &lt;li&gt;&lt;p&gt;On collaborations with institutions specialized on housing and climate vulnerability  (international or national scale), with Municipal Institutes, we have been able to understand better the needs in terms of data management and use, the urgency to improve information as it deals with resilience and disaster prevention, and the great opportunity to provide more specific support and make links this mapping work with action in areas of risk (case of the Island of Carmen). The map is a lever for more in-depth collaboration, timely knowledge of territories, and action.&lt;/p&gt;&lt;/li&gt;
  55. &lt;li&gt;&lt;p&gt;On local community strengthening strategies, the Mexican community is not large or united enough to achieve meaningful participation through a single open call. Despite our desire to temporary stop massive training activities, it was in this way that we were able to obtain a relevant participation, implying another difficulty: a strong need for guidance.&lt;/p&gt;&lt;/li&gt;
  56. &lt;/ol&gt;
  58. &lt;p&gt;The most common edits difficulties are:&lt;/p&gt;
  60. &lt;ul&gt;
  61. &lt;li&gt;Lack of habit in the observation of the imagery, which discards many important objects, such as natural elements, rivers, etc.&lt;/li&gt;
  62. &lt;li&gt;A difficulty to correctly map buildings with an orthogonal shape because they are only partially seen in the imagery&lt;/li&gt;
  63. &lt;li&gt;A low tolerance towards despair, having to map a dense built area, or opening cells with few objects to map.&lt;/li&gt;
  64. &lt;li&gt;A low understanding of the need to articulate the contents of the cells with each other which leads students to use the cell boundary as the strict limit of objects.&lt;/li&gt;
  65. &lt;/ul&gt;
  67. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  68. &lt;img src="" alt="Alt text"/&gt;
  69. &lt;img src="" alt="Alt text"/&gt;
  70. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  72. &lt;p&gt;We also find meticulously covered tasks:
  73. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  75. &lt;p&gt;We understand that involving a large number of beginners in such an extensive mapping operation means important monitoring, validation and cleaning work on our part.&lt;/p&gt;
  77. &lt;h2&gt;This leads to several strategies (please share comments and experiences)&lt;/h2&gt;
  79. &lt;ul&gt;
  80. &lt;li&gt;The first concerns the &lt;strong&gt;balance between objects quantity and quality&lt;/strong&gt;. In the current conditions of the Mexican community, privileging quality over quantity in the first instance would mean to give up progress on the map.&lt;/li&gt;
  81. &lt;li&gt;If we decide instead to involve large groups of beginners who will be trained with the hope they&amp;#39;d be part of the active community of OpenStreetMap, and accepting the cost of significant monitoring and correction work by very few people, forces us to &lt;strong&gt;look for new ways to save time on other tasks and optimize teaching methods&lt;/strong&gt;.&lt;/li&gt;
  82. &lt;/ul&gt;
  84. &lt;p&gt;We now consider it is necessary to integrate mapping exercises into the school programs where we collaborate in a continuous way, articulated with courses on cartographic tools and &lt;strong&gt;not only establishing incentives and valuations but also qualification mechanisms by the University&lt;/strong&gt;.
  85. We are devising a scheme to coordinate with the teachers, to think about the &lt;strong&gt;most functional mechanisms to monitor the editions on complete semesters and to qualify each mapper&lt;/strong&gt;, besides creating some &lt;strong&gt;certificate validated by OpenStreetMap and the partners of Humanitarian OpenStreetMap Team&lt;/strong&gt;. Humanitarian support has the potential to generate strong interest in students, which, in addition, strengthen professional skills by learning the use of mapping and monitoring tools, and eventually analyzing cartographic databases.&lt;/p&gt;
  87. &lt;h2&gt;Wikis links&lt;/h2&gt;
  89. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;
  90. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  91. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  92. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  93. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  94. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  96. &lt;h2&gt;&lt;a href="" rel="nofollow"&gt;Resources for viewing changes during mapping&lt;/a&gt;&lt;/h2&gt;
  98. &lt;h2&gt;&lt;a href=",aniversarioxiii_latam" rel="nofollow"&gt;Monitoring Tools&lt;/a&gt;&lt;/h2&gt;
  99. </description>
  100.      <dc:creator>mapeadora</dc:creator>
  101.      <pubDate>Tue, 22 Aug 2017 21:25:56 +0000</pubDate>
  102.      <comments></comments>
  103.      <geo:lat>19.405078137486</geo:lat>
  104.      <geo:long>-99.1365051269531</geo:long>
  105.      <georss:point>19.405078137486 -99.1365051269531</georss:point>
  106.    </item>
  107.    <item>
  108.      <title>Rho Ciclabile Via Vittorio Veneto</title>
  109.      <link></link>
  110.      <guid></guid>
  111.      <description>&lt;p&gt;Per il progetto città di Rho ciclabile è stata aggiunta la pista ciclabile di Via Vittorio Veneto e un&amp;#39;ulteriore sezione della pista ciclabile Via Preganana che va dall&amp;#39;incrocio con Viale Italia all&amp;#39;incrocio con Via Vittorio Veneto.&lt;/p&gt;
  112. </description>
  113.      <dc:creator>fra_miglietta</dc:creator>
  114.      <pubDate>Tue, 22 Aug 2017 12:15:38 +0000</pubDate>
  115.      <comments></comments>
  116.      <geo:lat>45.527010336433</geo:lat>
  117.      <geo:long>9.03604567050934</geo:long>
  118.      <georss:point>45.527010336433 9.03604567050934</georss:point>
  119.    </item>
  120.    <item>
  121.      <title>Mapaton aniversario LATAM 2017</title>
  122.      <link></link>
  123.      <guid></guid>
  124.      <description>&lt;p&gt;La comunidad latinoamericana de OpenStreetMap se comunica de manera constante en un chat de Telegram además de otros medios, sobre preguntas técnicas, retos metodológicos o de comunidades locales, proyectos, logros, a veces debates de opinión, etc. El diálogo ha llevado subgrupos a formarse, como fue el caso de Geochicas desde el otoño pasado 2016, o proyectos colectivos emerger entorno a alguna coyuntura, un interés compartido. Un chat permite unirse a una dinámica en proceso. Agregarse, aprender en el camino o simplemente observar, empaparse, y también interactuar e identificarse como comunidad.
  125. Considero que el mapaton aniversario fue una gran ocasión para esto en la comunidad LATAM.&lt;/p&gt;
  127. &lt;p&gt;Una feliz coincidencia llevó esta comunidad a planear un mapaton de escala continental, en ocasión del 13vo aniversario de OpenStreetMap.&lt;/p&gt;
  129. &lt;p&gt;Desde México, después de 2 años de esfuerzos repetidos de capacitación masivas en universidades y otras comunidades civiles y gubernamentales, la tendencia del grupo de OpenStreetMap es pausar este tipo de esfuerzo para dedicarse más, durante un tiempo, a la mejora del mapa a través esta vez de mapatones remotos promovidos en la comunidad existente.&lt;/p&gt;
  131. &lt;p&gt;Por otro lado el grupo &lt;a href="" rel="nofollow"&gt;Geochicas&lt;/a&gt;, por sus reflexiones sobre las distintas maneras de producir información y mejorar la base de datos de OpenStreetMap en un sentido que beneficie a las mujeres, y aprovechando estas actividades para empoderar a las mujeres de la comunidad, también llegamos meses atrás a la decisión de organizar en algún momento un gran mapaton remoto sobre zonas donde las mujeres experimentan un nivel agudo de vulnerabilidad. Las zonas vulnerables en general podían resultar beneficiadas del mapeo y las mujeres de estas zonas recibirían un beneficio aún más grande por efecto de la mejora general de la información, además de impulsar un mapeo paralelo y permanente de equipamientos y puntos de interés considerados de utilidad y de importancia para las mujeres. Esta segunda categoría de datos siendo más difícil de recabar sin un conocimiento fino de la zona, parecía más factible organizar de entrada un mapaton general sobre asentamientos vulnerables.&lt;/p&gt;
  133. &lt;p&gt;Empezamos en el chat LATAM a hablar del aniversario 13 de OpenStreetMap. Varias personas entre quienes Humberto Yances y las mujeres de Geochicas, mencionamos la posibilidad de realizar un mapaton LATAM donde se coordinarían las comunidades de todos los países activos durante el mes de agosto.&lt;/p&gt;
  135. &lt;p&gt;Por la inclinación de algunos participantes de la comunidad hacia la dimensión humanitaria, también preocupados desde México por el gran rezago en el mapa del Sur del territorio, regularmente afectado por cataclismos, coincidimos en impulsar el tema de asentamientos irregulares vulnerables entre otros.&lt;/p&gt;
  137. &lt;p&gt;Humberto Yances tomó un rol propositivo en la metodología y en la coordinación de este mapaton, orientando cada grupo en la recolección de polígonos prioritarios aprovechando enlaces preexistentes con organizaciones especialistas en el continente y en cada país en la vivienda o en zonas vulnerables, como en particular Techo internacional; organizando y guiando a los participantes para la construcción de una serie de Wikis (ver lista abajo) para llevar la operación de manera articulada y con una práctica sistemática de documentación; y tambien capacitándonos en el uso del gestor de tareas o &lt;a href="" rel="nofollow"&gt;tasking manager Colombia&lt;/a&gt; para que cada grupo realizará sus proyectos e impulsará el mapeo en sus comunidades respectivas.&lt;/p&gt;
  139. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  140. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  142. &lt;p&gt;En México utilizamos información de Techo México así como del IMPLAN de Ciudad del Carmen donde @mapeadora tiene un contacto directo y que representa una zona de alta vulnerabilidad a huracanes, con un crecimiento urbano rápido y desorganizado que afecta las zonas naturales de manglares. Para el largo plazo, añadimos otro proyecto con los municipios del país con alto nivel de rezago social a partir de una clasificación de la CONEVAL (Consejo Nacional de Evaluación de la Política de Desarrollo Social) en 2010. @Cuauhtémoc trabajó arduamente en preparar la información y @mapeadora creó y gestiona los &lt;a href=";direction=desc&amp;search=%23Mexico" rel="nofollow"&gt;Tasking Manager&lt;/a&gt;.&lt;/p&gt;
  144. &lt;p&gt;Durante ese mes de agosto los proyectos de todos los países fueron promovidos en las redes y también a través de actividades presenciales de mapeo con estudiantes y otras comunidades.
  145. &lt;a href=";src=typd&amp;lang=es" rel="nofollow"&gt;Hilo en twitter&lt;/a&gt;&lt;/p&gt;
  147. &lt;p&gt;En México iniciamos el mes de agosto con un &lt;a href=";src=typd&amp;lang=es" rel="nofollow"&gt;mapatón en la Universidad Autónoma del Estado de México&lt;/a&gt; con la cual tenemos una colaboración sólida, y logramos así la participación de 90 estudiantes, guiados por @mapanauta y @Beny Carbajal.
  148. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  150. &lt;h2&gt;Resultados&lt;/h2&gt;
  152. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  153. &lt;img src="" alt="Alt text"/&gt;
  154. &lt;a href="" rel="nofollow"&gt;Missingmaps leaderboards&lt;/a&gt;&lt;/p&gt;
  156. &lt;h2&gt;Aprendizajes&lt;/h2&gt;
  158. &lt;ol&gt;
  159. &lt;li&gt;&lt;p&gt;En término de comunidad y de red, el aprendizaje es invaluable. El mapatón representa un proyecto colectivo que fortalece los lazos y es un poderoso vector de transmisión de conocimiento. &lt;/p&gt;&lt;/li&gt;
  160. &lt;li&gt;&lt;p&gt;A nivel de colaboraciones con instituciones de distintos auges: especialistas de la vivienda y zonas vulnerables (escala internacional o nacional); e Institutos Municipales, nos permite entender las necesidades en materia de gestión y aprovechamiento de datos, la urgencia de mejorar la información ya que trata de resiliencia y prevención del desastre, la gran oportunidad para dar asesorías más puntuales y vincular este trabajo de mapeo con acciones reales en zonas de riesgo (caso de la Isla de Carmen). El mapatón es una palanca para colaboraciones más a profundidad, conocimientos puntuales sobre los territorios, y acción.  &lt;/p&gt;&lt;/li&gt;
  161. &lt;li&gt;&lt;p&gt;En cuanto a estrategias de fortalecimiento de comunidad local, la comunidad mexicana no es lo suficientemente numerosa ni unida para lograr una participación significativa a través de un solo llamado abierto. Pese a nuestro deseo de dejar en pausa las actividades de capacitación masivas, fue de esta manera que pudimos obtener una participación relevante, implicando otra dificultad: una necesidad de orientación sostenida.
  162. Las observaciones más comunes son:&lt;/p&gt;&lt;/li&gt;
  163. &lt;/ol&gt;
  165. &lt;ul&gt;
  166. &lt;li&gt;Falta de costumbre en la observación de las fotos, lo cual descarta muchos objetos importantes, como elementos naturales, ríos, etc.&lt;/li&gt;
  167. &lt;li&gt;Una dificultad para mapear correctamente los edificios con una forma ortogonal debido a que se ven sólo parcialmente en la imagen&lt;/li&gt;
  168. &lt;li&gt;Una baja tolerancia hacia la desesperación, al tener que mapear una zona densa en edificios, o al abrir celdas con pocos objetos que mapear.&lt;/li&gt;
  169. &lt;li&gt;Un entendimiento bajo de la necesidad de articular el contenido de las celdas entre sí lo que llevan los estudiantes a utilizar el límite de la celda como límite estricto de los objetos.&lt;/li&gt;
  170. &lt;/ul&gt;
  172. &lt;p&gt;&lt;img src="" alt="Alt text"/&gt;
  173. &lt;img src="" alt="Alt text"/&gt;
  174. &lt;img src="" alt="Alt text"/&gt;
  175. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  177. &lt;p&gt;También encontramos tareas meticulosamente cubiertas:
  178. &lt;img src="" alt="Alt text"/&gt;&lt;/p&gt;
  180. &lt;p&gt;Entendemos que involucrar un gran número de principiantes en una operación tan extensa de mapeo implica un importante trabajo de monitoreo, validación y limpieza de nuestra parte.&lt;/p&gt;
  182. &lt;h2&gt;Esto nos conduce a varias estrategias (agradecemos comentarios)&lt;/h2&gt;
  184. &lt;ul&gt;
  185. &lt;li&gt;La primera sobre sobre el &lt;strong&gt;equilibrio entre cantidad y calidad de objetos&lt;/strong&gt;. En las condiciones actuales de la comunidad mexicana, privilegiar la calidad sobre la cantidad en primera instancia, equivaldría a renunciar a tener progreso en el mapa.&lt;/li&gt;
  186. &lt;li&gt;Si al contrario decidimos involucrar a grandes grupos de principiantes que capacitamos con la esperanza de que formen parte de la comunidad activa de OpenStreetMap, y aceptando el costo de un trabajo importante de monitoreo y corrección por muy pocas personas, nos obliga a &lt;strong&gt;buscar formas de ahorro de tiempo en otras tareas y optimizar nuestros métodos de enseñanza&lt;/strong&gt;.&lt;/li&gt;
  187. &lt;/ul&gt;
  189. &lt;p&gt;Consideramos ahora necesario integrar el mapeo a los programas escolares donde colaboramos de manera contínua, articulado con cursos de herramientas cartográficas y &lt;strong&gt;estableciendo ya no sólo incentivos y valorizaciones pero mecanismos de calificación por parte de la universidad&lt;/strong&gt;.
  190. Estamos ideando un esquema que coordinar con los profesores que han sido líderes de los mapatones en su institución, para pensar en los &lt;strong&gt;mecanismos más funcionales para monitorear las ediciones sobre semestres completos y calificar&lt;/strong&gt; cada mapeador, además de crear un &lt;strong&gt;reconocimiento o diploma validado por OpenStreetMap y los socios de Humanitarian OpenStreetMap Team&lt;/strong&gt;.  El apoyo humanitario tiene el potencial de generar interés en los estudiantes, los cuales, además, fortalecen competencias profesionales al aprender el uso de herramientas, entender y eventualmente analizar bases de datos cartográficos.&lt;/p&gt;
  192. &lt;h2&gt;Ligas de las wikis de coordinación&lt;/h2&gt;
  194. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;
  195. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  196. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  197. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  198. &lt;a href="" rel="nofollow"&gt;;/a&gt;
  199. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  201. &lt;h2&gt;&lt;a href="" rel="nofollow"&gt;Recursos para visualizar cambios durante mapatones presenciales&lt;/a&gt;&lt;/h2&gt;
  203. &lt;h2&gt;&lt;a href=",aniversarioxiii_latam" rel="nofollow"&gt;Herramientas para monitoreo&lt;/a&gt;&lt;/h2&gt;
  204. </description>
  205.      <dc:creator>mapeadora</dc:creator>
  206.      <pubDate>Tue, 22 Aug 2017 02:21:54 +0000</pubDate>
  207.      <comments></comments>
  208.      <geo:lat>19.4039447646156</geo:lat>
  209.      <geo:long>-99.136848449707</geo:long>
  210.      <georss:point>19.4039447646156 -99.136848449707</georss:point>
  211.    </item>
  212.    <item>
  213.      <title>Improving the Kashmir Valley</title>
  214.      <link></link>
  215.      <guid></guid>
  216.      <description>&lt;p&gt;For the last few weeks I&amp;#39;ve been improving the data for the Kashmir Valley. &lt;/p&gt;
  218. &lt;p&gt;Have improved the accuracy of the forested areas, which previously were drawn in very low resolution, and often incorrectly included large parts of non-forested land. I may have included some areas of scrubland within the forested areas, it&amp;#39;s sometimes difficult to differentiate from the imagery.&lt;/p&gt;
  220. &lt;p&gt;Now working on highways.  have been genuinely surprised at just how many highways and tracks there are in the area.&lt;/p&gt;
  221. </description>
  222.      <dc:creator>dmgroom_ct</dc:creator>
  223.      <pubDate>Tue, 22 Aug 2017 02:17:00 +0000</pubDate>
  224.      <comments></comments>
  225.      <geo:lat>34.1278727215934</geo:lat>
  226.      <geo:long>74.6356201171875</geo:long>
  227.      <georss:point>34.1278727215934 74.6356201171875</georss:point>
  228.    </item>
  229.    <item>
  230.      <title>Silueta de la ciudad (relaciones)</title>
  231.      <link></link>
  232.      <guid></guid>
  233.      <description>&lt;p&gt;Hice algunas incorporaciones segun datos de  la DGR (Imagenes y planos, no se ven en Bing y otros servicios de img. al día de hoy) que incluyen calles que salen del area de la ciudad establecida por relaciones.
  234. Tengo que ver, preguntar, estudiar, como modificar las relaciones incluyendo las nuevas manzanas.&lt;/p&gt;
  235. </description>
  236.      <dc:creator>Javier Dieser</dc:creator>
  237.      <pubDate>Mon, 21 Aug 2017 18:14:49 +0000</pubDate>
  238.      <comments></comments>
  239.      <geo:lat>-36.6374366400627</geo:lat>
  240.      <geo:long>-64.2577376961708</geo:long>
  241.      <georss:point>-36.6374366400627 -64.2577376961708</georss:point>
  242.    </item>
  243.    <item>
  244.      <title>OSM go - and stop - what next?</title>
  245.      <link></link>
  246.      <guid></guid>
  247.      <description>&lt;p&gt;&lt;img src="" alt="OSMgo-stop"/&gt;&lt;/p&gt;
  249. &lt;p&gt;The development of OSMgo is on hold, may be forever. It was not intended to go that far anyway. I will do small changes now or then. And “support”: If anyone tells me new bugs or a missing feature, I most probably will get active. If you like to use OSMgo with a liddle help, I would be glad to guide you in multiuser mode. My friend Martin is coding a plane control/simulation. Soon you may fly through the virtual 3D world of OSM with/as a model plane. When the intended 3D model server/repository is online, it will be used by OSMgo to.&lt;/p&gt;
  251. &lt;p&gt;My whole code is a first shot style, really no clean code and not well structured. It has to be redone from the scratch. And in a way it will. But not by me. There is a project slightly relaying on my work. And I will contribute a bit. In that project, the dead ends of OSMgo may be solved, mostly by analysing the solutions of existing code. Mainly OSM2WORD because it is open source and OSMBuildings with an open source client at last. Are there other good sources? Unfortunely the really good solutions are in commercial products like F4. But they will not support a community project, will they? I would like, not only to have correct and complete code, but also a public description of the functions and algorithms. Yes, in the OSM wiki are pages about multipolygons and more. There are other disasters of complexity in OSMgo: rendering roof types and even roof directions, replacing buildings by building parts. The recursive OSM relations are hell. On the other hand, most of this problems are already solved by the 2D renders. And they are open source!&lt;/p&gt;
  253. &lt;p&gt;There are some ugly errors I will not fix. Like my roof typ gabled or the flickering land uses. Some buildings holes or holes in landuses are missing because of an error in ThreeJS. That may be gone in the next version. The frame rate is mostly a mess, mainly because I use ThreeJS. The new project uses Cesium now and so, it will also be limited. But Cesium may partly replace it with “native” code later. A lot of functiionality, like the analysis of OSM tags should not be done by the client but an tile server, a vector tile server of course. There are quite a view such servers already, most of them are commercial. I would be happy, if the OSM community would set up its own independent server and code.&lt;/p&gt;
  255. &lt;p&gt;Creating the Houses of Parliament in London etc. in details with building:parts is artwork of it’s own kind. I am always impressed what some OSM user have done. I started the page &amp;quot;&lt;a href="" rel="nofollow"&gt;”&lt;/a&gt; and almost forgot it. There are much more artful places in OSM. Some can be found in the twitter feed “OSM__go”.
  256. But I think, creating labyrinthine Objekte as &amp;quot;Simple 3D buildings” is only ok ok for really simple buildings. If I see an artful created fountain in Paris, I don’t think, that should be part of the OSM data base. That’s a job for the model server. Building heights or levels are necessary, roof types and colours are fine. But building:parts only intent do create an exact outer view. And they will interfere with indoor mapping! For objects of a certain complexity, they should be “exported” into a file format for 3D editors and the 3D model should be placed in the model server.&lt;/p&gt;
  258. &lt;p&gt;I see OSMgo as a sandbox for experiments. Recently, I added an OBJ file of my favourite space ship Orion (&lt;a href="" rel="nofollow"&gt;;/a&gt;). After “running” around it, I wanted it to fly. That may happen in OSMgo. And it may be my next big project, a &amp;quot;Syfy Space Sip Simulator&amp;quot;. Off-course OSM would be used to show the Earth.  So that would be a union of my long time hobbies: Raumpatrouille/Science Fiction, OSM and gravity simulation. After a start in Javascript I may change to WebAssembly &amp;amp; Apple Swift and may even use the VR-Kit. (Mabbox is showing some experiments with OSM and VR-Kit already.)&lt;/p&gt;
  260. &lt;p&gt;What do you think about this: The OSM community should start an OSM 3D renderer in WebAssembly. Oh, wait a minute! Java can be compiled into WebAssembly. So OSM2WORLD could run as an Web-App. Supported by a good tile server it could make OSM great again (sorry, a spontaneous joke). But not only 3D! A 2D renderer is almost a subset of a 3D one. But in this case, it would be a 2D vector renderer with many advantages. The view of all objects configurable by MapCSS, even the zoom-height it gets lowly visible, or not at all. So you define the content and the layout. We don’t need special maps for horse riding or what ever, but just a new MapCSS. There are many vector renderer already. Except the experiments, sadly they all are commercial. A community 2D(+3D?) vector renderer in WebAssembly could be the future landing page of OSM.&lt;/p&gt;
  262. &lt;p&gt;-karlos-&lt;/p&gt;
  263. </description>
  264.      <dc:creator>-karlos-</dc:creator>
  265.      <pubDate>Mon, 21 Aug 2017 17:44:26 +0000</pubDate>
  266.      <comments></comments>
  267.    </item>
  268.    <item>
  269.      <title>OSM go - und stopp - was nun?</title>
  270.      <link></link>
  271.      <guid></guid>
  272.      <description>&lt;p&gt;&lt;img src="" alt="OSMgo-stop"/&gt;&lt;/p&gt;
  274. &lt;p&gt;Die Entwicklung von OSMgo ist angehalten, vielleicht für immer. Das es so weit geht war garnicht angedacht. Ich werde hi und da kleine Änderungen machen. Und “Support”: Wenn jemand neue Fehler meldet oder Funktionen gewünscht werden, werde ich sehr wascheidlich aktiv werden. Wer beim Benutzen von OSMgo etwas Hilfe möchte, den werde ich mit Freuden im Multiuser-Modus begleiten. Mein Freund Martin schreibt gerade Code für eine Flugzeug-Steuerung/-Simulation. Bald kann man mit einem Modellflugzeug durch die virtuelle 3D Welt von OSM fliegen. Wenn der geplante 3D-Server/Service online ist, wird er auch von OSMgo genutzt.&lt;/p&gt;
  276. &lt;p&gt;Mein ganzer Code ist nur ein erster Versuch, wirklich kein Clean Code und nicht gut strukturieret. Er müßte komplett neu gemacht werden. Und in gewisser Weise wird er das. Es gibt ein Projekt, teils auf meiner Arbeit aufsetzt. In dem Projekt werden die Sackgassen von OSMgo hoffendlich gelöst, meistens, durch Analysen von vorhandenem Code. Hauptsächlich OSM2WORLD weile es open source ist und OSMBuldings mit einem zumindest offenen Client. Gibt es andere gute Quellen? Die wirklich guten Lösungen sind leider in kommerziellen Produkten wie F4. Aber die werden ein Kommunity-Projekt nicht unterstützen, oder? Ich möchte nicht nur korrekten, kompletten Code sondern auch eine öffentliche Beschreibung der Funktionen und Lösungen. Ja, im OSM-Wiki sind Seiten zu Multipolygonen und mehr. Da sind noch andere Katastropen von Komplexität im OSMgo-Code: Rendern von Dachtypen und sogar Dachrichtungen; Gebäude ersetzen durch Gebäudeteile. Die rekursiven Relationen sind die Hölle. Andererseits, die meisten dieser Probleme sind schon von 2D-Renderern gelöst. Und die sind open soruce!&lt;/p&gt;
  278. &lt;p&gt;Einige fiese Fehler werde ich nicht mehr flicken. Wie meinen Dachtyp “gabled” oder das flackern bei Landflächen. Einige Haushöfe oder Lücken in Landflächen fehlen wegen eines Fehlers in ThreeJS. Das könnte in der nächsten Version weg sein. Die Framerate ist meistens schlimm, hauptsächlich, weil ich ThreeJS nutze. Das neue Projekt nutzt Cesium und wird so auch begrenzt sein. Doch Cesium mag später durch nativen Code ersetzt werden. Viele Funktionen, wie die Analyse der OSM-Tags sollten nicht vom Client sondern von einem Server erledigt werden, ein Vektor-Tiel-Server natürlich. Es gibt da schon einige Server, aber meist kommerziell. Ich würde mich freuen, wenn die OSM-Gemeinschaft eigenen Server-Service /- Code erstellt.&lt;/p&gt;
  280. &lt;p&gt;Erstellen der Houses of Parliament in London usw. mit building:parts ist eine eigene Art von Kunst. Ich bin immer beeindruckt, was mansche OSM-User geschafft haben. Ich habe die Seite &amp;quot;&lt;a href="" rel="nofollow"&gt;”&lt;/a&gt; angefangen und dann fast vergessen. Es gibt viele kunstvolle Orte in OSM. Einige kann man im Twitter-Feed “OSM__go”.
  281. Aber ich denke, verwinkelte Objekte sollten nur mit  &amp;quot;Simple 3D buildings” gebaut werden, wenn es wirklich simple Gebäude sind. Wenn ich einen kunstvoll gebauten Brunnen in Paris sehe, denke ich, das sollte nicht Teil der OSM-Daten sein. Das eine Aufgabe für einen Modell-Server. Gebäudehöhen oder Stockwerke sind notwendig, Dachtypen und Farben sind prima. Aber building:parts wollen nur die Aussenansicht von Gebäuden genau darstellen. Und sie beissen sich mit Indoor-Mapping! Objekte mit einer gewissen Komplexität sollten in ein Dateiformat für 3D-Eitoren “exportiert” werden und das 3D-Modell sollte in den Modell-Server gepackt werden.&lt;/p&gt;
  283. &lt;p&gt;ich sene OSMgo als einen Spielplatz für Experimente. Kürzlich habe ich eine OBJ-Datei meines Lieblings-Raumschiffs eingebaut (&lt;a href="" rel="nofollow"&gt;;/a&gt;). Nach einem “Spaziergang” ‘drumherum wollte ich , dass es auch fliegt. Das mache ich vielleicht auch noch in OSMgo. Das könnte aber ich mein nächstes großes Projekt geben, einen &amp;quot;SF Raumschiff-Simulator” Natürlich wird OSM genutzt um die Erde darzustellen. So würde das eine Vereinigung meiner Langzeit-Hobbies: Raumpatrouille/Science Fiction, OSM and Gravitationssimulation. Nach dem Start in Javascript wechsle ich vielleicht zu WebAssembly &amp;amp; Apple-Swift und benutze eventuell sogar VR-Kit. (Mapbox zeigt schon einige Experimente mit OSM und VR-Kit)&lt;/p&gt;
  285. &lt;p&gt;Was denkst du darüber: Die OSM-Gemeinschaft sollte einen SMO 3D renderer in WebAssembly anfangen. Oh, warte mal! Java kann zu WebAssembly übersetzt werden. So kann OSM2WORLD als eine Web-App laufen. Unterstützt von einem Vektor-Tiel-Server könnte das OSM “make great again” (Sorry, ein spontaner Witz). Aber nicht nur für 3D! Ein 2D-Renderer ist fast eine Untermenge von 3D. Auf diese weise würde es ein 2D-Renderer mit vielen Vorteilen: Das Aussehen von allen Objekten konfigurierbar mit MapCSS, sogar die Zoom-Höhe bei der es langsam sichtbar wird, oder auch nie. So bestimmt man den Inhalt und das Aussehen. Wir brauchen keine extra Karten fürs Reiten oder so, nur eine neue MapCSS. Es gibt schon eine menge Vektor-Renderer. Außer den Experimentellen, sind leider alle Kommerziell. Ein 2d(+3D) Vektor-Runderer in WebAssembly der OSM-Gemeinschaft könnte die zukünfige Landingpage von OSM sein.&lt;/p&gt;
  287. &lt;p&gt;-karlos-&lt;/p&gt;
  288. </description>
  289.      <dc:creator>-karlos-</dc:creator>
  290.      <pubDate>Mon, 21 Aug 2017 17:43:27 +0000</pubDate>
  291.      <comments></comments>
  292.    </item>
  293.    <item>
  294.      <title>Ajout des boîtes aux lettres manquantes à l'aide des données de La Poste</title>
  295.      <link></link>
  296.      <guid></guid>
  297.      <description>&lt;p&gt;Bonjour,&lt;/p&gt;
  299. &lt;p&gt;J&amp;#39;ai ajouté sur OSM les boîtes aux lettres non cartographié dans le centre de Metz, je vais décrire rapidement les outils utilisés pour effectuer cette cartographie. (je vais utiliser l&amp;#39;acronyme BAL pour Boîte Aux Lettres)&lt;/p&gt;
  301. &lt;h2&gt;Étape 1 : repérer les boites aux lettres manquantes&lt;/h2&gt;
  303. &lt;p&gt;La Poste fournit des données ouvertes, qui recensent les BAL avec leur adresse, référence. Ces données sont daté de 2015, et le positionnement n&amp;#39;est pas très précis, il faut donc contrôler sur le terrain l&amp;#39;existence des BAL avant de les saisir dans Openstreetmap.&lt;/p&gt;
  305. &lt;p&gt;Le données de La Poste vont être très utile pour voir quelles sont les BAL qui sont listés par la Poste mais qui ne sont pas dans OSM. Pour comparer OSM et les data La Poste j&amp;#39;utilise l&amp;#39;outil qualité &lt;a href="" rel="nofollow"&gt;Osmose&lt;/a&gt;, qui permet l&amp;#39;analyse de l&amp;#39;intégration d&amp;#39;Opendata.
  306. Dans les filtres à gauche je sélectionne les erreurs qui m&amp;#39;intéressent (&amp;quot;boîtes aux lettres&amp;quot; et &amp;quot;boîtes aux lettres à intégrer&amp;quot;), et j&amp;#39;obtiens les BAL à vérifier sur le terrain :
  307. &lt;img src="" alt=""/&gt;
  308. Ensuite Osmose permet d&amp;#39;exporter les erreurs, j&amp;#39;exporte dans un format gpx afin de l&amp;#39;enregistrer sur mon smartphone.
  309. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  311. &lt;h2&gt;Étape 2 : vérifier les données sur le terrain&lt;/h2&gt;
  313. &lt;p&gt;Ici j&amp;#39;utilise l&amp;#39;app OSMand, car c&amp;#39;est celle que j&amp;#39;utilise habituellement. J&amp;#39;importe le gpx, et j&amp;#39;affiche maintenant les point à vérifier.
  314. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  316. &lt;p&gt;Une fois sur place, 2 possibilités :&lt;/p&gt;
  318. &lt;ul&gt;
  319. &lt;li&gt;Utiliser le greffon OSMand &amp;quot;Contribuer à OSM&amp;quot; afin d&amp;#39;ajouter directement la BAL avec sa référence, depuis l&amp;#39;application.&lt;/li&gt;
  320. &lt;li&gt;Prendre une photo/note de la BAL afin de relever l&amp;#39;emplacement exacte et la référence et ajouter ces données ensuite sur OSM depuis un ordinateur.&lt;/li&gt;
  321. &lt;/ul&gt;
  323. &lt;p&gt;Pour chaque BAL j&amp;#39;ai ajouté, la référence, l&amp;#39;heure limite de collecte et le type, voir l&amp;#39;exemple ici :
  324. &lt;a href="" rel="nofollow"&gt;exemple node&lt;/a&gt;&lt;/p&gt;
  326. &lt;h2&gt;Conclusion :&lt;/h2&gt;
  328. &lt;p&gt;Et voilà la méthode que j&amp;#39;ai suivi afin d&amp;#39;ajouter les BAL manquantes dans ma ville, C&amp;#39;est fait sans prétention et en m&amp;#39;appuyant sur des outils et données existantes, vos remarques et commentaires sont les bienvenues :D&lt;/p&gt;
  330. &lt;p&gt;Note : j&amp;#39;ai cherché, un outil libre qui permet de définir un itinéraire qui relierai plusieurs points GPX de la façon la plus courte possible, mais sans succès..&lt;/p&gt;
  331. </description>
  332.      <dc:creator>Kazing</dc:creator>
  333.      <pubDate>Mon, 21 Aug 2017 16:00:21 +0000</pubDate>
  334.      <comments></comments>
  335.      <geo:lat>49.1154991144526</geo:lat>
  336.      <geo:long>6.17400527000427</geo:long>
  337.      <georss:point>49.1154991144526 6.17400527000427</georss:point>
  338.    </item>
  339.    <item>
  340.      <title>Rho Ciclostazione Piazza Della Libertà</title>
  341.      <link></link>
  342.      <guid></guid>
  343.      <description>&lt;p&gt;Per il progetto città di Rho ciclabile è stata aggiunta la Ciclostazione di Piazza della Libertà davanti alla stazione ferroviaria. La ciclostazione è recintata e custodita e rappresenta un elemento fondamentale della mobilità sostenibile all&amp;#39;interno della città.&lt;/p&gt;
  345. &lt;p&gt;Nella descrizione dell&amp;#39;elemento viene anche indicata la &lt;a href="" rel="nofollow"&gt;Cooperativa Sociale La Musa&lt;/a&gt; come gestore dell&amp;#39;impianto.&lt;/p&gt;
  346. </description>
  347.      <dc:creator>fra_miglietta</dc:creator>
  348.      <pubDate>Mon, 21 Aug 2017 12:22:18 +0000</pubDate>
  349.      <comments></comments>
  350.      <geo:lat>45.5243339573901</geo:lat>
  351.      <geo:long>9.04278874397278</geo:long>
  352.      <georss:point>45.5243339573901 9.04278874397278</georss:point>
  353.    </item>
  354.    <item>
  355.      <title>Rho Ciclabile Via Pregnana</title>
  356.      <link></link>
  357.      <guid></guid>
  358.      <description>&lt;p&gt;Per il progetto città di Rho ciclabile è stata aggiunta la pista ciclabile di Via Pregnana che va dall&amp;#39;incrocio con Via Mattei all&amp;#39;incrocio con Via Virgilio. Sono stati anche aggiunti gli attraversamenti ciclabili lungo tutto il tragitto.&lt;/p&gt;
  360. &lt;p&gt;Sono state anche apportate migliorie alla descrizione della pista ciclabile di Via Mattei essendo questa collegata a quella di Via Pregnana.&lt;/p&gt;
  361. </description>
  362.      <dc:creator>fra_miglietta</dc:creator>
  363.      <pubDate>Mon, 21 Aug 2017 12:12:15 +0000</pubDate>
  364.      <comments></comments>
  365.      <geo:lat>45.5243858225953</geo:lat>
  366.      <geo:long>9.0281867980957</geo:long>
  367.      <georss:point>45.5243858225953 9.0281867980957</georss:point>
  368.    </item>
  369.    <item>
  370.      <title>Wprowadzenie pierwszych obiektów na mapie OSM</title>
  371.      <link></link>
  372.      <guid></guid>
  373.      <description>&lt;ol&gt;
  374. &lt;li&gt;Pojemnik na odzież PCK.&lt;/li&gt;
  375. &lt;li&gt;Fryzjer w przejściu przy sklepie &amp;quot;Artus&amp;quot;.&lt;/li&gt;
  376. &lt;/ol&gt;
  377. </description>
  378.      <dc:creator>sloxn</dc:creator>
  379.      <pubDate>Mon, 21 Aug 2017 11:56:39 +0000</pubDate>
  380.      <comments></comments>
  381.    </item>
  382.    <item>
  383.      <title>Правки, правки</title>
  384.      <link></link>
  385.      <guid></guid>
  386.      <description>&lt;p&gt;Как то даже не заметил как проскочил юбилейный рубеж в 500 правок :)&lt;/p&gt;
  387. </description>
  388.      <dc:creator>dansit</dc:creator>
  389.      <pubDate>Sun, 20 Aug 2017 15:18:53 +0000</pubDate>
  390.      <comments></comments>
  391.    </item>
  392.    <item>
  393.      <title>Bringázásra</title>
  394.      <link></link>
  395.      <guid></guid>
  396.      <description>&lt;p&gt;Bringázásra
  397. Tárnok Százhalombatta benta patak part
  398. Jó időbe kiváló &lt;/p&gt;
  399. </description>
  400.      <dc:creator>Sztankó Attila</dc:creator>
  401.      <pubDate>Sun, 20 Aug 2017 08:52:05 +0000</pubDate>
  402.      <comments></comments>
  403.      <geo:lat>47.3510777495738</geo:lat>
  404.      <geo:long>18.8806106770062</geo:long>
  405.      <georss:point>47.3510777495738 18.8806106770062</georss:point>
  406.    </item>
  407.    <item>
  408.      <title>凄い</title>
  409.      <link></link>
  410.      <guid></guid>
  411.      <description>&lt;p&gt;Wikipediaよりも詳しく出ているので驚きました。&lt;/p&gt;
  412. </description>
  413.      <dc:creator>猫のチャチャ</dc:creator>
  414.      <pubDate>Sun, 20 Aug 2017 08:34:49 +0000</pubDate>
  415.      <comments></comments>
  416.    </item>
  417.    <item>
  418.      <title>Mistakes &amp; Regrets I've Made Editing OpenStreetMap</title>
  419.      <link></link>
  420.      <guid></guid>
  421.      <description>&lt;ol&gt;
  422. &lt;li&gt;Armchair Mapping Mistakes&lt;/li&gt;
  423. &lt;/ol&gt;
  425. &lt;ul&gt;
  426. &lt;li&gt;&lt;p&gt;Going to a place to survey it, returning home to mark it on OpenStreetMap, and then saying it was an armchair edit since I wasn&amp;#39;t actually at the location when I uploaded my changes.&lt;/p&gt;&lt;/li&gt;
  427. &lt;li&gt;&lt;p&gt;Assuming that just because something was there in my childhood, that it still would be there and unchanged.&lt;/p&gt;&lt;/li&gt;
  428. &lt;li&gt;&lt;p&gt;Trusting satellite imagery more then my own eyes.&lt;/p&gt;&lt;/li&gt;
  429. &lt;li&gt;&lt;p&gt;Not correcting misaligned satellite imagery with GPS traces.&lt;/p&gt;&lt;/li&gt;
  430. &lt;/ul&gt;
  432. &lt;ol&gt;
  433. &lt;li&gt;Surveying Mistakes&lt;/li&gt;
  434. &lt;/ol&gt;
  436. &lt;ul&gt;
  437. &lt;li&gt;&lt;p&gt;Taking photos in public places like Main Street. It&amp;#39;s better to be discrete and take photos from behind a car window then risk aggravating rural locals.&lt;/p&gt;&lt;/li&gt;
  438. &lt;li&gt;&lt;p&gt;Trusting a wonky smartphone satnav and compass when using Mapillary. Openstreetcam handles the wonky satnav part really well, but it&amp;#39;s even worse with the compass since you can&amp;#39;t currently correct it manually after uploading like in Mapillary.&lt;/p&gt;&lt;/li&gt;
  439. &lt;li&gt;&lt;p&gt;Using OpenSTREETcam on a footpath.&lt;/p&gt;&lt;/li&gt;
  440. &lt;li&gt;&lt;p&gt;Not uploading high quality 360&amp;#39;s to Mapillary when possible and instead focusing on low quality 2D images.&lt;/p&gt;&lt;/li&gt;
  441. &lt;li&gt;&lt;p&gt;Not using Mapillary or OpenStreetCam at all when there was no coverage in my area.&lt;/p&gt;&lt;/li&gt;
  442. &lt;li&gt;&lt;p&gt;Not annotating as I mapped of areas with really outdated satellite imagery.&lt;/p&gt;&lt;/li&gt;
  443. &lt;li&gt;&lt;p&gt;Surveying without a full charge on my devices.&lt;/p&gt;&lt;/li&gt;
  444. &lt;li&gt;&lt;p&gt;Using a standard lens instead of a wide angle one.&lt;/p&gt;&lt;/li&gt;
  445. &lt;/ul&gt;
  447. &lt;ol&gt;
  448. &lt;li&gt;Community Mistakes&lt;/li&gt;
  449. &lt;/ol&gt;
  451. &lt;ul&gt;
  452. &lt;li&gt;&lt;p&gt;Not taking advantage of my surveys to also improve Wikipedia, Wikidata, and Wikivoyage.&lt;/p&gt;&lt;/li&gt;
  453. &lt;li&gt;&lt;p&gt;Not editing the OpenStreetMap wiki to help other mappers.&lt;/p&gt;&lt;/li&gt;
  454. &lt;li&gt;&lt;p&gt;Trying to do things alone.&lt;/p&gt;&lt;/li&gt;
  455. &lt;/ul&gt;
  456. </description>
  457.      <dc:creator>Johnny Mapperseed</dc:creator>
  458.      <pubDate>Sat, 19 Aug 2017 18:58:35 +0000</pubDate>
  459.      <comments></comments>
  460.      <geo:lat>41.3748763714283</geo:lat>
  461.      <geo:long>-83.6505460739136</geo:long>
  462.      <georss:point>41.3748763714283 -83.6505460739136</georss:point>
  463.    </item>
  464.    <item>
  465.      <title>multilingual names in Canada</title>
  466.      <link></link>
  467.      <guid></guid>
  468.      <description>&lt;p&gt;Something in the weekly newsletter caught my eye:&lt;/p&gt;
  470. &lt;blockquote&gt;
  471. &lt;p&gt;Miguel Sevilla Callejo (msevilla00) from Zaragoza, Spain, is currently in Wales. He noticed an inconsistent use of English and Welsh in OpenStreetMap. His email resulted in a readable, long-lasting and controversial discussion on the Talk-GB mailing list (threads in July and August) and comments in an OSM changeset. Nearly the same problem in Switzerland – read the following article. 😉&lt;/p&gt;
  473. &lt;p&gt;— &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  475. &lt;p&gt;Miguel Sevilla Callejo (msevilla00) de Saragosse, en Espagne, est actuellement au pays de Galles. Il remarque une utilisation pas toujours cohérente de l’anglais et du gallois dans OpenStreetMap. Son courriel a donné lieu à une longue et controversée discussion sur la liste Talk-GB (juillet et août) et des commentaires dans un changeset OSM. Presque le même problème en Suisse – Lisez l’article suivant. 😉&lt;/p&gt;
  477. &lt;p&gt;— &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  478. &lt;/blockquote&gt;
  480. &lt;p&gt;So I went to the “Multilingual names” page &lt;a href="" rel="nofollow"&gt;;/a&gt; and found Canada conspicuously absent. Is this because:&lt;/p&gt;
  482. &lt;ol&gt;
  483. &lt;li&gt;we&amp;#39;re already doing it perfectly in Canada; or&lt;/li&gt;
  484. &lt;li&gt;local mappers already know what they&amp;#39;re doing (an argument that seemed to be dismissed in the original discussion about Wales); or&lt;/li&gt;
  485. &lt;li&gt;&lt;em&gt;nope nope nope not touching that with a rad-hardened barge pole&lt;/em&gt;?&lt;/li&gt;
  486. &lt;/ol&gt;
  487. </description>
  488.      <dc:creator>scruss</dc:creator>
  489.      <pubDate>Sat, 19 Aug 2017 18:01:24 +0000</pubDate>
  490.      <comments></comments>
  491.    </item>
  492.    <item>
  493.      <title>Val Di Mello</title>
  494.      <link></link>
  495.      <guid></guid>
  496.      <description>&lt;p&gt;Io, Tania, Fabio e Vale&lt;/p&gt;
  497. </description>
  498.      <dc:creator>Fabrizio Fillo</dc:creator>
  499.      <pubDate>Sat, 19 Aug 2017 12:30:47 +0000</pubDate>
  500.      <comments></comments>
  501.      <geo:lat>46.2608997357166</geo:lat>
  502.      <geo:long>9.67303276062012</geo:long>
  503.      <georss:point>46.2608997357166 9.67303276062012</georss:point>
  504.    </item>
  505.    <item>
  506.      <title>「ロードバイク動画にGPSログを簡単合成! GPX Playerの使い方からOSM編集まで」動画公開</title>
  507.      <link></link>
  508.      <guid></guid>
  509.      <description>&lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  511. &lt;p&gt;GPX Playerとは、動画とGPSログを見やすく再生するソフトです
  512. 前半ではGPX Playerの使用方法を
  513. 後半ではGPX Playerを使ったOSMの編集を説明します。&lt;/p&gt;
  514. </description>
  515.      <dc:creator>roguish</dc:creator>
  516.      <pubDate>Fri, 18 Aug 2017 21:42:39 +0000</pubDate>
  517.      <comments></comments>
  518.    </item>
  519.    <item>
  520.      <title>Imports</title>
  521.      <link></link>
  522.      <guid></guid>
  523.      <description>&lt;p&gt;I recently received notice that a changeset I had made had been reverted due to not following the protocols in place for importing data.  First the facts of the matter.  My family was going to vacation at Folly Beach in South Carolina and I thought it an excellent opportunity to do some mapping while in the area to verify local businesses and add information about them to the map.  When viewing the area in OSM I saw that only a few buildings had been mapped and that the majority of POIs were nodes.  I decided that I would see if I could find a building footprint file already created from the county so that I could add the buildings to the map and then replace the node information with tags connected to the structures where a single occupant resided within the buildings.  I find this to be cleaner when it is able to be done rather than have closed ways and nodes trying to describe the very same thing.  Now I will admit that I had some confusion and very much a lack of knowledge of what constituted an import and the process that was in place to regulate them.  I found a file with the county for building footprints, exported the buildings for Folly Beach using Qgis, cleaned up the attribute data so that when bringing them into JOSM they would have the tag building = yes and proceeded to copy them into the main layer.  After this was done I scoured the area for duplicates and resolved any there were, removed nodes that had POI information and instead attributed that information the the closed ways, and used the error checker to insure that I had not introduced any errors.  I believe it was necessary to move some roads that ran through buildings due to geographical error but other than that it was nearly a blank canvas.  I posted the changeset and readied myself for my vacation.&lt;br/&gt;
  524. On arrival and with the mind to do some mapping in the wild I loaded up Vespucci and began downloading the data so that I could get to it.  I was amazed to find that the buildings I had placed and properly attributed had been removed.  When I arrived back at home I checked my email and found that a user had redacted my changes and rolled everything back to as it was before I began editing, citing a lack of a wiki page or discussion within the import mailing list.  I searched out the import page to see if I had been in violation and it would seem that I had been.  Mea culpa, mea culpa.  &lt;/p&gt;
  526. &lt;p&gt;Now based on the directions at the import site I can see that if a group was to be doing very large and numerous imports the instructions make complete sense, especially in regards to large geographic areas.  The need to insure that data is duplicated or error is introduced has been addressed and I see that there were lessons learned the hard way.  Based on the instructions included it seems that the idea is about very large imports along a county, province, state, country, or large city where the potential for error is far greater and much data may already exist.  Folly Beach is, according to Wikipedia, 18.9 square miles, the data that existed were a few nodes, the beaches, the wetlands, the roads, and a couple of buildings.  The chances of error were minuscule and the import, which I acknowledge failed the guidelines, was checked over for error.  My problem is that the wholesale redaction of the changeset did not actually look at whether there was an improvement to the map (I believe throughout the OSM community it is generally found desirable to have buildings represented) nor if any error had been introduced.  It would seem rather that a prominent individual within the community has created an account that is solely dedicated to a vigilante style role of cleaning up what he describes as vandalism and what he deems to be bad imports and mechanical edits.  Now while this role may be a valid and needed one I do find it intriguing that while there is so much oversight in the import process, one individual can decide for himself without discussion or debate that a changeset is either vandalism or an illegal import or is damaging to the map.  Be that as it may I submit myself to that editing as I had seemed to violate the protocols in place.&lt;/p&gt;
  528. &lt;p&gt;As to the protocols themselves I find that while it does seem to make sense to prevent error or duplication, it has a chilling effect on mappers and on entities that may wish to upload their data to map.  In the United States there are 50 states, 3,007 counties, and 19,354 incorporated places that are, for the most part, independent of one another.  This also does not take into account that each of these entities would have multiple commissions or departments that could have interest in uploading data to the map.  What the import guidelines would mean for these groups, should they wish to share data with the map, is that they would each create a wiki page for each import they wish to do, they each create an account specific for the import, and that they would submit their import to a mailing list for approval.  Having worked in the public sector for small government I can verify that the majority would not want to go through this hassle every single time they wished to share data with the community at large, nor would they have the time at their disposal to do such.  This leads to less adoption of the map and a loss of great data for the map.  The question would be what to do about this.&lt;/p&gt;
  530. &lt;p&gt;We could hope that the many different entities would work in cooperation to limit the amount of import wikis and requests by combining their efforts or even forming a committee to combine their efforts thus making the requests less numerous (presupposing mass adoption of the map).  This could happen and it would be great, but I do not see it in the near future as many have no idea about the map or about contributing to it.  The second proposal that I would humbly submit is this, allow a trusted partner status to communities and groups much in the same way that Google has done with their map.  Communities have a great desire to see their communities represented accurately in online maps.  In two of the local governments I worked for we had this partnership with Google, which did not exclude us from scrutiny but rather gave us the benefit of the doubt that we knew what we were talking about.  With this process an entity would need only submit once for the right to import, committees that accept the applications can make a stress of what imports are allowed and the requirements the group must follow, verify that the group is legitimate, and then approve them to maintain their AOI on the map.  I think this process could lead to greater adoption and more accuracy for the map in the long run.&lt;/p&gt;
  532. &lt;p&gt;Whatever may be decided on the future of imports I still acknowledge my error and humbly offer my apologies for breaking protocol in my efforts to strive for the bettering of the map.&lt;/p&gt;
  533. </description>
  534.      <dc:creator>TheDude05</dc:creator>
  535.      <pubDate>Fri, 18 Aug 2017 20:57:56 +0000</pubDate>
  536.      <comments></comments>
  537.      <geo:lat>32.6552742843399</geo:lat>
  538.      <geo:long>-79.9435615539551</geo:long>
  539.      <georss:point>32.6552742843399 -79.9435615539551</georss:point>
  540.    </item>
  541.    <item>
  542.      <title>Scientific articles about OSM</title>
  543.      <link></link>
  544.      <guid></guid>
  545.      <description>&lt;p&gt;Here&amp;#39;s my list of some scientific articles on OSM that I might read once retired:&lt;/p&gt;
  547. &lt;ul&gt;
  548. &lt;li&gt;&lt;p&gt;Neis, P., &amp;amp; Zipf, A. (2012). Analyzing the contributor activity of a volunteered geographic information project—The case of OpenStreetMap. ISPRS International Journal of Geo-Information, 1(2), 146-165.&lt;/p&gt;&lt;/li&gt;
  549. &lt;li&gt;&lt;p&gt;Neis, P., &amp;amp; Zielstra, D. (2014). Recent developments and future trends in volunteered geographic information research: The case of OpenStreetMap. Future Internet, 6(1), 76-106.&lt;/p&gt;&lt;/li&gt;
  550. &lt;li&gt;&lt;p&gt;Senaratne, H., Mobasheri, A., Ali, A. L., Capineri, C., &amp;amp; Haklay, M. (2017). A review of volunteered geographic information quality assessment methods. International Journal of Geographical Information Science, 31(1), 139-167.&lt;/p&gt;&lt;/li&gt;
  551. &lt;li&gt;&lt;p&gt;Barrington-Leigh, C., &amp;amp; Millard-Ball, A. (2017). The world’s user-generated road map is more than 80% complete. PloS one, 12(8), e0180698.&lt;/p&gt;&lt;/li&gt;
  552. &lt;/ul&gt;
  553. </description>
  554.      <dc:creator>juminet</dc:creator>
  555.      <pubDate>Fri, 18 Aug 2017 08:41:56 +0000</pubDate>
  556.      <comments></comments>
  557.    </item>
  558.  </channel>
  559. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda