[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>I-295 Redesignation</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  20. &lt;p&gt;I have updated some of the missing roadway name to I-295.
  21. But why the roadway shield still shows I-95 (Zoom in on roadway section and observe roadway label in the back)&lt;/p&gt;
  22. </description>
  23.      <dc:creator>BT1</dc:creator>
  24.      <pubDate>Fri, 20 Apr 2018 18:24:03 +0000</pubDate>
  25.      <comments></comments>
  26.      <geo:lat>40.28532</geo:lat>
  27.      <geo:long>-74.72357</geo:long>
  28.      <georss:point>40.28532 -74.72357</georss:point>
  29.    </item>
  30.    <item>
  31.      <title>OpenStreetMap Carto release v4.10.0</title>
  32.      <link></link>
  33.      <guid></guid>
  34.      <description>&lt;p&gt;Dear all,&lt;/p&gt;
  36. &lt;p&gt;Today, v4.10.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released. Once changes are deployed on the it will take couple of days before all tiles show the new rendering.&lt;/p&gt;
  38. &lt;p&gt;Changes include&lt;/p&gt;
  40. &lt;ul&gt;
  41. &lt;li&gt;Adding rendering for historic=castle and historic=manor&lt;/li&gt;
  42. &lt;li&gt;Adding rendering office=* as dots + names&lt;/li&gt;
  43. &lt;li&gt;Adding rendering for waterway=waterfall&lt;/li&gt;
  44. &lt;li&gt;Adding place=square name rendering for nodes&lt;/li&gt;
  45. &lt;li&gt;Adding rendering for big natural=bay&lt;/li&gt;
  46. &lt;li&gt;Adding rendering for leisure=beach_resort&lt;/li&gt;
  47. &lt;li&gt;Adding rendering for amenity=parking_space&lt;/li&gt;
  48. &lt;li&gt;Adding rendering of aerialway=zip_line&lt;/li&gt;
  49. &lt;li&gt;Adding rendering for shop=bed&lt;/li&gt;
  50. &lt;li&gt;Adding rendering for shop=video_games&lt;/li&gt;
  51. &lt;li&gt;Adding halo to roads on z6 and z7&lt;/li&gt;
  52. &lt;li&gt;Extending intermittent waterbody rendering to landuse=basin&lt;/li&gt;
  53. &lt;li&gt;Moving highway=mini_roundabout rendering to higher zoom level&lt;/li&gt;
  54. &lt;li&gt;Dropping waterway=derelict_canal rendering&lt;/li&gt;
  55. &lt;li&gt;Small documentation and code fixes&lt;/li&gt;
  56. &lt;/ul&gt;
  58. &lt;p&gt;Thanks to all the contributors for this release, including d3d9, doktorpixel14 and hikemaniac, new contributors.&lt;/p&gt;
  60. &lt;p&gt;For a full list of commits, see &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  62. &lt;p&gt;As always, we welcome any bug reports at &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  63. </description>
  64.      <dc:creator>kocio</dc:creator>
  65.      <pubDate>Fri, 20 Apr 2018 14:43:34 +0000</pubDate>
  66.      <comments></comments>
  67.    </item>
  68.    <item>
  69.      <title>Welcome to OpenStreetMap!</title>
  70.      <link></link>
  71.      <guid></guid>
  72.      <description>&lt;p&gt;— Yay, new mapper! Welcome to OpenStreetMap!&lt;/p&gt;
  74. &lt;p&gt;— I see you are using wrong tags. Please read Map Features and don&amp;#39;t come back until you&amp;#39;re done. I don&amp;#39;t care if it&amp;#39;s too long. Go to Google Map Maker if you&amp;#39;re intimidated.&lt;/p&gt;
  76. &lt;p&gt;— I don&amp;#39;t know you. Please go to [email protected] mailing list and introduce yourself and reasons for your mapping. Yes, I know you have to sign up using some obscure web page, and then receive unwanted mail for eternity. But rules are rules. Go do it, or leave.&lt;/p&gt;
  78. &lt;p&gt;— I see you work for a mapping company. I will be watching you, because you do not care for our map. None of you do. Yes, I am working at such company too, but I care.&lt;/p&gt;
  80. &lt;p&gt;— I caught you not tracing from Bing like the rest of us. Please explain your sources and acquire specific permissions for using these. Or better stop.&lt;/p&gt;
  82. &lt;p&gt;— I see that among 500 buildings you&amp;#39;ve traced, 20 have been recently demolished. I know that they are still on imagery and in the registry. But it looks like your quality of mapping will never reach mine. Please go away and never come back.&lt;/p&gt;
  84. &lt;p&gt;— Hey, I&amp;#39;ve seen more edits from you. I think we&amp;#39;ve discussed it. I don&amp;#39;t care if they are good, I have reverted them. Please do not come back.&lt;/p&gt;
  86. &lt;p&gt;...&lt;/p&gt;
  88. &lt;p&gt;— Hi new mapper, welcome to OpenStreetMap!&lt;/p&gt;
  89. </description>
  90.      <dc:creator>Zverik</dc:creator>
  91.      <pubDate>Fri, 20 Apr 2018 14:16:27 +0000</pubDate>
  92.      <comments></comments>
  93.    </item>
  94.    <item>
  95.      <title>Velo1</title>
  96.      <link></link>
  97.      <guid></guid>
  98.      <description>&lt;p&gt;123&lt;/p&gt;
  99. </description>
  100.      <dc:creator>Strangelove23</dc:creator>
  101.      <pubDate>Fri, 20 Apr 2018 14:14:00 +0000</pubDate>
  102.      <comments></comments>
  103.      <geo:lat>56.3087291850169</geo:lat>
  104.      <geo:long>43.9834924954087</geo:long>
  105.      <georss:point>56.3087291850169 43.9834924954087</georss:point>
  106.    </item>
  107.    <item>
  108.      <title>Speed limits</title>
  109.      <link></link>
  110.      <guid></guid>
  111.      <description>&lt;p&gt;Hallo wie sieht man tempo Limits auf der karte  und wie kann Mann sie korrigieren &lt;/p&gt;
  113. &lt;p&gt;l.g  rs&lt;/p&gt;
  114. </description>
  115.      <dc:creator>Reinhard Schölzhorn</dc:creator>
  116.      <pubDate>Fri, 20 Apr 2018 11:49:40 +0000</pubDate>
  117.      <comments></comments>
  118.      <geo:lat>46.6709727418852</geo:lat>
  119.      <geo:long>11.1552429512035</geo:long>
  120.      <georss:point>46.6709727418852 11.1552429512035</georss:point>
  121.    </item>
  122.    <item>
  123.      <title>Viewing the maps</title>
  124.      <link></link>
  125.      <guid></guid>
  126.      <description>&lt;p&gt;I would like to be able to view the maps normally without the screen covered in &amp;#39;X&amp;#39;s or green Ticks. How do I remove these from my view please.&lt;/p&gt;
  127. </description>
  128.      <dc:creator>CraigEmm99</dc:creator>
  129.      <pubDate>Fri, 20 Apr 2018 09:20:35 +0000</pubDate>
  130.      <comments></comments>
  131.    </item>
  132.    <item>
  133.      <title>[GitHub] OSM Resources List!</title>
  134.      <link></link>
  135.      <guid></guid>
  136.      <description>&lt;h1&gt;OSM Links&lt;/h1&gt;
  138. &lt;p&gt;&lt;strong&gt;An open list of useful resources relating to OpenStreetMap.&lt;/strong&gt;&lt;/p&gt;
  140. &lt;h2&gt;About&lt;/h2&gt;
  142. &lt;p&gt;This repository aims to be a community-maintainted list of resources regarding OpenStreetMap. The list can contain anything from materials for contributors, guides for newcomers, etc.&lt;/p&gt;
  144. &lt;h3&gt;&lt;a href="" rel="nofollow"&gt;Link&lt;/a&gt;&lt;/h3&gt;
  145. </description>
  146.      <dc:creator>rivermont</dc:creator>
  147.      <pubDate>Fri, 20 Apr 2018 00:33:57 +0000</pubDate>
  148.      <comments></comments>
  149.    </item>
  150.    <item>
  151.      <title>How We Improve OpenStreetMap</title>
  152.      <link></link>
  153.      <guid></guid>
  154.      <description>&lt;p&gt;At Development Seed we’re always looking for ways to contribute to open source projects. Recently, we started thinking about how we might be able to help improve the OpenStreetMap (OSM) ecosystem of tools. Of course we had our suspicions, but to insure whatever we came up with had the whole OSM community in mind, we started with a round of user interviews. Below you’ll find our process and findings, in hopes that we can all start supporting tools to serve the greater community.&lt;/p&gt;
  156. &lt;h4&gt;Process&lt;/h4&gt;
  158. &lt;p&gt;User interviews are essentially what they sound like, interviewing users to better understand who they are, what they do, how they use OSM tools, and what they feel could be improved within the OSM ecosystem. To try and capture the opinions of such a large group, we broke up the community into 3 different groups:&lt;/p&gt;
  160. &lt;ul&gt;
  161. &lt;li&gt;Inexperienced mappers, ones who had only mapped a few times&lt;/li&gt;
  162. &lt;li&gt;Experienced mappers, including people who map for their work vs people who map on their own&lt;/li&gt;
  163. &lt;li&gt;People who want map data, people at organizations like American Red Cross or HOT&lt;/li&gt;
  164. &lt;/ul&gt;
  166. &lt;p&gt;We interviewed at least 4 people from each group, to ensure that we were hearing from a number of different voices. For the 19 different people we talked to, from Belgium to Japan, we asked them a &lt;a href="" rel="nofollow"&gt;base set of questions&lt;/a&gt;, and asked follow up questions based on the discussion. There were a lot of interesting patterns and ideas that emerged from our conversations:&lt;/p&gt;
  168. &lt;h4&gt;Having a community is key&lt;/h4&gt;
  170. &lt;ul&gt;
  171. &lt;li&gt;Most mappers want to map what they know and are concerned about what is nearby to them. This seemed to outweigh the desire to contribute to humanitarian efforts, although that did make mappers feel as if they were doing something good.&lt;/li&gt;
  172. &lt;li&gt;New mappers often learn more quickly when they have a community, than they would otherwise. Being a part of the community is a huge motivator for people to map.&lt;/li&gt;
  173. &lt;li&gt;Having someone who can give feedback and make mappers feel welcome increases retention.&lt;/li&gt;
  174. &lt;/ul&gt;
  176. &lt;h4&gt;Understanding completeness and complexity drives motivation&lt;/h4&gt;
  178. &lt;ul&gt;
  179. &lt;li&gt;Community feedback and support motivates a lot of mappers.&lt;/li&gt;
  180. &lt;li&gt;Completeness is a huge driver for many mappers. Knowing what is new and what needs to be mapped, helps them to map more.&lt;/li&gt;
  181. &lt;li&gt;Understanding, very clearly, how a task is going to help people. Mappers who were involved in humanitarian mapping often didn’t know what the purpose of the task was, which made them significantly less motivated.&lt;/li&gt;
  182. &lt;li&gt;Communicating the complexity of a task helps mappers better choose a task that fits their skill level. Knowing that a task takes 10 mins or otherwise, is extremely valuable to guide mapping efforts. The skill level of the mappers and the density of the area that is being mapped should be thoroughly considered.&lt;/li&gt;
  183. &lt;li&gt;Completing a task in 10 mins or less. When tasks are only 10 minutes long, mappers often complete more tasks than they would otherwise.&lt;/li&gt;
  184. &lt;li&gt;Many mappers talked about not having a good way to see what is unmapped, especially when they’re away from their computers. Not having an easy way to see this information hurts their ability to collect that data when they’re outside of their homes, in their local communities, or are out in the field.&lt;/li&gt;
  185. &lt;/ul&gt;
  187. &lt;h4&gt;Better onboarding and guides help new mappers&lt;/h4&gt;
  189. &lt;ul&gt;
  190. &lt;li&gt;Many interviewees commented on how new mappers often don’t understand what OSM is or what it can do. To increase their understanding, more experienced mappers often point them to local communities, the wiki, walkthroughs and most importantly, applications. All of these things are hard to come across or know how to access from the homepage.&lt;/li&gt;
  191. &lt;li&gt;Adding metadata is a challenge for new mappers. iD’s interface for presets leaves users confused and often leads them select the wrong attribute. Improving autocomplete search and reimagining how new mappers interact with this complicated subject would help.&lt;/li&gt;
  192. &lt;li&gt;Many mappers are using a trackpad to map and not a mouse, so they often don’t notice the right click features.&lt;/li&gt;
  193. &lt;li&gt;People learn better by doing. Giving them a way to do this will increase their knowledge.&lt;/li&gt;
  194. &lt;/ul&gt;
  196. &lt;h4&gt;Being able to easily understand and discover local standards will improve quality&lt;/h4&gt;
  198. &lt;p&gt;Communities often have their own standards or features that are unique to an area. People who aren’t engaged in the local communities, who don&amp;#39;t know what these derivations are, can sometimes do more harm that good. It would be ideal to be able to showcase those local variations so that mappers are more aware of them.&lt;/p&gt;
  200. &lt;h4&gt;Learning about other mappers helps coordination&lt;/h4&gt;
  202. &lt;p&gt;Many interviewees commented on how it would be nice to know more information about a mapper. For example, what kind of skills they have, features they’re interested in mapping, potentially how responsive they are to messages. Knowing more information about a mapper could help better build a community, giving people a better understanding of which individuals to reach out to.&lt;/p&gt;
  204. &lt;h4&gt;Improving offline OSM capabilities will reach new users&lt;/h4&gt;
  206. &lt;p&gt;Many people in the field or people who often don’t have good wifi connections talked about this. One OSM member commented on how it’s been hard building the community without a way to demo OSM offline.&lt;/p&gt;
  208. &lt;h4&gt;Other ideas&lt;/h4&gt;
  210. &lt;ul&gt;
  211. &lt;li&gt;There is a need for an easier and better Overpass, or alternatives.&lt;/li&gt;
  212. &lt;li&gt;Creating a better building tool for iD.&lt;/li&gt;
  213. &lt;li&gt;Improve tools to align imagery faster.&lt;/li&gt;
  214. &lt;li&gt;Better ways to deal with multi-polygon relationships.&lt;/li&gt;
  215. &lt;li&gt;Being able to have more layers in OSM&lt;/li&gt;
  216. &lt;/ul&gt;
  218. &lt;h2&gt;Conclusions Per Audience&lt;/h2&gt;
  220. &lt;p&gt;Another interesting way to look at the data collected is by the different audiences.&lt;/p&gt;
  222. &lt;h4&gt;People or organisations who use OSM data&lt;/h4&gt;
  224. &lt;ul&gt;
  225. &lt;li&gt;They want easier ways to import large amounts of information&lt;/li&gt;
  226. &lt;li&gt;Ways to filter down data - see features that are relevant to them in certain areas&lt;/li&gt;
  227. &lt;li&gt;Easier ways to export data&lt;/li&gt;
  228. &lt;li&gt;Being able to map things that don’t belong on OSM, e.g. minefields&lt;/li&gt;
  229. &lt;/ul&gt;
  231. &lt;h4&gt;People who manage teams of mappers&lt;/h4&gt;
  233. &lt;ul&gt;
  234. &lt;li&gt;Their wants are mainly focused around getting a better overview of what mappers are doing. Also, being able to show progress in what they’re doing. They want things like:&lt;/li&gt;
  235. &lt;li&gt;Dashboards
  237. &lt;ul&gt;
  238. &lt;li&gt;Leaderboards (e.g. features in Missing Maps)&lt;/li&gt;
  239. &lt;li&gt;Being able to see who’s mapping where&lt;/li&gt;
  240. &lt;li&gt;Seeing change over time&lt;/li&gt;
  241. &lt;/ul&gt;&lt;/li&gt;
  242. &lt;li&gt;Easier ways to get new mappers up to speed so that there are fewer errors&lt;/li&gt;
  243. &lt;/ul&gt;
  245. &lt;h4&gt;Experienced Mappers&lt;/h4&gt;
  247. &lt;ul&gt;
  248. &lt;li&gt;Better community&lt;/li&gt;
  249. &lt;li&gt;Being able to know what is missing or what has changed in their neighborhoods/areas they map&lt;/li&gt;
  250. &lt;li&gt;Better information in one place. There is a need for more user friendly information on OSM intricacies, and complex tasks such as mapping cycleways.&lt;/li&gt;
  251. &lt;/ul&gt;
  253. &lt;h4&gt;New Mappers&lt;/h4&gt;
  255. &lt;ul&gt;
  256. &lt;li&gt;Better tools to help them understand the OSM ecosystem
  258. &lt;ul&gt;
  259. &lt;li&gt;Better way of tagging&lt;/li&gt;
  260. &lt;li&gt;Better access to lists of resources&lt;/li&gt;
  261. &lt;li&gt;Better understanding of how HOT and OSM work together (for new mappers there seems to be much confusion over the interaction between the two tabs. They will often close Tasking Manager which obviously creates much more work for them when they’ve completed a task).&lt;/li&gt;
  262. &lt;li&gt;Better tutorials (Shorter so that they can learn a little bit at a time and/or more easily rewatch a video around a particular topic when they’re confronted with that topic).&lt;/li&gt;
  263. &lt;li&gt;Encouragement&lt;/li&gt;
  264. &lt;li&gt;Better community (less intimidating and having a better understanding of how to access the community)&lt;/li&gt;
  265. &lt;/ul&gt;&lt;/li&gt;
  266. &lt;/ul&gt;
  268. &lt;p&gt;Overall, there is a lot of good potential work here. At Development Seed, our next steps will be coming up with potential projects that fit the needs of the community, as outlined above. Of course, we’d love to hear any suggestions for how to keep in contact with the community or any thoughts about projects to improve OSM moving forward.&lt;/p&gt;
  270. &lt;p&gt;Find our &lt;a href="" rel="nofollow"&gt;blog post here&lt;/a&gt;.&lt;/p&gt;
  271. </description>
  272.      <dc:creator>felskia</dc:creator>
  273.      <pubDate>Thu, 19 Apr 2018 19:32:54 +0000</pubDate>
  274.      <comments></comments>
  275.    </item>
  276.    <item>
  277.      <title>Fehlersuche in OSM</title>
  278.      <link></link>
  279.      <guid></guid>
  280.      <description>&lt;p&gt;Generell ist vieles unter den Stichworten Quality assurance zu finden. Hier ein paar Sachen, die ich mir selbst herausgesucht habe.
  281. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  283. &lt;h1&gt;Fehlersuche direkt mit OSM&lt;/h1&gt;
  285. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt; rechts Layer anzeigen und unter &amp;quot;Overlays zur Fehlersuche aktivieren&amp;quot; den Punkt &amp;quot;Hinweise/Fehlermeldungen&amp;quot; anwählen.&lt;/p&gt;
  287. &lt;h1&gt;Externe Quellen&lt;/h1&gt;
  289. &lt;ul&gt;
  290. &lt;li&gt;Geofabrik OSM Inspector - &lt;a href="" rel="nofollow"&gt;;/a&gt; &lt;/li&gt;
  291. &lt;li&gt;keep it right - &lt;a href="" rel="nofollow"&gt;;/a&gt; (Tagging kontrolle)&lt;/li&gt;
  292. &lt;li&gt;OSM Relation Analyzer - &lt;a href="" rel="nofollow"&gt;;/a&gt; &lt;/li&gt;
  293. &lt;li&gt;MapDust - &lt;a href="" rel="nofollow"&gt;;/a&gt; (Über Skobbler erfasste Routingfehler)&lt;/li&gt;
  294. &lt;li&gt;ITO Map - &lt;a href="" rel="nofollow"&gt;;/a&gt; (Bestimmte Eigenschaften hervorheben)&lt;/li&gt;
  295. &lt;/ul&gt;
  297. &lt;h1&gt;JOSM&lt;/h1&gt;
  299. &lt;ul&gt;
  300. &lt;li&gt;Validator Plugin - &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/li&gt;
  301. &lt;/ul&gt;
  303. &lt;h1&gt;Overpass&lt;/h1&gt;
  305. &lt;ul&gt;
  306. &lt;li&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;
  307. Mit diesem Tool können eigenen Suchanfragen abgesetzt werden, allerdings wird hier Code benötigt.
  308. Beispiele:&lt;br/&gt;
  309. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/li&gt;
  310. &lt;/ul&gt;
  311. </description>
  312.      <dc:creator>Negreheb</dc:creator>
  313.      <pubDate>Thu, 19 Apr 2018 15:40:37 +0000</pubDate>
  314.      <comments></comments>
  315.    </item>
  316.    <item>
  317.      <title>Updates on Dasmariñas City (part 2)</title>
  318.      <link></link>
  319.      <guid></guid>
  320.      <description>&lt;h1&gt;Project Street-level Photos via Mapillary&lt;/h1&gt;
  322. &lt;p&gt;Dasmariñas City has to undergo precise mapping, hence DEAR PAUL 24 have boarded the jeep from Salitran to DBB and DBB to WalterMart Dasmariñas at the front seat to provide the updated street imagery where most inner DBB PUV Routes have to base on the correct route line. Some drivers are yet to know the route modernization where the PUV Routes have to map on OSM by DEAR PAUL 24, hence briefing has to be executed himself. Some previously-uploaded street-level photos have resulted in the precise mapping of the sidewalk and roadways, especially in most Congressional Road Networks (Mangubat Avenue segment).&lt;/p&gt;
  324. &lt;h1&gt;Road Widening, Traffic Island, Drainage and Sidewalk Construction&lt;/h1&gt;
  326. &lt;p&gt;Dasmariñas City has widened the Congressional Road Network (Burol-J-E-F segment, initially Santa Cruz/San Lorenzo Ruiz 1-San Luis-Fatima section) to consider safety considerations and to avoid wrong-way driving/unsafe passing that may result in another head-on crash disaster. Being the safety and accessibility advocate himself, installing drainage and sidewalk will prevent or mitigate flooding and reduce the pedestrian-vehicle crash incidents, respectively.&lt;/p&gt;
  328. &lt;h1&gt;Proper PUV Stops and Transit Lanes&lt;/h1&gt;
  330. &lt;p&gt;Most errant commuters are not staying at the designated PUV Stops (whether signed or with shelter), thus impeding the regular traffic flow. To solve this problem within the Dasmariñas City, including Bagong Bayan (Resettlement Area), the City Government have constructed the Transit Lanes within the Congressional Road Network (North-South segment from Fatima to DLSU-D Gate 1/7-Eleven) along with the island separator, drainage, sidewalk, and public transport shelter specifications. Similarly, the City Government have rehabilitated and possibly widened the Congressional Road Network (Mangubat Avenue segment from Highway 419 to Bridge before DLSU-D Gate 3/DC Park) by 36 meters, which is sufficient enough to provide the Transit Lanes on both directions separated by the island separator. Hence, it is different from the Highway 1/AH26/EDSA in Metro Manila where the Transit Lanes (a.k.a. Yellow Lane) and General Multi-Purpose Travel Lanes are separated only by double lines.
  331. By convention, all private motor vehicles (including Taxis and TNVS), trucks and motorcycles must keep off the Transit Lanes since the Transit Lanes are intended for Buses (for 1/AH26/EDSA), Jeepneys, UV Express Services, and sometimes shared with Bicycles.&lt;/p&gt;
  333. &lt;h1&gt;Green Transportation&lt;/h1&gt;
  335. &lt;p&gt;Cyclists have to use bicycles safely to reach their desired destination, but most errant motor vehicles are either not passing the bicyclists at the safe distance or encroaching the bicycle lane, which may result in injury or even death. Remember the Marikina City&amp;#39;s truck-bicycle accident disaster that led to the death of a single mother within the city&amp;#39;s bicycle lane, and to avoid another disaster, being the safety advocate, DEAR PAUL 24 have pre-mapped the shared-use lane and bicycle lane along the Congressional Road Networks. Bicycle Lanes have normally marked with helmeted bicyclist symbol or BIKE LANE markings, along with solid line and/or green pavement. Washington Place has the existing Bicycle Lanes (as listed below) to provide safer and more-efficient green transportation, along with Bicycle Parking Racks (mapped on OSM) and electric tricycles as private shuttle service to homeowners.
  336. To avoid impeding the bicycle traffic flow, stopping and/or parking on the bicycle lanes are punishable by law, depending on the jurisdiction. This is the same with the sidewalks where pedestrians are expected to walk safely, and any form of illegal parking and/or stopping within the sidewalks are also punishable by law under Section 52 of RA 4136.&lt;/p&gt;
  338. &lt;h1&gt;Bicycle Lanes within Dasmariñas City&lt;/h1&gt;
  340. &lt;h2&gt;Existing&lt;/h2&gt;
  342. &lt;h3&gt;Washington Place&lt;/h3&gt;
  344. &lt;ul&gt;
  345. &lt;li&gt;WP1 | Washington Avenue&lt;/li&gt;
  346. &lt;li&gt;WP2 | Madison Avenue&lt;/li&gt;
  347. &lt;li&gt;WP4 | Texas Avenue&lt;/li&gt;
  348. &lt;/ul&gt;
  350. &lt;h2&gt;Soon&lt;/h2&gt;
  352. &lt;ul&gt;
  353. &lt;li&gt;Idesia Dasmariñas&lt;/li&gt;
  354. &lt;li&gt;Dasmariñas Bagong Bayan&lt;/li&gt;
  355. &lt;li&gt;Congressional Road Network&lt;/li&gt;
  356. &lt;li&gt;Paliparan Site&lt;/li&gt;
  357. &lt;/ul&gt;
  359. &lt;h1&gt;PUV Routes within and outside Dasmariñas City&lt;/h1&gt;
  361. &lt;h2&gt;Updated&lt;/h2&gt;
  363. &lt;ol&gt;
  364. &lt;li&gt;Intra-DBB PUV Route (D-F-B-A1-A3-G)&lt;/li&gt;
  365. &lt;li&gt;Intra-DBB PUV Route (D-F-B-A1 Loop)&lt;/li&gt;
  366. &lt;li&gt;Paliparan Site - Inter-DBB (C-D-F-E-J) - Downtown Dasmariñas and vice-versa PUV Route&lt;/li&gt;
  367. &lt;li&gt;DBB-C - SM Dasmariñas and vice-versa PUV Route&lt;/li&gt;
  368. &lt;li&gt;Parts of DBB-C - SWITX and vice-versa PUV Route&lt;/li&gt;
  369. &lt;/ol&gt;
  371. &lt;h2&gt;Upcoming&lt;/h2&gt;
  373. &lt;ol&gt;
  374. &lt;li&gt;Inter-DBB (A1-A3-G)  - Salitran - Imus City and vice-versa PUV Route&lt;/li&gt;
  375. &lt;li&gt;Inter-DBB (A1-A3-G) - Salitran - Bacoor City and vice-versa PUV Route&lt;/li&gt;
  376. &lt;li&gt;Inter-DBB (C-F-B) - Burol - Bacoor City and vice-versa PUV Route&lt;/li&gt;
  377. &lt;/ol&gt;
  379. &lt;h1&gt;Sources&lt;/h1&gt;
  381. &lt;ul&gt;
  382. &lt;li&gt;DearPaulPH on Mapillary&lt;/li&gt;
  383. &lt;/ul&gt;
  384. </description>
  385.      <dc:creator>DearPaulPH</dc:creator>
  386.      <pubDate>Thu, 19 Apr 2018 13:06:32 +0000</pubDate>
  387.      <comments></comments>
  388.      <geo:lat>14.278747544312</geo:lat>
  389.      <geo:long>120.973257869482</geo:long>
  390.      <georss:point>14.278747544312 120.973257869482</georss:point>
  391.    </item>
  392.    <item>
  393.      <title>My Involvement in OpenStreetMap </title>
  394.      <link></link>
  395.      <guid></guid>
  396.      <description>&lt;p&gt;Hello
  397. i&amp;#39;m  Astou Nathalie SIDIBE, a Human Ressources Manager, a
  398. social Activist, committed to Communities development and lots other  volunteer and humanitarian activities for a long time, in Mali.&lt;/p&gt;
  400. &lt;p&gt;I got involved in OpenstreetMap Project in December 2014 after two weeks of workshops with the Projet Espace OpenStreetMap Francophone, &lt;a href="" rel="nofollow"&gt;ProjetEOF&lt;/a&gt; in Bamako and then I cofounded  &lt;a href="" rel="nofollow"&gt;OpenStreetMap Mali&lt;/a&gt; and advocate for  OpenStreetMap and OpenData projects in Mali.&lt;/p&gt;
  402. &lt;p&gt;So, since January 2015, i’ve been planning and organizing mapping parties, MappingCamps  in Mali, cofacilitating trainings in Mali and in West Africa.
  403. I&amp;#39;m personnally involved in developing partnership with Public and Private Universities, High Schools, local and International Organizations . and also with National and international Organisations.
  404. I&amp;#39;m also the Lead of the French-Speaking Africa Community for OpenData, &lt;a href="" rel="nofollow"&gt;CAFDO&lt;/a&gt; , in Mali &lt;/p&gt;
  406. &lt;p&gt;As a Voting Member, becoming a Board Member is an opportunity to contribute more to HOT, to learn more and strengthen my leadership and also to share my fews experiences leading a local community.&lt;/p&gt;
  407. </description>
  408.      <dc:creator>Nathalie SIDIBE</dc:creator>
  409.      <pubDate>Wed, 18 Apr 2018 23:33:41 +0000</pubDate>
  410.      <comments></comments>
  411.    </item>
  412.    <item>
  413.      <title>Standing for the HOT Chair of Voting Members</title>
  414.      <link></link>
  415.      <guid></guid>
  416.      <description>&lt;p&gt;I am running for the elected position of Humanitarian OpenStreetMap Team’s Chair of Voting Members.&lt;/p&gt;
  418. &lt;p&gt;Voting Members are the core of HOT’s work and values; I see the position of chair as one that facilitates the Membership in many of the actions that lead and grow the organisation. A number  of the responsibilities are procedural, such as the calling and convening of meetings, but I also believe the Chair should foster and encourage individual volunteers to become Members, Mappers, Working Group contributors, Board candidates and more.&lt;/p&gt;
  420. &lt;p&gt;I have previously served on the Board of Directors, and have most recently been a member of the Governance Working Group. I have been a Mapper, have lead mapathons and have spoken publicly about our work. As such I believe I possess the range of experience required for this position.&lt;/p&gt;
  422. &lt;p&gt;HOT Members are a incredible group of humanitarians, mappers, hackers and creatives: I would like to efficiently and productively help these wonderful people lead the organisation.&lt;/p&gt;
  423. </description>
  424.      <dc:creator>IknowJoseph</dc:creator>
  425.      <pubDate>Wed, 18 Apr 2018 20:18:35 +0000</pubDate>
  426.      <comments></comments>
  427.      <geo:lat>51.6685</geo:lat>
  428.      <geo:long>-1.27948</geo:long>
  429.      <georss:point>51.6685 -1.27948</georss:point>
  430.    </item>
  431.    <item>
  432.      <title>Rua Silva Teles sp</title>
  433.      <link></link>
  434.      <guid></guid>
  435.      <description>&lt;p&gt;Importante via que corta os bairros do Belém, Pari e Brás e que termina na marginal tiete 100% numerada, com pontos de ônibus , semáforos, iluminação e lombadas incluídos  &lt;/p&gt;
  436. </description>
  437.      <dc:creator>O Fim</dc:creator>
  438.      <pubDate>Wed, 18 Apr 2018 13:41:15 +0000</pubDate>
  439.      <comments></comments>
  440.    </item>
  441.    <item>
  442.      <title>Required URL / graves / was not found on this server.</title>
  443.      <link></link>
  444.      <guid></guid>
  445.      <description>&lt;p&gt;Required URL &lt;a href=";lon=18.10289&amp;z=19" rel="nofollow"&gt;;amp;lon=18.10289&amp;amp;z=19&lt;/a&gt;  was not found on this server.
  446. At this address was a graves finder in the town of Czarna Woda.&lt;/p&gt;
  447. </description>
  448.      <dc:creator>Ryszard44</dc:creator>
  449.      <pubDate>Wed, 18 Apr 2018 10:55:45 +0000</pubDate>
  450.      <comments></comments>
  451.      <geo:lat>53.83426</geo:lat>
  452.      <geo:long>18.10289</geo:long>
  453.      <georss:point>53.83426 18.10289</georss:point>
  454.    </item>
  455.    <item>
  456.      <title>Mapeando cidades do Estado do Piauí - Parte 3</title>
  457.      <link></link>
  458.      <guid></guid>
  459.      <description>&lt;p&gt;Olá amigos mapeadores do Open Street Map! Como estão?. Venho hoje compartilhar minha experiência de mapear as cidades deste Estado. Desta vez mapeei as cidades cujo a inicial é a letra &amp;quot;C&amp;quot;. No total são 33 cidades com esta inicial. Destas, apenas 5 cidades ficaram sem nomes de ruas, devido não ter camada do IBGE urbano.&lt;/p&gt;
  461. &lt;p&gt;São estas as cidades: Caldeirão Grande do Piauí, Campo Grande do Piauí, Caridade do Piauí, Caxingó e Currais. Estão sem nomes de ruas, podendo alguém, futuramente, fazer alterações.&lt;/p&gt;
  463. &lt;p&gt;Neste mapeamento tive bastante trabalho, pois haviam algumas cidades com bastante ruas como Campo Maior, Canto do Buriti, entre outras. Cada mapeamento, além dos nomes de ruas, adicionei alguns riachos, vias locais, escolas, igrejas, etc. Corrigi, ajustei, alinhei ruas, enfim, tentei deixar tudo bem trabalhado.&lt;/p&gt;
  465. &lt;p&gt;Aos poucos estou colocando o Piauí no mapa OSM, pois é um Estado que aparentemente tem poucos mapeadores ativos. Recentemente foi criado um grupo no Telegram, denominado &amp;quot;OSM Nordeste&amp;quot;, cujo o objetivo principal no momento é colocar nomes de ruas nas cidades que faltam. &lt;/p&gt;
  467. &lt;p&gt;Piauí, Maranhão, Pernambuco e Paraíba são os Estados que estão com um mapeamento muito deficitário nesta região. &lt;/p&gt;
  469. &lt;p&gt;Estou fazendo minha parte no Estado do Piauí, estou gostando, e pouco a pouco a gente vai fazendo um grande trabalho. Novas edições em breve! Abraços e até a próxima!&lt;/p&gt;
  470. </description>
  471.      <dc:creator>FrancyskoMarkes</dc:creator>
  472.      <pubDate>Wed, 18 Apr 2018 01:15:03 +0000</pubDate>
  473.      <comments></comments>
  474.    </item>
  475.    <item>
  476.      <title>Feasibility of Telegram channel as a major matter of communication for Russian OSM community</title>
  477.      <link></link>
  478.      <guid></guid>
  479.      <description>&lt;p&gt;As it has been mentioned before, establishing a Telegram channel as a major matter of communication for Russian-speaking OSM community is a questionable step itself since it creates an additional fragmentation and benefits only a certain group of people within this community.&lt;/p&gt;
  481. &lt;p&gt;However, this situation got some development recently. &lt;a href=",_Information_Technology_and_Mass_Media" rel="nofollow"&gt;Russian communication regulator authority, RKN&lt;/a&gt; (actually, the government censorship agency) officially &lt;a href="" rel="nofollow"&gt;started blocking Telegram messenger communication protocol&lt;/a&gt;. Ironically, at the same time, iD got Russian OSM Telegram channel listed on its sidebar, above the link to OSM Russia forum section (which was always the main method of communication), giving a hint of its greater importance.&lt;/p&gt;
  483. &lt;p&gt;So, from now on, only those Russian users of those rare internet service providers who haven&amp;#39;t started following the order of RKN or those who are able to set up and use network tunneling services (soon they will be illegal in Russia too) will have an access to Telegram.&lt;/p&gt;
  485. &lt;p&gt;Most likely, some commenters might argue that it is so easy to set up a VPN and so on, but that&amp;#39;s not the point. The point is that any random OSM user from Russia should not have to violate (obviously, stupid and unconstitutional, but still existing) law or learn how to be an IT specialist to have an access to community communication channel. It doesn&amp;#39;t mean that some people can&amp;#39;t keep using that channel privately if they want to, but it should not be listed anywhere as a major or preferred channel of communication.&lt;/p&gt;
  486. </description>
  487.      <dc:creator>Dzertanoj</dc:creator>
  488.      <pubDate>Tue, 17 Apr 2018 21:29:52 +0000</pubDate>
  489.      <comments></comments>
  490.    </item>
  491.    <item>
  492.      <title>Piscina 3 casas rurales parejas</title>
  493.      <link></link>
  494.      <guid></guid>
  495.      <description>&lt;p&gt;Piscina Casas rurales dedicadas al turismo rural con jacuzzi o Terma romana en la habitación.&lt;/p&gt;
  496. </description>
  497.      <dc:creator>Ecorural</dc:creator>
  498.      <pubDate>Tue, 17 Apr 2018 11:12:29 +0000</pubDate>
  499.      <comments></comments>
  500.      <geo:lat>40.3411859922612</geo:lat>
  501.      <geo:long>-0.0728367269039154</geo:long>
  502.      <georss:point>40.3411859922612 -0.0728367269039154</georss:point>
  503.    </item>
  504.    <item>
  505.      <title>Quarterly project for traditionally under-mapped things</title>
  506.      <link></link>
  507.      <guid></guid>
  508.      <description>&lt;p&gt;Over on the &lt;a href="" rel="nofollow"&gt;diversity-talk mailing list&lt;/a&gt; I&amp;#39;m &lt;a href="" rel="nofollow"&gt;floating the idea&lt;/a&gt; of a quarterly project to map traditionally under-represented things. There&amp;#39;s been lots of legit talk lately about what is and isn&amp;#39;t mapped in OSM, so let&amp;#39;s try to map it. I&amp;#39;ve set up a &lt;a href="" rel="nofollow"&gt;poll&lt;/a&gt; to gather ideas and select something. If you&amp;#39;re interested in helping with this, feel free to vote, take part, and/or join the mailing list.&lt;/p&gt;
  509. </description>
  510.      <dc:creator>rorym</dc:creator>
  511.      <pubDate>Tue, 17 Apr 2018 07:40:29 +0000</pubDate>
  512.      <comments></comments>
  513.    </item>
  514.    <item>
  515.      <title>What is an import?</title>
  516.      <link></link>
  517.      <guid></guid>
  518.      <description>&lt;p&gt;I have been working on some code to detect if a changeset is an import, SPAM, or if it has a tagging error. &lt;/p&gt;
  520. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  522. &lt;p&gt;Detecting SPAM and tagging errors is pretty straight forward. However, detecting imports is much more challenging. Before I started, I thought I knew what an import was. I was looking for large changesets, that only added 1 or two kinds of data. However, this criteria performs poorly in practice. In OSM many import changesets are not large, also it is not uncommon that the imported data has some hand editing mixed it. &lt;/p&gt;
  524. &lt;p&gt;My new definition of an import&lt;/p&gt;
  526. &lt;p&gt;An import is any addition to OSM that directly derives from other digital map sources. &lt;/p&gt;
  527. </description>
  528.      <dc:creator>jremillard</dc:creator>
  529.      <pubDate>Tue, 17 Apr 2018 03:35:58 +0000</pubDate>
  530.      <comments></comments>
  531.    </item>
  532.    <item>
  533.      <title>Updates to Lebap Welayat in Turkmenistan</title>
  534.      <link></link>
  535.      <guid></guid>
  536.      <description>&lt;p&gt;Among the things on my to-do list are checking to ensure that changes to names of places in Lebap welayat adopted in November 2017 have been taken care of.  The whole list is in &lt;a href="" rel="nofollow"&gt;this article&lt;/a&gt; in the Russian language.  As time permits, I&amp;#39;ll check and edit as necessary.  Among other things, the city of Atamyrat and surrounding district have had their old names (Kerki and Kerki etraby) restored.  I changed the city name some time back but still have some work ahead.&lt;/p&gt;
  537. </description>
  538.      <dc:creator>apm-wa</dc:creator>
  539.      <pubDate>Mon, 16 Apr 2018 15:15:31 +0000</pubDate>
  540.      <comments></comments>
  541.      <geo:lat>38.6039932755917</geo:lat>
  542.      <geo:long>63.3334350585938</geo:long>
  543.      <georss:point>38.6039932755917 63.3334350585938</georss:point>
  544.    </item>
  545.  </channel>
  546. </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