[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>Framaliste [email protected]</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;Une framaliste est maintenant disponible pour discuter de la cartographie OSM en Hainaut Français&lt;/p&gt;
  20. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  22. &lt;p&gt;Également : &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  23. </description>
  24.      <dc:creator>HainautCart@</dc:creator>
  25.      <pubDate>Sat, 29 Apr 2017 12:01:12 +0000</pubDate>
  26.      <comments></comments>
  27.    </item>
  28.    <item>
  29.      <title>Belarus in Belarusian + bilingual / trilingual / quadrilingual names in Europe</title>
  30.      <link></link>
  31.      <guid></guid>
  32.      <description>&lt;p&gt;Dear All,&lt;/p&gt;
  34. &lt;p&gt;I have been in around 35 countries around the world and I noticed Belarus is the only country that appears on Openstreetmap in a different language than on-spot.
  35. To be more precise, all names appear in OSM in Russian (Островец, Осиновка, Ошмяны for example), but when you drive there, everything is written in Belarusian (Астравец, Асінаўка, Ашмяны for instance).
  36. I&amp;#39;ve got nothing against Russian language (which is definitely more spoken in Belarus than Belarusian). However, I think we should start ASAP to correct that mistake and make Belarusian village, town and city names the main ones. In some cases even street and public transport names (in Minsk these things appear in Belarusian).
  37. The purpose is simple: for instance when you use (a GPS app that uses OSM), if you drive to Asinaŭka. it appears &amp;quot;Asinaŭka&amp;quot; and, just below, the name in Russian (Оснивока). However, when you arrive to that village, you see &amp;quot;Асінаўка&amp;quot;. It is extremely confusing for travelers, especially if they don&amp;#39;t read cyrillic.&lt;/p&gt;
  39. &lt;p&gt;Another question: multilingual names in Europe. Numerous cities, towns, and villages appear with bilingual names on spot (but on OSM their main names appear only in one language). It would be good to make those names appear as they appear on spot.&lt;/p&gt;
  41. &lt;p&gt;How do you think?&lt;/p&gt;
  42. </description>
  43.      <dc:creator>meijerry</dc:creator>
  44.      <pubDate>Sat, 29 Apr 2017 11:11:50 +0000</pubDate>
  45.      <comments></comments>
  46.    </item>
  47.    <item>
  48.      <title>Dear Diary</title>
  49.      <link></link>
  50.      <guid></guid>
  51.      <description>&lt;p&gt;Sometimes I wonder who really cares about the nitty-gritty details of ways. All that really needs to be mapped is the geometry to show what ways are connected, and what can absolutely not travel on it. By no means am I an expert, but I have a feeling that there&amp;#39;s a lot of info that&amp;#39;s practically not needed. The ability to add it just makes people fight and unhappy with others&amp;#39; judgement.&lt;/p&gt;
  52. </description>
  53.      <dc:creator>3ngineer</dc:creator>
  54.      <pubDate>Sat, 29 Apr 2017 10:00:06 +0000</pubDate>
  55.      <comments></comments>
  56.    </item>
  57.    <item>
  58.      <title>Latest MapRoulette newsletter</title>
  59.      <link></link>
  60.      <guid></guid>
  61.      <description>&lt;p&gt;I am going to stop posting the full monthly MapRoulette newsletter here from now on, but the April newsletter has just been sent to the subscribers! You can view it &lt;a href="" rel="nofollow"&gt;here&lt;/a&gt;.&lt;/p&gt;
  63. &lt;p&gt;Subscribe to the newsletter &lt;a href="" rel="nofollow"&gt;on this page&lt;/a&gt;.&lt;/p&gt;
  64. </description>
  65.      <dc:creator>mvexel</dc:creator>
  66.      <pubDate>Fri, 28 Apr 2017 22:01:03 +0000</pubDate>
  67.      <comments></comments>
  68.    </item>
  69.    <item>
  70.      <title>OSM Tutorials</title>
  71.      <link></link>
  72.      <guid></guid>
  73.      <description>&lt;p&gt;Trying to create some video tutorials for OSM. Playlist is here:&lt;/p&gt;
  75. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  76. </description>
  77.      <dc:creator>mmahmud</dc:creator>
  78.      <pubDate>Fri, 28 Apr 2017 17:21:44 +0000</pubDate>
  79.      <comments></comments>
  80.    </item>
  81.    <item>
  82.      <title>About landuses and landcover, in particular landuse=residential</title>
  83.      <link></link>
  84.      <guid></guid>
  85.      <description>&lt;p&gt;Today I was asked by another (very active) mapper via email these questions:&lt;/p&gt;
  87. &lt;blockquote&gt;
  88. &lt;p&gt;We are currently discussing best practices for landuse mapping in Belgium.
  89. Some of the problems:&lt;/p&gt;
  91. &lt;ul&gt;
  92. &lt;li&gt;do you use multipolygons to avoid overlapping landuse or do you split a residential landuse so you can have smaller landuses ? Or do you just overlay them ? A lot of landuse is already mapped in a rough way, so we typically have large areas of residential landuse.&lt;/li&gt;
  93. &lt;li&gt;Do you include streets in residential landuse or do you exclude them so one can later add area:highway or landuse=highway ?&lt;/li&gt;
  94. &lt;li&gt;I&amp;#39;m in favour of landcover to avoid &amp;quot;forests&amp;quot; in gardens. Which landcover proposal do you follow ? (I believe there are 2).&lt;/li&gt;
  95. &lt;li&gt;what about grass/bushes in towns near highways ?&lt;/li&gt;
  96. &lt;/ul&gt;
  97. &lt;/blockquote&gt;
  99. &lt;p&gt;I wrote some lines how I believe it should be done. Here&amp;#39;s a slightly modified version: &lt;/p&gt;
  101. &lt;h2&gt;Residential landuse&lt;/h2&gt;
  103. &lt;p&gt;Regarding the residential landuse, I am since almost 10 years advocating to not include roads but end the landuse at the property borders. Not only does it add more detail, because you can clearly distinguish (even without roads), parcelled land and common land, it will also be easier to add landuse=highway, i.e. the land that is legally a road. It just makes no sense from a legal point of view to add streets to the residential landuse (save maybe those areas where the streets are private). I do include driveways though, i.e. &amp;quot;roads&amp;quot; on the properties. &lt;/p&gt;
  105. &lt;p&gt;Clearly, public roads are road landuse, so they must not be included in residential, industrial, commercial, retail or other similar landuse.&lt;/p&gt;
  107. &lt;h3&gt;why do people often use huge polygons including whole settlements in one landuse object?&lt;/h3&gt;
  109. &lt;p&gt;IMHO the 3 reasons for people to include roads are&lt;/p&gt;
  111. &lt;ol&gt;
  112. &lt;li&gt;&lt;p&gt;lazyness (to draw and to determine the precise border, ...)&lt;/p&gt;&lt;/li&gt;
  113. &lt;li&gt;&lt;p&gt;OSM standard style is not rendering place areas, so people misuse residential landuse to say: built up area&lt;/p&gt;&lt;/li&gt;
  114. &lt;li&gt;&lt;p&gt;people hating &amp;quot;gaps&amp;quot; or voids in the map and think it must be &amp;quot;complete&amp;quot;, so they connect the landuse to the road and prefer to have it &amp;quot;wrong&amp;quot; rather than &amp;quot;incomplete&amp;quot;.&lt;/p&gt;&lt;/li&gt;
  115. &lt;/ol&gt;
  117. &lt;h3&gt;Scale&lt;/h3&gt;
  119. &lt;p&gt;Of course it also depends on scale. IMHO we should try to map in a high scale, e.g. 1:500 - 1:1000 (because simplifications can be computed at need, while details can&amp;#39;t), but if you do your mapping in 1:10.000 and lower you would likely not represent these details and would &amp;quot;include&amp;quot; the roads (actually it wouldn&amp;#39;t be discernable whether they are included or not in these scales).&lt;/p&gt;
  121. &lt;h2&gt;Using multipolygons in landuse mapping&lt;/h2&gt;
  123. &lt;p&gt;I also advocate to not use multipolygons for built up landuse, if it is not strictly necessary (never met a situation where it was necessary, but it might exist). It just creates unnecessary complexity and deters less experienced mappers, and leads to errors laters. It is not necessary, just make the landuse as small as you like and need. (I think that landuse is a property of the land, I don&amp;#39;t see it as a feature, i.e. for mapping a &amp;quot;residential area with a name&amp;quot; = part of a settlement, I suggest to use place, e.g. quarter, neighbourhood. Can even work for industrial areas (their names)). This way, you don&amp;#39;t mix stuff and are not forced to ignore parcels with different landuses which are also a part of the settlement part (toponomastic area).&lt;/p&gt;
  125. &lt;p&gt;On the other hand, when mapping in rural areas and landuses like farmland, forests and other natural features (scrubs, heath, beaches, ...), multipolygons might come in handy to avoid duplicating long (and complex) ways by reusing them.&lt;/p&gt;
  127. &lt;h2&gt;Landcover&lt;/h2&gt;
  129. &lt;p&gt;Regarding landcover, I mostly only use 3 values: trees, sand, grass, although it could be extended by more vegetation and surface types (like bushes or whatever term is correct for these, currently I use natural=scrub for thickly vegetated / unpassable areas and avoid the landcover tag there). I admit as long as it doesn&amp;#39;t render I still add stupid forest tags additionally, although it really is stupid ;-)
  130. I don&amp;#39;t know about 2 landcover proposals, but for trees, sand and grass there isn&amp;#39;t much to discuss I think.&lt;/p&gt;
  132. &lt;h2&gt;Grass and bushes along roads&lt;/h2&gt;
  134. &lt;p&gt;If they are (legally) part of the road I would see them as landuse=highway, grass can be landcover=grass, bushes are (in my mapping but I believe it is a common agreement) natural=scrub.&lt;/p&gt;
  135. </description>
  136.      <dc:creator>dieterdreist</dc:creator>
  137.      <pubDate>Fri, 28 Apr 2017 17:21:13 +0000</pubDate>
  138.      <comments></comments>
  139.    </item>
  140.    <item>
  141.      <title>Louvre indoor</title>
  142.      <link></link>
  143.      <guid></guid>
  144.      <description>&lt;p&gt;Aujourd&amp;#39;hui j&amp;#39;ai terminé &lt;a href=";lon=2.336236&amp;z=18&amp;t=0&amp;lvl=-2&amp;tcd=1&amp;urd=0&amp;bdg=0&amp;pic=0&amp;nte=0&amp;ilv=0" rel="nofollow"&gt;le Louvre&lt;/a&gt;. 1 035 objets &lt;em&gt;indoor&lt;/em&gt; selon l&amp;#39;indispensable OpenLevelUp. J&amp;#39;ai suivi la spécification &lt;a href="" rel="nofollow"&gt;Simple Indoor Tagging&lt;/a&gt;. Il ne manque que quelques salles fermées pour travaux, et tout ce que j&amp;#39;ai sûrement oublié ici ou là. Je vais donc faire un second passage pour vérifier chaque salle, chaque couloir, chaque entrée, et chaque attribut de chaque objet. Harmoniser la gestion des descriptions, des entrées. Rajouter sans doute des escaliers en &lt;em&gt;ways&lt;/em&gt; parce que les &lt;em&gt;areas&lt;/em&gt;, ce n&amp;#39;est pas suffisant pour un escalier. Indiquer peut-être les noms de départements.&lt;/p&gt;
  146. &lt;p&gt;Rien n&amp;#39;est simple au Louvre : &lt;a href=";lon=2.335430&amp;z=22&amp;t=0&amp;lvl=0.25&amp;tcd=1&amp;urd=0&amp;bdg=0&amp;pic=0&amp;nte=0&amp;ilv=0#" rel="nofollow"&gt;escaliers de trois ou quatre marches&lt;/a&gt; avec  un arrêt d&amp;#39;ascenseur en haut et un autre en bas, étages superposés mais jamais identiques, fiches descriptives de salles qui suivent des conventions différentes d&amp;#39;un département à l&amp;#39;autre, angles pas forcément droits, &lt;a href=";lon=2.338083&amp;z=20&amp;t=0&amp;lvl=-1&amp;tcd=1&amp;urd=0&amp;bdg=0&amp;pic=0&amp;nte=0&amp;ilv=0" rel="nofollow"&gt;vestiges médiévaux&lt;/a&gt;, &lt;a href=";lon=2.338878&amp;z=21&amp;t=0&amp;lvl=0&amp;tcd=1&amp;urd=0&amp;bdg=0&amp;pic=0&amp;nte=0&amp;ilv=0" rel="nofollow"&gt;escaliers aux formes ingérables&lt;/a&gt;...&lt;/p&gt;
  148. &lt;p&gt;Et puis il faudra peut-être se demander à quoi tout cela peut servir. Il y aurait de quoi faire un petit guide sur smartphone.&lt;/p&gt;
  149. </description>
  150.      <dc:creator>thbz</dc:creator>
  151.      <pubDate>Fri, 28 Apr 2017 15:47:37 +0000</pubDate>
  152.      <comments></comments>
  153.    </item>
  154.    <item>
  155.      <title>Mapbox has a new logo!</title>
  156.      <link></link>
  157.      <guid></guid>
  158.      <description>&lt;p&gt;OpenStreetMap is an integral part of &lt;a href="" rel="nofollow"&gt;Mapbox&lt;/a&gt;, I&amp;#39;m  happy to share the announcement about our new logo with the community! 🎉&lt;/p&gt;
  160. &lt;p&gt;The logo is a helmet of an astronaut and my favorite part of this logo is that it reinstates Mapbox’s culture of curiosity and passion! It showcases the team’s vision and enthusiasm towards new opportunities. The star that you see in the astronaut’s helmet demonstrates our spirits to reach new heights! Know more details about the logo &lt;a href="" rel="nofollow"&gt;here&lt;/a&gt;.&lt;/p&gt;
  162. &lt;p&gt;&lt;img src="" alt="33284852904_49008d0641_o"/&gt;&lt;/p&gt;
  164. &lt;p&gt;Though we have a new look and feel, we still continue to be the Mapbox that you all know. Our commitment towards improving OpenStreetMap data remains the same and so is our &lt;a href="" rel="nofollow"&gt;attribution&lt;/a&gt; around OpenStreetMap! ✨&lt;/p&gt;
  165. </description>
  166.      <dc:creator>jinalfoflia</dc:creator>
  167.      <pubDate>Fri, 28 Apr 2017 11:57:11 +0000</pubDate>
  168.      <comments></comments>
  169.    </item>
  170.    <item>
  171.      <title>Mapped in Every Country of the World</title>
  172.      <link></link>
  173.      <guid></guid>
  174.      <description>&lt;p&gt;28th April, 2017&lt;/p&gt;
  176. &lt;p&gt;Well, this was a personal goal of mine to Map in every single country in the World with OpenStreetMap. Well, mapping in every country is easy so I took it upon myself to make at least 1000 changes in every country. So, today finally that goal is achieved.&lt;/p&gt;
  178. &lt;p&gt;I mapped in all 197 countries in the World and made at least 1000 changes (Except in Vatican City because that place is too well mapped).&lt;/p&gt;
  180. &lt;p&gt;Country list:
  181. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  183. &lt;p&gt;&lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  185. &lt;p&gt;You can check it here:
  186. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  188. &lt;p&gt;Notes:&lt;/p&gt;
  190. &lt;p&gt;Palestine is shown as West Bank and Gaza Strip combined.&lt;/p&gt;
  192. &lt;p&gt;New Caledonia and Guadeloupe are states of France.&lt;/p&gt;
  194. &lt;p&gt;Western Sahara is part of Morocco.&lt;/p&gt;
  195. </description>
  196.      <dc:creator>mmahmud</dc:creator>
  197.      <pubDate>Fri, 28 Apr 2017 10:37:20 +0000</pubDate>
  198.      <comments></comments>
  199.    </item>
  200.    <item>
  201.      <title>l</title>
  202.      <link></link>
  203.      <guid></guid>
  204.      <description>&lt;p&gt;l&lt;/p&gt;
  205. </description>
  206.      <dc:creator>JakobStute</dc:creator>
  207.      <pubDate>Fri, 28 Apr 2017 09:54:37 +0000</pubDate>
  208.      <comments></comments>
  209.      <geo:lat>47.5436416462776</geo:lat>
  210.      <geo:long>14.8935180902481</geo:long>
  211.      <georss:point>47.5436416462776 14.8935180902481</georss:point>
  212.    </item>
  213.    <item>
  214.      <title>Tagondaing</title>
  215.      <link></link>
  216.      <guid></guid>
  217.      <description>&lt;p&gt;Tagondaing, Kyain State, Burma&lt;/p&gt;
  218. </description>
  219.      <dc:creator>wonraw</dc:creator>
  220.      <pubDate>Thu, 27 Apr 2017 19:06:18 +0000</pubDate>
  221.      <comments></comments>
  222.      <geo:lat>16.0685220200565</geo:lat>
  223.      <geo:long>97.9084774006333</geo:long>
  224.      <georss:point>16.0685220200565 97.9084774006333</georss:point>
  225.    </item>
  226.    <item>
  227.      <title>New developments in Batangas City</title>
  228.      <link></link>
  229.      <guid></guid>
  230.      <description>&lt;p&gt;Since starting mapping in 2015, Batangas City is still developing, and many newer developments have come. Much of the new developments are occurring along Diversion Road and the Batangas Port area. Subdivisions are growing into the suburban and rural barangays. Two new power plants have opened. But, current imagery used for mapping creates a problem to map these new developments. Though Bing announced imagery updates this 2017, it will be a long wait.&lt;/p&gt;
  232. &lt;p&gt;Developments to be mapped is shown below, along with description, notes, and status.&lt;/p&gt;
  234. &lt;ul&gt;
  235. &lt;li&gt;Batangas Health Specialists Medical Center (involved also relocation of some NGCP 69 kV lines due to construction work on part of right-of-way of those subtransmission lines. Polygon and building now mapped, but not the 69 kV line relocation.)&lt;/li&gt;
  236. &lt;li&gt;Batangas City Grand Terminal expansion (adding commercial areas and covered bus terminal. Traffic rerouting mapped, but not the new developments)&lt;/li&gt;
  237. &lt;li&gt;new car dealers along Diversion Road (Suzuki Batangas City, Isuzu Batangas City, Hino Batangas City. Now added)&lt;/li&gt;
  238. &lt;li&gt;San Gabriel and Avion power plants (opened 2016. Still unmapped because imagery still do not show any evidence of those plants, even just their construction.)&lt;/li&gt;
  239. &lt;li&gt;NGCP Batangas Substation (addition of two 150 MVA transformers and 69 kV switchgear to accommodate Meralco&amp;#39;s Mahabang Parang - Batangas City 69 kV subtransmission lines and 69 kV power supply for JG Summit in 2015, and relocation of some 69 kV lines in 2017, that replaced some tap connections with connection to a new 69 kV bus in the substation in 2017. Transformer additions, including new bay, are mapped, but not the new switchgear, due to lack of usable imagery from Bing. 69 kV line relocation still not mapped, while thick can be mapped without using any aerial imagery.)&lt;/li&gt;
  240. &lt;li&gt;Camella Solamente (started 2015. Still not mapped due to lack of more recent imagery showing development.)&lt;/li&gt;
  241. &lt;li&gt;Monte Maria Batangas (opening of chapel below statue of the Virgin Mary. Building below the statue already mapped, along with realignment of surrounding road, adding of Meralco 13.2 kV distribution line and restaurant. Needs further update).&lt;/li&gt;
  242. &lt;li&gt;Batangas Port expansion (started 2015/16 and ongoing. Only a few warehouse buildings mapped, but expansion area is mapped)&lt;/li&gt;
  243. &lt;li&gt;SM City Batangas (new side entrance, hallway shops, and restaurants, and relocation of some shops and SM Supermarket. Partially mapped.)&lt;/li&gt;
  244. &lt;/ul&gt;
  246. &lt;p&gt;As these developments go around the clock, these are to be placed in priority. Barangay mapping, further land use, woodland and farm mapping, and other local updates, especially around Poblacion, Cuta, Pallocan West, Kumintang Ibaba, Kumintang Ilaya, and Alangilan, are also to be added to the mapping priority list for Batangas City.&lt;/p&gt;
  247. </description>
  248.      <dc:creator>TagaSanPedroAko</dc:creator>
  249.      <pubDate>Thu, 27 Apr 2017 18:01:03 +0000</pubDate>
  250.      <comments></comments>
  251.    </item>
  252.    <item>
  253.      <title>Increasing mapping activity in Batangas City (update 1)</title>
  254.      <link></link>
  255.      <guid></guid>
  256.      <description>&lt;p&gt;Mapping in Batangas City has been increasing after the LGU-led mapping from March to April, yet, it caused some problems in the current data because of mapping practice that looks like tagging for the renderer. Yet, aside from the LGU-led  (Batangas City CPDO, CDRMMO, and OCVAS) mapping, there is a new surge of mapping activity in Batangas City. It is part of the MapTVPL activity in Batangas. One among who led the mapping is (GOWin)[&lt;a href="" rel="nofollow"&gt;;/a&gt;), who mapped Batangas State University, and the surrounding area. Batangas State Univerity&amp;#39;s map has improved, with some named streets inside added, buildings named, and new buildings mapped. It is also the same case for the adjacent Batangas National High School (BNHS), whose buildings have been named and more facilities inside mapped, since I started mapping it&amp;#39;s buildings, plus mapping during the NOAH-ISAIAH HOT task in Batangas.&lt;/p&gt;
  258. &lt;p&gt;It may be expected that the Batangas City LGU may start another mapping project, but should have to avoid problems with existing map data, especially buildings and POI&amp;#39;s. The rural barangays have improved, thanks to Batangas City employees contributions, with barangay halls, water supply tanks, schools and day care centers mapped, and a lot more must be expected. Marking the centers of barangays, using the newly added data from Batangas City LGU mapping, are still needed, and further mapping of other missing critical POI&amp;#39;s especially schools, as they serve as evacuation centers in times of calamities. &lt;/p&gt;
  259. </description>
  260.      <dc:creator>TagaSanPedroAko</dc:creator>
  261.      <pubDate>Thu, 27 Apr 2017 17:41:09 +0000</pubDate>
  262.      <comments></comments>
  263.    </item>
  264.    <item>
  265.      <title>OpenStreetMap tutuksi</title>
  266.      <link></link>
  267.      <guid></guid>
  268.      <description>&lt;p&gt;&lt;em&gt;A beginner&amp;#39;s guide to OpenStreetMap in Finnish&lt;/em&gt;&lt;/p&gt;
  270. &lt;h1&gt;OpenStreetMap tutuksi&lt;/h1&gt;
  272. &lt;p&gt;Tätä harjoitusta varten tarvitset:&lt;/p&gt;
  274. &lt;ul&gt;
  275. &lt;li&gt;kynän ja paperia&lt;/li&gt;
  276. &lt;li&gt;tietokoneen&lt;/li&gt;
  277. &lt;li&gt;nettiyhteyden&lt;/li&gt;
  278. &lt;li&gt;oman sähköpostiosoitteen&lt;/li&gt;
  279. &lt;li&gt;hiiren (ei pakollinen, mutta suositeltava)&lt;/li&gt;
  280. &lt;/ul&gt;
  282. &lt;h2&gt;Kartan rakennuspalikat&lt;/h2&gt;
  284. &lt;p&gt;Kartta on tehokas tapa välittää tietoa. Karttojen avulla pystymme vastaamaan tärkeisiin kysymyksiin, kuten: &lt;em&gt;Missä sijaitsee lähin koulu? Mikä on nopein reitti kauppaan? Kuinka monta ihmistä asuu kohtuullisen matkan päässä lähimmästä terveyskeskuksesta?&lt;/em&gt;&lt;/p&gt;
  286. &lt;p&gt;&lt;strong&gt;Tehtävä 1: Piirrä paperille kartta kotipaikkakunnaltasi (esim. koulun tai kodin ympäristö). Pohdi, mitkä kohteet on tärkeä esittää kartalla. Kenelle kartasta voisi olla hyötyä?&lt;/strong&gt;&lt;/p&gt;
  288. &lt;p&gt;Luultavasti piirsit kartalle viivamaisia kohteita (esim. tiet), aluemaisia kohteita (esim. rakennukset ja puistot), ja mahdollisesti myös pisteitä (esim. osoittamaan tarkemmin jonkun paikan sijainnin).  &lt;/p&gt;
  290. &lt;p&gt;Pisteet, viivat ja alueet ovat digitaalisten karttojen peruselementtejä, joilla esitetään karttakohteiden sijaintia. Sijaintitiedon lisäksi digitaalisissa kartoissa on usein tietoa karttakohteiden ominaisuuksista, kuten esimerkiksi tieluokka, rakennuksen kerrosmäärä tai kohteen nimi. &lt;/p&gt;
  292. &lt;h2&gt;OpenStreetMap – avoin maailmankartta&lt;/h2&gt;
  294. &lt;p&gt;OpenStreetMap (OSM) on avoin digitaalinen kartta-aineisto. Kuka tahansa voi muokata karttaa ja aineistoa saa käyttää ilmaiseksi kaupallisiin ja ei-kaupallisiin tarkoituksiin. OSM perustettiin vuonna 2004 Englannissa, jonka jälkeen OSM on kehittynyt varteenotettavaksi vaihtoehdoksi kaupallisille ja kansallisille paikkatietoaineistoille eri puolilla maailmaa. Esimerkiksi pääkaupunkiseudulla toimiva –sivusto ja koko Suomessa toimiva –sivusto hyödyntävät OpenStreetMap-aineistoja palveluissaan. OSM muuttuu jatkuvasti sitä mukaan kun karttaa muokataan eri puolilla maailmaa.&lt;/p&gt;
  296. &lt;p&gt;&lt;strong&gt;Tehtävä 2: Mene osoitteeseen &lt;a href="" rel="nofollow"&gt;;/a&gt; ja zoomaa kartta tutulle alueelle. Löydätkö oman kodin ja koulun kartalta?&lt;/strong&gt;&lt;/p&gt;
  298. &lt;p&gt;&lt;em&gt;Jos kohteet puuttuvat kartalta voit piirtää ne itse, tai ilmoittaa puutteista OSM-yhteisölle. Aineiston muokkausta varten tarvitaan käyttäjätunnus.&lt;/em&gt;&lt;/p&gt;
  300. &lt;h2&gt;OpenStreetMap-tunnukset&lt;/h2&gt;
  302. &lt;p&gt;&lt;img src="" alt="Kuva: SignUp to OpenStreetMap"/&gt;&lt;/p&gt;
  304. &lt;p&gt;&lt;strong&gt;Tehtävä 3: Mene osoitteeseen &lt;a href="" rel="nofollow"&gt;;/a&gt; ja luo itsellesi käyttäjätunnus.&lt;/strong&gt;&lt;/p&gt;
  306. &lt;p&gt;&lt;em&gt;OpenStreetMap aineisto kattaa hyvin Suomen isojen kaupunkien tieverkon ja rakennuskannan, ja luultavasti kotitalosi ja koulurakennus löytyvät jo kartalta. Seuraavassa osiossa käymme läpi OpenStreetMap editoinnin perusperiaatteet, jotta voisimme muokata aineistoa kartoittamattomilta alueilta.&lt;/em&gt;&lt;/p&gt;
  308. &lt;h3&gt;Lähteet&lt;/h3&gt;
  310. &lt;ul&gt;
  311. &lt;li&gt;Learn OpenStreetMap Step by Step: &lt;a href="" rel="nofollow"&gt;;/a&gt; &lt;/li&gt;
  312. &lt;/ul&gt;
  313. </description>
  314.      <dc:creator>VuokkoH</dc:creator>
  315.      <pubDate>Thu, 27 Apr 2017 16:29:21 +0000</pubDate>
  316.      <comments></comments>
  317.    </item>
  318.    <item>
  319.      <title>Ottawa Mapping Party!</title>
  320.      <link></link>
  321.      <guid></guid>
  322.      <description>&lt;p&gt;The OpenStreetMap Ottawa community was working on the &lt;a href="" rel="nofollow"&gt;Ottawa building import&lt;/a&gt; that led to an addition of 350K buildings and address points to OpenStreetMap.&lt;/p&gt;
  324. &lt;p&gt;This project was completed on the 7th of April with a &lt;a href="" rel="nofollow"&gt;mapping party&lt;/a&gt; hosted by the community, and Mapbox had an opportunity to sponsor this mapping party. As a Mapbox data team member, this was a great opportunity for me to interact with the community and get an understanding of the workflows they follow to make this import happen! The community is currently validating these tasks.&lt;/p&gt;
  326. &lt;p&gt;&lt;img src="" alt="ottawa"/&gt;
  327. &lt;em&gt;The map showing the buildings added by the community made using &lt;a href="" rel="nofollow"&gt;Mapbox&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  329. &lt;p&gt;It was early morning (5 am) in Bangalore but it was worth waking up to interact with the folks from &lt;em&gt;literally&lt;/em&gt; the other end of the world ;). There were nearly 25 attendees for the meetup and it was great to chat with the organisers and get an understanding of the import, and in general the community! Love how different communities work together for making OpenStreetMap the best map of the world! Special thanks to &lt;a href="" rel="nofollow"&gt;Rps333&lt;/a&gt; for helping us in making this happen!🙇🏼 &lt;/p&gt;
  331. &lt;p&gt;&lt;img src="" alt=""/&gt;
  332. &lt;em&gt;Members of the OSM Ottawa community at the weekend mapping party to discuss the Ottawa building import and mapping the remaining buildings in the city interacting with the Mapbox data team in India&lt;/em&gt;&lt;/p&gt;
  333. </description>
  334.      <dc:creator>jinalfoflia</dc:creator>
  335.      <pubDate>Wed, 26 Apr 2017 14:21:14 +0000</pubDate>
  336.      <comments></comments>
  337.    </item>
  338.    <item>
  339.      <title>Det Røde Spor</title>
  340.      <link></link>
  341.      <guid></guid>
  342.      <description>&lt;p&gt;Det Røde Spor i Hareskoven&lt;/p&gt;
  343. </description>
  344.      <dc:creator>Martin Møller</dc:creator>
  345.      <pubDate>Wed, 26 Apr 2017 11:52:35 +0000</pubDate>
  346.      <comments></comments>
  347.      <geo:lat>55.7709729454616</geo:lat>
  348.      <geo:long>12.3803901672363</geo:long>
  349.      <georss:point>55.7709729454616 12.3803901672363</georss:point>
  350.    </item>
  351.    <item>
  352.      <title>Dodo Coiff</title>
  353.      <link></link>
  354.      <guid></guid>
  355.      <description>&lt;p&gt;Dodo Coiff
  356. (Coiffure à domicile)&lt;/p&gt;
  358. &lt;p&gt;Web :
  359. &lt;a href="" rel="nofollow"&gt;;/a&gt;&lt;/p&gt;
  361. &lt;p&gt;Tel :
  362. 0699460395
  363. +33699460395&lt;/p&gt;
  364. </description>
  365.      <dc:creator>Dodo Coiff</dc:creator>
  366.      <pubDate>Wed, 26 Apr 2017 11:34:02 +0000</pubDate>
  367.      <comments></comments>
  368.    </item>
  369.    <item>
  370.      <title>Tagondaing city</title>
  371.      <link></link>
  372.      <guid></guid>
  373.      <description>&lt;p&gt;This area is Tagondaing village&lt;/p&gt;
  374. </description>
  375.      <dc:creator>Won Raw</dc:creator>
  376.      <pubDate>Wed, 26 Apr 2017 09:49:41 +0000</pubDate>
  377.      <comments></comments>
  378.      <geo:lat>16.0680358186091</geo:lat>
  379.      <geo:long>97.906965698121</geo:long>
  380.      <georss:point>16.0680358186091 97.906965698121</georss:point>
  381.    </item>
  382.    <item>
  383.      <title>สูตรการเล่นไฮโล วิธีฟังเสียงไฮโล </title>
  384.      <link></link>
  385.      <guid></guid>
  386.      <description>&lt;p&gt;เพิ่งรู้ว่าเล่นไฮโลแล้วได้เงินจริงก็วันนี้ กับเว็บ royal-th ทดลองเล่นมาหลายเว็บไซต์แล้ว บางเว็บก็โหลดช้ามาก บางเว็บไม่แจกโปรโมชั่น แต่สำหรับเว็บนี้คุ้มสุดๆกับการสมัครครั้งแรกก็รับทันที 100% ของเงินยอดฝากแรก รวมไปถึง promotion มีมากกว่า 10 รายการ รูปแบบของเว็บไซต์มีความรวดเร็วตอบสนองกับโทรศัพท์มากที่สุด และที่สำคัญไม่ดาวน์โหลดใดๆทั้งสิ้น&lt;/p&gt;
  387. </description>
  388.      <dc:creator>Royal-hilo2265 Good income</dc:creator>
  389.      <pubDate>Wed, 26 Apr 2017 09:22:01 +0000</pubDate>
  390.      <comments></comments>
  391.    </item>
  392.    <item>
  393.      <title>Review of Africa Highway Tags</title>
  394.      <link></link>
  395.      <guid></guid>
  396.      <description>&lt;p&gt;In Ethiopia most of the population lives in rural areas outside of towns and villages.
  397. The existing OSM road tagging is inadequate to adequately document the functional use of a road.&lt;/p&gt;
  399. &lt;p&gt;The Africa Highway tags are a good start but do not have a tag that is appropriate for rural residential roads.&lt;/p&gt;
  401. &lt;p&gt;At the State of the Map Africa 2017 &lt;a href="" rel="nofollow"&gt;;/a&gt; we will be discussing the tagging for roads in an Africa context.
  402. #SOTMAfrica&lt;/p&gt;
  403. </description>
  404.      <dc:creator>Palolo</dc:creator>
  405.      <pubDate>Wed, 26 Apr 2017 02:09:22 +0000</pubDate>
  406.      <comments></comments>
  407.      <geo:lat>6.9114979</geo:lat>
  408.      <geo:long>38.415579</geo:long>
  409.      <georss:point>6.9114979 38.415579</georss:point>
  410.    </item>
  411.  </channel>
  412. </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