FEED Validator

Congratulations!

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.

• line 108, column 0: description should not contain loading attribute (15 occurrences) [help]

        <description>&lt;p dir="auto"&gt;&lt;img src="https://upload.wikimedia ...
  

• line 518, column 2: Missing atom:link with rel="self" [help]

    </channel>
    ^

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/RealKorean_2828/diary/407035</link>
17.      <guid>https://www.openstreetmap.org/user/RealKorean_2828/diary/407035</guid>
18.      <description>&lt;p dir="auto"&gt;OSM모임이나 협회 같은거 우리나라에도 있으면 좋겠다 바로 옆나라 일본도 있던데&lt;/p&gt;
19. </description>
20.      <dc:creator>RealKorean_2828</dc:creator>
21.      <pubDate>Sun, 06 Jul 2025 08:58:54 +0000</pubDate>
22.      <comments>https://www.openstreetmap.org/user/RealKorean_2828/diary/407035#comments</comments>
23.    </item>
24.    <item>
25.      <title>Micromapping Latrobe Valley</title>
26.      <link>https://www.openstreetmap.org/user/aussierider75/diary/407034</link>
27.      <guid>https://www.openstreetmap.org/user/aussierider75/diary/407034</guid>
28.      <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;
29. </description>
30.      <dc:creator>aussierider75</dc:creator>
31.      <pubDate>Sun, 06 Jul 2025 01:00:03 +0000</pubDate>
32.      <comments>https://www.openstreetmap.org/user/aussierider75/diary/407034#comments</comments>
33.      <geo:lat>-38.18505225452746</geo:lat>
34.      <geo:long>146.29046648740768</geo:long>
35.      <georss:point>-38.18505225452746 146.29046648740768</georss:point>
36.    </item>
37.    <item>
38.      <title>Grünpfeil für Radfahrer: Geeignete Orte finden</title>
39.      <link>https://www.openstreetmap.org/user/Discostu36/diary/407033</link>
40.      <guid>https://www.openstreetmap.org/user/Discostu36/diary/407033</guid>
41.      <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;
42.  
43. <h3 dir="auto" id="wo-sind-solche-zeichen-sinnvoll">Wo sind solche Zeichen sinnvoll?</h3>
44.  
45. <p dir="auto">Wenn ich meine persönliche Erfahrung und die gesetzlichen Vorgaben (<a href="https://www.gesetze-im-internet.de/stvo_2013/__37.html" rel="nofollow noopener noreferrer">StVO</a>, <a href="https://www.verwaltungsvorschriften-im-internet.de/bsvwvbund_26012001_S3236420014.htm##:~:text=Wechsellichtzeichen" rel="nofollow noopener noreferrer">VwV-StVO</a>) zusammennehme, ist der Grünpfeil für Radfahrende vor allem in dieser Situation sinnvoll: <strong>Wenn ich aus einer Wohnstraße komme (kein Radweg vorhanden) und rechts auf eine Straße einbiegen will, die einen abgetrennten Radweg hat.</strong> 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.</p>
46.  
47. <h3 dir="auto" id="overpass-query-finden">Overpass-Query finden.</h3>
48.  
49. <p dir="auto">Ich will die Abfrage nicht zu kompliziert machen, aussortierne kann ich ja immer noch. Ich will also wissen, <strong>wo Ampeln auf Wohnstraßen stehen</strong>, bei denen <strong>im Umkreis von 10 Metern ein Radweg oder ein getrennter Rad-/Fußweg</strong> existiert.</p>
50.  
51. <p dir="auto">Die gesuchten Merkmale lassen sich so in OSM-Tags fassen:</p>
52.  
53. <ul dir="auto">
54.  <li>Die Ampel ist ein <code dir="auto">node</code> mit <code dir="auto">highway=traffic_signals</code></li>
55.  <li>Sie liegt auf einer <code dir="auto">way</code> mit <code dir="auto">highway=residential</code></li>
56.  <li>In der Nähe (max. 10 m) existiert ein:
57.    <ul dir="auto">
58.      <li><code dir="auto">way</code> mit <code dir="auto">highway=cycleway</code><br>
59. oder</li>
60.      <li><code dir="auto">way</code> mit <code dir="auto">highway=path</code> <strong>und</strong> <code dir="auto">bicycle=designated</code> <strong>und</strong> <code dir="auto">segregated=yes</code></li>
61.    </ul>
62.  </li>
63. </ul>
64.  
65. <p dir="auto">Mithilfe von ChatGPT (ja, ich weiß, aber ich finde die Overpass-QL echt schwierig), habe ich diesen funktionierenden Query gefunden:</p>
66.  
67. <pre dir="auto"><code>[out:json][timeout:25];
68.  
69. // 1. Wohnstraßen und zugehörige Ampeln
70. way["highway"="residential"]({{bbox}})->.residentials;
71. node(w.residentials)["highway"="traffic_signals"]->.signals;
72.  
73. // 2. Radwege nach OSM-Tagging-Standards
74. (
75.  way["highway"="cycleway"]({{bbox}});
76.  way["highway"="path"]["bicycle"="designated"]["segregated"="yes"]({{bbox}});
77. )->.cycleways;
78.  
79. // 3. Finde Ampeln, die innerhalb von 10 m zu einem Radweg liegen
80. node.signals(around.cycleways:10)->.relevant_signals;
81.  
82. .relevant_signals out center;
83. </code></pre>
84. <p dir="auto">👉 <a href="https://overpass-turbo.eu/s/27hJ" rel="nofollow noopener noreferrer">Abfrage in Overpass Turbo öffnen</a></p>
85.  
86. <h3 dir="auto" id="und-jetzt">Und jetzt?</h3>
87.  
88. <p dir="auto">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.</p>
89. </description>
90.      <dc:creator>Discostu36</dc:creator>
91.      <pubDate>Sat, 05 Jul 2025 13:27:19 +0000</pubDate>
92.      <comments>https://www.openstreetmap.org/user/Discostu36/diary/407033#comments</comments>
93.    </item>
94.    <item>
95.      <title>Bot destroying powerlines</title>
96.      <link>https://www.openstreetmap.org/user/Maps%20Man/diary/407032</link>
97.      <guid>https://www.openstreetmap.org/user/Maps%20Man/diary/407032</guid>
98.      <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;
99. </description>
100.      <dc:creator>Maps Man</dc:creator>
101.      <pubDate>Sat, 05 Jul 2025 13:10:38 +0000</pubDate>
102.      <comments>https://www.openstreetmap.org/user/Maps%20Man/diary/407032#comments</comments>
103.    </item>
104.    <item>
105.      <title>Engagement et rencontres : un retour sur SotM Global 2024 au Kenya</title>
106.      <link>https://www.openstreetmap.org/user/Abibis/diary/407030</link>
107.      <guid>https://www.openstreetmap.org/user/Abibis/diary/407030</guid>
108.      <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;
109. 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.</p>
110.  
111. <p dir="auto">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.
112. 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.</p>
113.  
114. <p dir="auto">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.
115. Je suis pleinement motivée à poursuivre mon engagement et à jouer un rôle plus actif lors des prochaines éditions.</p>
116.  
117. <p dir="auto">Rendez-vous à Manille pour SotM 2025 !</p>
118.  
119. <p dir="auto"><img src="https://upload.wikimedia.org/wikipedia/commons/8/87/SotM_Global_2024_au_Kenya_04.jpg" alt="Texte alternatif" loading="lazy"></p>
120. </description>
121.      <dc:creator>Abibis</dc:creator>
122.      <pubDate>Fri, 04 Jul 2025 19:54:43 +0000</pubDate>
123.      <comments>https://www.openstreetmap.org/user/Abibis/diary/407030#comments</comments>
124.    </item>
125.    <item>
126.      <title>جيل مرغم علي التاريخي </title>
127.      <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>
128.      <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>
129.      <description>&lt;h4 dir="auto" id="section"&gt;جبل مرغم علي التاريخي&lt;/h4&gt;
130. <p dir="auto">يعد جبل مرغم علي أحد المعالم التاريخية والأثرية البارزة في قرية ضريبة العرش اليمنية، حيث يحمل بين صخوره آثارًا تعود إلى عهد الدولة الحميرية. يقع هذا الجبل في موقع استراتيجي، إذ كان يستخدم كحصن دفاعي لحماية قلعة الملك الحميري شمر يَهرعِش، التي تبعد عنه حوالي 9 كم في مدينة رداع.
131. #### المعالم الأثرية
132. رغم مرور الزمن، لا تزال بعض بقايا القلاع الحميرية قائمة على قمة الجبل، مما يدل على براعة الهندسة العسكرية في ذلك العصر. هذه القلاع كانت مبنية من الحجارة الصلبة، مما ساعدها على الصمود أمام عوامل الطبيعة لقرون طويلة.
133. #### الموقع الجغرافي والطبيعة
134. يتميز جبل مرغم علي بتضاريسه الوعرة وارتفاعه الذي يوفر إطلالة رائعة على المناطق المجاورة. كما أن موقعه يجعله نقطة جذب للباحثين في التاريخ والجغرافيا، حيث يمكن للزوار استكشاف بقايا التحصينات القديمة والاستمتاع بجمال الطبيعة المحيطة.
135. #### أهمية الجبل في السياحة والتراث
136. يعد هذا الجبل من المواقع التي يمكن أن تسهم في تنشيط السياحة التاريخية في اليمن، خاصة لمحبي الآثار والتاريخ القديم. فهو جزءًا من مسار سياحي يشمل قلعة شمر يَهرعِش وقرية موكل وغيرها من المواقع الحميرية في المنطقة</p>
137. </description>
138.      <dc:creator>نصرقائداحمدالهلالي</dc:creator>
139.      <pubDate>Fri, 04 Jul 2025 19:46:50 +0000</pubDate>
140.      <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>
141.      <geo:lat>14.3535004</geo:lat>
142.      <geo:long>44.7821999</geo:long>
143.      <georss:point>14.3535004 44.7821999</georss:point>
144.    </item>
145.    <item>
146.      <title>Tag: highway = bus_stop</title>
147.      <link>https://www.openstreetmap.org/user/bernward1/diary/407028</link>
148.      <guid>https://www.openstreetmap.org/user/bernward1/diary/407028</guid>
149.      <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;
150.  
151. <p dir="auto">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</p>
152.  
153. <p dir="auto">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.</p>
154.  
155. <p dir="auto">Es müsste “<b>verpflichtend</b>” heißen. (Auf der englischen Seite heißt der Eintrag auch Required)</p>
156.  
157. </description>
158.      <dc:creator>bernward1</dc:creator>
159.      <pubDate>Fri, 04 Jul 2025 09:54:15 +0000</pubDate>
160.      <comments>https://www.openstreetmap.org/user/bernward1/diary/407028#comments</comments>
161.    </item>
162.    <item>
163.      <title>First Steps in Mapping: My Experience with Transmission Projects and OSM</title>
164.      <link>https://www.openstreetmap.org/user/%EA%B2%BD%EC%82%AC%EB%9E%91/diary/407027</link>
165.      <guid>https://www.openstreetmap.org/user/%EA%B2%BD%EC%82%AC%EB%9E%91/diary/407027</guid>
166.      <description>&lt;p dir="auto"&gt;안녕하세요, OSM 커뮤니티 여러분!&lt;/p&gt;
167.  
168. <p dir="auto">최근 제가 참여한 송전선 계획 및 라우팅 프로젝트를 계기로 오픈스트리트맵(OpenStreetMap, 이하 OSM)에 대해 다시 한 번 깊이 생각해보게 되어, 이렇게 일기 형식으로 공유하게 되었습니다.</p>
169.  
170. <p dir="auto">🛰️ 현장 측량과 OSM의 만남
171. 송전선 노선을 계획하고 설계하는 과정에서 저는 다음과 같은 업무에 참여했습니다:</p>
172.  
173. <p dir="auto">지형 분석을 통한 송전선 라우팅 및 우회 노선 평가</p>
174.  
175. <p dir="auto">GNSS 장비를 활용한 좌표 수집 및 기록 작업</p>
176.  
177. <p dir="auto">QGIS와 AutoCAD를 이용한 노선 시각화 및 도면 제작</p>
178.  
179. <p dir="auto">공간 데이터를 기반으로 한 노선 최적화 및 보고서 작성</p>
180.  
181. <p dir="auto">이 과정에서 지도와 공간 정보가 얼마나 중요한 역할을 하는지 직접 체감할 수 있었고, 자연스럽게 오픈스트리트맵과 같은 개방형 지도 플랫폼의 가치를 떠올리게 되었습니다.</p>
182.  
183. <p dir="auto">🌍 OSM의 중요성을 느낀 계기
184. 현장에 나가면 종종 공식 지도에는 없는 마을길, 임도, 건물을 만나게 됩니다.
185. 놀랍게도, 그중 상당수는 OSM에는 이미 반영되어 있거나 반대로 추가 기여가 필요한 공간들이었습니다.</p>
186.  
187. <p dir="auto">단순한 공공기관의 지도보다도, OSM이 오히려 더 현실에 가까운 정보를 담고 있는 경우를 직접 경험하면서,
188. “나도 이 플랫폼에 직접 기여해보고 싶다”는 마음이 생겼습니다.</p>
189.  
190. <p dir="auto">💡 앞으로의 계획
191. 프로젝트 중 수집한 위치 정보와 현장 관찰을 바탕으로 도로, 건물, 포인트 등의 정보를 직접 OSM에 추가할 계획입니다.</p>
192.  
193. <p dir="auto">주변의 측량 및 엔지니어링 분야 동료들에게 OSM의 가치와 기여 방법을 공유해볼 생각입니다.</p>
194.  
195. <p dir="auto">앞으로도 다양한 인프라 프로젝트에 참여하면서, 기여가 필요한 지역을 중심으로 활동을 이어가고자 합니다.</p>
196.  
197. <p dir="auto">OSM은 단순히 지도를 그리는 도구가 아니라, 사람과 공간을 연결하고, 누구도 지도에서 소외되지 않도록 돕는 플랫폼이라는 점에서 큰 감명을 받았습니다.</p>
198.  
199. <p dir="auto">읽어주셔서 감사합니다! 앞으로도 자주 글을 남기고, 커뮤니티 여러분들과도 소통하며 성장하고 싶습니다.
200. 피드백이나 팁, 조언이 있다면 언제든지 환영합니다.</p>
201.  
202. <p dir="auto">행복한 매핑 되세요!
203. – [69intv.com]</p>
204. </description>
205.      <dc:creator>경사랑</dc:creator>
206.      <pubDate>Fri, 04 Jul 2025 09:46:36 +0000</pubDate>
207.      <comments>https://www.openstreetmap.org/user/%EA%B2%BD%EC%82%AC%EB%9E%91/diary/407027#comments</comments>
208.    </item>
209.    <item>
210.      <title>Edificios en Pachuca</title>
211.      <link>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025</link>
212.      <guid>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025</guid>
213.      <description>&lt;p dir="auto"&gt;no se que poner jaja&lt;/p&gt;
214. </description>
215.      <dc:creator>El ArquiPachuca</dc:creator>
216.      <pubDate>Fri, 04 Jul 2025 05:50:41 +0000</pubDate>
217.      <comments>https://www.openstreetmap.org/user/El%20ArquiPachuca/diary/407025#comments</comments>
218.    </item>
219.    <item>
220.      <title>bonjour </title>
221.      <link>https://www.openstreetmap.org/user/giteamoudou/diary/407024</link>
222.      <guid>https://www.openstreetmap.org/user/giteamoudou/diary/407024</guid>
223.      <description>&lt;p dir="auto"&gt;Excellent accueil par Mafhoud et sa famille. Il n’est pas avare de renseignements. Cuisine excellente, bien mieux qu’au restaurant ! Sanitaires très propres. On y reviendra..&lt;/p&gt;
224. </description>
225.      <dc:creator>giteamoudou</dc:creator>
226.      <pubDate>Thu, 03 Jul 2025 20:41:20 +0000</pubDate>
227.      <comments>https://www.openstreetmap.org/user/giteamoudou/diary/407024#comments</comments>
228.      <geo:lat>31.243878548423407</geo:lat>
229.      <geo:long>-6.588766295017251</geo:long>
230.      <georss:point>31.243878548423407 -6.588766295017251</georss:point>
231.    </item>
232.    <item>
233.      <title>INTERNEE</title>
234.      <link>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023</link>
235.      <guid>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023</guid>
236.      <description>
237. <p dir="auto">Activities Performed</p>
238.  
239. <ul dir="auto">
240.  <li>Participated in ‘‘transmission grid planning’’, applying surveying and cartographic principles to infrastructure development.</li>
241.  <li>Conducted line routing and selection exercises, evaluating terrain and land use for optimal transmission line alignment.</li>
242.  <li>'’Collected and recorded coordinates’’ using GNSS equipment to support planning and line diversion strategies.</li>
243.  <li>Assisted with **line diversion assessments by integrating spatial analysis and route optimization techniques.</li>
244.  <li>Engaged in GIS-based mapping and spatial data management for transmission corridors and project layouts.</li>
245.  <li>Supported **drawing office tasks  including drafting, editing, and refining technical layouts for transmission lines using AutoCAD and GIS software.</li>
246.  <li>Contributed to the preparation of  survey reports*, integrating observations, geospatial data, and recommendations for planning documentation.</li>
247. </ul>
248.  
249. <p dir="auto">Skills Applied</p>
250.  
251. <ul dir="auto">
252.  <li>Georeferencing and symbology in GIS</li>
253.  <li>AutoCAD drafting and technical alignment</li>
254.  <li>Thematic layering and map production</li>
255.  <li>Field coordination using QField and GNSS tools</li>
256.  <li>Formal report writing and spatial data interpretation</li>
257. </ul>
258.  
259. <p dir="auto">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.</p>
260. </description>
261.      <dc:creator>MugerwaHukasha</dc:creator>
262.      <pubDate>Thu, 03 Jul 2025 12:29:14 +0000</pubDate>
263.      <comments>https://www.openstreetmap.org/user/MugerwaHukasha/diary/407023#comments</comments>
264.    </item>
265.    <item>
266.      <title>Straße/ Weg falsch eingezeichnet. Führt zu unschönen Problemen</title>
267.      <link>https://www.openstreetmap.org/user/BilleBu/diary/407022</link>
268.      <guid>https://www.openstreetmap.org/user/BilleBu/diary/407022</guid>
269.      <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;
270.  
271. <p dir="auto">Hallo alle zusammen,</p>
272.  
273. <p dir="auto">bin neu hier und habe etwas in der Karte entdeckt, was so nicht richtig ist, bzw. den wahren örtlichen Gegebenheiten entspricht.
274. Diese Punkt-Stichlinie zeigt wohl einen “Fußweg” an.
275. 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.
276. Bei dem “Fußweg” handelt es sich ebenfalls um ein privates Grundstück.
277. Es ist leider so dargestellt das man dort durchfahren/ durchgehen kann.
278. Das geht nicht: dort befindet sich eine feste Absperrung.
279. Zumal es sich hier um private Grundstücke handelt, wo der allgemeine und öffentliche Zutritt nicht erlaubt ist.
280. Es verursacht hier sehr unschöne Probleme, weil sich Menschen auf dieses Kartenmaterial berufen.
281. Ich würde mich sehr freuen, wenn hier jemand ist, der das zeitnah korrigieren kann.
282. Vielen Dank</p>
283. </description>
284.      <dc:creator>BilleBu</dc:creator>
285.      <pubDate>Thu, 03 Jul 2025 10:04:43 +0000</pubDate>
286.      <comments>https://www.openstreetmap.org/user/BilleBu/diary/407022#comments</comments>
287.    </item>
288.    <item>
289.      <title>Черчение контуров зданий по фотографиям схем строек</title>
290.      <link>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021</link>
291.      <guid>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021</guid>
292.      <description>
293. <p dir="auto">Не высокая частота обновления спутниковых снимков, не всегда позволяет добавлять новые здания. В этой ситуации можно воспользоваться схемами с паспортов строек.
294. При перерисовке схемы возникает проблема, состоящая в том, что фотографии схем содержат искажение перспективы, которое надо как то исправлять. Ниже предложен не сложный способ того, как можно это сделать с помощью растрового графического редактора GIMP, векторного - Inkscape, а так же JOSM с установленным плагином <a href="https://wiki.openstreetmap.org/wiki/JOSM/Plugins/ImportVec" rel="nofollow noopener noreferrer">ImportVec</a>.</p>
295.  
296. <ul dir="auto">
297.  <li>
298.    <p dir="auto">На первом изображении видно искажение перспективы возникшее в результате отклонения фокальной плоскости фотокамеры относительно плоскости схемы стройки.</p>
299.  
300.    <p dir="auto"><img src="https://imgur.com/Ux0bc1A.png" alt="" loading="lazy"></p>
301.  </li>
302.  <li>
303.    <p dir="auto">Загружаем изображение в редактор GIMP, и в меню “Вид” включаем отображение сетки</p>
304.  
305.    <p dir="auto"><img src="https://imgur.com/kGgiu2X.png" alt="" loading="lazy"></p>
306.  </li>
307.  <li>
308.    <p dir="auto">Далее с помощью инструмента 3D преобразование или Перспектива, совмещаем прямоугольные границы рамки паспорта, с направляющими сетки так, что бы горизонтальные линии плаката совпали с горизонтальными линиями сетки, а вертикальные, с вертикальными. Для наклона изображения следует зажимать клавишу Ctrl. В результате мы должны получить вполне правильный прямоугольник.  После этого, можно обрезать лишние края, и добавить контрастности изображения для увеличения чёткости линий.
309. Тут важно отметить, что на фото обязательно должен быть виден весь паспорт, а не только его часть со схемой, поскольку выравнивание происходит по прямоугольной форме края его рамки.
310.  <img src="https://imgur.com/gOP4ouC.png" alt="" loading="lazy"></p>
311.  </li>
312.  <li>
313.    <p dir="auto">Сохраняем изображение, и открываем его в редакторе Inkscape. Теперь необходимо обвести контуры здания.  Так же следует обвести контуры уже существующих зданий, границ и дорог, для того что бы по этими линиями можно было привязаться к уже существующим объектам карты в JOSM. Сохраняем результат в SVG, не забыв перед этим удалить из файла растровую подложку.</p>
314.  
315.    <p dir="auto"><img src="https://i.imgur.com/D1JxXCI.png" alt="" loading="lazy"></p>
316.  </li>
317.  <li>
318.    <p dir="auto">Загружаем в JOSM данные OSM интересующего нас участка</p>
319.  
320.    <p dir="auto"><img src="https://i.imgur.com/Pr5nLMy.png" alt="" loading="lazy"></p>
321.  </li>
322.  <li>
323.    <p dir="auto">Далее, поверх него создаём новый пустой слой, и перетаскиваем (d&d) на него полученный SVG файл.  Как видно на скриншоте, масштаб и положение линий не совпадают со слоем загруженных данных.</p>
324.  
325.    <p dir="auto"><img src="https://i.imgur.com/auKMZsK.png" alt="" loading="lazy"></p>
326.  </li>
327.  <li>
328.    <p dir="auto">Теперь выделяем все линии, и с помощью масштабирования, и поворота, добиваемся совмещения линий дорог и зданий которые мы обвели, с уже существующими объектами карты, и фотоподложки.</p>
329.  
330.    <p dir="auto"><img src="https://i.imgur.com/cgDZW1q.png" alt="" loading="lazy"></p>
331.  </li>
332.  <li>
333.    <p dir="auto">Выделяем контур интересующего нас здания, копируем его ( ctrl+c), и переключившись на слой с данными OSM вставляем (ctrl+v).   Контур будет вставлен в редактируемый слой, но не на то же место где он находился в его родном слое. Это легко исправить простым перетаскиванием, до совпадения с полупрозрачным контуром этого же объекта в другом слое, где мы его выровняли. Остаётся добавить тэги, и выгрузить данные в OSM.
334.  <img src="https://i.imgur.com/sGlKPjq.png" alt="" loading="lazy"></p>
335.  </li>
336. </ul>
337.  
338. <p dir="auto">Таким способом можно достаточно просто и быстро переносить данные со схем строящихся зданий, дорог и других объектов.</p>
339. </description>
340.      <dc:creator>solenoid jam</dc:creator>
341.      <pubDate>Thu, 03 Jul 2025 03:38:07 +0000</pubDate>
342.      <comments>https://www.openstreetmap.org/user/solenoid%20jam/diary/407021#comments</comments>
343.    </item>
344.    <item>
345.      <title>غذای سالم</title>
346.      <link>https://www.openstreetmap.org/user/Dietfoodgym/diary/407019</link>
347.      <guid>https://www.openstreetmap.org/user/Dietfoodgym/diary/407019</guid>
348.      <description>&lt;p dir="auto"&gt;داشتن یه برنامه غذایی سالم شمارو از تک تک مریضی ها حفظ و یه بدنت کامل سالم به خودتون هدیه میدین کافیه با ما تماس بگیرید و برنامه غذایی اون رو درب منزل دریافت کنید&lt;/p&gt;
349. </description>
350.      <dc:creator>Dietfoodgym</dc:creator>
351.      <pubDate>Wed, 02 Jul 2025 06:26:31 +0000</pubDate>
352.      <comments>https://www.openstreetmap.org/user/Dietfoodgym/diary/407019#comments</comments>
353.      <geo:lat>35.58129418751151</geo:lat>
354.      <geo:long>53.37161993263226</geo:long>
355.      <georss:point>35.58129418751151 53.37161993263226</georss:point>
356.    </item>
357.    <item>
358.      <title>Capturing the whole city of Salzburg in 360°: Better Mounting, Better Coverage (Part 3)</title>
359.      <link>https://www.openstreetmap.org/user/Negreheb/diary/407018</link>
360.      <guid>https://www.openstreetmap.org/user/Negreheb/diary/407018</guid>
361.      <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;
362. Part 2: <a href="https://www.openstreetmap.org/user/Negreheb/diary/406030" rel="nofollow noopener noreferrer" dir="auto">osm.org/user/Negreheb/diary/406030</a></p>
363.  
364. <h1 dir="auto" id="mapping-salzburg--update-3-better-mounting-better-coverage">360° Mapping Salzburg – Update #3: Better Mounting, Better Coverage</h1>
365.  
366. <p dir="auto">Hello OSM Community,</p>
367.  
368. <p dir="auto">I’m continuing my effort to capture 360° images of the city of Salzburg for use in <strong>Mapillary</strong> and <strong>Panoramax</strong>. The goal remains the same: improve OpenStreetMap data, especially in areas with unresolved notes where better visual context can help.</p>
369.  
370. <h2 dir="auto" id="progress-so-far">Progress So Far</h2>
371.  
372. <p dir="auto">Here’s the current state of coverage from my 360° image collection:</p>
373.  
374. <p dir="auto"><img src="https://i.imgur.com/dtzhAHQ.png" alt="Salzburg" loading="lazy"></p>
375.  
376. <h2 dir="auto" id="my-route-planning-setup">My Route Planning Setup</h2>
377.  
378. <p dir="auto">To plan my routes, I’ve been using <strong>OSMAnd’s</strong> 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.</p>
379.  
380. <p dir="auto">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.</p>
381.  
382. <h2 dir="auto" id="managing-photos-for-upload">Managing Photos for Upload</h2>
383.  
384. <p dir="auto">On the photo management side, I’ve kept my setup from last time: using the <strong>command-line tools</strong> from both <strong>Mapillary</strong> and <strong>Panoramax</strong>. They continue to work flawlessly and are far more stable and efficient than the GUI options.</p>
385.  
386. <p dir="auto">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.</p>
387.  
388. <h2 dir="auto" id="whats-changed-since-the-last-post">What’s Changed Since the Last Post</h2>
389.  
390. <p dir="auto">One major improvement: I switched from a <strong>helmet-mounted camera</strong> to a <strong>selfie stick mounted directly on my bicycle</strong>. This setup means I can now look around naturally (better safety) while riding without affecting the camera’s field of view.</p>
391.  
392. <p dir="auto"><img src="https://i.imgur.com/MC0uazr.jpeg" alt="Clamping-Setup" loading="lazy"></p>
393.  
394. <p dir="auto">Additionally, I’ve started adding a <strong>nadir</strong> - 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 <a href="https://www.trekview.org/blog/adding-a-custom-nadir-to-360-video-photo/" rel="nofollow noopener noreferrer">Trek View</a> to make this happen.</p>
395.  
396. <p dir="auto"><a href="https://www.mapillary.com/app/user/OidaHeast?lat=47.7931037&lng=13.0470726&z=17&all_coverage=false&pKey=1147948973437204&focus=photo" rel="nofollow noopener noreferrer">Example picutre with Nadir on Mapillary</a></p>
397.  
398. <h2 dir="auto" id="reflections-on-the-new-setup">Reflections on the New Setup</h2>
399.  
400. <p dir="auto">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.</p>
401.  
402. <h2 dir="auto" id="whats-next">What’s Next?</h2>
403.  
404. <p dir="auto">My goal remains ambitious: to <strong>capture all of Salzburg</strong>, street by street, and make the imagery available to everyone through <strong>Mapillary</strong> and <strong>Panoramax</strong>. I believe this kind of street-level imagery can benefit the entire OSM community—locally and beyond.</p>
405.  
406. <p dir="auto">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!</p>
407. </description>
408.      <dc:creator>Negreheb</dc:creator>
409.      <pubDate>Tue, 01 Jul 2025 18:24:45 +0000</pubDate>
410.      <comments>https://www.openstreetmap.org/user/Negreheb/diary/407018#comments</comments>
411.      <geo:lat>47.80969602390851</geo:lat>
412.      <geo:long>13.050178525736555</geo:long>
413.      <georss:point>47.80969602390851 13.050178525736555</georss:point>
414.    </item>
415.    <item>
416.      <title>Is There Any news about Satellite Imagery ?</title>
417.      <link>https://www.openstreetmap.org/user/farhadGuli/diary/407015</link>
418.      <guid>https://www.openstreetmap.org/user/farhadGuli/diary/407015</guid>
419.      <description>&lt;p dir="auto"&gt;Dear OSM Community and Team,
420. 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.</p>
421. </description>
422.      <dc:creator>farhadGuli</dc:creator>
423.      <pubDate>Tue, 01 Jul 2025 09:56:25 +0000</pubDate>
424.      <comments>https://www.openstreetmap.org/user/farhadGuli/diary/407015#comments</comments>
425.    </item>
426.    <item>
427.      <title>Better OSM Diary : ideas, reflexions, improvements</title>
428.      <link>https://www.openstreetmap.org/user/Koreller/diary/407012</link>
429.      <guid>https://www.openstreetmap.org/user/Koreller/diary/407012</guid>
430.      <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;
431.  
432. <p dir="auto">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 “<a href="https://github.com/openstreetmap/openstreetmap-website/issues/3785" rel="nofollow noopener noreferrer">Reimagining the OSM.org</a>” or “<a href="https://github.com/deevroman/better-osm-org" rel="nofollow noopener noreferrer">Better-osm-org</a>” but without the technical side.</p>
433.  
434. <p dir="auto">This diary is a proposal, a reflection. Its aim is to offer a vision of what diaries might look like in the future.</p>
435.  
436. <h2 dir="auto" id="observation">Observation</h2>
437. <p dir="auto">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.</p>
438.  
439. <p dir="auto">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.).</p>
440.  
441. <p dir="auto">The aim is to offer ways to find interesting diaries more easily, to know which ones the community values or finds interesting.</p>
442.  
443. <h2 dir="auto" id="proposal">Proposal</h2>
444.  
445. <h3 dir="auto" id="categorise">Categorise</h3>
446. <p dir="auto">Allowing diaries to be categorised offers several advantages:</p>
447.  
448. <ul dir="auto">
449.  <li>Easier to identify the topic(s) of a diary</li>
450.  <li>Have a list of diaries talking of a specific topic</li>
451.  <li>Easier to find a specific diary</li>
452. </ul>
453.  
454. <p dir="auto">A category would group together several diaries addressing the same theme.</p>
455.  
456. <p dir="auto">This categorisation might be done in the form of keywords, for example: #tutorial #josm #streetcomplete #sotm #telecom #esri.</p>
457.  
458. <h3 dir="auto" id="add-upvotes">Add upvotes</h3>
459. <p dir="auto">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.</p>
460.  
461. <p dir="auto">The same options for comments might be used to highlight the comments most appreciated by the community.</p>
462.  
463. <p dir="auto">This system would be very similar to GitLab for issues, or Reddit for content.</p>
464.  
465. <p dir="auto"><img src="https://i.postimg.cc/nrvMkf6F/Git-Lab-Reddit-vote.jpg" alt="GitLab and Reddit upvotes downvotes and reactions" loading="lazy"></p>
466.  
467. <h3 dir="auto" id="diaries-search">Diaries search</h3>
468.  
469. <p dir="auto">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.</p>
470.  
471. <h3 dir="auto" id="community-diaries--share-a-landing-page-for-diaries">“Community Diaries > Share” a landing page for diaries</h3>
472. <p dir="auto"><img src="https://i.postimg.cc/G37qvwbP/Community-Diaries-Share.jpg" alt="Community Diaries Share" loading="lazy"></p>
473.  
474. <h3 dir="auto" id="community-diaries--explore-a-page-for-curating-diaries">“Community Diaries > Explore” a page for curating diaries</h3>
475. <p dir="auto"><img src="https://i.postimg.cc/TYhTfDdV/Community-Diaries-Explore.jpg" alt="Community Diaries Explore" loading="lazy"></p>
476. </description>
477.      <dc:creator>Koreller</dc:creator>
478.      <pubDate>Tue, 01 Jul 2025 08:36:55 +0000</pubDate>
479.      <comments>https://www.openstreetmap.org/user/Koreller/diary/407012#comments</comments>
480.    </item>
481.    <item>
482.      <title>Kann Karten nicht mehr drucken!</title>
483.      <link>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</link>
484.      <guid>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010</guid>
485.      <description>&lt;p dir="auto"&gt;Kann Karten nicht mehr drucken!&lt;/p&gt;
486. </description>
487.      <dc:creator>FrankBuchholz</dc:creator>
488.      <pubDate>Mon, 30 Jun 2025 09:44:39 +0000</pubDate>
489.      <comments>https://www.openstreetmap.org/user/FrankBuchholz/diary/407010#comments</comments>
490.    </item>
491.    <item>
492.      <title>Editing</title>
493.      <link>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</link>
494.      <guid>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009</guid>
495.      <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
496. I went ahead and edited my villages by adding the various buildings and trees that haven’t been mapped yet</p>
497. </description>
498.      <dc:creator>Ofoyrwoth</dc:creator>
499.      <pubDate>Mon, 30 Jun 2025 09:30:21 +0000</pubDate>
500.      <comments>https://www.openstreetmap.org/user/Ofoyrwoth/diary/407009#comments</comments>
501.      <geo:lat>0.055702319934704085</geo:lat>
502.      <geo:long>32.466012239428835</geo:long>
503.      <georss:point>0.055702319934704085 32.466012239428835</georss:point>
504.    </item>
505.    <item>
506.      <title>Ventura Plaza</title>
507.      <link>https://www.openstreetmap.org/user/Ingeniero43/diary/407006</link>
508.      <guid>https://www.openstreetmap.org/user/Ingeniero43/diary/407006</guid>
509.      <description>&lt;p dir="auto"&gt;Centro comercial&lt;/p&gt;
510. </description>
511.      <dc:creator>Ingeniero43</dc:creator>
512.      <pubDate>Mon, 30 Jun 2025 02:42:23 +0000</pubDate>
513.      <comments>https://www.openstreetmap.org/user/Ingeniero43/diary/407006#comments</comments>
514.      <geo:lat>7.888399253680378</geo:lat>
515.      <geo:long>-72.4968963861466</geo:long>
516.      <georss:point>7.888399253680378 -72.4968963861466</georss:point>
517.    </item>
518.  </channel>
519. </rss>
520.  

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):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//www.openstreetmap.org/diary/rss"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

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