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 24, column 0: description should not contain loading attribute (8 occurrences) [help]

  <p dir="auto"><img src="https://dvi0dlx39lw11.cloudfront.net/road_s ...
  

• line 1483, 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>Shire Roads - No Footpaths</title>
16.      <link>https://www.openstreetmap.org/user/FrodoMappins/diary/407700</link>
17.      <guid>https://www.openstreetmap.org/user/FrodoMappins/diary/407700</guid>
18.      <description>&lt;p dir="auto"&gt;Ok, my good friend Butterball wanted to pay me a visit from Bree.  You all know how he is, super braggy. He told me he just got a brand new iPhone version 1 with 20 KB of RAM. I was like, “Okay, cool, Butterball. We’ll see you. Just don’t be braggy.”&lt;/p&gt;
19.  
20. <p dir="auto">He wrote me a long letter promising me that he wouldn’t be braggy, but then he told me about a problem that he had. He had too many footpaths coming up on his map. He couldn’t find the way easily.  Every time he brought up the map, his iPhone crashed. Check out the shire with all of the footpaths!</p>
21.  
22. <h2 dir="auto" id="crazy-map-with-footpaths">Crazy Map With Footpaths!</h2>
23.  
24. <p dir="auto"><img src="https://dvi0dlx39lw11.cloudfront.net/road_spec/too_many_roads.png" alt="dense shire map" loading="lazy"></p>
25.  
26. <p dir="auto">I told him, “Don’t worry, I’ll just modify his map with a new layer with just roads on it instead of all the other extra crap.”</p>
27.  
28. <p dir="auto">I was like, Open Street Map is pretty awesome, but they include a lot of stuff in their layers, and then they let you just claw back what you want. I think what we want to do is modify it so we only show the tags that we want, so your map doesn’t crash. Does that sound like a good plan?</p>
29.  
30. <p dir="auto">Two months later, I got a reply from Butterball in a long letter where he said, “Yeah, that sounds good. Send me over the new map spec.”</p>
31.  
32. <p dir="auto">Month I started planning this workout. What I did was I went to OpenStreetMap, of course. And then I looked at how they mapped roads.   I use the concept of high-wage, which has everything on it. Foot-passed is my number one problem, so I only wanted to pull back a subset of what I wanted.</p>
33.  
34. <h2 dir="auto" id="simple-map-with-just-main-roads">Simple Map With Just Main Roads</h2>
35.  
36. <p dir="auto">It was simple.. all I did was add this filter over the shire using <a href="https://overpass-turbo.eu/" rel="nofollow noopener noreferrer">Overpass</a>.</p>
37.  
38. <pre dir="auto"><code>[out:json];
39. (
40.  way["highway"="motorway"]({{bbox}});
41.  way["highway"="trunk"]({{bbox}});
42.  way["highway"="primary"]({{bbox}});
43.  way["highway"="secondary"]({{bbox}});
44.  way["highway"="tertiary"]({{bbox}});
45.  way["highway"="unclassified"]({{bbox}});
46.  way["highway"="residential"]({{bbox}});
47.  way["highway"="motorway_link"]({{bbox}});
48.  way["highway"="trunk_link"]({{bbox}});
49.  way["highway"="primary_link"]({{bbox}});
50.  way["highway"="secondary_link"]({{bbox}});
51.  way["highway"="tertiary_link"]({{bbox}});
52.  way["highway"="service"]({{bbox}});
53.  way["highway"="living_street"]({{bbox}});
54. );
55. out geom;
56. </code></pre>
57.  
58. <p dir="auto">I then exported the GeoJSON and uploaded it into the new map server I built.  Then all I did was simply do a Docker build, and I deployed my new map server to a map that I had built using ArgonathWebServices and Bam… he could see what he needed without all of the fuss!</p>
59.  
60. <p dir="auto"><img src="https://dvi0dlx39lw11.cloudfront.net/road_spec/simplified.png" alt="New decluttered map!" loading="lazy"></p>
61.  
62. <p dir="auto">I don’t want to bore you with the whole file, but here’s a cool snapshot.</p>
63.  
64. <pre dir="auto"><code>{
65.  "type": "FeatureCollection",
66.  "generator": "overpass-turbo",
67.  "copyright": "The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.",
68.  "timestamp": "2025-11-04T14:44:54Z",
69.  "features": [
70.    {
71.      "type": "Feature",
72.      "properties": {
73.        "@id": "way/88016159",
74.        "access": "private",
75.        "highway": "service",
76.        "maxspeed": "30",
77.        "surface": "gravel"
78.      },
79.      "geometry": {
80.        "type": "LineString",
81.        "coordinates": [
82.          [
83.            175.6827828,
84.            -37.8715179
85.          ],
86.          [
87.            175.6827449,
88.            -37.8714729
89.          ],
90.          [
91.            175.682637,
92.            -37.8713327
93.          ],
94.          [
95.            175.682593,
96.            -37.8712624
97.          ],
98.          [
99.  
100. </code></pre>
101.  
102. </description>
103.      <dc:creator>FrodoMappins</dc:creator>
104.      <pubDate>Tue, 04 Nov 2025 14:18:35 +0000</pubDate>
105.      <comments>https://www.openstreetmap.org/user/FrodoMappins/diary/407700#comments</comments>
106.    </item>
107.    <item>
108.      <title>Projeto Mapeia Brasil - Mapeia Brasil Project  - 2025/2026</title>
109.      <link>https://www.openstreetmap.org/user/raphaelmirc/diary/407698</link>
110.      <guid>https://www.openstreetmap.org/user/raphaelmirc/diary/407698</guid>
111.      <description>&lt;p dir="auto"&gt;🚀 Projeto Mapeia Brasil - Mapeia Brasil Project&lt;/p&gt;
112.  
113. <p dir="auto"><img src="https://i.imgur.com/o3ZT9a9.png" alt="" loading="lazy"></p>
114.  
115. <h1 dir="auto" id="histria-do-projeto">História do Projeto</h1>
116.  
117. <p dir="auto">O Mapeia Brasil é um projeto que surgiu com a missão de melhorar a qualidade dos dados geográficos no Brasil, com foco na atualização e correção dos nomes das ruas e vias no OpenStreetMap (OSM). A ideia foi originada em 2025, após uma análise comparativa entre os dados do OSM e os dados do IBGE (Instituto Brasileiro de Geografia e Estatística), especificamente do Censo de 2022. Durante esse processo, foi identificado que 13 cidades brasileiras precisavam urgentemente de atualizações nos seus dados de vias. O projeto visa corrigir essas informações para melhorar a navegação, os serviços públicos e facilitar o uso de aplicativos de transporte, compras online e outros serviços essenciais.</p>
118.  
119. <p dir="auto">Esses dados estarão disponíveis publicamente para todos, com acesso por meio da Wiki do projeto, e com uma licença aberta que pode ser utilizada por qualquer usuário para realizar o mapeamento e atualização no OSM. Para garantir que as cidades que precisam dessa atualização possam ser facilmente mapeadas e disponibilizadas de forma eficiente, a equipe do Mapeia Brasil está utilizando o editor JOSM (Java OpenStreetMap Editor), uma das ferramentas mais poderosas para edição no OSM, que possibilita o mapeamento colaborativo e preciso.
120. Objetivo</p>
121.  
122. <p dir="auto">O objetivo principal do Mapeia Brasil é garantir que os dados do IBGE, relativos ao Censo de 2022, sejam atualizados diretamente no OpenStreetMap para as 13 cidades selecionadas. Essas cidades são: Goiânia, Teresina, Rio Branco, Manaus, Salvador, João Pessoa, São Luís, Jaboatão dos Guararapes, Aracaju, Natal, Maceió, Belo Horizonte e São José do Rio Preto. Com a atualização desses dados, buscamos disponibilizá-los para aplicativos de transporte, serviços públicos, e-commerce e outros serviços que dependem de dados de ruas precisos.</p>
123.  
124. <p dir="auto">A ideia é também envolver mapeadores locais, que serão capacitados por meio de oficinas presenciais e online para colaborar no mapeamento das vias dessas cidades. O projeto não apenas visa corrigir os dados, mas também assegurar que as cidades brasileiras estejam totalmente mapeadas e com os dados mais recentes disponíveis no OSM.
125. Metodologia</p>
126.  
127. <p dir="auto">A metodologia adotada pelo projeto Mapeia Brasil é colaborativa, envolvendo diversas etapas:</p>
128.  
129. <pre dir="auto"><code>Capacitação dos Mapeadores Locais: Será feita por meio de oficinas presenciais e online, nas quais os participantes aprenderão como usar a ferramenta JOSM e outras ferramentas relacionadas ao OpenStreetMap. Essas oficinas irão equipar os mapeadores locais com o conhecimento necessário para realizar as edições de forma correta e eficaz.
130. Mapeamento Colaborativo: O mapeamento será feito diretamente no OpenStreetMap. A plataforma oferece uma interface intuitiva e acessível para os usuários, que poderão contribuir diretamente com a atualização dos dados.
131. Uso de Hashtags Oficiais: Para garantir o rastreamento e a organização do trabalho, será utilizado o uso de hashtags específicas, tanto para o projeto quanto para cada cidade mapeada. O uso das hashtags facilitará o acompanhamento do progresso e a verificação das contribuições realizadas por cada mapeador.
132. </code></pre>
133.  
134. <p dir="auto">As principais hashtags são:</p>
135.  
136. <pre dir="auto"><code>#MapeiaBrasil para o projeto geral.
137. #Mapeia[Cidade] para cada cidade mapeada (por exemplo, #MapeiaGoiânia, #MapeiaTeresina etc.).
138. </code></pre>
139.  
140. <p dir="auto">Dessa forma, qualquer alteração feita por um mapeador poderá ser rapidamente identificada e monitorada, tornando o processo de mapeamento transparente e eficiente.
141. Fonte de Dados</p>
142.  
143. <p dir="auto">Os dados usados para o mapeamento vêm do IBGE, que os disponibiliza sob a licença DDDL (Data Documentation License). A DDDL permite que os dados sejam livres para uso, distribuição e modificação, o que garante que qualquer pessoa possa utilizá-los para realizar as correções e atualizações necessárias.</p>
144.  
145. <p dir="auto">O link para os arquivos dos dados utilizados no projeto pode ser encontrado aqui: Link para os Arquivos
146. <a href="https://mapeiabrasil.mapaslivre.com.br/" rel="nofollow noopener noreferrer" dir="auto">https://mapeiabrasil.mapaslivre.com.br/</a></p>
147.  
148. </description>
149.      <dc:creator>raphaelmirc</dc:creator>
150.      <pubDate>Tue, 04 Nov 2025 13:17:49 +0000</pubDate>
151.      <comments>https://www.openstreetmap.org/user/raphaelmirc/diary/407698#comments</comments>
152.      <geo:lat>-12.32282821258808</geo:lat>
153.      <geo:long>-46.0546875</geo:long>
154.      <georss:point>-12.32282821258808 -46.0546875</georss:point>
155.    </item>
156.    <item>
157.      <title>Why is showing pedestrian crossings so complicated?</title>
158.      <link>https://www.openstreetmap.org/user/SomeoneElse/diary/407696</link>
159.      <guid>https://www.openstreetmap.org/user/SomeoneElse/diary/407696</guid>
160.      <description>&lt;p dir="auto"&gt;&lt;img src="https://map.atownsend.org.uk/tmp/Screenshot_20251103_231242.png" alt="A map of part of London" loading="lazy"&gt;&lt;/p&gt;
161.  
162. <p dir="auto">I have a couple of web maps, and they are supposed to show pedestrian crossings.  If there’s some crossing infrastructure (for example - zebra stripes, or tactile paving and a lowered kerb) you’re supposed to see a “crossing” icon.  If there are traffic signals associated with the crossing, that icon should be replaced with a “traffic signals” one.</p>
163.  
164. <p dir="auto">Years ago it was straightforward - you’d get a <code dir="auto">highway=crossing</code> tag on a node on the roadway, and there would be another tag, such as <code dir="auto">crossing_ref</code> to say what sort of crossing it was.  Some crossings (such as pelican, puffin and pegasus) have traffic signals; others (zebra and informal crossings) tend not to.</p>
165.  
166. <p dir="auto">Unfortunately, it has got a lot more complicated.</p>
167.  
168. <p dir="auto">Sometimes, the <code dir="auto">highway</code> tag is <a href="https://taginfo.openstreetmap.org/tags/highway=crossing%3Btraffic_signals" rel="nofollow noopener noreferrer"><code dir="auto">crossing;<something></code></a> or <a href="https://taginfo.openstreetmap.org/tags/highway=stop%3Bcrossing" rel="nofollow noopener noreferrer"><code dir="auto"><something>;crossing</code></a>.  Sometimes that <code dir="auto">something</code> should be ignored and treated as a crossing.</p>
169.  
170. <p dir="auto">Some crossings are added with <code dir="auto">crossing=<something></code> but <a href="https://overpass-turbo.eu/s/2eR1" rel="nofollow noopener noreferrer">without any <code dir="auto">highway=crossing</code></a> tag.  Of course I <em>could</em> just look for that, but in addition to <code dir="auto">highway=crossing</code> I now also need to think about <a href="https://overpass-turbo.eu/s/2eR2" rel="nofollow noopener noreferrer"><code dir="auto">railway=crossing</code></a> (and <code dir="auto">tram_crossing</code>) and handle those separately (in my case, like level crossings).  I also need to look for <a href="https://overpass-turbo.eu/s/2eR3" rel="nofollow noopener noreferrer"><code dir="auto">disused:highway=crossing</code></a> and exclude those, even if a <code dir="auto">crossing</code> tag is set.  If <a href="https://overpass-turbo.eu/s/2eR4" rel="nofollow noopener noreferrer"><code dir="auto">highway</code> is set to <code dir="auto">something</code> that is not <code dir="auto">crossing</code></a>, I probably should treat the object as whatever that <code dir="auto">something</code> is rather than a <code dir="auto">crossing</code>.</p>
171.  
172. <p dir="auto">Attributes of crossings are often added with semicolon tags such as <a href="https://overpass-turbo.eu/s/2eR5" rel="nofollow noopener noreferrer"><code dir="auto">crossing:markings</code></a>, <a href="https://overpass-turbo.eu/s/2eR6" rel="nofollow noopener noreferrer"><code dir="auto">crossing:island</code></a>, <a href="https://overpass-turbo.eu/s/2eR7" rel="nofollow noopener noreferrer"><code dir="auto">crossing:signals</code></a> (and for <code dir="auto">railway</code> crossings <code dir="auto">crossing:barrier</code>, <code dir="auto">crossing:bell</code> etc.), and also tags such as <a href="https://overpass-turbo.eu/s/2eR8" rel="nofollow noopener noreferrer"><code dir="auto">crossing_ref</code></a> (which is still around) and <code dir="auto">tactile_paving</code>.</p>
173.  
174. <p dir="auto">Alas, sometimes attributes such as <a href="https://overpass-turbo.eu/s/2eRa" rel="nofollow noopener noreferrer"><code dir="auto">crossing:markings</code></a> can occur without a <code dir="auto">crossing</code> tag, and in that case that’s a pretty good indicator that the object with that tag is a crossing.  However, what about <a href="https://overpass-turbo.eu/s/2eRb" rel="nofollow noopener noreferrer"><code dir="auto">crossing:island</code></a>?  There’s a whole <a href="https://community.openstreetmap.org/t/poll-separately-mapped-traffic-islands-and-crossing-island/137438" rel="nofollow noopener noreferrer">forum thread</a> about that right now (it actually seems to be sometimes used to tag <em>part</em> of a crossing).  In addition, tags such as <code dir="auto">crossing:markings</code> will have <a href="https://overpass-turbo.eu/s/2eRc" rel="nofollow noopener noreferrer">“negative”</a> values (ones that should be treated as if there <em>aren’t</em> crossing markings) and those negative values aren’t always <code dir="auto">no</code>.  Of course, each individual <code dir="auto">crossing:</code> tag that I am interested in needs to be checked separately.</p>
175.  
176. <p dir="auto">Once we’ve worked out that there is a crossing here, we need to see if it has traffic signals.  That requires checking values in three different tags (<code dir="auto">crossing</code>, <code dir="auto">crossing_ref</code> and <code dir="auto">crossing:signals</code>) and in the case of <code dir="auto">crossing</code>, that includes some semicolon combinations.</p>
177.  
178. <p dir="auto">Finally we want to <em>exclude</em> any crossings that we’ve got this far with that don’t really have any infrastructure (not even <code dir="auto">tactile_paving</code>) - if someone has added <code dir="auto">highway=crossing</code> but then explictly said “there is no infrastructure here” we shouldn’t show it as a crossing, because it isn’t one really.</p>
179.  
180. <p dir="auto">All in all, that’s about <a href="https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/shared_lua.lua#L7369" rel="nofollow noopener noreferrer">200 lines of lua</a>.</p>
181.  
182. <p dir="auto">Surely things don’t need to be that complicated?</p>
183. </description>
184.      <dc:creator>SomeoneElse</dc:creator>
185.      <pubDate>Mon, 03 Nov 2025 23:19:39 +0000</pubDate>
186.      <comments>https://www.openstreetmap.org/user/SomeoneElse/diary/407696#comments</comments>
187.      <geo:lat>51.48411</geo:lat>
188.      <geo:long>-0.1843</geo:long>
189.      <georss:point>51.48411 -0.1843</georss:point>
190.    </item>
191.    <item>
192.      <title>Reflections on My OpenStreetMap Editing Experience</title>
193.      <link>https://www.openstreetmap.org/user/ronjaaaaa/diary/407694</link>
194.      <guid>https://www.openstreetmap.org/user/ronjaaaaa/diary/407694</guid>
195.      <description>&lt;p dir="auto"&gt;One of the most important things I learned about mapping with OpenStreetMap is how collaborative and detailed the global mapping community is. Every edit, no matter how small, contributes to a shared, constantly evolving map that supports navigation, humanitarian efforts, and local development. I realized how crucial accuracy and verification are, each feature needs to be placed and tagged correctly so that it’s useful for others. The most challenging part of editing OSM was learning the tagging system and ensuring that my edits followed mapping conventions. I mainly mapped in areas that lacked detailed data. Overall, the experience showed me how open data and collective participation can create powerful geographic resources that benefit communities around the world.&lt;/p&gt;
196. </description>
197.      <dc:creator>ronjaaaaa</dc:creator>
198.      <pubDate>Mon, 03 Nov 2025 17:40:24 +0000</pubDate>
199.      <comments>https://www.openstreetmap.org/user/ronjaaaaa/diary/407694#comments</comments>
200.      <geo:lat>52.25397321468939</geo:lat>
201.      <geo:long>11.614346981114068</geo:long>
202.      <georss:point>52.25397321468939 11.614346981114068</georss:point>
203.    </item>
204.    <item>
205.      <title>Why have I mapped what I have so far? </title>
206.      <link>https://www.openstreetmap.org/user/MappingGuy25/diary/407693</link>
207.      <guid>https://www.openstreetmap.org/user/MappingGuy25/diary/407693</guid>
208.      <description>
209. <p dir="auto">I edited an area where I grew up and frequently return. I chose to focus on some features in this area, as I figured some would be missing or incorrect due to fewer resources to investigate them and their lower priority given the town’s smaller size. I decided to start with elements I knew were recent in the town, such as the opening, closing, or rebranding of businesses. Then I moved into land-use elements, as some areas were assigned to a broader category when a more specific use could be assigned. I updated some other features as well, like microfeatures in Murphy Park and Canada Post mailboxes, but I mainly focused on businesses and updating the elements around them. I learned that, in OSM, you can get a lot more detail on land use in an area, which I thought was a really nice feature. One of the challenges for me was finding the aforementioned resources. If I had not frequented this area, it would be difficult for me to understand what to update or add, as the larger mapping services are also outdated. I foresee this as a challenge with OSM: without someone in a small town committed to making changes, they will slowly lag behind the already slow giants in the industry.</p>
210. </description>
211.      <dc:creator>MappingGuy25</dc:creator>
212.      <pubDate>Mon, 03 Nov 2025 17:26:52 +0000</pubDate>
213.      <comments>https://www.openstreetmap.org/user/MappingGuy25/diary/407693#comments</comments>
214.      <geo:lat>44.89740009288783</geo:lat>
215.      <geo:long>-76.02066993713379</geo:long>
216.      <georss:point>44.89740009288783 -76.02066993713379</georss:point>
217.    </item>
218.    <item>
219.      <title>Diary Entry</title>
220.      <link>https://www.openstreetmap.org/user/egknauff/diary/407692</link>
221.      <guid>https://www.openstreetmap.org/user/egknauff/diary/407692</guid>
222.      <description>&lt;p dir="auto"&gt;The areas I mapped are familiar to me, so I was able to add new things that haven’t been marked on OpenStreetMap before. The most important thing about OpenStreetMap, to me at least, is how much contribution is needed to keep everything accurate and up to date. There were some edits in that area that were made 15 years ago, some that haven’t been modified to accurately display the area (under LuLu’s Variety, the block of houses is labelled as a park 15 years ago, when it isn’t a park now). The most challenge I had while editing was trying to accurately name certain buildings. For example, Itec Equipment is a building material supply store, but there weren’t any labels like “Supply Store” or “Building Supply Store”; the best I could label it with was “Rural Supplies Store, but I’m not sure if that is accurate.&lt;/p&gt;
223. </description>
224.      <dc:creator>egknauff</dc:creator>
225.      <pubDate>Mon, 03 Nov 2025 15:12:48 +0000</pubDate>
226.      <comments>https://www.openstreetmap.org/user/egknauff/diary/407692#comments</comments>
227.    </item>
228.    <item>
229.      <title>Contributing to Open Street maps</title>
230.      <link>https://www.openstreetmap.org/user/aramimaidana/diary/407691</link>
231.      <guid>https://www.openstreetmap.org/user/aramimaidana/diary/407691</guid>
232.      <description>&lt;p dir="auto"&gt;For this OpenStreetMap activity I focused on adding and improving features in an area I am familar with. I contributed information based on places I know, such as my University campus, which made the mapping process both meaningful and interesting to me. I think it is very important to share accurate and local information in OSM, because small details can make a big difference. I also noticed that some information around my area is outdated or incomplete, so in the future I would like to contribute more.&lt;/p&gt;
233. </description>
234.      <dc:creator>aramimaidana</dc:creator>
235.      <pubDate>Mon, 03 Nov 2025 14:53:10 +0000</pubDate>
236.      <comments>https://www.openstreetmap.org/user/aramimaidana/diary/407691#comments</comments>
237.    </item>
238.    <item>
239.      <title>Halifax Bus Route Notes</title>
240.      <link>https://www.openstreetmap.org/user/diwesser/diary/407690</link>
241.      <guid>https://www.openstreetmap.org/user/diwesser/diary/407690</guid>
242.      <description>&lt;p dir="auto"&gt;I seem to have started on the questionable task of adding all the bus routes in Halifax.&lt;/p&gt;
243.  
244. <p dir="auto">I’ve been grabbing the <a href="https://www.halifax.ca/transportation/halifax-transit/routes-schedules/route-descriptions" rel="nofollow noopener noreferrer">route description</a> from the Halifax Transit website, creating the route relations via Id and then adding to the relation with <a href="https://osm-simple-route-editor.kyle.kiwi/" rel="nofollow noopener noreferrer">OSM Simple Route Editor</a>. (I’d prefer to use <a href="https://relatify.monicz.dev/" rel="nofollow noopener noreferrer">OSM Relatify</a>, but it seems to take a while to notice that the relation has been created or is having some other issue.) I have been using Relatify to verify that the route is correctly ordered and connected. I have also used the sort feature in JOSM “PT Assistant” plugin to deal with grumpy route alignment.</p>
245.  
246. <p dir="auto">I have been doing inbound and outbound legs of the bus route as separate routes to avoid the complications from using the same way twice. In the case of the 1, they were already split like that with a master route that joined the two which seems rather elegant. But, it may be worth seeing if there is a way to join the halves together after the fact.</p>
247.  
248. <p dir="auto">Here’s the overpass-turbo query I cobbled together to find current OSM routes (it mostly worked):</p>
249.  
250. <pre dir="auto"><code>[out:json][timeout:25];
251. // gather results
252. (
253.  relation["type"="route"]["route"="bus"]["network:wikidata"="Q14875719"]({{bbox}});
254.  relation["type"="route"]["route"="bus"]["operator"="Halifax Regional Municipality"]({{bbox}});
255.  relation["type"="route"]["route"="bus"]["network"="Halifax Transit"]({{bbox}});
256. );
257. // print results
258. out meta geom;
259. </code></pre>
260.  
261. <p dir="auto">So far I have found these routes either in OSM or via the current list of route descriptions:</p>
262.  
263. <table dir="auto" class="table table-sm w-auto">
264.  <thead>
265.    <tr>
266.      <th>Relation ID</th>
267.      <th>Route</th>
268.      <th>Entire Route?</th>
269.      <th>Current Route?</th>
270.    </tr>
271.  </thead>
272.  <tbody>
273.    <tr>
274.      <td><a href="https://www.openstreetmap.org/relation/17135729" rel="nofollow noopener noreferrer">17135729</a></td>
275.      <td>1 Spring Garden</td>
276.      <td>Wrapper route for 8481012 and 17135728</td>
277.      <td> </td>
278.    </tr>
279.    <tr>
280.      <td><a href="https://www.openstreetmap.org/relation/17135728" rel="nofollow noopener noreferrer">17135728</a></td>
281.      <td>1 Spring Garden (To Bridge Terminal)</td>
282.      <td>Part of 1 Spring Garden (17135729)</td>
283.      <td> </td>
284.    </tr>
285.    <tr>
286.      <td><a href="https://www.openstreetmap.org/relation/8481012" rel="nofollow noopener noreferrer">8481012</a></td>
287.      <td>1 Spring Garden (To Mumford Terminal)</td>
288.      <td>Part of 1 Spring Garden (17135729)</td>
289.      <td> </td>
290.    </tr>
291.    <tr>
292.      <td><a href="https://www.openstreetmap.org/relation/19787536" rel="nofollow noopener noreferrer">19787536</a></td>
293.      <td>2 Fairview (To Lacewood Terminal)</td>
294.      <td>standalone</td>
295.      <td> </td>
296.    </tr>
297.    <tr>
298.      <td><a href="https://www.openstreetmap.org/relation/19787493" rel="nofollow noopener noreferrer">19787493</a></td>
299.      <td>2 Fairview (To Water Street Terminal)</td>
300.      <td>standalone</td>
301.      <td> </td>
302.    </tr>
303.    <tr>
304.      <td><a href="https://www.openstreetmap.org/relation/8481112" rel="nofollow noopener noreferrer">8481112</a></td>
305.      <td>2 Wedgewood</td>
306.      <td>standalone</td>
307.      <td> </td>
308.    </tr>
309.    <tr>
310.      <td> </td>
311.      <td>3</td>
312.      <td> </td>
313.      <td>Yes</td>
314.    </tr>
315.    <tr>
316.      <td><a href="https://www.openstreetmap.org/relation/8487359" rel="nofollow noopener noreferrer">8487359</a></td>
317.      <td>4 Rosedale</td>
318.      <td> </td>
319.      <td> </td>
320.    </tr>
321.    <tr>
322.      <td><a href="https://www.openstreetmap.org/relation/8487379" rel="nofollow noopener noreferrer">8487379</a></td>
323.      <td>5 Chebucto</td>
324.      <td> </td>
325.      <td> </td>
326.    </tr>
327.    <tr>
328.      <td><a href="https://www.openstreetmap.org/relation/8510891" rel="nofollow noopener noreferrer">8510891</a></td>
329.      <td>6A Woodside</td>
330.      <td> </td>
331.      <td> </td>
332.    </tr>
333.    <tr>
334.      <td> </td>
335.      <td>6B</td>
336.      <td> </td>
337.      <td>Yes</td>
338.    </tr>
339.    <tr>
340.      <td> </td>
341.      <td>6C</td>
342.      <td> </td>
343.      <td>Yes</td>
344.    </tr>
345.    <tr>
346.      <td><a href="https://www.openstreetmap.org/relation/8487423" rel="nofollow noopener noreferrer">8487423</a></td>
347.      <td>7 Robie</td>
348.      <td> </td>
349.      <td> </td>
350.    </tr>
351.    <tr>
352.      <td> </td>
353.      <td>7A</td>
354.      <td> </td>
355.      <td>Yes</td>
356.    </tr>
357.    <tr>
358.      <td> </td>
359.      <td>7B</td>
360.      <td> </td>
361.      <td>Yes</td>
362.    </tr>
363.    <tr>
364.      <td> </td>
365.      <td>8</td>
366.      <td> </td>
367.      <td>Yes</td>
368.    </tr>
369.    <tr>
370.      <td><a href="https://www.openstreetmap.org/relation/8487503" rel="nofollow noopener noreferrer">8487503</a></td>
371.      <td>9A Greystone</td>
372.      <td> </td>
373.      <td> </td>
374.    </tr>
375.    <tr>
376.      <td><a href="https://www.openstreetmap.org/relation/8487504" rel="nofollow noopener noreferrer">8487504</a></td>
377.      <td>9B Herring Cove</td>
378.      <td> </td>
379.      <td> </td>
380.    </tr>
381.    <tr>
382.      <td><a href="https://www.openstreetmap.org/relation/8487558" rel="nofollow noopener noreferrer">8487558</a></td>
383.      <td>10 Dalhousie</td>
384.      <td> </td>
385.      <td> </td>
386.    </tr>
387.    <tr>
388.      <td> </td>
389.      <td>10A</td>
390.      <td> </td>
391.      <td>Yes</td>
392.    </tr>
393.    <tr>
394.      <td> </td>
395.      <td>10B</td>
396.      <td> </td>
397.      <td>Yes</td>
398.    </tr>
399.    <tr>
400.      <td> </td>
401.      <td>10C</td>
402.      <td> </td>
403.      <td>Yes</td>
404.    </tr>
405.    <tr>
406.      <td><a href="https://www.openstreetmap.org/relation/8487590" rel="nofollow noopener noreferrer">8487590</a></td>
407.      <td>11 Dockyard</td>
408.      <td> </td>
409.      <td> </td>
410.    </tr>
411.    <tr>
412.      <td><a href="https://www.openstreetmap.org/relation/8490159" rel="nofollow noopener noreferrer">8490159</a></td>
413.      <td>14 Leiblin Park</td>
414.      <td> </td>
415.      <td> </td>
416.    </tr>
417.    <tr>
418.      <td><a href="https://www.openstreetmap.org/relation/6548527" rel="nofollow noopener noreferrer">6548527</a></td>
419.      <td>15 Purcells Cove</td>
420.      <td> </td>
421.      <td> </td>
422.    </tr>
423.    <tr>
424.      <td><a href="https://www.openstreetmap.org/relation/8490255" rel="nofollow noopener noreferrer">8490255</a></td>
425.      <td>17 Saint Marys</td>
426.      <td> </td>
427.      <td> </td>
428.    </tr>
429.    <tr>
430.      <td><a href="https://www.openstreetmap.org/relation/8490437" rel="nofollow noopener noreferrer">8490437</a></td>
431.      <td>18 Universities</td>
432.      <td> </td>
433.      <td> </td>
434.    </tr>
435.    <tr>
436.      <td><a href="https://www.openstreetmap.org/relation/5970948" rel="nofollow noopener noreferrer">5970948</a></td>
437.      <td>20</td>
438.      <td> </td>
439.      <td> </td>
440.    </tr>
441.    <tr>
442.      <td><a href="https://www.openstreetmap.org/relation/8490513" rel="nofollow noopener noreferrer">8490513</a></td>
443.      <td>21 Lakeside / Timberlea</td>
444.      <td> </td>
445.      <td> </td>
446.    </tr>
447.    <tr>
448.      <td><a href="https://www.openstreetmap.org/relation/8490634" rel="nofollow noopener noreferrer">8490634</a></td>
449.      <td>22 Armdale</td>
450.      <td> </td>
451.      <td> </td>
452.    </tr>
453.    <tr>
454.      <td><a href="https://www.openstreetmap.org/relation/8491228" rel="nofollow noopener noreferrer">8491228</a></td>
455.      <td>23 Timberlea / Mumford</td>
456.      <td> </td>
457.      <td> </td>
458.    </tr>
459.    <tr>
460.      <td> </td>
461.      <td>24</td>
462.      <td> </td>
463.      <td>Yes</td>
464.    </tr>
465.    <tr>
466.      <td> </td>
467.      <td>25</td>
468.      <td> </td>
469.      <td>Yes</td>
470.    </tr>
471.    <tr>
472.      <td> </td>
473.      <td>26</td>
474.      <td> </td>
475.      <td>Yes</td>
476.    </tr>
477.    <tr>
478.      <td> </td>
479.      <td>28</td>
480.      <td> </td>
481.      <td>Yes</td>
482.    </tr>
483.    <tr>
484.      <td><a href="https://www.openstreetmap.org/relation/8491500" rel="nofollow noopener noreferrer">8491500</a></td>
485.      <td>29 Barrington</td>
486.      <td> </td>
487.      <td> </td>
488.    </tr>
489.    <tr>
490.      <td> </td>
491.      <td>30</td>
492.      <td> </td>
493.      <td>Yes</td>
494.    </tr>
495.    <tr>
496.      <td><a href="https://www.openstreetmap.org/relation/8492884" rel="nofollow noopener noreferrer">8492884</a></td>
497.      <td>31 Main Express</td>
498.      <td> </td>
499.      <td> </td>
500.    </tr>
501.    <tr>
502.      <td><a href="https://www.openstreetmap.org/relation/8493340" rel="nofollow noopener noreferrer">8493340</a></td>
503.      <td>32 Cowie Hill Express</td>
504.      <td> </td>
505.      <td> </td>
506.    </tr>
507.    <tr>
508.      <td><a href="https://www.openstreetmap.org/relation/8500329" rel="nofollow noopener noreferrer">8500329</a></td>
509.      <td>33 Tantallon Express</td>
510.      <td> </td>
511.      <td> </td>
512.    </tr>
513.    <tr>
514.      <td><a href="https://www.openstreetmap.org/relation/8500360" rel="nofollow noopener noreferrer">8500360</a></td>
515.      <td>34 Glenbournie Express</td>
516.      <td> </td>
517.      <td> </td>
518.    </tr>
519.    <tr>
520.      <td><a href="https://www.openstreetmap.org/relation/8500421" rel="nofollow noopener noreferrer">8500421</a></td>
521.      <td>35 Parkland Express</td>
522.      <td> </td>
523.      <td> </td>
524.    </tr>
525.    <tr>
526.      <td> </td>
527.      <td>39</td>
528.      <td> </td>
529.      <td>Yes</td>
530.    </tr>
531.    <tr>
532.      <td><a href="https://www.openstreetmap.org/relation/8500919" rel="nofollow noopener noreferrer">8500919</a></td>
533.      <td>41 Dalhousie - Dartmouth</td>
534.      <td> </td>
535.      <td> </td>
536.    </tr>
537.    <tr>
538.      <td><a href="https://www.openstreetmap.org/relation/8500960" rel="nofollow noopener noreferrer">8500960</a></td>
539.      <td>42 Dalhousie - Lacewood</td>
540.      <td> </td>
541.      <td> </td>
542.    </tr>
543.    <tr>
544.      <td> </td>
545.      <td>50</td>
546.      <td> </td>
547.      <td>Yes</td>
548.    </tr>
549.    <tr>
550.      <td><a href="https://www.openstreetmap.org/relation/8501938" rel="nofollow noopener noreferrer">8501938</a></td>
551.      <td>51 Windmill</td>
552.      <td> </td>
553.      <td> </td>
554.    </tr>
555.    <tr>
556.      <td> </td>
557.      <td>51A</td>
558.      <td> </td>
559.      <td>Yes</td>
560.    </tr>
561.    <tr>
562.      <td> </td>
563.      <td>51B</td>
564.      <td> </td>
565.      <td>Yes</td>
566.    </tr>
567.    <tr>
568.      <td><a href="https://www.openstreetmap.org/relation/8502076" rel="nofollow noopener noreferrer">8502076</a></td>
569.      <td>52 Crosstown</td>
570.      <td> </td>
571.      <td> </td>
572.    </tr>
573.    <tr>
574.      <td><a href="https://www.openstreetmap.org/relation/8510563" rel="nofollow noopener noreferrer">8510563</a></td>
575.      <td>53 Notting Park</td>
576.      <td> </td>
577.      <td> </td>
578.    </tr>
579.    <tr>
580.      <td><a href="https://www.openstreetmap.org/relation/8510614" rel="nofollow noopener noreferrer">8510614</a></td>
581.      <td>54 Montebello</td>
582.      <td> </td>
583.      <td> </td>
584.    </tr>
585.    <tr>
586.      <td><a href="https://www.openstreetmap.org/relation/8510620" rel="nofollow noopener noreferrer">8510620</a></td>
587.      <td>55 Port Wallace</td>
588.      <td> </td>
589.      <td> </td>
590.    </tr>
591.    <tr>
592.      <td><a href="https://www.openstreetmap.org/relation/8510653" rel="nofollow noopener noreferrer">8510653</a></td>
593.      <td>56 Dartmouth Crossing</td>
594.      <td> </td>
595.      <td> </td>
596.    </tr>
597.    <tr>
598.      <td><a href="https://www.openstreetmap.org/relation/8510668" rel="nofollow noopener noreferrer">8510668</a></td>
599.      <td>57 Russell Lake</td>
600.      <td> </td>
601.      <td> </td>
602.    </tr>
603.    <tr>
604.      <td><a href="https://www.openstreetmap.org/relation/8510696" rel="nofollow noopener noreferrer">8510696</a></td>
605.      <td>58 Woodlawn</td>
606.      <td> </td>
607.      <td> </td>
608.    </tr>
609.    <tr>
610.      <td><a href="https://www.openstreetmap.org/relation/8510708" rel="nofollow noopener noreferrer">8510708</a></td>
611.      <td>59 Colby</td>
612.      <td> </td>
613.      <td> </td>
614.    </tr>
615.    <tr>
616.      <td><a href="https://www.openstreetmap.org/relation/8510749" rel="nofollow noopener noreferrer">8510749</a></td>
617.      <td>60 Eastern Passage</td>
618.      <td> </td>
619.      <td> </td>
620.    </tr>
621.    <tr>
622.      <td><a href="https://www.openstreetmap.org/relation/8510790" rel="nofollow noopener noreferrer">8510790</a></td>
623.      <td>61 Auburn - North Preston</td>
624.      <td> </td>
625.      <td> </td>
626.    </tr>
627.    <tr>
628.      <td><a href="https://www.openstreetmap.org/relation/8510888" rel="nofollow noopener noreferrer">8510888</a></td>
629.      <td>62 Wildwood</td>
630.      <td> </td>
631.      <td> </td>
632.    </tr>
633.    <tr>
634.      <td> </td>
635.      <td>63</td>
636.      <td> </td>
637.      <td>Yes</td>
638.    </tr>
639.    <tr>
640.      <td><a href="https://www.openstreetmap.org/relation/8510947" rel="nofollow noopener noreferrer">8510947</a></td>
641.      <td>64 Akerley</td>
642.      <td> </td>
643.      <td> </td>
644.    </tr>
645.    <tr>
646.      <td><a href="https://www.openstreetmap.org/relation/8510996" rel="nofollow noopener noreferrer">8510996</a></td>
647.      <td>65 Caldwell</td>
648.      <td> </td>
649.      <td> </td>
650.    </tr>
651.    <tr>
652.      <td><a href="https://www.openstreetmap.org/relation/8511398" rel="nofollow noopener noreferrer">8511398</a></td>
653.      <td>66 Penhorn</td>
654.      <td> </td>
655.      <td> </td>
656.    </tr>
657.    <tr>
658.      <td> </td>
659.      <td>67</td>
660.      <td> </td>
661.      <td>Yes</td>
662.    </tr>
663.    <tr>
664.      <td><a href="https://www.openstreetmap.org/relation/8513172" rel="nofollow noopener noreferrer">8513172</a></td>
665.      <td>68 Cherrybrook</td>
666.      <td> </td>
667.      <td> </td>
668.    </tr>
669.    <tr>
670.      <td><a href="https://www.openstreetmap.org/relation/8513771" rel="nofollow noopener noreferrer">8513771</a></td>
671.      <td>72 Portland Hills</td>
672.      <td> </td>
673.      <td> </td>
674.    </tr>
675.    <tr>
676.      <td><a href="https://www.openstreetmap.org/relation/8513780" rel="nofollow noopener noreferrer">8513780</a></td>
677.      <td>78 Mount Edward Express</td>
678.      <td> </td>
679.      <td> </td>
680.    </tr>
681.    <tr>
682.      <td><a href="https://www.openstreetmap.org/relation/8516204" rel="nofollow noopener noreferrer">8516204</a></td>
683.      <td>79 Cole Harbour Express</td>
684.      <td> </td>
685.      <td> </td>
686.    </tr>
687.    <tr>
688.      <td><a href="https://www.openstreetmap.org/relation/4026930" rel="nofollow noopener noreferrer">4026930</a></td>
689.      <td>80 Halifax - Sackville Terminal</td>
690.      <td>Part of Sackville (4026931)</td>
691.      <td> </td>
692.    </tr>
693.    <tr>
694.      <td><a href="https://www.openstreetmap.org/relation/4026931" rel="nofollow noopener noreferrer">4026931</a></td>
695.      <td>80 Sackville</td>
696.      <td>Wrapper for 4026930</td>
697.      <td> </td>
698.    </tr>
699.    <tr>
700.      <td><a href="https://www.openstreetmap.org/relation/6582655" rel="nofollow noopener noreferrer">6582655</a></td>
701.      <td>80 Sackville</td>
702.      <td>standalone</td>
703.      <td> </td>
704.    </tr>
705.    <tr>
706.      <td><a href="https://www.openstreetmap.org/relation/4024166" rel="nofollow noopener noreferrer">4024166</a></td>
707.      <td>81 Downtown - Hemlock Ravine</td>
708.      <td>standalone</td>
709.      <td> </td>
710.    </tr>
711.    <tr>
712.      <td><a href="https://www.openstreetmap.org/relation/8516226" rel="nofollow noopener noreferrer">8516226</a></td>
713.      <td>81 Hemlock Ravine</td>
714.      <td>standalone</td>
715.      <td> </td>
716.    </tr>
717.    <tr>
718.      <td><a href="https://www.openstreetmap.org/relation/4024101" rel="nofollow noopener noreferrer">4024101</a></td>
719.      <td>81 Hemlock Ravine - Downtown</td>
720.      <td>standalone</td>
721.      <td> </td>
722.    </tr>
723.    <tr>
724.      <td><a href="https://www.openstreetmap.org/relation/4027046" rel="nofollow noopener noreferrer">4027046</a></td>
725.      <td>82 Millwood</td>
726.      <td>Wrapper for 4027045 and 4027047</td>
727.      <td> </td>
728.    </tr>
729.    <tr>
730.      <td><a href="https://www.openstreetmap.org/relation/4027047" rel="nofollow noopener noreferrer">4027047</a></td>
731.      <td>82 Millwood (Halifax - Sackville)</td>
732.      <td>Part of Millwood (4027046)</td>
733.      <td> </td>
734.    </tr>
735.    <tr>
736.      <td><a href="https://www.openstreetmap.org/relation/4027045" rel="nofollow noopener noreferrer">4027045</a></td>
737.      <td>82 Millwood (Sackville - Halifax)</td>
738.      <td>Part of Millwood (4027046)</td>
739.      <td> </td>
740.    </tr>
741.    <tr>
742.      <td><a href="https://www.openstreetmap.org/relation/8516231" rel="nofollow noopener noreferrer">8516231</a></td>
743.      <td>83 Springfield</td>
744.      <td> </td>
745.      <td> </td>
746.    </tr>
747.    <tr>
748.      <td><a href="https://www.openstreetmap.org/relation/8516276" rel="nofollow noopener noreferrer">8516276</a></td>
749.      <td>84 Glendale Express</td>
750.      <td> </td>
751.      <td> </td>
752.    </tr>
753.    <tr>
754.      <td><a href="https://www.openstreetmap.org/relation/8516300" rel="nofollow noopener noreferrer">8516300</a></td>
755.      <td>85 Downsview Express</td>
756.      <td> </td>
757.      <td> </td>
758.    </tr>
759.    <tr>
760.      <td><a href="https://www.openstreetmap.org/relation/8516575" rel="nofollow noopener noreferrer">8516575</a></td>
761.      <td>86 Basinview</td>
762.      <td> </td>
763.      <td> </td>
764.    </tr>
765.    <tr>
766.      <td><a href="https://www.openstreetmap.org/relation/8517180" rel="nofollow noopener noreferrer">8517180</a></td>
767.      <td>87 Glendale</td>
768.      <td> </td>
769.      <td> </td>
770.    </tr>
771.    <tr>
772.      <td><a href="https://www.openstreetmap.org/relation/8517192" rel="nofollow noopener noreferrer">8517192</a></td>
773.      <td>88 Bedford Commons</td>
774.      <td> </td>
775.      <td> </td>
776.    </tr>
777.    <tr>
778.      <td><a href="https://www.openstreetmap.org/relation/8517483" rel="nofollow noopener noreferrer">8517483</a></td>
779.      <td>89 Bedford</td>
780.      <td> </td>
781.      <td> </td>
782.    </tr>
783.    <tr>
784.      <td><a href="https://www.openstreetmap.org/relation/4010941" rel="nofollow noopener noreferrer">4010941</a></td>
785.      <td>90 Larry Uteck</td>
786.      <td>Wrapper route for 4011680 and 16311338</td>
787.      <td> </td>
788.    </tr>
789.    <tr>
790.      <td><a href="https://www.openstreetmap.org/relation/4011680" rel="nofollow noopener noreferrer">4011680</a></td>
791.      <td>90 Larry Uteck</td>
792.      <td>Part of Larry Uteck (4010941)</td>
793.      <td> </td>
794.    </tr>
795.    <tr>
796.      <td><a href="https://www.openstreetmap.org/relation/16311338" rel="nofollow noopener noreferrer">16311338</a></td>
797.      <td>90 Larry Uteck</td>
798.      <td>Part of Larry Uteck (4010941)</td>
799.      <td> </td>
800.    </tr>
801.    <tr>
802.      <td> </td>
803.      <td>91</td>
804.      <td> </td>
805.      <td>Yes</td>
806.    </tr>
807.    <tr>
808.      <td> </td>
809.      <td>93</td>
810.      <td> </td>
811.      <td>Yes</td>
812.    </tr>
813.    <tr>
814.      <td> </td>
815.      <td>123</td>
816.      <td> </td>
817.      <td>Yes</td>
818.    </tr>
819.    <tr>
820.      <td> </td>
821.      <td>127</td>
822.      <td> </td>
823.      <td>Yes</td>
824.    </tr>
825.    <tr>
826.      <td> </td>
827.      <td>135</td>
828.      <td> </td>
829.      <td>Yes</td>
830.    </tr>
831.    <tr>
832.      <td> </td>
833.      <td>136</td>
834.      <td> </td>
835.      <td>Yes</td>
836.    </tr>
837.    <tr>
838.      <td> </td>
839.      <td>137</td>
840.      <td> </td>
841.      <td>Yes</td>
842.    </tr>
843.    <tr>
844.      <td> </td>
845.      <td>138</td>
846.      <td> </td>
847.      <td>Yes</td>
848.    </tr>
849.    <tr>
850.      <td> </td>
851.      <td>158</td>
852.      <td> </td>
853.      <td>Yes</td>
854.    </tr>
855.    <tr>
856.      <td><a href="https://www.openstreetmap.org/relation/8520377" rel="nofollow noopener noreferrer">8520377</a></td>
857.      <td>159 Portland Hills MetroLINK</td>
858.      <td> </td>
859.      <td> </td>
860.    </tr>
861.    <tr>
862.      <td> </td>
863.      <td>161</td>
864.      <td> </td>
865.      <td>Yes</td>
866.    </tr>
867.    <tr>
868.      <td> </td>
869.      <td>165</td>
870.      <td> </td>
871.      <td>Yes</td>
872.    </tr>
873.    <tr>
874.      <td> </td>
875.      <td>168A</td>
876.      <td> </td>
877.      <td>Yes</td>
878.    </tr>
879.    <tr>
880.      <td> </td>
881.      <td>168B</td>
882.      <td> </td>
883.      <td>Yes</td>
884.    </tr>
885.    <tr>
886.      <td> </td>
887.      <td>182</td>
888.      <td> </td>
889.      <td>Yes</td>
890.    </tr>
891.    <tr>
892.      <td> </td>
893.      <td>183</td>
894.      <td> </td>
895.      <td>Yes</td>
896.    </tr>
897.    <tr>
898.      <td><a href="https://www.openstreetmap.org/relation/8530711" rel="nofollow noopener noreferrer">8530711</a></td>
899.      <td>185 Sackville MetroLINK</td>
900.      <td> </td>
901.      <td> </td>
902.    </tr>
903.    <tr>
904.      <td> </td>
905.      <td>186</td>
906.      <td> </td>
907.      <td>Yes</td>
908.    </tr>
909.    <tr>
910.      <td> </td>
911.      <td>192</td>
912.      <td> </td>
913.      <td>Yes</td>
914.    </tr>
915.    <tr>
916.      <td><a href="https://www.openstreetmap.org/relation/13052520" rel="nofollow noopener noreferrer">13052520</a></td>
917.      <td>194 West Bedford Express to Downtown</td>
918.      <td> </td>
919.      <td> </td>
920.    </tr>
921.    <tr>
922.      <td><a href="https://www.openstreetmap.org/relation/8520012" rel="nofollow noopener noreferrer">8520012</a></td>
923.      <td>194 West Bedford Express to Innovation Dr</td>
924.      <td> </td>
925.      <td> </td>
926.    </tr>
927.    <tr>
928.      <td><a href="https://www.openstreetmap.org/relation/12561386" rel="nofollow noopener noreferrer">12561386</a></td>
929.      <td>196 Basinview Express</td>
930.      <td> </td>
931.      <td> </td>
932.    </tr>
933.    <tr>
934.      <td><a href="https://www.openstreetmap.org/relation/12671265" rel="nofollow noopener noreferrer">12671265</a></td>
935.      <td>320 Airport—Fall River</td>
936.      <td>Wrapper route containing two relations</td>
937.      <td> </td>
938.    </tr>
939.    <tr>
940.      <td><a href="https://www.openstreetmap.org/relation/8530735" rel="nofollow noopener noreferrer">8530735</a></td>
941.      <td>320 Downtown Halifax via Bridge Terminal</td>
942.      <td>Included in 320 Airport—Fall River (12671265)</td>
943.      <td> </td>
944.    </tr>
945.    <tr>
946.      <td><a href="https://www.openstreetmap.org/relation/12671264" rel="nofollow noopener noreferrer">12671264</a></td>
947.      <td>320 Fall River-Airport</td>
948.      <td>part of 320 Airport—Fall River (12671265)</td>
949.      <td> </td>
950.    </tr>
951.    <tr>
952.      <td><a href="https://www.openstreetmap.org/relation/8534829" rel="nofollow noopener noreferrer">8534829</a></td>
953.      <td>330 Tantallon MetroX</td>
954.      <td> </td>
955.      <td> </td>
956.    </tr>
957.    <tr>
958.      <td><a href="https://www.openstreetmap.org/relation/8536977" rel="nofollow noopener noreferrer">8536977</a></td>
959.      <td>370 Porters Lake MetroX</td>
960.      <td> </td>
961.      <td> </td>
962.    </tr>
963.    <tr>
964.      <td><a href="https://www.openstreetmap.org/relation/8520019" rel="nofollow noopener noreferrer">8520019</a></td>
965.      <td>400 Beaver Bank</td>
966.      <td> </td>
967.      <td> </td>
968.    </tr>
969.    <tr>
970.      <td><a href="https://www.openstreetmap.org/relation/8520131" rel="nofollow noopener noreferrer">8520131</a></td>
971.      <td>401 Porters Lake</td>
972.      <td> </td>
973.      <td> </td>
974.    </tr>
975.    <tr>
976.      <td><a href="https://www.openstreetmap.org/relation/6122014" rel="nofollow noopener noreferrer">6122014</a></td>
977.      <td>402</td>
978.      <td> </td>
979.      <td> </td>
980.    </tr>
981.    <tr>
982.      <td> </td>
983.      <td>415</td>
984.      <td> </td>
985.      <td>Yes</td>
986.    </tr>
987.    <tr>
988.      <td> </td>
989.      <td>433</td>
990.      <td> </td>
991.      <td>Yes</td>
992.    </tr>
993.  </tbody>
994. </table>
995.  
996. <p dir="auto">(For anyone else reading this, the main version of this list is offline.)</p>
997. </description>
998.      <dc:creator>diwesser</dc:creator>
999.      <pubDate>Mon, 03 Nov 2025 07:10:06 +0000</pubDate>
1000.      <comments>https://www.openstreetmap.org/user/diwesser/diary/407690#comments</comments>
1001.    </item>
1002.    <item>
1003.      <title>beitrag im blog suchen / Ortsteil falsch</title>
1004.      <link>https://www.openstreetmap.org/user/KaBa69/diary/407686</link>
1005.      <guid>https://www.openstreetmap.org/user/KaBa69/diary/407686</guid>
1006.      <description>&lt;p dir="auto"&gt;Ich suche gerne erstmal in blogs, aber hier geht es leider nicht, oder ich weiß nicht, wie.
1007. Eigentlich bin ich über die App “nora” darüber gefallen, daß eine Straße mit PLZ einem Ortsteil zugeordnet wurde, aber nicht dem Hauptort, wo diese Straße wirklich ist. Wie kann man so etwas korrigieren ?</p>
1008. </description>
1009.      <dc:creator>KaBa69</dc:creator>
1010.      <pubDate>Sun, 02 Nov 2025 14:28:53 +0000</pubDate>
1011.      <comments>https://www.openstreetmap.org/user/KaBa69/diary/407686#comments</comments>
1012.    </item>
1013.    <item>
1014.      <title>Werkzeuge für Arbeiten an OpenStreetMap</title>
1015.      <link>https://www.openstreetmap.org/user/MichaelFS/diary/407683</link>
1016.      <guid>https://www.openstreetmap.org/user/MichaelFS/diary/407683</guid>
1017.      <description>&lt;p dir="auto"&gt;Mit &lt;strong&gt;+++&lt;/strong&gt; gekennzeichnete Einträge basieren auf von mir programmierten Erweiterungen. Diese werden regelmäßig aktualisiert; im Kopf dieser Seite wird der Zeitstempel der letzten Aktualisierung angezeigt.&lt;/p&gt;
1018.  
1019. <ul dir="auto">
1020.  <li>
1021.    <p dir="auto"><strong>+++</strong> <a href="https://osm.intago.de/HowToMap/OSM-HowToMap%20ONline.html" rel="nofollow noopener noreferrer">OpenStreetMap-Wiki DE:How to map a [A..Z]</a><br>Aus dem OSM-Wiki <a href="https://wiki.openstreetmap.org/wiki/DE:How_to_map_a" rel="nofollow noopener noreferrer">DE:How to map a</a> wird jede Seite des alphabetischen Registers [A..Z] ausgewertet; alle Attribute (EN: tags) werden <strong><em>auf einer Seite</em></strong> gelistet, ein Suchfeld erlaubt die Filterung  auf Teilstring-Filter.</p>
1022.  </li>
1023.  <li>
1024.    <p dir="auto"><a href="https://confusedbuffalo.github.io/phone-report/" rel="nofollow noopener noreferrer">OSM Telefonnummern-Validierung</a></p>
1025.  </li>
1026. </ul>
1027. </description>
1028.      <dc:creator>MichaelFS</dc:creator>
1029.      <pubDate>Sun, 02 Nov 2025 10:31:56 +0000</pubDate>
1030.      <comments>https://www.openstreetmap.org/user/MichaelFS/diary/407683#comments</comments>
1031.    </item>
1032.    <item>
1033.      <title>Koh Phangan: The Gem Born from Magma and Sea</title>
1034.      <link>https://www.openstreetmap.org/user/JunglerKP/diary/407682</link>
1035.      <guid>https://www.openstreetmap.org/user/JunglerKP/diary/407682</guid>
1036.      <description>&lt;p dir="auto"&gt;Koh Phangan is one of Thailand’s most enchanting islands, floating gracefully in the Gulf of Thailand between its famous neighbors, Koh Samui and Koh Tao. Known for its palm-fringed beaches, lush jungles, and vibrant culture, Koh Phangan is far more than just the site of the world-renowned Full Moon Party - it’s an island with a fascinating geological and cultural history shaped by magma, time, and the sea.&lt;/p&gt;
1037.  
1038. <p dir="auto">Millions of years ago, long before travelers set foot on its shores, the land that became Koh Phangan was formed deep within the Earth’s crust. The island originated from volcanic activity during a period of intense tectonic movement. As magma rose from beneath the Earth’s surface, it cooled and solidified, giving birth to the island’s granite core. That foundation still defines its rugged mountains and dramatic rock formations today.</p>
1039.  
1040. <p dir="auto">Over millennia, erosion, wind, and the gentle rise and fall of sea levels sculpted the island into its present form. The lush jungle that now blankets Koh Phangan slowly took root over the ancient volcanic rock, transforming a once-fiery mass into a tropical paradise.</p>
1041.  
1042. <p dir="auto">So, in a very real sense, Koh Phangan was forged from magma. Its land born of molten rock and shaped by the slow artistry of nature.</p>
1043.  
1044. <p dir="auto">Archaeological evidence suggests that humans have lived on the island for over 2,000 years. Ancient pottery, tools, and inscriptions hint at early Malay and Thai settlers who relied on fishing, coconut farming, and trade with nearby islands.</p>
1045.  
1046. <p dir="auto">By the 14th century, during the Srivijaya Empire, Koh Phangan was part of a thriving maritime network. It later became a peaceful retreat for Buddhist monks, and even Thailand’s King Rama V (Chulalongkorn) visited the island over a dozen times. His royal insignia can still be found carved into stones at Than Sadet Waterfall, a site of deep spiritual significance.</p>
1047.  
1048. <p dir="auto">In the 20th century, Koh Phangan began to attract travelers seeking something different: a slower, more authentic Thailand. Backpackers discovered the island’s secluded beaches in the 1970s, and soon after, the legendary Full Moon Party was born on Haad Rin Beach. What started as a small gathering of friends celebrating under the moonlight became an international phenomenon, drawing thousands each month.</p>
1049.  
1050. <p dir="auto">Yet beyond the party scene, Koh Phangan has managed to retain a rare balance. Its northern and eastern shores remain tranquil and largely undeveloped, home to yoga retreats, eco-resorts, and communities devoted to sustainable living. Inland, waterfalls, dense jungles, and secret temples make it a haven for hikers and spiritual seekers alike.</p>
1051.  
1052. <p dir="auto">Koh Phangan is not just shaped by ancient magma. It is alive with energy. The whole year you can catch the stage of spectacular lightning storms that light up the sky over the Gulf of Thailand. Bolts crack across the horizon, illuminating palm trees, cliffs, and beaches in electric flashes. Lightning’s sound travel much slower on this island, about around 343 m/s (1230 km/h) at sea level, because of the warm tropical air. You can count the seconds between the flash and the thunder easily. Every 3 seconds ≈ 1 kilometer (or about 5 seconds ≈ 1 mile). So if you see lightning over Haad Rin Beach and hear thunder 9 seconds later, the strike was roughly 3 km away.</p>
1053.  
1054. <p dir="auto">What makes Koh Phangan truly awesome is its duality. It is both wild and serene, ancient and alive, volcanic and oceanic. Whether you come for the spiritual energy of its temples, the rhythm of its beach festivals, or the simple joy of watching the sun set over the sea, the island has a way of pulling you into its rhythm.</p>
1055.  
1056. <p dir="auto">Koh Phangan is not just a destination.It is a living reminder of the Earth’s power to create beauty from magma, time, and transformation.</p>
1057. </description>
1058.      <dc:creator>JunglerKP</dc:creator>
1059.      <pubDate>Sun, 02 Nov 2025 03:18:05 +0000</pubDate>
1060.      <comments>https://www.openstreetmap.org/user/JunglerKP/diary/407682#comments</comments>
1061.      <geo:lat>9.747407466434215</geo:lat>
1062.      <geo:long>100.02777099609375</geo:long>
1063.      <georss:point>9.747407466434215 100.02777099609375</georss:point>
1064.    </item>
1065.    <item>
1066.      <title>绘图时翻涌起的回忆，以及有关归属感的挣扎</title>
1067.      <link>https://www.openstreetmap.org/user/WayeeTan/diary/407681</link>
1068.      <guid>https://www.openstreetmap.org/user/WayeeTan/diary/407681</guid>
1069.      <description>&lt;p dir="auto"&gt;我主要绘制地图的地方都是我熟悉的地段。伦敦的地图早已细致得无可挑剔，我所能做的，不过是依照自己的实地探访，添几笔修补与更新。而那些我真正想描绘的地方——韶关、狮山——在地图上却几乎是一片空白。于是我盯着卫星影像，凭借记忆，一条一条地把它们补上去。&lt;/p&gt;
1070.  
1071. <p dir="auto">然而，一旦动笔，记忆便被无声地唤醒。</p>
1072.  
1073. <p dir="auto">狮山的郊外，是满目灰尘与机器轰鸣的工业区。但在那段短暂的大四下学期——也正是中国放开三年疫情封控的时节——我几乎把所有空闲都花在漫步上。我终于能重新走出校门。那是一种久违的自由，也是一种怅然的陌生。我在风尘漫天的乡村与工业区之间走走停停，感受空气、阳光，还有一种模糊的“重生”的气息。如今每当我在地图上画下那一条条路，心里都能重新浮现当时看到的一切：斜阳下的厂房、贴着褪色标语的围墙、被工厂分割得七零八落的农田……</p>
1074.  
1075. <p dir="auto">狮山的城区，则是我课余时常去的地方。几个广场、几座公园，见证了太多微小却清晰的瞬间——我记得每一次同行的人，记得谈笑的片段，甚至记得那时吹过的风。</p>
1076.  
1077. <p dir="auto">而狮山大学城，那更不必说。四年光阴的流动，几乎都沉淀在那片土地上。无数的晨昏交替、无数未完的对话、无数被时间吞没的小事——都化作我记忆的一部分。</p>
1078.  
1079. <p dir="auto">再往前追溯，就是韶关，我的故乡。那座夹在群山之间的袖珍小城，从小到大承载了太多我的生活。每一条街道、每一个转角，都藏着旧日的故事。那是一个人生命中最初的坐标，是无论走多远都无法抹去的印记。</p>
1080.  
1081. <p dir="auto">所以，当我坐在远在数千公里外的伦敦，往这些空白的区域绘图的时候，心里总会冒出一个问题：</p>
1082.  
1083. <p dir="auto">——我到底该留在哪里？</p>
1084.  
1085. <p dir="auto">年初的时候，我曾以为这一年会让我找到答案。但时至今日，犹豫仍在。</p>
1086.  
1087. <p dir="auto">文化上，我当然认同留在广东。嗰度嘅语言、食物、人情，都系我最熟悉、最舒服嘅空气。</p>
1088.  
1089. <p dir="auto">可与此同时，也有些记忆在暗暗提醒我：不要回去。那些过去几年留下的痕迹——恐惧、疏离、无力感——仍像一层薄雾，笼罩在记忆的上空。我怀念那片土地，也被它深深刺痛。</p>
1090.  
1091. <p dir="auto"><strong><em>​I love my country, but not the party.</em></strong></p>
1092.  
1093. <p dir="auto">我爱这片土地，也爱生活在其上的人们。</p>
1094.  
1095. <p dir="auto">但那份爱并不来自，也不属于盘踞在那片土地之上的权力、旗帜，与口号。</p>
1096.  
1097. <p dir="auto">也许我找不到一个可以真正安放自己的地方。但我希望，那些我亲手画下的线，能在虚拟二维的OpenStreetMap里，延续我对故土最温柔的告白。</p>
1098. </description>
1099.      <dc:creator>WayeeTan</dc:creator>
1100.      <pubDate>Sun, 02 Nov 2025 01:25:31 +0000</pubDate>
1101.      <comments>https://www.openstreetmap.org/user/WayeeTan/diary/407681#comments</comments>
1102.    </item>
1103.    <item>
1104.      <title>Vontade de falar sobre a geografia de Florianópolis</title>
1105.      <link>https://www.openstreetmap.org/user/loganlidno/diary/407680</link>
1106.      <guid>https://www.openstreetmap.org/user/loganlidno/diary/407680</guid>
1107.      <description>&lt;p dir="auto"&gt;Não gosto muito de falar em público ou coisa assim mas me deu vontade então vou falar coisas&lt;/p&gt;
1108.  
1109. <p dir="auto">Eu sou nativo de Florianópolis e morei minha vida inteira aqui, tirando a única vez que eu tive uma pousada em São josé. Desde pequeno eu fui muito interessado sobre geografia. Bom, o Openstreetmap basicamente foi um portal abrindo por que o maps ele é cheio de erros e o OSM parecia o céu dos mapas.</p>
1110.  
1111. <p dir="auto">E é, só que como tudo, não é perfeito. Igual a organização geográfica de Florianópolis. Só pra vcs terem noção ela virou municipio no final dos 1726 e é cidade desde 1600 e coisa coisa, e só em <strong>1999</strong> fizeram os primeiros bairros. Isso é 300 anos sem bairros oficiais. E só agora tão oficializando as localidades..
1112. Algo que eu percebi é que tem uns erros aqui no OSM de Florianópolis, como, a Tapera da Base pega a UEP Morro do Peralta, sendo que, de acordo com a lei, não pega, deveria ser parte do Carianos. Quer dizer, Carianos nem deveria tar com mapa, POR QUE NEM É BAIRRO IGUAL TUDO EXCETO A TAPERA E REGIÃO DO DISTRITO SEDE ANTIGO</p>
1113.  
1114. <p dir="auto">Bla bla bla vcs entenderam</p>
1115.  
1116. <p dir="auto">Algo que é um desejo é arrumar tudo que tem de erro em Florianópolis no OSM, pelo menos pra ficar num nivel onde você pode ter 100% de confiança ao olhar o mapa, só que ninguém parece dar bolas pra geografia da minha, da NOSSA cidade, parece que fazem por que são forçados, e o atendimento da prefeitura com esses tipos de coisa é terrivel, tem coisa que eu mandei meia década atrás pra eles e eles ainda não me responderam. Um sonho meu é poder ser parte do sistema de geografia de florianópolis e arrumar tudo que fizeram mal ou nem olharam.</p>
1117.  
1118. <p dir="auto">Também eu quero ter parceiros para atualizar florianópolis já que agora a gente tá em uma coisa histórica do municipio, teve varias modificações na geografia da cidade, criação de 6 novos distritos, 30 bairros oficializados, e daqui a pouco, novas localidades</p>
1119. </description>
1120.      <dc:creator>loganlidno</dc:creator>
1121.      <pubDate>Sat, 01 Nov 2025 18:12:38 +0000</pubDate>
1122.      <comments>https://www.openstreetmap.org/user/loganlidno/diary/407680#comments</comments>
1123.    </item>
1124.    <item>
1125.      <title>ProjetDuMois can now monitor contribution projects worldwide</title>
1126.      <link>https://www.openstreetmap.org/user/InfosReseaux/diary/407679</link>
1127.      <guid>https://www.openstreetmap.org/user/InfosReseaux/diary/407679</guid>
1128.      <description>&lt;p dir="auto"&gt;Some news and visions about topic focused contribution monitoring capabilities of ProjetDuMois&lt;/p&gt;
1129.  
1130. <h3 dir="auto" id="projetdumois-platform">ProjetDuMois platform</h3>
1131.  
1132. <p dir="auto">For more than 6 years, <a href="https://github.com/vdct/ProjetDuMois" rel="nofollow noopener noreferrer">ProjetDuMois platform</a> was used to plan, encourage and monitor “<a href="https://wiki.openstreetmap.org/wiki/Project_of_the_month" rel="nofollow noopener noreferrer">Projects of the month</a>” by French community (and some other countries too). It has been a significant progress for people responsible of those very short projects as it has freed us from the hassle of counting changesets and provides a mappers-friendly customized editor.</p>
1133.  
1134. <p dir="auto"><img src="https://wiki.openstreetmap.org/w/images/3/34/ProjetDuMois_web_interface.png" alt="ProjetDuMois web interface for EVSE inventory" loading="lazy"></p>
1135.  
1136. <p dir="auto">It relies on daily <a href="https://wiki.openstreetmap.org/wiki/OSM_XML" rel="nofollow noopener noreferrer">OSH/OSC files</a> processing to extract history of filtered features, rebuild focused changelog from a remote date in the past and breakdown changes in dashboards at different custom geographical boundaries (usually administrative boundaries).
1137. It somehow differs from other approaches intended to inspect OSM contribution like <a href="https://github.com/GIScience/oshdb" rel="nofollow noopener noreferrer">HeiGIT’s OSHDB</a>. Here all features and their history related to a given project is first of all extracted from the OSH file and then dedicated process occurs on a smaller population than the whole OSM database even on local level.</p>
1138.  
1139. <p dir="auto">The original instance is available online at <a href="https://projetdumois.fr" rel="nofollow noopener noreferrer" dir="auto">https://projetdumois.fr</a> and <a href="https://github.com/vdct/ProjetDuMois/tree/master/docs" rel="nofollow noopener noreferrer">official documentation</a> on GitHub.</p>
1140.  
1141. <p dir="auto">However, it was designed for country scale and we didn’t imagine at first it could manage projects worldwide. Country scale processing was already heavy and dealing with world planet file with its history was out of reach.</p>
1142.  
1143. <h3 dir="auto" id="mapyourgrid-improvements">MapYourGrid improvements</h3>
1144.  
1145. <p dir="auto">In mid 2025, <a href="https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/MapYourGrid_Initiative" rel="nofollow noopener noreferrer">MapYourGrid initiative</a> needed to monitor the contribution on power grids in many countries and it triggered me to improve ProjetDuMois to process worldwide data with following amounts to breakdown per country in mind:</p>
1146.  
1147. <ul dir="auto">
1148.  <li>5M versions of transmission lines segments</li>
1149.  <li>10M km of transmission lines segments</li>
1150.  <li>100M versions of supports</li>
1151.  <li>10M versions of substations</li>
1152. </ul>
1153.  
1154. <p dir="auto">Adrien Pavie and I reworked the workflow and it now works beyond my expectations thanks to <a href="https://osmcode.org" rel="nofollow noopener noreferrer">Osmium ecosystem</a>. Several improvements has been done:</p>
1155.  
1156. <ul dir="auto">
1157.  <li><a href="https://github.com/vdct/ProjetDuMois/blob/master/docs/DEVELOP.md#projects-timeline" rel="nofollow noopener noreferrer">Consistent project timeline</a>, OSH initialisation and daily changes accumulation from OSC files</li>
1158.  <li><a href="https://github.com/vdct/ProjetDuMois/blob/master/docs/DEVELOP.md#features-counts" rel="nofollow noopener noreferrer">Counting directly</a> from changelog</li>
1159.  <li>World scale processing, additional administrative boundaries levels</li>
1160.  <li><a href="https://github.com/open-energy-transition/ProjetDuMois/blob/feature/categories/docs/DEVELOP.md#filtering-features" rel="nofollow noopener noreferrer">Business labeling</a> for features inside a given project</li>
1161. </ul>
1162.  
1163. <p dir="auto">MapYourGrid now monitors a changelog from 2024-01 that covers:</p>
1164.  
1165. <ul dir="auto">
1166.  <li>1.4M of power lines segments versions (+ 23.8M of members nodes versions)</li>
1167.  <li>39M of power supports versions</li>
1168.  <li>4.5M of mixed features versions for power substations</li>
1169.  <li>25M of mixed features versions for power generators</li>
1170.  <li>16M of mixed features versions for power plants</li>
1171. </ul>
1172.  
1173. <p dir="auto">And it takes approximately 6 hours to rebuild on demand (or updated daily in less than 2 hours with worldwide OSC). It’s then convenient to rebuild a project on any extent, tagging or strategy change.</p>
1174.  
1175. <p dir="auto">Platform’s API also allows to derivate statistics into <a href="https://dianethy.shinyapps.io/Progress_MapYourGrid/" rel="nofollow noopener noreferrer">a custom dashboard</a> or downstream application.</p>
1176.  
1177. <p dir="auto"><img src="https://wiki.openstreetmap.org/w/images/8/8a/MapYourGrid_dashboard_interface.png" alt="MapYourGrid progress dashboard fed by ProjetDuMois API" loading="lazy"></p>
1178.  
1179. <h3 dir="auto" id="future-and-roadmap">Future and roadmap</h3>
1180. <p dir="auto">I now run 3 instances for different purposes you can find online as demos:</p>
1181.  
1182. <ul dir="auto">
1183.  <li>Worldwide <a href="https://mapyourgrid.infos-reseaux.com" rel="nofollow noopener noreferrer">MapYourGrid monitoring</a> since 2024-01 <=> <a href="https://dianethy.shinyapps.io/Progress_MapYourGrid/" rel="nofollow noopener noreferrer">custom business dashboard</a></li>
1184.  <li>French <a href="https://enedis.openstreetmap.fr" rel="nofollow noopener noreferrer">Monitoring for partnership</a> with power DSO Enedis since 2020-10</li>
1185.  <li>French <a href="https://ftth.infos-reseaux.com" rel="nofollow noopener noreferrer">Monitoring of telecommunication infrastructure contribution</a> since 2018-01</li>
1186. </ul>
1187.  
1188. <p dir="auto">Even if it improves, bugs and technical debt remain. We maintain a <a href="https://github.com/vdct/ProjetDuMois/issues" rel="nofollow noopener noreferrer">list of issues</a> to be solved on GitHub and anyone interested is welcome to help. Here are the most sensitive points:</p>
1189.  
1190. <ul dir="auto">
1191.  <li>Find a better name! <a href="https://github.com/vdct/ProjetDuMois/issues/353" rel="nofollow noopener noreferrer">#353</a></li>
1192.  <li>Support Panoramax and restore old functionalities like <a href="https://wiki.openstreetmap.org/wiki/Pic4Review" rel="nofollow noopener noreferrer">Pic4Review</a> <a href="https://github.com/vdct/ProjetDuMois/issues/318" rel="nofollow noopener noreferrer">#318</a></li>
1193.  <li>Rewrite processing scripts from bash to Python</li>
1194.  <li>Improve mappers population monitoring <a href="https://github.com/vdct/ProjetDuMois/issues/330" rel="nofollow noopener noreferrer">#330</a></li>
1195. </ul>
1196.  
1197. <p dir="auto">Feel free to reuse for your own needs, meet us and help!</p>
1198. </description>
1199.      <dc:creator>InfosReseaux</dc:creator>
1200.      <pubDate>Sat, 01 Nov 2025 17:31:29 +0000</pubDate>
1201.      <comments>https://www.openstreetmap.org/user/InfosReseaux/diary/407679#comments</comments>
1202.    </item>
1203.    <item>
1204.      <title>没有主题</title>
1205.      <link>https://www.openstreetmap.org/user/John%20Due/diary/407678</link>
1206.      <guid>https://www.openstreetmap.org/user/John%20Due/diary/407678</guid>
1207.      <description>&lt;p dir="auto"&gt;出于个人的隐私考虑，本人的 OpenStreetMap 账户的用户名使用化名，敬请谅解。&lt;/p&gt;
1208.  
1209. <h2 dir="auto" id="section">简介&来意</h2>
1210.  
1211. <p dir="auto">我是一名陕西省咸阳市的中学生，在探索开源软件的过程中遇到了 <a href="https://organicmaps.app/zh-Hans/" rel="nofollow noopener noreferrer">Organic Maps</a>、<a href="https://www.comaps.app/" rel="nofollow noopener noreferrer">CoMaps</a> 和 <a href="https://f-droid.org/packages/net.osmand.plus/" rel="nofollow noopener noreferrer">OsmAnd~</a>，并认识了 OpenStreetMap。由于对开源软件的热爱，以及发现 OpenStreetMap 对中国大陆的小城市（包括我居住的城市）的数据支持不够完善，因此想做出一些贡献，用这种方式帮助自己身边的人以及需要的人（虽然周围的人没有一个知道 OpenStreetMap，但是万一他们哪一天需要呢）</p>
1212.  
1213. <p dir="auto">一直以来，坐标系统的不一致导致 Google 地图和其他海外地图在中国大陆的卫星影像和人工标注的道路信息差了上百米，国内的地图软件对国外的数据支持也有限，更重要的是国内外主流的地图产品出于商业考虑不向公众共享地图数据，OpenStreetMap 在这一点上无疑是很好的<strong>开源</strong>替代品。但其在中国大陆（在国外也可能符合这个规律）的地图数据的详细程度大致与这个地区的经济发展状况成正比关系（正常，商业地图公司的员工开车全国跑，地图数据也要详细的多），这容易让人误解：某个地方除了道路什么也没有。</p>
1214.  
1215. <p dir="auto">编辑地图只是出于我对开源软件和开放数据的热爱，而且也不是我的正事，因此我每天不会花太多时间在这件事上。</p>
1216.  
1217. <blockquote>
1218.  <h2 dir="auto" id="section-1">事件</h2>
1219.  
1220.  <ol dir="auto">
1221.    <li>
1222.      <p dir="auto">在 2025 年 10 月 29 日，我收到了贡献者 <a href="https://www.openstreetmap.org/user/booktiger" rel="nofollow noopener noreferrer">booktiger</a> 发送的一封欢迎消息，并且阅读并了解了中国的法律情况和编辑指南（说实话我只是想完善一下居民区建筑信息以及店铺信息，我连监狱都不想往上画，更不要说国家机密了），也阅读了他参与的一些讨论（比如 <a href="https://www.openstreetmap.org/user/assanges/diary/397559" rel="nofollow noopener noreferrer">397559</a>）。</p>
1223.  
1224.      <p dir="auto">本人对政治并不感兴趣，但这并不意味着本人没有一点政治常识。对于台湾问题，我很庆幸 OpenStreetMap 上没有标注国界线，这避免了许多潜在的争议（虽然一些人将水陆分界线当成了国界线并且发表自己的意见，比如 <a href="https://www.openstreetmap.org/user/snally/diary/395824" rel="nofollow noopener noreferrer">395824</a>）。但是如果你因为 OpenStreetMap 没有给“台湾”后面加“省”感到特别生气，也可以在网络上发表自己的意见。我绝不会干涉任何一方的言论自由，而且也不会修改台湾（省）本地的任何信息。</p>
1225.    </li>
1226.  </ol>
1227. </blockquote>
1228. </description>
1229.      <dc:creator>John Due</dc:creator>
1230.      <pubDate>Sat, 01 Nov 2025 05:52:53 +0000</pubDate>
1231.      <comments>https://www.openstreetmap.org/user/John%20Due/diary/407678#comments</comments>
1232.    </item>
1233.    <item>
1234.      <title>State of the Map 2025 - 從單純參與者到社群組織者與推廣者心路歷程</title>
1235.      <link>https://www.openstreetmap.org/user/Supaplex/diary/407675</link>
1236.      <guid>https://www.openstreetmap.org/user/Supaplex/diary/407675</guid>
1237.      <description>&lt;p dir="auto"&gt;這篇是拖了一段時間的參與心得，先從比較有官方色彩的開放街圖基金會的相關記錄與討論開始，再來比較個人的交流與觀察。&lt;/p&gt;
1238.  
1239. <p dir="auto">大會第三天在閉幕式前的 OSMF 時段，由具備理事身份的人座談。OSMF理事長談到一些花費是這麼說的，大家覺得努力募款增加捐款數字，但目前很多幫助來自業者服務捐贈，如CDN、Bing衛星圖、伺服器等，如果任何業者決定中止捐增，會導致 OSMF 有很嚴重的財務缺口。而圖客參與畫地圖才能一直維持地圖的活力，所以社群經營也是重要的挑戰。理事Otris提到，他們目前重點是讓硬體設備能支援未來的需求，很努力進行開發與硬體架構設備。</p>
1240.  
1241. <p dir="auto">OSM Award Brandon 被提名，然後他們自己不知道，他開完笑說知道他被提名還可以拉一些票，再來是多位獲獎者不在現場，需要由人代領。</p>
1242.  
1243. <p dir="auto"><a href="https://awards.openstreetmap.org/" rel="nofollow noopener noreferrer" dir="auto">https://awards.openstreetmap.org/</a></p>
1244.  
1245. <h2 dir="auto" id="hot-">HOT 主力的大會</h2>
1246.  
1247. <p dir="auto">這次以HOT Asia Pacific Map Guru身份參與State of the Map 2025大會，不只是講者的身份，或是地方社群組織者，還有HOT身份，有點汗顏台灣不是HOT AP優先區域，也不大需要靠OpenStreetMap去成為救災主力圖資。
1248. ## 東亞與南亞社群的聯結
1249. 我再次遇到韓國社群的成員，先前在台灣時已經在COSCUP遇到他了，鼓勵南韓的Dong Hwang也可以參與HOT相關訓練課程，其內容都蠻實用的。
1250. 從日本社群的古橋大地桑聽到PLATEAU建築資料集的故事，原來背後推動人士瞭解社群，知道怎麼調和彼此關注之處，從而引路社群機制來共同編輯資料集。
1251. 與印度社群交流，他們也有類似台灣弄學校資料的整理，由於關注度因素得弄獨立的MediaWiki站，然後他們不同單位有不同代碼，不只需要弄一個代碼。</p>
1252.  
1253. <h2 dir="auto" id="section">台灣經驗分享</h2>
1254. <p dir="auto">這次演講題目細數台灣曾經做過的專案，談論將OpenStreetMap與Wikidata彼此連結的經驗。儘管我沒太講工具的部分，但有口頭講在維基媒體生態系的工具生態系較成熟，有運用在Wikidata上的自動表格工具Listeria，監控Wikidata上即時的項目，例如所有台灣的國中小、教會、廟宇、村里行政區之類。目前 OpenStreetMap 上面則沒有太好用的監控維護工具，所以得依整先在 Wikidata 上確定資料完整，再回過頭檢查 OpenStreetMap 的物件。
1255. 近期熟悉OpenRefine是相當好的工具，不過來不及在演講時敘述。OpenRefine是適合做維護工具，有一份相對穩定的有維護的清單，去比對在Wikidata上面是否資料為即時的。</p>
1256.  
1257. <p dir="auto">SotM 2025我的講場是第二天一早，我這一軌下一個講場則是烏干達維基人分享自己怎麼做圖書館資料的繪製。他們狀況是並沒有政府維護的圖書館清單，所以得自己依靠社群去收集圖書館基本資訊，如照片、位置等。我的講場與他的講場差別在，有資料集可以用與否，蠻有意思的比較。</p>
1258.  
1259. <p dir="auto">另外除了我之外，還有兩位來自台灣的參與者，Proton Maps 的創辦人Brandon 跟他搭同班一早的長榮航班飛來馬尼拉，不過他沒有議程，純來交流。積丹尼是當初破解台電變電箱外數字，被稱為電力座標，其實是 TWD67座標系，則是投稿一場，又有一場lightning talk。跟他聊原來他已經搬到北屯了，不在東勢山區了，聽說原由是他跟鄰居吵架導致他不能住他的農舍了。我還調侃Minh應該常需要檢視積丹尼對OpenStreetMap、OSM-Carto接近無理取鬧的討論提議，他是笑笑覺得還好。他現在是OpenStreetMap Foundation 的工程師，應該也習慣非技術討論，偏向政治的議題討論狀況了。</p>
1260.  
1261. <p dir="auto">積丹尼的講場圍繞地址相關議題，用程式方式分析菲律賓一帶地址標示狀況，來檢視其邏輯，他的lightning talk講題偏倡議，則在推廣grid 的地址系統，認為是最棒的。其實積丹尼的講場應該也可以去投稿學術軌</p>
1262.  
1263. <h2 dir="auto" id="section-1">密切交流</h2>
1264.  
1265. <p dir="auto">這次的大會除了HOT的人交際之外，還有與美國背景的人討論蠻多議題。從桃園機場登機口遇到Brandon，以及他的好友Minh。從Minh口中得到Mapmatching的技術，能夠依據先前位置，去判斷你是在高架還是平面道路，或是你是沿著道路旁邊的單車道或人行道。辦在歐洲、美國之外，本來參與人數就少了，這次也看不太到大公司的人，與前幾年的感覺相比，回歸到推動組織與在地社群的面向為主。儘管煙火小了，但是有實際在地組織，在地社群參與，是很實在的，也能應對在地需求。
1266. Minh與Brandon曾為Mapbox做事，而近年Mapbox的曝光度變蠻低的，在這次大會當中，就Maning而已。而他們曾經雇大量Data team的人，也有與台灣的社群交流，也看來不再有那麼大的規模。</p>
1267.  
1268. <p dir="auto">Brandon 的父母台灣出身，自己因家庭因素也在台灣生活多年。他對台灣社群的觀察還蠻精準的，說都我在OpenStreetMap台灣po文，看不太到其他人，版面都被我洗版了。他是有點開完笑語氣跟我這麼說，沒直接講的事情是 OpenStreetMap 台灣算是規模小的社群，我只能回說有不少人默默畫地圖，比較不愛在社群發文。他可說是相當瞭解台灣社群狀況。</p>
1269.  
1270. <p dir="auto">Mapbox的影響力大不如前，而此次State of th Map 2025呈現HOT為主的組織與人際網路，HOT AP Hub以及HOT在印度、非洲的相關社群成員關係密切，他們不少成員來到會場，從 HOT 以及青少年學子團體年輕圖客都相當活躍。</p>
1271.  
1272. <p dir="auto">Minh跟我討論Map matching 技術，除了用經過的點來判斷你是上高架道路還是留在平面道路之外，還可以判斷你是否沿著道路的人行道還是單車道移動，就不用另外加上人行道或是單車道名稱，導航系統顯示人行道或是單車道沿著的道路名稱即可。</p>
1273.  
1274. <p dir="auto">大洋洲的紐西蘭成員也有交流，與他聊不同克里澳語是否能弄維基百科，跟他指明需要確認是否有 ISO639-3 代碼。他也答應協助連結大洋洲的維基社群。</p>
1275.  
1276. <p dir="auto">另外也有與菲律賓社群的Ian Lopez聊，他比較是維基與OpenStreetMap雙棲的編輯者，第一天遇到他也是現場註冊報名，吊牌是現場製作手寫名字。有請他幫忙一些我在 ESEAP Strategy Summit 2025 提到的ESEAP 影視作品編輯計畫，Wikidata上菲律賓出品的他加祿語
1277. ／菲律賓語影視作品的標示方式，就等他有空想到方式後回應我了。</p>
1278.  
1279. <h2 dir="auto" id="section-2">亞洲社群事務</h2>
1280.  
1281. <p dir="auto">先前討論 State of the Map Asia 2025 事務，有人提議與這次 State of the Map 2025 合辦，但 Arnalie 拒絕，表示資源有限，沒有多餘資源能支援。實際到大會會場看，真得很難調度資源來弄平行一軌的 State of the Map Asia 2025，而且 State of the Map 2025 這次本身就很亞洲了，不大需要另外一軌。</p>
1282.  
1283. <p dir="auto">中國這次沒有人來，在地圖這麼政治化的表現工具，中國戰狼應對應該會被各國 OSM 參與者排擠，也很難說服說他們的敘事與表現的地圖技術還是標準，能被大家接受。我自己這幾年演講者都會講述來自中國破壞者的事蹟，歷來如何應對的方式。在這次 State of the Map 2025，不少如菲律賓、印度、台灣，都有與中國的圖客有糾紛，也表達對中國侵略性態度不悅。</p>
1284.  
1285. <p dir="auto">很高興能夠參與 State of the Map 2025 大會，要由衷感謝兩位主辦人Arnalie以及Feye，她們很努力處理大大小小的事情，成功舉辦這場大會。一些大會嚴肅議程之外，輕鬆的晚宴部分，如第二天的派對我們玩得很開心，謝謝主辦方。</p>
1286. </description>
1287.      <dc:creator>Supaplex</dc:creator>
1288.      <pubDate>Fri, 31 Oct 2025 17:19:50 +0000</pubDate>
1289.      <comments>https://www.openstreetmap.org/user/Supaplex/diary/407675#comments</comments>
1290.      <geo:lat>14.656838771985703</geo:lat>
1291.      <geo:long>121.07396140694618</geo:long>
1292.      <georss:point>14.656838771985703 121.07396140694618</georss:point>
1293.    </item>
1294.    <item>
1295.      <title>GIS mjesec osm-hr 112</title>
1296.      <link>https://www.openstreetmap.org/user/hbogner/diary/407673</link>
1297.      <guid>https://www.openstreetmap.org/user/hbogner/diary/407673</guid>
1298.      <description>&lt;p dir="auto"&gt;&lt;a href="https://osm-hr.org/2025/10/31/gis-mjesec-osm-hr-112/" rel="nofollow noopener noreferrer"&gt;GIS mjesec osm-hr 112&lt;/a&gt;&lt;/p&gt;
1299.  
1300. <p dir="auto">Dan GIS-a (GIS Day) slavi se svake srijede unutar Geography Awareness Week kako bi se istaknula važnost geografskih informacijskih sustava u obrazovanju, industriji i javnom sektoru. Ove godine je to 19.11.2025. i tijekom tog dana organiziraju se demonstracije, radionice i prezentacije koje pokazuju kako GIS pomaže u planiranju grada, upravljanju resursima i donošenju odluka temeljenih na prostoru. OpenStreetMap predstavlja dobar primjer otvorenog, zajednički stvaranog kartografskog projekta koji se često koristi kao izvor podataka u GIS projektima. Korištenje OpenStreetMap podataka i drugih otvorenih podataka u GIS-u potiče transparentnost i suradnju te pomaže bolje razumjeti i upravljati prostorom oko nas. Proširenje GIS Day akcije na OpenStreetMap aktivnost mapiranja tijekom cijelog GIS mjeseca može donijeti dugoročniji učinak, jer se stvaranje i ažuriranje otvorenih podataka prenosi iz jednokratnog događaja u kontinuiranu zajedničku aktivnost. Mi smo se odlučili za sličan pristup, akcija “GIS month osm-hr 112“</p>
1301.  
1302. <p dir="auto"><img src="https://osm-hr.org/wp-content/uploads/2025/10/gis_month_osm-hr-112.png" alt="gis month osm-hr 112" loading="lazy"></p>
1303.  
1304. <p dir="auto">Brojka 112 je višestruko simbolična jer OSM podatci pomažu u hitnim intervencijama diljem svijeta, a naša lokalna zajednica je pomagala sa aktivnostima nakon potresa 2020. godine. Brojka 112 se može smatrati i pozivom zajednici da pomogne sa stvaranjem i održavanjem OSM podataka. Osim same simbolike brojka 1-1-2 sadrži i uputstva što treba raditi svakodnevno:</p>
1305.  
1306. <pre dir="auto"><code>1 – 1 task mapirati
1307. 1 – 1 task validirati
1308. 2 – riješiti 2 notes
1309. </code></pre>
1310.  
1311. <p dir="auto">Kako sudjelovati?</p>
1312.  
1313. <p dir="auto">Svaki dan tokom mjeseca na tasks serveru odaberite jedan od GIS-MONTH projekata. Među njima odaberite jedan slobodan task za mapiranje, te dodajte sve što nedostaje. Nakon toga odaberite nečiji tuđi task za validaciju, te provjerite je li dodano sve što treba biti. Nakon toga proučite notes, bilo putem weba, bilo putem popisa, te riješite makar 2 prijave. U ovom trenutku imamo preko 2600 otvorenih prijava, pomozite nam da to riješimo.</p>
1314.  
1315. <p dir="auto">Na kraju mjeseca možemo usporediti stanje prije i poslije ove akcije i vidjeti njen efekt u brojkama i grafovima.</p>
1316.  
1317. <p dir="auto">Sretno mapiranje!</p>
1318. </description>
1319.      <dc:creator>hbogner</dc:creator>
1320.      <pubDate>Fri, 31 Oct 2025 13:23:09 +0000</pubDate>
1321.      <comments>https://www.openstreetmap.org/user/hbogner/diary/407673#comments</comments>
1322.    </item>
1323.    <item>
1324.      <title>Obchvat Českého Krumlova – výstavba, nebo jiné chování za volantem?</title>
1325.      <link>https://www.openstreetmap.org/user/Jiri%20Podhorecky/diary/407671</link>
1326.      <guid>https://www.openstreetmap.org/user/Jiri%20Podhorecky/diary/407671</guid>
1327.      <description>&lt;p dir="auto"&gt;Český Krumlov stojí před rozhodnutím, které zdaleka není jen technické. Postavit severní obchvat, anebo hledat jiná řešení dopravní zátěže? Na první pohled jde o jasný krok. Odvést tranzit mimo město. Jenže realita krajiny, chráněných území a členitého terénu ukazuje, že nic takového nejde udělat bez následků. Severní svahy města přecházejí do CHKO Blanský les a přírodního parku Cvičák, kde každý zásah znamená dlouhodobou změnu charakteru krajiny. Městská varianta trasy zas počítá s tunelem, který by stavbu významně prodražil. Ani jedno ale nepovažuji za kvalitní odpověď k výzvě, co s dopravní situací.&lt;/p&gt;
1328.  
1329. <p dir="auto"><img src="https://opu.peklo.biz/p/25/10/29/1761767183-d7dec.jpg" alt="Alternativní text" loading="lazy">
1330. <strong>obrázek: Zelení Český Krumlov</strong></p>
1331.  
1332. <h2 dir="auto" id="kdy-technika-naraz-na-tern">Když technika narazí na terén</h2>
1333.  
1334. <p dir="auto">Plánovaný obchvat se opírá o logiku dopravního inženýrství: přesměrovat proud vozidel a zklidnit hlavní tranzitní tepnu. Problém je, že území severně od města je členité a ekologicky cenné. Silnice by musela vést s velkými terénními úpravami, anebo částečně tunelem, v obou případech by vizuálně i fakticky rozdělila obytné i klidové území. Město i kraj s tím počítají, ale otázkou zůstává, zda přínos odpovídá ceně – finanční i ekologické.</p>
1335.  
1336. <h2 dir="auto" id="dopravn-indukce--past-novch-silnic">Dopravní indukce – past nových silnic</h2>
1337.  
1338. <p dir="auto">Dopravní teorie mluví jasně: nová komunikace zpravidla přitáhne nová auta. Řidiči rychle přizpůsobí své trasy, časy i návyky. Co se na první pohled zdá jako úleva, se po pár letech může změnit v návrat k původnímu stavu – jen s větším provozem a vyšší zátěží prostředí. Fenomén dopravní indukce není domněnka, ale opakovaně ověřený jev. Tam, kde se zvyšuje kapacita bez omezení poptávky, roste i intenzita dopravy.</p>
1339.  
1340. <h2 dir="auto" id="tranzit-nen-jeden-proud">Tranzit není jeden proud</h2>
1341.  
1342. <p dir="auto">Městem neprojíždí jen osobní auta, nebo jen kamiony. Proud tvoří i dodávky, turistické autobusy do Krumlova, autobusy směřující na Lipno, nebo do blízkého okolí. Každá z těchto skupin účastníků provozu se chová jinak, v jiný čas a s jiným cílem. Proto ani jedno řešení – ať už nový obchvat, nebo zákaz vjezdu – nemůže účinně zasáhnout všechny. Město by potřebovalo jemnější nástroje, které rozlišují různé typy dopravy a reagují na ně cíleně.</p>
1343.  
1344. <h2 dir="auto" id="zen-chovn-msto-betonovch-een">Řízení chování místo betonových řešení</h2>
1345.  
1346. <p dir="auto">Jedním z možných kroků by mohlo být řízení dopravy pomocí časových slotů. Například tranzit směrem na Lipno by mohl být rozdělen do vyhrazených časových pásem, kdy by průjezd byl bezplatný. Řidiči, kteří by jeli mimo tato období, by automaticky zaplatili mýtné prostřednictvím brány. Tím by se část provozu přirozeně rozložila do méně exponovaných hodin a zároveň by se omezil hluk a znečištění ve špičkách.</p>
1347.  
1348. <p dir="auto">Podobné principy již fungují ve městech, kde chtěli omezit nadměrný provoz, ale bez uzavírek. Nejde o trest, ale o motivaci – kdo se přizpůsobí pravidlům, jede levněji a plynuleji. Kdo ne, přispěje na údržbu infrastruktury.</p>
1349.  
1350. <h2 dir="auto" id="citlivj-alternativy">Citlivější alternativy</h2>
1351.  
1352. <p dir="auto">Vedle regulace dopravy lze posílit i jiné způsoby mobility: lepší veřejná doprava mezi Krumlovem, Lipnem a Českými Budějovicemi, rozšíření parkovišť P+R a podpora cyklotras pro místní dopravu. Víc menších změn může dohromady přinést efekt dřív, než jedna velká stavba.  Neměl by se vytěsnit i záměr elektrifikace železniční trati do Kájova, což je v principu příspěvek pro lepší ekologii dopravy.</p>
1353.  
1354. <h2 dir="auto" id="problm-nen-jen-na-map">Problém není jen na mapě</h2>
1355.  
1356. <p dir="auto">Rozhodnutí o obchvatu není jen otázkou vytýčení trasy v katastru města. Je to zrcadlo vztahu lidí ke krajině i k vlastní dopravní kultuře. Pokud se budeme snažit vyřešit přetížení města jen další objížďkou, vytvoříme spíš novou ránu v krajině, než trvalou úlevu. Skutečné řešení může být jinde – v ochotě přemýšlet o dopravě jako o lidském chování, ne jen jako o technickém problému.</p>
1357. </description>
1358.      <dc:creator>Jiri Podhorecky</dc:creator>
1359.      <pubDate>Fri, 31 Oct 2025 00:24:48 +0000</pubDate>
1360.      <comments>https://www.openstreetmap.org/user/Jiri%20Podhorecky/diary/407671#comments</comments>
1361.      <geo:lat>48.823819003701075</geo:lat>
1362.      <geo:long>14.307117462158203</geo:long>
1363.      <georss:point>48.823819003701075 14.307117462158203</georss:point>
1364.    </item>
1365.    <item>
1366.      <title>Bank and ditch</title>
1367.      <link>https://www.openstreetmap.org/user/foxandpotatoes/diary/407665</link>
1368.      <guid>https://www.openstreetmap.org/user/foxandpotatoes/diary/407665</guid>
1369.      <description>&lt;h1 dir="auto" id="bank-and-ditch"&gt;Bank and ditch&lt;/h1&gt;
1370.  
1371. <h2 dir="auto" id="preliminary">Preliminary</h2>
1372.  
1373. <p dir="auto">This is a provisional report about a future proposition for specific tags for the following types of banks and ditches:</p>
1374.  
1375. <ul dir="auto">
1376.  <li>bank and ditch barrier</li>
1377.  <li>hedge and ditch barrier</li>
1378.  <li>canal d’abissage</li>
1379.  <li>fossé bordier</li>
1380.  <li>talus</li>
1381.  <li>old way (e.g. <a href="https://www.openstreetmap.org/way/696637714" rel="nofollow noopener noreferrer">Tiense Groef</a>)</li>
1382. </ul>
1383.  
1384. <p dir="auto">We have presently (30 October 2025) the following tags:</p>
1385.  
1386. <ul dir="auto">
1387.  <li>barrier=ditch - A man-made ditch or a trench is a long and narrow man-made barrier dug in the ground to prevent access to the other side. No precision about the type of the ditch. 82262 occurrences</li>
1388.  <li>military=trench - Is used to map a military trench: an excavation in the ground that is generally deeper than it is wide, dug into the ground as a barrier for military purposes (e.g. trench warfare). 25148 occurrences</li>
1389.  <li>natural=earth_bank - Not a man-made feature. 19672 occurrences.</li>
1390.  <li>natural=valley - Not a man_made feature. 59800 occurrences.</li>
1391.  <li>natural=cliff - Not a man_made feature. 916448 occurrences.</li>
1392.  <li>waterway=ditch - A simple narrow artificial waterway used to drain nearby land, to remove storm-water or similar. 4438049 occurrences.</li>
1393.  <li>waterway=drain - Artificial waterways, typically lined with concrete or similar, used to carry superfluous water like storm water or grey-discharge. 1801170 occurrences.</li>
1394.  <li>man_made=embankment - Is used to map an artificial slope or steep incline built for example to provide a level platform on top for a road or railway line or to otherwise shape or stabilize the terrain. For micro-mapped embankments, it is not possible to specify the dimensions (height, width). 307709 occurrences.</li>
1395.  <li>embankment=yes - Add this tag to a way that is already tagged with a highway=<em>, railway=</em> or waterway=* tag. 278223 occurrences.</li>
1396. </ul>
1397.  
1398. <p dir="auto">None of them seem to <strong>exactly</strong> concern the <em>banks and ditches</em> mentioned above.</p>
1399.  
1400. <h2 dir="auto" id="bank-and-ditch-1">Bank and ditch</h2>
1401.  
1402. <p dir="auto">

<em>Bank and ditch</em> or <em>hedge and ditch</em> are man made earthworks in the landscape. All have a historic interest as being the landmark for present and past administrative boundaries. They were used to limit lands, parish, communes, forests, etc.</p>
1403.  
1404. <p dir="auto">
They are not designed for drainage even if water can flow in the ditch. 
</p>
1405.  
1406. <p dir="auto">They can be found under various names :</p>
1407.  
1408. <ul dir="auto">
1409.  <li>in English: ditch, bank, bank and ditch, hedge and ditch, dry ditch, earth bank, ditch earthworks, levee, ha-ha</li>
1410.  <li>in French: fossé, talus, talus-fossé, berme, bourrelet de terre, levée, levée de terre, saut de loup, ha-ha hâ-hâ</li>
1411.  <li>in Dutch: landweer, Ha-Ha, Aha</li>
1412.  <li>in German: Ha-Ha, Aha</li>
1413. </ul>
1414.  
1415. <p dir="auto">
Usually, the ditch and the bank are parallel. Occasionally, it can happen there is one ditch and two banks on either sides, a single bank and a ditch on either sides.</p>
1416.  
1417. <p dir="auto">Hillshade LiDAR-derived imagery gives an good opportunity to observe their tracks. They have been studied in various articles:</p>
1418.  
1419. <ul dir="auto">
1420.  <li>Boundaries in the Landscape – Banks, Ditches and Walls, See <a href="https://fr.wikipedia.org/wiki/Clos-masure" rel="nofollow noopener noreferrer">1</a></li>
1421.  <li>
Section of an early medieval boundary ditch known as the Nico Ditch on Denton golf course 320 m south west of Lodge Farm. See <a href="https://historicengland.org.uk/listing/the-list/list-entry/1016197" rel="nofollow noopener noreferrer">2</a></li>
1422.  <li>Banks and Ditches on the Northern Malvern Hills. See <a href="https://www.malvernhills.org.uk/media/1463/enclosures-leaflet-final-mhaonb.pdf" rel="nofollow noopener noreferrer">3</a></li>
1423.  <li>Pits, Platforms, Banks and Ditches. See <a href="https://ukeconet.org/wp-content/uploads/2012/12/Leaflet_4_Pits_Platforms.pdf" rel="nofollow noopener noreferrer">4</a></li>
1424. </ul>
1425.  
1426. <h2 dir="auto" id="usual-suggested-tags-are">Usual suggested tags are:</h2>
1427.  
1428. <pre dir="auto"><code>barrier = ditch
1429. ditch:type = bank_and_ditch
1430. historic = yes
1431. </code></pre>
1432.  
1433. <h2 dir="auto" id="other-ditches-and-barriers-with-no-specific-tag">Other ditches and barriers with no specific tag</h2>
1434.  
1435. <h3 dir="auto" id="hedge-and-ditch">Hedge and ditch</h3>
1436.  
1437. <p dir="auto">[tbd]</p>
1438.  
1439. <h3 dir="auto" id="canal-dabissage">Canal d’abissage</h3>
1440.  
1441. <p dir="auto">Used for an artificial waterway designed as a watercourse in a ditch created for this purpose, a ditch called ri d’abissage” or ry d’abissage or fossé d’abissage or bief d’abissage depending on the region, in order to bring it upstream of the meadows to be irrigated. See <a href="https://fr.wikipedia.org/wiki/Abissage" rel="nofollow noopener noreferrer">6</a>.</p>
1442.  
1443. <h3 dir="auto" id="foss-bordier">Fossé bordier</h3>
1444.  
1445. <p dir="auto">Fossé qui délimite d’anciennes parcelles exploitées de manière discontinue depuis au moins deux millénaires en Narbonnaise. Sa présence marque la trace sur le sol de l’appropriation d’un terroir et d’anciennes mises en culture. Ditch which delimits former plots of land which have been exploited discontinuously for at least two millennia in the Narbonnaise region. Its presence marks the trace on the soil of the appropriation of a terroir and old cultivation.</p>
1446.  
1447. <h3 dir="auto" id="talus">Talus</h3>
1448.  
1449. <p dir="auto">[tbd]</p>
1450.  
1451. <h3 dir="auto" id="talus-plants">Talus plantés</h3>
1452.  
1453. <p dir="auto">Are one of the identity elements of the clos-masure. Fencing off the plot of land which includes all the buildings, the high jet trees are planted on land levees 1.5 to 2.5 m wide and 0.6 m to 1.30 m high. In Normandy. See <a href="https://fr.wikipedia.org/wiki/Clos-masure" rel="nofollow noopener noreferrer">7</a></p>
1454.  
1455. <h3 dir="auto" id="limites-de-centuriations">Limites de centuriations</h3>
1456.  
1457. <p dir="auto">Centuriation (in Latin centuriatio or, more usually, limitatio, also known as Roman grid, was a method of land measurement used by the Romans. In many cases land divisions based on the survey formed a field system, often referred to in modern times by the same name. It may appear in the form of roads, canals and agricultural plots. Maybe not of interest presently on OSM!</p>
1458.  
1459. <p dir="auto">[text to be clarified and completed]</p>
1460. </description>
1461.      <dc:creator>foxandpotatoes</dc:creator>
1462.      <pubDate>Thu, 30 Oct 2025 17:21:34 +0000</pubDate>
1463.      <comments>https://www.openstreetmap.org/user/foxandpotatoes/diary/407665#comments</comments>
1464.    </item>
1465.    <item>
1466.      <title>Purchase Historical Eswatini Topographic Maps</title>
1467.      <link>https://www.openstreetmap.org/user/Firefishy/diary/407664</link>
1468.      <guid>https://www.openstreetmap.org/user/Firefishy/diary/407664</guid>
1469.      <description>&lt;p dir="auto"&gt;I’m raising funds to purchase the historic 1:50,000 topographic map series of Eswatini (formerly Swaziland), so I can preserve and share them online as a seamless, zoomable mosaic - free for everyone.&lt;/p&gt;
1470.  
1471. <p dir="auto">In 2008 I successfully raised £1000 to acquire the equivalent series for Namibia (South West Africa). You can explore that project here: <a href="https://namibia-topo.openstreetmap.org.za/" rel="nofollow noopener noreferrer" dir="auto">https://namibia-topo.openstreetmap.org.za/</a></p>
1472.  
1473. <p dir="auto">Donate and more information:
1474. <a href="https://www.gofundme.com/f/purchase-historical-eswatini-topographic-maps" rel="nofollow noopener noreferrer" dir="auto">https://www.gofundme.com/f/purchase-historical-eswatini-topographic-maps</a></p>
1475. </description>
1476.      <dc:creator>Firefishy</dc:creator>
1477.      <pubDate>Thu, 30 Oct 2025 17:09:05 +0000</pubDate>
1478.      <comments>https://www.openstreetmap.org/user/Firefishy/diary/407664#comments</comments>
1479.      <geo:lat>-26.325950845233468</geo:lat>
1480.      <geo:long>31.14451825618744</geo:long>
1481.      <georss:point>-26.325950845233468 31.14451825618744</georss:point>
1482.    </item>
1483.  </channel>
1484. </rss>
1485.  

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