Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

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

Source: http://www.openstreetmap.org/diary/rss

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:georss="http://www.georss.org/georss">
  3.  <channel>
  4.    <title>OpenStreetMap diary entries</title>
  5.    <description>Recent diary entries from users of OpenStreetMap</description>
  6.    <link>https://www.openstreetmap.org/diary</link>
  7.    <image>
  8.      <url>https://www.openstreetmap.org/assets/mag_map-rss2.0-4f212209b7745e172d20b38bd751327337c6b7a7fc641c8b6d54f7ff33abcea7.png</url>
  9.      <title>OpenStreetMap diary entries</title>
  10.      <width>100</width>
  11.      <height>100</height>
  12.      <link>https://www.openstreetmap.org/diary</link>
  13.    </image>
  14.    <item>
  15.      <title>Die Landestochter SWEG nutzt Openstreetmap</title>
  16.      <link>https://www.openstreetmap.org/user/q_un_go/diary/392279</link>
  17.      <guid>https://www.openstreetmap.org/user/q_un_go/diary/392279</guid>
  18.      <description>&lt;p&gt;Die Landestochter SWEG nutzt für die Umgebungskarten ihres Schienenersatzverkehrs im Elztal Ooenstreetmap.&lt;/p&gt;
  19.  
  20. &lt;p&gt;&lt;a href="https://www.sweg.de/html/schienenersatzverkehr_elztal.html" rel="nofollow noopener noreferrer"&gt;https://www.sweg.de/html/schienenersatzverkehr_elztal.html&lt;/a&gt;&lt;/p&gt;
  21.  
  22. &lt;p&gt;Die Karte z.B. hier ist ja schön:
  23. &lt;a href="https://www.sweg.de/html/media/dl.html?i=46288" rel="nofollow noopener noreferrer"&gt;https://www.sweg.de/html/media/dl.html?i=46288&lt;/a&gt;&lt;/p&gt;
  24.  
  25. &lt;p&gt;Und wenn die Landestochter und die Nahverkehrsgesellschaft des Landes lernen, wie man korrekt die Urheber und die Lizenz der Karte attribuiert, wäre es noch schöner.
  26. Aber angesichts des Fiaskos mit der S1 hat die NVBW wohl nun andere Sorgen mit der S2. Und da das Land ja via Maps4Bw auch etwas an OSM gegeben hat, will ich auch nicht zu kleinlich sein.&lt;/p&gt;
  27. </description>
  28.      <dc:creator>q_un_go</dc:creator>
  29.      <pubDate>Sun, 23 Feb 2020 23:21:39 +0000</pubDate>
  30.      <comments>https://www.openstreetmap.org/user/q_un_go/diary/392279#comments</comments>
  31.      <geo:lat>48.069345042007</geo:lat>
  32.      <geo:long>7.88267970085144</geo:long>
  33.      <georss:point>48.069345042007 7.88267970085144</georss:point>
  34.    </item>
  35.    <item>
  36.      <title>Using Layer Opacity to Validate (ft. JOSM)</title>
  37.      <link>https://www.openstreetmap.org/user/Uyan/diary/392277</link>
  38.      <guid>https://www.openstreetmap.org/user/Uyan/diary/392277</guid>
  39.      <description>&lt;p&gt;A quick but useful tip I found hidden in this video:&lt;/p&gt;
  40.  
  41. &lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=iwJnZQFi_C8" rel="nofollow noopener noreferrer"&gt;https://www.youtube.com/watch?v=iwJnZQFi_C8&lt;/a&gt;&lt;/p&gt;
  42.  
  43. &lt;p&gt;At around 24:00, the speaker notes the use of opacity: using multiple layers, and lowering the opacity of the front/uppermost layer to verify map alterations across different data sets (“data sets” being the layers themselves i.e. Bing, Esri, Maxar etc.). A tip I’ve already had good success with. I find lowering the opacity to around 70% works nicely.&lt;/p&gt;
  44. </description>
  45.      <dc:creator>Uyan</dc:creator>
  46.      <pubDate>Sun, 23 Feb 2020 21:18:07 +0000</pubDate>
  47.      <comments>https://www.openstreetmap.org/user/Uyan/diary/392277#comments</comments>
  48.    </item>
  49.    <item>
  50.      <title>Nizi region, Democratic Republic of Congo</title>
  51.      <link>https://www.openstreetmap.org/user/AmeliaMap/diary/392276</link>
  52.      <guid>https://www.openstreetmap.org/user/AmeliaMap/diary/392276</guid>
  53.      <description>&lt;h1 id="missing-maps-nizi-region-democratic-republic-of-congo-2"&gt;8012 - Missing Maps: Nizi region, Democratic Republic of Congo (2)&lt;/h1&gt;
  54. &lt;p&gt;SHARE&lt;/p&gt;
  55.  
  56. &lt;p&gt;MSF is assisting in an Indoor Residual Spraying (IRS) campaign in the Nizi region in Ituri in the Democratic Republic of Congo. During this campaign insecticides will be applied on the inside of dwellings where malaria infected mosquitos rest. As a result the number of mosquitos will go down, which prevents the transition of Malaria.&lt;/p&gt;
  57.  
  58. &lt;p&gt;Spent 2 hours editing sectors and mapping buildings.&lt;/p&gt;
  59. </description>
  60.      <dc:creator>AmeliaMap</dc:creator>
  61.      <pubDate>Sun, 23 Feb 2020 20:57:21 +0000</pubDate>
  62.      <comments>https://www.openstreetmap.org/user/AmeliaMap/diary/392276#comments</comments>
  63.    </item>
  64.    <item>
  65.      <title>State of the Map Baltics 2020: two weeks reminder</title>
  66.      <link>https://www.openstreetmap.org/user/Zverik/diary/392275</link>
  67.      <guid>https://www.openstreetmap.org/user/Zverik/diary/392275</guid>
  68.      <description>&lt;p&gt;&lt;img src="https://2020.sotm-baltics.org/img/sotmbaltics2020.png" alt=""&gt;&lt;/p&gt;
  69.  
  70. &lt;p&gt;Reminding you that there is a big conference coming up: the State of the
  71. Map Baltics 2020 in Riga, Latvia. How big? Well, half a thousand
  72. attendees have already registered. It’s time for you to buy a flight and
  73. meet us and other GIS enthusiasts and professionals on 6th of March:&lt;/p&gt;
  74.  
  75. &lt;p&gt;&lt;a href="https://2020.sotm-baltics.org/" rel="nofollow noopener noreferrer"&gt;https://2020.sotm-baltics.org/&lt;/a&gt;&lt;/p&gt;
  76.  
  77. &lt;p&gt;Why so big? Well, it’s just a part of a bigger conference: Baltic GIT is
  78. not related to version control systems, but to geospatial technologies.
  79. Think of it as a partly local FOSS4G, only with less focus on open
  80. source. And it’s free!&lt;/p&gt;
  81.  
  82. &lt;p&gt;We’ve got Allan Mustard of OSMF, Stefan Gustafsson of ESA, Tomas
  83. Straupis, Kirill Bondarenko, Danil Kirsanov, Evgen Bodunov, Rihards
  84. Olups and dozens of other speakers and OSM members. Do visit, and let’s
  85. enjoy Riga together!&lt;/p&gt;
  86. </description>
  87.      <dc:creator>Zverik</dc:creator>
  88.      <pubDate>Sun, 23 Feb 2020 20:54:28 +0000</pubDate>
  89.      <comments>https://www.openstreetmap.org/user/Zverik/diary/392275#comments</comments>
  90.    </item>
  91.    <item>
  92.      <title>Mapping; Interessant, uitdagend en nieuw voor mij</title>
  93.      <link>https://www.openstreetmap.org/user/ForLackOfABetterName/diary/392274</link>
  94.      <guid>https://www.openstreetmap.org/user/ForLackOfABetterName/diary/392274</guid>
  95.      <description>&lt;p&gt;Hallo beste medemapper,&lt;/p&gt;
  96.  
  97. &lt;p&gt;Ik ben vandaag begonnen met het maken van edits in mijn buurt. Ik vind het erg interessant aangezien kaarten en topografische dingen mij altijd al geïnteresseerd hebben. Misschien een nieuwe hobby… We zullen zien waar dit mij brengt. Ik heb nog nooit iets dergelijks gedaan dus ik ben erg benieuwd naar wat ik allemaal tegen zal gaan komen. De eerste stap is in ieder geval gezet.&lt;/p&gt;
  98.  
  99. &lt;p&gt;Nog een prettige avond en tot later
  100. Met vriendelijke groet,
  101. F.L.O.A.B.N.&lt;/p&gt;
  102. </description>
  103.      <dc:creator>ForLackOfABetterName</dc:creator>
  104.      <pubDate>Sun, 23 Feb 2020 20:29:08 +0000</pubDate>
  105.      <comments>https://www.openstreetmap.org/user/ForLackOfABetterName/diary/392274#comments</comments>
  106.    </item>
  107.    <item>
  108.      <title>住宅區與分隔島</title>
  109.      <link>https://www.openstreetmap.org/user/flyingmint/diary/392272</link>
  110.      <guid>https://www.openstreetmap.org/user/flyingmint/diary/392272</guid>
  111.      <description>&lt;p&gt;  凡看到有建築的部份都畫上住宅範圍,也不管是不是工廠、商店、倉庫、養雞場…等等各種用途,作法相當粗糙隨便。這情形多到讓人沮喪,我覺得啊,OSM應該是畫手上有資料佐證,或自己實地走過的地方,對於不確定的,放著,總會有人處理。上個月想說來看一下安平區五期這地方,同樣的情形,範圍過大加上資料相當繁雜,因為它不是以街區﹝Block﹞為單位作繪製,島製資料載入過大,拖慢整個電腦效能,只好放棄。五期大部分是住宅區沒錯,但是如此大範圍標示,對圖資更動與修正,實是不小的負擔。&lt;/p&gt;
  112. &lt;p&gt;  有分隔島的道路,並不是實際獨立的道路,畫作是兩條單行線,也是挺不合理的,使用上也相當混淆。&lt;/p&gt;
  113. &lt;p&gt;  如果先翻譯OSM說明文件再來修正圖資,這樣是不是可以降低這樣的事情發生呢。只是我興趣還是比較喜歡到處跑,動滑鼠比動鍵盤輕鬆。若要翻譯,應該會從重點部分著手,看心情再翻譯剩下全篇。&lt;/p&gt;
  114. </description>
  115.      <dc:creator>flyingmint</dc:creator>
  116.      <pubDate>Sun, 23 Feb 2020 15:03:55 +0000</pubDate>
  117.      <comments>https://www.openstreetmap.org/user/flyingmint/diary/392272#comments</comments>
  118.    </item>
  119.    <item>
  120.      <title>Reminders/Notes about OSM</title>
  121.      <link>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392271</link>
  122.      <guid>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392271</guid>
  123.      <description>&lt;p&gt;Every object in the OSM database has coordinates (in degrees in the WGS84 projection/EPSG:4326), creation date, author and a description.&lt;/p&gt;
  124.  
  125. &lt;p&gt;The imagery usually has offset issues. The problem is that imagery usually isn’t correctly placed with respect to the coord system. The iD editor has a tool for temporarily aligning the imagery with polygons and whatnot. It’s found at the bottom of the imagery dialog.&lt;/p&gt;
  126.  
  127. </description>
  128.      <dc:creator>John O'Hanley</dc:creator>
  129.      <pubDate>Sun, 23 Feb 2020 14:07:15 +0000</pubDate>
  130.      <comments>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392271#comments</comments>
  131.    </item>
  132.    <item>
  133.      <title>Geodata references </title>
  134.      <link>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392267</link>
  135.      <guid>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392267</guid>
  136.      <description>&lt;p&gt;The Province has excellent resources online.&lt;/p&gt;
  137.  
  138. &lt;p&gt;&lt;a href="https://www.princeedwardisland.ca/en/information/finance/geographic-information-systems" rel="nofollow noopener noreferrer"&gt;Provincial GIS Resources&lt;/a&gt;&lt;/p&gt;
  139.  
  140. &lt;p&gt;&lt;a href="https://peitie.maps.arcgis.com/apps/MapJournal/index.html?appid=225121b0e2ab415fa48c3d6dad7d5df7" rel="nofollow noopener noreferrer"&gt;Active Living Map&lt;/a&gt;&lt;/p&gt;
  141.  
  142. &lt;p&gt;&lt;a href="http://www.gov.pe.ca/gis/index.php3?number=77543" rel="nofollow noopener noreferrer"&gt;GIS Data Layers&lt;/a&gt;&lt;/p&gt;
  143.  
  144. &lt;p&gt;&lt;a href="https://open.canada.ca/data/en/dataset/4c1ae636-5c7c-41ab-a943-1f82ae3faf89" rel="nofollow noopener noreferrer"&gt;PEI National Road Network PEINRN&lt;/a&gt; Up to date, includes all the data you’d ever need.&lt;/p&gt;
  145.  
  146. &lt;p&gt;&lt;a href="https://open.canada.ca/data/en/dataset/fe945388-1dd9-4a4a-9a1e-5c552579a28c" rel="nofollow noopener noreferrer"&gt;Place names in Canada&lt;/a&gt; No type info, or population info! No indication of the precision of the lat/long. English and French.&lt;/p&gt;
  147.  
  148. &lt;p&gt;&lt;a href="https://www.nrcan.gc.ca/earth-sciences/geography/download-geographical-names-data/9245" rel="nofollow noopener noreferrer"&gt;Feature names in Canada&lt;/a&gt;. Not bad. 1869 items for PEI. Water and towns. Dowside: no population number, BUT it has categories that can do the same thing: locality, community, town, city.&lt;/p&gt;
  149.  
  150. &lt;p&gt;&lt;a href="https://open.canada.ca/data/en/dataset/a4b190fe-e090-4e6d-881e-b87956c07977" rel="nofollow noopener noreferrer"&gt;Lakes and rivers- National Hydro Network - NHN - GeoBase Series&lt;/a&gt;&lt;/p&gt;
  151.  
  152. &lt;p&gt;&lt;a href="https://www.naturalearthdata.com/features/" rel="nofollow noopener noreferrer"&gt;Natural Earth - motherlode of global mapping data&lt;/a&gt;. Seems to be of high quality. 1:10000 is their most-detailed recommended scale.&lt;/p&gt;
  153.  
  154. &lt;p&gt;&lt;a href="https://www.naturalearthdata.com/downloads/10m-cultural-vectors/10m-populated-places/" rel="nofollow noopener noreferrer"&gt;Global place names with pop&lt;/a&gt;. About 7300 places. Small towns missing.&lt;/p&gt;
  155.  
  156. &lt;p&gt;&lt;a href="http://srtm.csi.cgiar.org/faq/" rel="nofollow noopener noreferrer"&gt;Global elevation data&lt;/a&gt; - the free versions of this data are usually based on data from NASA called &lt;a href="https://en.wikipedia.org/wiki/Shuttle_Radar_Topography_Mission" rel="nofollow noopener noreferrer"&gt;SRTM&lt;/a&gt;. You can download it &lt;a href="https://earthexplorer.usgs.gov/" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt;. That original data set has holes, that can be filled by interpolating. The CGIAR data set  interpolates. More info &lt;a href="https://wiki.openstreetmap.org/wiki/Shaded_relief_maps_using_mapnik#Download_and_import.2Fpreparation_of_elevation_data_into_postgis.2Ffor_hill_shading" rel="nofollow noopener noreferrer"&gt;here.&lt;/a&gt; The resolution comes in 2 flavours, 90m and 30m. Here’s an &lt;a href="https://wiki.openstreetmap.org/wiki/File:Lipno.png" rel="nofollow noopener noreferrer"&gt;example of it being used for shading&lt;/a&gt;. It’s certainly fine for indicating general elevation - &lt;a href="http://srtm.csi.cgiar.org/wp-content/uploads/files/image/srtm_th_24_03.jpg" rel="nofollow noopener noreferrer"&gt;example&lt;/a&gt;. Reference for &lt;a href="https://wiki.openstreetmap.org/wiki/Shaded_relief_maps_using_mapnik" rel="nofollow noopener noreferrer"&gt;mapnik&lt;/a&gt;.&lt;/p&gt;
  157.  
  158. &lt;p&gt;It’s likely best to use transparency, and the &lt;a href="https://wiki.openstreetmap.org/wiki/Hillshading_using_the_Alpha_Channel_of_an_Image" rel="nofollow noopener noreferrer"&gt;alpha-channel&lt;/a&gt;, to render the hillshading.&lt;/p&gt;
  159.  
  160. &lt;p&gt;&lt;a href="https://openmaptiles.com/downloads/dataset/hillshade/#8.21/46.288/-63.2434" rel="nofollow noopener noreferrer"&gt;Global elevation shading, $1000US&lt;/a&gt;&lt;/p&gt;
  161.  
  162. &lt;p&gt;Also see &lt;a href="https://www.opendem.info" rel="nofollow noopener noreferrer"&gt;OpenDEM&lt;/a&gt;.&lt;/p&gt;
  163.  
  164. &lt;p&gt;Global Bathymetry -
  165. &lt;a href="https://www.gebco.net/data_and_products/gridded_bathymetry_data/" rel="nofollow noopener noreferrer"&gt;GEBCO&lt;/a&gt; may be low res, hard to say. Also see &lt;a href="https://www.opendem.info/download_bathymetry.html" rel="nofollow noopener noreferrer"&gt;OpenDEM&lt;/a&gt;.&lt;/p&gt;
  166.  
  167. &lt;p&gt;Bathymetry of the Gulf of St. Lawrence?&lt;/p&gt;
  168.  
  169. &lt;p&gt;&lt;a href="https://www.charlottetown.ca/resident_services/maps" rel="nofollow noopener noreferrer"&gt;Municipal Zoning Maps&lt;/a&gt;&lt;/p&gt;
  170.  
  171. &lt;p&gt;&lt;a href="http://www.gov.pe.ca/civicaddress/index.php3" rel="nofollow noopener noreferrer"&gt;Provincial Civic Addresses&lt;/a&gt;&lt;/p&gt;
  172.  
  173. &lt;p&gt;Note that large municipalities (including Charlottetown) handle their own civic addressing.There’s location data for each address. The exact point seems to line up with the driveway of a house, not the centroid of the house. This makes sense, for access by emergency services. The nominal precision is about 1 metre. Example:&lt;/p&gt;
  174.  
  175. &lt;p&gt;91 PRINCE CHARLES DR CHARLOTTETOWN QUN 46.23739 -63.14737&lt;/p&gt;
  176.  
  177. &lt;p&gt;&lt;a href="http://www.gov.pe.ca/photos/original/tir_roadatlas14.pdf" rel="nofollow noopener noreferrer"&gt;Provincial road atlas 2014&lt;/a&gt; Quite nice, 102 pages, printable PDF. Not geodata, but a finished product.&lt;/p&gt;
  178.  
  179. &lt;p&gt;&lt;a href="http://www.gov.pe.ca/gis/index.php3?number=77583&amp;amp;lang=E" rel="nofollow noopener noreferrer"&gt;Confederation Trail, and Road Netwwork&lt;/a&gt;&lt;/p&gt;
  180. </description>
  181.      <dc:creator>John O'Hanley</dc:creator>
  182.      <pubDate>Sat, 22 Feb 2020 13:36:45 +0000</pubDate>
  183.      <comments>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392267#comments</comments>
  184.    </item>
  185.    <item>
  186.      <title>First edit completed</title>
  187.      <link>https://www.openstreetmap.org/user/kgbarth/diary/392260</link>
  188.      <guid>https://www.openstreetmap.org/user/kgbarth/diary/392260</guid>
  189.      <description>&lt;p&gt;Finally submitted a first edit to OSM - a nordic skiing track that is groomed by scooter.
  190. (Uværsløypa (775423923)). The track is drawn based on GPS output from in field survey.&lt;/p&gt;
  191.  
  192. &lt;p&gt;Interesting point is that neither Uværsløypa, nor the longer loop around it shows up in OSM when zooming to this area, unless I go in edit mode - then they both show up.&lt;/p&gt;
  193.  
  194. &lt;p&gt;Question: part of the larger loop around Uværsløypa is a a path in summer. Can additional attributes be added to a section of the nordic track to show summer use?&lt;/p&gt;
  195. </description>
  196.      <dc:creator>kgbarth</dc:creator>
  197.      <pubDate>Fri, 21 Feb 2020 23:37:05 +0000</pubDate>
  198.      <comments>https://www.openstreetmap.org/user/kgbarth/diary/392260#comments</comments>
  199.      <geo:lat>60.2992627529715</geo:lat>
  200.      <geo:long>8.55340361595154</geo:long>
  201.      <georss:point>60.2992627529715 8.55340361595154</georss:point>
  202.    </item>
  203.    <item>
  204.      <title>What Imagery to Use for Validation?</title>
  205.      <link>https://www.openstreetmap.org/user/Uyan/diary/392259</link>
  206.      <guid>https://www.openstreetmap.org/user/Uyan/diary/392259</guid>
  207.      <description>&lt;p&gt;After I validate a square in HOTOSM Tasking Manager, I label what imagery I validated the square against (e.g. Bing, Esri, Maxar). I got this idea after seeing mappers comment with which imagery they mapped their buildings, roads etc.&lt;/p&gt;
  208.  
  209. &lt;p&gt;The problem arises when the imagery is validated against a different imagery that was used to map the area. For example, I regularly validate against Bing Aerial Imagery, but sometimes users have noted that they used Maxar Premium Imagery. It would make sense for me to instead validate using the same imagery - in this case Maxar - but when loading the imagery in JOSM I get the following message:&lt;/p&gt;
  210.  
  211. &lt;p&gt;Error downloading tiles: INVALID
  212. CONNECT ID: &lt;em&gt;apiKey&lt;/em&gt;&lt;/p&gt;
  213.  
  214. &lt;p&gt;There are also other problems. Bing has the highest resolution imagery, the main reason it is my preferred imagery to validate against. Esri has lower resolution, and is also inconsistent with Bing, in large part due to them having taken the pictures at different times/dates in history. Which poses another question: which imagery is the most up-to-date? I’ve assumed Bing, but that assumption is without reason.&lt;/p&gt;
  215. </description>
  216.      <dc:creator>Uyan</dc:creator>
  217.      <pubDate>Fri, 21 Feb 2020 17:55:22 +0000</pubDate>
  218.      <comments>https://www.openstreetmap.org/user/Uyan/diary/392259#comments</comments>
  219.    </item>
  220.    <item>
  221.      <title>Street names - change to exactly match those used by the Province</title>
  222.      <link>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392258</link>
  223.      <guid>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392258</guid>
  224.      <description>&lt;p&gt;I notice that Canada Post and the province now use abbreviated street names. What I mean by that is, for example, “Grafton ST” is used, not “Grafton Street”. The last part is abbreviated (and capitalized):&lt;/p&gt;
  225.  
  226. &lt;ul&gt;
  227.  &lt;li&gt;ST - street&lt;/li&gt;
  228.  &lt;li&gt;DR - drive&lt;/li&gt;
  229.  &lt;li&gt;LN - lane&lt;/li&gt;
  230.  &lt;li&gt;CRT - court&lt;/li&gt;
  231.  &lt;li&gt;AV - avenue&lt;/li&gt;
  232.  &lt;li&gt;… and so on …&lt;/li&gt;
  233. &lt;/ul&gt;
  234.  
  235. &lt;p&gt;Here’s a link to the &lt;a href="http://www.gov.pe.ca/civicaddress/streetplanner/index.php3?selection=community" rel="nofollow noopener noreferrer"&gt;Provincial data&lt;/a&gt;.&lt;/p&gt;
  236.  
  237. &lt;p&gt;It seems like the data in OSM for Charlottetown is manually entered, and not uploaded en masse using data from the province.&lt;/p&gt;
  238.  
  239. &lt;p&gt;My feeling is that I would like to change the street names to match EXACTLY what’s defined by the Province. Reasons for doing so:&lt;/p&gt;
  240.  
  241. &lt;ul&gt;
  242.  &lt;li&gt;it’s always shorter text! This helps in rendering maps, since space is at such a premium on a map.&lt;/li&gt;
  243.  &lt;li&gt;it matches exactly the official source. This would make it possible (in principle) to write queries once a year, to see if there’s any mismatch at all between the Province and OSM. Thus the two could be kept in fairly close sync.&lt;/li&gt;
  244.  &lt;li&gt;street names are probably the single most important items on a typical map. To be able to verify that they match the Province’s official list would be a boon.&lt;/li&gt;
  245. &lt;/ul&gt;
  246.  
  247. </description>
  248.      <dc:creator>John O'Hanley</dc:creator>
  249.      <pubDate>Fri, 21 Feb 2020 17:26:38 +0000</pubDate>
  250.      <comments>https://www.openstreetmap.org/user/John%20O'Hanley/diary/392258#comments</comments>
  251.      <geo:lat>46.2335279137657</geo:lat>
  252.      <geo:long>-63.1255960464478</geo:long>
  253.      <georss:point>46.2335279137657 -63.1255960464478</georss:point>
  254.    </item>
  255.    <item>
  256.      <title>I'm getting tired...</title>
  257.      <link>https://www.openstreetmap.org/user/AkuAnakTimur/diary/392257</link>
  258.      <guid>https://www.openstreetmap.org/user/AkuAnakTimur/diary/392257</guid>
  259.      <description>&lt;p&gt;… seeing changes made by remote mappers.&lt;/p&gt;
  260.  
  261. &lt;p&gt;I get it, some corporates want(ed) gaps in the map to be populated as rapidly as possible &lt;em&gt;to be exploited in the near future&lt;/em&gt; (well, what else?).&lt;/p&gt;
  262.  
  263. &lt;p&gt;I’ve lost track whether field data, collected on the ground (&lt;code&gt;source=survey&lt;/code&gt;), as my hobby, simply for fun (when I began mapping back in 2013) is completely overwritten by paid contractors from thousands of miles away.&lt;/p&gt;
  264.  
  265. &lt;p&gt;Five years time, through the &lt;em&gt;Black Mirror&lt;/em&gt; might translate into the measure of an eon. Back then, high resolution imagery were only available for select places. So GPS tracks made mapping possible. Fast forward in time, we get additional imagery layers to make mapping easier - with an invisible warning sign that imageries may not really tell what’s what with respect to the reality.&lt;/p&gt;
  266.  
  267. &lt;p&gt;Now as this particular hobby has got its way shoved by other important life priorities, sometimes finding the right time to map is a challenge - but I may have not given up to volunteer uploading geodata into OpenStreetMap - right from where I traverse with my humble mode of transportation.&lt;/p&gt;
  268.  
  269. &lt;p&gt;I’m not totally frustrated with all these remote mappers. Some areas may have been mapped gorgeously e.g. unmapped highways in housing estates with regular patterns were mapped by these team - I really disliked mapping these, though.&lt;/p&gt;
  270.  
  271. &lt;p&gt;Some may have access to better data e.g. derived GPS tracks from trips made by car-share rides, or possible unmapped highways outputs from a machine vision with the assistance of imagery with better clarity.&lt;/p&gt;
  272.  
  273. &lt;p&gt;Don’t get me wrong, everyone including me, made mistakes (e.g. not responding to feedbacks and so on).&lt;/p&gt;
  274.  
  275. &lt;p&gt;But sometimes, things get too much - I may need to take a break. So, there goes my diary entry: I just wanted to vent out things. Happy mapping, everyone!&lt;/p&gt;
  276. </description>
  277.      <dc:creator>AkuAnakTimur</dc:creator>
  278.      <pubDate>Fri, 21 Feb 2020 16:00:52 +0000</pubDate>
  279.      <comments>https://www.openstreetmap.org/user/AkuAnakTimur/diary/392257#comments</comments>
  280.    </item>
  281.    <item>
  282.      <title>Event,- &amp; Hochzeits DJ Helmut Kleinert</title>
  283.      <link>https://www.openstreetmap.org/user/HKEvents/diary/392255</link>
  284.      <guid>https://www.openstreetmap.org/user/HKEvents/diary/392255</guid>
  285.      <description>&lt;p&gt;Bei uns finden Sie alles rund um das Thema Hochzeit, Heiraten!
  286. Eventplanung, Veranstalter-Service, Kinderbetreuung, DJ-Service, Ton,-&amp;amp; Lichtverleih, Foto-Booth, Fotography, Feuershows, Feuerwerk, Band-Vermittlung, Lokation, Weddingplaner, Hochzeitsplanung, Hochzeitsmessen, Vererinsfeste, Schulabschlussfeste, Sportveranstaltungen, Moderation und jede menge mehr…..
  287. Wir freuen uns auf Ihren Anruf! Ihr Helmut Kleinert&lt;/p&gt;
  288.  
  289. </description>
  290.      <dc:creator>HKEvents</dc:creator>
  291.      <pubDate>Fri, 21 Feb 2020 09:47:13 +0000</pubDate>
  292.      <comments>https://www.openstreetmap.org/user/HKEvents/diary/392255#comments</comments>
  293.      <geo:lat>48.7832221067477</geo:lat>
  294.      <geo:long>10.955705344677</geo:long>
  295.      <georss:point>48.7832221067477 10.955705344677</georss:point>
  296.    </item>
  297.    <item>
  298.      <title>Source code of blender-osm addon for Blender 3d is back on Github</title>
  299.      <link>https://www.openstreetmap.org/user/vvoovv/diary/392254</link>
  300.      <guid>https://www.openstreetmap.org/user/vvoovv/diary/392254</guid>
  301.      <description>&lt;p&gt;The source code of the blender-osm addon is back on Github:
  302. &lt;a href="https://github.com/vvoovv/blender-osm/tree/release" rel="nofollow noopener noreferrer"&gt;https://github.com/vvoovv/blender-osm/tree/release&lt;/a&gt;&lt;/p&gt;
  303.  
  304. &lt;p&gt;Unless you are a developer, please get the addon &lt;a href="https://gumroad.com/l/blender-osm" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;
  305.  
  306. &lt;p&gt;&lt;img src="https://raw.githubusercontent.com/wiki/vvoovv/blender-osm/images/blender-osm.png" alt="blender-osm"&gt;&lt;/p&gt;
  307. </description>
  308.      <dc:creator>vvoovv</dc:creator>
  309.      <pubDate>Fri, 21 Feb 2020 09:20:19 +0000</pubDate>
  310.      <comments>https://www.openstreetmap.org/user/vvoovv/diary/392254#comments</comments>
  311.    </item>
  312.    <item>
  313.      <title>Подъезды, квартиры СРВ, бухты по востоку Авачинской губы</title>
  314.      <link>https://www.openstreetmap.org/user/%D0%9C%D1%83%D1%81%D0%BA%D0%B0%D1%82%D0%B8%D0%BD%D1%8C%D0%B5%D0%B2%20%D0%9D%D0%B8%D0%BA%D0%BE%D0%BB%D0%B0%D0%B9/diary/392248</link>
  315.      <guid>https://www.openstreetmap.org/user/%D0%9C%D1%83%D1%81%D0%BA%D0%B0%D1%82%D0%B8%D0%BD%D1%8C%D0%B5%D0%B2%20%D0%9D%D0%B8%D0%BA%D0%BE%D0%BB%D0%B0%D0%B9/diary/392248</guid>
  316.      <description>&lt;p&gt;Добавил на СРВ здания и дороги ТЭЦ-1, определил границы судоремонтной верфи и ЖБФ. Проставил все подъезды и квартиры по ул Индустриальная, Заводская, Школьная, Садовый переулок, ул штурмана Елагина, по ул Свердлова и рядом некоторые дома по Океанской. Добавил бухты и мысы по восточному побережью Авачинской губы.  Добавил все почтовые отделения в Ленинском районе от СРВ до Электрона и Сероглазки. В 3D и жёлтенком цвете сделал ТЦ Галант на КП. Добавил кучу магазинчиков на КП возле ТЦ Плаза.&lt;/p&gt;
  317. </description>
  318.      <dc:creator>Мускатиньев Николай</dc:creator>
  319.      <pubDate>Thu, 20 Feb 2020 09:36:49 +0000</pubDate>
  320.      <comments>https://www.openstreetmap.org/user/%D0%9C%D1%83%D1%81%D0%BA%D0%B0%D1%82%D0%B8%D0%BD%D1%8C%D0%B5%D0%B2%20%D0%9D%D0%B8%D0%BA%D0%BE%D0%BB%D0%B0%D0%B9/diary/392248#comments</comments>
  321.      <geo:lat>52.966217624021</geo:lat>
  322.      <geo:long>158.680515289307</geo:long>
  323.      <georss:point>52.966217624021 158.680515289307</georss:point>
  324.    </item>
  325.    <item>
  326.      <title>Displaying accessibility information in map icons</title>
  327.      <link>https://www.openstreetmap.org/user/SomeoneElse/diary/392246</link>
  328.      <guid>https://www.openstreetmap.org/user/SomeoneElse/diary/392246</guid>
  329.      <description>&lt;p&gt;For some time I’ve been experimenting with how other information can be added to established icons.  For example, here’s how I’ve been representing various &lt;a href="https://wiki.openstreetmap.org/wiki/Tag%3Atourism%3Dinformation" rel="nofollow noopener noreferrer"&gt;tourist information&lt;/a&gt; items:&lt;/p&gt;
  330.  
  331. &lt;p&gt;&lt;img src="https://map.atownsend.org.uk/tmp/ti_example.png" alt="tourist=information icons"&gt;&lt;/p&gt;
  332.  
  333. &lt;p&gt;In those examples there are only two pieces of information - that it’s something to do with tourist information, and whether it’s a &lt;a href="https://wiki.openstreetmap.org/wiki/Tag:information%3Dboard" rel="nofollow noopener noreferrer"&gt;board&lt;/a&gt;, &lt;a href="https://wiki.openstreetmap.org/wiki/Tag:information%3Dguidepost" rel="nofollow noopener noreferrer"&gt;guidepost&lt;/a&gt;, plaque, etc.&lt;/p&gt;
  334.  
  335. &lt;p&gt;With &lt;a href="https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dpub" rel="nofollow noopener noreferrer"&gt;pubs&lt;/a&gt;, I already show several sorts of information together.  For example this one:&lt;/p&gt;
  336.  
  337. &lt;p&gt;&lt;img src="https://map.atownsend.org.uk/tmp/big_pub_yyyynyd.png" alt="pub icon filled with nice beer, underlined, and with &amp;quot;u&amp;quot; and &amp;quot;F&amp;quot;"&gt;&lt;/p&gt;
  338.  
  339. &lt;p&gt;is a pub that’s open (it’d have a cross in the middle of the beer glass if it wasn’t), serves &lt;a href="https://wiki.openstreetmap.org/wiki/Key:real_ale" rel="nofollow noopener noreferrer"&gt;real ale&lt;/a&gt; (you can tell from the maroon liquid in the glass), is a micropub (the μ at the left shows that), serves food (the F at the right) and has a &lt;a href="https://wiki.openstreetmap.org/wiki/Key:floor:material" rel="nofollow noopener noreferrer"&gt;noncarpeted floor&lt;/a&gt; that means if you’re wearing muddy boots you don’t need to take them off before going to the bar (the brown underline).&lt;/p&gt;
  340.  
  341. &lt;p&gt;A couple of other modifiers are also available - here’s a map showing a pub with a blue “roof” that offers &lt;a href="https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dpub#Additional_tags_.28suggested.29" rel="nofollow noopener noreferrer"&gt;accommodation&lt;/a&gt; as well as food:&lt;/p&gt;
  342.  
  343. &lt;p&gt;&lt;img src="https://map.atownsend.org.uk/tmp/belandthedragon.png" alt="Map snippet showing pub icon with blue roof for accommodation"&gt;&lt;/p&gt;
  344.  
  345. &lt;p&gt;I thought that it was possible to also show the values from a “&lt;a href="https://wiki.openstreetmap.org/wiki/Key%3Awheelchair#Common_values" rel="nofollow noopener noreferrer"&gt;wheelchair&lt;/a&gt;” tag, so I added that at the left-hand side of the “floor” bar:&lt;/p&gt;
  346.  
  347. &lt;p&gt;&lt;img src="https://map.atownsend.org.uk/tmp/big_pub_yyyynnyl.png" alt="pub icon with the first two pixels of the &amp;quot;floor&amp;quot; underline coloured yellow"&gt;&lt;/p&gt;
  348.  
  349. &lt;p&gt;Here yellow is used for “&lt;a href="https://wiki.openstreetmap.org/wiki/Key%3Awheelchair#wheelchair.3Dlimited" rel="nofollow noopener noreferrer"&gt;wheelchair=limited&lt;/a&gt;”, green means “&lt;a href="https://wiki.openstreetmap.org/wiki/Key%3Awheelchair#wheelchair.3Dyes" rel="nofollow noopener noreferrer"&gt;wheelchair=yes&lt;/a&gt;” and red for “&lt;a href="https://wiki.openstreetmap.org/wiki/Key%3Awheelchair#wheelchair.3Dno" rel="nofollow noopener noreferrer"&gt;wheelchair=no&lt;/a&gt;”.  If there is no wheelchair tag the original icon is used.&lt;/p&gt;
  350.  
  351. &lt;p&gt;Obviously, specialist maps such as &lt;a href="https://wheelmap.org" rel="nofollow noopener noreferrer"&gt;wheelmap&lt;/a&gt; already exist for this sort of thing, and they can provide much more information (e.g. nearest wheelchair accessible toilets), but there’s no reason why a more general map style can’t show this sort of thing too.&lt;/p&gt;
  352.  
  353. &lt;p&gt;&lt;a href="https://map.atownsend.org.uk/maps/map/map.html#zoom=19&amp;amp;lat=54.281621&amp;amp;lon=-0.872499" rel="nofollow noopener noreferrer"&gt;Here&lt;/a&gt;’s an example of what the resulting map looks like.  The extra colour is deliberately not intrusive but is designed to be visible if you’re looking for it.&lt;/p&gt;
  354. </description>
  355.      <dc:creator>SomeoneElse</dc:creator>
  356.      <pubDate>Wed, 19 Feb 2020 12:12:42 +0000</pubDate>
  357.      <comments>https://www.openstreetmap.org/user/SomeoneElse/diary/392246#comments</comments>
  358.    </item>
  359.    <item>
  360.      <title>First Entry (and I already have a backlog)</title>
  361.      <link>https://www.openstreetmap.org/user/ExpresswayDave/diary/392245</link>
  362.      <guid>https://www.openstreetmap.org/user/ExpresswayDave/diary/392245</guid>
  363.      <description>&lt;p&gt;I’ve seen others use the diary feature to good effect, so I thought I’d join in.  I actually have a lot of work backlogged from when I was in Iowa in December of 2019, to the train trip to and from the Washington, D.C. area in Dec 2019/Jan 2020 for MAGFest, as well as some work in the Champaign/Urbana area, where I’m local now.&lt;/p&gt;
  364.  
  365. &lt;p&gt;Things on my to-do list:&lt;/p&gt;
  366.  
  367. &lt;p&gt;Iowa/Illinois (outside of Champaign/Urbana):&lt;/p&gt;
  368.  
  369. &lt;ul&gt;
  370.  &lt;li&gt;Replace the intersections at the IA 58/Main St interchange in Cedar Falls, Iowa with a &lt;a href="https://en.wikipedia.org/wiki/Diamond_interchange#Dogbone" rel="nofollow noopener noreferrer"&gt;dogbone interchange&lt;/a&gt; also known as a “raindrop roundabout”&lt;/li&gt;
  371. &lt;/ul&gt;
  372.  
  373. &lt;p&gt;Prince George County, Maryland:&lt;/p&gt;
  374.  
  375. &lt;ul&gt;
  376.  &lt;li&gt;Add stops to the NH1 and NH2 bus routes. I have GPS waypoints for these&lt;/li&gt;
  377. &lt;/ul&gt;
  378.  
  379. &lt;p&gt;Champaign/Urbana area:&lt;/p&gt;
  380.  
  381. &lt;ul&gt;
  382.  &lt;li&gt;Extend bike lane on County Fair Drive to Prospect Avenue&lt;/li&gt;
  383.  &lt;li&gt;Fix Greenbelt Bikeway near Heritage Park, which right now portrays an unbroken route and paved path in an area that has neither&lt;/li&gt;
  384. &lt;/ul&gt;
  385.  
  386. &lt;p&gt;Completed:&lt;/p&gt;
  387.  
  388. &lt;p&gt;Iowa/Illinois:&lt;/p&gt;
  389.  
  390. &lt;ul&gt;
  391.  &lt;li&gt;Added maxspeed and maxspeed:source tags to IL 5/John Deere Road in Rock Island and Moline&lt;/li&gt;
  392.  &lt;li&gt;Added expressway=yes tag to U.S. 63 between Waterloo and the New Hampton freeway bypass&lt;/li&gt;
  393. &lt;/ul&gt;
  394.  
  395. &lt;p&gt;Now that I know about the expressway and motorroad tags I’m going to be tagging roads with them. I’ll only do this for roads I’ve actually surveyed, however, and I’ll upload my GPS traces when I do as evidence I’ve actually been there. That’s a policy of mine in general, especially when editing OSM for areas outside of my local area, but as I’ve encountered edit wars on these things in the past this is an area where I like to have evidence to back up my edits should they get reversed.&lt;/p&gt;
  396. </description>
  397.      <dc:creator>ExpresswayDave</dc:creator>
  398.      <pubDate>Wed, 19 Feb 2020 03:40:32 +0000</pubDate>
  399.      <comments>https://www.openstreetmap.org/user/ExpresswayDave/diary/392245#comments</comments>
  400.    </item>
  401.    <item>
  402.      <title>new year</title>
  403.      <link>https://www.openstreetmap.org/user/walley/diary/392240</link>
  404.      <guid>https://www.openstreetmap.org/user/walley/diary/392240</guid>
  405.      <description>&lt;p&gt;it’s 2020, YAY!&lt;/p&gt;
  406. </description>
  407.      <dc:creator>walley</dc:creator>
  408.      <pubDate>Tue, 18 Feb 2020 15:25:35 +0000</pubDate>
  409.      <comments>https://www.openstreetmap.org/user/walley/diary/392240#comments</comments>
  410.    </item>
  411.    <item>
  412.      <title>FUN DAYS</title>
  413.      <link>https://www.openstreetmap.org/user/nyamey/diary/392237</link>
  414.      <guid>https://www.openstreetmap.org/user/nyamey/diary/392237</guid>
  415.      <description>&lt;p&gt;GOOD DAY!&lt;/p&gt;
  416.  
  417. &lt;p&gt;I’am a student from Polytechnic University of the Philippines (San Juan) , under the coursed of BSED-English. As part of our CWTS activities, we need to attend the Mapa Time Session that really helps us not just to tract some schools but to build a social interaction. After a long hour of sitting in the classroom, finally we have a time to have fun while we are learning new things! Mapa time is indeed worth the effort! I’ve learned how to locate nor tract some school that are not able to see of some of us, and creating and labeling it as well. In attending those 5 sessions, I can say that my favorite part is locating the areas because this is the first time that Im doing this, I’am new to this and there is a high possibility that I will be one of the volunteer here.&lt;/p&gt;
  418. </description>
  419.      <dc:creator>nyamey</dc:creator>
  420.      <pubDate>Tue, 18 Feb 2020 06:50:02 +0000</pubDate>
  421.      <comments>https://www.openstreetmap.org/user/nyamey/diary/392237#comments</comments>
  422.    </item>
  423.    <item>
  424.      <title>Let's Get Mapping!</title>
  425.      <link>https://www.openstreetmap.org/user/mischelleann/diary/392236</link>
  426.      <guid>https://www.openstreetmap.org/user/mischelleann/diary/392236</guid>
  427.      <description>&lt;p&gt;Hi, I am a student of PUPSJ. Let’s talk about myself first, actually I love computers. I like sitting in front of computer screen and making myself busy. I am into typing than reading. I like computers but I am not good at it and that is so sad.
  428. So, let’s talk about my experience in MapaTime. My five sessions in #MapaTime are so fun. My time and effort are so worth it. It may be a short period of time but I learned a lot. What have I learned? I learned how to locate some areas. I also know how to straight the curved roads. I am not good at directions, seriously but this #MapaTime help me to improved it. I also learned how to fix roads, residential and all. My favourite activity here is adding school in the Philippines, it may seem so easy but it’s not. Honestly speaking, I want to volunteer in the near future, I want to teach other students how to use #MapaTime but I already know to myself that I will not going to succeed it, I am that shy.&lt;/p&gt;
  429. </description>
  430.      <dc:creator>mischelleann</dc:creator>
  431.      <pubDate>Tue, 18 Feb 2020 06:48:51 +0000</pubDate>
  432.      <comments>https://www.openstreetmap.org/user/mischelleann/diary/392236#comments</comments>
  433.    </item>
  434.  </channel>
  435. </rss>
  436.  

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:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.openstreetmap.org/diary/rss

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