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>작업 중 참고할 태그 목록</title>
  16.      <link>https://www.openstreetmap.org/user/aaei924/diary/407041</link>
  17.      <guid>https://www.openstreetmap.org/user/aaei924/diary/407041</guid>
  18.      <description>&lt;p dir="auto"&gt;개인적으로 참고하기 위해 작성한 항목입니다. (수시 업데이트)&lt;/p&gt;
  19.  
  20. &lt;h2 dir="auto" id="section"&gt;도로&lt;/h2&gt;
  21. &lt;ul dir="auto"&gt;
  22.  &lt;li&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/Ko:Relation:enforcement" rel="nofollow noopener noreferrer"&gt;enforcement 관계&lt;/a&gt;: 교통법규 단속 장비&lt;/li&gt;
  23.  &lt;li&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/Key:change" rel="nofollow noopener noreferrer"&gt;change 키&lt;/a&gt;: 차로 변경 가능 여부&lt;/li&gt;
  24.  &lt;li&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/Key:expressway" rel="nofollow noopener noreferrer"&gt;expressway 키&lt;/a&gt;: 고속화도로 여부&lt;/li&gt;
  25.  &lt;li&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/Key:motorroad" rel="nofollow noopener noreferrer"&gt;motorroad 키&lt;/a&gt;: 자동차전용도로 여부&lt;/li&gt;
  26. &lt;/ul&gt;
  27. </description>
  28.      <dc:creator>aaei924</dc:creator>
  29.      <pubDate>Mon, 07 Jul 2025 07:38:32 +0000</pubDate>
  30.      <comments>https://www.openstreetmap.org/user/aaei924/diary/407041#comments</comments>
  31.    </item>
  32.    <item>
  33.      <title>WORKSHOP MPCS 2025 OPEN FOR FREE REGISTRATION</title>
  34.      <link>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407039</link>
  35.      <guid>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407039</guid>
  36.      <description>&lt;h4 dir="auto" id="free-and-open-registration-for-the-iii-workshop-on-participatory-mapping-and-social-cartography---mpcs-2025"&gt;FREE AND OPEN REGISTRATION FOR THE III WORKSHOP ON PARTICIPATORY MAPPING AND SOCIAL CARTOGRAPHY - MPCS 2025&lt;/h4&gt;
  37.  
  38. &lt;hr&gt;
  39.  
  40. &lt;p dir="auto"&gt;— &lt;a href="https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407038" rel="nofollow noopener noreferrer"&gt;Ler em Português&lt;/a&gt;&lt;/p&gt;
  41.  
  42. &lt;h5 dir="auto" id="you-can-now-register-for-the-collective-mapping-event-of-2025-thank-you-to-everyone-who-sent-their-contributions"&gt;You can now register for the collective mapping event of 2025. Thank you to everyone who sent their contributions!&lt;/h5&gt;
  43.  
  44. &lt;h5 dir="auto" id="well-see-you-in-august-at-the-event-which-is-100-online-and-completely-open-to-the-public-registration-at"&gt;We’ll see you in August at the event, which is 100% online and completely open to the public. Registration at:&lt;/h5&gt;
  45.  
  46. &lt;h5 dir="auto" id="httpsividesorgworkshopmpcs2025httpsividesorgworkshopmpcs2025"&gt;&lt;a href="https://ivides.org/workshopmpcs2025" dir="auto" rel="nofollow noopener noreferrer"&gt;https://ivides.org/workshopmpcs2025&lt;/a&gt;&lt;/h5&gt;
  47.  
  48. &lt;p dir="auto"&gt;The actual event numbers are:&lt;/p&gt;
  49.  
  50. &lt;ul dir="auto"&gt;
  51.  &lt;li&gt;133 speakers&lt;/li&gt;
  52.  &lt;li&gt;36 Projects in the Mapping Exhibition&lt;/li&gt;
  53.  &lt;li&gt;20 book chapter presentations&lt;/li&gt;
  54.  &lt;li&gt;9 Special Keynotes with invited experts&lt;/li&gt;
  55.  &lt;li&gt;1 OpenStreetMap training session + 01 Mapathon&lt;/li&gt;
  56.  &lt;li&gt;1 book release [90 authors and 20 chapters]&lt;/li&gt;
  57. &lt;/ul&gt;
  58.  
  59. &lt;p dir="auto"&gt;To keep contact: &lt;a href="mailto:ivides@ivides.org" rel="nofollow noopener noreferrer" dir="auto"&gt;ivides@ivides.org&lt;/a&gt;&lt;/p&gt;
  60.  
  61. &lt;hr&gt;
  62.  
  63. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/07/divulga_numeros_MPCS2025.png" alt="event divulgation" loading="lazy"&gt;&lt;/p&gt;
  64.  
  65. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2023/09/logo_ivides_reg_md-300x263.png" alt="IVIDES_logo" loading="lazy"&gt;&lt;/p&gt;
  66.  
  67. </description>
  68.      <dc:creator>Raquel Dezidério Souto</dc:creator>
  69.      <pubDate>Sun, 06 Jul 2025 23:30:50 +0000</pubDate>
  70.      <comments>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407039#comments</comments>
  71.    </item>
  72.    <item>
  73.      <title>INSCRIÇÕES ABERTAS PARA O WORKSHOP MPCS 2025</title>
  74.      <link>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407038</link>
  75.      <guid>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407038</guid>
  76.      <description>&lt;h3 dir="auto" id="inscries-livres-e-abertas-para-o-iii-workshop-mapeamento-participativo-e-cartografia-social---mpcs-2025"&gt;INSCRIÇÕES LIVRES E ABERTAS PARA O III WORKSHOP MAPEAMENTO PARTICIPATIVO E CARTOGRAFIA SOCIAL - MPCS 2025&lt;/h3&gt;
  77.  
  78. &lt;hr&gt;
  79.  
  80. &lt;p dir="auto"&gt;— &lt;a href="https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407039" rel="nofollow noopener noreferrer"&gt;Read in English&lt;/a&gt;&lt;/p&gt;
  81.  
  82. &lt;h5 dir="auto" id="voc-j-pode-se-inscrever-para-o-maior-evento-de-mapeamento-coletivo-de-2025-agradecemos-a-participao-de-todos-que-enviaram-as-suas-contribuies"&gt;Você já pode se inscrever para o maior evento de mapeamento coletivo de 2025. Agradecemos a participação de todos que enviaram as suas contribuições!&lt;/h5&gt;
  83.  
  84. &lt;h5 dir="auto" id="nos-veremos-em-agosto-no-evento-100-online-e-completamente-aberto-ao-pblico-inscries-em"&gt;Nos veremos em agosto, no evento 100% online e completamente aberto ao público. Inscrições em:&lt;/h5&gt;
  85.  
  86. &lt;h5 dir="auto" id="httpsividesorgworkshopmpcs2025httpsividesorgworkshopmpcs2025"&gt;&lt;a href="https://ivides.org/workshopmpcs2025" dir="auto" rel="nofollow noopener noreferrer"&gt;https://ivides.org/workshopmpcs2025&lt;/a&gt;&lt;/h5&gt;
  87.  
  88. &lt;p dir="auto"&gt;Números do evento até o momento:&lt;/p&gt;
  89.  
  90. &lt;ul dir="auto"&gt;
  91.  &lt;li&gt;133 palestrantes&lt;/li&gt;
  92.  &lt;li&gt;36 Projetos na Mostra de mapeamento&lt;/li&gt;
  93.  &lt;li&gt;20 Apresentações de capítulos do livro&lt;/li&gt;
  94.  &lt;li&gt;9 Palestras especiais com especialistas convidados&lt;/li&gt;
  95.  &lt;li&gt;1 Oficina de OpenStreetMap + 01 Mapatona&lt;/li&gt;
  96.  &lt;li&gt;1 Lançamento de livro [90 autores(a) e 20 capítulos]&lt;/li&gt;
  97. &lt;/ul&gt;
  98.  
  99. &lt;hr&gt;
  100.  
  101. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2025/07/divulga_numeros_MPCS2025.png" alt="evento divulgacao" loading="lazy"&gt;&lt;/p&gt;
  102.  
  103. &lt;p dir="auto"&gt;&lt;img src="https://ivides.org/wp-content/uploads/2023/09/logo_ivides_reg_md-300x263.png" alt="IVIDES_logo" loading="lazy"&gt;&lt;/p&gt;
  104.  
  105. </description>
  106.      <dc:creator>Raquel Dezidério Souto</dc:creator>
  107.      <pubDate>Sun, 06 Jul 2025 23:30:00 +0000</pubDate>
  108.      <comments>https://www.openstreetmap.org/user/Raquel%20Dezid%C3%A9rio%20Souto/diary/407038#comments</comments>
  109.    </item>
  110.    <item>
  111.      <title>Cập nhật hành chính tỉnh Cao Bằng (Việt Nam): Quá trình sáp nhập từ 2000 đến 2025/Administrative update of Cao Bang Province (Vietnam): Mergers from 2000 to 2025</title>
  112.      <link>https://www.openstreetmap.org/user/Ducminhduongcb/diary/407036</link>
  113.      <guid>https://www.openstreetmap.org/user/Ducminhduongcb/diary/407036</guid>
  114.      <description>&lt;p dir="auto"&gt;Tôi vừa hoàn thành một đợt cập nhật dữ liệu hành chính tỉnh Cao Bằng trên bản đồ OSM, dựa theo các nghị quyết chính thức của Quốc hội Việt Nam về việc sắp xếp lại các đơn vị hành chính cấp huyện và xã trong giai đoạn hiện đại.&lt;/p&gt;
  115.  
  116. &lt;p dir="auto"&gt;🗂️ Tổng hợp quá trình sáp nhập:
  117. 2000–2019:&lt;/p&gt;
  118.  
  119. &lt;p dir="auto"&gt;Tỉnh Cao Bằng duy trì 13 huyện và ~199 xã/phường/thị trấn.&lt;/p&gt;
  120.  
  121. &lt;p dir="auto"&gt;Không có thay đổi lớn, chỉ có điều chỉnh nhỏ về địa giới hành chính, tên gọi.&lt;/p&gt;
  122.  
  123. &lt;p dir="auto"&gt;2020:&lt;/p&gt;
  124.  
  125. &lt;p dir="auto"&gt;Theo Nghị quyết 864/NQ-UBTVQH14 (10/01/2020):&lt;/p&gt;
  126.  
  127. &lt;p dir="auto"&gt;Sáp nhập huyện Thông Nông vào huyện Hà Quảng&lt;/p&gt;
  128.  
  129. &lt;p dir="auto"&gt;Giảm 38 xã, từ 199 còn 161 xã/phường/thị trấn&lt;/p&gt;
  130.  
  131. &lt;p dir="auto"&gt;2025:&lt;/p&gt;
  132.  
  133. &lt;p dir="auto"&gt;Theo Nghị quyết 1657/NQ-UBTVQH15 (16/06/2025) và Đề án 383/ĐA-CP (09/05/2025):&lt;/p&gt;
  134.  
  135. &lt;p dir="auto"&gt;Tỉnh giảm còn 56 xã/phường (53 xã + 3 phường)&lt;/p&gt;
  136.  
  137. &lt;p dir="auto"&gt;Các phường mới của TP Cao Bằng:&lt;/p&gt;
  138.  
  139. &lt;p dir="auto"&gt;Thục Phán (gồm: Sông Hiến, Hợp Giang, Đề Thám, Hưng Đạo, Hoàng Tung)&lt;/p&gt;
  140.  
  141. &lt;p dir="auto"&gt;Nùng Trí Cao (gồm: Ngọc Xuân, Vĩnh Quang, Sông Bằng)&lt;/p&gt;
  142.  
  143. &lt;p dir="auto"&gt;Tân Giang (gồm: Tân Giang, Duyệt Trung, Hòa Chung, Chu Trinh, Lê Chung)&lt;/p&gt;
  144.  
  145. &lt;p dir="auto"&gt;Nhiều xã mới được thành lập như: Quang Long, Nam Quang, Hưng Đạo, Yên Thổ, Sơn Lộ…&lt;/p&gt;
  146.  
  147. &lt;p dir="auto"&gt;Từ 01/07/2025, mô hình chính quyền 2 cấp (tỉnh → xã/phường) chính thức áp dụng tại Cao Bằng.&lt;/p&gt;
  148.  
  149. &lt;p dir="auto"&gt;Just completed an update of administrative boundaries for Cao Bang Province (Vietnam) in OpenStreetMap, based on official government resolutions about merging lower-level administrative units.&lt;/p&gt;
  150.  
  151. &lt;p dir="auto"&gt;🗂️ Summary of the process:
  152. 2000–2019:&lt;/p&gt;
  153.  
  154. &lt;p dir="auto"&gt;The province had 13 districts and ~199 communes/wards/townlets.&lt;/p&gt;
  155.  
  156. &lt;p dir="auto"&gt;No major changes, only minor adjustments.&lt;/p&gt;
  157.  
  158. &lt;p dir="auto"&gt;2020:&lt;/p&gt;
  159.  
  160. &lt;p dir="auto"&gt;Under Resolution 864/NQ-UBTVQH14 (Jan 10, 2020):&lt;/p&gt;
  161.  
  162. &lt;p dir="auto"&gt;Thong Nong District merged into Ha Quang District&lt;/p&gt;
  163.  
  164. &lt;p dir="auto"&gt;Number of communes reduced from 199 to 161&lt;/p&gt;
  165.  
  166. &lt;p dir="auto"&gt;2025:&lt;/p&gt;
  167.  
  168. &lt;p dir="auto"&gt;Under Resolution 1657/NQ-UBTVQH15 (June 16, 2025) and Plan 383/DA-CP (May 9, 2025):&lt;/p&gt;
  169.  
  170. &lt;p dir="auto"&gt;Province reorganized to just 56 communes/wards (53 communes + 3 wards)&lt;/p&gt;
  171.  
  172. &lt;p dir="auto"&gt;New wards of Cao Bang City:&lt;/p&gt;
  173.  
  174. &lt;p dir="auto"&gt;Thuc Phan (from Song Hien, Hop Giang, De Tham, Hung Dao, Hoang Tung)&lt;/p&gt;
  175.  
  176. &lt;p dir="auto"&gt;Nung Tri Cao (from Ngoc Xuan, Vinh Quang, Song Bang)&lt;/p&gt;
  177.  
  178. &lt;p dir="auto"&gt;Tan Giang (from Tan Giang, Duyet Trung, Hoa Chung, Chu Trinh, Le Chung)&lt;/p&gt;
  179.  
  180. &lt;p dir="auto"&gt;New communes formed: Quang Long, Nam Quang, Hung Dao, Yen Tho, Son Lo, etc.&lt;/p&gt;
  181.  
  182. &lt;p dir="auto"&gt;From July 1st, 2025, Cao Bang implements a 2-tier government model: province → commune/ward (no urban district level in the capital).&lt;/p&gt;
  183.  
  184. &lt;p dir="auto"&gt;🔗 Nguồn / Sources:
  185. Nghị quyết 864/NQ-UBTVQH14 – 2020&lt;/p&gt;
  186.  
  187. &lt;p dir="auto"&gt;Nghị quyết 1657/NQ-UBTVQH15 – 2025&lt;/p&gt;
  188.  
  189. &lt;p dir="auto"&gt;Lễ công bố tại Cao Bằng – Nhân Dân 30/6/2025&lt;/p&gt;
  190. </description>
  191.      <dc:creator>Ducminhduongcb</dc:creator>
  192.      <pubDate>Sun, 06 Jul 2025 15:03:54 +0000</pubDate>
  193.      <comments>https://www.openstreetmap.org/user/Ducminhduongcb/diary/407036#comments</comments>
  194.      <geo:lat>22.66249459833735</geo:lat>
  195.      <geo:long>106.26386806368828</geo:long>
  196.      <georss:point>22.66249459833735 106.26386806368828</georss:point>
  197.    </item>
  198.    <item>
  199.      <title>그</title>
  200.      <link>https://www.openstreetmap.org/user/RealKorean_2828/diary/407035</link>
  201.      <guid>https://www.openstreetmap.org/user/RealKorean_2828/diary/407035</guid>
  202.      <description>&lt;p dir="auto"&gt;OSM모임이나 협회 같은거 우리나라에도 있으면 좋겠다 바로 옆나라 일본도 있던데&lt;/p&gt;
  203. </description>
  204.      <dc:creator>RealKorean_2828</dc:creator>
  205.      <pubDate>Sun, 06 Jul 2025 08:58:54 +0000</pubDate>
  206.      <comments>https://www.openstreetmap.org/user/RealKorean_2828/diary/407035#comments</comments>
  207.    </item>
  208.    <item>
  209.      <title>Micromapping Latrobe Valley</title>
  210.      <link>https://www.openstreetmap.org/user/gipps75/diary/407034</link>
  211.      <guid>https://www.openstreetmap.org/user/gipps75/diary/407034</guid>
  212.      <description>&lt;h1 dir="auto" id="newborough-has-been-fully-micromapped-that-includes-powerlines-street-lights-street-trees-and-underground-fire-hydrants-roads-have-been-edited-and-instead-of-basic-lines-they-now-follow-the-center-point-of-the-road-perfectly"&gt;Newborough has been fully micromapped, that includes: powerlines, street lights, street trees and underground fire hydrants. Roads have been edited and instead of basic lines, they now follow the center point of the road perfectly.&lt;/h1&gt;
  213. </description>
  214.      <dc:creator>gipps75</dc:creator>
  215.      <pubDate>Sun, 06 Jul 2025 01:00:03 +0000</pubDate>
  216.      <comments>https://www.openstreetmap.org/user/gipps75/diary/407034#comments</comments>
  217.      <geo:lat>-38.18505225452746</geo:lat>
  218.      <geo:long>146.29046648740768</geo:long>
  219.      <georss:point>-38.18505225452746 146.29046648740768</georss:point>
  220.    </item>
  221.    <item>
  222.      <title>Grünpfeil für Radfahrer: Geeignete Orte finden</title>
  223.      <link>https://www.openstreetmap.org/user/Discostu36/diary/407033</link>
  224.      <guid>https://www.openstreetmap.org/user/Discostu36/diary/407033</guid>
  225.      <description>&lt;p dir="auto"&gt;Seit dem Frühjahr 2020 gibt es in Deutschland ein neues Verkehrszeichen: den &lt;a href="https://www.stvo2go.de/gruenpfeil-radverkehr/" rel="nofollow noopener noreferrer"&gt;Grünpfeil nur für Radfahrende&lt;/a&gt;. Es erlaubt Radfahrenden, auch bei roter Ampel nach rechts abzubiegen. Ich habe mich gefragt, ob ich mit Hilfe von OpenStreetMap automatisch Stellen raussuchen kann, bei denen die Aufstellung so eines Zeichens sinnvoll wäre.&lt;/p&gt;
  226.  
  227. &lt;h3 dir="auto" id="wo-sind-solche-zeichen-sinnvoll"&gt;Wo sind solche Zeichen sinnvoll?&lt;/h3&gt;
  228.  
  229. &lt;p dir="auto"&gt;Wenn ich meine persönliche Erfahrung und die gesetzlichen Vorgaben (&lt;a href="https://www.gesetze-im-internet.de/stvo_2013/__37.html" rel="nofollow noopener noreferrer"&gt;StVO&lt;/a&gt;, &lt;a href="https://www.verwaltungsvorschriften-im-internet.de/bsvwvbund_26012001_S3236420014.htm##:~:text=Wechsellichtzeichen" rel="nofollow noopener noreferrer"&gt;VwV-StVO&lt;/a&gt;) zusammennehme, ist der Grünpfeil für Radfahrende vor allem in dieser Situation sinnvoll: &lt;strong&gt;Wenn ich aus einer Wohnstraße komme (kein Radweg vorhanden) und rechts auf eine Straße einbiegen will, die einen abgetrennten Radweg hat.&lt;/strong&gt; Da ich hier nur auf querenden Fuß- und Radverkehr achten muss, ist ein sicheres Abbiegen nach rechts auch bei rot in der Regel möglich.&lt;/p&gt;
  230.  
  231. &lt;h3 dir="auto" id="overpass-query-finden"&gt;Overpass-Query finden.&lt;/h3&gt;
  232.  
  233. &lt;p dir="auto"&gt;Ich will die Abfrage nicht zu kompliziert machen, aussortierne kann ich ja immer noch. Ich will also wissen, &lt;strong&gt;wo Ampeln auf Wohnstraßen stehen&lt;/strong&gt;, bei denen &lt;strong&gt;im Umkreis von 10 Metern ein Radweg oder ein getrennter Rad-/Fußweg&lt;/strong&gt; existiert.&lt;/p&gt;
  234.  
  235. &lt;p dir="auto"&gt;Die gesuchten Merkmale lassen sich so in OSM-Tags fassen:&lt;/p&gt;
  236.  
  237. &lt;ul dir="auto"&gt;
  238.  &lt;li&gt;Die Ampel ist ein &lt;code dir="auto"&gt;node&lt;/code&gt; mit &lt;code dir="auto"&gt;highway=traffic_signals&lt;/code&gt;&lt;/li&gt;
  239.  &lt;li&gt;Sie liegt auf einer &lt;code dir="auto"&gt;way&lt;/code&gt; mit &lt;code dir="auto"&gt;highway=residential&lt;/code&gt;&lt;/li&gt;
  240.  &lt;li&gt;In der Nähe (max. 10 m) existiert ein:
  241.    &lt;ul dir="auto"&gt;
  242.      &lt;li&gt;&lt;code dir="auto"&gt;way&lt;/code&gt; mit &lt;code dir="auto"&gt;highway=cycleway&lt;/code&gt;&lt;br&gt;
  243. oder&lt;/li&gt;
  244.      &lt;li&gt;&lt;code dir="auto"&gt;way&lt;/code&gt; mit &lt;code dir="auto"&gt;highway=path&lt;/code&gt; &lt;strong&gt;und&lt;/strong&gt; &lt;code dir="auto"&gt;bicycle=designated&lt;/code&gt; &lt;strong&gt;und&lt;/strong&gt; &lt;code dir="auto"&gt;segregated=yes&lt;/code&gt;&lt;/li&gt;
  245.    &lt;/ul&gt;
  246.  &lt;/li&gt;
  247. &lt;/ul&gt;
  248.  
  249. &lt;p dir="auto"&gt;Mithilfe von ChatGPT (ja, ich weiß, aber ich finde die Overpass-QL echt schwierig), habe ich diesen funktionierenden Query gefunden:&lt;/p&gt;
  250.  
  251. &lt;pre dir="auto"&gt;&lt;code&gt;[out:json][timeout:25];
  252.  
  253. // 1. Wohnstraßen und zugehörige Ampeln
  254. way["highway"="residential"]({{bbox}})-&amp;gt;.residentials;
  255. node(w.residentials)["highway"="traffic_signals"]-&amp;gt;.signals;
  256.  
  257. // 2. Radwege nach OSM-Tagging-Standards
  258. (
  259.  way["highway"="cycleway"]({{bbox}});
  260.  way["highway"="path"]["bicycle"="designated"]["segregated"="yes"]({{bbox}});
  261. )-&amp;gt;.cycleways;
  262.  
  263. // 3. Finde Ampeln, die innerhalb von 10 m zu einem Radweg liegen
  264. node.signals(around.cycleways:10)-&amp;gt;.relevant_signals;
  265.  
  266. .relevant_signals out center;
  267. &lt;/code&gt;&lt;/pre&gt;
  268. &lt;p dir="auto"&gt;👉 &lt;a href="https://overpass-turbo.eu/s/27hJ" rel="nofollow noopener noreferrer"&gt;Abfrage in Overpass Turbo öffnen&lt;/a&gt;&lt;/p&gt;
  269.  
  270. &lt;h3 dir="auto" id="und-jetzt"&gt;Und jetzt?&lt;/h3&gt;
  271.  
  272. &lt;p dir="auto"&gt;Als nächten Schritt werde ich die Ergebnisse für meine Heimatstadt auswerten (tatsächliche Eignung mithilfe von Mapillary oder Sichtung vor Ort prüfen) und anschließend bei der Verwaltung anregen, an diesen Stellen diese Schilder aufzustellen.&lt;/p&gt;
  273. </description>
  274.      <dc:creator>Discostu36</dc:creator>
  275.      <pubDate>Sat, 05 Jul 2025 13:27:19 +0000</pubDate>
  276.      <comments>https://www.openstreetmap.org/user/Discostu36/diary/407033#comments</comments>
  277.    </item>
  278.    <item>
  279.      <title>Bot destroying powerlines</title>
  280.      <link>https://www.openstreetmap.org/user/Maps%20Man/diary/407032</link>
  281.      <guid>https://www.openstreetmap.org/user/Maps%20Man/diary/407032</guid>
  282.      <description>&lt;p dir="auto"&gt;I notice all across China that bots have destroyed powerlines and now they are missing many segments that were previously complete.&lt;/p&gt;
  283. </description>
  284.      <dc:creator>Maps Man</dc:creator>
  285.      <pubDate>Sat, 05 Jul 2025 13:10:38 +0000</pubDate>
  286.      <comments>https://www.openstreetmap.org/user/Maps%20Man/diary/407032#comments</comments>
  287.    </item>
  288.    <item>
  289.      <title>Engagement et rencontres : un retour sur SotM Global 2024 au Kenya</title>
  290.      <link>https://www.openstreetmap.org/user/Abibis/diary/407030</link>
  291.      <guid>https://www.openstreetmap.org/user/Abibis/diary/407030</guid>
  292.      <description>&lt;p dir="auto"&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/commons/0/04/State_of_the_map_Kenya_2024.jpg" alt="State of the Map 2024, Nairobi, Kenya" loading="lazy"&gt;
  293. J’ai eu l’honneur de participer en présentiel à la première conférence State of the Map Global 2024 organisée en Afrique, au Kenya. Cette expérience a été marquante et enrichissante, me permettant de rencontrer de nombreux acteurs passionnés engagés dans divers projets. Bien que je sois la seule représentante du Bénin, je me suis sentie pleinement intégrée dans cette dynamique internationale. Retrouver des amis de la communauté Wikimedia à SotM a été une agréable surprise.&lt;/p&gt;
  294.  
  295. &lt;p dir="auto"&gt;Les sessions, présentations et ateliers étaient d’une qualité exceptionnelle. Bien que je n’aie pas animé d’atelier cette fois-ci, je suis plus déterminée que jamais à le faire lors des prochaines éditions. J’ai particulièrement apprécié les interventions sur l’égalité des genres, notamment celle d’Anastazia Caroll sur Women in OSM Tech, ainsi que celle de Bénédicta, qui a mis en lumière les perspectives de la participation des femmes dans OpenStreetMap.
  296. La réunion des membres votants de HOT m’a permis de rencontrer le président et d’autres membres de l’organisation. Ce fut une occasion précieuse d’échanger des idées et de mieux comprendre les dynamiques internes de HOT. Ces interactions ont renforcé mon engagement au sein de la communauté et m’ont permis de nouer des relations professionnelles significatives.&lt;/p&gt;
  297.  
  298. &lt;p dir="auto"&gt;Je tiens à exprimer ma profonde gratitude à OSM Kenya et au groupe de travail de SotM pour l’organisation exceptionnelle de cet événement, ainsi qu’à HOT pour m’avoir accordé cette bourse qui m’a permis de vivre cette expérience unique. Un immense merci également à l’équipe organisatrice et aux bénévoles, qui ont fait de cette conférence un véritable succès.
  299. Je suis pleinement motivée à poursuivre mon engagement et à jouer un rôle plus actif lors des prochaines éditions.&lt;/p&gt;
  300.  
  301. &lt;p dir="auto"&gt;Rendez-vous à Manille pour SotM 2025 !&lt;/p&gt;
  302.  
  303. &lt;p dir="auto"&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/commons/8/87/SotM_Global_2024_au_Kenya_04.jpg" alt="Texte alternatif" loading="lazy"&gt;&lt;/p&gt;
  304. </description>
  305.      <dc:creator>Abibis</dc:creator>
  306.      <pubDate>Fri, 04 Jul 2025 19:54:43 +0000</pubDate>
  307.      <comments>https://www.openstreetmap.org/user/Abibis/diary/407030#comments</comments>
  308.    </item>
  309.    <item>
  310.      <title>جيل مرغم علي التاريخي </title>
  311.      <link>https://www.openstreetmap.org/user/%D9%86%D8%B5%D8%B1%D9%82%D8%A7%D8%A6%D8%AF%D8%A7%D8%AD%D9%85%D8%AF%D8%A7%D9%84%D9%87%D9%84%D8%A7%D9%84%D9%8A/diary/407029</link>
  312.      <guid>https://www.openstreetmap.org/user/%D9%86%D8%B5%D8%B1%D9%82%D8%A7%D8%A6%D8%AF%D8%A7%D8%AD%D9%85%D8%AF%D8%A7%D9%84%D9%87%D9%84%D8%A7%D9%84%D9%8A/diary/407029</guid>
  313.      <description>&lt;h4 dir="auto" id="section"&gt;جبل مرغم علي التاريخي&lt;/h4&gt;
  314. &lt;p dir="auto"&gt;يعد جبل مرغم علي أحد المعالم التاريخية والأثرية البارزة في قرية ضريبة العرش اليمنية، حيث يحمل بين صخوره آثارًا تعود إلى عهد الدولة الحميرية. يقع هذا الجبل في موقع استراتيجي، إذ كان يستخدم كحصن دفاعي لحماية قلعة الملك الحميري شمر يَهرعِش، التي تبعد عنه حوالي 9 كم في مدينة رداع.
  315. #### المعالم الأثرية
  316. رغم مرور الزمن، لا تزال بعض بقايا القلاع الحميرية قائمة على قمة الجبل، مما يدل على براعة الهندسة العسكرية في ذلك العصر. هذه القلاع كانت مبنية من الحجارة الصلبة، مما ساعدها على الصمود أمام عوامل الطبيعة لقرون طويلة.
  317. #### الموقع الجغرافي والطبيعة
  318. يتميز جبل مرغم علي بتضاريسه الوعرة وارتفاعه الذي يوفر إطلالة رائعة على المناطق المجاورة. كما أن موقعه يجعله نقطة جذب للباحثين في التاريخ والجغرافيا، حيث يمكن للزوار استكشاف بقايا التحصينات القديمة والاستمتاع بجمال الطبيعة المحيطة.
  319. #### أهمية الجبل في السياحة والتراث
  320. يعد هذا الجبل من المواقع التي يمكن أن تسهم في تنشيط السياحة التاريخية في اليمن، خاصة لمحبي الآثار والتاريخ القديم. فهو جزءًا من مسار سياحي يشمل قلعة شمر يَهرعِش وقرية موكل وغيرها من المواقع الحميرية في المنطقة&lt;/p&gt;
  321. </description>
  322.      <dc:creator>نصرقائداحمدالهلالي</dc:creator>
  323.      <pubDate>Fri, 04 Jul 2025 19:46:50 +0000</pubDate>
  324.      <comments>https://www.openstreetmap.org/user/%D9%86%D8%B5%D8%B1%D9%82%D8%A7%D8%A6%D8%AF%D8%A7%D8%AD%D9%85%D8%AF%D8%A7%D9%84%D9%87%D9%84%D8%A7%D9%84%D9%8A/diary/407029#comments</comments>
  325.      <geo:lat>14.3535004</geo:lat>
  326.      <geo:long>44.7821999</geo:long>
  327.      <georss:point>14.3535004 44.7821999</georss:point>
  328.    </item>
  329.    <item>
  330.      <title>Tag: highway = bus_stop</title>
  331.      <link>https://www.openstreetmap.org/user/bernward1/diary/407028</link>
  332.      <guid>https://www.openstreetmap.org/user/bernward1/diary/407028</guid>
  333.      <description>&lt;p dir="auto"&gt;Lange habe ich gedacht, dass dieses Tag durch PTV2 überflüssig werden wird, bis ist gemerkt habe dass es notwendig ist.&lt;/p&gt;
  334.  
  335. &lt;p dir="auto"&gt;Das Tag “highway=bus_stop” (nur zulässig auf Knoten) ist nicht veraltet. Es ist notwendig damit die Bushaltestelle in vielen Karten dargestellt wird. Z.B.: auf der Standardkarte openstreetmap.org&lt;/p&gt;
  336.  
  337. &lt;p dir="auto"&gt;Im Wiki steht auf der Seite Tag:highway=bus_stop in der Spalte “Verwendung” nur “Kompatibilität”. Die mehr als 10 Jahren von PTV2 haben aber gezeigt, dass das Tag weiterhin gebraucht wird.&lt;/p&gt;
  338.  
  339. &lt;p dir="auto"&gt;Es müsste “&lt;b&gt;verpflichtend&lt;/b&gt;” heißen. (Auf der englischen Seite heißt der Eintrag auch Required)&lt;/p&gt;
  340.  
  341. </description>
  342.      <dc:creator>bernward1</dc:creator>
  343.      <pubDate>Fri, 04 Jul 2025 09:54:15 +0000</pubDate>
  344.      <comments>https://www.openstreetmap.org/user/bernward1/diary/407028#comments</comments>
  345.    </item>
  346.    <item>
  347.      <title>Edificios en Pachuca</title>
  348.      <link>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025</link>
  349.      <guid>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025</guid>
  350.      <description>&lt;p dir="auto"&gt;no se que poner jaja&lt;/p&gt;
  351. </description>
  352.      <dc:creator>El ArquiPachuca</dc:creator>
  353.      <pubDate>Fri, 04 Jul 2025 05:50:41 +0000</pubDate>
  354.      <comments>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025#comments</comments>
  355.    </item>
  356.    <item>
  357.      <title>INTERNEE</title>
  358.      <link>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023</link>
  359.      <guid>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023</guid>
  360.      <description>
  361. &lt;p dir="auto"&gt;Activities Performed&lt;/p&gt;
  362.  
  363. &lt;ul dir="auto"&gt;
  364.  &lt;li&gt;Participated in ‘‘transmission grid planning’’, applying surveying and cartographic principles to infrastructure development.&lt;/li&gt;
  365.  &lt;li&gt;Conducted line routing and selection exercises, evaluating terrain and land use for optimal transmission line alignment.&lt;/li&gt;
  366.  &lt;li&gt;'’Collected and recorded coordinates’’ using GNSS equipment to support planning and line diversion strategies.&lt;/li&gt;
  367.  &lt;li&gt;Assisted with **line diversion assessments by integrating spatial analysis and route optimization techniques.&lt;/li&gt;
  368.  &lt;li&gt;Engaged in GIS-based mapping and spatial data management for transmission corridors and project layouts.&lt;/li&gt;
  369.  &lt;li&gt;Supported **drawing office tasks  including drafting, editing, and refining technical layouts for transmission lines using AutoCAD and GIS software.&lt;/li&gt;
  370.  &lt;li&gt;Contributed to the preparation of  survey reports*, integrating observations, geospatial data, and recommendations for planning documentation.&lt;/li&gt;
  371. &lt;/ul&gt;
  372.  
  373. &lt;p dir="auto"&gt;Skills Applied&lt;/p&gt;
  374.  
  375. &lt;ul dir="auto"&gt;
  376.  &lt;li&gt;Georeferencing and symbology in GIS&lt;/li&gt;
  377.  &lt;li&gt;AutoCAD drafting and technical alignment&lt;/li&gt;
  378.  &lt;li&gt;Thematic layering and map production&lt;/li&gt;
  379.  &lt;li&gt;Field coordination using QField and GNSS tools&lt;/li&gt;
  380.  &lt;li&gt;Formal report writing and spatial data interpretation&lt;/li&gt;
  381. &lt;/ul&gt;
  382.  
  383. &lt;p dir="auto"&gt;Today’s tasks deepened my understanding of how surveying and cartographic techniques drive transmission infrastructure planning. The integration of GIS with field activities reaffirmed the importance of spatial accuracy in energy distribution networks. I was particularly engaged with the line diversion analysis, which challenged both technical reasoning and spatial decision-making. I continue to learn from my mentors and refine my approach to precision mapping and collaborative survey documentation.&lt;/p&gt;
  384. </description>
  385.      <dc:creator>MugerwaHukasha</dc:creator>
  386.      <pubDate>Thu, 03 Jul 2025 12:29:14 +0000</pubDate>
  387.      <comments>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023#comments</comments>
  388.    </item>
  389.    <item>
  390.      <title>Straße/ Weg falsch eingezeichnet. Führt zu unschönen Problemen</title>
  391.      <link>https://www.openstreetmap.org/user/BilleBu/diary/407022</link>
  392.      <guid>https://www.openstreetmap.org/user/BilleBu/diary/407022</guid>
  393.      <description>&lt;p dir="auto"&gt;&lt;a href="https://www.openstreetmap.org/#map=17/54.618512/9.361435" rel="nofollow noopener noreferrer" dir="auto"&gt;osm.org/#map=17/54.618512/9.361435&lt;/a&gt;&lt;/p&gt;
  394.  
  395. &lt;p dir="auto"&gt;Hallo alle zusammen,&lt;/p&gt;
  396.  
  397. &lt;p dir="auto"&gt;bin neu hier und habe etwas in der Karte entdeckt, was so nicht richtig ist, bzw. den wahren örtlichen Gegebenheiten entspricht.
  398. Diese Punkt-Stichlinie zeigt wohl einen “Fußweg” an.
  399. Bei dem Teilstück von der Hauptstrasse kommen in Richtung Waldstück neben der 2a, handelt es sich um eine private Zufahrt, also Privatgrundstück (nämlich meins), zum Haus.
  400. Bei dem “Fußweg” handelt es sich ebenfalls um ein privates Grundstück.
  401. Es ist leider so dargestellt das man dort durchfahren/ durchgehen kann.
  402. Das geht nicht: dort befindet sich eine feste Absperrung.
  403. Zumal es sich hier um private Grundstücke handelt, wo der allgemeine und öffentliche Zutritt nicht erlaubt ist.
  404. Es verursacht hier sehr unschöne Probleme, weil sich Menschen auf dieses Kartenmaterial berufen.
  405. Ich würde mich sehr freuen, wenn hier jemand ist, der das zeitnah korrigieren kann.
  406. Vielen Dank&lt;/p&gt;
  407. </description>
  408.      <dc:creator>BilleBu</dc:creator>
  409.      <pubDate>Thu, 03 Jul 2025 10:04:43 +0000</pubDate>
  410.      <comments>https://www.openstreetmap.org/user/BilleBu/diary/407022#comments</comments>
  411.    </item>
  412.    <item>
  413.      <title>Черчение контуров зданий по фотографиям схем строек</title>
  414.      <link>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021</link>
  415.      <guid>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021</guid>
  416.      <description>
  417. &lt;p dir="auto"&gt;Не высокая частота обновления спутниковых снимков, не всегда позволяет добавлять новые здания. В этой ситуации можно воспользоваться схемами с паспортов строек.
  418. При перерисовке схемы возникает проблема, состоящая в том, что фотографии схем содержат искажение перспективы, которое надо как то исправлять. Ниже предложен не сложный способ того, как можно это сделать с помощью растрового графического редактора GIMP, векторного - Inkscape, а так же JOSM с установленным плагином &lt;a href="https://wiki.openstreetmap.org/wiki/JOSM/Plugins/ImportVec" rel="nofollow noopener noreferrer"&gt;ImportVec&lt;/a&gt;.&lt;/p&gt;
  419.  
  420. &lt;ul dir="auto"&gt;
  421.  &lt;li&gt;
  422.    &lt;p dir="auto"&gt;На первом изображении видно искажение перспективы возникшее в результате отклонения фокальной плоскости фотокамеры относительно плоскости схемы стройки.&lt;/p&gt;
  423.  
  424.    &lt;p dir="auto"&gt;&lt;img src="https://imgur.com/Ux0bc1A.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  425.  &lt;/li&gt;
  426.  &lt;li&gt;
  427.    &lt;p dir="auto"&gt;Загружаем изображение в редактор GIMP, и в меню “Вид” включаем отображение сетки&lt;/p&gt;
  428.  
  429.    &lt;p dir="auto"&gt;&lt;img src="https://imgur.com/kGgiu2X.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  430.  &lt;/li&gt;
  431.  &lt;li&gt;
  432.    &lt;p dir="auto"&gt;Далее с помощью инструмента 3D преобразование или Перспектива, совмещаем прямоугольные границы рамки паспорта, с направляющими сетки так, что бы горизонтальные линии плаката совпали с горизонтальными линиями сетки, а вертикальные, с вертикальными. Для наклона изображения следует зажимать клавишу Ctrl. В результате мы должны получить вполне правильный прямоугольник.  После этого, можно обрезать лишние края, и добавить контрастности изображения для увеличения чёткости линий.
  433. Тут важно отметить, что на фото обязательно должен быть виден весь паспорт, а не только его часть со схемой, поскольку выравнивание происходит по прямоугольной форме края его рамки.
  434.  &lt;img src="https://imgur.com/gOP4ouC.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  435.  &lt;/li&gt;
  436.  &lt;li&gt;
  437.    &lt;p dir="auto"&gt;Сохраняем изображение, и открываем его в редакторе Inkscape. Теперь необходимо обвести контуры здания.  Так же следует обвести контуры уже существующих зданий, границ и дорог, для того что бы по этими линиями можно было привязаться к уже существующим объектам карты в JOSM. Сохраняем результат в SVG, не забыв перед этим удалить из файла растровую подложку.&lt;/p&gt;
  438.  
  439.    &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/D1JxXCI.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  440.  &lt;/li&gt;
  441.  &lt;li&gt;
  442.    &lt;p dir="auto"&gt;Загружаем в JOSM данные OSM интересующего нас участка&lt;/p&gt;
  443.  
  444.    &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/Pr5nLMy.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  445.  &lt;/li&gt;
  446.  &lt;li&gt;
  447.    &lt;p dir="auto"&gt;Далее, поверх него создаём новый пустой слой, и перетаскиваем (d&amp;amp;d) на него полученный SVG файл.  Как видно на скриншоте, масштаб и положение линий не совпадают со слоем загруженных данных.&lt;/p&gt;
  448.  
  449.    &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/auKMZsK.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  450.  &lt;/li&gt;
  451.  &lt;li&gt;
  452.    &lt;p dir="auto"&gt;Теперь выделяем все линии, и с помощью масштабирования, и поворота, добиваемся совмещения линий дорог и зданий которые мы обвели, с уже существующими объектами карты, и фотоподложки.&lt;/p&gt;
  453.  
  454.    &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/cgDZW1q.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  455.  &lt;/li&gt;
  456.  &lt;li&gt;
  457.    &lt;p dir="auto"&gt;Выделяем контур интересующего нас здания, копируем его ( ctrl+c), и переключившись на слой с данными OSM вставляем (ctrl+v).   Контур будет вставлен в редактируемый слой, но не на то же место где он находился в его родном слое. Это легко исправить простым перетаскиванием, до совпадения с полупрозрачным контуром этого же объекта в другом слое, где мы его выровняли. Остаётся добавить тэги, и выгрузить данные в OSM.
  458.  &lt;img src="https://i.imgur.com/sGlKPjq.png" alt="" loading="lazy"&gt;&lt;/p&gt;
  459.  &lt;/li&gt;
  460. &lt;/ul&gt;
  461.  
  462. &lt;p dir="auto"&gt;Таким способом можно достаточно просто и быстро переносить данные со схем строящихся зданий, дорог и других объектов.&lt;/p&gt;
  463. </description>
  464.      <dc:creator>solenoid jam</dc:creator>
  465.      <pubDate>Thu, 03 Jul 2025 03:38:07 +0000</pubDate>
  466.      <comments>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021#comments</comments>
  467.    </item>
  468.    <item>
  469.      <title>Capturing the whole city of Salzburg in 360°: Better Mounting, Better Coverage (Part 3)</title>
  470.      <link>https://www.openstreetmap.org/user/Negreheb/diary/407018</link>
  471.      <guid>https://www.openstreetmap.org/user/Negreheb/diary/407018</guid>
  472.      <description>&lt;p dir="auto"&gt;Part 1: &lt;a href="https://www.openstreetmap.org/user/Negreheb/diary/405306" rel="nofollow noopener noreferrer" dir="auto"&gt;osm.org/user/Negreheb/diary/405306&lt;/a&gt;&lt;br&gt;
  473. Part 2: &lt;a href="https://www.openstreetmap.org/user/Negreheb/diary/406030" rel="nofollow noopener noreferrer" dir="auto"&gt;osm.org/user/Negreheb/diary/406030&lt;/a&gt;&lt;/p&gt;
  474.  
  475. &lt;h1 dir="auto" id="mapping-salzburg--update-3-better-mounting-better-coverage"&gt;360° Mapping Salzburg – Update #3: Better Mounting, Better Coverage&lt;/h1&gt;
  476.  
  477. &lt;p dir="auto"&gt;Hello OSM Community,&lt;/p&gt;
  478.  
  479. &lt;p dir="auto"&gt;I’m continuing my effort to capture 360° images of the city of Salzburg for use in &lt;strong&gt;Mapillary&lt;/strong&gt; and &lt;strong&gt;Panoramax&lt;/strong&gt;. The goal remains the same: improve OpenStreetMap data, especially in areas with unresolved notes where better visual context can help.&lt;/p&gt;
  480.  
  481. &lt;h2 dir="auto" id="progress-so-far"&gt;Progress So Far&lt;/h2&gt;
  482.  
  483. &lt;p dir="auto"&gt;Here’s the current state of coverage from my 360° image collection:&lt;/p&gt;
  484.  
  485. &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/dtzhAHQ.png" alt="Salzburg" loading="lazy"&gt;&lt;/p&gt;
  486.  
  487. &lt;h2 dir="auto" id="my-route-planning-setup"&gt;My Route Planning Setup&lt;/h2&gt;
  488.  
  489. &lt;p dir="auto"&gt;To plan my routes, I’ve been using &lt;strong&gt;OSMAnd’s&lt;/strong&gt; built-in GPX recording and map display. This allows me to see where I’ve already been and make instant decisions on which streets to cover next - without having a router trying to direct me back on track constantly.&lt;/p&gt;
  490.  
  491. &lt;p dir="auto"&gt;I can also choose freely whether to ride on streets, paths, or cycleways depending on conditions. This flexibility has proven much more practical than relying on pre-planned routes.&lt;/p&gt;
  492.  
  493. &lt;h2 dir="auto" id="managing-photos-for-upload"&gt;Managing Photos for Upload&lt;/h2&gt;
  494.  
  495. &lt;p dir="auto"&gt;On the photo management side, I’ve kept my setup from last time: using the &lt;strong&gt;command-line tools&lt;/strong&gt; from both &lt;strong&gt;Mapillary&lt;/strong&gt; and &lt;strong&gt;Panoramax&lt;/strong&gt;. They continue to work flawlessly and are far more stable and efficient than the GUI options.&lt;/p&gt;
  496.  
  497. &lt;p dir="auto"&gt;However, I still need to manually filter the images - removing duplicates taken at traffic lights, while standing still, or checking my phone. It’s a bit of work, but it ensures that the uploaded sequences are clean and useful. I’m not sure i want this with the video-mode - but with the new mounting it might be worth a try.&lt;/p&gt;
  498.  
  499. &lt;h2 dir="auto" id="whats-changed-since-the-last-post"&gt;What’s Changed Since the Last Post&lt;/h2&gt;
  500.  
  501. &lt;p dir="auto"&gt;One major improvement: I switched from a &lt;strong&gt;helmet-mounted camera&lt;/strong&gt; to a &lt;strong&gt;selfie stick mounted directly on my bicycle&lt;/strong&gt;. This setup means I can now look around naturally (better safety) while riding without affecting the camera’s field of view.&lt;/p&gt;
  502.  
  503. &lt;p dir="auto"&gt;&lt;img src="https://i.imgur.com/MC0uazr.jpeg" alt="Clamping-Setup" loading="lazy"&gt;&lt;/p&gt;
  504.  
  505. &lt;p dir="auto"&gt;Additionally, I’ve started adding a &lt;strong&gt;nadir&lt;/strong&gt; - a small branded graphic at the bottom of the image that hides the mounting point and promotes our local OSM club. I followed the excellent guide by &lt;a href="https://www.trekview.org/blog/adding-a-custom-nadir-to-360-video-photo/" rel="nofollow noopener noreferrer"&gt;Trek View&lt;/a&gt; to make this happen.&lt;/p&gt;
  506.  
  507. &lt;p dir="auto"&gt;&lt;a href="https://www.mapillary.com/app/user/OidaHeast?lat=47.7931037&amp;amp;lng=13.0470726&amp;amp;z=17&amp;amp;all_coverage=false&amp;amp;pKey=1147948973437204&amp;amp;focus=photo" rel="nofollow noopener noreferrer"&gt;Example picutre with Nadir on Mapillary&lt;/a&gt;&lt;/p&gt;
  508.  
  509. &lt;h2 dir="auto" id="reflections-on-the-new-setup"&gt;Reflections on the New Setup&lt;/h2&gt;
  510.  
  511. &lt;p dir="auto"&gt;The fixed camera mount provied useful so far. The image quality more consistent, but I also feel more comfortable riding. My bike has a bit of an unusual frame, which made mounting the selfie stick with clamps surprisingly easy.&lt;/p&gt;
  512.  
  513. &lt;h2 dir="auto" id="whats-next"&gt;What’s Next?&lt;/h2&gt;
  514.  
  515. &lt;p dir="auto"&gt;My goal remains ambitious: to &lt;strong&gt;capture all of Salzburg&lt;/strong&gt;, street by street, and make the imagery available to everyone through &lt;strong&gt;Mapillary&lt;/strong&gt; and &lt;strong&gt;Panoramax&lt;/strong&gt;. I believe this kind of street-level imagery can benefit the entire OSM community—locally and beyond.&lt;/p&gt;
  516.  
  517. &lt;p dir="auto"&gt;If you have ideas, tools, or workflows that might help, I’d love to hear them. And if you’re local and want to collaborate, let’s connect!&lt;/p&gt;
  518. </description>
  519.      <dc:creator>Negreheb</dc:creator>
  520.      <pubDate>Tue, 01 Jul 2025 18:24:45 +0000</pubDate>
  521.      <comments>https://www.openstreetmap.org/user/Negreheb/diary/407018#comments</comments>
  522.      <geo:lat>47.80969602390851</geo:lat>
  523.      <geo:long>13.050178525736555</geo:long>
  524.      <georss:point>47.80969602390851 13.050178525736555</georss:point>
  525.    </item>
  526.    <item>
  527.      <title>Is There Any news about Satellite Imagery ?</title>
  528.      <link>https://www.openstreetmap.org/user/farhadGuli/diary/407015</link>
  529.      <guid>https://www.openstreetmap.org/user/farhadGuli/diary/407015</guid>
  530.      <description>&lt;p dir="auto"&gt;Dear OSM Community and Team,
  531. 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;
  532. </description>
  533.      <dc:creator>farhadGuli</dc:creator>
  534.      <pubDate>Tue, 01 Jul 2025 09:56:25 +0000</pubDate>
  535.      <comments>https://www.openstreetmap.org/user/farhadGuli/diary/407015#comments</comments>
  536.    </item>
  537.    <item>
  538.      <title>Better OSM Diary : ideas, reflexions, improvements</title>
  539.      <link>https://www.openstreetmap.org/user/Koreller/diary/407012</link>
  540.      <guid>https://www.openstreetmap.org/user/Koreller/diary/407012</guid>
  541.      <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;
  542.  
  543. &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;
  544.  
  545. &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;
  546.  
  547. &lt;h2 dir="auto" id="observation"&gt;Observation&lt;/h2&gt;
  548. &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;
  549.  
  550. &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;
  551.  
  552. &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;
  553.  
  554. &lt;h2 dir="auto" id="proposal"&gt;Proposal&lt;/h2&gt;
  555.  
  556. &lt;h3 dir="auto" id="categorise"&gt;Categorise&lt;/h3&gt;
  557. &lt;p dir="auto"&gt;Allowing diaries to be categorised offers several advantages:&lt;/p&gt;
  558.  
  559. &lt;ul dir="auto"&gt;
  560.  &lt;li&gt;Easier to identify the topic(s) of a diary&lt;/li&gt;
  561.  &lt;li&gt;Have a list of diaries talking of a specific topic&lt;/li&gt;
  562.  &lt;li&gt;Easier to find a specific diary&lt;/li&gt;
  563. &lt;/ul&gt;
  564.  
  565. &lt;p dir="auto"&gt;A category would group together several diaries addressing the same theme.&lt;/p&gt;
  566.  
  567. &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;
  568.  
  569. &lt;h3 dir="auto" id="add-upvotes"&gt;Add upvotes&lt;/h3&gt;
  570. &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;
  571.  
  572. &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;
  573.  
  574. &lt;p dir="auto"&gt;This system would be very similar to GitLab for issues, or Reddit for content.&lt;/p&gt;
  575.  
  576. &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;
  577.  
  578. &lt;h3 dir="auto" id="diaries-search"&gt;Diaries search&lt;/h3&gt;
  579.  
  580. &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;
  581.  
  582. &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;
  583. &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;
  584.  
  585. &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;
  586. &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;
  587. </description>
  588.      <dc:creator>Koreller</dc:creator>
  589.      <pubDate>Tue, 01 Jul 2025 08:36:55 +0000</pubDate>
  590.      <comments>https://www.openstreetmap.org/user/Koreller/diary/407012#comments</comments>
  591.    </item>
  592.    <item>
  593.      <title>Kann Karten nicht mehr drucken!</title>
  594.      <link>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</link>
  595.      <guid>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</guid>
  596.      <description>&lt;p dir="auto"&gt;Kann Karten nicht mehr drucken!&lt;/p&gt;
  597. </description>
  598.      <dc:creator>FrankBuchholz</dc:creator>
  599.      <pubDate>Mon, 30 Jun 2025 09:44:39 +0000</pubDate>
  600.      <comments>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010#comments</comments>
  601.    </item>
  602.    <item>
  603.      <title>Editing</title>
  604.      <link>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</link>
  605.      <guid>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</guid>
  606.      <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
  607. I went ahead and edited my villages by adding the various buildings and trees that haven’t been mapped yet&lt;/p&gt;
  608. </description>
  609.      <dc:creator>Ofoyrwoth</dc:creator>
  610.      <pubDate>Mon, 30 Jun 2025 09:30:21 +0000</pubDate>
  611.      <comments>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009#comments</comments>
  612.      <geo:lat>0.055702319934704085</geo:lat>
  613.      <geo:long>32.466012239428835</geo:long>
  614.      <georss:point>0.055702319934704085 32.466012239428835</georss:point>
  615.    </item>
  616.  </channel>
  617. </rss>
  618.  

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