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>Is There Any news about Satellite Imagery ?</title>
  16.      <link>https://www.openstreetmap.org/user/farhadGuli/diary/407015</link>
  17.      <guid>https://www.openstreetmap.org/user/farhadGuli/diary/407015</guid>
  18.      <description>&lt;p dir="auto"&gt;Dear OSM Community and Team,
  19. Is there any possibility of accessing a newer imagery layer, such as Maxar? The current Bing Maps Aerial imagery appears to be significantly outdated, which makes it challenging to accurately update or edit map content.&lt;/p&gt;
  20. </description>
  21.      <dc:creator>farhadGuli</dc:creator>
  22.      <pubDate>Tue, 01 Jul 2025 09:56:25 +0000</pubDate>
  23.      <comments>https://www.openstreetmap.org/user/farhadGuli/diary/407015#comments</comments>
  24.    </item>
  25.    <item>
  26.      <title>Better OSM Diary : ideas, reflexions, improvements</title>
  27.      <link>https://www.openstreetmap.org/user/Koreller/diary/407012</link>
  28.      <guid>https://www.openstreetmap.org/user/Koreller/diary/407012</guid>
  29.      <description>&lt;p dir="auto"&gt;I see many diaries on OSM, but unfortunately the good ones are hard to find, if they can be found at all.&lt;/p&gt;
  30.  
  31. &lt;p dir="auto"&gt;In this diary, I offer some perspectives, without any technical pretensions, but just for the thinking of “what it might look like” in the vein of “&lt;a href="https://github.com/openstreetmap/openstreetmap-website/issues/3785" rel="nofollow noopener noreferrer"&gt;Reimagining the OSM.org&lt;/a&gt;” or “&lt;a href="https://github.com/deevroman/better-osm-org" rel="nofollow noopener noreferrer"&gt;Better-osm-org&lt;/a&gt;” but without the technical side.&lt;/p&gt;
  32.  
  33. &lt;p dir="auto"&gt;This diary is a proposal, a reflection. Its aim is to offer a vision of what diaries might look like in the future.&lt;/p&gt;
  34.  
  35. &lt;h2 dir="auto" id="observation"&gt;Observation&lt;/h2&gt;
  36. &lt;p dir="auto"&gt;Many diaries published by the community are interesting, not all of them are, but those that are would benefit from being discovered and promoted to a wider audience.&lt;/p&gt;
  37.  
  38. &lt;p dir="auto"&gt;Diaries are not discoverable from osm.org. When a diary is discovered, it is almost exclusively through direct sharing via an OSM communication channel (forum, Telegram, Discord, etc.).&lt;/p&gt;
  39.  
  40. &lt;p dir="auto"&gt;The aim is to offer ways to find interesting diaries more easily, to know which ones the community values or finds interesting.&lt;/p&gt;
  41.  
  42. &lt;h2 dir="auto" id="proposal"&gt;Proposal&lt;/h2&gt;
  43.  
  44. &lt;h3 dir="auto" id="categorise"&gt;Categorise&lt;/h3&gt;
  45. &lt;p dir="auto"&gt;Allowing diaries to be categorised offers several advantages:&lt;/p&gt;
  46.  
  47. &lt;ul dir="auto"&gt;
  48.  &lt;li&gt;Easier to identify the topic(s) of a diary&lt;/li&gt;
  49.  &lt;li&gt;Have a list of diaries talking of a specific topic&lt;/li&gt;
  50.  &lt;li&gt;Easier to find a specific diary&lt;/li&gt;
  51. &lt;/ul&gt;
  52.  
  53. &lt;p dir="auto"&gt;A category would group together several diaries addressing the same theme.&lt;/p&gt;
  54.  
  55. &lt;p dir="auto"&gt;This categorisation might be done in the form of keywords, for example: #tutorial #josm #streetcomplete #sotm #telecom #esri.&lt;/p&gt;
  56.  
  57. &lt;h3 dir="auto" id="add-upvotes"&gt;Add upvotes&lt;/h3&gt;
  58. &lt;p dir="auto"&gt;To enable the community to highlight the diaries that have generated the most interest and that they found most useful, it would be possible to add a like (or a downvote or an emoji reaction) to a diary.&lt;/p&gt;
  59.  
  60. &lt;p dir="auto"&gt;The same options for comments might be used to highlight the comments most appreciated by the community.&lt;/p&gt;
  61.  
  62. &lt;p dir="auto"&gt;This system would be very similar to GitLab for issues, or Reddit for content.&lt;/p&gt;
  63.  
  64. &lt;p dir="auto"&gt;&lt;img src="https://i.postimg.cc/nrvMkf6F/Git-Lab-Reddit-vote.jpg" alt="GitLab and Reddit upvotes downvotes and reactions" loading="lazy"&gt;&lt;/p&gt;
  65.  
  66. &lt;h3 dir="auto" id="diaries-search"&gt;Diaries search&lt;/h3&gt;
  67.  
  68. &lt;p dir="auto"&gt;Once the keyword categories are in place, followed by the community’s reactions to the diaries, it will be possible to explore the diaries according to different criteria: by category, by reactions, by comments, by creation date, or even by location.&lt;/p&gt;
  69.  
  70. &lt;h3 dir="auto" id="community-diaries--share-a-landing-page-for-diaries"&gt;“Community Diaries &amp;gt; Share” a landing page for diaries&lt;/h3&gt;
  71. &lt;p dir="auto"&gt;&lt;img src="https://i.postimg.cc/G37qvwbP/Community-Diaries-Share.jpg" alt="Community Diaries Share" loading="lazy"&gt;&lt;/p&gt;
  72.  
  73. &lt;h3 dir="auto" id="community-diaries--explore-a-page-for-curating-diaries"&gt;“Community Diaries &amp;gt; Explore” a page for curating diaries&lt;/h3&gt;
  74. &lt;p dir="auto"&gt;&lt;img src="https://i.postimg.cc/TYhTfDdV/Community-Diaries-Explore.jpg" alt="Community Diaries Explore" loading="lazy"&gt;&lt;/p&gt;
  75. </description>
  76.      <dc:creator>Koreller</dc:creator>
  77.      <pubDate>Tue, 01 Jul 2025 08:36:55 +0000</pubDate>
  78.      <comments>https://www.openstreetmap.org/user/Koreller/diary/407012#comments</comments>
  79.    </item>
  80.    <item>
  81.      <title>Kann Karten nicht mehr drucken!</title>
  82.      <link>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</link>
  83.      <guid>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</guid>
  84.      <description>&lt;p dir="auto"&gt;Kann Karten nicht mehr drucken!&lt;/p&gt;
  85. </description>
  86.      <dc:creator>FrankBuchholz</dc:creator>
  87.      <pubDate>Mon, 30 Jun 2025 09:44:39 +0000</pubDate>
  88.      <comments>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010#comments</comments>
  89.    </item>
  90.    <item>
  91.      <title>Editing</title>
  92.      <link>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</link>
  93.      <guid>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</guid>
  94.      <description>&lt;p dir="auto"&gt;This is my my second day into the field of OSM, i went back and edited my home grown plce, yuh my home village and and waiting to welcome any reviews because i believe it is the right think to do and am welcoming any mistakes and am hoping to add many more places on the OSM today
  95. I went ahead and edited my villages by adding the various buildings and trees that haven’t been mapped yet&lt;/p&gt;
  96. </description>
  97.      <dc:creator>Ofoyrwoth</dc:creator>
  98.      <pubDate>Mon, 30 Jun 2025 09:30:21 +0000</pubDate>
  99.      <comments>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009#comments</comments>
  100.      <geo:lat>0.055702319934704085</geo:lat>
  101.      <geo:long>32.466012239428835</geo:long>
  102.      <georss:point>0.055702319934704085 32.466012239428835</georss:point>
  103.    </item>
  104.    <item>
  105.      <title>Ventura Plaza</title>
  106.      <link>https://www.openstreetmap.org/user/Ingeniero43/diary/407006</link>
  107.      <guid>https://www.openstreetmap.org/user/Ingeniero43/diary/407006</guid>
  108.      <description>&lt;p dir="auto"&gt;Centro comercial&lt;/p&gt;
  109. </description>
  110.      <dc:creator>Ingeniero43</dc:creator>
  111.      <pubDate>Mon, 30 Jun 2025 02:42:23 +0000</pubDate>
  112.      <comments>https://www.openstreetmap.org/user/Ingeniero43/diary/407006#comments</comments>
  113.      <geo:lat>7.888399253680378</geo:lat>
  114.      <geo:long>-72.4968963861466</geo:long>
  115.      <georss:point>7.888399253680378 -72.4968963861466</georss:point>
  116.    </item>
  117.    <item>
  118.      <title>9999 edits  - a love letter to OpenSteetMap</title>
  119.      <link>https://www.openstreetmap.org/user/Kri_ttt/diary/407004</link>
  120.      <guid>https://www.openstreetmap.org/user/Kri_ttt/diary/407004</guid>
  121.      <description>&lt;p dir="auto"&gt;so i’m nearing my 10,000th edit on openstreetmap.&lt;br&gt;
  122. wild. i’ve been thinking a lot about what that actually means.&lt;br&gt;
  123. what started as a hobby - or maybe an obsession - has slowly become a record of care. &lt;br&gt;a way to see. &lt;br&gt;a way to let others see.&lt;br&gt;
  124. mapping Bangkok, piece by piece.&lt;br&gt;
  125. making it just a little more visible.&lt;br&gt;
  126. a little more precise.&lt;br&gt;
  127. a little more known - to others, &lt;br&gt;and to myself.&lt;br&gt;
  128. i’ve been thinking a lot about maps.&lt;br&gt; about what this whole thing has meant - not just as a mapper, &lt;br&gt;but as a local voice,&lt;br&gt; a small thread in a bigger web, by others. &lt;br&gt;by myself.&lt;br&gt; by the place itself. &lt;br&gt;piece by piece. &lt;br&gt;making it just a little more visible. &lt;br&gt;a little more precise. &lt;br&gt;a little more known - to others, &lt;br&gt;and to myself.&lt;br&gt;
  129. -&lt;br&gt;
  130. i’ve always loved maps.&lt;br&gt;
  131. even when i didn’t know the word for what i was feeling.&lt;br&gt;
  132. as a kid, i was drawn to them like magnets. &lt;br&gt;
  133. atlases in bookshops. globes with soft pastel oceans. &lt;br&gt;
  134. the tiny maps printed on the backs of business cards.&lt;br&gt;
  135. spatial things made me feel calm. &lt;br&gt;
  136. made me feel like the world could be held in my hands.&lt;br&gt;
  137. Vast space compress into something compact, 2 dimensional.&lt;br&gt;
  138. -&lt;br&gt;
  139. my first game was simcity 4 - my dad played it.&lt;br&gt; i didn’t really get it, &lt;br&gt;but i still did play it. &lt;br&gt;a lot, &lt;br&gt;to much, maybe.&lt;br&gt;
  140. then came minecraft. &lt;br&gt;and yeah, like every gen z kid, &lt;br&gt;i was obsessed.
  141. not the survival part.&lt;br&gt;
  142. i built cities. &lt;br&gt;creative model. &lt;br&gt;little parks and structures. &lt;br&gt;entire worlds.&lt;br&gt;i think i was looking for something i hadn’t seen yet in real life. &lt;br&gt;or maybe building the kind of place i wanted to see.&lt;br&gt;
  143. -&lt;br&gt;
  144. i still don’t know where the fascination comes from.&lt;br&gt;
  145. maybe it’s an autistic special interest.&lt;br&gt;
  146. maybe it’s just how i’ve always tried to make sense of things - through shapes, &lt;br&gt;through patterns, &lt;br&gt;through place.&lt;br&gt;
  147. -&lt;br&gt;
  148. it was the monsoon season of 2021.&lt;br&gt;
  149. midst of covid lockdown. my last year of high school.
  150. rain on the roof every day.&lt;br&gt;
  151. i opened openstreetmap one night and… that was it.&lt;br&gt;
  152. the editor was slow, clunky, frustrating - but something about it felt right.&lt;br&gt;
  153. i mapped a street.&lt;br&gt;
  154. then my school.&lt;br&gt;
  155. then a neighborhood.&lt;br&gt;
  156. then a whole district.&lt;br&gt;
  157. and then i edit.&lt;br&gt;
  158. and edit.&lt;br&gt;
  159. like nothing else matters.&lt;br&gt;
  160. i know it’s not healthy.&lt;br&gt;
  161. i know i’m not supposed to feel this alive hunched over a screen, tracing lines, renaming bus stops, aligning satellite tiles until my eyes blur.&lt;br&gt;
  162. but it satisfies something.&lt;br&gt;
  163. something deep.&lt;br&gt;
  164. something hidden in a place i don’t have a name for.&lt;br&gt;
  165. a warm ache in the center of me that only quiet edits can soothe.&lt;br&gt;
  166. so i keep going.&lt;br&gt;
  167. i expand.&lt;br&gt;
  168. translating tools like josm into thai, writing wiki articles, answering forum posts like i’ve been part of this community forever.&lt;br&gt;
  169. and maybe i have.&lt;br&gt;
  170. maybe this is my hometown, too.&lt;br&gt;
  171. not the real one, but the mapped one. &lt;br&gt;the shared one. &lt;br&gt;the infinite, editable one.&lt;br&gt;
  172. and now i’m here.&lt;br&gt;
  173. thousands of edits later.&lt;br&gt;
  174. still tracing, still tagging.&lt;br&gt;still trying to name things.&lt;br&gt;
  175. still looking for a way to understand the world a little better.&lt;br&gt;
  176. openstreetmap is familiar to me now.&lt;br&gt;
  177. like an old friend.&lt;br&gt;
  178. like a ritual.&lt;br&gt;
  179. and somewhere along the way i realized - &lt;br&gt;
  180. i believe in open-source.&lt;br&gt;
  181. i believe in open-content.&lt;br&gt;
  182. i believe geographical data is a human right.&lt;br&gt;
  183. i believe it should be free.&lt;br&gt;
  184. for everyone.&lt;br&gt;
  185. forever.&lt;br&gt;
  186. and yes - &lt;br&gt;
  187. i do love openstreetmap &amp;lt;3&lt;br&gt;
  188. -&lt;br&gt;
  189. thanks for reading. if you’re here, you probably get it.&lt;br&gt;
  190. -&amp;nbsp;&lt;br&gt;
  191. 🗺️✳️&lt;br&gt;
  192. krittin&lt;/p&gt;
  193. </description>
  194.      <dc:creator>Kri_ttt</dc:creator>
  195.      <pubDate>Sun, 29 Jun 2025 14:14:47 +0000</pubDate>
  196.      <comments>https://www.openstreetmap.org/user/Kri_ttt/diary/407004#comments</comments>
  197.    </item>
  198.    <item>
  199.      <title>مدينة أبوقير الجديدة</title>
  200.      <link>https://www.openstreetmap.org/user/%D9%90Ahmed%20Yahia/diary/407002</link>
  201.      <guid>https://www.openstreetmap.org/user/%D9%90Ahmed%20Yahia/diary/407002</guid>
  202.      <description>&lt;p dir="auto"&gt;مدينة أبوقير الجديدة&lt;/p&gt;
  203. </description>
  204.      <dc:creator>ِAhmed Yahia</dc:creator>
  205.      <pubDate>Sun, 29 Jun 2025 03:19:36 +0000</pubDate>
  206.      <comments>https://www.openstreetmap.org/user/%D9%90Ahmed%20Yahia/diary/407002#comments</comments>
  207.      <geo:lat>31.33774480715643</geo:lat>
  208.      <geo:long>30.0522766134236</geo:long>
  209.      <georss:point>31.33774480715643 30.0522766134236</georss:point>
  210.    </item>
  211.    <item>
  212.      <title>Personal Mappilary project-2025</title>
  213.      <link>https://www.openstreetmap.org/user/Bayazid%20Ahmed/diary/407001</link>
  214.      <guid>https://www.openstreetmap.org/user/Bayazid%20Ahmed/diary/407001</guid>
  215.      <description>
  216. &lt;h1 dir="auto" id="a-journey-on-foot-a-project-from-the-heart"&gt;🚶‍♂️ A journey on foot, a project from the heart.&lt;/h1&gt;
  217.  
  218. &lt;p dir="auto"&gt;This project began with my own steps — capturing street-level imagery from Daffodil International University to Eastern University, Dhaka, Savar. Using &lt;a href="https://www.mapillary.com/app/user/Bayazid_Ahmed?lat=23.875891461564834&amp;amp;lng=90.31950214803999&amp;amp;z=17&amp;amp;pKey=3506563999480053" rel="nofollow noopener noreferrer"&gt;Mapillary&lt;/a&gt;, I documented the road to support open mapping.&lt;/p&gt;
  219.  
  220. &lt;p dir="auto"&gt;These images aren’t just photos — they’re vital pieces that will directly support and enhance OpenStreetMap. Every frame contributes to a bigger, collaborative mission: building a better, more accurate map for everyone.&lt;/p&gt;
  221.  
  222. &lt;p dir="auto"&gt;&lt;img src="https://media.licdn.com/dms/image/v2/D5622AQFJ-HSn2SMBUQ/feedshare-shrink_800/B56Ze4MlfwH8Ag-/0/1751141998388?e=1753920000&amp;amp;v=beta&amp;amp;t=04p3jQuwMxGDAS8z72IMQe560H4pTeotDfAl1Vfojtg" alt="" loading="lazy"&gt;&lt;/p&gt;
  223.  
  224. &lt;p dir="auto"&gt;The journey is still ongoing, day by day. Feel free to share any powerful screenshots — let’s map the future, together. 🌍&lt;/p&gt;
  225. </description>
  226.      <dc:creator>Bayazid Ahmed</dc:creator>
  227.      <pubDate>Sat, 28 Jun 2025 20:17:19 +0000</pubDate>
  228.      <comments>https://www.openstreetmap.org/user/Bayazid%20Ahmed/diary/407001#comments</comments>
  229.      <geo:lat>23.866547745076932</geo:lat>
  230.      <geo:long>90.31389892101288</geo:long>
  231.      <georss:point>23.866547745076932 90.31389892101288</georss:point>
  232.    </item>
  233.    <item>
  234.      <title>OsmAnd Live, Free for OSM Mappers</title>
  235.      <link>https://www.openstreetmap.org/user/buy_osmand/diary/407000</link>
  236.      <guid>https://www.openstreetmap.org/user/buy_osmand/diary/407000</guid>
  237.      <description>&lt;p dir="auto"&gt;are eligible for free unlimited map downloads and live updates. To qualify: &lt;a href="https://osmand.net/docs/user/plugins/osm-editing" rel="nofollow noopener noreferrer"&gt;Enable the OpenStreetMap Editing plugin&lt;/a&gt;. Log in with your OSM username. Maintain at least 30 edits over the last two months.&lt;/p&gt;
  238.  
  239. &lt;p dir="auto"&gt;&lt;a href="https://osmand.net/docs/user/personal/maps-resources?_highlight=live#free-for-osm-mappers" rel="nofollow noopener noreferrer"&gt;?_highlight=live#free-for-osm-mappers&lt;/a&gt;&lt;/p&gt;
  240.  
  241. &lt;h1 dir="auto" id="alhamdullilahirrabilaalaameen"&gt;Alhamdullilahirrabilaalaameen!&lt;/h1&gt;
  242. </description>
  243.      <dc:creator>buy_osmand</dc:creator>
  244.      <pubDate>Sat, 28 Jun 2025 14:55:26 +0000</pubDate>
  245.      <comments>https://www.openstreetmap.org/user/buy_osmand/diary/407000#comments</comments>
  246.    </item>
  247.    <item>
  248.      <title>Request to Add Charchall Village – Akre District, Kurdistan Region</title>
  249.      <link>https://www.openstreetmap.org/user/Harkimuhamad/diary/406999</link>
  250.      <guid>https://www.openstreetmap.org/user/Harkimuhamad/diary/406999</guid>
  251.      <description>&lt;p dir="auto"&gt;Hello everyone,&lt;/p&gt;
  252.  
  253. &lt;p dir="auto"&gt;I would like to request the addition of a missing village to OpenStreetMap. The village is called Charchall, located in the Akre District, Sawsana Subdistrict, Duhok Governorate, in the Kurdistan Region of Iraq.&lt;/p&gt;
  254.  
  255. &lt;p dir="auto"&gt;Basic information:&lt;/p&gt;
  256.  
  257. &lt;p dir="auto"&gt;🏘️ Village name: Charchall&lt;/p&gt;
  258.  
  259. &lt;p dir="auto"&gt;🗺️ District: Akre&lt;/p&gt;
  260.  
  261. &lt;p dir="auto"&gt;🏞️ Subdistrict: Sawsana&lt;/p&gt;
  262.  
  263. &lt;p dir="auto"&gt;🏴 Governorate: Duhok – Kurdistan Region, Iraq&lt;/p&gt;
  264.  
  265. &lt;p dir="auto"&gt;🧾 Postal Code: 24005&lt;/p&gt;
  266.  
  267. &lt;p dir="auto"&gt;🛣️ Main connecting road: Charchall Road&lt;/p&gt;
  268.  
  269. &lt;p dir="auto"&gt;📍 Nearby village: benatah&lt;/p&gt;
  270.  
  271. &lt;p dir="auto"&gt;This village is recognized by local government maps, but it is still missing from OpenStreetMap. We kindly ask for it to be added so that the area can be better represented for residents, navigation, and future development.&lt;/p&gt;
  272. </description>
  273.      <dc:creator>Harkimuhamad</dc:creator>
  274.      <pubDate>Sat, 28 Jun 2025 12:28:24 +0000</pubDate>
  275.      <comments>https://www.openstreetmap.org/user/Harkimuhamad/diary/406999#comments</comments>
  276.      <geo:lat>36.7519516162354</geo:lat>
  277.      <geo:long>43.74403953552246</geo:long>
  278.      <georss:point>36.7519516162354 43.74403953552246</georss:point>
  279.    </item>
  280.    <item>
  281.      <title>résumé</title>
  282.      <link>https://www.openstreetmap.org/user/Gasconha18/diary/406998</link>
  283.      <guid>https://www.openstreetmap.org/user/Gasconha18/diary/406998</guid>
  284.      <description>&lt;h2 dir="auto" id="objc"&gt;objc.&lt;/h2&gt;
  285. &lt;ul dir="auto"&gt;
  286.  &lt;li&gt;Road networks / Réseaux routiers&lt;/li&gt;
  287. &lt;/ul&gt;
  288.  
  289. &lt;p dir="auto"&gt;(esp. ref /
  290. spé. ref)&lt;/p&gt;
  291.  
  292. &lt;h2 dir="auto" id="zone"&gt;zone&lt;/h2&gt;
  293. &lt;ul dir="auto"&gt;
  294.  &lt;li&gt;Gironde + Northern Landes (France) /  Gironde + Nord des Landes (France)&lt;/li&gt;
  295. &lt;/ul&gt;
  296.  
  297. </description>
  298.      <dc:creator>Gasconha18</dc:creator>
  299.      <pubDate>Sat, 28 Jun 2025 00:00:21 +0000</pubDate>
  300.      <comments>https://www.openstreetmap.org/user/Gasconha18/diary/406998#comments</comments>
  301.    </item>
  302.    <item>
  303.      <title>none</title>
  304.      <link>https://www.openstreetmap.org/user/BKPC/diary/406995</link>
  305.      <guid>https://www.openstreetmap.org/user/BKPC/diary/406995</guid>
  306.      <description>&lt;p dir="auto"&gt;none&lt;/p&gt;
  307. </description>
  308.      <dc:creator>BKPC</dc:creator>
  309.      <pubDate>Fri, 27 Jun 2025 15:03:33 +0000</pubDate>
  310.      <comments>https://www.openstreetmap.org/user/BKPC/diary/406995#comments</comments>
  311.    </item>
  312.    <item>
  313.      <title>Introduction</title>
  314.      <link>https://www.openstreetmap.org/user/Ofoyrwoth/diary/406994</link>
  315.      <guid>https://www.openstreetmap.org/user/Ofoyrwoth/diary/406994</guid>
  316.      <description>&lt;p dir="auto"&gt;Today is my introduction to OSM through an internship process by Mr Samson who take as through an online intern, we are getting into it before you know it and this will mark the start of one of the greatest open street mappers who has ver been born, am actually learning a lot from this process and looking forward to contributing so much to the members of the community, we wanna make Uganda great and make my village the best in the world
  317. #2025OptusAcademyInternship&lt;/p&gt;
  318. </description>
  319.      <dc:creator>Ofoyrwoth</dc:creator>
  320.      <pubDate>Fri, 27 Jun 2025 08:26:53 +0000</pubDate>
  321.      <comments>https://www.openstreetmap.org/user/Ofoyrwoth/diary/406994#comments</comments>
  322.      <geo:lat>0.051757798037387476</geo:lat>
  323.      <geo:long>32.46254588729994</geo:long>
  324.      <georss:point>0.051757798037387476 32.46254588729994</georss:point>
  325.    </item>
  326.    <item>
  327.      <title>Isócronas en Python</title>
  328.      <link>https://www.openstreetmap.org/user/kaxtillo/diary/406993</link>
  329.      <guid>https://www.openstreetmap.org/user/kaxtillo/diary/406993</guid>
  330.      <description>&lt;h2 dir="auto" id="resaltar-reas-transitables-en-python"&gt;Resaltar áreas transitables en Python&lt;/h2&gt;
  331.  
  332. &lt;p dir="auto"&gt;&lt;img src="https://live.staticflickr.com/65535/54615084087_a4742d1dd2.jpg" alt="Isócronas Popayán" loading="lazy"&gt;
  333. En las ciencias geoespaciales y la inteligencia de ubicación, las isócronas representan áreas geográficas accesibles en un tiempo determinado desde un punto específico. Por ejemplo, en el contexto de las distancias a pie, las isócronas son herramientas útiles para profesionales como los urbanistas que buscan comprender la accesibilidad y la conectividad dentro de un área determinada.&lt;/p&gt;
  334.  
  335. &lt;p dir="auto"&gt;Al visualizar las isócronas, la ciencia de datos puede proporcionar una herramienta rápida y fácil de usar para ayudar a obtener información sobre el nivel de conectividad y accesibilidad a pie de los vecindarios, ayudar a identificar áreas que están bien conectadas y señalar áreas potenciales de mejoras de infraestructura.&lt;/p&gt;
  336.  
  337. &lt;p dir="auto"&gt;En este artículo, explico cómo generar isócronas de distancia a pie mediante los paquetes de Python NetworkX (diseñado para análisis de grafos) y OSMNnx (que combina OpenStreetMap y NetworkX). Tomamos como ejemplo Perímetro urbano de la ciudad de Popayán. Primero, descargamos la red vial del área, seleccionamos un nodo aleatorio (una intersección aleatoria) y dibujamos las isócronas de distancia a pie de 5, 10, 20 y 30 minutos a su alrededor.&lt;/p&gt;
  338.  
  339. &lt;h2 dir="auto" id="adquisicin-de-datos"&gt;1. Adquisición de datos&lt;/h2&gt;
  340. &lt;p dir="auto"&gt;Primero, importaremos OSMnx y lo usaremos para descargar los límites administrativos del área objetivo. Puede reemplazarlo por el nombre de cualquier lugar que prefiera, que puede consultar fácilmente en OpenStreetMap. A continuación, usaremos OSMnx para descargar la red vial del área objetivo y mostrar el tamaño de esta red de nodos en términos de número de intersecciones y segmentos viales. Además, debemos especificar el tipo de red , que ahora está configurado como “walk” para obtener solo las partes transitables de la red vial.&lt;/p&gt;
  341.  
  342. &lt;pre dir="auto"&gt;&lt;code&gt;# Importing osmnx
  343. import osmnx as ox
  344.  
  345. # Configurar Matplotlib para visualización si es necesario
  346. # import matplotlib.pyplot as plt
  347.  
  348. # Definir el polígono para la ciudad de Popayán, Cauca, Colombia
  349. # Es importante ser específico para que OSMnx identifique correctamente el área.
  350. # Puedes probar con diferentes niveles de especificidad si la primera no funciona,
  351. # por ejemplo: 'Popayán, Colombia' o 'Popayán'.
  352. # 'Perímetro urbano de Popayán, Cauca, Colombia' es un buen punto de partida.
  353. print("Geocodificando la ciudad de Popayán...")
  354. try:
  355.    admin_district = ox.geocode_to_gdf('Perímetro urbano de Popayán, Cauca, Colombia')
  356.    print("Geocodificación exitosa.")
  357. except Exception as e:
  358.    print(f"Error al geocodificar Popayán: {e}")
  359.    print("Asegúrate de que la cadena de ubicación sea correcta y haya conexión a internet.")
  360.    # Puedes probar con una cadena menos específica si da error, como 'Popayán, Colombia' o 'Popayán'
  361.    admin_district = ox.geocode_to_gdf('Popayán, Colombia') # Intento alternativo
  362.  
  363. # Muestra el polígono en un gráfico (opcional, para verificar que es correcto)
  364. print("Mostrando el polígono geocodificado...")
  365. admin_district.plot()
  366. # Si estás en un entorno interactivo como Jupyter, la trama se mostrará automáticamente.
  367. # Si estás en un script .py, puedes añadir plt.show() al final para que la ventana del gráfico aparezca.
  368. # plt.show()
  369.  
  370. # Extraer la geometría del polígono de la primera fila del GeoDataFrame
  371. # Asumimos que el primer resultado es el correcto para la ciudad de Popayán.
  372. # Puedes inspeccionar admin_district si hay múltiples geometrías.
  373. admin_poly = admin_district.geometry.values[0]
  374.  
  375. # Guardar imagen del mapa
  376. png_path = os.path.join(output_dir, "map.png")
  377. plt.savefig(png_path, dpi=300, bbox_inches='tight')
  378.  
  379. # Cargar el grafo de la red de calles dentro de ese polígono
  380. print("Cargando el grafo de la red de calles de Popayán...")
  381. G = ox.graph_from_polygon(admin_poly, network_type='walk')
  382. print("Grafo cargado exitosamente.")
  383.  
  384. print('\nAnálisis de la red de calles de Popayán:')
  385. print('Número de intersecciones (nodos): ', G.number_of_nodes())
  386. print('Número de segmentos de carretera (aristas):',  G.number_of_edges())
  387.  
  388. # Opcional: Visualizar el grafo
  389. # print("\nVisualizando el grafo...")
  390. # fig, ax = ox.plot_graph(G, figsize=(10, 10), node_size=0, edge_linewidth=0.5, show=False, close=False)
  391. # plt.title("Red Peatonal de Popayán")
  392. # plt.show()
  393. &lt;/code&gt;&lt;/pre&gt;
  394.  
  395. &lt;h2 dir="auto" id="polgonos-de-alcanzabilidad"&gt;2. Polígonos de alcanzabilidad&lt;/h2&gt;
  396. &lt;p dir="auto"&gt;Ahora, construyamos los polígonos isócronos de transitabilidad. Para ello, primero, asumimos una velocidad promedio de caminata de 5 km/h (1,39 m/s) y, con esta velocidad, asignamos un tiempo de caminata a cada borde de la red vial. Luego, seleccionamos un nodo aleatorio para comenzar y definimos la lista de rangos de transitabilidad: 5, 10, 20 y 30 minutos.&lt;/p&gt;
  397.  
  398. &lt;p dir="auto"&gt;Para crear los polígonos de accesibilidad, primero usamos la función integrada de NetworkX llamada _ego graph , que devuelve un subgrafo específico de la red vial original que contiene todos los nodos dentro de un radio determinado, según las métricas de distancia que elijamos. Si seleccionamos _travel time , podemos devolver el subgrafo accesible en un tiempo determinado y almacenarlo como un atributo de borde llamado _travel time .&lt;/p&gt;
  399.  
  400. &lt;p dir="auto"&gt;Luego, necesitamos extraer todas las coordenadas de los nodos de este subgrafo, que almacenaremos en la lista _node points . Finalmente, las convertimos en un polígono, lo graficamos y lo guardamos para la siguiente sección.&lt;/p&gt;
  401.  
  402. &lt;p dir="auto"&gt;El resultado: todos los polígonos isócronos de transitabilidad, para 5, 10, 20 y 30 minutos, respectivamente&lt;/p&gt;
  403.  
  404. &lt;pre dir="auto"&gt;&lt;code&gt;# Define the walking speed (5 km/h -&amp;gt; 1.39 m/s)
  405. walking_speed = 1.39  # in meters per second
  406.  
  407. # Calculate travel time for each edge
  408. for u, v, data in G.edges(data=True):
  409.    # Calculate travel time in seconds
  410.    data['travel_time'] = data['length'] / walking_speed
  411.  
  412. # Pick a center node
  413. center_node = list(G.nodes())[30]  # starting point
  414.  
  415. # Generate isochrones
  416. isochrone_times = [5, 10, 20, 30]  # isochrones in minutes
  417.  
  418. # Library imports
  419. import networkx as nx
  420. from shapely.geometry import Point, Polygon  
  421. import geopandas as gpd
  422.  
  423. isochrone_polys = []
  424.  
  425. for time in isochrone_times:
  426.    subgraph = nx.ego_graph(G,
  427.                            center_node,
  428.                            radius=time*60,
  429.                            distance='travel_time')
  430.  
  431.    node_points = [Point((data['x'], data['y']))
  432.                   for node, data in subgraph.nodes(data=True)]
  433.  
  434.    polygon = Polygon(gpd.GeoSeries(node_points).unary_union.convex_hull)
  435.    gpd.GeoDataFrame([polygon], columns = ['geometry']).plot()
  436.    isochrone_polys.append(gpd.GeoSeries([polygon]))
  437. &lt;/code&gt;&lt;/pre&gt;
  438.  
  439. &lt;h2 dir="auto" id="visualizando-las-iscronas"&gt;3. Visualizando las isócronas&lt;/h2&gt;
  440.  
  441. &lt;p dir="auto"&gt;Por último, utilicemos Matplotlib y la coloración de rojo a verde para trazar y visualizar las isócronas sobre la red de carreteras.&lt;/p&gt;
  442.  
  443. &lt;pre dir="auto"&gt;&lt;code&gt;import os
  444.  
  445. # Crear carpeta de salida (si no existe)
  446. output_dir = "isochrones_popayan"
  447. os.makedirs(output_dir, exist_ok=True)
  448.  
  449. import matplotlib.pyplot as plt
  450. import matplotlib.patches as mpatches
  451. import osmnx as ox
  452. import networkx as nx
  453. import geopandas as gpd
  454.  
  455.  
  456. ox.settings.use_cache = True
  457. ox.settings.log_console = True
  458.  
  459. # 1. Obtener geometría de Popayán
  460. admin_district = ox.geocode_to_gdf('Perímetro urbano de Popayán, Cauca, Colombia')
  461. polygon = admin_district.geometry.iloc[0]
  462.  
  463. # 2. Descargar red caminable
  464. G = ox.graph_from_polygon(polygon, network_type='walk', simplify=True)
  465.  
  466. # 3. Proyectar grafo a CRS métrico
  467. G_proj = ox.project_graph(G)
  468. nodes_proj = ox.graph_to_gdfs(G_proj, nodes=True, edges=False)
  469.  
  470. # 4. Nodo de inicio: centroide proyectado
  471.  
  472. # Coordenadas del punto inicial (WGS84)
  473. lat, lon = 2.441901, -76.606439
  474.  
  475. # Crear GeoSeries y proyectar al CRS del grafo
  476. point_wgs = gpd.GeoSeries([gpd.points_from_xy([lon], [lat])[0]], crs="EPSG:4326")
  477. point_proj = point_wgs.to_crs(G_proj.graph['crs'])
  478. x, y = point_proj.geometry.iloc[0].x, point_proj.geometry.iloc[0].y
  479.  
  480. # Obtener el nodo más cercano a esas coordenadas proyectadas
  481. center_node = ox.distance.nearest_nodes(G_proj, X=x, Y=y)
  482.  
  483.  
  484.  
  485. # 5. Definir tiempos y distancias
  486. trip_times = [5, 10, 15, 20]  # minutos
  487. meters_per_minute = 80  # m/min
  488. travel_distances = [t * meters_per_minute for t in trip_times]
  489.  
  490. # 6. Generar polígonos de isócrona
  491. def make_iso_polys(G, center_node, distances):
  492.    polys = []
  493.    for dist in distances:
  494.        subgraph = nx.ego_graph(G, center_node, radius=dist, distance='length')
  495.        nodes_gdf = ox.graph_to_gdfs(subgraph, nodes=True, edges=False)
  496.        if not nodes_gdf.empty:
  497.            union = nodes_gdf.unary_union
  498.            buffered = gpd.GeoSeries([union]).buffer(100)  # Aumentar buffer para visibilidad
  499.            polys.append(buffered)
  500.        else:
  501.            polys.append(gpd.GeoSeries())
  502.    return polys
  503.  
  504. isochrone_polys = make_iso_polys(G_proj, center_node, travel_distances)
  505.  
  506. # 7. Visualización
  507. fig, ax = plt.subplots(figsize=(10, 10))
  508. colors = ['red', 'orange', 'yellow', 'green']
  509.  
  510. # Dibujar isócronas
  511. for idx, (poly, time) in enumerate(reversed(list(zip(isochrone_polys, trip_times)))):
  512.    if not poly.empty and not poly.is_empty.all():
  513.        poly.plot(ax=ax, color=colors[idx], alpha=0.4)
  514.        poly.boundary.plot(ax=ax, color=colors[idx], linewidth=2)
  515.  
  516. # Leyenda manual
  517. handles = [
  518.    mpatches.Patch(color=colors[idx], alpha=0.5, label=f'{time} min')
  519.    for idx, time in enumerate(reversed(trip_times))
  520. ]
  521.  
  522. ox.plot_graph(G_proj, ax=ax, node_size=0, edge_linewidth=0.5, show=False)
  523. ax.set_title("Isócronas desde el centro de Popayán, Cauca", fontsize=15)
  524. plt.legend(handles=handles)
  525. plt.tight_layout()
  526.  
  527. # Guardar imagen del mapa
  528. png_path = os.path.join(output_dir, "isochrones_map.png")
  529. plt.savefig(png_path, dpi=300, bbox_inches='tight')
  530.  
  531.  
  532. plt.show()
  533. &lt;/code&gt;&lt;/pre&gt;
  534.  
  535. &lt;p dir="auto"&gt;&lt;a href="https://github.com/kaxtillo/OSMnx/blob/main/OSMnx_isochrone.ipynb" rel="nofollow noopener noreferrer"&gt;Repositorio&lt;/a&gt;&lt;/p&gt;
  536. </description>
  537.      <dc:creator>kaxtillo</dc:creator>
  538.      <pubDate>Thu, 26 Jun 2025 20:14:11 +0000</pubDate>
  539.      <comments>https://www.openstreetmap.org/user/kaxtillo/diary/406993#comments</comments>
  540.      <geo:lat>2.4415215095572482</geo:lat>
  541.      <geo:long>-76.60780334263109</geo:long>
  542.      <georss:point>2.4415215095572482 -76.60780334263109</georss:point>
  543.    </item>
  544.    <item>
  545.      <title>OsmAPP 1.7.0 released</title>
  546.      <link>https://www.openstreetmap.org/user/zby-cz/diary/406992</link>
  547.      <guid>https://www.openstreetmap.org/user/zby-cz/diary/406992</guid>
  548.      <description>&lt;ul dir="auto"&gt;
  549.  &lt;li&gt;URL: &lt;a href="https://osmapp.org" rel="nofollow noopener noreferrer" dir="auto"&gt;https://osmapp.org&lt;/a&gt;&lt;/li&gt;
  550.  &lt;li&gt;Full changelog: &lt;a href="https://github.com/zbycz/osmapp/releases/tag/v1.7.0" rel="nofollow noopener noreferrer" dir="auto"&gt;https://github.com/zbycz/osmapp/releases/tag/v1.7.0&lt;/a&gt;&lt;/li&gt;
  551. &lt;/ul&gt;
  552.  
  553. &lt;p dir="auto"&gt;OsmAPP is the one integrated app for OpenStreetMap ecosystem for both web and mobile. It should be as easy to use as Google Maps, but fully open-source using all the great services around. It was first aimed at broad public, but now it becomes apparent, that it works best for the OpenStreetMap contributors, who want better UX or share OSM around.&lt;/p&gt;
  554.  
  555. &lt;p dir="auto"&gt;Special thanks to all our 6 contributors in this release. 🎉&lt;/p&gt;
  556.  
  557. &lt;h3 dir="auto" id="the-new-relation-editor"&gt;The new Relation editor&lt;/h3&gt;
  558.  
  559. &lt;p dir="auto"&gt;The main feature of this release is the reworked Edit dialog with the new Relation editor. That took a lot of work and refactoring. Now if you click (or create) a relation, you can browser through its members and its parents and easily edit metadata accross whole hierarchies.&lt;/p&gt;
  560.  
  561. &lt;p dir="auto"&gt;It is the most useful on hierarchies like the &lt;code dir="auto"&gt;climbing=area&lt;/code&gt;, &lt;code dir="auto"&gt;climbing=crag&lt;/code&gt; and routes (&lt;a href="https://osmapp.org/relation/17130099/edit" rel="nofollow noopener noreferrer"&gt;example here&lt;/a&gt;), but it is written in general manner and can help OSM contributors in unexpected ways.&lt;/p&gt;
  562.  
  563. &lt;p dir="auto"&gt;&lt;img width="500" alt="editdialog" src="https://raw.githubusercontent.com/zbycz/osm-static/main/screenshots/release-1.7.0/editdialog.jpg" loading="lazy"&gt;&lt;/p&gt;
  564.  
  565. &lt;h3 dir="auto" id="indoor-maps---"&gt;Indoor maps 🏢 🏣 🏛️&lt;/h3&gt;
  566.  
  567. &lt;p dir="auto"&gt;Thanks to &lt;a href="https://2metz.fr/" rel="nofollow noopener noreferrer"&gt;@francois2metz&lt;/a&gt; who created vector tiles for indoor features (&lt;a href="https://indorequeal.com/" rel="nofollow noopener noreferrer"&gt;indorequeal.com&lt;/a&gt;), you can now browse inside of buildings, where it is mapped with &lt;code dir="auto"&gt;level=*&lt;/code&gt; and &lt;code dir="auto"&gt;indoor=*&lt;/code&gt; tags. (&lt;a href="https://osmapp.org/#17.85/50.0726/14.4023" rel="nofollow noopener noreferrer"&gt;Example&lt;/a&gt;). Or find some examples in your neighborhood with query: &lt;code dir="auto"&gt;level=* and indoor=*&lt;/code&gt; which you can enter in the search box (or &lt;a href="https://osmapp.org/?q=level=*%20and%20indoor=*" rel="nofollow noopener noreferrer"&gt;link&lt;/a&gt;)&lt;/p&gt;
  568.  
  569. &lt;p dir="auto"&gt;&lt;img width="500" alt="indoor" src="https://raw.githubusercontent.com/zbycz/osm-static/main/screenshots/release-1.7.0/indoor.jpg" loading="lazy"&gt;&lt;/p&gt;
  570.  
  571. &lt;h3 dir="auto" id="directions-evolved----"&gt;Directions evolved 🚶 🚴 🚗 🚀&lt;/h3&gt;
  572.  
  573. &lt;p dir="auto"&gt;Directions form has evolved to the industry standard. You can add multiple destinations, drag&amp;amp;drop them, click the map, drag the markers or choose “My location”. Thanks to &lt;a href="https://www.openstreetmap.org/user/jvaclavik" rel="nofollow noopener noreferrer"&gt;@jvaclavik&lt;/a&gt; for development, and &lt;a href="https://github.com/karussell" rel="nofollow noopener noreferrer"&gt;@karussell&lt;/a&gt; for providing a free tier on the Graphhoper.com. ❤️&lt;/p&gt;
  574.  
  575. &lt;p dir="auto"&gt;&lt;img width="400" alt="directions" src="https://raw.githubusercontent.com/zbycz/osm-static/main/screenshots/release-1.7.0/directions.jpg" loading="lazy"&gt;&lt;/p&gt;
  576.  
  577. &lt;h3 dir="auto" id="wikimedia-commons-category-preview"&gt;Wikimedia Commons Category preview&lt;/h3&gt;
  578.  
  579. &lt;p dir="auto"&gt;One fun addition was to develop a custom “masonry-style” preview image, when an OSM feature links to a Wikimedia Commons Category. OsmAPP now download first 10 images and tries to fit them in a nice collage. You can explore OSM items in your vicinity by executing this Overpass query in the OsmAPP searchbox: &lt;code dir="auto"&gt;op:nwr["wikimedia_commons"~"Category"]&lt;/code&gt;
  580. (or &lt;a href="https://osmapp.org/?q=op:nwr%5B%22wikimedia_commons%22~%22Category%22%5D" rel="nofollow noopener noreferrer"&gt;link&lt;/a&gt;).&lt;/p&gt;
  581.  
  582. &lt;p dir="auto"&gt;&lt;img width="400" alt="category preview" src="https://raw.githubusercontent.com/zbycz/osm-static/main/screenshots/release-1.7.0/category.jpg" loading="lazy"&gt;&lt;/p&gt;
  583.  
  584. &lt;h3 dir="auto" id="other-notable-changes"&gt;Other notable changes&lt;/h3&gt;
  585. &lt;ul dir="auto"&gt;
  586.  &lt;li&gt;⚙️ Add metric/imperial switch to settings by &lt;a href="https://github.com/dlurak" rel="nofollow noopener noreferrer"&gt;@Dlurak&lt;/a&gt;, &lt;a href="https://github.com/zbycz/osmapp/pull/812" rel="nofollow noopener noreferrer"&gt;PR&lt;/a&gt;
  587.    &lt;ul dir="auto"&gt;
  588.      &lt;li&gt;You can choose the system by clicking the measure component in the down left. It will be instantly propagated through the whole app.&lt;/li&gt;
  589.    &lt;/ul&gt;
  590.  &lt;/li&gt;
  591.  &lt;li&gt;🌎 Use globe 3D projection by &lt;a href="https://www.openstreetmap.org/user/jvaclavik" rel="nofollow noopener noreferrer"&gt;@jvaclavik&lt;/a&gt;, &lt;a href="https://github.com/zbycz/osmapp/pull/817" rel="nofollow noopener noreferrer"&gt;PR&lt;/a&gt;
  592.    &lt;ul dir="auto"&gt;
  593.      &lt;li&gt;Because flat-earth is so old-school. 🙂 🗺️&lt;/li&gt;
  594.    &lt;/ul&gt;
  595.  &lt;/li&gt;
  596.  &lt;li&gt;🚌 add transport layer from Thunderforest.com + dark mode by &lt;a href="https://github.com/zbycz" rel="nofollow noopener noreferrer"&gt;@zbycz&lt;/a&gt;, &lt;a href="https://github.com/zbycz/osmapp/pull/789" rel="nofollow noopener noreferrer"&gt;PR&lt;/a&gt;
  597.    &lt;ul dir="auto"&gt;
  598.      &lt;li&gt;This is the only layer on OsmAPP, which follows the user setting of Dark mode / Light mode.&lt;/li&gt;
  599.    &lt;/ul&gt;
  600.  &lt;/li&gt;
  601.  &lt;li&gt;📍 Coordinate and OLC search by &lt;a href="https://github.com/dlurak" rel="nofollow noopener noreferrer"&gt;@Dlurak&lt;/a&gt;, &lt;a href="https://github.com/zbycz/osmapp/pull/927" rel="nofollow noopener noreferrer"&gt;PR&lt;/a&gt;
  602.    &lt;ul dir="auto"&gt;
  603.      &lt;li&gt;Plus codes and coordinates can be pasted in the SearchBox to display it on the map. Also when you share&lt;/li&gt;
  604.    &lt;/ul&gt;
  605.  &lt;/li&gt;
  606. &lt;/ul&gt;
  607.  
  608. &lt;h3 dir="auto" id="climbing-project-update"&gt;Climbing project update&lt;/h3&gt;
  609.  
  610. &lt;p dir="auto"&gt;OpenClimbing.org is a standalone app for using the rock climbing data in OpenStreetMap. It is fully based on OsmAPP and with this release we celebrate the public launch of the service.&lt;/p&gt;
  611.  
  612. &lt;p dir="auto"&gt;You can read more in a dedicated blogpost: &lt;a href="https://www.openstreetmap.org/user/jvaclavik/diary/406991" rel="nofollow noopener noreferrer"&gt;HERE&lt;/a&gt;&lt;/p&gt;
  613.  
  614. &lt;h3 dir="auto" id="summary-of-all-cool-features-in-osmapp----"&gt;Summary of all cool features in OsmAPP  🗺 📱 🖥&lt;/h3&gt;
  615.  
  616. &lt;ul dir="auto"&gt;
  617.  &lt;li&gt;&lt;strong&gt;clickable map&lt;/strong&gt; – POIs, cities, localities, ponds, airports (more coming soon)&lt;/li&gt;
  618.  &lt;li&gt;&lt;strong&gt;feature panel&lt;/strong&gt; – presets and fields from iD editor
  619.    &lt;ul dir="auto"&gt;
  620.      &lt;li&gt;Display multiple images from Wikipedia, Wikidata, Commons, Mapillary, KartaView, Panoramax or Fody&lt;/li&gt;
  621.      &lt;li&gt;public transport: clickable line numbers (on stops), routes on map (on stations), stop itineraries (on routes)&lt;/li&gt;
  622.      &lt;li&gt;Socket types on electric vehicle charging stations&lt;/li&gt;
  623.      &lt;li&gt;Runway table on airports, viewpoint direction arrow, colors as colors&lt;/li&gt;
  624.    &lt;/ul&gt;
  625.  &lt;/li&gt;
  626.  &lt;li&gt;&lt;strong&gt;editing&lt;/strong&gt; – Save changes with osm login. Insert note for anonymous users.
  627.    &lt;ul dir="auto"&gt;
  628.      &lt;li&gt;Opening hours editor – use simple editor for most common cases.&lt;/li&gt;
  629.      &lt;li&gt;Relation hierarchy editor - simply click through relation childs and parents. Optimized for climbing=area, climbing=crag and routes.&lt;/li&gt;
  630.    &lt;/ul&gt;
  631.  &lt;/li&gt;
  632.  &lt;li&gt;&lt;strong&gt;search engine&lt;/strong&gt; – try for example “Tesco, London” (powered by Photon).
  633.    &lt;ul dir="auto"&gt;
  634.      &lt;li&gt;Category search using &lt;a href="https://github.com/openstreetmap/id-tagging-schema" rel="nofollow noopener noreferrer"&gt;iD editor presets&lt;/a&gt;&lt;/li&gt;
  635.      &lt;li&gt;For advanced users: support for overpass queries (e.g. &lt;code dir="auto"&gt;amenity=*&lt;/code&gt; or &lt;code dir="auto"&gt;op:&amp;lt;query&amp;gt;&lt;/code&gt;)&lt;/li&gt;
  636.    &lt;/ul&gt;
  637.  &lt;/li&gt;
  638.  &lt;li&gt;&lt;strong&gt;directions&lt;/strong&gt; - everyhing you need from modern app - drag&amp;amp;drop destinations, drag markers, click to map to select, etc. (by &lt;a href="https://www.graphhopper.com/" rel="nofollow noopener noreferrer"&gt;GraphHopper Directions API&lt;/a&gt;)&lt;/li&gt;
  639.  &lt;li&gt;&lt;strong&gt;vector maps&lt;/strong&gt; – with the possibility of tilting to 3D (drag the compass, or do two fingers drag)
  640.    &lt;ul dir="auto"&gt;
  641.      &lt;li&gt;3D terrain – turned on when tilted&lt;/li&gt;
  642.      &lt;li&gt;tourist map – vector Outdoor map from MapTiler including marked routes&lt;/li&gt;
  643.    &lt;/ul&gt;
  644.  &lt;/li&gt;
  645.  &lt;li&gt;&lt;strong&gt;layer switcher&lt;/strong&gt; – you can add your own layers, also select from &lt;code dir="auto"&gt;editor-layer-index&lt;/code&gt; list&lt;/li&gt;
  646.  &lt;li&gt;&lt;strong&gt;mobile applications&lt;/strong&gt; – using PWA technology, see &lt;a href="https://osmapp.org/install" rel="nofollow noopener noreferrer"&gt;osmapp.org/install&lt;/a&gt;&lt;/li&gt;
  647.  &lt;li&gt;&lt;strong&gt;permanent URLs&lt;/strong&gt; – eg. &lt;a href="https://osmapp.org/way/123557148" rel="nofollow noopener noreferrer"&gt;osmapp.org/way/123557148&lt;/a&gt; and shortener, eg. &lt;a href="https://osmapp.org/kkjwwaw" rel="nofollow noopener noreferrer"&gt;osmapp.org/kkjwwaw&lt;/a&gt;&lt;/li&gt;
  648.  &lt;li&gt;&lt;strong&gt;creating POIs&lt;/strong&gt; – after clicking the coordinates (see e.g. &lt;a href="https://osmapp.org/50.1,14.39" rel="nofollow noopener noreferrer"&gt;osmapp.org/50.1,14.39&lt;/a&gt;)&lt;/li&gt;
  649.  &lt;li&gt;&lt;strong&gt;languages&lt;/strong&gt; – interface in English, Czech, German, Polish, Spanish, Amharic, Italian, French, Japanese&lt;/li&gt;
  650.  &lt;li&gt;&lt;strong&gt;undelete&lt;/strong&gt; – undo accidental delete in osmapp or elsewhere, e.g. &lt;a href="https://osmapp.org/node/1219767385" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt;&lt;/li&gt;
  651.  &lt;li&gt;and a lot of little details 🙂&lt;/li&gt;
  652. &lt;/ul&gt;
  653.  
  654. &lt;hr&gt;
  655.  
  656. &lt;p dir="auto"&gt;We are looking forward to any feedback!&lt;/p&gt;
  657.  
  658. &lt;p dir="auto"&gt;Thank you for your support!&lt;/p&gt;
  659.  
  660. &lt;p dir="auto"&gt;&lt;a href="https://www.openstreetmap.org/user/zby-cz" rel="nofollow noopener noreferrer"&gt;@zbycz&lt;/a&gt; and &lt;a href="https://www.openstreetmap.org/user/jvaclavik" rel="nofollow noopener noreferrer"&gt;@jvaclavik&lt;/a&gt;&lt;/p&gt;
  661.  
  662. </description>
  663.      <dc:creator>zby-cz</dc:creator>
  664.      <pubDate>Thu, 26 Jun 2025 15:44:00 +0000</pubDate>
  665.      <comments>https://www.openstreetmap.org/user/zby-cz/diary/406992#comments</comments>
  666.    </item>
  667.    <item>
  668.      <title>Openclimbing.org - climbing guides &amp; topos in OpenStreetMap</title>
  669.      <link>https://www.openstreetmap.org/user/jvaclavik/diary/406991</link>
  670.      <guid>https://www.openstreetmap.org/user/jvaclavik/diary/406991</guid>
  671.      <description>&lt;p dir="auto"&gt;The goal of &lt;a href="https://openclimbing.org" dir="auto" rel="nofollow noopener noreferrer"&gt;https://openclimbing.org&lt;/a&gt; is to offer a &lt;strong&gt;non-commercial alternative to traditional climbing apps&lt;/strong&gt;. Instead of filling private databases, we decided to design a structure for &lt;a href="https://wiki.openstreetmap.org/wiki/Key:wikimedia_commons:path" rel="nofollow noopener noreferrer"&gt;mapping climbing routes&lt;/a&gt; directly into OpenStreetMap.&lt;/p&gt;
  672.  
  673. &lt;p dir="auto"&gt;This way, &lt;strong&gt;all data in the app is fully open and can be freely used or edited by anyone&lt;/strong&gt;.&lt;/p&gt;
  674.  
  675. &lt;p dir="auto"&gt;&lt;img src="https://janvaclavik.cz/wp-content/uploads/2025/06/hlubocepy.png" alt="Climbing guide for climbing crag Hlubočepy, Czechia" loading="lazy"&gt;
  676. &lt;a href="https://openclimbing.org/relation/17262674/climbing/photo/Hlubo%C4%8Depsk%C3%A9%20plotny%20-%20Prav%C3%A1%20plotna.jpg#17.00/50.0432/14.3924" rel="nofollow noopener noreferrer"&gt;Image: Crag with marked climbing routes in Hlubočepy, Czechia&lt;/a&gt;&lt;/p&gt;
  677.  
  678. &lt;h2 dir="auto" id="key-features-of-openclimbingorg"&gt;Key Features of openclimbing.org&lt;/h2&gt;
  679. &lt;ul dir="auto"&gt;
  680.  &lt;li&gt;
  681.    &lt;p dir="auto"&gt;Both the database and the &lt;a href="https://github.com/zbycz/osmapp" rel="nofollow noopener noreferrer"&gt;code&lt;/a&gt; are completely open, so anyone can contribute with content or code. Thanks to the open data approach, anyone can create new ways to use or visualize the data.&lt;/p&gt;
  682.  &lt;/li&gt;
  683.  &lt;li&gt;
  684.    &lt;p dir="auto"&gt;Each climbing route has defined GPS coordinates, making it easier to find in the terrain. This is big advantage but also a limitation – you cannot add routes without it.&lt;/p&gt;
  685.  &lt;/li&gt;
  686. &lt;/ul&gt;
  687.  
  688. &lt;p dir="auto"&gt;&lt;img src="https://janvaclavik.cz/wp-content/uploads/2025/06/map.png" alt="Showing climbing routes on the map" loading="lazy"&gt;
  689. &lt;a href="https://openclimbing.org/relation/17089246#18.58/49.6540/14.2522" rel="nofollow noopener noreferrer"&gt;Image: Climbing routes on the map&lt;/a&gt;&lt;/p&gt;
  690.  
  691. &lt;ul dir="auto"&gt;
  692.  &lt;li&gt;Optimized for mobile devices, so it can be used directly in the field.&lt;/li&gt;
  693.  &lt;li&gt;Integration of the map with photo EXIF data – you can see on the map where a photo was taken and where climbing routes are located.&lt;/li&gt;
  694. &lt;/ul&gt;
  695.  
  696. &lt;h3 dir="auto" id="d-climbing-maps"&gt;3D climbing maps&lt;/h3&gt;
  697. &lt;ul dir="auto"&gt;
  698.  &lt;li&gt;Fully mapped climbing crags can be displayed in 3D – tilt the map (ctrl/cmd+drag)&lt;/li&gt;
  699. &lt;/ul&gt;
  700.  
  701. &lt;p dir="auto"&gt;&lt;img src="https://janvaclavik.cz/wp-content/uploads/2025/06/divadylko.png" alt="climbing crag in 3D" loading="lazy"&gt;
  702. &lt;a href="https://openclimbing.org/relation/17424001" rel="nofollow noopener noreferrer"&gt;Image: Kačák climbing area, Czechia&lt;/a&gt;&lt;/p&gt;
  703.  
  704. &lt;p dir="auto"&gt;&lt;img src="https://janvaclavik.cz/wp-content/uploads/2025/06/uskedalen.png" alt="Climbing area Uskedalen in 3D" loading="lazy"&gt;
  705. &lt;a href="https://openclimbing.org/relation/19136912" rel="nofollow noopener noreferrer"&gt;Image: Uskedalen climbing area, Norway&lt;/a&gt;&lt;/p&gt;
  706.  
  707. &lt;ul dir="auto"&gt;
  708.  &lt;li&gt;A basic climbing logbook for tracking ascents, with the option to display them directly on the map.&lt;/li&gt;
  709.  &lt;li&gt;For drawing climbing routes onto photos, we use the &lt;a href="https://wiki.openstreetmap.org/wiki/Key:wikimedia_commons:path" rel="nofollow noopener noreferrer"&gt;wikimedia_commons:path specification&lt;/a&gt;, and the photos are stored in &lt;a href="https://commons.wikimedia.org/" rel="nofollow noopener noreferrer"&gt;Wikimedia Commons&lt;/a&gt;. Additionally, we use a climbing tagging scheme documented directly on the &lt;a href="https://wiki.openstreetmap.org/wiki/Tag:sport%3Dclimbing" rel="nofollow noopener noreferrer"&gt;OSM Wiki&lt;/a&gt;, which is also supported by the iD editor.&lt;/li&gt;
  710. &lt;/ul&gt;
  711.  
  712. &lt;h3 dir="auto" id="grade-systems-conversion"&gt;Grade systems conversion&lt;/h3&gt;
  713.  
  714. &lt;ul dir="auto"&gt;
  715.  &lt;li&gt;The app includes a &lt;a href="https://openclimbing.org/climbing-grades" rel="nofollow noopener noreferrer"&gt;converter&lt;/a&gt; for most commonly used climbing grade systems.
  716. &lt;img src="https://janvaclavik.cz/wp-content/uploads/2025/06/grades.png" alt="Climbing grades table in openclimbing.org" loading="lazy"&gt;&lt;/li&gt;
  717. &lt;/ul&gt;
  718.  
  719. &lt;h1 dir="auto" id="stats"&gt;Stats&lt;/h1&gt;
  720.  
  721. &lt;ul dir="auto"&gt;
  722.  &lt;li&gt;We generate our own climbing tiles on the map, where we display:
  723.    &lt;ul dir="auto"&gt;
  724.      &lt;li&gt;26,000+ climbing areas&lt;/li&gt;
  725.      &lt;li&gt;22,000+ climbing routes&lt;/li&gt;
  726.      &lt;li&gt;1,700+ climbing routes drawn on photos&lt;/li&gt;
  727.      &lt;li&gt;8,000+ artificial climbing walls&lt;/li&gt;
  728.      &lt;li&gt;200+ via ferratas&lt;/li&gt;
  729.    &lt;/ul&gt;
  730.  &lt;/li&gt;
  731. &lt;/ul&gt;
  732.  
  733. &lt;p dir="auto"&gt;We are looking forward to any feedback!&lt;/p&gt;
  734.  
  735. &lt;p dir="auto"&gt;Thank you for your support.&lt;/p&gt;
  736.  
  737. &lt;p dir="auto"&gt;&lt;a href="https://www.openstreetmap.org/user/zby-cz" rel="nofollow noopener noreferrer"&gt;@zbycz&lt;/a&gt; and &lt;a href="https://www.openstreetmap.org/user/jvaclavik" rel="nofollow noopener noreferrer"&gt;@jvaclavik&lt;/a&gt;&lt;/p&gt;
  738. </description>
  739.      <dc:creator>jvaclavik</dc:creator>
  740.      <pubDate>Thu, 26 Jun 2025 15:40:57 +0000</pubDate>
  741.      <comments>https://www.openstreetmap.org/user/jvaclavik/diary/406991#comments</comments>
  742.    </item>
  743.    <item>
  744.      <title>Unicore UM980 use with RTKLIB for </title>
  745.      <link>https://www.openstreetmap.org/user/hopet/diary/406985</link>
  746.      <guid>https://www.openstreetmap.org/user/hopet/diary/406985</guid>
  747.      <description>&lt;p dir="auto"&gt;UM980 is relatively affordable chip allowing multi-constellation multi-frequency GNSS with capability to provide raw phase measurements and hence potentially suitable for use in OpenStreetMap environment for precise mapping susing RTK.&lt;/p&gt;
  748.  
  749. &lt;p dir="auto"&gt;In this post (or potentially series of posts), I will document my experiences with using UM980 with RTKLIB and other open-source or free tools.&lt;/p&gt;
  750.  
  751. &lt;h1 dir="auto" id="hardware"&gt;Hardware&lt;/h1&gt;
  752.  
  753. &lt;ul dir="auto"&gt;
  754.  &lt;li&gt;UM980 RTK GNSS USB Dongle with SMA antenna - ELT0222 (from &lt;a href="https://gnss.store/unicore-gnss-modules/247-401-elt0222.html#/77-ant_mb2-no_antenna" rel="nofollow noopener noreferrer"&gt;gnss.store&lt;/a&gt;)&lt;/li&gt;
  755.  &lt;li&gt;EM-FD700 antenna (form &lt;a href="https://www.aliexpress.com/item/1005007944873653.html" rel="nofollow noopener noreferrer"&gt;AliExpress&lt;/a&gt;)&lt;/li&gt;
  756. &lt;/ul&gt;
  757.  
  758. &lt;p dir="auto"&gt;The module can easily be configured using UPrecise tool coming with UM980. It is advisable to have faster than default COM port rate
  759. ~~~
  760. CONFIG COM1 230400
  761. ~~~
  762. and use the signal group 2 (note that this leads to reset of the UM980 module
  763. ~~~
  764. CONFIG SIGNALGROUP 2
  765. ~~~&lt;/p&gt;
  766.  
  767. &lt;p dir="auto"&gt;If you need to stop the stream of measured data, you can use
  768. ~~~
  769. UNLOG
  770. ~~~
  771. You can also UNLOG just specific messages.&lt;/p&gt;
  772.  
  773. &lt;p dir="auto"&gt;If you want to store your config of the module so that it survives unplugging and restarting the module, use
  774. ~~~
  775. SAVECONFIG
  776. ~~~&lt;/p&gt;
  777.  
  778. &lt;h1 dir="auto" id="software-setup-on-android"&gt;Software setup on Android&lt;/h1&gt;
  779.  
  780. &lt;h2 dir="auto" id="rtkgps---collecting-raw-phase-measurements"&gt;RTKGPS+ - collecting raw phase measurements&lt;/h2&gt;
  781. &lt;p dir="auto"&gt;This is to collect the raw data in real time. The &lt;a href="https://github.com/sctg-development/RtkGps" rel="nofollow noopener noreferrer"&gt;last RTKGPS+ tool is release&lt;/a&gt; is unfortunately relatively old and hence does not support, so the native UniCore support, which is available in &lt;a href="https://github.com/rtklibexplorer/RTKLIB/releases/" rel="nofollow noopener noreferrer"&gt;demo5_b34L version of RTKLIB&lt;/a&gt;, is not yet available in RTKGPS+. Hence it is mostly useful for collecting raw data, rather than providing real-time solutions. If you want to collect the data, choose BINEX as the format and just log the input stream from the USB. This is how to configure the module:&lt;/p&gt;
  782.  
  783. &lt;pre dir="auto"&gt;&lt;code&gt;CONFIG PPP DISABLE
  784.  
  785. OBSVMB 1
  786.  
  787. GPSEPHB 120
  788. BDSEPHB 120
  789. BD3EPHB 120
  790. GLOEPHB 120
  791. GALEPHB 120
  792.  
  793. GPSIONB 120
  794. BDSIONB 120
  795. BD3IONB 120
  796. GALIONB 120
  797. &lt;/code&gt;&lt;/pre&gt;
  798.  
  799. &lt;p dir="auto"&gt;If you want to have faster measurements, you can use
  800. ~~~
  801. OBSVMB 0.2
  802. ~~~
  803. But it may be then advisable to use at least 240kbaud rate of the COM port (which is generally well supported by RTKGPS+).&lt;/p&gt;
  804.  
  805. &lt;p dir="auto"&gt;The input stream configuration is 230400/8-N-1 and format to store the data is BINEX.&lt;/p&gt;
  806.  
  807. &lt;h2 dir="auto" id="rtkgps---undocumented-navtel-compatible-mode"&gt;RTKGPS+ - undocumented NavTel-compatible mode&lt;/h2&gt;
  808. &lt;p dir="auto"&gt;Alternatively, one can attempt to use it using undocumented mode of UM980 to produce binary data compatible data:
  809. ~~~
  810. RANGEB COM1 0.2
  811. ~~~
  812. However, I had problem that only very poor solutions were found, with only using GLONASS and Galileo constellation - probably due to lack of ephemeris included (use of “CONFIG ALLEPHRTCM ENABLE” option is still to be explored).&lt;/p&gt;
  813.  
  814. &lt;p dir="auto"&gt;Then the input format is NovAtel OEMV/4.&lt;/p&gt;
  815.  
  816. &lt;h2 dir="auto" id="rtkgps---recording-the-base-data"&gt;RTKGPS+ - recording the base data&lt;/h2&gt;
  817. &lt;p dir="auto"&gt;It is possible to use the RTKGPS+ to log also the data from the base, a nearby coming from IGS or from EUREF (both requiring a free registration) and store the data in RTCM 3 format.&lt;/p&gt;
  818.  
  819. &lt;h2 dir="auto" id="sw-maps---free-software-on-android-to-read-nmea-data"&gt;SW Maps - free software on Android to read NMEA data&lt;/h2&gt;
  820. &lt;p dir="auto"&gt;This is an example how to use PPP on the UM980 module and collect the data using &lt;a href="https://play.google.com/store/apps/details?id=np.com.softwel.swmaps&amp;amp;hl=en" rel="nofollow noopener noreferrer"&gt;SW Maps&lt;/a&gt;.
  821. ~~~
  822. CONFIG PPP ENABLE E6-HAS
  823. CONFIG PPP DATUM WGS84
  824. CONFIG PPP TIMEOUT 120
  825. CONFIG PPP CONVERGE 15 30&lt;/p&gt;
  826.  
  827. &lt;p dir="auto"&gt;GPGGA 0.2
  828. GPGSA 1
  829. GPGST 1
  830. GPGSV 1
  831. GPGLL 1
  832. GPGNS 1
  833. GPRMC 1
  834. ~~~&lt;/p&gt;
  835.  
  836. &lt;h1 dir="auto" id="use-of-rtklib-on-the-windows"&gt;Use of RTKLIB on the Windows&lt;/h1&gt;
  837.  
  838. &lt;p dir="auto"&gt;This assumes use of &lt;a href="https://github.com/rtklibexplorer/RTKLIB/releases/" rel="nofollow noopener noreferrer"&gt;demo5_b34L version of RTKLIB&lt;/a&gt; or later.
  839. Once the data is captured using RTKLIB, one can process the data using convbin and rtkpost from RTKLIB to process the data&lt;/p&gt;
  840.  
  841. &lt;h2 dir="auto" id="converting-from-unc-and-rtcm3-formats"&gt;Converting from UNC and RTCM3 formats&lt;/h2&gt;
  842. &lt;pre dir="auto"&gt;&lt;code&gt;convbin -od -os -oi -ot  rover_20250626042937.unc
  843. convbin -od -os -oi -ot  base_20250626042937.rtcm3
  844. &lt;/code&gt;&lt;/pre&gt;
  845.  
  846. &lt;h2 dir="auto" id="rtkpost-config-for-postprocessing-with-output-to-pos-file"&gt;rtkpost config for postprocessing with output to pos file&lt;/h2&gt;
  847. &lt;pre dir="auto"&gt;&lt;code&gt;# rtkpost options (2025/06/26 04:39:16, v.demo5 b34L)
  848.  
  849. pos1-posmode       =kinematic  # (0:single,1:dgps,2:kinematic,3:static,4:static-start,5:movingbase,6:fixed,7:ppp-kine,8:ppp-static,9:ppp-fixed)
  850. pos1-frequency     =l1+l2+l5+l6 # (1:l1,2:l1+l2,3:l1+l2+l5,4:l1+l2+l5+l6)
  851. pos1-soltype       =combined   # (0:forward,1:backward,2:combined,3:combined-nophasereset)
  852. pos1-elmask        =15         # (deg)
  853. pos1-snrmask_r     =off        # (0:off,1:on)
  854. pos1-snrmask_b     =off        # (0:off,1:on)
  855. pos1-snrmask_L1    =38,38,38,38,38,38,38,38,38
  856. pos1-snrmask_L2    =0,0,0,0,0,0,0,0,0
  857. pos1-snrmask_L5    =0,0,0,0,0,0,0,0,0
  858. pos1-snrmask_L6    =0,0,0,0,0,0,0,0,0
  859. pos1-dynamics      =on         # (0:off,1:on)
  860. pos1-tidecorr      =0          # (1:solid+2:otl+4:spole)
  861. pos1-ionoopt       =brdc       # (0:off,1:brdc,2:sbas,3:dual-freq,4:est-stec,5:ionex-tec,6:qzs-brdc)
  862. pos1-tropopt       =saas       # (0:off,1:saas,2:sbas,3:est-ztd,4:est-ztdgrad)
  863. pos1-sateph        =brdc       # (0:brdc,1:precise,2:brdc+sbas,3:brdc+ssrapc,4:brdc+ssrcom)
  864. pos1-posopt1       =off        # (0:off,1:on)
  865. pos1-posopt2       =off        # (0:off,1:on)
  866. pos1-posopt3       =off        # (0:off,1:on,2:precise)
  867. pos1-posopt4       =off        # (0:off,1:on)
  868. pos1-posopt5       =off        # (0:off,1:on)
  869. pos1-posopt6       =off        # (0:off,1:on)
  870. pos1-exclsats      =           # (prn ...)
  871. pos1-navsys        =47         # (1:gps+2:sbas+4:glo+8:gal+16:qzs+32:bds+64:navic)
  872. pos2-armode        =fix-and-hold # (0:off,1:continuous,2:instantaneous,3:fix-and-hold)
  873. pos2-gloarmode     =fix-and-hold # (0:off,1:on,2:autocal,3:fix-and-hold)
  874. pos2-bdsarmode     =off        # (0:off,1:on)
  875. pos2-arfilter      =on         # (0:off,1:on)
  876. pos2-arthres       =3
  877. pos2-arthresmin    =3
  878. pos2-arthresmax    =3
  879. pos2-arthres1      =0.1
  880. pos2-arthres2      =0
  881. pos2-arthres3      =1e-09
  882. pos2-arthres4      =1e-05
  883. pos2-varholdamb    =0.1        # (cyc^2)
  884. pos2-gainholdamb   =0.01
  885. pos2-arlockcnt     =0
  886. pos2-minfixsats    =4
  887. pos2-minholdsats   =5
  888. pos2-mindropsats   =10
  889. pos2-arelmask      =15         # (deg)
  890. pos2-arminfix      =100
  891. pos2-armaxiter     =1
  892. pos2-elmaskhold    =15         # (deg)
  893. pos2-aroutcnt      =20
  894. pos2-maxage        =30         # (s)
  895. pos2-syncsol       =off        # (0:off,1:on)
  896. pos2-slipthres     =0.05       # (m)
  897. pos2-dopthres      =0          # (m)
  898. pos2-rejionno      =1          # (m)
  899. pos2-rejcode       =10         # (m)
  900. pos2-niter         =1
  901. pos2-baselen       =0          # (m)
  902. pos2-basesig       =0          # (m)
  903. out-solformat      =llh        # (0:llh,1:xyz,2:enu,3:nmea)
  904. out-outhead        =on         # (0:off,1:on)
  905. out-outopt         =on         # (0:off,1:on)
  906. out-outvel         =off        # (0:off,1:on)
  907. out-timesys        =gpst       # (0:gpst,1:utc,2:jst)
  908. out-timeform       =hms        # (0:tow,1:hms)
  909. out-timendec       =3
  910. out-degform        =deg        # (0:deg,1:dms)
  911. out-fieldsep       =
  912. out-outsingle      =on         # (0:off,1:on)
  913. out-maxsolstd      =0          # (m)
  914. out-height         =geodetic   # (0:ellipsoidal,1:geodetic)
  915. out-geoid          =internal   # (0:internal,1:egm96,2:egm08_2.5,3:egm08_1,4:gsi2000)
  916. out-solstatic      =all        # (0:all,1:single)
  917. out-nmeaintv1      =0          # (s)
  918. out-nmeaintv2      =0          # (s)
  919. out-outstat        =residual   # (0:off,1:state,2:residual)
  920. stats-eratio1      =300
  921. stats-eratio2      =300
  922. stats-eratio5      =300
  923. stats-eratio6      =300
  924. stats-errphase     =0.003      # (m)
  925. stats-errphaseel   =0.003      # (m)
  926. stats-errphasebl   =0          # (m/10km)
  927. stats-errdoppler   =1          # (Hz)
  928. stats-snrmax       =52         # (dB.Hz)
  929. stats-errsnr       =0          # (m)
  930. stats-errrcv       =0          # ( )
  931. stats-stdbias      =30         # (m)
  932. stats-stdiono      =0.03       # (m)
  933. stats-stdtrop      =0.3        # (m)
  934. stats-prnaccelh    =3          # (m/s^2)
  935. stats-prnaccelv    =1          # (m/s^2)
  936. stats-prnbias      =0.0001     # (m)
  937. stats-prniono      =0.001      # (m)
  938. stats-prntrop      =0.0001     # (m)
  939. stats-prnpos       =0          # (m)
  940. stats-clkstab      =5e-12      # (s/s)
  941. ant1-postype       =llh        # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm,6:raw)
  942. ant1-pos1          =0          # (deg|m)
  943. ant1-pos2          =0          # (deg|m)
  944. ant1-pos3          =0          # (m|m)
  945. ant1-anttype       =
  946. ant1-antdele       =0          # (m)
  947. ant1-antdeln       =0          # (m)
  948. ant1-antdelu       =0          # (m)
  949. ant2-postype       =single     # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm,6:raw)
  950. ant2-pos1          =0          # (deg|m)
  951. ant2-pos2          =0          # (deg|m)
  952. ant2-pos3          =0          # (m|m)
  953. ant2-anttype       =
  954. ant2-antdele       =0          # (m)
  955. ant2-antdeln       =0          # (m)
  956. ant2-antdelu       =0          # (m)
  957. ant2-maxaveep      =1
  958. ant2-initrst       =on         # (0:off,1:on)
  959. misc-timeinterp    =off        # (0:off,1:on)
  960. misc-sbasatsel     =0          # (0:all)
  961. misc-rnxopt1       =
  962. misc-rnxopt2       =-EPHALL
  963. misc-pppopt        =
  964. file-satantfile    =
  965. file-rcvantfile    =
  966. file-staposfile    =
  967. file-geoidfile     =
  968. file-ionofile      =
  969. file-dcbfile       =
  970. file-eopfile       =
  971. file-blqfile       =
  972. file-tempdir       =
  973. file-geexefile     =
  974. file-solstatfile   =
  975. file-tracefile     =
  976. &lt;/code&gt;&lt;/pre&gt;
  977.  
  978. &lt;h2 dir="auto" id="rtkpost-config-for-postprocessing-with-output-to-nmea-file"&gt;rtkpost config for postprocessing with output to NMEA file&lt;/h2&gt;
  979. &lt;pre dir="auto"&gt;&lt;code&gt;# rtkpost options (2025/06/26 06:28:15, v.demo5 b34L)
  980.  
  981. pos1-posmode       =kinematic  # (0:single,1:dgps,2:kinematic,3:static,4:static-start,5:movingbase,6:fixed,7:ppp-kine,8:ppp-static,9:ppp-fixed)
  982. pos1-frequency     =l1+l2+l5+l6 # (1:l1,2:l1+l2,3:l1+l2+l5,4:l1+l2+l5+l6)
  983. pos1-soltype       =combined   # (0:forward,1:backward,2:combined,3:combined-nophasereset)
  984. pos1-elmask        =15         # (deg)
  985. pos1-snrmask_r     =off        # (0:off,1:on)
  986. pos1-snrmask_b     =off        # (0:off,1:on)
  987. pos1-snrmask_L1    =38,38,38,38,38,38,38,38,38
  988. pos1-snrmask_L2    =0,0,0,0,0,0,0,0,0
  989. pos1-snrmask_L5    =0,0,0,0,0,0,0,0,0
  990. pos1-snrmask_L6    =0,0,0,0,0,0,0,0,0
  991. pos1-dynamics      =on         # (0:off,1:on)
  992. pos1-tidecorr      =0          # (1:solid+2:otl+4:spole)
  993. pos1-ionoopt       =brdc       # (0:off,1:brdc,2:sbas,3:dual-freq,4:est-stec,5:ionex-tec,6:qzs-brdc)
  994. pos1-tropopt       =saas       # (0:off,1:saas,2:sbas,3:est-ztd,4:est-ztdgrad)
  995. pos1-sateph        =brdc       # (0:brdc,1:precise,2:brdc+sbas,3:brdc+ssrapc,4:brdc+ssrcom)
  996. pos1-posopt1       =off        # (0:off,1:on)
  997. pos1-posopt2       =off        # (0:off,1:on)
  998. pos1-posopt3       =off        # (0:off,1:on,2:precise)
  999. pos1-posopt4       =off        # (0:off,1:on)
  1000. pos1-posopt5       =off        # (0:off,1:on)
  1001. pos1-posopt6       =off        # (0:off,1:on)
  1002. pos1-exclsats      =           # (prn ...)
  1003. pos1-navsys        =47         # (1:gps+2:sbas+4:glo+8:gal+16:qzs+32:bds+64:navic)
  1004. pos2-armode        =fix-and-hold # (0:off,1:continuous,2:instantaneous,3:fix-and-hold)
  1005. pos2-gloarmode     =fix-and-hold # (0:off,1:on,2:autocal,3:fix-and-hold)
  1006. pos2-bdsarmode     =off        # (0:off,1:on)
  1007. pos2-arfilter      =on         # (0:off,1:on)
  1008. pos2-arthres       =3
  1009. pos2-arthresmin    =3
  1010. pos2-arthresmax    =3
  1011. pos2-arthres1      =0.1
  1012. pos2-arthres2      =0
  1013. pos2-arthres3      =1e-09
  1014. pos2-arthres4      =1e-05
  1015. pos2-varholdamb    =0.1        # (cyc^2)
  1016. pos2-gainholdamb   =0.01
  1017. pos2-arlockcnt     =0
  1018. pos2-minfixsats    =4
  1019. pos2-minholdsats   =5
  1020. pos2-mindropsats   =10
  1021. pos2-arelmask      =15         # (deg)
  1022. pos2-arminfix      =100
  1023. pos2-armaxiter     =1
  1024. pos2-elmaskhold    =15         # (deg)
  1025. pos2-aroutcnt      =20
  1026. pos2-maxage        =30         # (s)
  1027. pos2-syncsol       =off        # (0:off,1:on)
  1028. pos2-slipthres     =0.05       # (m)
  1029. pos2-dopthres      =0          # (m)
  1030. pos2-rejionno      =1          # (m)
  1031. pos2-rejcode       =10         # (m)
  1032. pos2-niter         =1
  1033. pos2-baselen       =0          # (m)
  1034. pos2-basesig       =0          # (m)
  1035. out-solformat      =nmea       # (0:llh,1:xyz,2:enu,3:nmea)
  1036. out-outhead        =on         # (0:off,1:on)
  1037. out-outopt         =on         # (0:off,1:on)
  1038. out-outvel         =on         # (0:off,1:on)
  1039. out-timesys        =gpst       # (0:gpst,1:utc,2:jst)
  1040. out-timeform       =hms        # (0:tow,1:hms)
  1041. out-timendec       =3
  1042. out-degform        =deg        # (0:deg,1:dms)
  1043. out-fieldsep       =
  1044. out-outsingle      =on         # (0:off,1:on)
  1045. out-maxsolstd      =0          # (m)
  1046. out-height         =geodetic   # (0:ellipsoidal,1:geodetic)
  1047. out-geoid          =internal   # (0:internal,1:egm96,2:egm08_2.5,3:egm08_1,4:gsi2000)
  1048. out-solstatic      =all        # (0:all,1:single)
  1049. out-nmeaintv1      =0          # (s)
  1050. out-nmeaintv2      =0          # (s)
  1051. out-outstat        =state      # (0:off,1:state,2:residual)
  1052. stats-eratio1      =300
  1053. stats-eratio2      =300
  1054. stats-eratio5      =300
  1055. stats-eratio6      =300
  1056. stats-errphase     =0.003      # (m)
  1057. stats-errphaseel   =0.003      # (m)
  1058. stats-errphasebl   =0          # (m/10km)
  1059. stats-errdoppler   =1          # (Hz)
  1060. stats-snrmax       =52         # (dB.Hz)
  1061. stats-errsnr       =0          # (m)
  1062. stats-errrcv       =0          # ( )
  1063. stats-stdbias      =30         # (m)
  1064. stats-stdiono      =0.03       # (m)
  1065. stats-stdtrop      =0.3        # (m)
  1066. stats-prnaccelh    =3          # (m/s^2)
  1067. stats-prnaccelv    =1          # (m/s^2)
  1068. stats-prnbias      =0.0001     # (m)
  1069. stats-prniono      =0.001      # (m)
  1070. stats-prntrop      =0.0001     # (m)
  1071. stats-prnpos       =0          # (m)
  1072. stats-clkstab      =5e-12      # (s/s)
  1073. ant1-postype       =llh        # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm,6:raw)
  1074. ant1-pos1          =0          # (deg|m)
  1075. ant1-pos2          =0          # (deg|m)
  1076. ant1-pos3          =0          # (m|m)
  1077. ant1-anttype       =
  1078. ant1-antdele       =0          # (m)
  1079. ant1-antdeln       =0          # (m)
  1080. ant1-antdelu       =0          # (m)
  1081. ant2-postype       =single     # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm,6:raw)
  1082. ant2-pos1          =0          # (deg|m)
  1083. ant2-pos2          =0          # (deg|m)
  1084. ant2-pos3          =0          # (m|m)
  1085. ant2-anttype       =
  1086. ant2-antdele       =0          # (m)
  1087. ant2-antdeln       =0          # (m)
  1088. ant2-antdelu       =0          # (m)
  1089. ant2-maxaveep      =1
  1090. ant2-initrst       =on         # (0:off,1:on)
  1091. misc-timeinterp    =off        # (0:off,1:on)
  1092. misc-sbasatsel     =0          # (0:all)
  1093. misc-rnxopt1       =
  1094. misc-rnxopt2       =-EPHALL
  1095. misc-pppopt        =
  1096. file-satantfile    =
  1097. file-rcvantfile    =
  1098. file-staposfile    =
  1099. file-geoidfile     =
  1100. file-ionofile      =
  1101. file-dcbfile       =
  1102. file-eopfile       =
  1103. file-blqfile       =
  1104. file-tempdir       =
  1105. file-geexefile     =
  1106. file-solstatfile   =
  1107. file-tracefile     =
  1108. &lt;/code&gt;&lt;/pre&gt;
  1109.  
  1110. &lt;h2 dir="auto" id="using-rtkpost"&gt;Using rtkpost&lt;/h2&gt;
  1111. &lt;p dir="auto"&gt;Simply select .obs and .nav data provided by your rover (generated using convbin above) and .obs data from your base (also generated using convbin above).&lt;/p&gt;
  1112.  
  1113. &lt;h1 dir="auto" id="next-steps"&gt;Next steps&lt;/h1&gt;
  1114. &lt;ul dir="auto"&gt;
  1115.  &lt;li&gt;figure out if “CONFIG ALLEPHRTCM ENABLE” option has any impact&lt;/li&gt;
  1116.  &lt;li&gt;explore if GPS/GNSS ephemeris can be used with RANGEB undocumented option&lt;/li&gt;
  1117.  &lt;li&gt;update RTKGPS+ to demo5_b34L&lt;/li&gt;
  1118.  &lt;li&gt;figure out if SW Maps can be used to feed RTCM3 data from base to feed the UM980 to compute RTK on the module in real time&lt;/li&gt;
  1119. &lt;/ul&gt;
  1120. </description>
  1121.      <dc:creator>hopet</dc:creator>
  1122.      <pubDate>Thu, 26 Jun 2025 08:24:15 +0000</pubDate>
  1123.      <comments>https://www.openstreetmap.org/user/hopet/diary/406985#comments</comments>
  1124.    </item>
  1125.    <item>
  1126.      <title>What food is there - and can I get a wheelchair in?</title>
  1127.      <link>https://www.openstreetmap.org/user/SomeoneElse/diary/406982</link>
  1128.      <guid>https://www.openstreetmap.org/user/SomeoneElse/diary/406982</guid>
  1129.      <description>&lt;p dir="auto"&gt;I recently updated &lt;a href="https://map.atownsend.org.uk/maps/map/map.html#20/51.51012/-0.12892" rel="nofollow noopener noreferrer"&gt;this map&lt;/a&gt;:&lt;/p&gt;
  1130.  
  1131. &lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20250624_205644.png" alt="Some restaurants in London (raster)" loading="lazy"&gt;&lt;/p&gt;
  1132.  
  1133. &lt;p dir="auto"&gt;and &lt;a href="https://map.atownsend.org.uk/vector/index.html#19/51.51013/-0.12889" rel="nofollow noopener noreferrer"&gt;this one&lt;/a&gt;:&lt;/p&gt;
  1134.  
  1135. &lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20250624_205807.png" alt="Some restaurants in London (vector)" loading="lazy"&gt;&lt;/p&gt;
  1136.  
  1137. &lt;p dir="auto"&gt;to show different types of restaurants (the most common cuisine types cause the top part of the icon to be modified), just like that map has shown fast food for some time now.  However, it’s not technically difficult to also show what wheelchair access is available - &lt;a href="https://www.openstreetmap.org/node/6173754810" rel="nofollow noopener noreferrer"&gt;this one&lt;/a&gt;:&lt;/p&gt;
  1138.  
  1139. &lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20250624_210325.png" alt="A restaurant icon with a pizza slice above (Italian) and a yellow flash below (limited wheelchair)" loading="lazy"&gt;&lt;/p&gt;
  1140.  
  1141. &lt;p dir="auto"&gt;is an Italian restaurant with limited wheelchair access.  The yellow flash for that is deliberately small so as to not dominate the view, but visible if you are looking for it.&lt;/p&gt;
  1142.  
  1143. &lt;p dir="auto"&gt;Shouldn’t showing that information be “table stakes” for maps showing OSM data?&lt;/p&gt;
  1144. </description>
  1145.      <dc:creator>SomeoneElse</dc:creator>
  1146.      <pubDate>Tue, 24 Jun 2025 20:09:34 +0000</pubDate>
  1147.      <comments>https://www.openstreetmap.org/user/SomeoneElse/diary/406982#comments</comments>
  1148.      <geo:lat>51.510003</geo:lat>
  1149.      <geo:long>-0.128226</geo:long>
  1150.      <georss:point>51.510003 -0.128226</georss:point>
  1151.    </item>
  1152.    <item>
  1153.      <title>My MapRoulette presentation at SOTM US</title>
  1154.      <link>https://www.openstreetmap.org/user/mvexel/diary/406980</link>
  1155.      <guid>https://www.openstreetmap.org/user/mvexel/diary/406980</guid>
  1156.      <description>&lt;p dir="auto"&gt;I had a fantastic time at SOTM US. Thanks to all at OSM US for their work putting the event together.&lt;/p&gt;
  1157.  
  1158. &lt;p dir="auto"&gt;I gave two presentations, one on MapRoulette and one on the new Meet Your Mappers tool. I posted annotated slides for the MapRoulette talk &lt;a href="https://mvexel.prose.sh/20250623-maproulette-sotmus-2025" rel="nofollow noopener noreferrer"&gt;on my blog&lt;/a&gt;.&lt;/p&gt;
  1159. </description>
  1160.      <dc:creator>mvexel</dc:creator>
  1161.      <pubDate>Tue, 24 Jun 2025 16:43:50 +0000</pubDate>
  1162.      <comments>https://www.openstreetmap.org/user/mvexel/diary/406980#comments</comments>
  1163.    </item>
  1164.    <item>
  1165.      <title>On Overture's Avoidance of the ODbL</title>
  1166.      <link>https://www.openstreetmap.org/user/jacobwhall/diary/406979</link>
  1167.      <guid>https://www.openstreetmap.org/user/jacobwhall/diary/406979</guid>
  1168.      <description>&lt;p dir="auto"&gt;Dear Overture Team and OpenStreetMap Community,&lt;/p&gt;
  1169.  
  1170. &lt;p dir="auto"&gt;This diary entry is a follow-up to an in-person conversation I had with some of the Overture team at State of the Map U.S. To their credit, they were quick to admit to and apologize for some of these omissions and verbally committed to making appropriate changes. I am therefore posting this entry for the following reasons:&lt;/p&gt;
  1171.  
  1172. &lt;ul dir="auto"&gt;
  1173.  &lt;li&gt;to fully document my concerns,&lt;/li&gt;
  1174.  &lt;li&gt;to invite others to (respectfully please!) share their perspectives,&lt;/li&gt;
  1175.  &lt;li&gt;to hold the Overture team accountable for making these changes.&lt;/li&gt;
  1176. &lt;/ul&gt;
  1177.  
  1178. &lt;h2 dir="auto" id="clarity-on-attribution-page"&gt;Clarity on Attribution Page&lt;/h2&gt;
  1179.  
  1180. &lt;p dir="auto"&gt;In my opinion, Overture does not take care to spell out the necessity of OpenStreetMap attribution on their &lt;a href="https://docs.overturemaps.org/attribution/" rel="nofollow noopener noreferrer"&gt;Attribution and Licensing&lt;/a&gt; page. After an optional citation comes the following language:&lt;/p&gt;
  1181.  
  1182. &lt;blockquote&gt;
  1183.  &lt;p dir="auto"&gt;The Overture Maps Foundation does not require text attribution or an OMF logo on maps, visualizations, and graphics created with our datasets. If you would like to credit Overture, we suggest: &lt;code dir="auto"&gt;© Overture Maps Foundation&lt;/code&gt;.&lt;/p&gt;
  1184. &lt;/blockquote&gt;
  1185.  
  1186. &lt;p dir="auto"&gt;So far it seems pretty easy to use Overture data. We can attribute…but only if we want. Easy peasy! After that, the potential for additional attribution requirements is raised:&lt;/p&gt;
  1187.  
  1188. &lt;blockquote&gt;
  1189.  &lt;p dir="auto"&gt;Some of the data sources we use in Overture datasets do require their own attribution, according to their licenses. For example, our Explore tool displays several Overture datasets that are made wholly or in part from OpenStreetMap data, so we added the following line of attribution to adhere to the requirements of the &lt;a href="https://opendatacommons.org/licenses/odbl/" rel="nofollow noopener noreferrer"&gt;Open Database License&lt;/a&gt;: &lt;code dir="auto"&gt;© OpenStreetMap contributors, Overture Maps Foundation&lt;/code&gt;.&lt;/p&gt;
  1190. &lt;/blockquote&gt;
  1191.  
  1192. &lt;p dir="auto"&gt;Let’s take a close look at this paragraph. In Overture’s only mention of OpenStreetMap attribution requirements (that I could find), they frame it as a passing example. It’s as if the OpenStreetMap community should feel lucky that Overture chose us as their example of potential attribution requirements. To me, this deflection of our dataset’s license comes across as deeply disrespectful.&lt;/p&gt;
  1193.  
  1194. &lt;p dir="auto"&gt;So, how much of Overture is derived from OpenStreetMap data? Clicking into each of the dataset descriptions, &lt;em&gt;four out of the six&lt;/em&gt; datasets are derived from OpenStreetMap and therefore distributed under the ODbL: “Base,” “Buildings,” “Divisions,” and “Transportation.”&lt;/p&gt;
  1195.  
  1196. &lt;p dir="auto"&gt;With that in mind, Overture seems better-described as an OpenStreetMap distribution with some extra data tacked on. Great, ODbL needs to be front-and-center on their &lt;a href="https://overturemaps.org/download/" rel="nofollow noopener noreferrer"&gt;download page&lt;/a&gt;, release pages, and &lt;a href="https://docs.overturemaps.org/attribution/" rel="nofollow noopener noreferrer"&gt;Attribution page&lt;/a&gt;, with a link to the &lt;a href="https://osmfoundation.org/wiki/Licence/Attribution_Guidelines" rel="nofollow noopener noreferrer"&gt;official OpenStreetMap Attribution Guidelines&lt;/a&gt;. Overture has a responsibility to ensure its data consumers correctly attribute OpenStreetMap Contributors, and understand the legal liability they open themselves up to if they do not properly attribute. Beyond legal requirements, attribution is the respectful thing for hard-working OpenStreetMap volunteers whose work gets used in a commercial context.&lt;/p&gt;
  1197.  
  1198. &lt;h2 dir="auto" id="the-faq-page"&gt;The FAQ Page&lt;/h2&gt;
  1199.  
  1200. &lt;p dir="auto"&gt;The further we get from Overture’s attribution page, the worse things get. On the FAQs page, under “How Is Overture Data Licensed?” lies the following text (pasted in full):&lt;/p&gt;
  1201.  
  1202. &lt;blockquote&gt;
  1203.  &lt;p dir="auto"&gt;Generally, &lt;a href="https://docs.overturemaps.org/attribution/" rel="nofollow noopener noreferrer"&gt;Overture data is licensed&lt;/a&gt; under the Community Database License Agreement – Permissive v2 (CDLA) unless derived from a source that requires publishing under a different license, such as data derived from OpenStreetMap, that constitutes a “Derivative Database” (as defined under ODbL v1.0), which will be licensed under ODbL v1.0.&lt;/p&gt;
  1204. &lt;/blockquote&gt;
  1205.  
  1206. &lt;blockquote&gt;
  1207.  &lt;p dir="auto"&gt;Overture considers (A) any maps or outcomes obtained by computational analysis that are created using Overture data licensed under CDLA Permissive v 2.0, or (B) the supplementing of (1) a Data Recipient’s content or (2) a third-party’s data – in either case, obtained through computational analysis – with CDLA Permissive v.2-licensed data from Overture, to be “Results” and according to Section 3, not subject to the requirement to provide the text of the license.&lt;/p&gt;
  1208. &lt;/blockquote&gt;
  1209.  
  1210. &lt;p dir="auto"&gt;This seems to be purposefully misleading. As stated above, &lt;em&gt;four out of six&lt;/em&gt; of Overture’s datasets are distributed under the ODbL, so saying Overture is “generally” CDLA is untrue. Perhaps Overture wishes to have more CDLA datasets in the future?&lt;/p&gt;
  1211.  
  1212. &lt;p dir="auto"&gt;Secondly, this FAQ fully omits the need for attribution to OpenStreetMap, which is required for the majority of Overture datasets. Surely that is worthy of inclusion on your FAQ page.&lt;/p&gt;
  1213.  
  1214. &lt;h2 dir="auto" id="elsewhere-on-the-overture-site"&gt;Elsewhere on the Overture Site&lt;/h2&gt;
  1215.  
  1216. &lt;p dir="auto"&gt;The &lt;a href="https://overturemaps.org/" rel="nofollow noopener noreferrer"&gt;Overture homepage&lt;/a&gt; makes no mention of OpenStreetMap, one of their primary data sources. The two featured links at the top of its page, &lt;a href="https://docs.overturemaps.org/getting-data/" rel="nofollow noopener noreferrer"&gt;“Getting Started”&lt;/a&gt; and &lt;a href="https://overturemaps.org/about/who-we-are/" rel="nofollow noopener noreferrer"&gt;“Learn More”&lt;/a&gt; point to pages that also make no mention of OpenStreetMap.&lt;/p&gt;
  1217.  
  1218. &lt;p dir="auto"&gt;On the aforementioned &lt;a href="https://docs.overturemaps.org/getting-data/" rel="nofollow noopener noreferrer"&gt;“Getting Started”&lt;/a&gt; page, there are many download links provided to OpenStreetMap-derived datasets, without any mention of the ODbL. That page links to &lt;a href="https://docs.overturemaps.org/getting-data/overturemaps-py/" rel="nofollow noopener noreferrer"&gt;this one&lt;/a&gt; about the Python CLI, which features a one-liner for downloading the Overture “Buildings” dataset (which includes OpenStreetMap data) without one word about attribution requirements. Not only is this disrespectful to the OSM community, but it’s dangerous to your users who need to understand what the terms of that data use are.&lt;/p&gt;
  1219.  
  1220. &lt;p dir="auto"&gt;The “Learn More” page includes this gem from Executive Director Marc Prioleau:&lt;/p&gt;
  1221.  
  1222. &lt;blockquote&gt;
  1223.  &lt;p dir="auto"&gt;With the collective insights of our expanding community, it’s not just about amassing datasets. Instead, it’s a conscious effort to lay the groundwork for a future where map data remains current and interoperable, serving a wide range of applications. Overture is about harnessing available high-quality data sources and building bridges of cooperation.&lt;/p&gt;
  1224. &lt;/blockquote&gt;
  1225.  
  1226. &lt;p dir="auto"&gt;At least we could properly attribute those bridges, eh Marc?&lt;/p&gt;
  1227.  
  1228. &lt;h2 dir="auto" id="final-thoughts"&gt;Final Thoughts&lt;/h2&gt;
  1229.  
  1230. &lt;p dir="auto"&gt;I really like Overture’s work. They offer clean extracts of geospatial data from OpenStreetMap and other data sources, with end-users in mind. They help bridge the gap between OSM tagging madness and company X’s need for a clean map.&lt;/p&gt;
  1231.  
  1232. &lt;p dir="auto"&gt;I want to believe that Overture cares about the OpenStreetMap community and wishes to grow with us. I met a couple of them at State of the Map U.S. and they were friendly. They helped fund the event, and expressed genuine, positive sentiment about the community who makes their work possible. Indeed, most of their datasets rely on our data.&lt;/p&gt;
  1233.  
  1234. &lt;p dir="auto"&gt;I am concerned by Overture’s willingness to gloss over OpenStreetMap and the ODbL on their website. Overture enjoys ample funding from their corporate partners, and has a responsibility to pass some of that success on to the sources they rely on, including OpenStreetMap. I worry that when Overture is not attending SOTMUS, they might be forgetting to mention where their data comes from to all those &lt;a href="https://overturemaps.org/become-a-member/" rel="nofollow noopener noreferrer"&gt;$3M/yr members&lt;/a&gt;.&lt;/p&gt;
  1235.  
  1236. &lt;p dir="auto"&gt;Overture, fix your website. Show some real enthusiasm about our community in your marketing materials. Help sustainably fund-raise for the institutions you rely on. Do the work to build those bridges you claim to build.
  1237. &lt;br&gt;&lt;br&gt;&lt;br&gt;
  1238. Best Regards,&lt;br&gt;
  1239. Jacob Hall&lt;/p&gt;
  1240. </description>
  1241.      <dc:creator>jacobwhall</dc:creator>
  1242.      <pubDate>Mon, 23 Jun 2025 15:52:01 +0000</pubDate>
  1243.      <comments>https://www.openstreetmap.org/user/jacobwhall/diary/406979#comments</comments>
  1244.    </item>
  1245.  </channel>
  1246. </rss>
  1247.  

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