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-2973595662b8a92522b315b6c69bf5ee9bec75e07d702c5932f114c44a6251ea.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>Digitalni ortofoto Gornja Rijeka 2017 na TMS i TM serveru</title>
  16.      <link>https://www.openstreetmap.org/user/hbogner/diary/407622</link>
  17.      <guid>https://www.openstreetmap.org/user/hbogner/diary/407622</guid>
  18.      <description>&lt;p dir="auto"&gt;&lt;a href="https://osm-hr.org/2025/10/20/digitalni-ortofoto-gornja-rijeka-2017-na-tms-i-tm-serveru/" rel="nofollow noopener noreferrer"&gt;Digitalni ortofoto Gornja Rijeka 2017 na TMS i TM serveru&lt;/a&gt;&lt;/p&gt;
  19.  
  20. &lt;p dir="auto"&gt;&lt;img src="https://osm-hr.org/wp-content/uploads/2025/10/gornja_rijeka-2017-dof.png" alt="Alt DOF area" loading="lazy"&gt;&lt;/p&gt;
  21.  
  22. &lt;p dir="auto"&gt;Nastavljamo sa Cadcom DOF objavama. Do sad objavljene snimke su već od prije u obradi: Igrane, Božava, Kali, Sali. Sad je na redu Gornja Rijeka snimana 2017.&lt;/p&gt;
  23.  
  24. &lt;p dir="auto"&gt;Za korištenje potrebno je ručno upisati TMS adresu u željeni editor.&lt;/p&gt;
  25.  
  26. &lt;p dir="auto"&gt;Kao i za prethodne snimke kreiran je i projekt na našem Tasking Manager servisu koji olakšava grupno uređivanje određenog područja. Uključite se i provjerite sve kuće, prometnice, staze.&lt;/p&gt;
  27.  
  28. &lt;p dir="auto"&gt;Kad koristite TM servis za odabir zadatka automatski se učitava gore navedena podloga.&lt;/p&gt;
  29.  
  30. &lt;p dir="auto"&gt;Sretno mapiranje!&lt;/p&gt;
  31. </description>
  32.      <dc:creator>hbogner</dc:creator>
  33.      <pubDate>Mon, 20 Oct 2025 15:10:02 +0000</pubDate>
  34.      <comments>https://www.openstreetmap.org/user/hbogner/diary/407622#comments</comments>
  35.    </item>
  36.    <item>
  37.      <title>classifying places of worship for risk management</title>
  38.      <link>https://www.openstreetmap.org/user/joost%20schouppe/diary/407621</link>
  39.      <guid>https://www.openstreetmap.org/user/joost%20schouppe/diary/407621</guid>
  40.      <description>&lt;p dir="auto"&gt;When processing places of worship for the National Crisis Center (Belgium), I run into the problem that it’s quite hard to filter just “significant” places of worship from OSM. We’re interested in places where it’s likely that regular services take place, or that get regular crowds (e.g. weddings &amp;amp; funerals). But it’s hard to remove all the little wayside crosses or chapels that are just not relevant because their tagging is too limited.&lt;/p&gt;
  41.  
  42. &lt;p dir="auto"&gt;&lt;img src="https://imgur.com/L0FEhdp.jpg" alt="Map with all the places of worship that could not be classified" loading="lazy"&gt;
  43. &lt;a href="https://umap.openstreetmap.fr/nl/map/place-of-unknown_1296869" rel="nofollow noopener noreferrer"&gt;uMap with all the places of worship that could not be classified&lt;/a&gt;&lt;/p&gt;
  44.  
  45. &lt;p dir="auto"&gt;To do so, we start from all places with &lt;code dir="auto"&gt;amenity=place_of_worship&lt;/code&gt;. For our search area (Belgium + areas we have projects in + a buffer), that give us about 45.000 locations.&lt;/p&gt;
  46.  
  47. &lt;p dir="auto"&gt;My initial strategy was to then exclude “obviously small places”. There’s three tags we can use for that:&lt;/p&gt;
  48.  
  49. &lt;ul dir="auto"&gt;
  50.  &lt;li&gt;&lt;code dir="auto"&gt;place_of_worship&lt;/code&gt; (and the deprecated but still used &lt;code dir="auto"&gt;place_of_worship:type&lt;/code&gt;)&lt;/li&gt;
  51.  &lt;li&gt;&lt;code dir="auto"&gt;building&lt;/code&gt; (and &lt;code dir="auto"&gt;building:part&lt;/code&gt;) which gives an idea of the function of the building&lt;/li&gt;
  52.  &lt;li&gt;&lt;code dir="auto"&gt;historic&lt;/code&gt;, which is often used to indicate wayside crosses, shrines and chapels&lt;/li&gt;
  53. &lt;/ul&gt;
  54.  
  55. &lt;p dir="auto"&gt;The most useful tag here is &lt;code dir="auto"&gt;building&lt;/code&gt;, with which almost 70% of all cases can be classified as large (church, cathedral, temple, mosque) or small (chapel, wayside_chapel) etc. &lt;code dir="auto"&gt;place_of_worship&lt;/code&gt; and &lt;code dir="auto"&gt;historic&lt;/code&gt; just add a few percent together.&lt;/p&gt;
  56.  
  57. &lt;p dir="auto"&gt;The fact that there are &lt;code dir="auto"&gt;service_times&lt;/code&gt; filled in helps us classify another 7% as large. This tag does contain a lot of free text, including several cases which amount to “none” in some way.&lt;/p&gt;
  58.  
  59. &lt;p dir="auto"&gt;I also make the assumption that a place without a &lt;code dir="auto"&gt;name&lt;/code&gt; nor &lt;code dir="auto"&gt;religion&lt;/code&gt; tag is likely not significant.&lt;/p&gt;
  60.  
  61. &lt;h3 dir="auto" id="guesstimates-for-the-rest"&gt;Guesstimates for the rest&lt;/h3&gt;
  62.  
  63. &lt;p dir="auto"&gt;I reluctantly made the assumption that this part of the world likely doesn’t have much Islamic places that are quite small, for another 1% assigned to a class. This of course makes the logic only applicable in parts of the world without a long Islamic tradition.&lt;/p&gt;
  64.  
  65. &lt;p dir="auto"&gt;And while &lt;em&gt;name is for the name only&lt;/em&gt;, apparently it is quite useful to look at the name. Searching for kapel/chapelle and moschee/moskee/mosqu/kerk/church/kirche/église in the name, allows to classify 11% of the data.&lt;/p&gt;
  66.  
  67. &lt;p dir="auto"&gt;That still leaves us with 14% of cases where we have no idea whatsoever about the type of place of worship. I guess I could include the size of the building too. But we’re only relatively certain for about a good 70% of the cases, and another 14% isn’t much more than a guess. So I’d rather we improved the quality of the tagging instead.&lt;/p&gt;
  68.  
  69. &lt;table dir="auto" class="table table-sm w-auto"&gt;
  70.  &lt;thead&gt;
  71.    &lt;tr&gt;
  72.      &lt;th&gt;&amp;nbsp;&lt;/th&gt;
  73.      &lt;th&gt;large&lt;/th&gt;
  74.      &lt;th&gt;small&lt;/th&gt;
  75.      &lt;th&gt;likely large&lt;/th&gt;
  76.      &lt;th&gt;likely small&lt;/th&gt;
  77.      &lt;th&gt;no idea&lt;/th&gt;
  78.      &lt;th&gt;total&lt;/th&gt;
  79.      &lt;th&gt;&amp;nbsp;% of total&lt;/th&gt;
  80.    &lt;/tr&gt;
  81.  &lt;/thead&gt;
  82.  &lt;tbody&gt;
  83.    &lt;tr&gt;
  84.      &lt;td&gt;place_of_worship&lt;/td&gt;
  85.      &lt;td&gt;43&lt;/td&gt;
  86.      &lt;td&gt;405&lt;/td&gt;
  87.      &lt;td&gt;0&lt;/td&gt;
  88.      &lt;td&gt;0&lt;/td&gt;
  89.      &lt;td&gt;0&lt;/td&gt;
  90.      &lt;td&gt;448&lt;/td&gt;
  91.      &lt;td&gt;1%&lt;/td&gt;
  92.    &lt;/tr&gt;
  93.    &lt;tr&gt;
  94.      &lt;td&gt;place_of_worship:type&lt;/td&gt;
  95.      &lt;td&gt;0&lt;/td&gt;
  96.      &lt;td&gt;84&lt;/td&gt;
  97.      &lt;td&gt;0&lt;/td&gt;
  98.      &lt;td&gt;0&lt;/td&gt;
  99.      &lt;td&gt;0&lt;/td&gt;
  100.      &lt;td&gt;84&lt;/td&gt;
  101.      &lt;td&gt;0%&lt;/td&gt;
  102.    &lt;/tr&gt;
  103.    &lt;tr&gt;
  104.      &lt;td&gt;building&lt;/td&gt;
  105.      &lt;td&gt;20277&lt;/td&gt;
  106.      &lt;td&gt;7913&lt;/td&gt;
  107.      &lt;td&gt;0&lt;/td&gt;
  108.      &lt;td&gt;0&lt;/td&gt;
  109.      &lt;td&gt;0&lt;/td&gt;
  110.      &lt;td&gt;28.190&lt;/td&gt;
  111.      &lt;td&gt;63%&lt;/td&gt;
  112.    &lt;/tr&gt;
  113.    &lt;tr&gt;
  114.      &lt;td&gt;building_part&lt;/td&gt;
  115.      &lt;td&gt;50&lt;/td&gt;
  116.      &lt;td&gt;37&lt;/td&gt;
  117.      &lt;td&gt;0&lt;/td&gt;
  118.      &lt;td&gt;0&lt;/td&gt;
  119.      &lt;td&gt;0&lt;/td&gt;
  120.      &lt;td&gt;87&lt;/td&gt;
  121.      &lt;td&gt;0%&lt;/td&gt;
  122.    &lt;/tr&gt;
  123.    &lt;tr&gt;
  124.      &lt;td&gt;historic&lt;/td&gt;
  125.      &lt;td&gt;4&lt;/td&gt;
  126.      &lt;td&gt;966&lt;/td&gt;
  127.      &lt;td&gt;2&lt;/td&gt;
  128.      &lt;td&gt;12&lt;/td&gt;
  129.      &lt;td&gt;1&lt;/td&gt;
  130.      &lt;td&gt;985&lt;/td&gt;
  131.      &lt;td&gt;2%&lt;/td&gt;
  132.    &lt;/tr&gt;
  133.    &lt;tr&gt;
  134.      &lt;td&gt;service_times&lt;/td&gt;
  135.      &lt;td&gt;3098&lt;/td&gt;
  136.      &lt;td&gt;0&lt;/td&gt;
  137.      &lt;td&gt;0&lt;/td&gt;
  138.      &lt;td&gt;0&lt;/td&gt;
  139.      &lt;td&gt;0&lt;/td&gt;
  140.      &lt;td&gt;3.098&lt;/td&gt;
  141.      &lt;td&gt;7%&lt;/td&gt;
  142.    &lt;/tr&gt;
  143.    &lt;tr&gt;
  144.      &lt;td&gt;name&lt;/td&gt;
  145.      &lt;td&gt;0&lt;/td&gt;
  146.      &lt;td&gt;0&lt;/td&gt;
  147.      &lt;td&gt;3088&lt;/td&gt;
  148.      &lt;td&gt;1886&lt;/td&gt;
  149.      &lt;td&gt;0&lt;/td&gt;
  150.      &lt;td&gt;4.974&lt;/td&gt;
  151.      &lt;td&gt;11%&lt;/td&gt;
  152.    &lt;/tr&gt;
  153.    &lt;tr&gt;
  154.      &lt;td&gt;lack of name and relgion&lt;/td&gt;
  155.      &lt;td&gt;0&lt;/td&gt;
  156.      &lt;td&gt;0&lt;/td&gt;
  157.      &lt;td&gt;0&lt;/td&gt;
  158.      &lt;td&gt;293&lt;/td&gt;
  159.      &lt;td&gt;0&lt;/td&gt;
  160.      &lt;td&gt;293&lt;/td&gt;
  161.      &lt;td&gt;1%&lt;/td&gt;
  162.    &lt;/tr&gt;
  163.    &lt;tr&gt;
  164.      &lt;td&gt;muslim&lt;/td&gt;
  165.      &lt;td&gt;0&lt;/td&gt;
  166.      &lt;td&gt;0&lt;/td&gt;
  167.      &lt;td&gt;570&lt;/td&gt;
  168.      &lt;td&gt;0&lt;/td&gt;
  169.      &lt;td&gt;0&lt;/td&gt;
  170.      &lt;td&gt;570&lt;/td&gt;
  171.      &lt;td&gt;1%&lt;/td&gt;
  172.    &lt;/tr&gt;
  173.    &lt;tr&gt;
  174.      &lt;td&gt;none&lt;/td&gt;
  175.      &lt;td&gt;0&lt;/td&gt;
  176.      &lt;td&gt;0&lt;/td&gt;
  177.      &lt;td&gt;0&lt;/td&gt;
  178.      &lt;td&gt;0&lt;/td&gt;
  179.      &lt;td&gt;6361&lt;/td&gt;
  180.      &lt;td&gt;6.361&lt;/td&gt;
  181.      &lt;td&gt;14%&lt;/td&gt;
  182.    &lt;/tr&gt;
  183.    &lt;tr&gt;
  184.      &lt;td&gt;total&lt;/td&gt;
  185.      &lt;td&gt;23.472&lt;/td&gt;
  186.      &lt;td&gt;9.405&lt;/td&gt;
  187.      &lt;td&gt;3.660&lt;/td&gt;
  188.      &lt;td&gt;2.191&lt;/td&gt;
  189.      &lt;td&gt;6.362&lt;/td&gt;
  190.      &lt;td&gt;45.090&lt;/td&gt;
  191.      &lt;td&gt;100%&lt;/td&gt;
  192.    &lt;/tr&gt;
  193.    &lt;tr&gt;
  194.      &lt;td&gt;% of total&amp;nbsp;&lt;/td&gt;
  195.      &lt;td&gt;52%&lt;/td&gt;
  196.      &lt;td&gt;21%&lt;/td&gt;
  197.      &lt;td&gt;8%&lt;/td&gt;
  198.      &lt;td&gt;5%&lt;/td&gt;
  199.      &lt;td&gt;14%&lt;/td&gt;
  200.      &lt;td&gt;100%&lt;/td&gt;
  201.      &lt;td&gt;&amp;nbsp;&lt;/td&gt;
  202.    &lt;/tr&gt;
  203.  &lt;/tbody&gt;
  204. &lt;/table&gt;
  205.  
  206. &lt;h3 dir="auto" id="how-to-improve"&gt;How to improve?&lt;/h3&gt;
  207.  
  208. &lt;p dir="auto"&gt;Now for Belgium, I’d like to fix this with one of &lt;a href="https://maproulette.org/browse/projects/54664" rel="nofollow noopener noreferrer"&gt;our MapRoulette challenges&lt;/a&gt;. We’re talking about 1014 uncertain places and 754 completely unknown places in Belgium. When it comes to instructions though, I’m not 100% convinced on what to recommend.&lt;/p&gt;
  209.  
  210. &lt;p dir="auto"&gt;These are some things I thought about:&lt;/p&gt;
  211.  
  212. &lt;ul dir="auto"&gt;
  213.  &lt;li&gt;for the smallest places, add &lt;code dir="auto"&gt;historic=wayside_shrine&lt;/code&gt; or &lt;code dir="auto"&gt;wayside_cross&lt;/code&gt; (or if you are so inclined, use &lt;code dir="auto"&gt;place_of_worship=*&lt;/code&gt; for this. I wouldn’t offer this as the main suggestion as it is used a 100 times less then the &lt;code dir="auto"&gt;historic&lt;/code&gt; synonyms).&lt;/li&gt;
  214.  &lt;li&gt;for small things you can actually enter, add &lt;code dir="auto"&gt;building=chapel&lt;/code&gt; (if polygon) or &lt;code dir="auto"&gt;place_of_worship=chapel&lt;/code&gt;. There’s no need to add &lt;code dir="auto"&gt;wayside_&lt;/code&gt; in front of it&lt;/li&gt;
  215.  &lt;li&gt;for less common small places (holy well, Lourdes grotto, calvary), there are some good suggestions on the place_of_worship wiki page&lt;/li&gt;
  216.  &lt;li&gt;for larger places, try adding the building tag (e.g. &lt;code dir="auto"&gt;building=church&lt;/code&gt; or &lt;code dir="auto"&gt;building=mosque&lt;/code&gt;). If the place is mapped as a point, try to map it on the building instead (but don’t force it if that doesn’t make sense). Only do this if the building was originally built for this function.&lt;/li&gt;
  217.  &lt;li&gt;If possible, add &lt;code dir="auto"&gt;service_times&lt;/code&gt;. These can be hard to find.&lt;/li&gt;
  218.  &lt;li&gt;If the building type does not help, and if there are no services (or you don’t find them or just want to save some time, add &lt;code dir="auto"&gt;place_of_worship=church&lt;/code&gt;, &lt;code dir="auto"&gt;mosque&lt;/code&gt; etc.. This goes against the current &lt;a href="https://wiki.openstreetmap.org/wiki/Key:place_of_worship" rel="nofollow noopener noreferrer"&gt;place_of_worship wiki&lt;/a&gt;), but it helps with edge cases. And I’m not entirely convinced that if there are no regular service_times, that should lead to exclusion.&lt;/li&gt;
  219.  &lt;li&gt;When you come upon &lt;code dir="auto"&gt;place_of_worship:type&lt;/code&gt;, consider converting it to &lt;code dir="auto"&gt;place_of_worship&lt;/code&gt;&lt;/li&gt;
  220.  &lt;li&gt;Review if it is a place of worship at all. It could be a community_centre instead, or have been closed by now&lt;/li&gt;
  221. &lt;/ul&gt;
  222.  
  223. &lt;p dir="auto"&gt;It was also suggested to simply remove the place_of_worship tag from the places that don’t really have a significant worshiping function, as the very description of a place of worship is &lt;em&gt;A place where religious services are conducted&lt;/em&gt;. But I think that’s a losing battle; and it opens the door for subjectivity on the decision where it is or is not “active enough” to merit the tag.&lt;/p&gt;
  224.  
  225. &lt;p dir="auto"&gt;My strategy would be to start with the Belgian places where I have no clue, and then move on to the cases where we do have an idea but aren’t certain. I can easily make an export for any area in Europe if you want to run your own challenge.&lt;/p&gt;
  226.  
  227. &lt;h3 dir="auto" id="did-that-make-sense-at-all"&gt;Did that make sense at all?&lt;/h3&gt;
  228. &lt;p dir="auto"&gt;So why did I write this? For one, as a way to just analyze this problem a bit more. But of course also to open the discussion. Which approaches did I miss? Are my guidelines acceptable? What would you add?&lt;/p&gt;
  229.  
  230. &lt;p dir="auto"&gt;Note that when making MapRoulette instructions, it’s hard to get folks to actually read them. The shorter the instructions, the more likely people actually read them. It should also be encouraged to mark tasks as “can’t complete” when folks aren’t certain, or at least mark the edit for review and leave a comment.&lt;/p&gt;
  231.  
  232. &lt;p dir="auto"&gt;If you live in our search area, have a look at the &lt;a href="https://umap.openstreetmap.fr/nl/map/place-of-unknown_1296869" rel="nofollow noopener noreferrer"&gt;uMap&lt;/a&gt; and maybe fix a few places around you. Simply click on a POI to get a link to the object. Looking forward to your feedback!&lt;/p&gt;
  233.  
  234. &lt;h3 dir="auto" id="logic-overview"&gt;Logic overview&lt;/h3&gt;
  235.  
  236. &lt;p dir="auto"&gt;If you want to have a closer look at the logical steps, check below. The choice_based_on computes the reason we classify something, the likely_size saves the result. This is just some ad hoc code to help with the analysis and a possible MapRoulette task.
  237. The records are classified step by step and only rows that have not been classified yet go through the next rule. So changing the order of rules would change the “blame” percentages, though not the end results.&lt;/p&gt;
  238.  
  239. &lt;pre dir="auto"&gt;&lt;code&gt;osm_all &amp;lt;- osm_all %&amp;gt;%
  240.  mutate(choice_based_on=case_when(
  241.            place_of_worship %in% c('wayside_chapel', 'wayside_shrine', 'lourdes_grotto', 'cross', 'shrine', 'altar', 'calvary' ,'holy_well', 'tree_chapel', 'chapel', 'tree') ~ 'place_of_worship',
  242.            place_of_worship %in% c('church', 'monastery', 'mosque', 'temple') ~ 'place_of_worship',
  243.            place_of_worship_type %in% c('wayside_chapel', 'wayside_shrine', 'lourdes_grotto', 'cross', 'shrine', 'altar', 'calvary' ,'holy_well', 'tree_chapel', 'chapel', 'tree') ~ 'place_of_worship:type',
  244.            building %in% c('wayside_chapel', 'wayside_cross', 'wayside_shrine', 'chapel', 'grotto', 'cross', 'shrine', 'bell_tower', 'cabin', 'cave', 'cemetery_chapel', 'hospital', 'ossuary') ~ 'building',
  245.            building_part %in% c('wayside_chapel', 'wayside_cross', 'wayside_shrine', 'chapel', 'grotto', 'cross', 'shrine', 'bell_tower', 'cabin', 'cave', 'cemetery_chapel', 'hospital', 'ossuary') ~ 'building_part',
  246.            !is.na(services) | !is.na(service_times) ~ 'service_times',
  247.            is.na(name) &amp;amp; is.na(religion) ~ 'lack of name and relgion',
  248.            historic %in% c('wayside_shrine', 'wayside_cross', 'wayside_chapel', 'chapel', 'ruins') ~'historic',
  249.            building %in% c('church', 'basilica', 'cathedral', 'chruch_of_christ', 'cloister', 'convent', 'funeral_hall', 'kingdom_hall', 'monastery', 'mosque', 'nunnery', 'synagogue', 'temple') ~ 'building',
  250.            building_part %in% c('church', 'basilica', 'cathedral', 'chruch_of_christ', 'cloister', 'convent', 'funeral_hall', 'kingdom_hall', 'monastery', 'mosque', 'nunnery', 'synagogue', 'temple') ~ 'building_part',
  251.            grepl('kapel|chapelle', name, ignore.case=TRUE)==TRUE ~ 'name',
  252.            grepl('moschee|moskee|mosqu|kerk|church|kirche|eglise|église', name, ignore.case=TRUE)==TRUE ~ 'name',
  253.            religion=='muslim' ~ 'muslim',
  254.            TRUE ~'none'
  255.          ),
  256.         likely_size=case_when(
  257.            place_of_worship %in% c('wayside_chapel', 'wayside_shrine', 'lourdes_grotto', 'cross', 'shrine', 'altar', 'calvary' ,'holy_well', 'tree_chapel', 'chapel', 'tree') ~'small',
  258.            place_of_worship %in% c('church', 'monastery', 'mosque', 'temple') ~ 'large',
  259.            place_of_worship_type %in% c('wayside_chapel', 'wayside_shrine', 'lourdes_grotto', 'cross', 'shrine', 'altar', 'calvary' ,'holy_well', 'tree_chapel', 'chapel', 'tree') ~'small',
  260.            building %in% c('wayside_chapel', 'wayside_cross', 'wayside_shrine', 'chapel', 'grotto', 'cross', 'shrine', 'bell_tower', 'cabin', 'cave', 'cemetery_chapel', 'hospital', 'ossuary') ~ 'small',
  261.            building_part %in% c('wayside_chapel', 'wayside_cross', 'wayside_shrine', 'chapel', 'grotto', 'cross', 'shrine', 'bell_tower', 'cabin', 'cave', 'cemetery_chapel', 'hospital', 'ossuary') ~ 'small',
  262.            !is.na(services) | !is.na(service_times) ~ 'large',
  263.            is.na(name) &amp;amp; is.na(religion) ~ 'likely small',
  264.            historic %in% c('wayside_shrine', 'wayside_cross', 'wayside_chapel') ~ 'small',
  265.            building %in% c('church', 'basilica', 'cathedral', 'chruch_of_christ', 'cloister', 'convent', 'funeral_hall', 'kingdom_hall', 'monastery', 'mosque', 'nunnery', 'synagogue', 'temple') ~ 'large',
  266.            building_part %in% c('church', 'basilica', 'cathedral', 'chruch_of_christ', 'cloister', 'convent', 'funeral_hall', 'kingdom_hall', 'monastery', 'mosque', 'nunnery', 'synagogue', 'temple') ~ 'large',
  267.            grepl('kapel|chapelle', name, ignore.case=TRUE)==TRUE ~ 'likely small',
  268.            grepl('moschee|moskee|mosqu|kerk|church|kirche|eglise|église', name, ignore.case=TRUE)==TRUE ~ 'likely large',
  269.            religion=='muslim' ~ 'likely large',
  270.            TRUE ~'no idea'
  271.          )
  272.         )
  273. &lt;/code&gt;&lt;/pre&gt;
  274. </description>
  275.      <dc:creator>joost schouppe</dc:creator>
  276.      <pubDate>Mon, 20 Oct 2025 15:02:40 +0000</pubDate>
  277.      <comments>https://www.openstreetmap.org/user/joost%20schouppe/diary/407621#comments</comments>
  278.    </item>
  279.    <item>
  280.      <title>زمین فوتبال بیشه کلا</title>
  281.      <link>https://www.openstreetmap.org/user/ali95fa/diary/407620</link>
  282.      <guid>https://www.openstreetmap.org/user/ali95fa/diary/407620</guid>
  283.      <description>&lt;p dir="auto"&gt;زمین چمن ورزشی متعلق به جوانان بیشه کلا معروف به زمین فوتبال&lt;/p&gt;
  284. </description>
  285.      <dc:creator>ali95fa</dc:creator>
  286.      <pubDate>Mon, 20 Oct 2025 14:30:02 +0000</pubDate>
  287.      <comments>https://www.openstreetmap.org/user/ali95fa/diary/407620#comments</comments>
  288.      <geo:lat>36.656112064515774</geo:lat>
  289.      <geo:long>52.3569203610532</geo:long>
  290.      <georss:point>36.656112064515774 52.3569203610532</georss:point>
  291.    </item>
  292.    <item>
  293.      <title>Understanding "How did you contribute to OpenStreetMap?" badges.</title>
  294.      <link>https://www.openstreetmap.org/user/Fiszi37/diary/407619</link>
  295.      <guid>https://www.openstreetmap.org/user/Fiszi37/diary/407619</guid>
  296.      <description>&lt;p dir="auto"&gt;Some people are confused about &lt;a href="https://hdyc.neis-one.org" rel="nofollow noopener noreferrer"&gt;neis-one&lt;/a&gt; “Type?” badge below “Discussed changesets” section. So what It’s actualy mean?&lt;/p&gt;
  297.  
  298. &lt;p dir="auto"&gt;There are simple and easy criteria for both secions. First one how many changesets user have and secound is how many mapping days contributor have collected.&lt;/p&gt;
  299.  
  300. &lt;p dir="auto"&gt;Chngesets (left section)&lt;/p&gt;
  301.  
  302. &lt;ul dir="auto"&gt;
  303.  &lt;li&gt;Fewer than 25: Hit-and-Run&lt;/li&gt;
  304.  &lt;li&gt;25 to 99: Newbie&lt;/li&gt;
  305.  &lt;li&gt;100 to 1,499: Casual Mapper&lt;/li&gt;
  306.  &lt;li&gt;1,500 to 2,999: Great Mapper&lt;/li&gt;
  307.  &lt;li&gt;3,000 to 5,999: Heavy Mapper&lt;/li&gt;
  308.  &lt;li&gt;6,000 to 9,999: Super Mapper&lt;/li&gt;
  309.  &lt;li&gt;10,000 to 14,999: Legendary Mapper&lt;/li&gt;
  310.  &lt;li&gt;15,000 to 59,999: Fantastic Mapper&lt;/li&gt;
  311.  &lt;li&gt;60,000 to 99,999: Mega Mapper&lt;/li&gt;
  312.  &lt;li&gt;100,000 or more: Epic Mapper&lt;/li&gt;
  313. &lt;/ul&gt;
  314.  
  315. &lt;p dir="auto"&gt;Activity categories by number of active days:&lt;/p&gt;
  316.  
  317. &lt;ul dir="auto"&gt;
  318.  &lt;li&gt;Fewer than 15: Rarely Active&lt;/li&gt;
  319.  &lt;li&gt;15 to 39: Regularly Active&lt;/li&gt;
  320.  &lt;li&gt;40 to 79: Active&lt;/li&gt;
  321.  &lt;li&gt;80 to 169: Very Active&lt;/li&gt;
  322.  &lt;li&gt;170 to 269: Highly Active&lt;/li&gt;
  323.  &lt;li&gt;270 or more: Mega Active&lt;/li&gt;
  324. &lt;/ul&gt;
  325. </description>
  326.      <dc:creator>Fiszi37</dc:creator>
  327.      <pubDate>Mon, 20 Oct 2025 12:22:33 +0000</pubDate>
  328.      <comments>https://www.openstreetmap.org/user/Fiszi37/diary/407619#comments</comments>
  329.    </item>
  330.    <item>
  331.      <title>State of the Map 2025</title>
  332.      <link>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407618</link>
  333.      <guid>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407618</guid>
  334.      <description>&lt;p dir="auto"&gt;I had the incredible opportunity to represent Vriddhi Project – UNOPS Sri Lanka at the State of the Map 2025 Conference, where I presented a talk on “Mapping for Impact: Introducing Open Mapping to Civil Society in Sri Lanka.”&lt;/p&gt;
  335.  
  336. &lt;p dir="auto"&gt;During this session, I shared how Vriddhi Project empowers civil society organizations (CSOs) across Sri Lanka to harness data and geospatial technologies for better advocacy, planning, and community engagement. Civil society often faces challenges in visualizing, analyzing, and applying data effectively. Geospatial tools allow CSOs to map resources, identify gaps, track progress, and communicate evidence-based solutions, amplifying their impact at the grassroots level.&lt;/p&gt;
  337.  
  338. &lt;p dir="auto"&gt;The session resonated strongly with the audience because it highlighted real-life applications, measurable results, and the transformative power of open mapping. Participants were inspired to see how geospatial tools can turn abstract data into actionable insights that drive social change.&lt;/p&gt;
  339.  
  340. &lt;p dir="auto"&gt;Thanks to State Of The Map and Open Mapping Hub - Asia Pacific for creating opportunities&lt;/p&gt;
  341. </description>
  342.      <dc:creator>MHF Hasna</dc:creator>
  343.      <pubDate>Mon, 20 Oct 2025 10:00:05 +0000</pubDate>
  344.      <comments>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407618#comments</comments>
  345.      <geo:lat>14.654410167278538</geo:lat>
  346.      <geo:long>121.06509590201313</geo:long>
  347.      <georss:point>14.654410167278538 121.06509590201313</georss:point>
  348.    </item>
  349.    <item>
  350.      <title>State of the Map 2025</title>
  351.      <link>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407617</link>
  352.      <guid>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407617</guid>
  353.      <description>&lt;p dir="auto"&gt;I had the incredible opportunity to represent Vriddhi Project – UNOPS Sri Lanka at the State of the Map 2025, held in Manila, Philippines from October 3rd to 5th, 2025.&lt;/p&gt;
  354.  
  355. &lt;p dir="auto"&gt;As part of this global gathering of open mapping enthusiasts, I conducted a hands-on workshop titled “Getting Started with QGIS: Beginner’s Guide to Mapping with Open Source Tools.” The session introduced participants to the exciting world of open geospatial technology and its potential to create positive impact at community level.&lt;/p&gt;
  356.  
  357. &lt;p dir="auto"&gt;During the workshop, we explored:
  358. - OpenStreetMap (OSM) and the HOT Tasking Manager for collaborative and humanitarian mapping.
  359. - Open data sources such as Planet OSM, Geofabrik, BBBike, and Overpass Turbo.
  360. - How to select the right data type, perform data cleaning, and integrate datasets into QGIS effectively.
  361. - Practical mapping exercises that turned open data into meaningful stories and insights.&lt;/p&gt;
  362.  
  363. &lt;p dir="auto"&gt;The energy in the room was inspiring — participants from different backgrounds came together to learn, question, and create. The conversations around open data, inclusivity, and sustainable development reaffirmed my belief that maps are more than visuals — they’re bridges that connect people, places, and purpose.&lt;/p&gt;
  364.  
  365. &lt;p dir="auto"&gt;Heartfelt thanks to the State Of The Map 2025 organizers, Open Mapping Hub - Asia Pacific and the passionate mapping community for this enriching experience!&lt;/p&gt;
  366. </description>
  367.      <dc:creator>MHF Hasna</dc:creator>
  368.      <pubDate>Mon, 20 Oct 2025 09:55:25 +0000</pubDate>
  369.      <comments>https://www.openstreetmap.org/user/MHF%20Hasna/diary/407617#comments</comments>
  370.      <geo:lat>14.654684194295927</geo:lat>
  371.      <geo:long>121.0672588351008</geo:long>
  372.      <georss:point>14.654684194295927 121.0672588351008</georss:point>
  373.    </item>
  374.    <item>
  375.      <title>HugoC01 à passer les 10 000 changesets le 20 octobre 2025.</title>
  376.      <link>https://www.openstreetmap.org/user/HugoC01/diary/407616</link>
  377.      <guid>https://www.openstreetmap.org/user/HugoC01/diary/407616</guid>
  378.      <description>&lt;p dir="auto"&gt;J’ai passé les 10 000 changesets ce 20 octobre vers 10h, après 1 an, 4 mois et 19 jours.
  379. Cela donne en moyenne:
  380. 19.8/j
  381. 138/semaine
  382. 602/mois
  383. 7194/an&lt;/p&gt;
  384. </description>
  385.      <dc:creator>HugoC01</dc:creator>
  386.      <pubDate>Mon, 20 Oct 2025 08:20:41 +0000</pubDate>
  387.      <comments>https://www.openstreetmap.org/user/HugoC01/diary/407616#comments</comments>
  388.    </item>
  389.    <item>
  390.      <title>Oficinas 2 and 3 - Mapeando com JOSM: multipolígono, relações e muito mais!</title>
  391.      <link>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407614</link>
  392.      <guid>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407614</guid>
  393.      <description>&lt;h3 dir="auto" id="voc-est-cansado-de-mapear-apenas-vias-e-edificaes"&gt;Você está cansado de mapear apenas vias e edificações?&lt;/h3&gt;
  394.  
  395. &lt;h3 dir="auto" id="venha-conosco-e-vamos-mapear-o-mundo-juntos--"&gt;Venha conosco e vamos mapear o mundo juntos  🌎&lt;/h3&gt;
  396. &lt;p dir="auto"&gt;&amp;nbsp;
  397. &amp;nbsp;&lt;/p&gt;
  398.  
  399. &lt;p dir="auto"&gt;Tenho o prazer de informar sobre a iniciativa que coordenei e que foi promovida pela minha empresa, IVIDES DATA®. Organizamos três reuniões online em setembro e outubro de 2025, nas quais ensinei sobre mapeamento com os editores iD e JOSM, desde recursos simples, como caminhos, até recursos complexos, como multipolígonos, além de validação com JOSM, OSMCha, Osmosis e OSM Inspector.&lt;/p&gt;
  400.  
  401. &lt;p dir="auto"&gt;Com essa iniciativa, pudemos notar que as pessoas não estão muito familiarizadas com a edição de algo diferente de edificações e vias, o que faz parte de inúmeras campanhas promovidas por outras empresas privadas e ONGs internacionais que atuam no Brasil, onde moro. Para entender esse movimento no meu país, você pode ler &lt;a href="https://zenodo.org/records/16805759/preview/02_ECMCP_cap2_Souto.pdf" rel="nofollow noopener noreferrer"&gt;o capítulo&lt;/a&gt; que escrevi no meu último livro.&lt;/p&gt;
  402.  
  403. &lt;p dir="auto"&gt;Espero sinceramente que estas sessões de formação possam ajudar mais pessoas a compreender o poder por trás do projeto OpenStreetMap… Sim! É um projeto global com 21 anos e não apenas uma plataforma. Por favor, não minimizem o OSM, reduzindo-o ao seu site.&lt;/p&gt;
  404.  
  405. &lt;p dir="auto"&gt;E gostaria de enfatizar que este material não é útil apenas para atividades de ensino, mas também pode ser um recurso útil para você aplicar em seus projetos e inspirá-lo a criar mais e melhores projetos!&lt;/p&gt;
  406.  
  407. &lt;p dir="auto"&gt;&amp;nbsp;
  408. &amp;nbsp;&lt;/p&gt;
  409.  
  410. &lt;hr&gt;
  411.  
  412. &lt;h4 dir="auto" id="oficina-1---mapeando-caminhos-no-openstreetmap-com-o-editor-id"&gt;Oficina #1 - Mapeando caminhos no OpenStreetMap com o editor iD&lt;/h4&gt;
  413.  
  414. &lt;hr&gt;
  415.  
  416. &lt;p dir="auto"&gt;Nesta sessão, mostro como mapear outros tipos de vias, como cursos de água ou calçadas, com o iD, o editor mais fácil para OSM. E algumas das regras de ouro para este tipo de mapeamento e conteúdo conceitual para prepará-lo para as outras duas oficinas.&lt;/p&gt;
  417.  
  418. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/09/capa_pdf_oficina1-e1760693149306.png" alt="capa_oficina1" loading="lazy"&gt;&lt;/p&gt;
  419.  
  420. &lt;h5 dir="auto" id="oficina-1---apresentao-pdf---pt--en"&gt;Oficina #1 - Apresentação PDF - PT | EN&lt;/h5&gt;
  421.  
  422. &lt;h5 dir="auto" id="download-pdfhttpsdoiorg105281zenodo17162510"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17162510" rel="nofollow noopener noreferrer"&gt;Download PDF&lt;/a&gt;&lt;/h5&gt;
  423.  
  424. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/09/oficina1-e1760693044850.png" alt="capa_video1" loading="lazy"&gt;
  425. iD Screen | Dados do mapa © contribuidores do OpenStreetMap.&lt;/p&gt;
  426.  
  427. &lt;h5 dir="auto" id="oficina-1---vdeo-18-set-2025"&gt;Oficina #1 - Vídeo (18 set. 2025)&lt;/h5&gt;
  428.  
  429. &lt;h5 dir="auto" id="assista-aquihttpsyoutubecomlivevutzwaiutfu"&gt;&lt;a href="https://youtube.com/live/vuTZWaiutFU" rel="nofollow noopener noreferrer"&gt;Assista aqui&lt;/a&gt;&lt;/h5&gt;
  430. &lt;p dir="auto"&gt;&amp;nbsp;
  431. &amp;nbsp;&lt;/p&gt;
  432.  
  433. &lt;hr&gt;
  434.  
  435. &lt;h4 dir="auto" id="oficina-2---mapeando-reas-no-openstreetmap-com-o-editor-josm"&gt;Oficina #2 - Mapeando áreas no OpenStreetMap com o editor JOSM&lt;/h4&gt;
  436.  
  437. &lt;hr&gt;
  438.  
  439. &lt;p dir="auto"&gt;Nesta sessão, mostro como mapear áreas no OpenStreetMap usando o editor JOSM. Primeiro, mostro como configurar o JOSM para usar o controle remoto e como instalar os &lt;em&gt;plugins&lt;/em&gt; para as atividades nas sessões de treinamento #2 e #3. Além disso, mostro como usar os plugins BuildingsTools e FastDraw para melhorar o design dos recursos.&lt;/p&gt;
  440.  
  441. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  442.  
  443. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_pdf_2-e1760692774306.png" alt="capa_oficina2" loading="lazy"&gt;&lt;/p&gt;
  444.  
  445. &lt;h5 dir="auto" id="oficina-2---roteiro-em-pdf---pt"&gt;Oficina #2 - Roteiro em PDF - PT&lt;/h5&gt;
  446.  
  447. &lt;h5 dir="auto" id="download-pdfhttpsdoiorg105281zenodo17376118"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17376118" rel="nofollow noopener noreferrer"&gt;Download PDF&lt;/a&gt;&lt;/h5&gt;
  448.  
  449. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  450.  
  451. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_video_2-e1760692838734.png" alt="capa_video2" loading="lazy"&gt;
  452. Tela do JOSM | Dados do mapa © contribuidores do OpenStreetMap.&lt;/p&gt;
  453.  
  454. &lt;h5 dir="auto" id="oficina-2---video-02-out-2025"&gt;Oficina #2 - Video (02 out. 2025)&lt;/h5&gt;
  455.  
  456. &lt;h5 dir="auto" id="assista-aquihttpsyoutubecomlivex0kaau2vldy"&gt;&lt;a href="https://youtube.com/live/x0kAau2VLDY" rel="nofollow noopener noreferrer"&gt;Assista aqui&lt;/a&gt;&lt;/h5&gt;
  457. &lt;p dir="auto"&gt;&amp;nbsp;
  458. &amp;nbsp;&lt;/p&gt;
  459.  
  460. &lt;hr&gt;
  461.  
  462. &lt;h4 dir="auto" id="oficina-3---validao-com-editor-josm-e-outros-programas"&gt;Oficina #3 - Validação com editor JOSM e outros programas&lt;/h4&gt;
  463.  
  464. &lt;hr&gt;
  465.  
  466. &lt;p dir="auto"&gt;Nesta sessão, mostro como realizar validações básicas com o JOSM e alguns programas - OSMCha, Osmosis e OSM Inspector, a fim de corrigir erros frequentes, como sobreposições e polígonos abertos.&lt;/p&gt;
  467.  
  468. &lt;h5 dir="auto" id="oficina-3---roteiro-em-pdf---pt"&gt;Oficina #3 - Roteiro em PDF - PT&lt;/h5&gt;
  469.  
  470. &lt;h5 dir="auto" id="download-pdfhttpsdoiorg105281zenodo17376118-1"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17376118" rel="nofollow noopener noreferrer"&gt;Download PDF&lt;/a&gt;&lt;/h5&gt;
  471.  
  472. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  473.  
  474. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_video3-e1760692889835.png" alt="capa_video3" loading="lazy"&gt;
  475. Tela do Osmosis | Dados do mapa © contribuidores do OpenStreetMap.&lt;/p&gt;
  476.  
  477. &lt;h5 dir="auto" id="oficina-3---video-15-out-2025"&gt;Oficina #3 - Video (15 out. 2025)&lt;/h5&gt;
  478.  
  479. &lt;h5 dir="auto" id="assista-aquihttpsyoutubecomlivemyoqvqlo5mm"&gt;&lt;a href="https://youtube.com/live/MyOQVqlO5MM" rel="nofollow noopener noreferrer"&gt;Assista aqui&lt;/a&gt;&lt;/h5&gt;
  480. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  481.  
  482. &lt;hr&gt;
  483.  
  484. &lt;h5 dir="auto" id="ivides-data-e-ividesorg-so-marcas-registradas"&gt;IVIDES DATA® e IVIDES.org® são marcas registradas.&lt;/h5&gt;
  485.  
  486. &lt;h5 dir="auto" id="no-pedimos-doaes"&gt;NÃO PEDIMOS DOAÇÕES&lt;/h5&gt;
  487.  
  488. &lt;h5 dir="auto" id="para-manter-contato--ivides-at-ividesorg--httpsividesorgservicos"&gt;Para manter contato:  ivides [at] ivides.org | &lt;a href="https://ivides.org/servicos" rel="nofollow noopener noreferrer" dir="auto"&gt;https://ivides.org/servicos&lt;/a&gt;&lt;/h5&gt;
  489.  
  490. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  491.  
  492. &lt;hr&gt;
  493.  
  494. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/04/logo_ID_preta_263_236.png" alt="IVIDES_logo" loading="lazy"&gt;&lt;/p&gt;
  495. </description>
  496.      <dc:creator>Raquel Dezidério Souto</dc:creator>
  497.      <pubDate>Sun, 19 Oct 2025 18:39:44 +0000</pubDate>
  498.      <comments>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407614#comments</comments>
  499.    </item>
  500.    <item>
  501.      <title>Completed a New Year's Resolution!</title>
  502.      <link>https://www.openstreetmap.org/user/Odological/diary/407613</link>
  503.      <guid>https://www.openstreetmap.org/user/Odological/diary/407613</guid>
  504.      <description>&lt;p dir="auto"&gt;I’m writing my first OSM Diary entry in hopes that some local Thunder Bay, ON or Northwestern Ontario mapper(s) will find me here. When I look at the dashboard, I don’t see any local mappers that have edited during the past several years, and no local mappers that have made a single diary entry.
  505. If you do stumble across this post, I want you to know that you are not alone trying to improve OSM in Thunder Bay.&lt;/p&gt;
  506.  
  507. &lt;ul dir="auto"&gt;
  508.  &lt;li&gt;Please feel free to reach out to me here.&lt;/li&gt;
  509.  &lt;li&gt;You can find my blog at &lt;a href="https://corvusspatial.ca" rel="nofollow noopener noreferrer"&gt;Corvus Spatial&lt;/a&gt;.&lt;/li&gt;
  510.  &lt;li&gt;Contact me on &lt;a href="https://mapstodon.space/@corvus" rel="nofollow noopener noreferrer"&gt;Mastodon&lt;/a&gt;.&lt;/li&gt;
  511.  &lt;li&gt;I’ve also started a &lt;a href="https://codeberg.org/Gerent/OSM_network/src/branch/main/sidewalk.md" rel="nofollow noopener noreferrer"&gt;rudimentary list of tags and instructions&lt;/a&gt; I have gleaned while attempting to follow &lt;a href="https://tcat.cs.washington.edu/opensidewalks/" rel="nofollow noopener noreferrer"&gt;Open Sidewalks&lt;/a&gt; as I’m mapping sidewalks.&lt;/li&gt;
  512. &lt;/ul&gt;
  513.  
  514. &lt;p dir="auto"&gt;As the title suggests this post was precipitated by achieving one of the &lt;a href="https://corvusspatial.ca/new-years-resolution-2025/" rel="nofollow noopener noreferrer"&gt;New Year’s resolutions I made late last December, 2024&lt;/a&gt;. At the time I noted that I had only made 42 edits over the ~13 years I had been signed up with OSM and tasked myself with at least doubling this. As of today, 2025-10-19, I have made exactly 84 edits that have included over 1500 individual changes to the map this past year so far. This is small potatoes compared to people that are really active editors, but I just recently started ramping up my edits in the past several weeks as I have gained confidence mapping sidewalks and crossings following a protocol that is designed to be helpful for network modelling for diverse map users.&lt;/p&gt;
  515.  
  516. &lt;p dir="auto"&gt;I have some ideas to get more people contributing to OSM in Northwestern Ontario, including some mapathons and other social events. I hope to meet you soon, in-person or on the interwebs.&lt;/p&gt;
  517.  
  518. </description>
  519.      <dc:creator>Odological</dc:creator>
  520.      <pubDate>Sun, 19 Oct 2025 15:21:46 +0000</pubDate>
  521.      <comments>https://www.openstreetmap.org/user/Odological/diary/407613#comments</comments>
  522.      <geo:lat>48.39729713260604</geo:lat>
  523.      <geo:long>-89.26528930664062</geo:long>
  524.      <georss:point>48.39729713260604 -89.26528930664062</georss:point>
  525.    </item>
  526.    <item>
  527.      <title>Mapping Abbiategrasso (MI)</title>
  528.      <link>https://www.openstreetmap.org/user/matteobott/diary/407612</link>
  529.      <guid>https://www.openstreetmap.org/user/matteobott/diary/407612</guid>
  530.      <description>&lt;p dir="auto"&gt;Il lavoro consiste nel raccogliere, verificare e inserire dati geografici della città di Abbiategrasso, in provincia di Milano, in modo che chiunque possa consultarli e riutilizzarli liberamente.&lt;/p&gt;
  531.  
  532. &lt;p dir="auto"&gt;Attraverso gli editor OSM, JOSM e rapID, sto tracciando edifici, strade, spazi pubblici e punti di interesse (come scuole, negozi, monumenti e servizi). Per ogni elemento aggiungo informazioni utili — come nomi, numeri civici, funzioni o categorie — seguendo le linee guida del progetto e con rispetto alla precisione e all’attendibilità del dato geografico.&lt;/p&gt;
  533.  
  534. &lt;p dir="auto"&gt;Dove possibile, integro i dati da osservazioni sul campo, foto o tracce GPS, per verificare ciò che non è visibile dalle immagini satellitari.
  535. L’obiettivo è creare una mappa completa, accurata e aggiornata di Abbiategrasso, utile per cittadini, turisti, amministrazioni e sviluppatori di applicazioni basate su dati geografici liberi.&lt;/p&gt;
  536.  
  537. &lt;p dir="auto"&gt;Questo lavoro contribuisce a rendere Abbiategrasso più visibile e accessibile digitalmente, inserendola in una rete globale di conoscenza geografica condivisa e partecipativa.&lt;/p&gt;
  538. </description>
  539.      <dc:creator>matteobott</dc:creator>
  540.      <pubDate>Sun, 19 Oct 2025 11:00:13 +0000</pubDate>
  541.      <comments>https://www.openstreetmap.org/user/matteobott/diary/407612#comments</comments>
  542.      <geo:lat>45.39835957433192</geo:lat>
  543.      <geo:long>8.916800022125244</geo:long>
  544.      <georss:point>45.39835957433192 8.916800022125244</georss:point>
  545.    </item>
  546.    <item>
  547.      <title>End-to-End Mapping Solution to Empowering Disaster Preparedness Using HOT’s Technology Innovation Tools. Case Study Mount Agung Volcano in Karangasem, Bali, Indonesia.                   </title>
  548.      <link>https://www.openstreetmap.org/user/kikihadwiyanti/diary/407611</link>
  549.      <guid>https://www.openstreetmap.org/user/kikihadwiyanti/diary/407611</guid>
  550.      <description>
  551. &lt;p dir="auto"&gt;&lt;strong&gt;Bali&lt;/strong&gt;, Indonesia’s “Island of the Gods,” is celebrated for its natural beauty and spiritual heritage, yet faces a complex array of disaster risks shaped by tectonic activity, climate variability, and human development. Located on the Pacific Ring of Fire, the island is prone to earthquakes, volcanic eruptions, floods, landslides, and tsunamis. Mount Agung, a sacred stratovolcano in Karangasem, exemplifies this duality revered by Balinese Hindus and feared for its deadly eruptions, including the catastrophic event in 1963 and its reawakening in 2017.
  552. In Karangasem, disaster risk reduction has progressed through a fusion of local leadership and geospatial innovation. Participatory mapping, drone surveys, and open data platforms now support early warning systems and contingency planning. Community-based programs such as Desa Tangguh Bencana and the Centre of Excellence initiative empower residents to map hazards, design evacuation routes, and conduct preparedness drills.&lt;/p&gt;
  553.  
  554. &lt;p dir="auto"&gt;In October 2025, the &lt;strong&gt;End-to-End Mapping Solution&lt;/strong&gt; was completed in Karangasem through collaboration between &lt;strong&gt;BPBD Karangasem&lt;/strong&gt;, &lt;strong&gt;Humanitarian OpenStreetMap Team (HOT)&lt;/strong&gt;, &lt;strong&gt;AP-Hub&lt;/strong&gt;, and &lt;strong&gt;local communities&lt;/strong&gt;. This initiative deployed tools such as Drone Tasking Manager, Field Tasking Manager, and ChatMap to orchestrate a seamless workflow from aerial data capture to field validation and coordination.
  555. The mapping effort focused not only on producing accurate geospatial outputs, but also on building systems that communities can sustain and scale. Orthophotos, hazard maps, and metadata protocols were designed to be locally relevant and technically sound. Facilitation methods translated complex tools into accessible knowledge, fostering shared learning and leadership.
  556. The resulting knowledge management system connects field data to policy frameworks, ensuring that outputs inform village-level disaster preparedness strategies and early warning protocols. Mount Agung, once a symbol of destruction, now anchors a movement of community-led resilience where open data, local wisdom, and global solidarity converge to protect lives and livelihoods.&lt;/p&gt;
  557.  
  558. &lt;p dir="auto"&gt;As an Open Mapping Guru, it’s a privilege of mentoring BPBD Karangasem in deploying cutting-edge tools like &lt;strong&gt;Drone Tasking Manager&lt;/strong&gt;, &lt;strong&gt;Field Tasking Manager&lt;/strong&gt;, and &lt;strong&gt;ChatMap&lt;/strong&gt; to orchestrate a seamless workflow from aerial data capture to field validation and coordination. Joining the &lt;strong&gt;End-to-End Mapping Solution&lt;/strong&gt; in Karangasem, Bali, this role brings a fusion of technical mastery, participatory leadership, and system design thinking to strengthen disaster resilience at the community level. The responsibility is not only to deliver accurate geospatial outputs but to build systems that empower local actors to sustain and scale them. We guiding teams through drone mapping workflows, open data protocols, and folder architecture design. Every orthophoto, hazard map, and metadata tag is ensured to be not just technically sound, but locally owned and contextually relevant. The facilitation style blends empathy with precision translating complex tools into accessible knowledge, and turning mapping sessions into spaces of shared learning and leadership.&lt;/p&gt;
  559.  
  560. &lt;h2 dir="auto" id="the-tools-hots-technology-innovation-tools"&gt;🛠️ The Tools: HOT’s Technology Innovation Tools&lt;/h2&gt;
  561.  
  562. &lt;p dir="auto"&gt;Three key tools from HOT’s technology ecosystem played a central role:&lt;/p&gt;
  563.  
  564. &lt;h3 dir="auto" id="drone-tasking-manager-dtmhttpsdronetmorg"&gt;&lt;a href="https://dronetm.org/" rel="nofollow noopener noreferrer"&gt;🚁1. Drone Tasking Manager (DTM)&lt;/a&gt;&lt;/h3&gt;
  565.  
  566. &lt;p dir="auto"&gt;Drone Tasking Manager (Drone TM) is not merely a flight coordination tool—it is a modular, open-source geospatial infrastructure that operationalizes community-led aerial mapping into a scalable, interoperable disaster resilience system. Its deployment in Karangasem, Bali, where Mount Agung’s volcanic threat demands rapid and localized geospatial intelligence, exemplifies how Drone TM transforms drone mapping from a fragmented activity into a systematized, multi-actor workflow. DTM enabled coordinated drone missions across the hazard zone. Gurus and BPBD staff used it to plan flights, assign tasks, and ensure coverage of critical areas. With DTM, drone operations became structured, safe, and replicable.&lt;/p&gt;
  567.  
  568. &lt;h3 dir="auto" id="field-tasking-manager-ftmhttpsfmtmhotosmorg"&gt;&lt;a href="https://fmtm.hotosm.org/" rel="nofollow noopener noreferrer"&gt;🗺️2. Field Tasking Manager (FTM)&lt;/a&gt;&lt;/h3&gt;
  569. &lt;p dir="auto"&gt;Field Tasking Manager (Field TM) is an open-source platform developed by the Humanitarian OpenStreetMap Team (HOT) to support coordinated field mapping efforts. It allows project managers to define areas of interest, assign tasks to mappers, and monitor progress in real time. Unlike traditional mapping tools that focus on remote digitization, Field TM is designed for on-the-ground data collection, often using mobile apps like ODK, KoboToolbox, or QField.&lt;/p&gt;
  570.  
  571. &lt;p dir="auto"&gt;FTM empowered offline field data collection. During the residential mapping phase, BPBD teams will use FTM to validate drone imagery, collect household-level data, and tag infrastructure relevant to evacuation and EWS planning. It bridged the gap between aerial data and ground truth.&lt;/p&gt;
  572.  
  573. &lt;h3 dir="auto" id="chatmaphttpschatmaphotosmorg"&gt;&lt;a href="https://chatmap.hotosm.org/" rel="nofollow noopener noreferrer"&gt;💬3. ChatMap&lt;/a&gt;&lt;/h3&gt;
  574. &lt;p dir="auto"&gt;ChatMap is a lightweight, open-source platform developed by the Humanitarian OpenStreetMap Team (HOT) that enables mapping through chat apps. It extracts location data, text, images, and videos from everyday conversations and converts them into structured geospatial information. This allows communities especially those with low digital literacy or limited internet access to contribute to mapping efforts using tools they already know: WhatsApp.
  575. Unlike traditional mapping platforms that require specialized software or training, ChatMap works by simply sending a message with a location pin, photo, or description in WhatsApp group. The system parses that input and places it on a map, creating a live, community-sourced spatial dataset.&lt;/p&gt;
  576.  
  577. &lt;p dir="auto"&gt;ChatMap provided real-time situational awareness. As teams moved between training rooms, field sites, and drone launch zones, ChatMap kept everyone connected. It allowed instant updates, direct report from the disaster affected, coordination, and decision-making especially vital in dynamic disaster contexts.&lt;/p&gt;
  578.  
  579. &lt;p dir="auto"&gt;&lt;em&gt;🌏The integration of these technologies not only strengthens disaster risk reduction efforts but also opens up opportunities for broader applications across sectors. These open mapping tools can be utilized for participatory spatial planning, environmental monitoring, public infrastructure mapping, climate adaptation, socio-economic profiling, indigenous land documentation, and transparent community-based project tracking. By combining community engagement with open-source innovation, this system empowers local actors to manage spatial data and make informed decisions. It demonstrates that mapping is not just a technical process, but a foundation for inclusive governance, spatial justice, and resilience rooted in community strength.&lt;/em&gt;&lt;/p&gt;
  580.  
  581. &lt;h2 dir="auto" id="dive-into-the-learning-journeyhttpslearninghotosmorgcoursee2e-id"&gt;&lt;a href="https://learning.hotosm.org/course/e2e-id" rel="nofollow noopener noreferrer"&gt;&lt;strong&gt;&lt;em&gt;Dive into the learning journey💡&lt;/em&gt;&lt;/strong&gt;&lt;/a&gt;&lt;/h2&gt;
  582.  
  583. </description>
  584.      <dc:creator>kikihadwiyanti</dc:creator>
  585.      <pubDate>Sun, 19 Oct 2025 09:24:30 +0000</pubDate>
  586.      <comments>https://www.openstreetmap.org/user/kikihadwiyanti/diary/407611#comments</comments>
  587.    </item>
  588.    <item>
  589.      <title>فروشگاه سور</title>
  590.      <link>https://www.openstreetmap.org/user/%D8%B3%D9%88%D8%B1/diary/407610</link>
  591.      <guid>https://www.openstreetmap.org/user/%D8%B3%D9%88%D8%B1/diary/407610</guid>
  592.      <description>&lt;p dir="auto"&gt;اجیل و خشکبار و‌عطاری سور&lt;/p&gt;
  593. </description>
  594.      <dc:creator>سور</dc:creator>
  595.      <pubDate>Sun, 19 Oct 2025 09:22:52 +0000</pubDate>
  596.      <comments>https://www.openstreetmap.org/user/%D8%B3%D9%88%D8%B1/diary/407610#comments</comments>
  597.    </item>
  598.    <item>
  599.      <title>Fahrten am 18.10.2025</title>
  600.      <link>https://www.openstreetmap.org/user/WARUMICHRADFAHRE/diary/407609</link>
  601.      <guid>https://www.openstreetmap.org/user/WARUMICHRADFAHRE/diary/407609</guid>
  602.      <description>&lt;ul dir="auto"&gt;
  603.  &lt;li&gt;2025 10 18 3,20 #lunetta DE NW FP&lt;/li&gt;
  604.  &lt;li&gt;2025 10 18 46,70 #Gspot DE NW THNRW Speedway Tollhausen WFH&lt;/li&gt;
  605.  &lt;li&gt;2025 10 18 7,50 #Gspot DE NW Horrem Kerpen Capitol Grad°Jetzt&lt;/li&gt;
  606.  &lt;li&gt;2025 10 18 6,90 #Gspot DE NW Kerpen Capitol Horrem&lt;/li&gt;
  607. &lt;/ul&gt;
  608.  
  609. &lt;p dir="auto"&gt;Die drei letzten Fahrten sind auch in meinen GPS Tracks hier zu finden.&lt;/p&gt;
  610.  
  611. &lt;p dir="auto"&gt;&lt;a href="https://www.openstreetmap.org/user/WARUMICHRADFAHRE/traces" rel="nofollow noopener noreferrer" dir="auto"&gt;osm.org/user/WARUMICHRADFAHRE/traces&lt;/a&gt;&lt;/p&gt;
  612. </description>
  613.      <dc:creator>WARUMICHRADFAHRE</dc:creator>
  614.      <pubDate>Sat, 18 Oct 2025 20:49:51 +0000</pubDate>
  615.      <comments>https://www.openstreetmap.org/user/WARUMICHRADFAHRE/diary/407609#comments</comments>
  616.    </item>
  617.    <item>
  618.      <title>Vector tiles with multilingual names in IE/GB</title>
  619.      <link>https://www.openstreetmap.org/user/SomeoneElse/diary/407608</link>
  620.      <guid>https://www.openstreetmap.org/user/SomeoneElse/diary/407608</guid>
  621.      <description>&lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20251018_202424.png" alt="A map of part or Ireland showing some townland names in Irish" loading="lazy"&gt;&lt;/p&gt;
  622.  
  623. &lt;p dir="auto"&gt;The vector tiles &lt;a href="https://map.atownsend.org.uk/vector/#8.89/51.6069/-3.66" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt; have always had names in “the local language”, so Welsh-speaking parts of Wales have Welsh names shown and English-speaking parts English names:&lt;/p&gt;
  624.  
  625. &lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20251018_201420.png" alt="A map of south Wales showing Caerfyddin and Newport" loading="lazy"&gt;&lt;/p&gt;
  626.  
  627. &lt;p dir="auto"&gt;Raster tiles can’t show multiple names in any sensible way, but with vector tiles “how the data is stored” and “how the data is displayed” are separate, so they can.  Also, because there are far fewer named things than there are unnamed things, storing extra names doesn’t even make the resulting vector tiles that much larger.&lt;/p&gt;
  628.  
  629. &lt;p dir="auto"&gt;I’ve added names for the native languages of the UK and Ireland, so “&lt;a href="https://map.atownsend.org.uk/vector/index_svwd01cy.html#5.89/54.642/-5.847" rel="nofollow noopener noreferrer"&gt;cy&lt;/a&gt;” (Welsh), “&lt;a href="https://map.atownsend.org.uk/vector/index_svwd01en.html#5.89/54.642/-5.847" rel="nofollow noopener noreferrer"&gt;en&lt;/a&gt;” (English), “&lt;a href="https://map.atownsend.org.uk/vector/index_svwd01ga.html#5.89/54.642/-5.847" rel="nofollow noopener noreferrer"&gt;ga&lt;/a&gt;” (Irish) and “&lt;a href="https://map.atownsend.org.uk/vector/index_svwd01gd.html#5.89/54.642/-5.847" rel="nofollow noopener noreferrer"&gt;gd&lt;/a&gt;” (Scots Gaelic) are now supported in addition to the &lt;a href="https://map.atownsend.org.uk/vector/index.html#5.89/53.332/-5.657" rel="nofollow noopener noreferrer"&gt;show names in local language&lt;/a&gt; ones, which are still the default.&lt;/p&gt;
  630.  
  631. &lt;p dir="auto"&gt;It’s particularly useful for Irish townlands, which are mostly well-mapped in both &lt;a href="https://map.atownsend.org.uk/vector/index_svwd01ga.html#10.23/53.0366/-7.4762" rel="nofollow noopener noreferrer"&gt;Irish&lt;/a&gt; and &lt;a href="https://map.atownsend.org.uk/vector/index_svwd01en.html#10.23/53.0366/-7.4762" rel="nofollow noopener noreferrer"&gt;English&lt;/a&gt;.  Townlands are mapped as localities in Ireland, which are shown in italics (along with things such as islands etc.); populated places are shown in non-italics.&lt;/p&gt;
  632.  
  633. &lt;p dir="auto"&gt;Where things don’t have a name in a particular language I’ve tried to fall back to a “nearby default” first, so here’s that same area in &lt;a href="https://map.atownsend.org.uk/vector/index_svwd01cy.html#10.23/53.0366/-7.4762" rel="nofollow noopener noreferrer"&gt;“Welsh”&lt;/a&gt;.  This is only a fallback - if real Welsh names exist; they’re &lt;a href="https://map.atownsend.org.uk/vector/index_svwd01cy.html#5.89/53.366/-3.992" rel="nofollow noopener noreferrer"&gt;used&lt;/a&gt;.&lt;/p&gt;
  634. </description>
  635.      <dc:creator>SomeoneElse</dc:creator>
  636.      <pubDate>Sat, 18 Oct 2025 19:38:25 +0000</pubDate>
  637.      <comments>https://www.openstreetmap.org/user/SomeoneElse/diary/407608#comments</comments>
  638.      <geo:lat>53.366</geo:lat>
  639.      <geo:long>-3.992</geo:long>
  640.      <georss:point>53.366 -3.992</georss:point>
  641.    </item>
  642.    <item>
  643.      <title>Noms de rues écorchés sur Poitiers</title>
  644.      <link>https://www.openstreetmap.org/user/JP1986/diary/407606</link>
  645.      <guid>https://www.openstreetmap.org/user/JP1986/diary/407606</guid>
  646.      <description>&lt;p dir="auto"&gt;Bonjour,&lt;/p&gt;
  647.  
  648. &lt;p dir="auto"&gt;J’écris cet article afin d’indiquer les noms de rues écorchés par la Maire de Poitiers et ses adjoints (ainsi que ses prédécesseurs) avec liens sur Google Maps en mode Satellite :&lt;/p&gt;
  649.  
  650. &lt;ul dir="auto"&gt;
  651.  &lt;li&gt;Faubourg de la Cueille-Mirebalaise (en rue du Faubourg de la Cueille Mirebalaise&lt;/li&gt;
  652. &lt;/ul&gt;
  653.  
  654. &lt;p dir="auto"&gt;&lt;a href="https://www.google.com/maps/place/1+Fbg+de+la+Cueille+Mirebalaise,+86000+Poitiers/@46.5938404,0.3349893,3a,15y,229.95h,89.6t/data=!3m7!1e1!3m5!1sRNXNsoevT7AgRq0CjrsJ3g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.40260647462223176%26panoid%3DRNXNsoevT7AgRq0CjrsJ3g%26yaw%3D229.94937793376542!7i16384!8i8192!4m6!3m5!1s0x47fdbde039c18e43:0x1c445fe16d367cbd!8m2!3d46.5938387!4d0.3348054!16s%2Fg%2F11nnkmll20?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.google.com/maps/place/1+Fbg+de+la+Cueille+Mirebalaise,+86000+Poitiers/@46.5938404,0.3349893,3a,15y,229.95h,89.6t/data=!3m7!1e1!3m5!1sRNXNsoevT7AgRq0CjrsJ3g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.40260647462223176%26panoid%3DRNXNsoevT7AgRq0CjrsJ3g%26yaw%3D229.94937793376542!7i16384!8i8192!4m6!3m5!1s0x47fdbde039c18e43:0x1c445fe16d367cbd!8m2!3d46.5938387!4d0.3348054!16s%2Fg%2F11nnkmll20?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D&lt;/a&gt;&lt;/p&gt;
  655.  
  656. &lt;p dir="auto"&gt;&lt;a href="https://www.google.com/maps/@46.5974212,0.3270056,3a,20.4y,50.75h,87.4t/data=!3m7!1e1!3m5!1s0pfWboUxBuAEiEmKGMopug!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.603578475874528%26panoid%3D0pfWboUxBuAEiEmKGMopug%26yaw%3D50.75451961715702!7i16384!8i8192?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.google.com/maps/@46.5974212,0.3270056,3a,20.4y,50.75h,87.4t/data=!3m7!1e1!3m5!1s0pfWboUxBuAEiEmKGMopug!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.603578475874528%26panoid%3D0pfWboUxBuAEiEmKGMopug%26yaw%3D50.75451961715702!7i16384!8i8192?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D&lt;/a&gt;&lt;/p&gt;
  657.  
  658. &lt;p dir="auto"&gt;&lt;a href="https://www.google.com/maps/place/1+Fbg+de+la+Cueille+Mirebalaise,+86000+Poitiers/@46.5938404,0.3349893,3a,15y,351.73h,92.42t/data=!3m7!1e1!3m5!1sRNXNsoevT7AgRq0CjrsJ3g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-2.4197143927485456%26panoid%3DRNXNsoevT7AgRq0CjrsJ3g%26yaw%3D351.73495820409886!7i16384!8i8192!4m6!3m5!1s0x47fdbde039c18e43:0x1c445fe16d367cbd!8m2!3d46.5938387!4d0.3348054!16s%2Fg%2F11nnkmll20?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.google.com/maps/place/1+Fbg+de+la+Cueille+Mirebalaise,+86000+Poitiers/@46.5938404,0.3349893,3a,15y,351.73h,92.42t/data=!3m7!1e1!3m5!1sRNXNsoevT7AgRq0CjrsJ3g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-2.4197143927485456%26panoid%3DRNXNsoevT7AgRq0CjrsJ3g%26yaw%3D351.73495820409886!7i16384!8i8192!4m6!3m5!1s0x47fdbde039c18e43:0x1c445fe16d367cbd!8m2!3d46.5938387!4d0.3348054!16s%2Fg%2F11nnkmll20?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D&lt;/a&gt;&lt;/p&gt;
  659.  
  660. &lt;ul dir="auto"&gt;
  661.  &lt;li&gt;avenue Lepeletier (écrit avenue Le Pelletier)&lt;/li&gt;
  662. &lt;/ul&gt;
  663.  
  664. &lt;p dir="auto"&gt;&lt;a href="https://www.google.com/maps/place/Hoche/@46.5875481,0.3741525,3a,24.9y,1.59h,88.97t/data=!3m7!1e1!3m5!1s590Opx7zFsgp5KZ2EnsjVg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.0255370210644799%26panoid%3D590Opx7zFsgp5KZ2EnsjVg%26yaw%3D1.5912716993181706!7i16384!8i8192!4m15!1m8!3m7!1s0x47fdbe98b673bce3:0xc90725f6e779604!2sAv.+Louis+Michel+le+Peletier,+86000+Poitiers!3b1!8m2!3d46.5876159!4d0.3750747!16s%2Fg%2F1v9lb45k!3m5!1s0x47fdbe98ce834a53:0xffcea847bff43f2!8m2!3d46.58759!4d0.37464!16s%2Fg%2F11jzhm87y1?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.google.com/maps/place/Hoche/@46.5875481,0.3741525,3a,24.9y,1.59h,88.97t/data=!3m7!1e1!3m5!1s590Opx7zFsgp5KZ2EnsjVg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.0255370210644799%26panoid%3D590Opx7zFsgp5KZ2EnsjVg%26yaw%3D1.5912716993181706!7i16384!8i8192!4m15!1m8!3m7!1s0x47fdbe98b673bce3:0xc90725f6e779604!2sAv.+Louis+Michel+le+Peletier,+86000+Poitiers!3b1!8m2!3d46.5876159!4d0.3750747!16s%2Fg%2F1v9lb45k!3m5!1s0x47fdbe98ce834a53:0xffcea847bff43f2!8m2!3d46.58759!4d0.37464!16s%2Fg%2F11jzhm87y1?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D&lt;/a&gt;&lt;/p&gt;
  665.  
  666. &lt;ul dir="auto"&gt;
  667.  &lt;li&gt;rue Édouard Grimaux (écrit rue Édouard-Grimaux sur la plaque de rue et Édouard Grimaud dans la base de donnée nationale)&lt;/li&gt;
  668. &lt;/ul&gt;
  669.  
  670. &lt;p dir="auto"&gt;&lt;a href="https://www.google.com/maps/place/Rue+%C3%89douard-Grimaux,+86000+Poitiers/@46.5826426,0.3404998,3a,75y,39.03h,99.76t/data=!3m7!1e1!3m5!1sY3w_bYLTvsfj3HI0CUOGrQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-9.761380048359214%26panoid%3DY3w_bYLTvsfj3HI0CUOGrQ%26yaw%3D39.0347429358803!7i16384!8i8192!4m6!3m5!1s0x47fdbe6d8bf330e5:0x6a0a2852f11b86f8!8m2!3d46.58294!4d0.3399426!16s%2Fg%2F1tdkll99?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.google.com/maps/place/Rue+%C3%89douard-Grimaux,+86000+Poitiers/@46.5826426,0.3404998,3a,75y,39.03h,99.76t/data=!3m7!1e1!3m5!1sY3w_bYLTvsfj3HI0CUOGrQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-9.761380048359214%26panoid%3DY3w_bYLTvsfj3HI0CUOGrQ%26yaw%3D39.0347429358803!7i16384!8i8192!4m6!3m5!1s0x47fdbe6d8bf330e5:0x6a0a2852f11b86f8!8m2!3d46.58294!4d0.3399426!16s%2Fg%2F1tdkll99?authuser=0&amp;amp;entry=ttu&amp;amp;g_ep=EgoyMDI1MTAxNS4wIKXMDSoASAFQAw%3D%3D&lt;/a&gt;&lt;/p&gt;
  671.  
  672. &lt;p dir="auto"&gt;&lt;a href="https://adresse.data.gouv.fr/carte-base-adresse-nationale?id=86194_1370" rel="nofollow noopener noreferrer" dir="auto"&gt;https://adresse.data.gouv.fr/carte-base-adresse-nationale?id=86194_1370&lt;/a&gt;&lt;/p&gt;
  673. </description>
  674.      <dc:creator>JP1986</dc:creator>
  675.      <pubDate>Fri, 17 Oct 2025 18:58:50 +0000</pubDate>
  676.      <comments>https://www.openstreetmap.org/user/JP1986/diary/407606#comments</comments>
  677.    </item>
  678.    <item>
  679.      <title>Landuse, landuse...</title>
  680.      <link>https://www.openstreetmap.org/user/marazzer/diary/407604</link>
  681.      <guid>https://www.openstreetmap.org/user/marazzer/diary/407604</guid>
  682.      <description>&lt;p dir="auto"&gt;I have gotten into mapping farmland and rural landuse this week.&lt;/p&gt;
  683.  
  684. &lt;p dir="auto"&gt;It is very fun, and I feel productive. I can color up a village that feels boring without it.&lt;/p&gt;
  685.  
  686. &lt;p dir="auto"&gt;Here is a &lt;a href="https://osm.org/go/0L7FphQ0E-?layers=N" rel="nofollow noopener noreferrer"&gt;link for the map&lt;/a&gt;, it is the village centre of the village of Kombornia, all of the landuse around has been mostly made by me.&lt;/p&gt;
  687. </description>
  688.      <dc:creator>marazzer</dc:creator>
  689.      <pubDate>Fri, 17 Oct 2025 16:37:55 +0000</pubDate>
  690.      <comments>https://www.openstreetmap.org/user/marazzer/diary/407604#comments</comments>
  691.      <geo:lat>49.70918679889503</geo:lat>
  692.      <geo:long>21.872558891773224</geo:long>
  693.      <georss:point>49.70918679889503 21.872558891773224</georss:point>
  694.    </item>
  695.    <item>
  696.      <title>New PowerShell Module for OpenStreetMap Visualization</title>
  697.      <link>https://www.openstreetmap.org/user/yotsuda/diary/407603</link>
  698.      <guid>https://www.openstreetmap.org/user/yotsuda/diary/407603</guid>
  699.      <description>&lt;h1 dir="auto" id="introducing-powershellmap-v100"&gt;Introducing PowerShell.Map v1.0.0&lt;/h1&gt;
  700.  
  701. &lt;p dir="auto"&gt;I’m excited to share PowerShell.Map - a new module that brings interactive OpenStreetMap visualization to the PowerShell command line!&lt;/p&gt;
  702.  
  703. &lt;h2 dir="auto" id="what-it-does"&gt;What it does&lt;/h2&gt;
  704.  
  705. &lt;p dir="auto"&gt;PowerShell.Map opens interactive maps in your browser directly from PowerShell commands:&lt;/p&gt;
  706.  
  707.  &lt;pre&gt;&lt;code&gt;&lt;span&gt;# Display multiple locations&lt;/span&gt;&lt;span&gt;
  708. &lt;/span&gt;&lt;span&gt;Show-OpenStreetMap&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Paris&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;London&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Rome&lt;/span&gt;&lt;span&gt;
  709.  
  710. &lt;/span&gt;&lt;span&gt;# Show routes with turn-by-turn directions&lt;/span&gt;&lt;span&gt;
  711. &lt;/span&gt;&lt;span&gt;Show-OpenStreetMapRoute&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;-From&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Tokyo&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;-To&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Osaka&lt;/span&gt;&lt;span&gt;
  712.  
  713. &lt;/span&gt;&lt;span&gt;# Create animated tours&lt;/span&gt;&lt;span&gt;
  714. &lt;/span&gt;&lt;span&gt;Start-OpenStreetMapTour&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Tokyo&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Kyoto&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;Osaka&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;-Duration&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;2&lt;/span&gt;&lt;span&gt;
  715. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;  
  716.  
  717. &lt;h2 dir="auto" id="use-cases"&gt;Use cases&lt;/h2&gt;
  718.  
  719. &lt;p dir="auto"&gt;PowerShell.Map brings OSM’s powerful features to the command line:&lt;/p&gt;
  720.  
  721. &lt;ul dir="auto"&gt;
  722.  &lt;li&gt;&lt;strong&gt;Zero setup&lt;/strong&gt;: Interactive maps with a single command - no web development needed&lt;/li&gt;
  723.  &lt;li&gt;&lt;strong&gt;Scriptable&lt;/strong&gt;: Automate map generation from CSV, databases, or any data source&lt;/li&gt;
  724.  &lt;li&gt;&lt;strong&gt;AI-powered&lt;/strong&gt;: Let Claude Desktop create maps via natural language&lt;/li&gt;
  725. &lt;/ul&gt;
  726.  
  727. &lt;h2 dir="auto" id="technical-stack"&gt;Technical stack&lt;/h2&gt;
  728.  
  729. &lt;p dir="auto"&gt;This project is built entirely on OpenStreetMap’s ecosystem:&lt;/p&gt;
  730.  
  731. &lt;ul dir="auto"&gt;
  732.  &lt;li&gt;&lt;strong&gt;Leaflet.js&lt;/strong&gt; for interactive map display&lt;/li&gt;
  733.  &lt;li&gt;&lt;strong&gt;OSM tiles&lt;/strong&gt; for base maps&lt;/li&gt;
  734.  &lt;li&gt;&lt;strong&gt;Nominatim&lt;/strong&gt; for geocoding&lt;/li&gt;
  735.  &lt;li&gt;&lt;strong&gt;OSRM&lt;/strong&gt; for routing and directions&lt;/li&gt;
  736.  &lt;li&gt;&lt;strong&gt;Built-in HTTP server&lt;/strong&gt; for seamless browser integration&lt;/li&gt;
  737. &lt;/ul&gt;
  738.  
  739. &lt;p dir="auto"&gt;Thank you to the OSM community for providing these excellent services!&lt;/p&gt;
  740.  
  741. &lt;h3 dir="auto" id="ai-integration"&gt;AI integration&lt;/h3&gt;
  742.  
  743. &lt;p dir="auto"&gt;PowerShell.Map integrates with Claude Desktop via &lt;a href="https://github.com/yotsuda/PowerShell.MCP" rel="nofollow noopener noreferrer"&gt;PowerShell.MCP&lt;/a&gt;, enabling natural language map visualization.&lt;/p&gt;
  744.  
  745. &lt;p dir="auto"&gt;First, tell Claude to set up the module:&lt;/p&gt;
  746.  
  747. &lt;p dir="auto"&gt;&lt;strong&gt;“Show me some fun map demos using the PowerShell.Map module”&lt;/strong&gt;&lt;/p&gt;
  748.  
  749. &lt;p dir="auto"&gt;Then simply ask for what you want:&lt;/p&gt;
  750.  
  751. &lt;ul dir="auto"&gt;
  752.  &lt;li&gt;&lt;strong&gt;“Show me a tour of famous temples in Kyoto”&lt;/strong&gt;&lt;/li&gt;
  753.  &lt;li&gt;&lt;strong&gt;“Create a route from Tokyo Tower to Senso-ji Temple”&lt;/strong&gt;&lt;/li&gt;
  754.  &lt;li&gt;&lt;strong&gt;“Show me a walking tour of cafes in Paris”&lt;/strong&gt;&lt;/li&gt;
  755.  &lt;li&gt;&lt;strong&gt;“Plan a hot spring tour across Japan with routes between locations”&lt;/strong&gt;&lt;/li&gt;
  756. &lt;/ul&gt;
  757.  
  758. &lt;p dir="auto"&gt;Claude translates these requests into PowerShell.Map commands and displays the interactive map instantly.&lt;/p&gt;
  759.  
  760. &lt;p dir="auto"&gt;&lt;strong&gt;Links:&lt;/strong&gt;&lt;/p&gt;
  761.  
  762. &lt;ul dir="auto"&gt;
  763.  &lt;li&gt;&lt;strong&gt;PowerShell Gallery&lt;/strong&gt;: &lt;a href="https://www.powershellgallery.com/packages/PowerShell.MCP" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.powershellgallery.com/packages/PowerShell.MCP&lt;/a&gt;&lt;/li&gt;
  764.  &lt;li&gt;&lt;strong&gt;GitHub&lt;/strong&gt;: &lt;a href="https://github.com/yotsuda/PowerShell.MCP" rel="nofollow noopener noreferrer" dir="auto"&gt;https://github.com/yotsuda/PowerShell.MCP&lt;/a&gt;&lt;/li&gt;
  765. &lt;/ul&gt;
  766.  
  767. &lt;h3 dir="auto" id="installation"&gt;Installation&lt;/h3&gt;
  768.  
  769. &lt;p dir="auto"&gt;Requires PowerShell 7.2+: &lt;a href="https://learn.microsoft.com/powershell/scripting/install/installing-powershell" rel="nofollow noopener noreferrer" dir="auto"&gt;https://learn.microsoft.com/powershell/scripting/install/installing-powershell&lt;/a&gt;&lt;/p&gt;
  770.  
  771.  &lt;pre&gt;&lt;code&gt;&lt;span&gt;Install-Module&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;PowerShell.Map&lt;/span&gt;&lt;span&gt;
  772. &lt;/span&gt;&lt;span&gt;Import-Module&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;PowerShell.Map&lt;/span&gt;&lt;span&gt;
  773. &lt;/span&gt;&lt;span&gt;Show-OpenStreetMap&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;"Your City"&lt;/span&gt;&lt;span&gt;
  774. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;  
  775.  
  776. &lt;h2 dir="auto" id="links"&gt;Links&lt;/h2&gt;
  777.  
  778. &lt;ul dir="auto"&gt;
  779.  &lt;li&gt;&lt;strong&gt;GitHub&lt;/strong&gt;: &lt;a href="https://github.com/yotsuda/PowerShell.Map" rel="nofollow noopener noreferrer" dir="auto"&gt;https://github.com/yotsuda/PowerShell.Map&lt;/a&gt;&lt;/li&gt;
  780.  &lt;li&gt;&lt;strong&gt;PowerShell Gallery&lt;/strong&gt;: &lt;a href="https://www.powershellgallery.com/packages/PowerShell.Map" rel="nofollow noopener noreferrer" dir="auto"&gt;https://www.powershellgallery.com/packages/PowerShell.Map&lt;/a&gt;&lt;/li&gt;
  781.  &lt;li&gt;&lt;strong&gt;License&lt;/strong&gt;: MIT&lt;/li&gt;
  782. &lt;/ul&gt;
  783.  
  784. &lt;h2 dir="auto" id="attribution"&gt;Attribution&lt;/h2&gt;
  785.  
  786. &lt;p dir="auto"&gt;Uses OpenStreetMap data © OpenStreetMap contributors&lt;br&gt;
  787. &lt;a href="https://www.openstreetmap.org/copyright" rel="nofollow noopener noreferrer" dir="auto"&gt;osm.org/copyright&lt;/a&gt;&lt;/p&gt;
  788.  
  789. &lt;p dir="auto"&gt;Feedback, issues, and contributions are welcome on GitHub!&lt;/p&gt;
  790. </description>
  791.      <dc:creator>yotsuda</dc:creator>
  792.      <pubDate>Fri, 17 Oct 2025 10:41:45 +0000</pubDate>
  793.      <comments>https://www.openstreetmap.org/user/yotsuda/diary/407603#comments</comments>
  794.    </item>
  795.    <item>
  796.      <title>Training sessions 2 and 3 - Mapping with JOSM: multipolygon, relations and much more!</title>
  797.      <link>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407602</link>
  798.      <guid>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407602</guid>
  799.      <description>&lt;h3 dir="auto" id="are-you-tired-of-mapping-only-highways-and-buildings"&gt;Are you tired of mapping only highways and buildings?&lt;/h3&gt;
  800.  
  801. &lt;h3 dir="auto" id="come-with-us-and-lets-map-the-world-together--"&gt;Come with us and let’s map the World together  🌎&lt;/h3&gt;
  802. &lt;p dir="auto"&gt;&amp;nbsp;
  803. &amp;nbsp;&lt;/p&gt;
  804.  
  805. &lt;p dir="auto"&gt;I am very happy to tell you about the initiative that was coordinated by me and promoted by my company, IVIDES DATA™. We organized three online meetings in September and October 2025, where I taught about mapping with the iD and the JOSM editors, from simple features, such as paths, to complex features, such as multipolygons, and also validation with JOSM, OSMCha, Osmosis and OSM Inspector.&lt;/p&gt;
  806.  
  807. &lt;p dir="auto"&gt;With this initiative, we could note that people are not very familiar with editing something different of buildings and highways, which is part of countless campaigns promoted by other private companies and international NGOs operating in Brazil, where I live. To understand this movement in my country, you can read &lt;a href="https://zenodo.org/records/16805759/preview/02_ECMCP_cap2_Souto.pdf" rel="nofollow noopener noreferrer"&gt;the chapter&lt;/a&gt; that I wrote in my last book.&lt;/p&gt;
  808.  
  809. &lt;p dir="auto"&gt;I really hope these training sessions can help more people to understand the power behind the OpenStreetMap project… Yes! It is a 21 years old global project and not only a &lt;em&gt;platform&lt;/em&gt;. Please, do not miniaturize the OSM, reducing it to its website.&lt;/p&gt;
  810.  
  811. &lt;p dir="auto"&gt;And I would like to emphasize that this material is not only useful for teaching activities, but can be also a useful resource for you to apply to your projects and to inspire you to create more and better projects!&lt;/p&gt;
  812.  
  813. &lt;p dir="auto"&gt;&amp;nbsp;
  814. &amp;nbsp;&lt;/p&gt;
  815.  
  816. &lt;hr&gt;
  817.  
  818. &lt;h4 dir="auto" id="training-session-1---mapping-ways-in-openstreetmap-with-id-editor"&gt;Training Session #1 - Mapping ways in OpenStreetMap with iD editor&lt;/h4&gt;
  819.  
  820. &lt;hr&gt;
  821.  
  822. &lt;p dir="auto"&gt;At this session, I show how to map other type of ways, like waterways or sidewalks, with iD, the easiest editor for OSM. And some of the golden mapping rules for this kind of mapping and conceptual content to prepare you to the other two lessons.&lt;/p&gt;
  823.  
  824. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/09/capa_pdf_oficina1-e1760693149306.png" alt="capa_oficina1" loading="lazy"&gt;&lt;/p&gt;
  825.  
  826. &lt;h5 dir="auto" id="training-session-1---lesson---pt--en"&gt;Training session #1 - Lesson - PT | EN&lt;/h5&gt;
  827.  
  828. &lt;h5 dir="auto" id="pdf-downloadhttpsdoiorg105281zenodo17162510"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17162510" rel="nofollow noopener noreferrer"&gt;PDF Download&lt;/a&gt;&lt;/h5&gt;
  829.  
  830. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/09/oficina1-e1760693044850.png" alt="capa_video1" loading="lazy"&gt;
  831. iD Screen | Map data © OpenStreetMap contributors.&lt;/p&gt;
  832.  
  833. &lt;h5 dir="auto" id="training-session-1---video-record-sept-18-2025"&gt;Training session #1 - Video Record (Sept. 18, 2025)&lt;/h5&gt;
  834.  
  835. &lt;h5 dir="auto" id="watch-herehttpsyoutubecomlivevutzwaiutfu"&gt;&lt;a href="https://youtube.com/live/vuTZWaiutFU" rel="nofollow noopener noreferrer"&gt;Watch here&lt;/a&gt;&lt;/h5&gt;
  836. &lt;p dir="auto"&gt;&amp;nbsp;
  837. &amp;nbsp;&lt;/p&gt;
  838.  
  839. &lt;hr&gt;
  840.  
  841. &lt;h4 dir="auto" id="training-session-2---mapping-areas-in-openstreetmap-with-josm-editor"&gt;Training Session #2 - Mapping areas in OpenStreetMap with JOSM editor&lt;/h4&gt;
  842.  
  843. &lt;hr&gt;
  844.  
  845. &lt;p dir="auto"&gt;At this session, I show how to map areas in OpenStreetMap using the JOSM editor. First, I show how to configure JOSM to use the remote control and how to install the plugins for the activities in training sessions #2 and #3. In addition, I show how to use the BuildingsTools and FastDraw plugins in order to improve the design of features.&lt;/p&gt;
  846.  
  847. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  848.  
  849. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_pdf_2-e1760692774306.png" alt="capa_oficina2" loading="lazy"&gt;&lt;/p&gt;
  850.  
  851. &lt;h5 dir="auto" id="training-session-2---lesson---en"&gt;Training session #2 - Lesson - EN&lt;/h5&gt;
  852.  
  853. &lt;h5 dir="auto" id="pdf-downloadhttpsdoiorg105281zenodo17376081"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17376081" rel="nofollow noopener noreferrer"&gt;PDF Download&lt;/a&gt;&lt;/h5&gt;
  854.  
  855. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  856.  
  857. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_video_2-e1760692838734.png" alt="capa_video2" loading="lazy"&gt;
  858. JOSM Screen | Map data © OpenStreetMap contributors.&lt;/p&gt;
  859.  
  860. &lt;h5 dir="auto" id="training-session-2---video-record-oct-02-2025"&gt;Training session #2 - Video Record (Oct. 02, 2025)&lt;/h5&gt;
  861.  
  862. &lt;h5 dir="auto" id="watch-herehttpsyoutubecomlivex0kaau2vldy"&gt;&lt;a href="https://youtube.com/live/x0kAau2VLDY" rel="nofollow noopener noreferrer"&gt;Watch here&lt;/a&gt;&lt;/h5&gt;
  863. &lt;p dir="auto"&gt;&amp;nbsp;
  864. &amp;nbsp;&lt;/p&gt;
  865.  
  866. &lt;hr&gt;
  867.  
  868. &lt;h4 dir="auto" id="training-session-3---validation-with-josm-editor-and-other-programs"&gt;Training Session #3 - Validation with JOSM editor and other programs&lt;/h4&gt;
  869.  
  870. &lt;hr&gt;
  871.  
  872. &lt;p dir="auto"&gt;At this session, I show how to perform basic validation with JOSM and some programs - OSMCha, Osmosis and OSM Inspector, in order to correct frequent errors, like overlaps and open polygons.&lt;/p&gt;
  873.  
  874. &lt;h5 dir="auto" id="training-session-3---lesson---en"&gt;Training session #3 - Lesson - EN&lt;/h5&gt;
  875.  
  876. &lt;h5 dir="auto" id="pdf-downloadhttpsdoiorg105281zenodo17376081-1"&gt;&lt;a href="https://doi.org/10.5281/zenodo.17376081" rel="nofollow noopener noreferrer"&gt;PDF Download&lt;/a&gt;&lt;/h5&gt;
  877.  
  878. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  879.  
  880. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/10/capa_video3-e1760692889835.png" alt="capa_video3" loading="lazy"&gt;
  881. Osmosis Screen | Map data © OpenStreetMap contributors.&lt;/p&gt;
  882.  
  883. &lt;h5 dir="auto" id="training-session-3---video-record-oct-15-2025"&gt;Training session #3 - Video Record (Oct. 15, 2025)&lt;/h5&gt;
  884.  
  885. &lt;h5 dir="auto" id="watch-herehttpsyoutubecomlivemyoqvqlo5mm"&gt;&lt;a href="https://youtube.com/live/MyOQVqlO5MM" rel="nofollow noopener noreferrer"&gt;Watch here&lt;/a&gt;&lt;/h5&gt;
  886. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  887.  
  888. &lt;hr&gt;
  889.  
  890. &lt;h5 dir="auto" id="ivides-data-and-ividesorg-are-registered-trademarks"&gt;IVIDES DATA™ and IVIDES.org™ are registered trademarks.&lt;/h5&gt;
  891.  
  892. &lt;h5 dir="auto" id="we-do-not-ask-for-donations"&gt;WE DO NOT ASK FOR DONATIONS&lt;/h5&gt;
  893.  
  894. &lt;h5 dir="auto" id="to-keep-contact--ivides-at-ividesorg--httpsividesorgservicos"&gt;To keep contact:  ivides [at] ivides.org | &lt;a href="https://ivides.org/servicos" rel="nofollow noopener noreferrer" dir="auto"&gt;https://ivides.org/servicos&lt;/a&gt;&lt;/h5&gt;
  895.  
  896. &lt;p dir="auto"&gt;&amp;nbsp;&lt;/p&gt;
  897.  
  898. &lt;hr&gt;
  899.  
  900. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/04/logo_ID_preta_263_236.png" alt="IVIDES_logo" loading="lazy"&gt;&lt;/p&gt;
  901. </description>
  902.      <dc:creator>Raquel Dezidério Souto</dc:creator>
  903.      <pubDate>Fri, 17 Oct 2025 09:36:16 +0000</pubDate>
  904.      <comments>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407602#comments</comments>
  905.    </item>
  906.    <item>
  907.      <title>On the State of the Map Latin America in Medellin - 2025</title>
  908.      <link>https://www.openstreetmap.org/user/mapeadora/diary/407600</link>
  909.      <guid>https://www.openstreetmap.org/user/mapeadora/diary/407600</guid>
  910.      <description>&lt;h2 dir="auto" id="a-latam-community-with-new-energy-and-the-sotms-have-a-lot-to-do-with-it"&gt;A LATAM community with new energy, and the SotMs have a lot to do with it&lt;/h2&gt;
  911.  
  912. &lt;p dir="auto"&gt;I am very happy to observe and participate in a trend that, since 2024 in Belém (Brazil), has been moving forward: a very positive streak in the OSM Latam community —the community where I am most active— around people who have managed to mobilize more people and remain united and cohesive up to the next regional State of the Map, which has already been chosen together with our Mexican community to take place in the historic center of Mexico City, in the wonderful historical building of the &lt;a href="https://www.openstreetmap.org/?#map=19/19.436043/-99.131090" rel="nofollow noopener noreferrer"&gt;&lt;strong&gt;Antiguo Colegio de San Ildefonso&lt;/strong&gt;&lt;/a&gt;.&lt;br&gt;
  913. A very good alliance and a very good omen with the &lt;strong&gt;Instituto de Geografía of UNAM&lt;/strong&gt;, a historical debt for the OSM Mexico community.&lt;/p&gt;
  914.  
  915. &lt;p dir="auto"&gt;I have always been convinced that the regional level in Latam has the greatest potential to share its impactful experiences and to strengthen deeper dynamics, as seen at different times in its history. And we are precisely in one of those moments.&lt;br&gt;
  916. This same community is the one that gave birth to another of my dearest communities, &lt;strong&gt;Geochicas&lt;/strong&gt;. For me, it is a nursery where important things emerge.&lt;/p&gt;
  917.  
  918. &lt;p dir="auto"&gt;So it really gives me great joy to see us growing around the organization of these State of the Maps, and to see how it has happened since Belém, now in Medellín, and that it also looks promising for Mexico — a true regional collaboration, and not just a responsibility assumed by the host country.&lt;/p&gt;
  919.  
  920. &lt;p dir="auto"&gt;It’s also been some time since this community used to have frequent tensions, leading to frustration and resignations caused by exclusionary visions.  Curiously, a time of calm and novelty has arrived, and &lt;strong&gt;it feels VERY good&lt;/strong&gt;.&lt;/p&gt;
  921.  
  922. &lt;p dir="auto"&gt;For me, the &lt;strong&gt;State of the Map Latam Medellín&lt;/strong&gt; has been the reaffirmation of something that could already be felt for about a year or a little more.&lt;/p&gt;
  923.  
  924. &lt;h2 dir="auto" id="sotm-medelln"&gt;SotM Medellín&lt;/h2&gt;
  925. &lt;p dir="auto"&gt;It turned out to be a lovely event, with high participation, strong presence of young people and women, and where it felt like it didn’t need to be a matter of struggle anymore — because there was acceptance. Of course, there’s still more to do.&lt;br&gt;
  926. This allowed us to work with a deeper perspective on topics such as gender, where, representing &lt;strong&gt;Geochicas&lt;/strong&gt;, I participated in several workshops together with Adele Birkenes: a presentation of the preliminary results of the global survey on gender diversity, participation styles, and community experiences in OpenStreetMap; and a reflection on tagging —existing and those that need to be created— for facilities specific to women.&lt;/p&gt;
  927.  
  928. &lt;p dir="auto"&gt;Then, wearing my &lt;strong&gt;HOT&lt;/strong&gt; hat and also as part of the &lt;strong&gt;OpenStreetMap Mexico&lt;/strong&gt; community, I spoke about &lt;em&gt;preventive mapping&lt;/em&gt; to provide cartography for policies of climate change preparedness.&lt;/p&gt;
  929.  
  930. &lt;p dir="auto"&gt;From my &lt;strong&gt;OpenStreetMap Latam&lt;/strong&gt; hat, I invited and co-designed months in advance, together with the broader community, a session where we shared techniques, tools, and tips all together in a &lt;em&gt;Tool Swap (Cambalache de herramientas)&lt;/em&gt;: Short demonstrations of mapping/data usage tools or techniques that you like, with anyone who wants to participate. This particular session turned out really cool, organic, intentionally improvised and informal, but quite efficient and enriching. I highly recommend it for other events: you learn a lot, community is built, and it creates a nice dynamic moment.&lt;/p&gt;
  931.  
  932. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/SotM_Latam_2025_-_dia_2_-_imagen_13-768x1024.jpg" alt="Participants at SotM Latam 2025" loading="lazy"&gt;&lt;/p&gt;
  933.  
  934. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/WhatsApp-Image-2025-09-25-at-12.10.23-PM-768x432.jpeg" alt="Session at the SotM Latam Medellín event" loading="lazy"&gt;&lt;/p&gt;
  935.  
  936. &lt;h2 dir="auto" id="thanks-and-lets-go-for-more"&gt;Thanks!!! And let’s go for more&lt;/h2&gt;
  937. &lt;p dir="auto"&gt;Thanks to the great effort of the organizers and their search for funding, it was a comfortable event, where there was food and even some support at the end for those who needed it most to attend.&lt;br&gt;
  938. I am deeply grateful to them, and also to those who contributed as &lt;strong&gt;sponsors&lt;/strong&gt;, who are key to making an event possible where more people can attend —which is the main goal—, where as a result we build more community, and where meeting in person raises appreciation and the motivation to collaborate.&lt;br&gt;
  939. These &lt;em&gt;sponsors&lt;/em&gt; were &lt;strong&gt;TomTom&lt;/strong&gt; and &lt;strong&gt;Geoapify&lt;/strong&gt;.
  940. Thousands of thanks also to the collaborators who supported and borrowed the venue.&lt;/p&gt;
  941.  
  942. &lt;p dir="auto"&gt;See more info and results from the event here: &lt;a href="https://www.osmlatam.org/2025/09/30/this-is-what-the-sotm-latam-2025-achieved/" rel="nofollow noopener noreferrer"&gt;This is what the SotM Latam 2025 achieved — OSM Latam&lt;/a&gt;&lt;/p&gt;
  943.  
  944. &lt;h4 dir="auto" id="wish-us-good-luck-and-send-your-energy-and-support-for-the-next-edition-in-mexico-city-but-most-of-all-we-want-to-see-you-there"&gt;Wish us good luck and send your energy and support for the next edition in Mexico City! But most of all… &lt;strong&gt;we want to see you there!!&lt;/strong&gt;&lt;/h4&gt;
  945.  
  946. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/WhatsApp-Image-2025-09-24-at-5.14.37-PM.jpeg" alt="SotM Latam 2026" loading="lazy"&gt;&lt;/p&gt;
  947. </description>
  948.      <dc:creator>mapeadora</dc:creator>
  949.      <pubDate>Fri, 17 Oct 2025 03:38:28 +0000</pubDate>
  950.      <comments>https://www.openstreetmap.org/user/mapeadora/diary/407600#comments</comments>
  951.      <geo:lat>6.25452238875594</geo:lat>
  952.      <geo:long>-75.61343416571617</geo:long>
  953.      <georss:point>6.25452238875594 -75.61343416571617</georss:point>
  954.    </item>
  955.    <item>
  956.      <title>State of the Map América Latina en Medellin 2025</title>
  957.      <link>https://www.openstreetmap.org/user/mapeadora/diary/407599</link>
  958.      <guid>https://www.openstreetmap.org/user/mapeadora/diary/407599</guid>
  959.      <description>&lt;h2 dir="auto" id="una-comunidad-latam-con-nueva-energa-y-los-sotm-tienen-mucho-que-ver"&gt;Una comunidad LATAM con nueva energía, y los SotM tienen mucho que ver&lt;/h2&gt;
  960.  
  961. &lt;p dir="auto"&gt;Estoy muy feliz de observar y participar en una tendencia que, desde 2024 en Belén (Brasil), se ha movido: una racha muy positiva de la comunidad OSM Latam —la comunidad donde más activa soy— en torno a personas que han sabido movilizar a más personas y seguir siendo unidas y cohesionadas hasta el próximo State of the Map regional, que ya ha sido elegido con nuestra comunidad mexicana para suceder en el centro histórico de la Ciudad de México, en el maravilloso edificio histórico del &lt;strong&gt;Antiguo Colegio de San Ildefonso&lt;/strong&gt;.&lt;br&gt;
  962. Una alianza muy buena y un muy buen augurio con el &lt;strong&gt;Instituto de Geografía de la UNAM&lt;/strong&gt;, una deuda histórica para la comunidad OSM México.&lt;/p&gt;
  963.  
  964. &lt;p dir="auto"&gt;Siempre he estado convencida de que el nivel regional en Latam es el que más potencial tiene para compartir sus experiencias de impacto y impulsar dinámicas de fondo, como se ha visto en diferentes momentos de su historia. Y estamos en uno precisamente.
  965. Esta misma comunidad es la que ha dado nacimiento a otra de mis comunidades queridas, &lt;strong&gt;Geochicas&lt;/strong&gt;. Para mí, es un vivero donde surgen cosas importantes.&lt;/p&gt;
  966.  
  967. &lt;p dir="auto"&gt;Entonces, me genera realmente un gran agrado vernos crecer en torno a la organización de estos State of the Map, y ver cómo ha sucedido desde Belén, ahora en Medellín, y también pinta para México una real colaboración regional, y no una responsabilidad esencialmente asumida por el país anfitrión.&lt;/p&gt;
  968.  
  969. &lt;p dir="auto"&gt;Ha pasado también un tiempo desde que esta comunidad tenía tensiones frecuentes, desembocando en frustraciones y renuncias por visiones excluyentes.  Curiosamente ha llegado un tiempo de calma y de novedad, y &lt;strong&gt;se siente MUY bien&lt;/strong&gt;.&lt;/p&gt;
  970.  
  971. &lt;p dir="auto"&gt;Para mí, el &lt;strong&gt;State of the Map Latam Medellín&lt;/strong&gt; ha sido la reafirmación de algo que se podía sentir desde hace un año o un poquito más.&lt;/p&gt;
  972.  
  973. &lt;h2 dir="auto" id="sotm-medelln"&gt;SotM Medellín&lt;/h2&gt;
  974. &lt;p dir="auto"&gt;Resultó ser un evento lindo, con alta participación, con fuerte presencia de jóvenes y de mujeres, y donde se sintió que no debía ser un tema de lucha porque había aceptación. Claro, todavía hay por hacer.
  975. De esta manera se pudo trabajar con una perspectiva más de fondo en temáticas como, por ejemplo, la de género, donde, en nombre de &lt;strong&gt;Geochicas&lt;/strong&gt;, participé en varios talleres junto con Adele Birkenes: una presentación de los resultados preliminares de la encuesta global sobre la diversidad de género y estilos de participación y vivencias comunitarias en OpenStreetMap; y una reflexión sobre las etiquetas —la existentes y las que necesitan ser creadas— para equipamientos específicos para mujeres.&lt;/p&gt;
  976.  
  977. &lt;p dir="auto"&gt;Y luego, con mi sombrero de &lt;strong&gt;HOT&lt;/strong&gt; y también de la comunidad &lt;strong&gt;OpenStreetMap México&lt;/strong&gt;, platiqué sobre el &lt;em&gt;mapeo preventivo&lt;/em&gt; para proveer cartografía a políticas de preparación ante el cambio climático.&lt;/p&gt;
  978.  
  979. &lt;p dir="auto"&gt;Desde mi sombrero de &lt;strong&gt;OpenStreetMap Latam&lt;/strong&gt;, invité y codiseñé desde meses antes con el conjunto de la comunidad una sesión donde compartimos técnicas, herramientas y tips todos juntos en un &lt;em&gt;Cambalache de herramientas&lt;/em&gt;: breves demostraciones de herramientas o técnicas de mapeo/uso de datos que le gusten, participando quien quiera.  Esta sesión en particular resultó muy linda, orgánica, informal. con intención de improvisación, pero bastante eficiente y enriquecedora. La recomiendo para otros eventos: se aprende bastante, se genera comunidad y se permite un momento bastante dinámico.&lt;/p&gt;
  980.  
  981. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/SotM_Latam_2025_-_dia_2_-_imagen_13-768x1024.jpg" alt="Participantes del SotM Latam 2025" loading="lazy"&gt;&lt;/p&gt;
  982.  
  983. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/WhatsApp-Image-2025-09-25-at-12.10.23-PM-768x432.jpeg" alt="Sesión en el evento SotM Latam Medellín" loading="lazy"&gt;&lt;/p&gt;
  984.  
  985. &lt;h2 dir="auto" id="gracias-y-vamos-por-ms"&gt;Gracias!!! Y vamos por más&lt;/h2&gt;
  986. &lt;p dir="auto"&gt;Con el gran esfuerzo de las personas organizadoras y su búsqueda de fondeo, pudo ser un evento cómodo, donde hubo alimento y algunos apoyos al final a quienes más lo necesitaban para poder asistir.&lt;br&gt;
  987. Les soy sumamente agradecida, y también a quienes pudieron aportar sus &lt;strong&gt;sponsors&lt;/strong&gt;, los cuales son claves para lograr un evento donde más gente pueda asistir —que es lo que se busca—, donde como resultado hagamos más comunidad, y donde el conocerse en persona eleva el aprecio y el ánimo de colaborar.&lt;br&gt;
  988. Estos &lt;em&gt;sponsors&lt;/em&gt; fueron &lt;strong&gt;TomTom&lt;/strong&gt; y &lt;strong&gt;Geoapify&lt;/strong&gt;.
  989. Mil gracias también a los colaboradores que apoyaron y prestaron sus instalaciones.&lt;/p&gt;
  990.  
  991. &lt;p dir="auto"&gt;Ver más info y resultados del evento aquí: &lt;a href="https://www.osmlatam.org/2025/09/30/this-is-what-the-sotm-latam-2025-achieved/" rel="nofollow noopener noreferrer"&gt;This is what the SotM Latam 2025 achieved — OSM Latam&lt;/a&gt;&lt;/p&gt;
  992.  
  993. &lt;h4 dir="auto" id="desennos-buena-suerte-y-aporten-sus-nimos-y-soporte-para-la-prxima-edicin-en-ciudad-de-mxico-pero-sobre-todo-les-queremos-all"&gt;¡Deséennos buena suerte y aporten sus ánimos y soporte para la próxima edición en Ciudad de México! Pero sobre todo… ¡¡¡Les queremos allí!!&lt;/h4&gt;
  994.  
  995. &lt;p dir="auto"&gt;&lt;img src="https://www.osmlatam.org/wp-content/uploads/2025/09/WhatsApp-Image-2025-09-24-at-5.14.37-PM.jpeg" alt="SotM Latam 2026" loading="lazy"&gt;&lt;/p&gt;
  996. </description>
  997.      <dc:creator>mapeadora</dc:creator>
  998.      <pubDate>Fri, 17 Oct 2025 03:24:47 +0000</pubDate>
  999.      <comments>https://www.openstreetmap.org/user/mapeadora/diary/407599#comments</comments>
  1000.      <geo:lat>6.255071051453137</geo:lat>
  1001.      <geo:long>-75.62363058328629</geo:long>
  1002.      <georss:point>6.255071051453137 -75.62363058328629</georss:point>
  1003.    </item>
  1004.  </channel>
  1005. </rss>
  1006.  

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

Home · About · News · Docs · Terms

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