[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>Potlatch 2.5</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;A new version of Potlatch 2 with several improvements and bugfixes:&lt;/p&gt;
  20. &lt;ul&gt;
  21. &lt;li&gt;&amp;#39;New-style&amp;#39; multipolygons are supported, where the tags are placed on the relation rather than the outer way. When you edit such a multipolygon, look at the bottom of the tag editor; you&amp;#39;ll see that it&amp;#39;s displaying the relation tags rather than the way. If you do want to change the tags on the way, you can choose that from the little dropdown menu there.&lt;/li&gt;
  22. &lt;li&gt;Pop-up dialogue boxes are now generally resizable.&lt;/li&gt;
  23. &lt;li&gt;In the Advanced tag view, long tag values now wrap onto multiple lines.&lt;/li&gt;
  24. &lt;li&gt;The background menu is now usable on smaller screens.&lt;/li&gt;
  25. &lt;li&gt;A &amp;#39;Clear all&amp;#39; button on the Bookmarks menu.&lt;/li&gt;
  26. &lt;li&gt;Shift-drag to zoom into a particular area; shift-click + or - to zoom three levels at a time; and you can now zoom out beyond zoom level 14, in which case no data will be displayed or loaded.&lt;/li&gt;
  27. &lt;li&gt;Shift-&amp;lt; and &amp;gt; jump 10 nodes at a time along a way.&lt;/li&gt;
  28. &lt;li&gt;Code now compiles with Apache Flex as well as with (older) Adobe Flex.&lt;/li&gt;
  29. &lt;li&gt;Plus a bunch of other small fixes.&lt;/li&gt;
  30. &lt;/ul&gt;
  32. &lt;p&gt;Potlatch 2 is somewhere between &amp;#39;active development&amp;#39; and &amp;#39;maintenance mode&amp;#39;: there&amp;#39;s no massive new features that I&amp;#39;m planning, but I intend to keep making small improvements to it along these lines, plus extra features as and when I&amp;#39;m doing some mapping and figure out a way to make it easier or quicker to use. OSM is lucky to have such an excellent default editor in iD, which gives P2 the freedom to develop as an efficient and comfortable editor for those who like its way of doing things.&lt;/p&gt;
  33. </description>
  34.      <dc:creator>Richard</dc:creator>
  35.      <pubDate>Sat, 25 Mar 2017 08:54:46 +0000</pubDate>
  36.      <comments></comments>
  37.    </item>
  38.    <item>
  39.      <title>Some vandalism</title>
  40.      <link></link>
  41.      <guid></guid>
  42.      <description>&lt;h1&gt;Vandalism on UP campus&lt;/h1&gt;
  44. &lt;p&gt;After checking some data of our campus I spot odd additions to the campus map.
  45. a User edited some information regarding the name and added some shops that did not exist.
  46. I contacted them and asked to revert changes made. Will monitor and follow the steps to correct data if not corrected.&lt;/p&gt;
  47. </description>
  48.      <dc:creator>FrikanRW</dc:creator>
  49.      <pubDate>Fri, 24 Mar 2017 18:37:28 +0000</pubDate>
  50.      <comments></comments>
  51.      <geo:lat>-25.7549472253134</geo:lat>
  52.      <geo:long>28.2305717468262</geo:long>
  53.      <georss:point>-25.7549472253134 28.2305717468262</georss:point>
  54.    </item>
  55.    <item>
  56.      <title>My Manifesto for HOT Board Member Position</title>
  57.      <link></link>
  58.      <guid></guid>
  59.      <description>&lt;p&gt;“Love and Compassion are necessities, not luxuries. Without them humanity cannot survive”.                                                                                                                                -  Dalai Lama&lt;/p&gt;
  61. &lt;p&gt;Hello, voting members! I am Ahasan, I belong to the coastal district Khulna of Bangladesh. I truly believe in humanity and continuously strive and work towards humanity because my motto in life is ‘if you want to leave a mark in the world, work for the humanity’. This ideology motivated me to expand OpenStreetMap in Bangladesh to make open geospatial data for all and to create OpenStreetMap Bangladesh (OSMBD) community and then work for Humanitarian Open Street Map (HOTOSM). I am truly honored to be nominated by Pete Masters in the global arena of HOTOSM. I express my heartfelt gratitude towards him for believing in me. &lt;/p&gt;
  63. &lt;p&gt;Who am I?&lt;/p&gt;
  65. &lt;ul&gt;
  66. &lt;li&gt;I am a Remote Sensing and Geographic Information System graduate from Asian University of Technology (AIT), Thailand. &lt;/li&gt;
  67. &lt;li&gt;I am also a graduate in Environmental Science from Khulna University, Bangladesh. &lt;/li&gt;
  68. &lt;li&gt;Diploma in Climate Change Vulnerability and Humanitarian Responses at Jointly University of Hawaii-USA, United Nations University, Keio &amp;amp; Okayama University-Japan, National university of Samoa and Asian Institute of Technology-Thailand.&lt;/li&gt;
  69. &lt;/ul&gt;
  71. &lt;p&gt;Currently, I am working as a Geospatial data consultant in Global Facility for Disaster Reduction and Recovery (GFDRR) unit which is a global partnership that helps developing countries better understand and reduce their vulnerability to natural hazards and climate change. GIS and Remote sensing  is my passion and working with it nationally and internationally for past 12 years. During my Master’s degree in Asian Institute of Technology (AIT) Thailand, I got involved with Open Source GIS. After coming back to my motherland – Bangladesh; GFDRR’s collaborative open city project gave me the chance to work actively with OpenStreetMap. From then on I fell in love with OSM and HOTOSM and till date, I am working passionately for both the communities. Bangladesh didn’t have much knowledge of OSM before 2013.  As a GIS specialist and supporter of free and open source projects, I realized the huge potential of OSM in developing Bangladesh, with regular disaster threat and top listed country for climate impacts. I got introduced with Humanitarian Open Street Map Team (HOT) through Jeff Hack and Robert Soden. Later I have worked with Ryan Somerville, Jorieke vyncke, Pete Masters, Dale Kunce, Daniel Joseph, Taichi Furuhashi, Chad Belevins, Patricia Solis and the SOTMUS 2015 gave me the chance to meet most of the legends of OSM/HOTOSM. If anyone asks me why I love OSM/HOT then my response will be, the location data should be open for any emergency, research and for the local community what I felt always during emergency response and in my academic life. I found, to be involved with HOT is a noble work what will serve the community for a long time with a very minimum effort. Therefore I started to disseminate this knowledge among people, building a strong OSM community involving academia, government and non government organizations, youth communities, youth entrepreneurs and the local level low tech community. I voluntarily facilitated more than 35 OSM training and coordinated many more mapping parties in Bangladesh. People hire me for conventional GIS mapping, I introduce OpenStreetMapping that’s how OSM is spreading among the agencies here. I write regularly about opendata and OSM in my personal blog(&lt;a href="" rel="nofollow"&gt;;/a&gt;)&lt;/p&gt;
  73. &lt;p&gt;Currently, along with like minded people of our community took decision to create OSM foundation officially to launch more events through agencies and academia. Simultaneously I am campaigning to create more use cases for the OSM data uploaded so far since &amp;quot;Data have no meaning if there is no use&amp;quot;. We shouldn’t wait for disaster to use this data only; therefore we need to use the OSM data in research and innovation.&lt;/p&gt;
  75. &lt;p&gt;My vision for HOTOSM:&lt;/p&gt;
  77. &lt;ul&gt;
  78. &lt;li&gt;I believe, HOTOSM is not only a non-profit organization but also a global family with open mind members who always works for the only purpose - serving the affected global community.&lt;br/&gt;&lt;/li&gt;
  79. &lt;li&gt;If I get elected as a board member, I will try my level best to provide logical, critical and right judgmental decisions for HOTOSM and its sustainable growth in future. &lt;/li&gt;
  80. &lt;li&gt;Ensure that HOT is a transparent organization for its members who can attend all meetings (Board included) and access all meeting notes, communications and all the Organization documents (specifically finance, admin, projects) ; within of course the respect of privacy.&lt;/li&gt;
  81. &lt;li&gt;HOTOSM will give me the official identity what will make my stand bold in future venture regarding OSM movement and HOT activation among communities around the world.&lt;/li&gt;
  82. &lt;li&gt;I ensure that HOTOSM fosters its support to the growth of autonomous local OSM communities (made of individuals, groups, chapters and economic operators) and develop their ability to sustain relations amongst themselves (global-local, South-South, North-South) and with technical communities (OSM, free software and open data) as well as the humanitarian and development actors. &lt;/li&gt;
  83. &lt;li&gt;My intention is to provide feedback from my knowledge and experiences in many contexts and type of projects, including e.g. budget optimization to systematically encompass support for local emergent OSM communities.&lt;/li&gt;
  84. &lt;li&gt;As a board member, I will be striving for better future for all HOTOSM communities around the world which meets hopes and resolves concerns. &lt;/li&gt;
  85. &lt;li&gt;I will be enhancing the networking and collaboration with other HOT members globally and participated in fundraising activates through my all channels.&lt;/li&gt;
  86. &lt;li&gt;I will be using the many branches that my experience provided me with: strategy, project engineering (design/implementation), reporting, admin/business processes, outreach, networking, advising, grants writing/fundraising and the field-specific technical and organizational skills. &lt;/li&gt;
  87. &lt;li&gt;Create HOT as an inclusive organization in terms of decision making; specifically in project design tied to subventions, grants, or core funds.&lt;/li&gt;
  88. &lt;li&gt;Redefine relations and roles between the Board of Directors and Operational staffs (ED and Project Managers). &lt;/li&gt;
  89. &lt;li&gt;Ensure a shift towards a more active role for the Directors in strategy/planning/design/implementation/monitoring of operations and projects with the ED in charge of running the day to day business.
  90. *More importantly, working as HOT Board member will provide me the chance to learn global scale non-profit organizational management. &lt;/li&gt;
  91. &lt;/ul&gt;
  93. &lt;p&gt;Thank you very much for nominating me as a Board member of HOT. Vote for the humanity, vote for the deserving candidate. I wish continuous growth of HOT in near future.&lt;/p&gt;
  95. &lt;p&gt;Ahasanul Hoque (Candidate for HOTOSM Board Member)&lt;/p&gt;
  97. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;HOT Voting Memeber&lt;/a&gt;
  98. &lt;a href="" rel="nofollow"&gt;LinkdIn&lt;/a&gt;
  99. &lt;a href="" rel="nofollow"&gt;Twitter&lt;/a&gt;
  100. &lt;a href="" rel="nofollow"&gt;OSM&lt;/a&gt;
  101. Skype: ahasan4u&lt;/p&gt;
  102. </description>
  103.      <dc:creator>aHaSaN</dc:creator>
  104.      <pubDate>Thu, 23 Mar 2017 17:28:41 +0000</pubDate>
  105.      <comments></comments>
  106.      <geo:lat>23.7460686394087</geo:lat>
  107.      <geo:long>90.3785133361817</geo:long>
  108.      <georss:point>23.7460686394087 90.3785133361817</georss:point>
  109.    </item>
  110.    <item>
  111.      <title>the centre of Berlin</title>
  112.      <link></link>
  113.      <guid></guid>
  114.      <description>&lt;p&gt;This is a follow up of my recent diary entry about &lt;a href="" rel="nofollow"&gt;the centre of Rome&lt;/a&gt; and in parts a reply to &lt;a href="" rel="nofollow"&gt;Warin61&amp;#39;s comment&lt;/a&gt; to that post.&lt;/p&gt;
  116. &lt;h2&gt;Generally&lt;/h2&gt;
  118. &lt;p&gt;I believe the local people usually &lt;em&gt;know&lt;/em&gt; where the centre is. They tell you when you ask them. Give it a try, I bet you&amp;#39;ll see that you get similar answers.&lt;/p&gt;
  120. &lt;p&gt;I would expect this most central spot to be often in front of the townhall (maybe sometimes the cathedral) or the main market square (in traditional towns) or likely both. Maybe the train station can be such a center as well (in more recent towns which developed after the railway was invented).&lt;/p&gt;
  122. &lt;p&gt;One criterion could be: where would you go to protest something. If you were to gather together with &amp;quot;all&amp;quot; citizens, where would you go.&lt;/p&gt;
  124. &lt;p&gt;Streetsigns aren&amp;#39;t useful from my experience. Often the centre is inside the main pedestrian area (typical for Germany, where many historic city centres have been pedestrianized) and it is generally so big that you will get signs in the outskirts indicating &amp;quot;city centre&amp;quot;, but when you arrive there will not be a sign stating &amp;quot;this is the city centre&amp;quot;, the signs will simply stop indicating a centre when you are in a central area (they might indicate &amp;quot;all directions&amp;quot; now, but that&amp;#39;s a different story, maybe to be told another time).&lt;/p&gt;
  126. &lt;h2&gt;Exceptions&lt;/h2&gt;
  128. &lt;h3&gt;West Berlin&lt;/h3&gt;
  130. &lt;p&gt;In special cases there could even be several centres, e.g. Berlin (there might be a bit of a difference between big cities and smaller towns). For West-Berliners, the centre was likely Breitscheidplatz &lt;a href="" rel="nofollow"&gt;(in OSM)&lt;/a&gt; and as you can see it is also very close to the former main station of West Berlin, Bahnhof Zoologischer Garten).
  131. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  133. &lt;h3&gt;East Berlin&lt;/h3&gt;
  135. &lt;p&gt;For the people in East Berlin it was probably Alexanderplatz &lt;a href="" rel="nofollow"&gt;(in OSM)&lt;/a&gt; with the centre extending also to here &lt;a href="" rel="nofollow"&gt;(between tower and main town hall&lt;/a&gt;. There might be some other opinions because the former centre (castle) was also reclaimed by the officials, naturally (see below).
  136. This is Alexanderplatz, you can also see the prominent tower, visible from everywhere in the city. Huge towers are generally issueing a statement of centrality). There&amp;#39;s also a station, but it is not important as a train station (it is a very important underground station though, with 3 lines crossing):
  137. &lt;img src="" alt=""/&gt; &lt;/p&gt;
  139. &lt;h3&gt;Berlin central island&lt;/h3&gt;
  141. &lt;p&gt;Another central spot and maybe the official centre during the GDR, surely during the German Empire, is the palace (Stadtschloss) (now in reconstruction), &lt;a href="" rel="nofollow"&gt;(in OSM)&lt;/a&gt;, in times of the GDR  this was the place of the &amp;quot;palace of the republic&amp;quot; (Palast der Republik), at its side there is also the &lt;a href="" rel="nofollow"&gt;national council&lt;/a&gt;. &lt;/p&gt;
  143. &lt;p&gt;In this map from 1688 you can see the central island (yellow-green). By that time there were still 2 towns, &lt;em&gt;Berlin&lt;/em&gt; (purple) and &lt;em&gt;Cöln&lt;/em&gt; (yellow), and this origin is likely a reason that there&amp;#39;s some concurrency between Alexanderplatz and the castle. The castle is signed &lt;em&gt;a&lt;/em&gt;. Alexanderplatz is in Berlin, while the castle is in Cöln.
  144. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  146. &lt;p&gt;The Berlin castle 1900
  147. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  149. &lt;p&gt;After tearing down the castle and waiting 20 years (in the meantime they set up a permanent grandstand for their military parades on national holidays), the palace of the republic was errected (after the reunification, the Germans waited again 20 years, until they decided to demolish this &amp;quot;palace&amp;quot; and reconstruct something which imitates the imperial castle&amp;#39;s volume and facade).&lt;/p&gt;
  151. &lt;p&gt;Tearing down the castle, 1950
  152. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  154. &lt;p&gt;Grandstand for parades at the place of the former castle, 1952 (likely not perceived as a centre):
  155. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  157. &lt;p&gt;Palast der Republik, 1981:
  158. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  160. &lt;p&gt;Closeup of a parade in front of the Palast der Republik, 1978:
  161. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  163. &lt;p&gt;Palast der Republik from the inside, 1976
  164. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  166. &lt;p&gt;Here&amp;#39;s another map to illustrate that this is the &lt;em&gt;centre of the centre&lt;/em&gt; (also note how the avenue &amp;quot;Unter den Linden&amp;quot; points straight to the castle (=centre), for many kilometers, and bends right in front of the centre to pass the castle). In red the former castle, gray underneath the palace of the republic, to the north-east Alexanderplatz and its tower):
  167. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  169. &lt;p&gt;The current reconstruction called &lt;em&gt;Stadtschloss&lt;/em&gt;, (2015). Very visible how &lt;em&gt;Unter den Linden&lt;/em&gt; bends for the castle, &lt;a href="" rel="nofollow"&gt;see it also in a much bigger scale in OSM&lt;/a&gt;. This is the main road, leading straight to the castle (current federal road does not completely follow the old road, but I think you can get it) and at the time used by the king to got to his residence in Potsdam. What is now there is in part also result of more recent times: the Nazi plan by Albert Speer).
  170. &lt;img src="" alt=""/&gt;&lt;/p&gt;
  172. &lt;p&gt;The OSM crowd currently has set the centre a bit closer to the west, at the crossroads Unter den Linden and Friedrichstraße &lt;a href="" rel="nofollow"&gt;(in OSM)&lt;/a&gt;, it&amp;#39;s not completely off as this is a very central place (and in the historic parts of Berlin, pre-industrialization), but it isn&amp;#39;t a centre where you would go to gather for protest (these would be Pariser Platz in front of Brandenburg Gate and close to the Reichstag, or Alexanderplatz).&lt;/p&gt;
  174. &lt;p&gt;I will soon have a look how this node moved around in OSM with the years (and also look for the previous Berlin node that was deleted in 2008).&lt;/p&gt;
  175. </description>
  176.      <dc:creator>dieterdreist</dc:creator>
  177.      <pubDate>Thu, 23 Mar 2017 11:36:38 +0000</pubDate>
  178.      <comments></comments>
  179.      <geo:lat>52.5177716658863</geo:lat>
  180.      <geo:long>13.4009921550751</geo:long>
  181.      <georss:point>52.5177716658863 13.4009921550751</georss:point>
  182.    </item>
  183.    <item>
  184.      <title>email</title>
  185.      <link></link>
  186.      <guid></guid>
  187.      <description>&lt;p&gt;You can contact me at my email ID &lt;a href="mailto:[email protected]" rel="nofollow"&gt;[email protected]&lt;/a&gt;&lt;/p&gt;
  188. </description>
  189.      <dc:creator>Nagesh_Blr</dc:creator>
  190.      <pubDate>Thu, 23 Mar 2017 09:46:02 +0000</pubDate>
  191.      <comments></comments>
  192.    </item>
  193.    <item>
  194.      <title>Montauban, France vandalized</title>
  195.      <link></link>
  196.      <guid></guid>
  197.      <description>&lt;p&gt;A &lt;a href=";is_suspect=False&amp;is_whitelisted=True&amp;checked=All" rel="nofollow"&gt;new user&lt;/a&gt; deleted over a 100 features including the place node in the centre of Montauban, a large town in France.&lt;/p&gt;
  199. &lt;p&gt;&lt;img src="" alt=""/&gt;&lt;/p&gt;
  201. &lt;p&gt;Just reverted both these changesets:&lt;/p&gt;
  203. &lt;ul&gt;
  204. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/li&gt;
  205. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/li&gt;
  206. &lt;/ul&gt;
  208. &lt;p&gt;Caught and reverted in 15 hours! A few tools where one can review changesets from new users apart from the &lt;a href="" rel="nofollow"&gt;history tab&lt;/a&gt;:&lt;/p&gt;
  210. &lt;ul&gt;
  211. &lt;li&gt;&lt;a href=";is_whitelisted=All&amp;checked=All&amp;reasons=40" rel="nofollow"&gt;osmcha-newmapper&lt;/a&gt;&lt;/li&gt;
  212. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;osm-discussion&lt;/a&gt;&lt;/li&gt;
  213. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;osm-suspicous&lt;/a&gt;&lt;/li&gt;
  214. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;newestosm&lt;/a&gt;&lt;/li&gt;
  215. &lt;/ul&gt;
  216. </description>
  217.      <dc:creator>PlaneMad</dc:creator>
  218.      <pubDate>Thu, 23 Mar 2017 09:26:57 +0000</pubDate>
  219.      <comments></comments>
  220.      <geo:lat>44.0165213438775</geo:lat>
  221.      <geo:long>1.351318359375</geo:long>
  222.      <georss:point>44.0165213438775 1.351318359375</georss:point>
  223.    </item>
  224.    <item>
  225.      <title>RFC: wikidata-&gt;osm lookup table</title>
  226.      <link></link>
  227.      <guid></guid>
  228.      <description>&lt;p&gt;OpenStreetMap has a &lt;a href="" rel="nofollow"&gt;wikidata tag&lt;/a&gt; which lets us connect OSM objects to their corresponding Wikidata items.&lt;/p&gt;
  230. &lt;blockquote&gt;
  231. &lt;p&gt;(Technical note: it&amp;#39;s a &amp;quot;same as&amp;quot; relationship - i.e. the tag asserts that the two items in different systems refer to the same entity. However, sometimes things in OSM are split into multiple objects; and sometimes one object in OSM actually refers to multiple items in Wikidata. So it&amp;#39;s actually a &amp;quot;many-to-many&amp;quot; matching, not &amp;quot;one-to-one&amp;quot;: a single OSM object sometimes has multiple semicolon-separated Wikidata identifiers, and multiple OSM objects sometimes have the same Wikidata identifier.)&lt;/p&gt;
  232. &lt;/blockquote&gt;
  234. &lt;p&gt;There are &lt;strong&gt;over 600,000&lt;/strong&gt; OSM objects with the &amp;quot;wikidata&amp;quot; tag. OK great, job done? I mean, nothing&amp;#39;s ever &amp;quot;complete&amp;quot; in these big open-ended crowdsource projects, but if we have more than half a million crosslinks between the systems, that&amp;#39;s really good going.&lt;/p&gt;
  236. &lt;p&gt;BUT THERE&amp;#39;S A PROBLEM!&lt;/p&gt;
  238. &lt;p&gt;Using the tag to jump from OSM to Wikidata works fine. But from Wikidata to OSM? Well, there&amp;#39;s no &lt;em&gt;persistent&lt;/em&gt; way to link from wkd-&amp;gt;osm, simply because OSM&amp;#39;s identifiers are impermanent - they&amp;#39;re not guaranteed to continue existing, or to continue referring to the same thing. So it&amp;#39;s not particularly sensible to store OSM identifiers in Wikidata. Instead, an Overpass lookup is required.&lt;/p&gt;
  240. &lt;p&gt;For example, on &lt;a href="" rel="nofollow"&gt;the OSM Wikidata page&lt;/a&gt; I found this friendly &lt;a href="" rel="nofollow"&gt;Wikidata interface called &amp;quot;Reasonator&amp;quot;&lt;/a&gt; - all very nice, but instead of cross-linking immediately to the OSM object, it offers a little &amp;quot;Overpass&amp;quot; link which you can click to do a dynamic lookup.&lt;/p&gt;
  242. &lt;p&gt;The effect is that it makes Wikidata-&amp;gt;OSM connections indirect, obscured, only-for-those-who-know-they-want-it. If a Wikidata coder says &amp;quot;OK great how do I jump to the item in OSM?&amp;quot; you first have to teach them what Overpass is and how it relates to OSM, then how to use its query language, how many queries a day you&amp;#39;re allowed to do on Overpass... bleh.&lt;/p&gt;
  244. &lt;p&gt;PROPOSED SOLUTION&lt;/p&gt;
  246. &lt;p&gt;Pretty simple proposal, then: a script that produces a Wikidata-&amp;gt;OSM lookup table. This could be run as a weekly cron job perhaps (or something monitoring minutely diffs for any changed wikidata tag? dunno) and it could &lt;strong&gt;produce a lookup table that is easy for non-OSM users to consume&lt;/strong&gt;. For example, it could produce a big CSV file like this:&lt;/p&gt;
  248. &lt;pre&gt;&lt;code&gt; Q1002133,node/29541385
  249. Q1002826,node/20919015
  250. Q1002845,node/241795518
  251. Q1004173,way/38387732
  252. Q1004824,node/29164070
  253. Q1026205,node/410291638,relation/1061137
  254. Q1005234,relation/2797450
  255. ...
  256. &lt;/code&gt;&lt;/pre&gt;
  258. &lt;p&gt;and a JSON file like this:&lt;/p&gt;
  260. &lt;pre&gt;&lt;code&gt; {
  261. &amp;quot;Q1002133&amp;quot;: [[&amp;quot;node&amp;quot;,29541385]],
  262. &amp;quot;Q1002826&amp;quot;: [[&amp;quot;node&amp;quot;,20919015]],
  263. &amp;quot;Q1002845&amp;quot;: [[&amp;quot;node&amp;quot;,241795518]],
  264. &amp;quot;Q1004173&amp;quot;: [[&amp;quot;way&amp;quot;,38387732]],
  265. &amp;quot;Q1004824&amp;quot;: [[&amp;quot;node&amp;quot;,29164070]],
  266. &amp;quot;Q1026205&amp;quot;: [[&amp;quot;node&amp;quot;,410291638], [&amp;quot;relation&amp;quot;,1061137]],
  267. &amp;quot;Q1005234&amp;quot;: [[&amp;quot;relation&amp;quot;,2797450]],
  268. ...
  269. }
  270. &lt;/code&gt;&lt;/pre&gt;
  272. &lt;p&gt;and then what might be useful could be for these to be published at a stable location, for other programmers to make use of dynamically. The intention is to make it easy for someone with no OSM knowledge and no GIS knowledge to be able to hook OSM into their open data ecosystem.&lt;/p&gt;
  274. &lt;p&gt;I wrote &lt;a href="" rel="nofollow"&gt;a Python script that makes these lookup tables&lt;/a&gt;. On my home desktop, it takes about 2 minutes to scan the UK extract; for the whole planet file, it takes a lot longer... 90 minutes! Oof. (The CSV and JSON files produced are 14 MB &amp;amp; 19 MB in size.)&lt;/p&gt;
  276. &lt;p&gt;Your thoughts?&lt;/p&gt;
  277. </description>
  278.      <dc:creator>mcld</dc:creator>
  279.      <pubDate>Wed, 22 Mar 2017 22:27:48 +0000</pubDate>
  280.      <comments></comments>
  281.    </item>
  282.    <item>
  283.      <title>New A556 Link Road, Cheshire,UK</title>
  284.      <link></link>
  285.      <guid></guid>
  286.      <description>&lt;p&gt;Congratulations to the people of OpenStreetMap who are the first to show the actual newly completed route and links.  Not yet on TomTom or Google maps and don&amp;#39;t think about seeing it on OS. Brilliant.
  287. Robin&lt;/p&gt;
  288. </description>
  289.      <dc:creator>NiborM</dc:creator>
  290.      <pubDate>Wed, 22 Mar 2017 15:30:03 +0000</pubDate>
  291.      <comments></comments>
  292.    </item>
  293.    <item>
  294.      <title>The centre of Rome</title>
  295.      <link></link>
  296.      <guid></guid>
  297.      <description>&lt;p&gt;There a very useful feature in JOSM which I just discovered now: when looking at the history diffs of an object and you choose the coordinates tab, you get a map visualizing the geometry in a map. &lt;/p&gt;
  299. &lt;p&gt;From time to time people are moving the &lt;a href="" rel="nofollow"&gt;Rome node&lt;/a&gt;.&lt;/p&gt;
  301. &lt;p&gt;I found it interesting to see how the position changed by the time. This is the complete position history of the Rome node:&lt;/p&gt;
  303. &lt;p&gt;The node creation on 2007-10-15. Back then the local map was empty and a node anywhere near the centre was perfectly fine, but the editor decided after 10 minutes he could do better and already refined to a location close to where the central point commonly is associated with (the Campidoglio).
  304. &lt;img src="" alt="the node creation on 2007-10-15"/&gt;&lt;/p&gt;
  306. &lt;p&gt;A further refinement on 2007-10-22. Now the position is perfect (for our means), it indicates the centre of the Campidoglio with the equestrian statue of Marcus Aurelius.
  307. &lt;img src="" alt="further refinement on 2007-10-22"/&gt;&lt;/p&gt;
  309. &lt;p&gt;This is the Piazza del Campidoglio with the equestrian statue in the centre, you can also note the concentric pavement structure indicating the centre:
  310. &lt;img src="" alt="Piazza del Campidoglio"/&gt;&lt;/p&gt;
  312. &lt;p&gt;Now comes a longer period of people &amp;quot;touching&amp;quot; the node without actually changing it noticably. Take a look at the distance indicator:
  313. &lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  315. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  317. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  319. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  321. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  323. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  325. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  327. &lt;p&gt;&lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  329. &lt;p&gt;Until someone comes along and decides in 2011 to relocate the centre close to the Spanish Steps (although this is a famous place, it is not generally considered the &amp;quot;centre point&amp;quot;:
  330. &lt;img src="" alt="move to the Spanish Steps"/&gt;&lt;/p&gt;
  332. &lt;p&gt;Just one minute later, the same user slightly adjusts the position, but keeps it at the Spanish Steps (Piazza di Spagna):
  333. &lt;img src="" alt="minor refinement"/&gt;&lt;/p&gt;
  335. &lt;p&gt;6 months later I relocate the node to the Capitoline Square (Piazza del Campidoglio):
  336. &lt;img src="" alt="relocation to Piazza del Campidoglio"/&gt;&lt;/p&gt;
  338. &lt;p&gt;3 years later another user starts readjusting the exact position (maybe in an attempt to optimize the rendering label positions and reduce label omissions):
  339. &lt;img src="" alt="slightly moving away from the centre"/&gt;&lt;/p&gt;
  341. &lt;p&gt;Some months later, the node is moved further away from the center to the border of the square:
  342. &lt;img src="" alt="moving to the border"/&gt;&lt;/p&gt;
  344. &lt;p&gt;3 months after this, there&amp;#39;s a new significant relocation, this time to Piazza Navona (while it is an important place, it is not the &amp;quot;centre&amp;quot;):
  345. &lt;img src="" alt="relocating to Piazza Navona"/&gt;&lt;/p&gt;
  347. &lt;p&gt;The same use relocates the node, 2 months later, to the Piazza delle Rotonda (square in front of the Pantheon):
  348. &lt;img src="" alt="relocating to Piazza Navona"/&gt;&lt;/p&gt;
  350. &lt;p&gt;That&amp;#39;s where we&amp;#39;re still right now, but I think I will relocate it to where I believe it belongs and where most of the other mappers also have seen for it the place to be. Well, actually there&amp;#39;s another spot which might be brought into discussion as well: it is the place of a column just a stone&amp;#39;s throw away on the Roman Forum, close to the temple of Saturn, errected the Emperor Augustus, which is the official start point of the &amp;quot;Vie Consolarie&amp;quot; (main arterial roads, historically until today).&lt;/p&gt;
  351. </description>
  352.      <dc:creator>dieterdreist</dc:creator>
  353.      <pubDate>Wed, 22 Mar 2017 11:50:49 +0000</pubDate>
  354.      <comments></comments>
  355.      <geo:lat>41.8932600557309</geo:lat>
  356.      <geo:long>12.482987344265</geo:long>
  357.      <georss:point>41.8932600557309 12.482987344265</georss:point>
  358.    </item>
  359.    <item>
  360.      <title>Храм Вознесения в Жуковском (2016)</title>
  361.      <link></link>
  362.      <guid></guid>
  363.      <description>&lt;p&gt;Добавил на карту новый православный храм Вознесения (освящён в 2016 году). Добавил по знанию местоположения символическим прямоугольником (никакие карты не обрисовывал, хотя сверился с аэрокосмическим снимком Google). На Bing карте совсем ничего не видно, чтобы там было строение. Один лес. Ощущение, что этот кусочек карты очень старый, хотя указывается 2017 год в нижнем левом углу.&lt;/p&gt;
  364. </description>
  365.      <dc:creator>Lunyo</dc:creator>
  366.      <pubDate>Wed, 22 Mar 2017 05:46:26 +0000</pubDate>
  367.      <comments></comments>
  368.    </item>
  369.    <item>
  370.      <title>E. Perry Parkway in Cherry Hills Village</title>
  371.      <link></link>
  372.      <guid></guid>
  373.      <description>&lt;p&gt;Updated with notes on extension of E. Perry Parkway North of Belleview Ave.&lt;/p&gt;
  374. </description>
  375.      <dc:creator>Terisa</dc:creator>
  376.      <pubDate>Tue, 21 Mar 2017 14:35:26 +0000</pubDate>
  377.      <comments></comments>
  378.      <geo:lat>39.625171</geo:lat>
  379.      <geo:long>-104.93443</geo:long>
  380.      <georss:point>39.625171 -104.93443</georss:point>
  381.    </item>
  382.    <item>
  383.      <title>Harare gets a new name</title>
  384.      <link></link>
  385.      <guid></guid>
  386.      <description>&lt;p&gt;&lt;img src="" alt=""/&gt;&lt;/p&gt;
  388. &lt;p&gt;Yesterday, &lt;a href="" rel="nofollow"&gt;Paris became a bicycle shop named France&lt;/a&gt; and today the Zimbabwe capital &lt;a href="" rel="nofollow"&gt;Harare became Hwinidi offices&lt;/a&gt;. This time the edit was from iD. The Mapbox data team caught this while reviewing edits on &lt;a href="" rel="nofollow"&gt;;/a&gt; around 13 hours after the edit.&lt;/p&gt;
  389. </description>
  390.      <dc:creator>PlaneMad</dc:creator>
  391.      <pubDate>Tue, 21 Mar 2017 12:13:23 +0000</pubDate>
  392.      <comments></comments>
  393.      <geo:lat>-17.8315572568659</geo:lat>
  394.      <geo:long>31.0459899902344</geo:long>
  395.      <georss:point>-17.8315572568659 31.0459899902344</georss:point>
  396.    </item>
  397.    <item>
  398.      <title>Notes save lives.</title>
  399.      <link></link>
  400.      <guid></guid>
  401.      <description>&lt;p&gt;Yesterday I saw that the hospital in construction in Mechelen looked like a real hospital on the map, though it was surrounded with an area &amp;quot;landuse=construction&amp;quot;.
  402. As I am a beginner I dared not change this.
  403. I placed a note, and as this area on the map is not a canvas for notes pointillism yet, it was quickly discovered  and corrected by a more experienced mapper.
  404. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  405. </description>
  406.      <dc:creator>philippec</dc:creator>
  407.      <pubDate>Tue, 21 Mar 2017 08:55:38 +0000</pubDate>
  408.      <comments></comments>
  409.    </item>
  410.    <item>
  411.      <title>OSM Diary HOT Board Nomination</title>
  412.      <link></link>
  413.      <guid></guid>
  414.      <description>&lt;p&gt;Dear HOT members,&lt;/p&gt;
  416. &lt;p&gt;I have accepted the kind nomination by Martin and Blake, as I would love to join the HOT Board to put my knowledge, skills, network and passion to use for the strategic planning for the future of HOT, and to support the community as a researcher, geographer, disastermapper as well as networker. &lt;/p&gt;
  418. &lt;p&gt;HOT has come a long way since the Haiti earthquakes. We have a growing number of HOT members and volunteers that are active in mapping, working groups and in building and directing our community. Thanks to this growing community we also have increasing OSM data coverage in vulnerable and disaster affected countries, as well as more and more advanced tools to facilitate the data collection and validation. Therefore, HOT became an increasingly globally distributed and acknowledged community, with a growing number of local chapters that has proven its potential, effectiveness and value in numerous disaster responses, as well as long-term community mapping and Missing Maps projects.&lt;/p&gt;
  420. &lt;p&gt;There are however also open questions, e.g.:&lt;/p&gt;
  422. &lt;blockquote&gt;
  423. &lt;ul&gt;
  424. &lt;li&gt;How well do we know our community, and what are their needs?&lt;/li&gt;
  425. &lt;li&gt;What is the impact of our work?* How can we better identify and meet the needs of potential data users?&lt;/li&gt;
  426. &lt;li&gt;How can we detect deficiencies in the OSM data, improve validation and data maintenance processes, and assure a certain level of data quality?&lt;/li&gt;
  427. &lt;li&gt;How can we better support and encourage local mapping communities, and link remote and local mappers?&lt;/li&gt;
  428. &lt;/ul&gt;
  429. &lt;/blockquote&gt;
  431. &lt;p&gt;As the work of HOT members like Nama Budhathoki, Robert Soden and Martin Dittus and partnerships between the &lt;a href="" rel="nofollow"&gt;disastermappers heidelberg&lt;/a&gt;/ &lt;a href="" rel="nofollow"&gt;GIScience Research Group of Heidelberg University&lt;/a&gt; and Missing Maps have shown, collaborations between researchers and our mapping community can help to address these questions and challenges.
  432. Over the last couple of years, I have learned a lot about the importance of HOT and OSM for vulnerable and disaster prone countries and decision makers through my work with &lt;a href="" rel="nofollow"&gt;Kathmandu Living Labs&lt;/a&gt;, HOT and Missing Maps, my projects in Heidelberg and by conducting and presenting research about OSM, HOT and disaster mapping to an international audience. I shared my experiences by teaching students in Heidelberg and beyond about the work of the HOT community and organizing open Mapathons and workshops with the disastermappers heidelberg initiative in the scope of my studies as well as in the scope of my work at the GIScience Research Group. Working at the &lt;a href="" rel="nofollow"&gt;disaster management and disastermapping department&lt;/a&gt;, I am now positioned at the intersection of research, application development, OSM interested data consumers and the HOT and OSM community. I would love to put this position, my network, my knowledge and research skills to use in the HOT Board and build a bridge between researchers, developers, the data consumers  and the HOT and OSM community to address our questions and challenges within and with the community and raise more awareness in the international world of academia and disaster management about the potentials of HOT and OSM and the amazing things a volunteer community can achieve. &lt;/p&gt;
  433. </description>
  434.      <dc:creator>Milli1201</dc:creator>
  435.      <pubDate>Mon, 20 Mar 2017 20:17:06 +0000</pubDate>
  436.      <comments></comments>
  437.      <geo:lat>49.4183891770582</geo:lat>
  438.      <geo:long>8.67554068565369</geo:long>
  439.      <georss:point>49.4183891770582 8.67554068565369</georss:point>
  440.    </item>
  441.    <item>
  442.      <title>Mapper of the Month:  Lauri Kytömaa (Finland)</title>
  443.      <link></link>
  444.      <guid></guid>
  445.      <description>&lt;p&gt;The interview is published on the &lt;a href="" rel="nofollow"&gt;Belgian OSM Website&lt;/a&gt;&lt;/p&gt;
  446. </description>
  447.      <dc:creator>escada</dc:creator>
  448.      <pubDate>Mon, 20 Mar 2017 19:48:27 +0000</pubDate>
  449.      <comments></comments>
  450.    </item>
  451.    <item>
  452.      <title>3D карты OSM</title>
  453.      <link></link>
  454.      <guid></guid>
  455.      <description>&lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  456. </description>
  457.      <dc:creator>DeadAngel</dc:creator>
  458.      <pubDate>Mon, 20 Mar 2017 17:22:00 +0000</pubDate>
  459.      <comments></comments>
  460.    </item>
  461.    <item>
  462.      <title>Paris is a bicycle shop</title>
  463.      <link></link>
  464.      <guid></guid>
  465.      <description>&lt;p&gt;&lt;img src="" alt=""/&gt;&lt;/p&gt;
  467. &lt;p&gt;The Paris city node got renamed to &lt;a href="" rel="nofollow"&gt;&lt;code&gt;France&lt;/code&gt; and tagged with &lt;code&gt;shop=bicycle&lt;/code&gt; yesterday&lt;/a&gt;. This was found and &lt;a href="" rel="nofollow"&gt;reverted by user:Chetan_Gowda&lt;/a&gt; from the Mapbox data team 27 hours later. For some reason the tiles still show a shop, while the name has got fixed.&lt;/p&gt;
  469. &lt;p&gt;While inspecting the Paris node, another user seemed to have renamed the French name to &lt;a href="" rel="nofollow"&gt;&lt;code&gt;Algerie&lt;/code&gt; 6 month ago&lt;/a&gt;. This was fixed after 4 hours.&lt;/p&gt;
  471. &lt;p&gt;Both edits came through, but this is just as simple an edit through any other editor. Its surprising no local mappers noticed this.&lt;/p&gt;
  472. </description>
  473.      <dc:creator>PlaneMad</dc:creator>
  474.      <pubDate>Mon, 20 Mar 2017 16:50:33 +0000</pubDate>
  475.      <comments></comments>
  476.      <geo:lat>48.8566134600841</geo:lat>
  477.      <geo:long>2.35150068998337</geo:long>
  478.      <georss:point>48.8566134600841 2.35150068998337</georss:point>
  479.    </item>
  480.    <item>
  481.      <title>Processing MapSwipe output for the HOT Tasking Manager</title>
  482.      <link></link>
  483.      <guid></guid>
  484.      <description>&lt;p&gt;Hello everyone,&lt;/p&gt;
  486. &lt;p&gt;MapSwipe - the mobile app that allows users to swiftly search through satellite imagery and identify huts, houses and villages - is accelerating the Missing Maps mapping process. Its output shapefiles, comprising only tasks identified as containing huts, houses, or villages, allow Missing Map&amp;#39;s task creators to omit from projects any tasks without huts, houses and villages. In short, any tasks that do not require mapping.&lt;/p&gt;
  488. &lt;p&gt;However, some areas covered by MapSwipe output tasks are quite likely to have already been mapped in OpenStreetMap. A little processing of MapSwipe&amp;#39;s output shapefile can make it even more effective!&lt;/p&gt;
  490. &lt;p&gt;First, MapSwipe output can be downloaded at &lt;a href="" rel="nofollow"&gt;;/a&gt; or using the MapSwipe Tools which can be downloaded at &lt;a href="" rel="nofollow"&gt;;/a&gt;.&lt;/p&gt;
  492. &lt;p&gt;Using overpass turbo:&lt;/p&gt;
  494. &lt;p&gt;1.1. Download the area&amp;#39;s building=yes and landuse=residential GeoJOSN files (Wizard &amp;gt; build and run query, then Export &amp;gt; as goeJOSN). The building data usually take a little while to download.&lt;/p&gt;
  496. &lt;p&gt;Using QGIS:&lt;/p&gt;
  498. &lt;p&gt;2.1 Convert the GeoJOSN files into shapefiles (Layer &amp;gt; Save As...).&lt;/p&gt;
  500. &lt;p&gt;2.2. Merge the two shapefiles (Vector &amp;gt; Data Management Tools &amp;gt; Merge Shapefiles to One...).&lt;/p&gt;
  502. &lt;p&gt;2.3. Clip the merge shapefile to the MapSwipe output (Vector &amp;gt; Geoprocessing Tools &amp;gt; Clip...).&lt;/p&gt;
  504. &lt;p&gt;2.4. Select MapSwipe tasks with the merge shapefile within their boundaries (Vector &amp;gt; Research Tools &amp;gt; Select by Location...).&lt;/p&gt;
  506. &lt;p&gt;2.5. Export selected tasks as a shapefile (Layer &amp;gt; Save As...).&lt;/p&gt;
  508. &lt;p&gt;2.6. Invert step 2.4&amp;#39;s selection (right-click on layer &amp;gt; Open Attribute Table &amp;gt; Invert selection).&lt;/p&gt;
  510. &lt;p&gt;2.7. Export selected tasks as a shapefile (Layer &amp;gt; Save As...).&lt;/p&gt;
  512. &lt;p&gt;The shapefile created in step 2.7 will partly dictate the HOT Tasking Manager project. Further processing of the shapefile created in step 2.5 is required.&lt;/p&gt;
  514. &lt;p&gt;Using QGIS:&lt;/p&gt;
  516. &lt;p&gt;3.1. Clip the landuse=residential  shapefile to the shapefile created in step 2.5 (Vector &amp;gt; Geoprocessing Tools &amp;gt; Clip...).&lt;/p&gt;
  518. &lt;p&gt;3.2. Select the clipped landuse=residential shapefile&amp;#39;s residential areas with the building=yes shapefile within their boundaries (Vector &amp;gt; Research Tools &amp;gt; Select by Location...).&lt;/p&gt;
  520. &lt;p&gt;3.3. Invert step 3.2&amp;#39;s selection (right-click on layer &amp;gt; Open Attribute Table &amp;gt; Invert selection).&lt;/p&gt;
  522. &lt;p&gt;3.4. Export selected residential areas as a shapefile (Layer &amp;gt; Save As...).&lt;/p&gt;
  524. &lt;p&gt;3.5. Select the shapefile created in step 2.5&amp;#39;s tasks with the shapefile created in step 3.4&amp;#39;s residential areas within them (Vector &amp;gt; Research Tools &amp;gt; Select by Location...).&lt;/p&gt;
  526. &lt;p&gt;3.6. Export the shapefile created in step 2.5&amp;#39;s selected tasks as a shapefile (Layer &amp;gt; Save As...).&lt;/p&gt;
  528. &lt;p&gt;Finally, using QGIS:&lt;/p&gt;
  530. &lt;p&gt;4.1. Merge the shapefiles created in step 2.7 and 3.6 (Vector &amp;gt; Data Management Tools &amp;gt; Merge Shapefiles to One...).&lt;/p&gt;
  532. &lt;p&gt;4.2. Convert the shapefile created in step 4.1 into a GeoJOSN file (Layer &amp;gt; Save As...).&lt;/p&gt;
  534. &lt;p&gt;The GeoJOSN file created in step 4.2 is what is used to create a more streamlined HOT Tasking Manager project. In brief, it constitutes MapSwipe&amp;#39;s output minus tasks already mapped but including residential areas without buildings within them.&lt;/p&gt;
  536. &lt;p&gt;Thanks for reading,&lt;/p&gt;
  538. &lt;p&gt;Paul&lt;/p&gt;
  539. </description>
  540.      <dc:creator>pjstewart1984</dc:creator>
  541.      <pubDate>Mon, 20 Mar 2017 11:41:37 +0000</pubDate>
  542.      <comments></comments>
  543.    </item>
  544.    <item>
  545.      <title>Streams &amp; Trees in Gedling, Notts</title>
  546.      <link></link>
  547.      <guid></guid>
  548.      <description>&lt;p&gt;Mapping in Gedling on Saturday 18 March in foul weather (it was raining hard; goodness me, could this be England by any chance?) (well, yes). My &lt;a href="" rel="nofollow"&gt;new smartphone&lt;/a&gt; turned out to NOT be as England-proof as my ISODRY-10000 jacket, but that&amp;#39;s another story.&lt;/p&gt;
  550. &lt;p&gt;There were one or two pleasant scenes &amp;amp; I thought to share them with you.&lt;/p&gt;
  552. &lt;p&gt;Right at the start of the track was an &lt;a href="" rel="nofollow"&gt;un-named recreation garden&lt;/a&gt; on &lt;a href="" rel="nofollow"&gt;Burton Road&lt;/a&gt;. It contained some yew trees (&lt;a href="" rel="nofollow"&gt;at the right&lt;/a&gt;) which sometimes is a sign of a former religious establishment in England. A neighbour said that there used to be a &lt;em&gt;“big house, with stables”&lt;/em&gt; at the rear, but had no other information.&lt;/p&gt;
  554. &lt;p&gt;&lt;img src="" alt="gardens, burton road gedling"/&gt;&lt;/p&gt;
  556. &lt;p&gt;Our &lt;a href="" rel="nofollow"&gt;second view&lt;/a&gt; is classic for a country house, except that it is within the suburbs, hidden away at the bottom of an unadopted road. However, the location &lt;em&gt;does&lt;/em&gt; feature yew trees &amp;amp; willow hanging over the &lt;a href="" rel="nofollow"&gt;Ouse Dyke&lt;/a&gt; (not the prettiest name, but clearly the reason that &lt;a href=",_Nottinghamshire" rel="nofollow"&gt;Gedling &amp;amp; it&amp;#39;s 678 A.D. church&lt;/a&gt; were established here in the first place) (the &lt;a href="" rel="nofollow"&gt;current church&lt;/a&gt; is 1089 A.D., but there were earlier versions):–&lt;/p&gt;
  558. &lt;p&gt;&lt;img src="" alt="willow over ouse dyke on burton close"/&gt;&lt;/p&gt;
  560. &lt;p&gt;The &lt;a href="" rel="nofollow"&gt;next view&lt;/a&gt; seems a world away from the previous one but is actually very close, simply on the other side of the dyke. The one building in view is on the other bank of the dyke from &lt;a href="" rel="nofollow"&gt;Brooklands Drive&lt;/a&gt;, which is immediately behind me as I shot this photo.&lt;/p&gt;
  562. &lt;p&gt;&lt;img src="" alt="Ouse Dyke bank, Brooklands Drive, gedling"/&gt;&lt;/p&gt;
  564. &lt;p&gt;I had a problem mapping that &lt;a href="" rel="nofollow"&gt;small section of land&lt;/a&gt;. First of all I was going to use:–&lt;/p&gt;
  566. &lt;blockquote&gt;
  567. &lt;p&gt;&lt;em&gt;‘Geography|Nature|Scrub’&lt;/em&gt;&lt;br/&gt;
  568. Bare lower lying uncultivated land with bushes but little or no tree cover&lt;/p&gt;
  569. &lt;/blockquote&gt;
  571. &lt;p&gt;...but that doesn&amp;#39;t fit. The trouble is that there is nothing within &lt;em&gt;‘Geography|Land Use’&lt;/em&gt; that fits. In the end I used this:–&lt;/p&gt;
  573. &lt;blockquote&gt;
  574. &lt;p&gt;&lt;em&gt;‘Geography|Nature|Wood’&lt;/em&gt;&lt;br/&gt;
  575. Woodland where timber production does not dominate use&lt;/p&gt;
  576. &lt;/blockquote&gt;
  578. &lt;p&gt;...which is about as close as I can get, I think, even though it is council-cultivated land rather than &lt;em&gt;‘natural’&lt;/em&gt;.&lt;/p&gt;
  580. &lt;p&gt;PS&lt;br/&gt;
  581. If you have admin or Mod rights, then please remove &lt;a href="" rel="nofollow"&gt;Mlafagos&lt;/a&gt; + the comment they made (below); their account was created today as Profile Spam, and the comment is simple spam bait for the Search-Engines.&lt;/p&gt;
  582. </description>
  583.      <dc:creator>alexkemp</dc:creator>
  584.      <pubDate>Sun, 19 Mar 2017 22:17:34 +0000</pubDate>
  585.      <comments></comments>
  586.      <geo:lat>52.9717098270992</geo:lat>
  587.      <geo:long>-1.07574939764163</geo:long>
  588.      <georss:point>52.9717098270992 -1.07574939764163</georss:point>
  589.    </item>
  590.    <item>
  591.      <title>Simple gardening/QA workflow: Improve old ways</title>
  592.      <link></link>
  593.      <guid></guid>
  594.      <description>&lt;p&gt;OSM can never be finished, we just keep improving the map. Our tools and sources get better. We can get better aerial imagery, and this means older data can be a little fuzzy. There&amp;#39;s a simple way to improve OSM by looking at old data and seeing if you can improve it.&lt;/p&gt;
  596. &lt;p&gt;First enable the &lt;a href="" rel="nofollow"&gt;TODO list plugin&lt;/a&gt; if you haven&amp;#39;t already (seriously, it&amp;#39;s a great plugin), and enable that window on the right hand side. Then download a large area. The &lt;a href="" rel="nofollow"&gt;JOSM Continuous Downloader plugin&lt;/a&gt; can help here. The we can use &lt;a href="" rel="nofollow"&gt;JOSM&amp;#39;s search functionality&lt;/a&gt; to find old data. Let&amp;#39;s try to fix up ways which haven&amp;#39;t been changed since 2010. Press Control-F to bring up the search box. Then enter &lt;code&gt;timestamp:/2010 type:way&lt;/code&gt;, and press enter. All old ways will be selected. Press the Add button to these to the TODO list. Double click on the first entry to start working on it. Compare it to the aerial imagery, and fix up it&amp;#39;s geometry if needed. &lt;a href="" rel="nofollow"&gt;JOSM&amp;#39;s improve way geometry feature&lt;/a&gt; (press &lt;code&gt;W&lt;/code&gt;) can make this easier. When you&amp;#39;ve finished with this way, press &lt;code&gt;]&lt;/code&gt; to go to the next object. Keep going as long as you want. Upload as often as you want.&lt;/p&gt;
  598. &lt;p&gt;With regular &amp;quot;gardening&amp;quot; tasks, OSM will be gradually improved and made better.&lt;/p&gt;
  599. </description>
  600.      <dc:creator>rorym</dc:creator>
  601.      <pubDate>Sun, 19 Mar 2017 17:23:14 +0000</pubDate>
  602.      <comments></comments>
  603.    </item>
  604.  </channel>
  605. </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