[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>Bibliobús Municipal de Málaga</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;He terminado de mapear las &lt;a href=";oldid=1535451#Bibliotecas_municipales" rel="nofollow"&gt;bibliotecas municipales de Málaga&lt;/a&gt;, ya están todas en el mapa. Todavía se pueden mejorar ampliando su etiquetado y retocando algunos detalles, pero ya se pueden encontrar sin más que buscarlas por su nombre. También he mapeado las paradas del &lt;a href="" rel="nofollow"&gt;Bibliobús Municipal&lt;/a&gt;, nuestra biblioteca pública itinerante.&lt;/p&gt;
  20. &lt;p&gt;Si tenéis bibliobuses en vuestras ciudades, os animaría a mapearlos. Suelen dar servicio a nucleos poblacionales aislados alejados del centro de las ciudades y que no disponen de bibliotecas. Para muchas personas, especialmente jóvenes y personas mayores, supone un servicio público esencial.&lt;/p&gt;
  22. &lt;p&gt;Hace tiempo tuvimos una &lt;a href="" rel="nofollow"&gt;discusión&lt;/a&gt; en la lista de correo de &lt;a href="" rel="nofollow"&gt;OSM España&lt;/a&gt; sobre la forma más adecuada de mapear los bibliobuses. Finalmente he optado por crear una relación tipo «route» y no usar la etiqueta «&lt;a href="" rel="nofollow"&gt;highway=bus_stop&lt;/a&gt;». Los puntos de parada los he etiquetado simplemente con sus nombres, sus horarios y una breve descripción. La información común a todas las paradas la he etiquetado en la relación tipo «route» que define al &lt;a href="" rel="nofollow"&gt;bibliobús&lt;/a&gt;.&lt;/p&gt;
  24. &lt;p&gt;Lo más engorroso ha sido tener que poner los horarios en todas y cada una de las paradas. En algunos sitios, el bibliobús pasa semanalmente, en otros quincenalmente, con horarios distintos en verano que durante el resto del año. Por lo demás, mapear un bibliobús es muy sencillo.&lt;/p&gt;
  26. &lt;p&gt;Existe una etiqueta que se puede usar para evitar tener que poner los horarios uno por uno, «&lt;a href="" rel="nofollow"&gt;opening_hours&lt;/a&gt;:url=*», enlazando con una página web externa donde se puedan consultar en línea. Como solución provisional, no me parece mal. Sin embargo, siempre que podáis, os recomiendo que los agregéis manualmente para tenerlos en nuestra propia base de datos OSM.&lt;/p&gt;
  27. </description>
  28.      <dc:creator>dcapillae</dc:creator>
  29.      <pubDate>Wed, 13 Dec 2017 21:53:40 +0000</pubDate>
  30.      <comments></comments>
  31.      <geo:lat>36.7213</geo:lat>
  32.      <geo:long>-4.4217</geo:long>
  33.      <georss:point>36.7213 -4.4217</georss:point>
  34.    </item>
  35.    <item>
  36.      <title>Málaga cultural</title>
  37.      <link></link>
  38.      <guid></guid>
  39.      <description>&lt;p&gt;He empezado a mapear la red de bibliotecas públicas de Málaga, algo que me propuse hace tiempo, aunque no le había prestado atención hasta ahora. De hecho, pensando más en general, me he propuesto mejorar el mapeado cultural de la ciudad.&lt;/p&gt;
  41. &lt;p&gt;Si estáis interesados en temas culturales de Málaga y queréis colaborar, echadle un vistazo a la &lt;a href="" rel="nofollow"&gt;página temática&lt;/a&gt; que he creado en el wiki. Intentaremos coordinarnos para mejorar el mapa en todo lo relativo a &lt;a href="" rel="nofollow"&gt;características&lt;/a&gt; culturales: bibliotecas, museos, centros culturales o de arte, patrimonio histórico y cultural, etc.&lt;/p&gt;
  43. &lt;p&gt;Si logramos poblar el mapa con todas sus características culturales, demostraremos que Málaga es una ciudad culturalmente rica, y evitaremos que se repita aquello que se decía antiguamente: «&lt;a href="" rel="nofollow"&gt;Málaga, ciudad de mil tabernas y una sola librería&lt;/a&gt;».&lt;/p&gt;
  44. </description>
  45.      <dc:creator>dcapillae</dc:creator>
  46.      <pubDate>Wed, 13 Dec 2017 15:29:20 +0000</pubDate>
  47.      <comments></comments>
  48.      <geo:lat>36.7213</geo:lat>
  49.      <geo:long>-4.4217</geo:long>
  50.      <georss:point>36.7213 -4.4217</georss:point>
  51.    </item>
  52.    <item>
  53.      <title>Mapping party at Wayanad</title>
  54.      <link></link>
  55.      <guid></guid>
  56.      <description>&lt;p&gt;This is the first time I went on a mapping party and that too to Wayanad. I didn&amp;#39;t know much before about what a mapping party is, but I looked up on the internet and realized that we will be learning how to map areas on Openstreetmap and will meet the community and the people contributing to it. Actually if any type of event is happening in Wayanad, you can be assured that you will have a good time. Its such a beautiful place, you cannot miss the chance to at least see it once :)&lt;/p&gt;
  58. &lt;p&gt;I asked &lt;a href="" rel="nofollow"&gt;Praveen&lt;/a&gt; sir about how to reach there and we decided to go from KSRTC bus stand from Calicut. The journey from Calicut to sulthan bathery was just mesmerizing, I witnessed the beautiful sunset in the hills from the bus. I was just hoping that the bus get some malfunction and stop there so that I can look at it for a little longer. And you can even see pineapple farms there, they were just beautiful. There were even people selling pineapples on the road sides. I wonder how fresh the pineapples were, its like you can ask them to pluck a fresh pineapple for you!&lt;/p&gt;
  60. &lt;p&gt;Also being an open source software user and supporter, to discuss what all is happening in the world is just awesome, It was like feeding your soul. And since we are talking about feeding, the food there has just another level of awesomeness. At first I was reluctant to try the food as I wasn&amp;#39;t sure what it is made up of. Then I tried puttu, and it had no taste, and then they told me that the taste of that depends on the curry. So you better have a good curry!! Puttu mixed with curry tastes delicious, it&amp;#39;s just that I wasn&amp;#39;t able to find the right curry :) A tomato curry would have been the one, I will try that next time.
  61. If you are a dosa fan but not much of a fan of potato, then let me tell, there is a thing called &amp;quot;ghee roast dosa&amp;quot;, you should definitely try that and even better is appam. The only thing that I didn&amp;#39;t try was idiyappam and I still think that I should have tried that. I missed the opportunity :)&lt;/p&gt;
  63. &lt;p&gt;The discussion on the dining table was about all the things going on in the technology world, I was happy that I wasn&amp;#39;t the only one reading about those things. We talked about all the cryptocurrencies, payment gateway of telegram, then out of nowhere elon musk came in (Boring company, tesla and spacex), and then the MINIX OS. Then sombody probably &lt;a href="" rel="nofollow"&gt;Joice&lt;/a&gt; mentioned Abish Mathew, and NOBODY knew who he was and  there ended one branch of the conversation :). Apparantely elon musk is more of a concern than Abish :)&lt;/p&gt;
  65. &lt;p&gt;Apart from that we mapped many parts of the sulthan bathery town. We got divided in a group of two each and started mapping on our own. The best thing about mapping is that you will know each and every path you mapped (Try creating a mind castle out of that !), next time when you go there. The first application that &lt;a href="" rel="nofollow"&gt;Sruthi&lt;/a&gt; mam suggested was Vespucci. It&amp;#39;s a nice application and it reduces your work a lot, you can directly upload the data as you map. The first day I mapped with Vespucci only. Later in the evening I realised that &lt;a href="" rel="nofollow"&gt;Kannan&lt;/a&gt; and &lt;a href="" rel="nofollow"&gt;Ambadi&lt;/a&gt; were mapping with OSMTracker and the cool thing about that is you can actually see the trail that you went through on the map. I liked OSMTracker and the next day I used that only. We specifically went through some of the less travelled paths and as &lt;a href="" rel="nofollow"&gt;Kannan&lt;/a&gt; told me, we were able to create new paths on the map. Although that path won&amp;#39;t be named after us but still good to know that we added it on the map and that information might help someone some day. &lt;/p&gt;
  67. &lt;p&gt;Just to &lt;code&gt;travel the paths less travelled&lt;/code&gt; we went through the roads in the fields and there I realised that kerala fields are very diverse, you can literally grow anything here let it be banana, coconuts, pineapples, coffee, tea and lot of other things that even &lt;a href="" rel="nofollow"&gt;Kannan&lt;/a&gt; didn&amp;#39;t know the names of and mind you that &lt;a href="" rel="nofollow"&gt;Kannan&lt;/a&gt; is from kerala :)
  68. The next day was to say goodbye to all, we went on our separate ways, and even on our way back we visted Pookode Lake. Although it is a great place but we found the parking the &amp;quot;Hard way&amp;quot; :) And probably somebody would have mapped it now (&lt;a href="" rel="nofollow"&gt;Ambadi&lt;/a&gt;?), so you won&amp;#39;t have any problem finding it.&lt;/p&gt;
  70. &lt;p&gt;And now whenever I am bored I start OSMTracker and just go by some weird routes and map it and share it with my friends so that they can also try that route :)
  71. Waiting for the next meetup :)&lt;/p&gt;
  72. </description>
  73.      <dc:creator>Hemantcompiler</dc:creator>
  74.      <pubDate>Wed, 13 Dec 2017 14:02:41 +0000</pubDate>
  75.      <comments></comments>
  76.      <geo:lat>11.6642359737643</geo:lat>
  77.      <geo:long>76.262589097023</geo:long>
  78.      <georss:point>11.6642359737643 76.262589097023</georss:point>
  79.    </item>
  80.    <item>
  81.      <title>Could you classify Landuse correctly? Do it</title>
  82.      <link></link>
  83.      <guid></guid>
  84.      <description>&lt;p&gt;Dear All,&lt;/p&gt;
  86. &lt;p&gt;I have to apologize for that the study link was broken for couple of days. Bugs are already fixed and the study is work well waiting for your contributions.
  87. Please, use study &lt;a href="" rel="nofollow"&gt;;/a&gt; to help science. Our research focuses on YOU (OSM users) and contributors.
  88. &lt;img src="" alt=""/&gt;
  89. Participate in the study &lt;a href="" rel="nofollow"&gt;;/a&gt; to see how perfect you are in recognizing landuse areas.&lt;/p&gt;
  90. </description>
  91.      <dc:creator>grass_and_green</dc:creator>
  92.      <pubDate>Wed, 13 Dec 2017 10:27:30 +0000</pubDate>
  93.      <comments></comments>
  94.    </item>
  95.    <item>
  96.      <title>Neuer Eintrag auf OSM (review requested)</title>
  97.      <link></link>
  98.      <guid></guid>
  99.      <description>&lt;p&gt;Also mir war nicht klar, dass in OSM ein neuer Eintrag doch etwas Zeit in Anspruch nimmt.
  100. Zur Qualitätssicherung habe ich bei meinem neuen Eintrag die Option  &amp;quot;review requested&amp;quot; gesetzt und nun findet sich anscheinend kein Reviewer für den &lt;a href="" rel="nofollow"&gt;Änderungssatz: 54273048&lt;/a&gt;&lt;/p&gt;
  102. &lt;p&gt;Bin gespannt, wie lange sich das hinzieht.... &lt;/p&gt;
  104. &lt;hr/&gt;
  106. &lt;p&gt;Ein &lt;a href="" rel="nofollow"&gt;Blogeintrag&lt;/a&gt; gibt den Hinweis auf das neue Feature. &lt;/p&gt;
  108. &lt;p&gt;Ich werden mir wohl auch mal Zeit nehmen andere &amp;#39;reviews&amp;#39; zu bearbeiten.&lt;/p&gt;
  109. </description>
  110.      <dc:creator>oltoX</dc:creator>
  111.      <pubDate>Tue, 12 Dec 2017 10:39:47 +0000</pubDate>
  112.      <comments></comments>
  113.      <geo:lat>52.5185328978323</geo:lat>
  114.      <geo:long>13.4465789794922</geo:long>
  115.      <georss:point>52.5185328978323 13.4465789794922</georss:point>
  116.    </item>
  117.    <item>
  118.      <title>Juntas de Distrito del Ayuntamiento de Málaga</title>
  119.      <link></link>
  120.      <guid></guid>
  121.      <description>&lt;p&gt;He añadido al mapa la ubicación de todas las &lt;a href=";oldid=1534130#Juntas_Municipales_de_Distrito" rel="nofollow"&gt;Juntas Municipales de Distrito&lt;/a&gt; de Málaga. Ya se pueden buscar directamente desde &lt;a href="" rel="nofollow"&gt;sitio web principal&lt;/a&gt; de OpenStreetMap, sin más que teclear «Junta de Distrito», el nombre del distrito correspondiente y agregando «Málaga», para especificar el municipio.&lt;/p&gt;
  123. &lt;p&gt;En Málaga tenemos once Juntas de Distrito, una por cada distrito municipal. Las Juntas Municipales de Distrito tienen como función principal fomentar y velar por la participación ciudadana, aunque también funcionan como unidades administrativas. En ellas se encuentran la Oficinas Municipales de Atención a la Ciudadanía (OMAC), que son el punto de contacto más directo entre el ciudadano y la administración local. En estas oficinas, por ejemplo, es donde se solicitan los certificados de empadronamiento, entre otros muchos trámites que se puede hacer.&lt;/p&gt;
  125. &lt;p&gt;El mapeado de Juntas de Distrito completa mis otros trabajos de mapeo sobre &lt;a href="" rel="nofollow"&gt;distritos&lt;/a&gt; y &lt;a href="" rel="nofollow"&gt;barrios&lt;/a&gt; de Málaga. Me ha parecido importante que no faltasen en el mapa, ya que suelen ser puntos de referencia para cualquier trámite administrativo que se pueda necesitar, y conviene que se puedan encontrar en OSM. He añadido toda la información de la que dispongo (direcciones, horarios, teléfonos, etc.), para que cuando alguien busque donde está la Junta de Distrito de su barrio, tenga toda la información disponible.&lt;/p&gt;
  126. </description>
  127.      <dc:creator>dcapillae</dc:creator>
  128.      <pubDate>Mon, 11 Dec 2017 17:18:53 +0000</pubDate>
  129.      <comments></comments>
  130.      <geo:lat>36.72127</geo:lat>
  131.      <geo:long>-4.42166</geo:long>
  132.      <georss:point>36.72127 -4.42166</georss:point>
  133.    </item>
  134.    <item>
  135.      <title>Pirate Open Street Mapping Party Wayanad</title>
  136.      <link></link>
  137.      <guid></guid>
  138.      <description>&lt;p&gt;It was fun mapping Wayanad. A district known for its environment, ethnic people, sensitive areas, Hills, Forests and of course Rain.&lt;/p&gt;
  140. &lt;p&gt;For the very first time, J4v4m4n, Pirate Praveen suggested the idea of pirate mapping parties. To be exact, &lt;a href="" rel="nofollow"&gt;5 months before&lt;/a&gt;, he started a new thread on Loomio as  a proposal to contributing to open street maps as [Pirates]( Later the discussion lead to mapping parties around Kerala. When Praveen completed Kannur, I asked him for  one here in Wayanad. Exactly a week before 9th of this month, Praveen told me, we can host on 9th. I got excited as well as nervous. I don&amp;#39;t know what to do, How to arrange accommodation, where to map, etc.
  141. I was really worried about bicycles. I thought cycles could speed up the mapping process. Another headache was whom will help us in mapping.
  142. Tada.. &lt;a href="" rel="nofollow"&gt;Ranjith Siji&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Mujeeb&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Kannan&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Ambadi&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Tanzeer&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Sruthi&lt;/a&gt;, &lt;a href="#top" rel="nofollow"&gt;Hemanth&lt;/a&gt; came up to fulfill our plans.&lt;/p&gt;
  144. &lt;p&gt;Next to resolve was accommodation. &lt;a href="#top" rel="nofollow"&gt;Sreejith Koiloth&lt;/a&gt; helped us to rent DIET hostel.&lt;/p&gt;
  146. &lt;h2&gt;Into the real fun&lt;/h2&gt;
  148. &lt;p&gt;Sruthi, Praveen and Hemanth reached Bathery on 8th. Had dinner from Aravind Mess House. And then headed to DIET hostel. We made some plans for the next day. Discussed a lot of things too.
  149. On 9th December of 2017, by 8&amp;#39;O clock, Ranjith Siji, Mujeeb, Kannan and Ambadi reached. I picked Tanzeem and we met everybody at NRS bakery, Sulthan Bathery. &lt;/p&gt;
  151. &lt;p&gt;As planned earlier, unto noon, we mapped Sulthan Bathery. we grouped by 2. Me, Tanzeem and Praveen became a group. Ambadi and Mujeeb became next, Sruthi and Hemanth, Ranjith and Kannan and so on.
  152. By 12.30, We covered Almost bathery. After that we sat on a bench and discussed about the progress. Kannan came up with a digital SLR camera. He made couple of beautiful snaps. ( He haven&amp;#39;t yet shared any of them. I will update whenever I recieve them)&lt;/p&gt;
  154. &lt;p&gt;Next was fooding time. We came back to NRS, Had food. I think me, Praveen and Tanzeem ordered regular rice. Kannnan is a different character. After watching Food Inc, He became kind of insane. He stopped having non-vegitarian.
  155. I wonder a documentary is having this much impact! He had a little salad. Sruthi too!! She joined Kannan&amp;#39;s league.
  156. I love to have discussions. I am feeling like organizing and participating these such events opens a wide door for dialoges. We discussed about rural network connectivity, intel-minix prob, Food Inc, global warming, cattles and global warming etc.
  157. Ambadi was arguing for cattles as major cause for global warming. yea, It was lot of fun. On that table, we discussed about afternoon session. Again we grouped by two and started mapping. Praveen, Tanzeem, Sruthi, Mujeeb, Hemanth
  158. headed to Kalpetta. Somebody mapped Meenangadi, some Muttil and people left mapped Kalpetta. they reached back by 7 in the evening.
  159. I felt happy that, me and ranjith siji joined as a group and mapped a long area. We went by bike. Center For Social Computing offered a motor cycle and we headed to Pulpally. I personally got thrilled when we added a new road to the map.
  160. I told him different myths about wayanad, The origin of Sulthan Bathery&amp;#39;s name, people etc. in shorts, we discussed our thoughts on food culture, wikidata, wiki commons, economy, economics, &lt;code&gt;My AI Fear&lt;/code&gt; etc. We reached Nadavayal to
  161. have Kappa Biriyani. We headed to Varkey&amp;#39;s Hotel. Kappa biriyani was not that good. but not bad. Anyway, Ranjith didn&amp;#39;t like it much.&lt;/p&gt;
  163. &lt;p&gt;10th was the last day of mapping. I was home. I had some engagements. So I directed them to head towards Muthanga. But for the fate, time was over. They mapped something else. Then we planned to map Panamaram. I reached panamaram.
  164. By noon, They also reached there. Had some food from MAH hotel. Then ranjith took some photos of river and bridge etc. by 3&amp;#39;O clock, everybody except me and Tanzeem left for home. Then Tanzeem and me covered Panamaram.
  165. By 5.30 PM, Mapping party officially finished.&lt;/p&gt;
  166. </description>
  167.      <dc:creator>Joicemj</dc:creator>
  168.      <pubDate>Mon, 11 Dec 2017 14:12:42 +0000</pubDate>
  169.      <comments></comments>
  170.      <geo:lat>11.6646366506297</geo:lat>
  171.      <geo:long>76.2531316280365</geo:long>
  172.      <georss:point>11.6646366506297 76.2531316280365</georss:point>
  173.    </item>
  174.    <item>
  175.      <title>"OSM go" - Impressions</title>
  176.      <link></link>
  177.      <guid></guid>
  178.      <description>&lt;p&gt;Impressions:  &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  180. &lt;p&gt;This 3D-Playground is running in multi user mode. So if you see a smile, don&amp;#39;t run away, have a chat with me (key C) &lt;/p&gt;
  182. &lt;h2&gt;Please leave a comment, either if you enjoyed it or if you experienced a problem.&lt;/h2&gt;
  184. &lt;p&gt;&lt;a href=";lon=2.24950&amp;ele=34&amp;dir=286&amp;view=-19&amp;name=Garros" rel="nofollow"&gt;Roland Garros, Paris&lt;/a&gt;
  185. &lt;img src="" alt="Roland Garros"/&gt;&lt;/p&gt;
  187. &lt;p&gt;&lt;a href=";lon=37.62480&amp;ele=28.97&amp;dir=110&amp;view=0&amp;tiles=5&amp;name=Moscow" rel="nofollow"&gt;Moscow&lt;/a&gt;
  188. &lt;img src="" alt="Moscow"/&gt;&lt;/p&gt;
  190. &lt;p&gt;&lt;a href=";lon=-74.01109&amp;ele=0.24&amp;dir=107&amp;view=22&amp;opt=1&amp;tiles=2&amp;con=1&amp;name=church" rel="nofollow"&gt;A small church in a big town -Trinity Church, Broadway/Rector Street, New York (USA)&lt;/a&gt;
  191. &lt;img src="" alt="Church"/&gt;&lt;/p&gt;
  193. &lt;p&gt;Singapore under attack
  194. &lt;img src="" alt="Singapore under attack"/&gt;&lt;/p&gt;
  196. &lt;p&gt;&lt;a href=";lon=-79.38436&amp;ele=712.31&amp;view=-36&amp;dbg=1.5&amp;fps=2&amp;tiles=10&amp;name=Toronto" rel="nofollow"&gt;Toronto, Canada&lt;/a&gt;
  197. &lt;img src="" alt="Toronto"/&gt;&lt;/p&gt;
  199. &lt;p&gt;&lt;a href=";lon=28.9777&amp;ele=70&amp;dir=170&amp;view=-13&amp;tiles=4&amp;name=Istambul" rel="nofollow"&gt;The Blue Mosque/Sultan Ahmed Mosque,Istanbul&lt;/a&gt;
  200. &lt;img src="" alt="Istambul"/&gt;&lt;/p&gt;
  202. &lt;p&gt;&lt;a href=";lon=23.72633&amp;ele=68&amp;dir=348&amp;view=-30&amp;tiles=2&amp;name=Parthenon" rel="nofollow"&gt;Parthenon / Παρθενώνας - Greek&lt;/a&gt;
  203. &lt;img src="" alt="Parthenon "/&gt;&lt;/p&gt;
  205. &lt;p&gt;&lt;a href=";lon=13.39907&amp;dir=300&amp;view=+4&amp;ele=30&amp;tiles=4&amp;name=berlin" rel="nofollow"&gt;Berlin,Germany&lt;/a&gt;
  206. &lt;img src="" alt="Berlin"/&gt;&lt;/p&gt;
  208. &lt;p&gt;&lt;a href=";lon=2.29403&amp;ele=81&amp;dir=180&amp;view=-25&amp;name=EifelTower" rel="nofollow"&gt;Tour Eiffel - virtuelle&lt;/a&gt;
  209. &lt;img src="" alt="Tour Eiffel"/&gt;&lt;/p&gt;
  211. &lt;p&gt;Subway Station
  212. &lt;img src="" alt="Subway Station"/&gt;&lt;/p&gt;
  214. &lt;p&gt;&lt;a href=";lon=39.82647769&amp;ele=3.08&amp;dir=103&amp;view=10&amp;name=Mekka" rel="nofollow"&gt;Kaaba (Ka&amp;#39;aba)  ٱلْكَعْبَة  -  Mecca مكة المكرمة Makkah al-Mukarramah Bakkah&lt;/a&gt;
  215. &lt;img src="" alt="Kaaba Makkah"/&gt;&lt;/p&gt;
  217. &lt;p&gt;&lt;a href=";lon=35.23481919&amp;ele=125.31&amp;dir=1&amp;view=-25&amp;con=1&amp;name=Jerusalem" rel="nofollow"&gt;Western Wall (Klagemauer), Jerusalem, Israel/Palestin&lt;/a&gt;
  218. &lt;img src="" alt="Jerusalem"/&gt;&lt;/p&gt;
  220. &lt;p&gt;Guess, what place is this?
  221. &lt;img src="" alt="Guess"/&gt;&lt;/p&gt;
  223. &lt;p&gt;&lt;a href=";lon=9.19737&amp;ele=74.33&amp;dir=28&amp;view=-29&amp;tiles=9&amp;name=park" rel="nofollow"&gt;A walk in the park&lt;/a&gt;
  224. &lt;img src="" alt="Park"/&gt;&lt;/p&gt;
  226. &lt;h2&gt;Videos:&lt;/h2&gt;
  228. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;“Flying through the air”&lt;/a&gt;&lt;/p&gt;
  230. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;A shuttle pod “Lancet” is flying to the (German) Space Ship Orion (Raumpatrouille)&lt;/a&gt;&lt;/p&gt;
  232. &lt;p&gt;&lt;a href=";" rel="nofollow"&gt;&amp;quot;OSM go&amp;quot; used on a smartphone with 1/2/3-finger touch gestures &lt;/a&gt;&lt;/p&gt;
  234. &lt;h2&gt;OSM-User  -karlos-&lt;/h2&gt;
  236. &lt;p&gt;&lt;a href="mailto:[email protected]" rel="nofollow"&gt;[email protected]&lt;/a&gt;  &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  237. </description>
  238.      <dc:creator>-karlos-</dc:creator>
  239.      <pubDate>Mon, 11 Dec 2017 14:10:21 +0000</pubDate>
  240.      <comments></comments>
  241.    </item>
  242.    <item>
  243.      <title>OSMF should vote more often......</title>
  244.      <link></link>
  245.      <guid></guid>
  246.      <description>&lt;p&gt; it attracts people to join the OSMF (on average)&lt;/p&gt;
  248. &lt;p&gt;&lt;img src=";height=743&amp;cropmode=none" alt="Chart"/&gt;&lt;/p&gt;
  249. </description>
  250.      <dc:creator>SunCobalt</dc:creator>
  251.      <pubDate>Mon, 11 Dec 2017 12:05:42 +0000</pubDate>
  252.      <comments></comments>
  253.    </item>
  254.    <item>
  255.      <title>New week and new energy required  </title>
  256.      <link></link>
  257.      <guid></guid>
  258.      <description>&lt;p&gt;Dear Folks,&lt;/p&gt;
  260. &lt;p&gt;As the year is counting down and ice is in most of the places. Please, use our study &lt;a href="" rel="nofollow"&gt;;/a&gt; to generate more energy in your brain and consequently your entire body.
  261. &lt;img src="" alt=""/&gt;
  262. Participate in the study &lt;a href="" rel="nofollow"&gt;;/a&gt; to see how perfect you are in recognizing landuse areas.&lt;/p&gt;
  263. </description>
  264.      <dc:creator>grass_and_green</dc:creator>
  265.      <pubDate>Mon, 11 Dec 2017 11:14:07 +0000</pubDate>
  266.      <comments></comments>
  267.    </item>
  268.    <item>
  269.      <title>SMART/DDOT overhaul</title>
  270.      <link></link>
  271.      <guid></guid>
  272.      <description>&lt;h1&gt;Background&lt;/h1&gt;
  274. &lt;p&gt;As I write this, a complete overhaul to SMART/DDOT relations is being uploaded to the server. I did this for two reasons.&lt;/p&gt;
  276. &lt;h2&gt;Reason the first:&lt;/h2&gt;
  278. &lt;p&gt;When I last &amp;quot;overhauled&amp;quot; SMART relations, I admittedly made a huge mess of things. There were two reasons I did this:&lt;/p&gt;
  280. &lt;ol&gt;
  281. &lt;li&gt;I thought it&amp;#39;d look nice on the transit map with each route number getting rendered just once per road.&lt;/li&gt;
  282. &lt;li&gt;I didn&amp;#39;t want to have to add the bus stops to &lt;em&gt;all the relations&lt;/em&gt; and risk forgetting some.&lt;/li&gt;
  283. &lt;/ol&gt;
  285. &lt;p&gt;So what I did was made route segments and route segment segments.&lt;/p&gt;
  287. &lt;p&gt;I apologize for that, now realizing that it&amp;#39;s wrong. Plus, the second point above is invalid, as I&amp;#39;ve since discovered; I can edit multiple relations simultaneously.&lt;/p&gt;
  289. &lt;p&gt;The first reason for this overhaul is to fix that.&lt;/p&gt;
  291. &lt;h2&gt;Reason the second:&lt;/h2&gt;
  293. &lt;p&gt;Data for both systems was horribly outdated. For example, there were still bus routes depicted on Woodward south of Campus Martius, which hasn&amp;#39;t been the case since the QLine construction started. The DDOT relations still used the old public transit format! So the second reason for this overhaul is a data update.&lt;/p&gt;
  295. &lt;h1&gt;Caveats&lt;/h1&gt;
  297. &lt;p&gt;There are a lot of bus routes I haven&amp;#39;t ridden:&lt;/p&gt;
  299. &lt;ul&gt;
  300. &lt;li&gt;Almost all DDOT routes outside of Downtown&lt;/li&gt;
  301. &lt;li&gt;SMART routes 160, 280, 445, 475&lt;/li&gt;
  302. &lt;/ul&gt;
  304. &lt;p&gt;For these routes, I&amp;#39;ve put my best effort to mapping them accurately, though in some places I simply could not tell where the route was intended to go (see: 38 at Harrison, Sears, or Outer Drive).&lt;/p&gt;
  306. &lt;h1&gt;Sources&lt;/h1&gt;
  308. &lt;p&gt;Official bus schedules and maps can be found at &lt;a href="" rel="nofollow"&gt;DDOT&lt;/a&gt;, &lt;a href="" rel="nofollow"&gt;SMART&lt;/a&gt;, and &lt;a href="" rel="nofollow"&gt;RTA&lt;/a&gt;. Additionally, for the RTA and SMART routes, some details not shown on the maps were mapped from personal experience.&lt;/p&gt;
  310. &lt;p&gt;For some DDOT routes where I couldn&amp;#39;t tell what was what on the map, I followed roads that were part of the pre-existing relations.&lt;/p&gt;
  312. &lt;p&gt;I also used a bit of OpenStreetCam data to figure out which way buses went around loops.&lt;/p&gt;
  314. &lt;p&gt;Lastly, DDOT&amp;#39;s GTFS file is public-domain, and helped me figure out a couple things as well. It can be downloaded &lt;a href="" rel="nofollow"&gt;here&lt;/a&gt;.&lt;/p&gt;
  316. &lt;h1&gt;What&amp;#39;s next&lt;/h1&gt;
  318. &lt;p&gt;I&amp;#39;m going to take a short break, then in 2018 ride all the SMART routes and record out the bus windows and put the videos on YouTube. I&amp;#39;ll license the videos for free use for open-source mapping projects - anything you see or hear on the video will be fair game to add to the map.&lt;/p&gt;
  320. &lt;p&gt;I personally will use the videos to map bus stops, and add them to back the relations.&lt;/p&gt;
  321. </description>
  322.      <dc:creator>NixillUmbreon</dc:creator>
  323.      <pubDate>Mon, 11 Dec 2017 02:53:31 +0000</pubDate>
  324.      <comments></comments>
  325.    </item>
  326.    <item>
  327.      <title>2017 Board Election Statistics</title>
  328.      <link></link>
  329.      <guid></guid>
  330.      <description>&lt;p&gt;The anonymized ballots from yesterday&amp;#39;s OSMF board vote are available as a handy text file &lt;a href="" rel="nofollow"&gt;on OpaVote&lt;/a&gt;, so I decided to play around with them a bit. Here&amp;#39;s a breakdown of the rankings for each candidate:&lt;/p&gt;
  332. &lt;p&gt;&lt;img src="" alt="Heather Leson (1: 179, 2: 67, 3: 45, 4: 71, 0: 127), Joost Schouppe (1: 118, 2: 223, 3: 66, 4: 34, 0: 48), Paul Norman (1: 129, 2: 105, 3: 54, 4: 50, 0: 151), David Dean (1: 52, 2: 62, 3: 168, 4: 64, 0: 143)"/&gt;&lt;/p&gt;
  334. &lt;p&gt;I was also curious if people usually filled in the maximum of four slots, or left some of them blank. This is the result:&lt;/p&gt;
  336. &lt;ul&gt;
  337. &lt;li&gt;0 candidates: 11&lt;/li&gt;
  338. &lt;li&gt;1 candidates: 21&lt;/li&gt;
  339. &lt;li&gt;2 candidates: 124&lt;/li&gt;
  340. &lt;li&gt;3 candidates: 114&lt;/li&gt;
  341. &lt;li&gt;4 candidates: 219&lt;/li&gt;
  342. &lt;/ul&gt;
  344. &lt;p&gt;So most people did indeed list 3 or 4 candidates! With STV, the third place can matter even if there are only two seats available, so it makes sense to fill it in. Nevertheless, I also looked more closely at the top two spots to see if there are any interesting correlations. Based on all ballots with at least 2 candidates, here&amp;#39;s the popularity of top two pairings (the order of candidate names carries no meaning):&lt;/p&gt;
  346. &lt;ul&gt;
  347. &lt;li&gt;Heather/Joost: 166&lt;/li&gt;
  348. &lt;li&gt;Paul/Joost: 136&lt;/li&gt;
  349. &lt;li&gt;Paul/David: 46&lt;/li&gt;
  350. &lt;li&gt;Heather/Paul: 43&lt;/li&gt;
  351. &lt;li&gt;Joost/David: 33&lt;/li&gt;
  352. &lt;li&gt;Heather/David: 33&lt;/li&gt;
  353. &lt;/ul&gt;
  355. &lt;p&gt;If there are any other statistics you&amp;#39;re curious about, feel free to ask – if I find the time, I&amp;#39;ll be glad to run them. :)&lt;/p&gt;
  356. </description>
  357.      <dc:creator>Tordanik</dc:creator>
  358.      <pubDate>Sun, 10 Dec 2017 20:11:24 +0000</pubDate>
  359.      <comments></comments>
  360.      <geo:lat>48.574451777597</geo:lat>
  361.      <geo:long>13.464258849599</geo:long>
  362.      <georss:point>48.574451777597 13.464258849599</georss:point>
  363.    </item>
  364.    <item>
  365.      <title>Algo que ainda gosto de fazer no OSM</title>
  366.      <link></link>
  367.      <guid></guid>
  368.      <description>&lt;p&gt;Finalizei a delimitação dos bairros de &lt;a href="" rel="nofollow"&gt;Rondonópolis - MT/BR&lt;/a&gt;. Demorou um pouco e deu trabalho, mas foi gratificante, principalmente por ser uma das atividades que ainda me motiva a contribuir para a plataforma. &lt;/p&gt;
  370. &lt;p&gt;Digo ainda me motiva pois o mapa já esta bem completo. Basicamente há poucos locais sem vias, e as tarefas atuais se limitam aos POIs, assim como as correções, que são coisas que não gosto muito de fazer.&lt;/p&gt;
  372. &lt;p&gt;E por quê a &lt;a href="" rel="nofollow"&gt;delimitação de bairros&lt;/a&gt; ainda me fascina e me motiva a contribuir? Nas cidades com plano diretor, onde num projeto urbanístico o bairro encabeça o projeto, isto e, antes de existir um logradouro, primeiro tem que existir um bairro. Assim, nome de ruas podem se repetir quantos vezes for necessário dentro de uma mesma cidade. &lt;/p&gt;
  374. &lt;p&gt;Nesse contexto os céticos podem dizeṛ &amp;quot;isso não existe, impossível&amp;quot;. Se a cidade estiver devidamente delimitada eh perfeitamente possível. Dai a importância da delimitação dos bairros.&lt;/p&gt;
  376. &lt;p&gt;&lt;img src="" alt="Rondonópolis - MT"/&gt;&lt;/p&gt;
  377. </description>
  378.      <dc:creator>ivaldonm</dc:creator>
  379.      <pubDate>Sun, 10 Dec 2017 18:14:07 +0000</pubDate>
  380.      <comments></comments>
  381.      <geo:lat>-16.4604326358776</geo:lat>
  382.      <geo:long>-54.6317794115748</geo:long>
  383.      <georss:point>-16.4604326358776 -54.6317794115748</georss:point>
  384.    </item>
  385.    <item>
  386.      <title>Thank you, now on with the next steps</title>
  387.      <link></link>
  388.      <guid></guid>
  389.      <description>&lt;p&gt;Thank you to all the OSMF members, fellow candidates, board, and outgoing board members.  It has been a privilege to consider your priorities for OSMF via questions, notes, and conversations. &lt;/p&gt;
  391. &lt;p&gt;We are the community, the map, and the project. The lovely people who make OSM part of their daily flows count on all of us at OSMF to meet the full mandate and the full potential. This means considering, then building on how we might balance the growing, changing needs of the open, global, diverse community.&lt;/p&gt;
  393. &lt;p&gt;Over the past few weeks, the questions on the wiki and the conversations on this mailing list have pointed to some potential actions. Converting those requests and ideas into productive working documents for consultation is the next step. There are many people on this list and in the wider community that will contribute if there are healthy spaces and a clear ask. It is up to us in the membership, in the working groups, and on the board to make this possible.&lt;/p&gt;
  395. &lt;p&gt;Thank you again, &lt;/p&gt;
  397. &lt;p&gt;Heather &lt;/p&gt;
  398. </description>
  399.      <dc:creator>Heather Leson</dc:creator>
  400.      <pubDate>Sun, 10 Dec 2017 16:35:38 +0000</pubDate>
  401.      <comments></comments>
  402.    </item>
  403.    <item>
  404.      <title>OSM es el mapa</title>
  405.      <link></link>
  406.      <guid></guid>
  407.      <description>&lt;p&gt;«Yo, personalmente, no tengo ningún interés especial en que OSM sea alternativa de nada. Para mí OSM es el mapa.»&lt;/p&gt;
  409. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;Rafael Ávila Coya&lt;/a&gt;, vía grupo &lt;a href="" rel="nofollow"&gt;OSM España&lt;/a&gt; en &lt;a href="" rel="nofollow"&gt;Telegram&lt;/a&gt;, 9 de diciembre de 2017.&lt;/p&gt;
  410. </description>
  411.      <dc:creator>dcapillae</dc:creator>
  412.      <pubDate>Sun, 10 Dec 2017 11:01:34 +0000</pubDate>
  413.      <comments></comments>
  414.    </item>
  415.    <item>
  416.      <title>The history of HOT US Inc governance - not to be replicated in OSMF</title>
  417.      <link></link>
  418.      <guid></guid>
  419.      <description>&lt;p&gt;(EN automatic translation below)&lt;/p&gt;
  421. &lt;p&gt;Durant la campagne pour les élections 2017 au board de l&amp;#39;OSM, je suis intervenu par trois fois sur la liste de discussion OSMF :&lt;/p&gt;
  423. &lt;ul&gt;
  424. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;ce premier courriel&lt;/a&gt; en anglais dans lequel je montre la faible implication de Heather Leson dans OSM depuis 2011. &lt;/p&gt;&lt;/li&gt;
  425. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;ce deuxième courriel&lt;/a&gt; intitulé &amp;quot; Language, tone and their explanations - why I resigned from HOT US Inc&amp;quot;, rédigé en français et traduit en anglais, pour expliquer le ton employé dans le premier via notamment ma lettre de résignation de HOT US Inc en 2016, que j&amp;#39;ai publié dans mon &lt;a href="" rel="nofollow"&gt;précédent billet de blog&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
  426. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;ce troisième courriel&lt;/a&gt; intitulé &amp;quot;The history of HOT US Inc governance - not to be replicated in OSMF&amp;quot; qui contient le lien vers un document, lui aussi rédigé en français et traduit en anglais, retraçant les graves soucis de gouvernance dans le board de HOT US Inc pendant la période durant laquelle j&amp;#39;en étais membre (mars 2014 à janvier 2016)&lt;/p&gt;&lt;/li&gt;
  427. &lt;/ul&gt;
  429. &lt;hr/&gt;
  431. &lt;p&gt;During the campaign for the 2017 elections on the board of the OSM, I spoke three times on the OSMF mailing list:&lt;/p&gt;
  433. &lt;ul&gt;
  434. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;this first email&lt;/a&gt; in English in which I show the weak involvement of Heather Leson in OSM since 2011.&lt;/p&gt;&lt;/li&gt;
  435. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;this second email&lt;/a&gt; titled &amp;quot;Language, tone and their explanations - why I resigned from HOT US Inc.&amp;quot; written in French and translated into English, to explain the tone used in the first via including my letter of resignation of HOT US Inc in 2016, which I published in my [previous blog post] (https: //&lt;a href="" rel="nofollow"&gt;;/a&gt;)&lt;/p&gt;&lt;/li&gt;
  436. &lt;li&gt;&lt;p&gt;&lt;a href="" rel="nofollow"&gt;this third email&lt;/a&gt; titled &amp;quot;The History of HOT US Inc Governance - not to be replicated in OSMF&amp;quot; which contains the link to a document, also written in French and translated into English, tracing the serious governance concerns in the board of HOT US Inc during the period during which I was a member (March 2014 to January 2016)&lt;/p&gt;&lt;/li&gt;
  437. &lt;/ul&gt;
  438. </description>
  439.      <dc:creator>sev_osm</dc:creator>
  440.      <pubDate>Sun, 10 Dec 2017 00:45:04 +0000</pubDate>
  441.      <comments></comments>
  442.    </item>
  443.    <item>
  444.      <title>mapper die voor problemen zorgt</title>
  445.      <link></link>
  446.      <guid></guid>
  447.      <description>&lt;p&gt;in project 3630 verschillende tasks
  448. GERMANIAGERMAN heeft gevalideerd. nog niet zo&amp;#39;n puinhoop gezien.
  449. diverse berichten gestuurd  met cc aan Bigardot
  450. task 313 en andere&lt;/p&gt;
  451. </description>
  452.      <dc:creator>Frans S</dc:creator>
  453.      <pubDate>Sat, 09 Dec 2017 20:30:32 +0000</pubDate>
  454.      <comments></comments>
  455.      <geo:lat>26.54058925</geo:lat>
  456.      <geo:long>88.4059095</geo:long>
  457.      <georss:point>26.54058925 88.4059095</georss:point>
  458.    </item>
  459.    <item>
  460.      <title>Dynamic manipulation of styles based on object values in libosmscout</title>
  461.      <link></link>
  462.      <guid></guid>
  463.      <description>&lt;p&gt;As just stated on the Fossgis Hackingweekend at the Linuxhotel in Essen... &amp;quot;I&amp;#39;m mapping the year of constrcution for a (huge) number of houses. I&amp;#39;m looking for a way to visualize this on the map&amp;quot;.&lt;/p&gt;
  465. &lt;p&gt;Likely multiple solutions exist, but how to do this with libosmscout? &lt;/p&gt;
  467. &lt;p&gt;At the start of the weekend this was not yet possible. Small discussion with another developer (not at the weekend) showed, that a general approach was needed, as colouring of ways based on attributes has also interesting use cases (hint: colour of metro lines).&lt;/p&gt;
  469. &lt;p&gt;Libosmscout implements tag and value combinations as features. All possible features of an object type (configurable during import) are flag in a bit set, if an concrete object has the feature.&lt;/p&gt;
  471. &lt;p&gt;The value of an feature is implemented as simple class that must offer serialization and deserialization methods.&lt;/p&gt;
  473. &lt;p&gt;So first we write a new Feature implementation that parses the &lt;code&gt;start_date&lt;/code&gt; and &lt;code&gt;year_of_construction&lt;/code&gt; tags. The new Feature will have two int attribute for the start and end year. Investigation of the actual tag values show and creation time can be an time interval, for our needs the year however is enough. Depending on the use case other implementation could be possible, too.&lt;/p&gt;
  475. &lt;p&gt;We need to do some string parsing to get most of the possible variants of the tag values parsed. Mapper: Please do not be to creative ;-)&lt;/p&gt;
  477. &lt;p&gt;Afterwards we add the possibility to register style processors into the rendering pipeline. The processor has a simple interface. It gets the list of feature values and the style as defined by the style sheet. It returns either the original style or a (cache) new style instance. Processors are registered by type.&lt;/p&gt;
  479. &lt;p&gt;Next step is to implement a simple processor for the type &lt;code&gt;building&lt;/code&gt;. The processor checks if the construction year feature is available and the year between 1800 and 2020. In this case it return a red fill style, with the actual brightness depending on the age. Older buildings get darker red.&lt;/p&gt;
  481. &lt;p&gt;See the result:&lt;/p&gt;
  483. &lt;p&gt;&lt;img src="" alt="Different coloring of houses based on construction year"/&gt;&lt;/p&gt;
  485. &lt;p&gt;Since there are not that much buildings with construction year mapped, let us try something more visible. Different colors depending on the house number been odd even (or not numerical).&lt;/p&gt;
  487. &lt;p&gt;Now that looks more obvious :-)&lt;/p&gt;
  489. &lt;p&gt;&lt;img src="" alt="Different coloring of houses based on house number being odd or even"/&gt;&lt;/p&gt;
  491. &lt;p&gt;Fine. That was fun. Now back to code to refactor it for a slightly better API...&lt;/p&gt;
  492. </description>
  493.      <dc:creator>Framstag</dc:creator>
  494.      <pubDate>Sat, 09 Dec 2017 14:57:25 +0000</pubDate>
  495.      <comments></comments>
  496.      <geo:lat>51.4307141499202</geo:lat>
  497.      <geo:long>7.11240828037262</geo:long>
  498.      <georss:point>51.4307141499202 7.11240828037262</georss:point>
  499.    </item>
  500.    <item>
  501.      <title>One year at the Foundation.. an incredible book series by Isaac Asimov</title>
  502.      <link></link>
  503.      <guid></guid>
  504.      <description>&lt;p&gt;Hi all :)&lt;/p&gt;
  506. &lt;p&gt;My name is Dorothea. I&amp;#39;ve been helping the &lt;a href="" rel="nofollow"&gt;OpenStreetMap Foundation&lt;/a&gt; board and some of the Working Groups in the past year, as an Administrative Assistant (one of two independent contractors that the Foundation has - the other one being the accountant). So, for transparency reasons I would like to give you a better idea of what I do and also my view of what being at the Board encompasses - based on my experiences from the previous year.&lt;/p&gt;
  508. &lt;h2&gt;What I do&lt;/h2&gt;
  510. &lt;p&gt;Basically I am helping the board (and some of the Working Groups, if there is time and they want to) with administrative tasks, so they can have more time to focus elsewhere. So far I am mainly involved with:&lt;/p&gt;
  512. &lt;ul&gt;
  513. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;Documenting board meetings&lt;/a&gt;&lt;/li&gt;
  514. &lt;li&gt;Documenting procedures on the board wiki&lt;/li&gt;
  515. &lt;li&gt;Dealing with Corporate Memberships&lt;/li&gt;
  516. &lt;/ul&gt;
  518. &lt;p&gt;Some non-regular tasks:&lt;/p&gt;
  520. &lt;ul&gt;
  521. &lt;li&gt;Administrative support during Local Chapter applications&lt;/li&gt;
  522. &lt;li&gt;Adding Advisory Board members to the AB mailing list and updating the wiki&lt;/li&gt;
  523. &lt;li&gt;Providing membership lists&lt;/li&gt;
  524. &lt;/ul&gt;
  526. &lt;p&gt;Infrequent:&lt;/p&gt;
  528. &lt;ul&gt;
  529. &lt;li&gt;Documenting Local Chapter Congresses (2016, &lt;a href="" rel="nofollow"&gt;2017&lt;/a&gt;)&lt;/li&gt;
  530. &lt;li&gt;Documenting the Face-to-Face meeting (2016 # on the board wiki)&lt;/li&gt;
  531. &lt;li&gt;Implementing the new Corporate Membership Payment system on CiviCRM (2016)&lt;/li&gt;
  532. &lt;li&gt;Running the Election to Board (&lt;a href="" rel="nofollow"&gt;2017&lt;/a&gt;)&lt;/li&gt;
  533. &lt;/ul&gt;
  535. &lt;h3&gt;Working Group related&lt;/h3&gt;
  537. &lt;p&gt;Two Working Groups have asked for administrative support from the board&lt;/p&gt;
  539. &lt;ul&gt;
  540. &lt;li&gt;Licensing Working Group: Documenting online meetings&lt;/li&gt;
  541. &lt;li&gt;State of the Map Working Group:
  543. &lt;ul&gt;
  544. &lt;li&gt;SotM2017 - Supporting &lt;a href="" rel="nofollow"&gt;scholars&lt;/a&gt;&lt;/li&gt;
  545. &lt;li&gt;SotM2018 - (Plan for) Supporting scholars (if there is going to be a scholarship program) and sponsorship&lt;/li&gt;
  546. &lt;/ul&gt;&lt;/li&gt;
  547. &lt;/ul&gt;
  549. &lt;h3&gt;Time allocation&lt;/h3&gt;
  551. &lt;p&gt;This can vary from month to month, with a cap of 65 hours per month. This was surpassed at least once before State of the Map 2017, as one of the scholars required extra support in order to get his visa (there was no Embassy of Japan in his country).&lt;/p&gt;
  553. &lt;p&gt;An overview of the time allocation is supplied monthly to the board. I also have a monthly meeting with the Secretary.&lt;/p&gt;
  555. &lt;h2&gt;An inside view of the Board&amp;#39;s work&lt;/h2&gt;
  557. &lt;p&gt;From the past year I can say that board members have to do a lot of &amp;quot;ground&amp;quot; work: writing documents, collaborating or providing feedback on documents writen by other board members or Working Groups, liaising with Working Groups, working on getting their ideas approved by other board members and the community.  It requires even more energy and time if you become one of the officers (Chairperson, Treasurer, Secretary). I think Frederik describes it better than I do in his &lt;a href="" rel="nofollow"&gt;post&lt;/a&gt;. Regarding visionary ideas &amp;amp; tasks, well my experience was that the board does very pragmatic work - the only exception I can think of was a discussion about the future that took place during the &lt;a href="" rel="nofollow"&gt;Face-to-Face meeting in May&lt;/a&gt;. Related to the F2F meetings: All board members are very passionate about OpenStreetMap, even if they have different views on some areas. The F2F meeting in May 2016 gave me the impression that it was easier for board members with different views to find common ground. I am not sure if it was related to non-verbal communication, but I had the impression that these meetings really helped the board members work together.&lt;/p&gt;
  559. &lt;h2&gt;Working Groups&lt;/h2&gt;
  561. &lt;p&gt;The people at the &lt;a href="" rel="nofollow"&gt;Working Groups&lt;/a&gt; do some amazing work. And you can make a real difference in the Foundation by participating in one of them. Just find the Working Group you would like to get involved with. If you don&amp;#39;t have much time to join a Working Group, perhaps you can help in other ways. As a CWG volunteer I can suggest some related tasks: you can translate your favorite OSMF blog post in your language (perhaps the &lt;a href="" rel="nofollow"&gt;PokemonGo&lt;/a&gt; one, as we have a new influx of mappers?), or send us your favorite OSM-related CC BY photos.&lt;/p&gt;
  563. &lt;p&gt;Finally, I would like to nudge people who are not very vocal to share your thoughts on [email protected], [email protected] or your diary - particularly if your views are different from the ones already expressed. Throughout the year :)&lt;/p&gt;
  565. &lt;p&gt;Some personal info: &lt;/p&gt;
  567. &lt;p&gt;I love OpenStreetMap :) I&amp;#39;ve been mapping for the past ~4 years, mostly outdoors. Currently I am mapping Athens (Greece), so if you ever visit, feel free to send me a message to meet at the local &lt;a href="" rel="nofollow"&gt;hackerspace&lt;/a&gt;.&lt;/p&gt;
  569. &lt;p&gt;GPG key ID: 0x1EF42A022575038A&lt;/p&gt;
  570. </description>
  571.      <dc:creator>Doro8ea</dc:creator>
  572.      <pubDate>Fri, 08 Dec 2017 22:14:47 +0000</pubDate>
  573.      <comments></comments>
  574.    </item>
  575.    <item>
  576.      <title>OpenStreetMap Foundation Chairperson's Report for the 2017 Annual General Meeting</title>
  577.      <link></link>
  578.      <guid></guid>
  579.      <description>&lt;p&gt;When sitting down to write the Chairperson’s Report for this Annual General Meeting of the OpenStreetMap Foundation I have to confess I was having a difficult time. Not because OpenStreetMap hasn’t continued to make great strides over the past year and continue to become further THE free map of the entire world. No, it was because my heart once again was heavy. This year&amp;#39;s election has been even more hostile than others. Some of the debate has surrounded around if OpenStreetMap is currently a welcoming place for all and if we ever make people not feel welcome due to the actions of some of our members. &lt;/p&gt;
  581. &lt;p&gt;Procrastinating on writing this I was scrolling through Twitter and I happened across a quote from the CEO of Creative Commons, Ryan Merkley. &lt;/p&gt;
  583. &lt;p&gt;&amp;quot;Pick big fights with your enemies, not small fights with your friends.”&lt;/p&gt;
  585. &lt;p&gt;Stop and think about that for a moment. &lt;/p&gt;
  587. &lt;p&gt;When OpenStreetMap started we picked a huge fight with proprietary map provides. For a long time we were just some little upstart, but then they began to take us seriously. Today we continue to be used in more prominent and more important ways all over the world. Just in the past 2 weeks OpenStreetMap became used in Ingress and Pokemon Go, applications of millions of users. New editors are coming in because they can update the map themselves. How exciting is it that all our work continues to be used in more and more ways?&lt;/p&gt;
  589. &lt;p&gt;What is our next big fight to continue to be the best free map of the entire world? Let’s all think about those challenges and how we are going to surmount them. &lt;/p&gt;
  591. &lt;p&gt;How can we lay aside differences and be welcoming to people who are different from us? It is certainly not from fighting amongst ourselves. That just makes people want to check out, myself included, hence the difficulty in writing this report. &lt;/p&gt;
  593. &lt;p&gt;We were not without accomplishments this year though. We’ve increased all types of membership with the OSMF membership standing at almost 900 people now. That is more than we’ve ever had. We’ve increased the &lt;a href="" rel="nofollow"&gt;Corporate Membership to 24&lt;/a&gt; and created an Advisory Board currently consisting of representatives from Corporate Members and Local Chapters. &lt;/p&gt;
  595. &lt;p&gt;Going forward things I’d like the OSMF Board to focus on in the next year include increasing the overall diversity of all our memberships. From encouraging different individuals to become OSMF Members, recruiting different types of corporate members and adding more local chapters. To do that I think we are going to have to show more value as the Foundation. By supporting local chapters more and tech community initiatives. To be able to do this we are going to have to explore ways to have additional funding avenues. I hope we can finish creating a micro-grants program to all groups to apply for this support.  &lt;/p&gt;
  597. &lt;p&gt;I hope after the election I can be hopeful for the next year. I hope we all can be, let’s come together and stop picking the small fights. &lt;/p&gt;
  598. </description>
  599.      <dc:creator>wonderchook</dc:creator>
  600.      <pubDate>Fri, 08 Dec 2017 22:02:53 +0000</pubDate>
  601.      <comments></comments>
  602.      <geo:lat>46.4918926638271</geo:lat>
  603.      <geo:long>-122.936496734619</geo:long>
  604.      <georss:point>46.4918926638271 -122.936496734619</georss:point>
  605.    </item>
  606.  </channel>
  607. </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