Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.openstreetmap.org/diary/rss

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:georss="http://www.georss.org/georss">
  3.  <channel>
  4.    <title>OpenStreetMap diary entries</title>
  5.    <description>Recent diary entries from users of OpenStreetMap</description>
  6.    <link>https://www.openstreetmap.org/diary</link>
  7.    <image>
  8.      <url>https://www.openstreetmap.org/assets/mag_map-rss2.0-670446293cd86fe914428d8e837bf3cf6f382bf122a926db7d02900e0d9220e2.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>Hussain Street, Rasool Park Lahore</title>
  16.      <link>https://www.openstreetmap.org/user/Adeel%20Shafqat/diary/44710</link>
  17.      <guid>https://www.openstreetmap.org/user/Adeel%20Shafqat/diary/44710</guid>
  18.      <description>&lt;p&gt;Hussain Street, Rasool Park Lahore&lt;/p&gt;
  19. </description>
  20.      <dc:creator>Adeel Shafqat</dc:creator>
  21.      <pubDate>Fri, 17 Aug 2018 10:00:32 +0000</pubDate>
  22.      <comments>https://www.openstreetmap.org/user/Adeel%20Shafqat/diary/44710#comments</comments>
  23.      <geo:lat>31.5376997490007</geo:lat>
  24.      <geo:long>74.3099261820316</geo:long>
  25.      <georss:point>31.5376997490007 74.3099261820316</georss:point>
  26.    </item>
  27.    <item>
  28.      <title>posting screen shots (rendered in Microsoft Paint) in "New Diary Entry"</title>
  29.      <link>https://www.openstreetmap.org/user/Robert%20Copithorne/diary/44707</link>
  30.      <guid>https://www.openstreetmap.org/user/Robert%20Copithorne/diary/44707</guid>
  31.      <description>&lt;p&gt;How do I post screen shots in new diary entries?&lt;/p&gt;
  32. </description>
  33.      <dc:creator>Robert Copithorne</dc:creator>
  34.      <pubDate>Fri, 17 Aug 2018 04:28:36 +0000</pubDate>
  35.      <comments>https://www.openstreetmap.org/user/Robert%20Copithorne/diary/44707#comments</comments>
  36.    </item>
  37.    <item>
  38.      <title>Vetorização semi-automática de matas densas com Sentinel-2</title>
  39.      <link>https://www.openstreetmap.org/user/smaprs/diary/44705</link>
  40.      <guid>https://www.openstreetmap.org/user/smaprs/diary/44705</guid>
  41.      <description>&lt;p&gt;Neste post descrevo, e submeto a opiniões, os passos adotados para um
  42. processamento semi-automático de
  43. vetorização a partir de imagem de satélite Sentinel-2
  44. tendo em vista a vetorização de áreas de matas
  45. com suficiente distinção entre &lt;code&gt;natural=wood&lt;/code&gt; e &lt;code&gt;landuse=forest&lt;/code&gt; (mata natural e mata cultivada).&lt;/p&gt;
  46.  
  47. &lt;p&gt;&lt;strong&gt;Importante:&lt;/strong&gt;&lt;br/&gt;
  48. esta metodologia é aqui proposta como um auxilío destinado somente ao mapeamento de coberturas de terreno (landcover).&lt;br/&gt;
  49. O processo todo resulta em simplificação, como curvas com espaçamento entre nós não menor que 10m (a resolução da imagem é 10m/px).&lt;br/&gt;
  50. Não serve para objetos pequenos como lotes, praças, etc., pois removeria detalhes que podem ser vistos nas imagens padrão do OSM.&lt;/p&gt;
  51.  
  52. &lt;p&gt;O propósito é:&lt;br/&gt;
  53. -poder gerar desenho de grandes áreas de mata densa, em interiores do território, não densamente urbanizados;&lt;br/&gt;
  54. -com diferenciação de vegetação usando índices apropriados, para forest e wood, o que não é facilmente, e/ou comumente, distinguido nos desenhos sobre as imagens padrão.
  55. Mesmo assim, deve ser verificado visualmente o resultado ao final do processamento, junto com as imagens padrão do OSM.&lt;/p&gt;
  56.  
  57. &lt;h2&gt;DESCRIÇÃO INICIAL DOS DADOS:&lt;/h2&gt;
  58.  
  59. &lt;p&gt;IMAGENS: SENTINEL-2&lt;br/&gt;
  60. Cobertura: ~100x100Km&lt;/p&gt;
  61.  
  62. &lt;p&gt;Documentação original:&lt;br/&gt;
  63. &lt;a href="https://www.sentinel-hub.com/develop/documentation/eo_products/Sentinel2EOproducts" rel="nofollow"&gt;https://www.sentinel-hub.com/develop/documentation/eo_products/Sentinel2EOproducts&lt;/a&gt;&lt;/p&gt;
  64.  
  65. &lt;p&gt;Licença compatível com OSM:&lt;br/&gt;
  66. conforme &lt;a href="https://wiki.openstreetmap.org/wiki/Sentinel-2" rel="nofollow"&gt;https://wiki.openstreetmap.org/wiki/Sentinel-2&lt;/a&gt;&lt;/p&gt;
  67.  
  68. &lt;p&gt;Fonte das imagens:&lt;br/&gt;
  69. &lt;a href="https://earthexplorer.usgs.gov/" rel="nofollow"&gt;https://earthexplorer.usgs.gov/&lt;/a&gt; camadas Sentinel-2&lt;/p&gt;
  70.  
  71. &lt;p&gt;Bandas utilizadas: B11&lt;br/&gt;
  72. (testadas todas as bandas, B11 se mostrou a melhor para o objetivo; condição:nuvem=0)  &lt;/p&gt;
  73.  
  74. &lt;h2&gt;Índices utilizados: NDVI; CRE  &lt;/h2&gt;
  75.  
  76. &lt;p&gt;NDVI : Normalized Difference Vegetation Index  &lt;/p&gt;
  77.  
  78. &lt;h2&gt;&lt;code&gt;Fórmula: NDVI = (B08 - B04) / (B08 + B04)&lt;/code&gt;&lt;/h2&gt;
  79.  
  80. &lt;p&gt;CRE : Chlorophyll Red-Edge  (abbrv. Chlred-edge)&lt;br/&gt;
  81. &lt;code&gt;Fórmula: CRE = (B07 / B05) ^ -1&lt;/code&gt;&lt;/p&gt;
  82.  
  83. &lt;h2&gt;PROCESSAMENTO - PASSOS:&lt;/h2&gt;
  84.  
  85. &lt;p&gt;&lt;strong&gt;1)ESCOLHA DA IMAGEM DE SATÉLITE - SENTINEL:&lt;/strong&gt;&lt;br/&gt;
  86. Escolhida imagem em data que não gere discrepâncias (para mais ou para menos) de atividade vegetal:
  87. preferencialmente entre equinócio e solstício; evitar alto inverno e alto verão.&lt;/p&gt;
  88.  
  89. &lt;p&gt;Caso Bom Jesus, RS:&lt;br/&gt;
  90. &lt;a href="https://earthexplorer.usgs.gov/" rel="nofollow"&gt;https://earthexplorer.usgs.gov/&lt;/a&gt; - Sentinel -  &amp;quot;T22JEP_20180420T132231_B11&amp;quot;&lt;br/&gt;
  91. Data: 2018/04/20&lt;br/&gt;
  92. Hora: 13:22 (09:22 Brasil; gera alguma sombra)&lt;br/&gt;
  93. (A imagem abaixo pode ser aberta em nova guia para visualizar detalhes em zoom maior.)&lt;br/&gt;
  94. &lt;img src="https://i.imgur.com/n3LV9qJ.jpg" alt=""/&gt;&lt;/p&gt;
  95.  
  96. &lt;hr/&gt;
  97.  
  98. &lt;p&gt;&lt;strong&gt;2)Examinar no QGIS valores do raster; procurar valores limites de distinções de classes:&lt;/strong&gt;
  99. CASO  Bom Jesus, RS:&lt;/p&gt;
  100.  
  101. &lt;hr/&gt;
  102.  
  103. &lt;p&gt;SENSOR / ÍNIDICE          :: B11         :: NDVI       ::  CRE&lt;br/&gt;
  104. Min.                     :: 511         :: -0.87       :: 0.2&lt;br/&gt;
  105. Max.                     ::   2709      ::   +0.87     ::   0.75   &lt;/p&gt;
  106.  
  107. &lt;hr/&gt;
  108.  
  109. &lt;p&gt;MATA NATIVA  (n.=wood)    ::    1200-1800::0.30  /0.80  ::&lt;br/&gt;
  110. MATA PLANTADA(l.=forest)  ::150-1200     ::  0.70/0.80  ::  &lt;/p&gt;
  111.  
  112. &lt;p&gt;Mata na sombra(encosta.S) ::150-400      ::0.30/0.65    :: 0.4  -  0.5&lt;br/&gt;
  113. Mata no sol   (encosta.N) :    1200-1800 ::    0.65/0.80::  0.25-0.3  &lt;/p&gt;
  114.  
  115. &lt;p&gt;campo ralo (null)      :: 1500  -3000 ::             :&lt;br/&gt;
  116.   urbanização            ::   1700-3000 ::-0.10/0.20   :  &lt;/p&gt;
  117.  
  118. &lt;p&gt;água parada (açude)    :: 50-150      ::-0.10/0.10   ::    0.8-1.0&lt;br/&gt;
  119.   água corrente (rio)    ::    150-300  ::  -0.30/0.60 :: 0.5-0.8  &lt;/p&gt;
  120.  
  121. &lt;p&gt;LIMITE P/ ÁGUA = 0        ::    0.5      &lt;/p&gt;
  122.  
  123. &lt;p&gt;Resultado observado:&lt;br/&gt;
  124. B11 distingue bem entre mata wood e forest.
  125. Em diferentes áreas do terreno abrangido na imagem, as mesmas classes de matas possuem alguma variação, apresentando ainda algum grau de imprecisão.
  126. Não separa rios de forest; para isto necessita constrastar B11 com outros índices.&lt;br/&gt;
  127. -NDVI e CRE destacam o que não é vegetação, como corpos de água.&lt;/p&gt;
  128.  
  129. &lt;p&gt;[IMAGEM-2]&lt;/p&gt;
  130.  
  131. &lt;hr/&gt;
  132.  
  133. &lt;p&gt;&lt;strong&gt;3)CORREÇÕES:&lt;/strong&gt;&lt;br/&gt;
  134. Corrigir o que não é bem detectado ou misturado quando somente usando na B11:&lt;br/&gt;
  135. mata na sombra (encostas Sul); água corrente&lt;/p&gt;
  136.  
  137. &lt;p&gt;Método: usados os índices NDVI e CRE para contrastar B11  &lt;/p&gt;
  138.  
  139. &lt;p&gt;OPERAÇÃO: B11+(1-NDVI)+CRE&lt;br/&gt;
  140. Raster calculator - SINTAXE: &lt;code&gt;&amp;quot;[email protected]&amp;quot;  + ((1-&amp;quot;[email protected]&amp;quot;)*1800) + (&amp;quot;[email protected]&amp;quot; *2600)&lt;/code&gt;&lt;br/&gt;
  141. Agregados empiricamente os fatores ponderadores NDVI*1800 e CRE*2600, para que fiquem acima de B11 (~2000) e equilibrá-los.  &lt;/p&gt;
  142.  
  143. &lt;p&gt;RESULTADO:    &amp;quot;B11+1-NDVI+CRE.tif&amp;quot;  :  (10m/px)  &lt;/p&gt;
  144.  
  145. &lt;p&gt;[IMAGEM-3]&lt;/p&gt;
  146.  
  147. &lt;hr/&gt;
  148.  
  149. &lt;p&gt;&lt;strong&gt;4)TESTAR CLASSES VISUALMENTE:&lt;/strong&gt;&lt;br/&gt;
  150. -Igual à etapa (2), para B11+1-NDVI+CRE:  &lt;/p&gt;
  151.  
  152. &lt;p&gt;Resultado:&lt;br/&gt;
  153. 5 CLASSES :&lt;br/&gt;
  154. (1)forest                &amp;lt;= 2150 &amp;lt;&lt;br/&gt;
  155. (2)wood                  &amp;lt;= 2600 &amp;lt;&lt;br/&gt;
  156. (3)campo alto ou ciliar  &amp;lt;= 3500 &amp;lt;&lt;br/&gt;
  157. (4)campo ralo ou trilha  &amp;lt;= 3950 &amp;lt;&lt;br/&gt;
  158. (5)água, estrada, cidade, lavourado  &lt;/p&gt;
  159.  
  160. &lt;hr/&gt;
  161.  
  162. &lt;p&gt;&lt;strong&gt;5)PROCESSAR A IMAGEM, REDUZINDO ÀS CLASSES TESTADAS:&lt;/strong&gt;  &lt;/p&gt;
  163.  
  164. &lt;p&gt;CONDICIONAIS  &amp;quot;if/then/else&amp;quot;:&lt;br/&gt;
  165. Raster calculator:&lt;br/&gt;
  166. SINTAXE: &lt;code&gt;((&amp;quot;@1&amp;quot;&amp;lt;x)* operação )&lt;/code&gt; =&amp;gt; se sim=1(opera); se não=0(não opera)  &lt;/p&gt;
  167.  
  168. &lt;p&gt;SINTAXE  :&lt;br/&gt;
  169. &lt;code&gt;(1*  ( &amp;quot;[email protected]&amp;quot;  &amp;lt;=2150 ))&lt;/code&gt;&lt;br/&gt;
  170. &lt;code&gt;+ (2* (( 2150 &amp;lt;  &amp;quot;[email protected]&amp;quot; ) AND ( &amp;quot;[email protected]&amp;quot; &amp;lt;=  2600 ) ))&lt;/code&gt;&lt;br/&gt;
  171. &lt;code&gt;+ (3* (( 2600 &amp;lt;  &amp;quot;[email protected]&amp;quot; ) AND ( &amp;quot;[email protected]&amp;quot; &amp;lt;=  3500 ) ))&lt;/code&gt;&lt;br/&gt;
  172. &lt;code&gt;+ (4* (( 3500 &amp;lt;  &amp;quot;[email protected]&amp;quot; ) AND ( &amp;quot;[email protected]&amp;quot; &amp;lt;=  3950 ) ))&lt;/code&gt;&lt;br/&gt;
  173. &lt;code&gt;+ (5*  ( &amp;quot;[email protected]&amp;quot; &amp;gt; 3950  ))&lt;/code&gt;  &lt;/p&gt;
  174.  
  175. &lt;p&gt;Resultado:&lt;br/&gt;
  176. Imagem com valores limitados às classes:    &amp;quot;B11-5classes.tif&amp;quot;  &lt;/p&gt;
  177.  
  178. &lt;p&gt;[IMAGEM-4]&lt;/p&gt;
  179.  
  180. &lt;hr/&gt;
  181.  
  182. &lt;p&gt;&lt;strong&gt;6)SIMPLIFICAR ÁREAS, REMOVER PIXELS ISOLADOS:&lt;/strong&gt;&lt;/p&gt;
  183.  
  184. &lt;p&gt;OPERAÇÕES:  ~1min cada&lt;br/&gt;
  185. QGIS: Processing / Toolbox /&lt;br/&gt;
  186. &lt;code&gt;* GDAl / Analysis  / Sieve&lt;/code&gt;&lt;br/&gt;
  187. &lt;code&gt;* GRASS / r.neighbor&lt;/code&gt;&lt;/p&gt;
  188.  
  189. &lt;p&gt;1 Sieve     T3 C8 - Remove até 3px(10x30m)&lt;br/&gt;
  190. 2 Neig Max   3 Ci - Aumenta borda do maior, 1px cada lado (10m+10m)&lt;br/&gt;
  191. 3 Sieve     T3 C4&lt;br/&gt;
  192. 4 Neig Mode  3 Sq&lt;br/&gt;
  193. 5 Sieve     T6 C8 - Remove até 6px(20x30m)&lt;/p&gt;
  194.  
  195. &lt;p&gt;Resultado:&lt;br/&gt;
  196. 5 classes filtradas: &amp;quot;B11-5classes-Filtrado.tif&amp;quot;  (10m/px)     &lt;/p&gt;
  197.  
  198. &lt;p&gt;[IMAGEM-5]&lt;/p&gt;
  199.  
  200. &lt;hr/&gt;
  201.  
  202. &lt;p&gt;&lt;strong&gt;7)REDUZIR A IMAGEM SOMENTE ÀS CLASSES DE INTERESSE (forest e wood; 1 e 2) E IGUALAR DEMAIS CLASSES (3,4,5) A &amp;quot;ZERO&amp;quot;:&lt;/strong&gt;&lt;/p&gt;
  203.  
  204. &lt;p&gt;QGIS: Raster calculator: &lt;code&gt;(( &amp;quot;@1&amp;quot; &amp;gt; 2 ) * 0) + (( &amp;quot;@1&amp;quot; &amp;lt;=2 ) * &amp;quot;@1&amp;quot; )&lt;/code&gt;&lt;/p&gt;
  205.  
  206. &lt;hr/&gt;
  207.  
  208. &lt;p&gt;&lt;strong&gt;8)CRUZAR O RASTER PROCESSADO COM OS VETORES EXISTENTES NO OSM, DE RIOS E ESTRADAS, PARA MELHORAR RECORTES NAS MATAS:&lt;/strong&gt;  &lt;/p&gt;
  209.  
  210. &lt;p&gt;-Baixar dados do OSM/overpass: highway=* or waterway=* and type:way&lt;br/&gt;
  211. -Criar um novo layer vetor SHP contendo as linhas de highway e waterway que servirão para recortar.&lt;br/&gt;
  212. -Adicionar um campo de número real, com valor &amp;quot;0&amp;quot;(zero) para todas as linhas/polígonos a serem filtrados&lt;br/&gt;
  213. -Gerar um buffer sobre todas as linhas:&lt;br/&gt;
  214. o buffer deve ser maior que a resolução da imagem destino e menor que os menores grupos de pixels após as filtragens.&lt;br/&gt;
  215. Para não gerar pixels ligados só nos cantos nem elminar a mais do que as filtragens anteriores.&lt;br/&gt;
  216. Utilizado buffer de 20m; suficiente para imagem de 10m/px. Contendo valor classe=0.&lt;br/&gt;
  217. -Salvar o buffer como SHP  &lt;/p&gt;
  218.  
  219. &lt;p&gt;RASTERIZAR O VETOR SOBRE A IMAGEM:&lt;br/&gt;
  220. -Fazer uma cópia simples do raster anteriormente processado, a ser alterada&lt;br/&gt;
  221. -Adicionar o layer vetor do buffer sobre a imagem destino:&lt;br/&gt;
  222. QGIS: Raster / Conversion / Rasterize: SHP com o buffer; campo p/ valor &amp;quot;0&amp;quot;(zero); imagem destino  &lt;/p&gt;
  223.  
  224. &lt;p&gt;ÚLTIMA FILTRAGEM:&lt;br/&gt;
  225. simplificar; remover últimos pequenos clumps de até 20 pixels isolados (4x5 pixels) que sobram em alguns recortes :
  226. Sieve T20 C4&lt;/p&gt;
  227.  
  228. &lt;p&gt;Resultado:
  229. &amp;quot;B11-0-1-2-Filtrado+OSM.tif&amp;quot; &lt;/p&gt;
  230.  
  231. &lt;p&gt;Não é objetivo do processo captar áreas com menos de 40x40m nas distinções, o que equivale a pouco, o que gera muitas imprecisões.
  232. Somente áreas de matas com maior homogeneidade, que possuem dimensões muito maiores. &lt;/p&gt;
  233.  
  234. &lt;p&gt;[IMAGEM-6]&lt;/p&gt;
  235.  
  236. &lt;hr/&gt;
  237.  
  238. &lt;p&gt;&lt;strong&gt;9) ELIMINAR DEMAIS CLASSES NÃO UTILIZADAS - Igualar &amp;quot;zero&amp;quot; a &amp;quot;null&amp;quot;:&lt;/strong&gt;&lt;br/&gt;
  239. (ajuda a reduzir a quantidade de polígnos no poligonize):  &lt;/p&gt;
  240.  
  241. &lt;p&gt;&lt;code&gt;QGIS: gdal_translate / -a_nodata &amp;lt;X&amp;gt;&lt;/code&gt;&lt;br/&gt;
  242. ( = valor da classe p/null)&lt;/p&gt;
  243.  
  244. &lt;p&gt;Resultado:&lt;br/&gt;
  245. Raster Classes 1+2+null : &amp;quot;B11-1-2-null+OSM.tif&amp;quot; &lt;/p&gt;
  246.  
  247. &lt;hr/&gt;
  248.  
  249. &lt;p&gt;&lt;strong&gt;10)VETORIZAR - Gerar polígonos do raster:&lt;/strong&gt;&lt;/p&gt;
  250.  
  251. &lt;p&gt;&lt;code&gt;QGIS: Raster / conversion / poligonize&lt;/code&gt;&lt;br/&gt;
  252. MANTER A MESMA CRS NO PROJETO&lt;/p&gt;
  253.  
  254. &lt;hr/&gt;
  255.  
  256. &lt;p&gt;&lt;strong&gt;11)SUAVIZAR POLÍGONOS - despixelizar:&lt;/strong&gt;&lt;br/&gt;
  257. &lt;code&gt;QGIS: GRASS commands -&amp;gt; v.generalize.smooth:&lt;/code&gt;&lt;br/&gt;
  258. (&lt;a href="https://grass.osgeo.org/grass64/manuals/v.generalize.html" rel="nofollow"&gt;https://grass.osgeo.org/grass64/manuals/v.generalize.html&lt;/a&gt;)  &lt;/p&gt;
  259.  
  260. &lt;p&gt;&lt;code&gt;* Sliding Averaging:&lt;/code&gt;&lt;br/&gt;
  261. look_ahead = 3 (min=3, sempre ímpar)
  262. slide = 0.7 &lt;/p&gt;
  263.  
  264. &lt;p&gt;Resultado: ~5min
  265. &amp;quot;Sliding-Average-L3-SL07-OK.shp&amp;quot;  &lt;/p&gt;
  266.  
  267. &lt;p&gt;LEGENDA:&lt;br/&gt;
  268. Verde claro: mata nativa &lt;code&gt;(natural=wood)&lt;/code&gt;&lt;br/&gt;
  269. Verde escuro: mata cultivada &lt;code&gt;(landuse=forest)&lt;/code&gt;&lt;br/&gt;
  270. Branco: null&lt;br/&gt;
  271. &lt;img src="https://i.imgur.com/7XUM6As.gif" alt=""/&gt;&lt;/p&gt;
  272.  
  273. &lt;hr/&gt;
  274.  
  275. &lt;p&gt;&lt;strong&gt;12)ADICIONAR TAGS OSM E LIMPAR:&lt;/strong&gt;  &lt;/p&gt;
  276.  
  277. &lt;p&gt;ELIMINAR DO SHP POLÍGONOS TRUNCADOS DE BORDA DE IMAGEM ou
  278. RESTRINGIR POLÍGONOS A MUNICÍPIO&lt;/p&gt;
  279.  
  280. &lt;p&gt;Salvar como novo layer: &amp;quot;B11+OSM-limpo.shp&amp;quot; &lt;/p&gt;
  281.  
  282. &lt;p&gt;-Selecionar todo polígono que encosta nas bordas do layer e remover manualmente (pode fazer um buffer menor que os limites do layer);&lt;br/&gt;
  283. -Adicionar tags (Table Manager + Field Calculator): landuse=forest; natural=wood;&lt;br/&gt;
  284. -Remover tags sem uso (area; classe).&lt;/p&gt;
  285.  
  286. &lt;p&gt;Salvar como WGS84-EPSG:4326 &lt;/p&gt;
  287.  
  288. &lt;hr/&gt;
  289.  
  290. &lt;p&gt;&lt;strong&gt;13) Opcional: Selecionar por máscara de município&lt;/strong&gt;&lt;br/&gt;
  291. (pois o JOSM fica muito pesado se abrir mais de 10.000 polígonos)&lt;/p&gt;
  292.  
  293. &lt;p&gt;&lt;code&gt;QGIS: Vector / Spatial Query&lt;/code&gt;:
  294. &amp;quot;SHP-origem&amp;quot; + Intersects + &amp;quot;SHP-máscara&amp;quot; - selection / invert / remove&lt;/p&gt;
  295.  
  296. &lt;hr/&gt;
  297.  
  298. &lt;h2&gt;PROCESSOS NO JOSM:&lt;/h2&gt;
  299.  
  300. &lt;p&gt;&lt;strong&gt;1)ABRIR CADA SHP SEPARADAMENTE :&lt;/strong&gt;&lt;/p&gt;
  301.  
  302. &lt;p&gt;-Sem baixar dados do OSM&lt;br/&gt;
  303. -salvar como .osm&lt;/p&gt;
  304.  
  305. &lt;p&gt;Já entra como polígono ou multipol(outer/inner); curvas com ~1nó/10m (mesma resolução das imagens raster)&lt;/p&gt;
  306.  
  307. &lt;p&gt;&lt;strong&gt;Monte Alegre dos Campos:&lt;/strong&gt;&lt;br/&gt;
  308. QGIS: SHP 5,2MB; features/polígonos= 3.519&lt;br/&gt;
  309. JOSM: &amp;quot;B11-MA-4326.osm&amp;quot; : 23,8MB; nodes= 243.070  &lt;/p&gt;
  310.  
  311. &lt;hr/&gt;
  312.  
  313. &lt;p&gt;&lt;strong&gt;2)SIMPLIFICAR:&lt;/strong&gt;&lt;br/&gt;
  314. &lt;code&gt;Select: type:way / Symplify way&lt;/code&gt;&lt;br/&gt;
  315. Resultado: nodes= 136.853&lt;/p&gt;
  316.  
  317. &lt;hr/&gt;
  318.  
  319. &lt;p&gt;&lt;strong&gt;3) VALIDAR SEPARADAMENTE&lt;/strong&gt;&lt;br/&gt;
  320. -Sem baixar dados do OSM&lt;/p&gt;
  321.  
  322. &lt;p&gt;Resultado:&lt;br/&gt;
  323. Errors:   (0)&lt;br/&gt;
  324. Warnings: (28)&lt;br/&gt;
  325.  Self-intersecting polygon ring (3)&lt;br/&gt;
  326.  Self-intersecting ways (25)  &lt;/p&gt;
  327.  
  328. &lt;p&gt;Todos foram casos de auto-intersecção em cruz (quina) - imagem abaixo.&lt;br/&gt;
  329. Talvez possa evitar previamente no QGIS com&lt;br/&gt;
  330. &lt;code&gt;QGIS: GRASS commands -&amp;gt; v.generalize.smooth / Displacement&lt;/code&gt;&lt;br/&gt;
  331. (&lt;a href="https://grass.osgeo.org/grass64/manuals/v.generalize.html" rel="nofollow"&gt;https://grass.osgeo.org/grass64/manuals/v.generalize.html&lt;/a&gt;)&lt;/p&gt;
  332.  
  333. &lt;p&gt;Solução:&lt;br/&gt;
  334. Alteração manual: &amp;quot;unglue(G)&amp;quot; nos nós de cada intersecção; afastar nós e ways&lt;br/&gt;
  335. Cuidar: testar todos os nós da intersecção após o unglue; manter polígonos e multipolígonos fechados ao final&lt;/p&gt;
  336.  
  337. &lt;p&gt;VALIDAR NOVAMENTE:&lt;br/&gt;
  338. Resultado: VALIDAÇÃO COMPLETA (0)&lt;/p&gt;
  339.  
  340. &lt;p&gt;&lt;img src="https://i.imgur.com/k19tibZ.png" alt=""/&gt;&lt;/p&gt;
  341.  
  342. &lt;hr/&gt;
  343.  
  344. &lt;p&gt;&lt;strong&gt;4) TESTES DE CONFLITO COM O EXISTENTE:&lt;/strong&gt;&lt;br/&gt;
  345. Baixar dados do OSM;&lt;/p&gt;
  346.  
  347. &lt;p&gt;VALIDAR:&lt;br/&gt;
  348. Resultado: VALIDAÇÃO COMPLETA (0)&lt;/p&gt;
  349.  
  350. &lt;p&gt;Pronto para aprovação e upload&lt;/p&gt;
  351.  
  352. &lt;hr/&gt;
  353.  
  354. &lt;p&gt;&lt;strong&gt;5) PARA UPLOAD DOS NOVOS DADOS AO OSM:&lt;/strong&gt;  &lt;/p&gt;
  355.  
  356. &lt;p&gt;Proposto salvar em changeset exclusivo, com a nota:&lt;br/&gt;
  357. &lt;em&gt;&amp;quot;adição de polígonos de matas (wood;forest) semi-automatizados com validação manual&amp;quot;&lt;/em&gt;  &lt;/p&gt;
  358.  
  359. &lt;p&gt;O arquivo .osm resultante deste teste para verificação pode ser baixado &lt;a href="https://www.dropbox.com/s/qdzpkfvj7rhfixu/B11-MA-4326-validado-final.rar?dl=0" rel="nofollow"&gt;neste repositório&lt;/a&gt;
  360. (não feito upload ao OSM).&lt;/p&gt;
  361.  
  362. &lt;hr/&gt;
  363.  
  364. &lt;p&gt;Comentários:  &lt;/p&gt;
  365.  
  366. &lt;p&gt;Onde acho que ainda pode melhorar:  &lt;/p&gt;
  367.  
  368. &lt;p&gt;Na filtragem, manter o mesmo buffer de aumento e retorno de limites de áreas vizinhas.&lt;br/&gt;
  369. Ficou um pouco a mais, 10m maior, pra dentro da mata. Por um lado evita invadir outras coisas.&lt;br/&gt;
  370. Mas usando os vetores do OSM para buffer de estradas e waterway, isso já resolve.&lt;/p&gt;
  371.  
  372. &lt;p&gt;A imagem classificada tem 10m/px.&lt;br/&gt;
  373. A área cobre 100.000mx100.000m.&lt;/p&gt;
  374.  
  375. &lt;p&gt;Na minha opinião tem que simplificar e eliminar clusters pequenos, como &amp;lt;40x40m (~16px), pois:&lt;br/&gt;
  376. -o OSM usa simplificação de áreas de terreno, exemplo maior as coast_lines;&lt;br/&gt;
  377. -manter áreas pequenas de &amp;lt;40x40m, tumultua o resultado com objetos pequenos sem alta precisão para a imagem, objetos que não são objetivo do processo.&lt;br/&gt;
  378. O objetivo são as áreas de mata densa e mais homogêneas.&lt;/p&gt;
  379.  
  380. &lt;p&gt;Por favor, fiquem à vontade para tecer comentários se desejarem,
  381. como se vale ou não vale a pena investir neste tipo de processo para desenhar áreas de mata densa,
  382. em regiões de interior, para o OSM.&lt;/p&gt;
  383. </description>
  384.      <dc:creator>smaprs</dc:creator>
  385.      <pubDate>Fri, 17 Aug 2018 01:44:38 +0000</pubDate>
  386.      <comments>https://www.openstreetmap.org/user/smaprs/diary/44705#comments</comments>
  387.      <geo:lat>-28.8407641566948</geo:lat>
  388.      <geo:long>-50.3002595901489</geo:long>
  389.      <georss:point>-28.8407641566948 -50.3002595901489</georss:point>
  390.    </item>
  391.    <item>
  392.      <title> 日本国内での車両別アクセス制限タグを規定するためのドラフト</title>
  393.      <link>https://www.openstreetmap.org/user/hayashi/diary/44704</link>
  394.      <guid>https://www.openstreetmap.org/user/hayashi/diary/44704</guid>
  395.      <description>&lt;h1&gt;osm_jp_access&lt;/h1&gt;
  396.  
  397. &lt;p&gt;OpenStreetMap 日本国内での車両別アクセス制限タグを規定するためのドラフトです。&lt;/p&gt;
  398.  
  399. &lt;p&gt;ドラフト版が完成したら&lt;a href="https://wiki.openstreetmap.org/wiki/Talk:Japan_tagging" rel="nofollow"&gt;OpenStreetMap/wiki - JapanTagging (議論)&lt;/a&gt; のページへ転載します。&lt;/p&gt;
  400.  
  401. &lt;hr/&gt;
  402.  
  403. &lt;p&gt;OpenStreetMap Japan Key:access draft&lt;/p&gt;
  404.  
  405. &lt;p&gt;提案する日本の「車両別アクセスタグ」&lt;/p&gt;
  406.  
  407. &lt;p&gt;&lt;code&gt;
  408. 1. access=*
  409. ┃
  410. ┣━ 2. foot=*   歩行者
  411. ┃
  412. ┗━ 3. vehicle=*    車両
  413. 　　　┃
  414. 　　　┣━ 4. bicycle=*     自転車
  415. 　　　┃
  416. 　　　┣━ 5. carriage=*    軽車両
  417. 　　　┃
  418. 　　　┗━ 6. motor_vehicle 動力付き車両
  419. 　　　　　　┃
  420. 　　　　　　┣━ 7. tram 路面電車
  421. 　　　　　　┃
  422. 　　　　　　┣━ 8. trollerbus 「トロリー」 トロリーバス
  423. 　　　　　　┃
  424. 　　　　　　┗━ 9. motor_car 自動車
  425. 　　　　　　　　　┃
  426. 　　　　　　　　　┣━ 10. hgv_caravan 「けん引」 重被牽引車をけん引しているけん引自動車
  427. 　　　　　　　　　┃
  428. 　　　　　　　　　┣━ 11. disabled 「標章車」 高齢運転者等、標章自動車
  429. 　　　　　　　　　┃
  430. 　　　　　　　　　┣━ 12. agricultural 「小特」 小型特殊自動車
  431. 　　　　　　　　　┃
  432. 　　　　　　　　　┣━ 13. route_bus   「路線バス」　路線定期運行の用に供する自動車
  433. 　　　　　　　　　┃
  434. 　　　　　　　　　┣━ 14. taxi=*      「タクシー」　一般乗用旅客自動車運送事業の用に供する自動車
  435. 　　　　　　　　　┃
  436. 　　　　　　　　　┣━ 15. moped=*,mofa=*,motorcycle=*「二輪」 二輪の自動車及び原動機付自転車
  437. 　　　　　　　　　┃　　┃
  438. 　　　　　　　　　┃　　┣━ 16. motorcycle　「自二輪」　大型自動二輪車、普通自動二輪車
  439. 　　　　　　　　　┃　　┃
  440. 　　　　　　　　　┃　　┗━ 17. moped　「小二輪」　小型二輪車、原動機付自転車
  441. 　　　　　　　　　┃　　　　　┃
  442. 　　　　　　　　　┃　　　　　┗━ 18. mofa　「原付」　原動機付自転車
  443. 　　　　　　　　　┃
  444. 　　　　　　　　　┣━ 19. hgv=*,goods=*  「貨物」　
  445. 　　　　　　　　　┃　　┃
  446. 　　　　　　　　　┃　　┣━ 20. hgv:l     「大貨」　
  447. 　　　　　　　　　┃　　┃
  448. 　　　　　　　　　┃　　┣━ 21. goods:m   「中貨」　
  449. 　　　　　　　　　┃　　┃
  450. 　　　　　　　　　┃　　┣━ 22. goods:ms  「準中貨」　
  451. 　　　　　　　　　┃　　┃
  452. 　　　　　　　　　┃　　┗━ 23. goods:normal 「普貨」　
  453. 　　　　　　　　　┃
  454. 　　　　　　　　　┣━ 24. motor_car:l=*,motor_car:xm=*,motor_car:xl=*　「大型等」
  455. 　　　　　　　　　┃　　┃
  456. 　　　　　　　　　┃　　┣━ 25. motor_car:l 「大型」 大型自動車
  457. 　　　　　　　　　┃　　┃　　┃
  458. 　　　　　　　　　┃　　┃　　┣━ 20. hgv:l  「大貨」　
  459. 　　　　　　　　　┃　　┃　　┃
  460. 　　　　　　　　　┃　　┃　　┗━ 26. psv:l 「大乗」 大型乗用自動車
  461. 　　　　　　　　　┃　　┃　　　　　┃
  462. 　　　　　　　　　┃　　┃　　　　　┣━ 27. tourist_bus 「観光バス」
  463. 　　　　　　　　　┃　　┃　　　　　┃
  464. 　　　　　　　　　┃　　┃　　　　　┣━ 28. bus:l 「大型バス」
  465. 　　　　　　　　　┃　　┃　　　　　┃
  466. 　　　　　　　　　┃　　┃　　　　　┗━ 29. minibus 「マイクロ」
  467. 　　　　　　　　　┃　　┃　　　　　　　　┃
  468. 　　　　　　　　　┃　　┃　　　　　　　　┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車
  469. 　　　　　　　　　┃　　┃
  470. 　　　　　　　　　┃　　┣━ 30. motor_car:m 「中型」 中型自動車
  471. 　　　　　　　　　┃　　┃　　┃
  472. 　　　　　　　　　┃　　┃　　┣━ 21. goods:m  「中貨」　
  473. 　　　　　　　　　┃　　┃　　┃
  474. 　　　　　　　　　┃　　┃　　┗━ 31. psv:m 「中乗」 中型乗用自動車
  475. 　　　　　　　　　┃　　┃
  476. 　　　　　　　　　┃　　┣━ 32.motor_car:xm 「特定中型」 特定中型自動車
  477. 　　　　　　　　　┃　　┃　　┃
  478. 　　　　　　　　　┃　　┃　　┣━ 33.hgv:xm  「特定中貨」　
  479. 　　　　　　　　　┃　　┃　　┃
  480. 　　　　　　　　　┃　　┃　　┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車
  481. 　　　　　　　　　┃　　┃
  482. 　　　　　　　　　┃　　┣━ 35.hgv 「大貨等」　
  483. 　　　　　　　　　┃　　┃　　┃
  484. 　　　　　　　　　┃　　┃　　┣━ 20.hgv:l  「大貨」　
  485. 　　　　　　　　　┃　　┃　　┃
  486. 　　　　　　　　　┃　　┃　　┣━ 34.mortor_car:xl　「大特」 大型特殊自動車
  487. 　　　　　　　　　┃　　┃　　┃
  488. 　　　　　　　　　┃　　┃　　┗━ 33.hgv:xm 「特定中貨」
  489. 　　　　　　　　　┃　　┃
  490. 　　　　　　　　　┃　　┣━ 22.goods:ms  「準中貨」　
  491. 　　　　　　　　　┃　　┃
  492. 　　　　　　　　　┃　　┗━ 23.goods:normal 「普貨」　
  493. 　　　　　　　　　┃
  494. 　　　　　　　　　┣━ 25.motor_car:l 「大型」 大型自動車
  495. 　　　　　　　　　┃　　┃
  496. 　　　　　　　　　┃　　┣━ 20.hgv:l  「大貨」　
  497. 　　　　　　　　　┃　　┃
  498. 　　　　　　　　　┃　　┗━ 26.psv:l 「大乗」 大型乗用自動車
  499. 　　　　　　　　　┃　　　　　┃
  500. 　　　　　　　　　┃　　　　　┣━ 27.tourist_bus 「観光バス」
  501. 　　　　　　　　　┃　　　　　┃
  502. 　　　　　　　　　┃　　　　　┣━ 28.bus:l 「大型バス」
  503. 　　　　　　　　　┃　　　　　┃
  504. 　　　　　　　　　┃　　　　　┗━ 29.minibus 「マイクロ」
  505. 　　　　　　　　　┃　　　　　　　　┃
  506. 　　　　　　　　　┃　　　　　　　　┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車
  507. 　　　　　　　　　┃
  508. 　　　　　　　　　┣━ 30.motor_car:m 「中型」 中型自動車
  509. 　　　　　　　　　┃　　┃
  510. 　　　　　　　　　┃　　┣━ 21.goods:m  「中貨」　
  511. 　　　　　　　　　┃　　┃
  512. 　　　　　　　　　┃　　┗━ 31.psv:m 「中乗」 中型乗用自動車
  513. 　　　　　　　　　┃
  514. 　　　　　　　　　┣━ 32.motor_car:xm 「特定中型」 特定中型自動車
  515. 　　　　　　　　　┃　　┃
  516. 　　　　　　　　　┃　　┣━ 33.hgv:xm  「特定中貨」　
  517. 　　　　　　　　　┃　　┃
  518. 　　　　　　　　　┃　　┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車
  519. 　　　　　　　　　┃
  520. 　　　　　　　　　┣━ 36.motor_car:ms 「準中型」 準中型自動車
  521. 　　　　　　　　　┃　　┃
  522. 　　　　　　　　　┃　　┣━ 22.goods:ms 「準中貨」　
  523. 　　　　　　　　　┃　　┃
  524. 　　　　　　　　　┃　　┗━ 37.psv:ms 「準中乗」 準中型乗用自動車
  525. 　　　　　　　　　┃
  526. 　　　　　　　　　┣━ 38.motor_car:normal 「普通」 普通自動車
  527. 　　　　　　　　　┃　　┃
  528. 　　　　　　　　　┃　　┣━ 23.goods:normal 「普貨」　
  529. 　　　　　　　　　┃　　┃
  530. 　　　　　　　　　┃　　┣━ 39.motor_car:kei 「軽」 軽自動車
  531. 　　　　　　　　　┃　　┃
  532. 　　　　　　　　　┃　　┗━ 40.psv:ms 「普乗」 普通乗用自動車
  533. 　　　　　　　　　┃
  534. 　　　　　　　　　┗━ 41. psv 「乗用」 専ら人を運搬する構造の自動車
  535. 　　　　　　　　　　　　┃
  536. 　　　　　　　　　　　　┣━ 31.psv:m 「中乗」 中型乗用自動車
  537. 　　　　　　　　　　　　┃
  538. 　　　　　　　　　　　　┣━ 42.bus 「バス」
  539. 　　　　　　　　　　　　┃　　┃
  540. 　　　　　　　　　　　　┃　　┗━ 26.psv:l 「大乗」 大型乗用自動車
  541. 　　　　　　　　　　　　┃　　　　　┃
  542. 　　　　　　　　　　　　┃　　　　　┣━ 27.tourist_bus 「観光バス」
  543. 　　　　　　　　　　　　┃　　　　　┃
  544. 　　　　　　　　　　　　┃　　　　　┣━ 28.bus:l 「大型バス」
  545. 　　　　　　　　　　　　┃　　　　　┃
  546. 　　　　　　　　　　　　┃　　　　　┗━ 29.minibus 「マイクロ」
  547. 　　　　　　　　　　　　┃　　　　　　　　┃
  548. 　　　　　　　　　　　　┃　　　　　　　　┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車
  549. 　　　　　　　　　　　　┃
  550. 　　　　　　　　　　　　┣━ 37.psv:ms 「準中乗」 準中型乗用自動車
  551. 　　　　　　　　　　　　┃
  552. 　　　　　　　　　　　　┗━ 40.psv:normal 「普乗」 普通乗用自動車
  553. &lt;/code&gt;&lt;/p&gt;
  554.  
  555. &lt;h2&gt;参考&lt;/h2&gt;
  556.  
  557. &lt;ul&gt;
  558. &lt;li&gt;日本の道路標識に示される車両種別は &lt;a href="http://elaws.e-gov.go.jp/search/elawsSearch/elaws_search/lsg0500/detail?lawId=335M50004002003&amp;openerCode=1" rel="nofollow"&gt;道路標識、区画線及び道路標示に関する命令 （六）車両の種類の略称&lt;/a&gt; に規定されている。
  559. 以下引用&lt;/li&gt;
  560. &lt;/ul&gt;
  561.  
  562. &lt;p&gt;| 略称        | 車両の種類          |
  563. |:-------------:|:--------------- |
  564. | 大型 | 大型自動車 |
  565. | 大型等 | 大型自動車、特定中型自動車及び大型特殊自動車 |
  566. | 中型 | 中型自動車 |
  567. | 特定中型 | 特定中型自動車 |
  568. | 準中型 | 準中型自動車 |
  569. | 普通 | 普通自動車 |
  570. | 大特 | 大型特殊自動車 |
  571. | 自二輪 | 大型自動二輪車及び普通自動二輪車（道路交通法施行規則第二条の表備考の規定により二輪の自動車とみなされ、かつ、同表の大型自動二輪車又は普通自動二輪車に区分される三輪の自動車を含む。） |
  572. | 軽 | 長さが三・四〇メートル以下、幅が一・四八メートル以下、高さが二・〇〇メートル以下の普通自動車（内燃機関を原動機とする自動車にあつては、総排気量が〇・六六〇リットル以下のものに限る。） |
  573. | 小特 | 小型特殊自動車 |
  574. | 原付 | 原動機付自転車 |
  575. | 二輪 | 二輪の自動車及び原動機付自転車 |
  576. | 小二輪 | 道路交通法施行規則第二十四条第一項に規定する小型二輪車及び原動機付自転車 |
  577. | 自転車 | 普通自転車 |
  578. | トロリー | トロリーバス |
  579. | 乗用 | 専ら人を運搬する構造の自動車 |
  580. | 大乗 | 大型乗用自動車 |
  581. | 中乗 | 中型乗用自動車 |
  582. | 特定中乗 | 特定中型乗用自動車 |
  583. | 準中乗 | 準中型乗用自動車 |
  584. | バス | 大型乗用自動車及び特定中型乗用自動車 |
  585. | 大型バス | 乗車定員が三〇人以上の大型乗用自動車 |
  586. | マイクロ | 大型バス以外の大型乗用自動車及び特定中型乗用自動車 |
  587. | 路線バス | 道路運送法（昭和二十六年法律第百八十三号）第九条第一項に規定する一般乗合旅客自動車運送事業者による同法第五条第一項第三号に規定する路線定期運行の用に供する自動車 |
  588. | 普乗 | 普通乗用自動車 |
  589. | タクシー | 道路運送法第三条第一号ハに規定する一般乗用旅客自動車運送事業の用に供する自動車 |
  590. | 貨物 | 大型乗用自動車以外の大型自動車、中型乗用自動車以外の中型自動車、準中型乗用自動車以外の準中型自動車及び普通乗用自動車以外の普通自動車 |
  591. | 大貨 | 大型乗用自動車以外の大型自動車 |
  592. | 大貨等 | 大型乗用自動車以外の大型自動車、特定中型乗用自動車以外の特定中型自動車及び大型特殊自動車 |
  593. | 中貨 | 中型乗用自動車以外の中型自動車 |
  594. | 特定中貨 | 特定中型乗用自動車以外の特定中型自動車 |
  595. | 準中貨 | 準中型乗用自動車以外の準中型自動車 |
  596. | 普貨 | 普通乗用自動車以外の普通自動車 |
  597. | けん引 | 重被牽 引車を牽 引している牽 引自動車 |
  598. | 標章車 | 高齢運転者等標章自動車 |&lt;/p&gt;
  599.  
  600. &lt;h2&gt;継承関係&lt;/h2&gt;
  601.  
  602. &lt;ul&gt;
  603. &lt;li&gt;&lt;a href="http://surveyor.mydns.jp/gitbucket/yuu/osm_jp_access/raw/master/OSMaccess.class.violet.html" rel="nofollow"&gt;車両種別の継承関係(クラス図)&lt;/a&gt;&lt;br/&gt;&lt;/li&gt;
  604. &lt;/ul&gt;
  605.  
  606. &lt;p&gt;&lt;img src="https://github.com/yuuhayashi/osm_jp_access/raw/master/OSMaccess.class.png" alt="車両種別の継承関係"/&gt;&lt;br/&gt;
  607. 上記は、&lt;a href="http://elaws.e-gov.go.jp/search/elawsSearch/elaws_search/lsg0500/detail?lawId=335M50004002003&amp;openerCode=1" rel="nofollow"&gt;車両の種類の略称&lt;/a&gt;の記載をもとに属性の継承関係を表したもの&lt;/p&gt;
  608.  
  609. &lt;h3&gt;継承関係の注意点&lt;/h3&gt;
  610.  
  611. &lt;p&gt;よく誤解されると思われる項目&lt;/p&gt;
  612.  
  613. &lt;ul&gt;
  614. &lt;li&gt;&lt;p&gt;「路線バス」は「バス」を継承していません。つまり、「路線バス」は「バス」ではありません。（「大型」でもない）&lt;br/&gt;
  615. このことにより、「バス」進入禁止どうろでも「路線バス」はその規制を受けません。&lt;/p&gt;&lt;/li&gt;
  616. &lt;li&gt;&lt;p&gt;同様に「タクシー」は「中乗」「普乗」を継承していません。&lt;/p&gt;&lt;/li&gt;
  617. &lt;li&gt;&lt;p&gt;「二輪」と「自二輪」は同一ではありません。タグ的に区別する必要が有ります。&lt;/p&gt;&lt;/li&gt;
  618. &lt;li&gt;&lt;p&gt;「小二輪」は「原付」も含みます。&lt;/p&gt;&lt;/li&gt;
  619. &lt;li&gt;&lt;/li&gt;
  620. &lt;/ul&gt;
  621.  
  622. &lt;h3&gt;マトリックス表&lt;/h3&gt;
  623.  
  624. &lt;p&gt;継承関係をマトリックスで表現したもの&lt;/p&gt;
  625.  
  626. &lt;ul&gt;
  627. &lt;li&gt;[matrix.ods](matrix.ods) [PDF](matrix.pdf)&lt;br/&gt;&lt;/li&gt;
  628. &lt;/ul&gt;
  629.  
  630. &lt;h2&gt;World Wide でのタグ構成&lt;/h2&gt;
  631.  
  632. &lt;ul&gt;
  633. &lt;li&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/JA:Key:access" rel="nofollow"&gt;OpenStreetMap Wiki - JA:Key:access&lt;/a&gt; の&lt;a href="https://wiki.openstreetmap.org/wiki/JA:Key:access#.E9.99.B8.E4.B8.8A.E4.BA.A4.E9.80.9A" rel="nofollow"&gt;6.1 陸上交通&lt;/a&gt;&lt;/li&gt;
  634. &lt;/ul&gt;
  635.  
  636. &lt;p&gt;&lt;code&gt;
  637. access=* （カテゴリ: すべての陸上交通）
  638. ┣━ 車両を使わない移動
  639. ┃　　┣━ foot=* （歩行者）
  640. ┃　　┣━ ski=*
  641. ┃　　┣━ inline_skates=*
  642. ┃　　┣━ ice_skates=*
  643. ┃　　┗━ horse=* （乗馬）
  644. ┗━ vehicle=* （カテゴリ: すべての車両)
  645. 　　　┣━ 動力がない車両
  646. 　　　┃　　┣━ 二輪車
  647.     ┃　　┃　　┗━ bicycle=* （自転車）
  648. 　　　┃　　┗━ 三輪以上
  649.     ┃　　　　　┣━ carriage=* （馬＋馬車）
  650.     ┃　　　　　┗━ trailer=* （トレイラー。他の車両が牽引する必要があり、それにも自身の通行制限があります）
  651.     ┃     　　　　　┗━ caravan=* （[W] キャンピングトレーラー、キャラバンとも呼ばれます）┗
  652. 　　　┗━ motor_vehicle=* （カテゴリ: すべての動力付き車両）
  653.    　　　　　　┣━ 二輪車
  654.          　　 ┃　　　┣━ motorcycle=* （オートバイ。二輪の動力付き車両、自動車専用道路を通行可）
  655.          　　 ┃　　　┣━ moped=* （速度制限付きの原動機付き自転車。例: 多くは50ccエンジンで、最高速度約45km/h）
  656.          　　 ┃　　　┗━ mofa=* (&amp;quot;低速モペット&amp;quot;、通常は最大設計速度25km/h)
  657.    　　　　　　┣━ 三輪以上
  658.          　　 ┃　　　┣━motorcar=* 自動車
  659.          　　 ┃　　　┃　　　┗━ motorhome=* （[W] キャンピングカー）
  660.    　　　　　　┃　　　┣━ tourist_bus=* ツアーバス、観光バス（路線バスでないもの）
  661.    　　　　　　┃　　　┣━ goods=* （小型貨物トラック、最大積載量3.5トン未満）
  662.    　　　　　　┃　　　┣━ hgv=* （大型貨物トラック、最大積載量3.5トン以上）
  663.    　　　　　　┃　　　┣━ agricultural=* （農耕用動力付き車両（トラクターなど）、追加の制限事項があります（速度制限25km/hなど））
  664.    　　　　　　┃　　　┣━ atv=* バギー （幅が50インチ（1.27m）以下に制限されています）提案中です。代わりにmaxwidth=1.27を使用したほうがよいかもしれません。
  665.    　　　　　　┃　　　┗━ snowmobile=*
  666.    　　　　　　┗━ 用途別
  667.          　　 　　　　┣━psv=* （乗合自動車）
  668.          　　 　　　　┣━bus=* （乗合自動車として使われる大型バス）
  669.          　　 　　　　┣━minibus=* （乗合自動車として使われる小型バス）
  670.          　　 　　　　┣━share_taxi=* （要求に応じて輸送する小型バス）
  671. 　          　　 　　　┣━taxi=* （タクシー）
  672.          　　 　　　　┣━hov=* （相乗り自動車、2人以上が同乗した車両（地域によって異なる））
  673.          　　 　　　　┣━car_sharing=* （カーシェアリングサービス）
  674.          　　 　　　　┣━emergency=* （カテゴリー: 緊急車両。救急車、消防車、パトカーなど）
  675.          　　 　　　　┣━hazmat=* （危険物搭載車両）
  676.          　　 　　　　┗━disabled=* （身体障害者標識や、その他の障害者向けの許可。通行制限から除外するために交通標識に使用されます。ただし、駐車に関するものを除く）
  677. &lt;/code&gt;&lt;/p&gt;
  678.  
  679. &lt;h3&gt;World Wide との相違点&lt;/h3&gt;
  680.  
  681. &lt;ul&gt;
  682. &lt;li&gt;&lt;p&gt;日本では「自転車」は「軽車両」に含まれるが、[&lt;code&gt;bicycle&lt;/code&gt;]と[&lt;code&gt;carriage&lt;/code&gt;]は別物&lt;/p&gt;&lt;/li&gt;
  683. &lt;li&gt;&lt;p&gt;日本では「けん引」は「牽引している車両（トレーラーヘッド）」を表すが、OSMでは[trailer]は「引っ張られる台車」を示すため「非動力車両」に分類されている。そのため、提案では「&lt;code&gt;hgv_caravan&lt;/code&gt;」と日本独自タグを新設しています。&lt;br/&gt;
  684. （タグの新設をやめ、「けん引」を「&lt;code&gt;trailer&lt;/code&gt;」としても不都合は生じないと思いますが？）&lt;/p&gt;&lt;/li&gt;
  685. &lt;li&gt;&lt;p&gt;日本の「自動車」と[&lt;code&gt;motor_vehicle&lt;/code&gt;]との違い： 日本では動力付き車両であっても「自動車」とみなさないもの（トロリーバス、路面電車など）が存在するため、提案では「&lt;code&gt;motor_car&lt;/code&gt;（自動車）」と独自タグを新設しています。&lt;/p&gt;&lt;/li&gt;
  686. &lt;li&gt;&lt;p&gt;二輪車について、日本の場合は、&lt;code&gt;motorcycle&lt;/code&gt;,&lt;code&gt;moped&lt;/code&gt;,&lt;code&gt;mofa&lt;/code&gt; に階層関係が存在します。&lt;/p&gt;&lt;/li&gt;
  687. &lt;li&gt;&lt;p&gt;「自二輪」に&lt;code&gt;motorcycle&lt;/code&gt;を割り当てました。「二輪」には独自タグを新設するのを避けるため、&lt;code&gt;motorcycle&lt;/code&gt;,&lt;code&gt;moped&lt;/code&gt;,&lt;code&gt;mofa&lt;/code&gt;を列記することとしましたが、適切なワードを新設したほうが良いのではないでしょうか？&lt;/p&gt;
  688.  
  689. &lt;ul&gt;
  690. &lt;li&gt;その他のタグ列記項目&lt;/li&gt;
  691. &lt;li&gt;「二輪」→ &lt;code&gt;motorcycle&lt;/code&gt;,&lt;code&gt;moped&lt;/code&gt;,&lt;code&gt;mofa&lt;/code&gt;&lt;/li&gt;
  692. &lt;li&gt;「大型等」→  motor_car:l=&lt;em&gt;,motor_car:xm=&lt;/em&gt;,motor_car:xl=*&lt;/li&gt;
  693. &lt;li&gt;「貨物」→  hgv=&lt;em&gt;,goods=&lt;/em&gt;&lt;/li&gt;
  694. &lt;/ul&gt;&lt;/li&gt;
  695. &lt;/ul&gt;
  696.  
  697. &lt;hr/&gt;
  698.  
  699. &lt;p&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/69/CC0_button.svg/88px-CC0_button.svg.png" alt="CC0"/&gt;&lt;/p&gt;
  700. </description>
  701.      <dc:creator>hayashi</dc:creator>
  702.      <pubDate>Thu, 16 Aug 2018 23:39:26 +0000</pubDate>
  703.      <comments>https://www.openstreetmap.org/user/hayashi/diary/44704#comments</comments>
  704.    </item>
  705.    <item>
  706.      <title>Updates in Lima and Arequipa (August 2018)</title>
  707.      <link>https://www.openstreetmap.org/user/Diego%20Sanguinetti/diary/44703</link>
  708.      <guid>https://www.openstreetmap.org/user/Diego%20Sanguinetti/diary/44703</guid>
  709.      <description>&lt;p&gt;Greetings everybod. Just to pass my boring time, I make some minor changes. I hope that ours tourists know how to guide the most of the map points. Without more to say, I highlighted the following:&lt;/p&gt;
  710.  
  711. &lt;ul&gt;
  712. &lt;li&gt;Some streets in Lima and Callao are in English (like &amp;quot;Ayacucho Avenue&amp;quot;)&lt;/li&gt;
  713. &lt;li&gt;More business between Plaza San Miguel and surroundings (30 min to airport)&lt;/li&gt;
  714. &lt;li&gt;Many stores at J. Chávez airport&lt;/li&gt;
  715. &lt;li&gt;Addings in the streets (which were incomplete)&lt;/li&gt;
  716. &lt;li&gt;Design improvements for the Government Palace (3D graphic)&lt;/li&gt;
  717. &lt;li&gt;Pedestrian areas in the Parque de la Reserva&lt;/li&gt;
  718. &lt;li&gt;More buildings and recreational areas (parks) in the district of Rímac&lt;/li&gt;
  719. &lt;li&gt;Design update of the Mounumental Stadium (Estadio Monumental, with boxes, entrance areas and stands)&lt;/li&gt;
  720. &lt;li&gt;Redesign of the Jockey Plaza (with toilets, shops and parking areas)&lt;/li&gt;
  721. &lt;/ul&gt;
  722.  
  723. &lt;p&gt;In addition, in other cities:&lt;/p&gt;
  724.  
  725. &lt;ul&gt;
  726. &lt;li&gt;Restaurants in Arequipa and close places (with addresses and phone numbers)&lt;/li&gt;
  727. &lt;li&gt;Some of the speed limits in Arequipa&amp;#39;s exteriors&lt;/li&gt;
  728. &lt;/ul&gt;
  729.  
  730. &lt;p&gt;PS: In Mission Impossible: Fallout, the map of Paris appears with OpenStreetMap prints. That motivated me to add improvements to those cities in case there was a similar intention.&lt;/p&gt;
  731.  
  732. &lt;p&gt;Translated from &lt;a href="https://www.openstreetmap.org/user/Diego%20Sanguinetti/diary/44626" rel="nofollow"&gt;my spanish post&lt;/a&gt;&lt;/p&gt;
  733. </description>
  734.      <dc:creator>Diego Sanguinetti</dc:creator>
  735.      <pubDate>Thu, 16 Aug 2018 21:59:52 +0000</pubDate>
  736.      <comments>https://www.openstreetmap.org/user/Diego%20Sanguinetti/diary/44703#comments</comments>
  737.    </item>
  738.    <item>
  739.      <title>مرحبا</title>
  740.      <link>https://www.openstreetmap.org/user/jawal222/diary/44702</link>
  741.      <guid>https://www.openstreetmap.org/user/jawal222/diary/44702</guid>
  742.      <description>&lt;p&gt;شكرا لجميع اصدقائي هنا&lt;/p&gt;
  743. </description>
  744.      <dc:creator>jawal222</dc:creator>
  745.      <pubDate>Thu, 16 Aug 2018 14:15:19 +0000</pubDate>
  746.      <comments>https://www.openstreetmap.org/user/jawal222/diary/44702#comments</comments>
  747.    </item>
  748.    <item>
  749.      <title>01-24(24)</title>
  750.      <link>https://www.openstreetmap.org/user/Herman%20Lee/diary/44699</link>
  751.      <guid>https://www.openstreetmap.org/user/Herman%20Lee/diary/44699</guid>
  752.      <description>&lt;p&gt;01-24内容：华信路—华龙路—化纤厂路—花园路片区初步&lt;/p&gt;
  753. </description>
  754.      <dc:creator>Herman Lee</dc:creator>
  755.      <pubDate>Thu, 16 Aug 2018 06:54:13 +0000</pubDate>
  756.      <comments>https://www.openstreetmap.org/user/Herman%20Lee/diary/44699#comments</comments>
  757.      <geo:lat>36.6845958445453</geo:lat>
  758.      <geo:long>117.085225582123</geo:long>
  759.      <georss:point>36.6845958445453 117.085225582123</georss:point>
  760.    </item>
  761.    <item>
  762.      <title>Managed forest polygon not rendering</title>
  763.      <link>https://www.openstreetmap.org/user/jorchr/diary/44698</link>
  764.      <guid>https://www.openstreetmap.org/user/jorchr/diary/44698</guid>
  765.      <description>&lt;p&gt;Several years ago someone added a big area as polygon around Svenljunga with id 616239831, tagged as Managed forest. It was outlined in a crude way, with long distances between nodes. Since then, it has been refined at several occations and a lot of inner relations have been added. I had a go last weekend and added a lot of inner relations where there is openings in the forest.&lt;/p&gt;
  766.  
  767. &lt;p&gt;Today I noticed that the entire area was missing from the rendered map. I can&amp;#39;t find any apparent problem with the area, except that it might be too complex. Can anyone explain why it fails to render?&lt;/p&gt;
  768.  
  769. &lt;p&gt;Actually my feeling is that the polygon should be divided into smaller polygons, but I have no idea how to do it, considering the may inner relations of the area. Each inner relation will need to be added to the correct smaller polygon, of course. I am afraid of loosing many hours of work, if something goes wrong. What can be done?&lt;/p&gt;
  770. </description>
  771.      <dc:creator>jorchr</dc:creator>
  772.      <pubDate>Wed, 15 Aug 2018 20:25:47 +0000</pubDate>
  773.      <comments>https://www.openstreetmap.org/user/jorchr/diary/44698#comments</comments>
  774.      <geo:lat>57.4717092143526</geo:lat>
  775.      <geo:long>13.0867767333984</geo:long>
  776.      <georss:point>57.4717092143526 13.0867767333984</georss:point>
  777.    </item>
  778.    <item>
  779.      <title>Mapeamento do Largo São João e Igreja Matriz de Laranjal Paulista em vídeo</title>
  780.      <link>https://www.openstreetmap.org/user/IgorEliezer/diary/44695</link>
  781.      <guid>https://www.openstreetmap.org/user/IgorEliezer/diary/44695</guid>
  782.      <description>&lt;p&gt;Esta é uma gravação em vídeo do mapeamento do Largo São João e Igreja Matriz de Laranjal Paulista pelo editor JOSM nos últimos meses. Também foi usado o site F4map para gerar o 3D.&lt;/p&gt;
  783.  
  784. &lt;p&gt;Vídeo: &lt;a href="https://www.youtube.com/watch?v=ezw-fb6EPf8" rel="nofollow"&gt;https://www.youtube.com/watch?v=ezw-fb6EPf8&lt;/a&gt; (duração: 5 minutos)&lt;/p&gt;
  785.  
  786. &lt;p&gt;O mapeamento do município de Laranjal Paulista no OpenStreetMap faz parte do meu projeto &lt;em&gt;Atlas de Laranjal Paulista&lt;/em&gt;. Detalhes: &lt;a href="http://www.igoreliezer.com/laranjal/w/index.php?title=Projeto:Mapa_digital" rel="nofollow"&gt;http://www.igoreliezer.com/laranjal/w/index.php?title=Projeto:Mapa_digital&lt;/a&gt;&lt;/p&gt;
  787. </description>
  788.      <dc:creator>IgorEliezer</dc:creator>
  789.      <pubDate>Wed, 15 Aug 2018 16:26:27 +0000</pubDate>
  790.      <comments>https://www.openstreetmap.org/user/IgorEliezer/diary/44695#comments</comments>
  791.      <geo:lat>-23.0502119823624</geo:lat>
  792.      <geo:long>-47.8367874026299</geo:long>
  793.      <georss:point>-23.0502119823624 -47.8367874026299</georss:point>
  794.    </item>
  795.    <item>
  796.      <title>01-23(23)</title>
  797.      <link>https://www.openstreetmap.org/user/Herman%20Lee/diary/44692</link>
  798.      <guid>https://www.openstreetmap.org/user/Herman%20Lee/diary/44692</guid>
  799.      <description>&lt;p&gt;01-23内容：华信路—花园路—七里河路—华龙路片区初步&lt;/p&gt;
  800. </description>
  801.      <dc:creator>Herman Lee</dc:creator>
  802.      <pubDate>Wed, 15 Aug 2018 09:20:13 +0000</pubDate>
  803.      <comments>https://www.openstreetmap.org/user/Herman%20Lee/diary/44692#comments</comments>
  804.      <geo:lat>36.684010780998</geo:lat>
  805.      <geo:long>117.076213359833</geo:long>
  806.      <georss:point>36.684010780998 117.076213359833</georss:point>
  807.    </item>
  808.    <item>
  809.      <title>Thank You for the Award</title>
  810.      <link>https://www.openstreetmap.org/user/tshedy/diary/44689</link>
  811.      <guid>https://www.openstreetmap.org/user/tshedy/diary/44689</guid>
  812.      <description>&lt;p&gt;My sincerest thanks to each and everyone who voted for me in the two categories, that is Greatness in Mapping Award and Improving the Africa Award. I&amp;#39;m honoured and humbled that you believed in me. From the day I noticed that my name has been nominated I felt encouragement to keep doing what I am doing. I will forever be greatful to the &lt;a href="https://twitter.com/openstreetmap?s=08" rel="nofollow"&gt;OpenSteetMap Community&lt;/a&gt;.&lt;/p&gt;
  813.  
  814. &lt;p&gt;I can&amp;#39;t express how thankful I am that I won the &lt;a href="https://wiki.openstreetmap.org/wiki/OpenStreetMap_Awards" rel="nofollow"&gt;Greatness in Mapping Award&lt;/a&gt;. It is an honour to be recognised by such a great community.
  815. &lt;img src="http://i.imgur.com/0tpLyz3.jpg" alt="Greatness in Mapping Award 2018"/&gt;&lt;/p&gt;
  816.  
  817. &lt;p&gt;I also want to thank &lt;a href="https://twitter.com/Fingalcoco?s=08" rel="nofollow"&gt;Fingal County Council&lt;/a&gt; for introducing &lt;a href="https://www.maplesotho.com" rel="nofollow"&gt;#MapLesotho&lt;/a&gt; because that&amp;#39;s how I first knew about OpenSteetMap and it&amp;#39;s usefulness. I am the one who got this honor but the award belongs at least equally to the great teams that I have had the good fortune to work with at the various stages, more especially my mentor &lt;a href="https://twitter.com/CiaranStaunton?s=08" rel="nofollow"&gt;DeBigC&lt;/a&gt; who dedicated his time to guide and advice me. I&amp;#39;m extremely grateful!&lt;/p&gt;
  818. </description>
  819.      <dc:creator>tshedy</dc:creator>
  820.      <pubDate>Wed, 15 Aug 2018 06:07:27 +0000</pubDate>
  821.      <comments>https://www.openstreetmap.org/user/tshedy/diary/44689#comments</comments>
  822.    </item>
  823.    <item>
  824.      <title>Developer wanted for CartoCSS</title>
  825.      <link>https://www.openstreetmap.org/user/kocio/diary/44687</link>
  826.      <guid>https://www.openstreetmap.org/user/kocio/diary/44687</guid>
  827.      <description>&lt;p&gt;I recently got worried about &lt;a href="https://wiki.openstreetmap.org/wiki/CartoCSS" rel="nofollow"&gt;CartoCSS&lt;/a&gt; project, which we use as a Mapnik configuration parser in OSM Carto. There&amp;#39;s only one person available for a long time and I feel this is dangerous, because he has officially stepped down recently and if he looses any interest in it, there would
  828. be not even basic support, like merging code or making the release.&lt;/p&gt;
  829.  
  830. &lt;p&gt;If there&amp;#39;s somebody ready to look at the code (JavaScript) and join the project even to just keep it alive in standby mode, I would be very glad. Here is nebulon42 story and what he expects to &amp;quot;share the keys&amp;quot; (or even pass the baton) in the project:&lt;/p&gt;
  831.  
  832. &lt;p&gt;&lt;a href="https://github.com/mapbox/carto/issues/495#issuecomment-412987738" rel="nofollow"&gt;https://github.com/mapbox/carto/issues/495#issuecomment-412987738&lt;/a&gt;&lt;/p&gt;
  833. </description>
  834.      <dc:creator>kocio</dc:creator>
  835.      <pubDate>Wed, 15 Aug 2018 01:16:18 +0000</pubDate>
  836.      <comments>https://www.openstreetmap.org/user/kocio/diary/44687#comments</comments>
  837.    </item>
  838.    <item>
  839.      <title>#My road trip to Milan</title>
  840.      <link>https://www.openstreetmap.org/user/montshyqn/diary/44686</link>
  841.      <guid>https://www.openstreetmap.org/user/montshyqn/diary/44686</guid>
  842.      <description>&lt;p&gt;The 4th of April 2018 became one of the best days of my life when I received  an email from Dorothea about a scholarship for the State of The Map 2018.The award meant that I would be travelling to Milan to participate in one of the best events in the world of mapping.&lt;/p&gt;
  843.  
  844. &lt;p&gt;The joy and anticipation of boarding a plane to Milan was out of this world but at the same time the anxiety of travelling to a foreign country by myself got to me,however our crowned queen Tshedy gave me a few contacts and i was able to connect with Geoffrey who coincidentally was awarded the same scholarship and would be travelling to Milan around  the same dates as i would be.Needless to say that gave me a bit of comfort and some relieve to have a companion to walk the streets of  Milan with. &lt;/p&gt;
  845.  
  846. &lt;p&gt;My Journey  from Lesotho (the kingdom in the sky) to Milan was amazing and got me thinking of how grateful I am to OpenStreetMap for granting me such an opportunity. I met some scholars namely Arnalie, Geoffrey and Eugene at Dubai airport and we didn&amp;#39;t have a problem finding our way in the big city of Milan and all thanks to &lt;a href="https://en.wikipedia.org/wiki/maps.me" rel="nofollow"&gt;maps.me&lt;/a&gt;.&lt;/p&gt;
  847.  
  848. &lt;p&gt;As we were traveling towards  the hotel,i made note of quiet a few things, to mention but a few - the drainage system was of high standard as any planner would appreciate,there was also no traffic congestion which i thought would the first thing to come across in big cities.
  849. I was impressed  by transport system in Milan where I noticed that public transport and cycling are encouraged and really working.
  850. &lt;img src="https://i.imgur.com/Mu32c3C.jpg" alt="public transport"/&gt;&lt;/p&gt;
  851.  
  852. &lt;p&gt;&lt;img src="https://i.imgur.com/fpaNVUY.jpg" alt="cycling"/&gt;&lt;/p&gt;
  853.  
  854. &lt;p&gt;Later that day we went out and explored the beautiful city where i was fascinated by its architectural landmarks which are highly remarkable and are a must-see &lt;img src="https://i.imgur.com/Fi0Mr9Z.jpg" alt="architectural landmarks"/&gt;.&lt;/p&gt;
  855.  
  856. &lt;p&gt;On the 28th July 2018, from the ebis hotel where the scholars were staying, we took a train to the conference  and it was easy as maps.me was our weapon..we gathered all at Politecnico de Milano, where we registered,got our packages including State of the Map t shirts.
  857. &lt;img src="https://i.imgur.com/LofUMe4.jpg" alt="SOTM 2018 attendees"/&gt;&lt;/p&gt;
  858.  
  859. &lt;p&gt;I signed up for MapBox account with other people where interactions were made and i felt comfortable and felt at home.There was the main conference room De Donato where we gathered in for welcome speech. There were presentations  during the course of the day that really opened my eyes to the real world on how OSM helps in sharing  and promoting maps that are free and editable .the events of that day were so many and interesting  I wanted to attend all the sessions however it was impossible as they were concurrently running. All the talks I attended were so insightful and gave me a reason to aspire more for my country.&lt;/p&gt;
  860.  
  861. &lt;p&gt;Moreover i learned the importance of  OSM data in relation to my day to day job as an Assistant Physical Planner. Networking with other scholars and attendees made me realize that there is a lot to be to done in my community and with all the talks I attended,it came to my attention  that there are youth mappers in other countries and saw an opportunity to advocate and work really hard back at home to make sure that they are there and  sustainable.&lt;/p&gt;
  862.  
  863. &lt;p&gt;On the last day of the conference I had  a 5 minute &lt;a href="https://www.slideshare.net/MontsengMoeti/maplesotho" rel="nofollow"&gt;presentation&lt;/a&gt; about &lt;a href="https://www.maplesotho.com" rel="nofollow"&gt;#MapLesotho&lt;/a&gt; and also attended OSM Africa meeting where the plan for the State of the Map Africa 2019 was discussed and  local chapters for OSM communities across Africa were set up.
  864. as we were moving towards the end of the ceremony speech were made and &lt;a href="http://awards.osmz.ru/" rel="nofollow"&gt;OSM awards&lt;/a&gt;,were handed out where Tshedy won the award for greatness in mapping and i collected the  award on her behalf and what an honor that was. &lt;/p&gt;
  865.  
  866. &lt;p&gt;All thanks to the OSM foundation for granting me such a great opportunity to be part of this important conference,without it I must admit i could not have had the opportunity and exposure to interact with other participants from different countries and gain insight on how MapLesotho community can grow and be sustainable.I would like to extent my gratitude to Dorothea and Rob for their assistance and guidance with all the arrangements needed in order to be part of the State of the Map 2018.&lt;/p&gt;
  867. </description>
  868.      <dc:creator>montshyqn</dc:creator>
  869.      <pubDate>Tue, 14 Aug 2018 22:05:23 +0000</pubDate>
  870.      <comments>https://www.openstreetmap.org/user/montshyqn/diary/44686#comments</comments>
  871.    </item>
  872.    <item>
  873.      <title>Continuity of the work on gender diversity in OSM by Geochicas - SOTM Milan 2018</title>
  874.      <link>https://www.openstreetmap.org/user/mapeadora/diary/44685</link>
  875.      <guid>https://www.openstreetmap.org/user/mapeadora/diary/44685</guid>
  876.      <description>&lt;h2&gt;Geochicas is a group of Spanish-speaking women from OpenStreetMap formed before SOTM-LATAM in Sao Paolo in 2016, around the pre-event discussions about the very low participation of female in proposals.&lt;/h2&gt;
  877.  
  878. &lt;p&gt;Derived from this observation in the Telegram channel of OSM-LATAM, the discussion about the low participation of women in this regional chat as well as in the community in general, in its local, regional and global scales was broadened.&lt;/p&gt;
  879.  
  880. &lt;p&gt;Following this observation, @SeleneYang (Argentina), @Mapanauta and @Mapeadora (Mexico) decided to organize together a series of activities in this SOTM to initiate a collective reflection on gender inequality in this regional community, raise the key issues, develop perennials lines of work.&lt;/p&gt;
  881.  
  882. &lt;p&gt;These lines were:&lt;/p&gt;
  883.  
  884. &lt;ol&gt;
  885. &lt;li&gt;The decision to have in every SOTM-LATAM a space for reflection on gender equity in the form of a talk and a panel with the assembly, looking for continuity&lt;/li&gt;
  886. &lt;li&gt;Form a group of women with a reserved chat called Geochicas, created in the conference with about 30 attendees&lt;/li&gt;
  887. &lt;li&gt;Have a proactive communication effort in the OpenStreetMap LATAM networks to keep the debate on gender equity active&lt;/li&gt;
  888. &lt;li&gt;Promote in the group of women peer-to-peer teaching of technical and theoretical topics&lt;/li&gt;
  889. &lt;li&gt;Promote our continuous participation in data and free technologies events, and a systematic participation in the SOTMs.&lt;/li&gt;
  890. &lt;/ol&gt;
  891.  
  892. &lt;p&gt;From 3 people the group grew during Sao Paolo- SOTM event to 30, and brings together, a year and a half later, around 150 people of diverse origins, from numerous communities, with very broad profiles.&lt;/p&gt;
  893.  
  894. &lt;p&gt;In this line of action, I participated on behalf of Geochicas in the State of the Map 2018 in Milan, with a presentation of the group&amp;#39;s activities and achievements, and presented the results of [our survey on gender representation in OSM](https: //slides.com/geochicasosm/geochicas-sotm2018/).
  895. &lt;img src="https://pbs.twimg.com/media/DjRhNjEW4AAfxJO.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  896.  
  897. &lt;h2&gt;With the intention of contributing to the construction of an OSM agenda on equity, we collaborated with @Heather Leson and Kate Chapman @Wonderchook in this session to brainstorm among the attendees about opening our communities.&lt;/h2&gt;
  898.  
  899. &lt;p&gt;&lt;img src="https://pbs.twimg.com/media/DjRhNjLWsAAIjAj.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  900.  
  901. &lt;p&gt;A mixed assistance and of all countries opined around 3 premises: I will do; We should stop doing; We should start or continue.&lt;/p&gt;
  902.  
  903. &lt;p&gt;&lt;img src="https://pbs.twimg.com/media/DjRlDDMXgAAmqn5.jpg" alt="Alt text"/&gt; &lt;img src="https://pbs.twimg.com/media/DjRlCHtWwAAEGd1.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  904.  
  905. &lt;p&gt;The ideas expressed can be summarized and grouped as follows:&lt;/p&gt;
  906.  
  907. &lt;p&gt;&lt;strong&gt;I will:&lt;/strong&gt;&lt;/p&gt;
  908.  
  909. &lt;ul&gt;
  910. &lt;li&gt;I will give an active female role model in the community of labels&lt;/li&gt;
  911. &lt;li&gt;I will pay attention to the concerns of women in the community&lt;/li&gt;
  912. &lt;li&gt;I will promote the organization of community activities, with attention to a diverse participation, and take care of the conditions of safe access&lt;/li&gt;
  913. &lt;li&gt;I will get involved in local communities and invite women to join&lt;/li&gt;
  914. &lt;li&gt;I will participate more in debates about the community, I will listen and not judge&lt;/li&gt;
  915. &lt;li&gt;I will promote the development of easy-to-use tools to contribute to the map&lt;/li&gt;
  916. &lt;li&gt;I will be alert to violent tones and harassment in communication channels&lt;/li&gt;
  917. &lt;li&gt;I will have more reflection on the subject of privileges and inequity&lt;/li&gt;
  918. &lt;li&gt;I will inquire about COCs and be more sensitive to the issue of respectful treatment&lt;/li&gt;
  919. &lt;li&gt;Consider and take advantage of diverse abilities, in the modes of contribution to OSM&lt;/li&gt;
  920. &lt;/ul&gt;
  921.  
  922. &lt;p&gt;&lt;strong&gt;We should stop:&lt;/strong&gt;&lt;/p&gt;
  923.  
  924. &lt;ul&gt;
  925. &lt;li&gt;To communicate the results with a ranking or competition system. we have to commit ourselves more to inclusion, to value different skills and different centers of interest&lt;/li&gt;
  926. &lt;li&gt;To consider the essence of OSM as a technological project&lt;/li&gt;
  927. &lt;li&gt;To have a prejudice about the motivations for contributing&lt;/li&gt;
  928. &lt;li&gt;To have a limited vision of genders, and expand the focus to all genders&lt;/li&gt;
  929. &lt;li&gt;From supporting the foundation until a complaint system of harassment is complied with&lt;/li&gt;
  930. &lt;li&gt;Stereotyping people, groups, nationalities&lt;/li&gt;
  931. &lt;li&gt;To conceal or tolerate harassment, provocations, abuses and toxic modes, all forms of discrimination&lt;/li&gt;
  932. &lt;li&gt;To pretend that inequality and discrimination in OSM does not exist and is not a problem&lt;/li&gt;
  933. &lt;li&gt;To limit the concept of diversity to gender diversity, expand the focus&lt;/li&gt;
  934. &lt;/ul&gt;
  935.  
  936. &lt;p&gt;&lt;strong&gt;We should start to:&lt;/strong&gt;&lt;/p&gt;
  937.  
  938. &lt;ul&gt;
  939. &lt;li&gt;Listen with empathy and respect disagreements and differences in vision, interest, and values&lt;/li&gt;
  940. &lt;li&gt;Measure changes systematically, periodically, with surveys or other instruments&lt;/li&gt;
  941. &lt;li&gt;Improve the mechanisms for the integration of new people&lt;/li&gt;
  942. &lt;li&gt;Analyze the fine mechanisms of exclusion of marginalized groups towards debates, community, activities and OSM events. Have a constant search for integration&lt;/li&gt;
  943. &lt;li&gt;Have a financing council to know projects and proposals with a need of development, and be able to channel resources towards a greater diversity&lt;/li&gt;
  944. &lt;li&gt;Have a solid strategy of awareness on diversity and equity, diverse interests, with a much broader understanding (gender, LGBTQIA, ages, physical conditions, etc.), address racial discrimination, work on access to marginalized communities&lt;/li&gt;
  945. &lt;li&gt;The board must have a specific work axis on diversity and clear objectives&lt;/li&gt;
  946. &lt;li&gt;Promote our allies&lt;/li&gt;
  947. &lt;li&gt;Have a more motivating perspective and also make visible the efforts and changes&lt;/li&gt;
  948. &lt;li&gt;Collaborate with allies and stakeholders with a clear stance in favor of diversity and equity&lt;/li&gt;
  949. &lt;li&gt;Develop safe spaces for women and other groups&lt;/li&gt;
  950. &lt;li&gt;Build a Code of Conduct, moderations, and an anonymous reporting system, and systems to identify micro-aggressions by the community&lt;/li&gt;
  951. &lt;li&gt;Expand the debate on the topic to share experience and co-create solutions&lt;/li&gt;
  952. &lt;li&gt;Support initiatives focused on women, such as #letgirlsmap, @OsmGirls, @geochicasosm, develop them at all scales&lt;/li&gt;
  953. &lt;li&gt;Have a formal work on the tagging system, with gender vision&lt;/li&gt;
  954. &lt;/ul&gt;
  955.  
  956. &lt;p&gt;(The complete list of comments and ideas written by participants to the brainstorming is transcribed in the mail list &lt;a href="mailto:[email protected]" rel="nofollow"&gt;[email protected]&lt;/a&gt;)&lt;/p&gt;
  957.  
  958. &lt;p&gt;This collective exercise of brainstorming has been invaluable. It allows us to better understand, with an expanded and diverse vision, the dimensions of the diversity and equity problem in OpenStreetMap. &lt;strong&gt;It allows us all to guide our actions in all the sectors where we participate and expresse a voice from the community towards the OSM Foundation to demand a development of the agenda that does belong to everyone.&lt;/strong&gt;
  959. &lt;img src="https://blog.openstreetmap.org/wp-content/uploads/2017/09/hands_with_OSM_sticker_201709-768x364.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  960. </description>
  961.      <dc:creator>mapeadora</dc:creator>
  962.      <pubDate>Tue, 14 Aug 2018 19:01:56 +0000</pubDate>
  963.      <comments>https://www.openstreetmap.org/user/mapeadora/diary/44685#comments</comments>
  964.      <geo:lat>19.4075067670435</geo:lat>
  965.      <geo:long>-99.1394233703613</geo:long>
  966.      <georss:point>19.4075067670435 -99.1394233703613</georss:point>
  967.    </item>
  968.    <item>
  969.      <title>Continuidad del trabajo sobre diversidad de género en OSM por Geochicas - SOTM Milán 2018</title>
  970.      <link>https://www.openstreetmap.org/user/mapeadora/diary/44684</link>
  971.      <guid>https://www.openstreetmap.org/user/mapeadora/diary/44684</guid>
  972.      <description>&lt;h2&gt;Geochicas es un grupo de mujeres de Openstreetmap de habla hispana, formado poco antes del  SOTM-LATAM en Sao Paolo en 2016, alrededor de los debates previos al evento sobre la muy baja participación femenina en las propuestas.&lt;/h2&gt;
  973.  
  974. &lt;p&gt;Derivado de esta observación en el canal de comunicación de OSM-LATAM (chat de Telegram), se amplió la discusión sobre la baja participación de mujeres en este chat regional así como en la comunidad en general, en sus escalas locales, regionales y global. &lt;/p&gt;
  975.  
  976. &lt;p&gt;Siguiendo esta constatación, @SeleneYang (Argentina), @Mapanauta y @Mapeadora (México) decidimos organizar juntas una serie de actividades en este SOTM para iniciar la reflexión colectiva sobre la inequidad de género en esta comunidad regional, plantear los temas claves, desarrollar líneas perenes de trabajo. &lt;/p&gt;
  977.  
  978. &lt;p&gt;Estas líneas fueron: &lt;/p&gt;
  979.  
  980. &lt;ol&gt;
  981. &lt;li&gt;La decisión de tener en todos los SOTM de este continente un espacio de reflexión en forma de charla y panel con la asamblea, sobre la equidad de género, podiendo dar continuidad y medir progresos&lt;/li&gt;
  982. &lt;li&gt;Formar un grupo de mujeres con un chat reservado llamado Geochicas, creado en el mismo momento de la asamblea con unas 30 asistentes&lt;/li&gt;
  983. &lt;li&gt;Tener un esfuerzo de comunicación proactivo en las redes de Openstreetmap LATAM para mantener activo el debate sobre equidad de género&lt;/li&gt;
  984. &lt;li&gt;Promover en el grupo de mujeres la enseñanza de temas técnicos, el debate de nivel teórico&lt;/li&gt;
  985. &lt;li&gt;Promover nuestra participación continua en eventos de datos y tecnologías libres y una participación sistemática en los SOTM.&lt;/li&gt;
  986. &lt;/ol&gt;
  987.  
  988. &lt;p&gt;De 3 personas el grupo creció durante el evento a 30, y reúne, año y medio después, a 150 personas de orígenes diversos, de numerosas comunidades, con perfiles muy amplios.&lt;/p&gt;
  989.  
  990. &lt;p&gt;En esta línea de acción, participé en nombre de Geochicas en el State of the Map 2018 de Milán, con una presentación del grupo de sus actividades y logros, y presenté los resultados de &lt;a href="https://slides.com/geochicasosm/geochicas-sotm2018/" rel="nofollow"&gt;nuestra encuesta sobre representación de género en OSM&lt;/a&gt;.&lt;br/&gt;
  991. &lt;img src="https://pbs.twimg.com/media/DjRhNjEW4AAfxJO.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  992.  
  993. &lt;h2&gt;Con la intención de aportar a la construcción de una agenda en OSM sobre equidad, colaboramos con @Heather Leson y Kate Chapman @Wonderchook en esta sesión para hacer un brainstorming entre los asistentes sobre lo que podemos hacer para abrir nuestras comunidades.&lt;/h2&gt;
  994.  
  995. &lt;p&gt;&lt;img src="https://pbs.twimg.com/media/DjRhNjLWsAAIjAj.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  996.  
  997. &lt;p&gt;Una asistencia mixta y de todos paises opinó alrededor de 3 premisas: Yo haré; Deberíamos dejar de hacer; Deberíamos empezar / continuar de hacer. &lt;/p&gt;
  998.  
  999. &lt;p&gt;&lt;img src="https://pbs.twimg.com/media/DjRlDDMXgAAmqn5.jpg" alt="Alt text"/&gt; &lt;img src="https://pbs.twimg.com/media/DjRlCHtWwAAEGd1.jpg" alt="Alt text"/&gt; &lt;/p&gt;
  1000.  
  1001. &lt;p&gt;Las ideas expresadas se pueden agrupar y resumir así: &lt;/p&gt;
  1002.  
  1003. &lt;p&gt;&lt;strong&gt;Haré:&lt;/strong&gt; &lt;/p&gt;
  1004.  
  1005. &lt;ul&gt;
  1006. &lt;li&gt;Daré un modelo de rol femenino activo en la comunidad&lt;/li&gt;
  1007. &lt;li&gt;Tendré atención a las preocupaciones de las mujeres de la comunidad &lt;/li&gt;
  1008. &lt;li&gt;Impulsaré la organización de actividades comunitarias, con atención a una participación diversa, y cuidando de las condiciones de acceso seguro&lt;/li&gt;
  1009. &lt;li&gt;Me involucraré en comunidades locales e invitaré a mujeres a unirse&lt;/li&gt;
  1010. &lt;li&gt;Participaré más en debates sobre la comunidad, escucharé&lt;/li&gt;
  1011. &lt;li&gt;Impulsaré el desarrollo de herramientas fáciles de uso para contribuir al mapa&lt;/li&gt;
  1012. &lt;li&gt;Seré alerta hacia tonos violentos y acoso en canales de comunicación, tendré mayor reflexión sobre el tema de privilegios y de inequidad&lt;/li&gt;
  1013. &lt;li&gt;Indagaré sobre COCs y seré más sensible a la cuestión del trato respetuoso&lt;/li&gt;
  1014. &lt;li&gt;Considerar y aprovechar abilidades diversas, en los modos de contribución a OSM&lt;/li&gt;
  1015. &lt;/ul&gt;
  1016.  
  1017. &lt;p&gt;&lt;strong&gt;Deberíamos dejar de:&lt;/strong&gt;&lt;/p&gt;
  1018.  
  1019. &lt;ul&gt;
  1020. &lt;li&gt;Comunicar los resultados con un sistema de rankings, comprometernos más con la inclusión, valorizar habilidades distintas e centros de interes distintos&lt;/li&gt;
  1021. &lt;li&gt;Considerar la esencia de OSM como un proyecto tecnológico&lt;br/&gt;&lt;/li&gt;
  1022. &lt;li&gt;Tener prejuicio sobre las motivaciones por contribuir&lt;/li&gt;
  1023. &lt;li&gt;Tener una visión limitada de los géneros, y ampliar el foco a todos los géneros&lt;/li&gt;
  1024. &lt;li&gt;Apoyar a la fondación hasta que se cumpla con un sistema de denuncia del acoso&lt;/li&gt;
  1025. &lt;li&gt;Estereotipar personas, grupos, nacionalidades&lt;/li&gt;
  1026. &lt;li&gt;Encubrir o tolerar el acoso, las provocaciones, abusos y modos tóxicos, todas formas de discriminación&lt;/li&gt;
  1027. &lt;li&gt;Pretender que la inequidad y discriminación en OSM no existe y no es un problema &lt;/li&gt;
  1028. &lt;li&gt;Limitar el concepto de diversidad a la diversidad de género, ampliar el foco&lt;/li&gt;
  1029. &lt;/ul&gt;
  1030.  
  1031. &lt;p&gt;&lt;strong&gt;Deberíamos empezar a:&lt;/strong&gt;&lt;/p&gt;
  1032.  
  1033. &lt;ul&gt;
  1034. &lt;li&gt;Escuchar con empatía y respetar los desacuerdos y las diferencias de visión, interés y valores&lt;/li&gt;
  1035. &lt;li&gt;Medir cambios sistematicamente, periodicamente, con encuestas&lt;/li&gt;
  1036. &lt;li&gt;Mejorar los mecanismos de integración de nuevas personas&lt;/li&gt;
  1037. &lt;li&gt;Analizar los mecanismos finos de exclusión de grupos marginados hacia los debates, la comunidad, las actividades y los eventos de OSM. Tener una busqueda constante de integración &lt;/li&gt;
  1038. &lt;li&gt;Tener un consejo de financiamiento para conocer proyectos y propuestas con necesidad de desarrollo y poder canalizar recursos hacia una mayor diversidad&lt;/li&gt;
  1039. &lt;li&gt;Tener una estrategia sólida de concientización sobre diversidad y equidad, intereses diversos, con un entendimiento mucho más amplio (géneroS, LGBTQIA, edades, condiciones físicas, etc.), abordar la discriminación racial, trabajar en el acceso hacia comunidades marginadas&lt;/li&gt;
  1040. &lt;li&gt;El board debe de tener un eje de trabajo concreto sobre diversidad y objetivos claros&lt;/li&gt;
  1041. &lt;li&gt;Promover nuestros aliados&lt;/li&gt;
  1042. &lt;li&gt;Tener una perspectiva más motivadora y visibilizar también los esfuerzos y los cambios&lt;/li&gt;
  1043. &lt;li&gt;Collaborar con aliados y grupos de interés con una postura clara a favor de la diversidad y equidad&lt;/li&gt;
  1044. &lt;li&gt;Desarrollar espacios seguros para mujeres y otros grupos &lt;/li&gt;
  1045. &lt;li&gt;Construir un Código de Conducta, moderaciones, y un sistema de denuncia anónimo, sistemas de identificación de microagresiones por la comunidad&lt;/li&gt;
  1046. &lt;li&gt;Ampliar el debate sobre el tema para compartir experiencia y co-crear soluciones&lt;/li&gt;
  1047. &lt;li&gt;Apoyar las iniciativas enfocadas a mujeres, como #letgirlsmap, @OsmGirls, @geochicasosm, desarrollarlas en todas las escalas&lt;/li&gt;
  1048. &lt;li&gt;Tener un trabajo formal sobre el sistema de etiquetas con visión de género&lt;/li&gt;
  1049. &lt;/ul&gt;
  1050.  
  1051. &lt;p&gt;(La lista completa de comentarios e ideas escritas por los participantes al taller están retranscritas en la lista de mail &lt;a href="mailto:[email protected]" rel="nofollow"&gt;[email protected]&lt;/a&gt;).&lt;/p&gt;
  1052.  
  1053. &lt;p&gt;Este ejercicio colectivo de propuestas ha sido valiosísimo. Nos permite entender mejor, con una visión ampliada y diversa, las dimensiones del problema de diversidad y equidad en OpenStreetMap. &lt;strong&gt;Nos permite a todos orientar nuestras acciones en todos los sectores donde participamos, y expresa una voz de la comunidad hacia la OSM Fundación para exigir un desarrollo de la agenda que, subrayamos, es de todos.&lt;/strong&gt;
  1054. &lt;img src="https://blog.openstreetmap.org/wp-content/uploads/2017/09/hands_with_OSM_sticker_201709-768x364.jpg" alt="Alt text"/&gt;&lt;/p&gt;
  1055. </description>
  1056.      <dc:creator>mapeadora</dc:creator>
  1057.      <pubDate>Tue, 14 Aug 2018 18:11:35 +0000</pubDate>
  1058.      <comments>https://www.openstreetmap.org/user/mapeadora/diary/44684#comments</comments>
  1059.      <geo:lat>19.4073448595346</geo:lat>
  1060.      <geo:long>-99.1378784179688</geo:long>
  1061.      <georss:point>19.4073448595346 -99.1378784179688</georss:point>
  1062.    </item>
  1063.    <item>
  1064.      <title>Ponte Morandi: why fiddling with the map?</title>
  1065.      <link>https://www.openstreetmap.org/user/sabas88/diary/44683</link>
  1066.      <guid>https://www.openstreetmap.org/user/sabas88/diary/44683</guid>
  1067.      <description>&lt;p&gt;I counted at least 50 changesets in or around the area of the collapsed brigde in my home town, following I assume some news in the mainstream media.
  1068. I wonder why there&amp;#39;s need to edit further the same object to add little value to the map.
  1069. People in Genoa already made the necessary changes after watching local news.
  1070. I deleted the bridge because it will be quite surely removed altogether, what is the point of showing a &amp;quot;collapsed&amp;quot; bridge when the actual bridge segment is in ruins in the waterway below?&lt;/p&gt;
  1071.  
  1072. &lt;p&gt;When the news will fade, we local mappers will once more take care of the local situation.
  1073. (which will reflect on the traffic of North-West Italy, but that&amp;#39;s another problem).&lt;/p&gt;
  1074. </description>
  1075.      <dc:creator>sabas88</dc:creator>
  1076.      <pubDate>Tue, 14 Aug 2018 15:55:58 +0000</pubDate>
  1077.      <comments>https://www.openstreetmap.org/user/sabas88/diary/44683#comments</comments>
  1078.      <geo:lat>44.4258731249275</geo:lat>
  1079.      <geo:long>8.8884973526001</geo:long>
  1080.      <georss:point>44.4258731249275 8.8884973526001</georss:point>
  1081.    </item>
  1082.    <item>
  1083.      <title>La verifica dei toponimi di Vittorio Emanuele III In Calabria</title>
  1084.      <link>https://www.openstreetmap.org/user/bubix/diary/44682</link>
  1085.      <guid>https://www.openstreetmap.org/user/bubix/diary/44682</guid>
  1086.      <description>&lt;p&gt;Nell&amp;#39;ambito del progetto &lt;a href="https://wiki.openstreetmap.org/wiki/Vittorio_Emanuele_III" rel="nofollow"&gt;#cittasenzamemoria&lt;/a&gt; è stata aggiornata la verifica dei toponimi dedicati a Vittorio Emanuele III in Calabria.&lt;/p&gt;
  1087.  
  1088. &lt;p&gt;&lt;img src="https://raw.githubusercontent.com/bubici/immagini/master/calabria%20veiii.jpg" alt="Calabria"/&gt;&lt;/p&gt;
  1089.  
  1090. &lt;p&gt;I dati provengono dalla mappa di &lt;a href="https://www.openstreetmap.org" rel="nofollow"&gt;OpenStreetMap&lt;/a&gt; finalizzata a creare una cartografia a contenuto libero del mondo. Le informazioni della mappa sono liberamente accessibili su licenza &lt;a href="http://www.openstreetmap.org/copyright" rel="nofollow"&gt;ODbL&lt;/a&gt; ed aggiornate ogni giorno. Per facilitare la consultazione i toponimi sono anche consultabili sulla &lt;a href="https://umap.geonue.com/m/782/" rel="nofollow"&gt;mappa on line dedicata&lt;/a&gt;. In totale sono stati individuati 74 odonimi qui di seguito riportati:&lt;/p&gt;
  1091.  
  1092. &lt;p&gt;id       toponimo                         Comune    &lt;/p&gt;
  1093.  
  1094. &lt;p&gt;1   Corso Vittorio Emanuele III     Acquaformosa&lt;br/&gt;
  1095. 2   Via Vittorio Emanuele III       Acquappesa&lt;br/&gt;
  1096. 3   Piazza Vittorio Emanuele III    Acri&lt;br/&gt;
  1097. 4   Corso Vittorio Emanuele III     Albidona&lt;br/&gt;
  1098. 5   Via Vittorio Emanuele III       Alessandria del Carretto&lt;br/&gt;
  1099. 6   Via Vittorio Emanuele III       Cerchiara di Calabria&lt;br/&gt;
  1100. 7   Via Vittorio Emanuele III       Corigliano Calabria&lt;br/&gt;
  1101. 8   Via Vittorio Emanuele III       Francavilla Marittima&lt;br/&gt;
  1102. 9   Via Vittorio Emanuele III       Lungro&lt;br/&gt;
  1103. 10  Piazza Vittorio Emanuele III    Nocara&lt;br/&gt;
  1104. 11  Via Vittorio Emanuele III       Panettieri&lt;br/&gt;
  1105. 12  Corso Vittorio Emanuele III     Pedivigliano&lt;br/&gt;
  1106. 13  Via Vittorio Emanuele III       Rende&lt;br/&gt;
  1107. 14  Via Vittorio Emanuele III       San Lorenzo Bellizzi&lt;br/&gt;
  1108. 15  Via Vittorio Emanuele III       San Marco Argentano&lt;br/&gt;
  1109. 16  Via Vittorio Emanuele III       San Pietro in Guarano&lt;br/&gt;
  1110. 17  Via Vittorio Emanuele III       San Vincenzo La Costa&lt;br/&gt;
  1111. 18  Corso Vittorio Emanuele III     Trebisacce&lt;br/&gt;
  1112. 19  Corso Vittorio Emanuele III     Argusto&lt;br/&gt;
  1113. 20  Via Vittorio Emanuele III       Badolato&lt;br/&gt;
  1114. 21  Via Vittorio Emanuele III       Carlopoli&lt;br/&gt;
  1115. 22  Via Vittorio Emanuele III di Castagna   Carlopoli&lt;br/&gt;
  1116. 23  Salita Vittorio Emanuele III    Cropani&lt;br/&gt;
  1117. 24  Corso Vittorio Emanuele III     Gimigliano&lt;br/&gt;
  1118. 25  Via Vittorio Emanuele III       Magisano&lt;br/&gt;
  1119. 26  Via Vittorio Emanuele III in San Pietro Magisano&lt;br/&gt;
  1120. 27  Piazza Vittorio Emanuele III    Maida&lt;br/&gt;
  1121. 28  Via Vittorio Emanuele III       Olivadi&lt;br/&gt;
  1122. 29  Via Vittorio Emanuele III       Palermiti&lt;br/&gt;
  1123. 30  Piazza Vittorio Emanuele III    Palermiti&lt;br/&gt;
  1124. 31  Corso Vittorio Emanuele III     Petrizzi&lt;br/&gt;
  1125. 32  Salita Vittorio Emanuele III    Petronà&lt;br/&gt;
  1126. 33  Corso Vittorio Emanuele III     San Floro&lt;br/&gt;
  1127. 34  Via Vittorio Emanuele III       Sant&amp;#39; Andrea Apostolo dello Ionio&lt;br/&gt;
  1128. 35  Piazza Vittorio Emanuele III    Serrastretta&lt;br/&gt;
  1129. 36  Via Vittorio Emanuele III       Settingiano&lt;br/&gt;
  1130. 37  Via Vittorio Emanuele III       Torre di Ruggiero&lt;br/&gt;
  1131. 38  Via Vittorio Emanuele III       Antonimina&lt;br/&gt;
  1132. 39  Via Vittorio Emanuele III       Bovalino&lt;br/&gt;
  1133. 40  Via Vittorio Emanuele III       Calanna&lt;br/&gt;
  1134. 41  Piazza Vittorio Emanuele III    Campo Calabro&lt;br/&gt;
  1135. 42  Via Vittorio Emanuele III       Cardeto&lt;br/&gt;
  1136. 43  Via Vittorio Emanuele III       Ciminà&lt;br/&gt;
  1137. 44  Via Vittorio Emanuele III       Cittanova&lt;br/&gt;
  1138. 45  Piazza Vittorio Emanuele III    Cosoleto&lt;br/&gt;
  1139. 46  Via Vittorio Emanuele III       Gioia Tauro&lt;br/&gt;
  1140. 47  Via Vittorio Emanuele III       Gioiosa Ionica&lt;br/&gt;
  1141. 48  Via Vittorio Emanuele III       Grotteria&lt;br/&gt;
  1142. 49  Via Vittorio Emanuele III       Melicuccà&lt;br/&gt;
  1143. 50  Corso Vittorio Emanuele III     Reggio Calabria&lt;br/&gt;
  1144. 51  Via Vittorio Emanuele III       Rizziconi&lt;br/&gt;
  1145. 52  Via Vittorio Emanuele III       San Lorenzo&lt;br/&gt;
  1146. 53  Via Vittorio Emanuele III       San Procopio&lt;br/&gt;
  1147. 54  Via Vittorio Emanuele III       Sant&amp;#39;Eufemia d&amp;#39;Aspromonte&lt;br/&gt;
  1148. 55  Via Vittorio Emanuele III       Cotronei&lt;br/&gt;
  1149. 56  Corso Vittorio Emanuele III     Isola di Capo Rizzuto&lt;br/&gt;
  1150. 57  Via Vittorio Emanuele III       Savelli&lt;br/&gt;
  1151. 58  Corso Vittorio Emanuele III     Arena&lt;br/&gt;
  1152. 59  Piazza Vittorio Emanuele III    Dasà&lt;br/&gt;
  1153. 60  Corso Vittorio Emanuele III     Dinami&lt;br/&gt;
  1154. 61  Corso Vittorio Emanuele III     Fabrizia&lt;br/&gt;
  1155. 62  Via Vittorio Emanuele III       Francica&lt;br/&gt;
  1156. 63  Via Vittorio Emanuele III       Mileto&lt;br/&gt;
  1157. 64  Via Vittorio Emanuele III       Nardidipace&lt;br/&gt;
  1158. 65  Corso Vittorio Emanuele III     Parghelia&lt;br/&gt;
  1159. 66  Via Vittorio Emanuele III       San Calogero&lt;br/&gt;
  1160. 67  Via Vittorio Emanuele III       Sorianello&lt;br/&gt;
  1161. 68  Via Vittorio Emanuele III       Villapiana&lt;br/&gt;
  1162. 69  Via Vittorio Emanuele III       Serra San Bruno&lt;br/&gt;
  1163. 70  Corso Vittorio Emanuele III     Vibo Valentia&lt;br/&gt;
  1164. 71  Via Vittorio Emanuele III       Monasterace&lt;br/&gt;
  1165. 72  Corso Vittorio Emanuele III     Mongiana&lt;br/&gt;
  1166. 73  Piazza Vittorio Emanuele III    Molochio&lt;br/&gt;
  1167. 74  Via Vittorio Emanuele III       Brancaleone                                                     &lt;/p&gt;
  1168.  
  1169. &lt;p&gt;Nel dettaglio i singoli odonimi sono anche visualizzabili sulla pagina wiki del progetto #cittasenzamemoria relativa alla &lt;a href="https://wiki.openstreetmap.org/wiki/Vittorio_Emanuele_III#La_verifica_degli_odonimi_in_Calabria" rel="nofollow"&gt;Calabria&lt;/a&gt;.&lt;/p&gt;
  1170.  
  1171. &lt;ul&gt;
  1172. &lt;li&gt;Metodo di lavoro&lt;/li&gt;
  1173. &lt;/ul&gt;
  1174.  
  1175. &lt;p&gt;Il metodo di lavoro è consistito nel verificare i dati provenienti &lt;a href="http://www.istat.it/storage/basi_territoriali_2013/dati_toponomastici/dati_sc_provvisori.zip" rel="nofollow"&gt;Censimento ISTAT 2011&lt;/a&gt;. Se la via è presente nel data base ISTAT attraverso fonti ancillari si è determinato che le targhe siano effettivamente intestate a Vittorio Emanuele III e non hai suoi due omonimi predecessori (Vittorio Emaneuele I e II). Se la verifica è positiva si è controllato la presenza della strada su OpenStreetMap. Il controllo finale si svolto mediante il bot &lt;a href="https://web.telegram.org/#/[email protected]_bot" rel="nofollow"&gt;Italy Names per Telegram&lt;/a&gt;  con lo scopo di visualizzare gli odonimi italiani suddivisi per comune. Il risultato prodotto è stato che la maggior parte dei 74 odonimi controllati erano per lo più già presenti e dunque accertati dalla &lt;a href="https://wiki.openstreetmap.org/wiki/Calabria" rel="nofollow"&gt;locale comunità di utenti OpenStreetmap&lt;/a&gt;. La Calabria è risultata la maggiore regione italiana con ben 74 toponimi dedicati a Vittorio Emanuele III.
  1176. I toponimi individuati sono in linea con i risultati del referendum del 2 giugno 1946 nel quale i favorevoli alla Repubblica persero con una percentuale del 60,3% nella circoscrizione di Catanzaro. &lt;/p&gt;
  1177.  
  1178. &lt;ul&gt;
  1179. &lt;li&gt;Considerazioni finali&lt;/li&gt;
  1180. &lt;/ul&gt;
  1181.  
  1182. &lt;p&gt;Il lavoro svolto sulla Calabria dimostra che la mappa di OpenStreetMap può essere considerata una valida base dati affidabile e certificata dalla stessa comunità di mappatori volontari che con il loro certosino lavoro, verificano, controllano e aggiornano i dati presenti sulle mappe.&lt;/p&gt;
  1183.  
  1184. &lt;p&gt;Bubix&lt;/p&gt;
  1185. </description>
  1186.      <dc:creator>bubix</dc:creator>
  1187.      <pubDate>Tue, 14 Aug 2018 14:52:53 +0000</pubDate>
  1188.      <comments>https://www.openstreetmap.org/user/bubix/diary/44682#comments</comments>
  1189.    </item>
  1190.    <item>
  1191.      <title>Information on Spam</title>
  1192.      <link>https://www.openstreetmap.org/user/alexkemp/diary/44681</link>
  1193.      <guid>https://www.openstreetmap.org/user/alexkemp/diary/44681</guid>
  1194.      <description>&lt;p&gt;Registered, logged-in users recently got an additional facility for every Diary posted within this site: a report button. At this current moment (Tuesday 14 August 2018) these are the option buttons available after pressing that button (choose just one):–&lt;/p&gt;
  1195.  
  1196. &lt;ul&gt;
  1197. &lt;li&gt;This diary entry is/contains spam&lt;br/&gt;&lt;/li&gt;
  1198. &lt;li&gt;This diary entry is obscene/offensive&lt;br/&gt;&lt;/li&gt;
  1199. &lt;li&gt;This diary entry contains a threat&lt;br/&gt;&lt;/li&gt;
  1200. &lt;li&gt;Other&lt;/li&gt;
  1201. &lt;/ul&gt;
  1202.  
  1203. &lt;p&gt;This diary post is about the first option (non-email &lt;a href="https://en.wikipedia.org/wiki/Spamming" rel="nofollow"&gt;SPAM&lt;/a&gt;) (&lt;a href="https://youtu.be/anwy2MPT5RE" rel="nofollow"&gt;you-tube&lt;/a&gt; (baked-beans are off)). OSM got going in 2004 and, from my POV, it is astonishing that it has taken 14 years to put a &lt;em&gt;Report&lt;/em&gt; option in place (I joined &lt;a href="https://www.stopforumspam.com/" rel="nofollow"&gt;StopForumSpam&lt;/a&gt; in 2009 and am a Mod on that site, so you will have to accept a strong anti-spam obsession in this post).&lt;/p&gt;
  1204.  
  1205. &lt;h2&gt;You are never alone with an IP&lt;/h2&gt;
  1206.  
  1207. &lt;p&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/en/6/65/Strand_Tipped_Cigarettes_%28Full_Flavour%29.jpg" alt="pack of Strand cigarettes"/&gt;&lt;br/&gt;
  1208. (The subhead is inspired by the advertising for &lt;a href="https://en.wikipedia.org/wiki/Strand_(cigarette)" rel="nofollow"&gt;Strand cigarettes&lt;/a&gt;)&lt;/p&gt;
  1209.  
  1210. &lt;p&gt;Telegrams became ubiquitous in the 19th Century &amp;amp; Western Union allowed multiple destinations. You should not be surprised to discover, therefore, that the first mass unsolicited commercial telegram was recorded in May 1864 (to British politicians from a dentist). However, telegrams were NOT free.&lt;/p&gt;
  1211.  
  1212. &lt;p&gt;Our current problems with SPAM were probably initiated by the success of the &lt;a href="https://en.wikipedia.org/wiki/Netscape_Navigator" rel="nofollow"&gt;Netscape Navigator browser&lt;/a&gt;, though that statement will take a few twists &amp;amp; turns to justify. Netscape (released 1994) was written by some of the same folks that had written &lt;a href="https://en.wikipedia.org/wiki/Mosaic_(web_browser)" rel="nofollow"&gt;Mosaic&lt;/a&gt; (released 1993) and initially was available for free, though that rapidly changed. Even though Mosaic development was funded by the USA government (and is the reason that Al Gore says he started the Internet), and was free in certain circumstances, it was a commercial product. In fact, a company called Spyglass licensed Mosaic for their own browser &amp;amp; Microsoft (M$) licensed Spyglass Mosaic in 1995 to create Internet Explorer. We now need just one more player to be able to try to justify the statement at the top of this paragraph.&lt;/p&gt;
  1213.  
  1214. &lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee" rel="nofollow"&gt;Sir Tim Berners-Lee&lt;/a&gt; wrote the code for all the initial components for a fully-functioning World Wide Web (WWW) in 1989 and gave it to the world &lt;em&gt;for free&lt;/em&gt; (no copyright nor proprietary constraints of any kind). Perfectly astonishing. It was rapidly taken up and implemented worldwide. However, it was text-only. And — just like the astonishment for 1930s audiences that watched a &lt;a href="https://youtu.be/F4eQmTizTSo" rel="nofollow"&gt;sepia Dorothy open the door&lt;/a&gt; and step into a &lt;a href="https://en.wikipedia.org/wiki/The_Wizard_of_Oz_(1939_film)" rel="nofollow"&gt;Technicolour Wizard of Oz&lt;/a&gt; world — moving from text-only browsers to graphical browsers like Mosaic or Netscape was utterly compelling.&lt;/p&gt;
  1215.  
  1216. &lt;p&gt;&lt;img src="https://i.ytimg.com/vi/F4eQmTizTSo/hqdefault.jpg" alt="sepia dorothy"/&gt;&lt;/p&gt;
  1217.  
  1218. &lt;h2&gt;You Cannot Beat Free&lt;/h2&gt;
  1219.  
  1220. &lt;p&gt;Netscape, released in 1994, rode the tailcoats of M$’s Windows 95 to commercial success. Folks in those days were prepared to pay for programs. Netscape flirted with free with v1.0 but changed to commercial with the 1995 v1.1. M$ quickly spotted the commercial possibilities. Bill Gates switched his stance, and placed M$ Internet Explorer (MSIE) into the kernel of Windows 98 &amp;amp; later (it is still there today, in spite of the anti-trust actions taken by the USA government &amp;amp; EU against M$) &amp;amp; promoted MSIE hard. They were successful, and Netscape is now dead, although it&amp;#39;s code was made open-source &amp;amp; became Mozilla Firefox.&lt;/p&gt;
  1221.  
  1222. &lt;p&gt;So, we now have the dawn of a new millennium, the WWW is spreading and, if you know someone&amp;#39;s IP, then you can hack them with ease (the Windows NetBEUI local-network protocol had zero protections against hacking &amp;amp; gave root access to the disk from remote locations; it was a nightmare). Likewise, &lt;em&gt;Bulletin Boards&lt;/em&gt; have become &lt;em&gt;Internet Forums&lt;/em&gt; &amp;amp; hackers have discovered the commercial possibilities of SPAM. And remember, whilst email spam was also going wild at this time, we are talking about forum &amp;amp; blog-post spam at this moment. You know, like these Diary posts.&lt;/p&gt;
  1223.  
  1224. &lt;h2&gt;So What is Spam?&lt;/h2&gt;
  1225.  
  1226. &lt;p&gt;I&amp;#39;ve already talked about SPAM&amp;#39;s mother (the WWW &amp;amp; culture of ‘free’) but &lt;a href="https://en.wikipedia.org/wiki/We_Need_to_Talk_About_Kevin" rel="nofollow"&gt;We Need to Talk About  Google&lt;/a&gt; (the father) to get to grips with what on earth is going on.&lt;/p&gt;
  1227.  
  1228. &lt;p&gt;Google is the 5,000 lb gorilla in the room in the early part of this millennium. As a search engine, Google ranks sites not so much by what the site itself is like, but rather by how many &lt;em&gt;other&lt;/em&gt; sites link to it. The more that other sites point to a specific site, the more that specific site will rise within the Search Engine Results Pages (SERPs). Entrepreneurs quickly realised this, and also realised that there were a massive number of forums &amp;amp; blogs that would allow them to place posts with links. And lo! Spamming was born!&lt;/p&gt;
  1229.  
  1230. &lt;p&gt;There are two types of spammer:–&lt;/p&gt;
  1231.  
  1232. &lt;ol&gt;
  1233. &lt;li&gt;Stupid Spammers&lt;/li&gt;
  1234. &lt;li&gt;Every Other Spammer&lt;/li&gt;
  1235. &lt;/ol&gt;
  1236.  
  1237. &lt;h2&gt;Stupid Spammers&lt;/h2&gt;
  1238.  
  1239. &lt;p&gt;Like most of the human race, stupid spammers do not bother to think for themselves. Somewhere, at some point, they have read or been told that it is a &lt;em&gt;Good Idea&lt;/em&gt; to promote their business/site/hobby/blog by putting links to it into random forums,&lt;/p&gt;
  1240.  
  1241. &lt;p&gt;There used to be lots &amp;amp; lots of forums or blogs that allowed anonymous logins, but not many today. So, they signup to OSM &amp;amp; make a Diary post. They are far too busy spamming to write anything that is of value to OSM users, and sometimes they are so stupid that they even forget to post a link. Or, indeed, anything much at all.&lt;/p&gt;
  1242.  
  1243. &lt;h2&gt;Every Other Spammer&lt;/h2&gt;
  1244.  
  1245. &lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Pareto_principle" rel="nofollow"&gt;Just like all things&lt;/a&gt;, 80% of the spammers fit into the other category, and even this one is a sliding scale of dumbness. Nevertheless, here are some of the ways spammers demonstrate glimmers of above-average intelligence:–&lt;/p&gt;
  1246.  
  1247. &lt;p&gt;&lt;em&gt;a. Using the Profile to Spam&lt;/em&gt;&lt;br/&gt;
  1248. The Diary post and/or comment is only to get the Search Engine to visit the Profile page. As with all spammers, it shows:–&lt;br/&gt;
  1249.  &lt;br/&gt;
  1250. Joined: Today&lt;br/&gt;
  1251. Edits: 0&lt;br/&gt;
  1252. Traces: 0&lt;br/&gt;
  1253.  &lt;br/&gt;
  1254. But, somewhere on that Profile is a link.&lt;br/&gt;
  1255.  &lt;br/&gt;
  1256. &lt;em&gt;b. The Patient Spammer&lt;/em&gt;&lt;br/&gt;
  1257. (these are few &amp;amp; far between - it also depends on the presence of an &lt;em&gt;Edit&lt;/em&gt; function)&lt;br/&gt;
  1258.  &lt;br/&gt;
  1259. They post something innocuous (often a snippet copied from another post) but no link. They then wait, often many months. On return they edit the Profile/Post and add a link.&lt;br/&gt;
  1260.  &lt;br/&gt;
  1261. &lt;em&gt;c. The 2-Link Spammer&lt;/em&gt;&lt;br/&gt;
  1262. The really intelligent end of the Spammer spectrum is far better at SEO than you are. Most spammers drop links to sites that are so obviously SPAM that it shouts loudly at you.These folks drop links to sites that look OK; odd, but not spammy. You then find that they are dropping 100,000 links across all the Internet to sites that all in turn contain links to their target site.&lt;/p&gt;
  1263.  
  1264. &lt;p&gt;This whole thing can be continued indefinitely.&lt;/p&gt;
  1265.  
  1266. &lt;p&gt;Please help by logging in &amp;amp; reporting spammy posts and/or comments.&lt;/p&gt;
  1267. </description>
  1268.      <dc:creator>alexkemp</dc:creator>
  1269.      <pubDate>Tue, 14 Aug 2018 12:06:43 +0000</pubDate>
  1270.      <comments>https://www.openstreetmap.org/user/alexkemp/diary/44681#comments</comments>
  1271.    </item>
  1272.    <item>
  1273.      <title>Pengalamanku di State of the Map 2018 – Milan, Italia.</title>
  1274.      <link>https://www.openstreetmap.org/user/wulankhairunisa/diary/44679</link>
  1275.      <guid>https://www.openstreetmap.org/user/wulankhairunisa/diary/44679</guid>
  1276.      <description>&lt;p&gt;Bisa hadir dan bergabung di acara &lt;a href="https://wiki.openstreetmap.org/wiki/State_Of_The_Map" rel="nofollow"&gt;State of The Map&lt;/a&gt; (SotM) 2018 adalah salah satu pengalaman terbaik saya di tahun ini. Mengapa? Karena ini merupakan konferensi internasional yang diselenggarakan tahunan dimana menjadi tempat berkumpulnya orang-orang dari berbagai negara dan berbagai latar belakang untuk saling berbagi pengalaman dan pengetahuannya dalam berkontribusi ataupun menggunakan OpenStreetMap. Dan saya menjadi salah satu orang yang mendapatkan kesempatan tersebut melalui program beasiswa.&lt;/p&gt;
  1277.  
  1278. &lt;p&gt;Saya sangat bersemangat sejak pertama kali tahu bahwa akan ke Milan, ini akan menjadi pengalaman pertama saya mengunjungi Benua Eropa. Hari pertama tiba di Italia, saya bertemu dengan dua orang penerima beasiswa lainnya di bandara, Kshitiz (asal Nepal) dan Laura (asal Kenya). Kami pergi menuju penginapan bersama dan siang hari itu kami menyempatkan diri berkeliling di sekitar penginapan, menikmati pemandangan kota yang unik dan berburu Gelato. Yuumm!&lt;/p&gt;
  1279.  
  1280. &lt;p&gt;&lt;img src="https://wiki.openstreetmap.org/w/images/a/a8/Milan-streets-sighting-gelato.jpg" alt="Beberapa sisi jalan di Kota Milan dan Gelato pertamaku di Milan!"/&gt;&lt;/p&gt;
  1281.  
  1282. &lt;p&gt;SotM sendiri berlangsung selama tiga hari, 28-30 Juli 2018 dimana di setiap harinya ada banyak &lt;a href="https://2018.stateofthemap.org/program/" rel="nofollow"&gt;sesi&lt;/a&gt; yang dilaksanakan secara paralel di ruangan yang berbeda. Kadang saya merasa galau setiap kali harus memilih sesi mana yang akan saya hadiri karena hampir semua sesi menyugukan tema-tema yang sangat menarik!  Untungnya panitia acara membuat rekaman video untuk sesi-sesi tersebut dan mereka unggah di Youtube. Ada beberapa jenis sesi yang tersedia seperti presentasi, diskusi panelis dan workshop. Acara ini dihadiri lebih dari 400 peserta dari kalangan mahasiswa, akademisi, perusahaan dan komunitas OSM yang tertarik akan data terbuka dan OpenStreetMap. Disini saya bertemu dan berkenalan dengan banyak orang baru. Disini pula akhirnya saya bertemu dengan beberapa rekan kerja yang selama ini hanya bekomunikasi melalui &lt;em&gt;email&lt;/em&gt; ataupun &lt;em&gt;concall&lt;/em&gt;.&lt;/p&gt;
  1283.  
  1284. &lt;p&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/commons/2/28/State_of_the_Map_2018_Milano_day_1_54.jpg" alt="Foto bersama peserta SotM 2018"/&gt;
  1285. &lt;em&gt;Foto bersama peserta SotM 2018.&lt;/em&gt;&lt;/p&gt;
  1286.  
  1287. &lt;p&gt;Keberuntungan saya bukan hanya bisa menghadiri acara ini namun saya juga mendapat kesempatan mewakili Humanitarian OpenStreetMap (HOT) Indonesia untuk sharing mengenai salah satu projek yang sedang berjalan di Indonesia, yaitu Indonesia Road Mapping. HOT bekerjasama dengan Facebook untuk memetakan jaringan jalan di Indonesia menggunakan OpenStreetMap. Kami memanfaatkan bantuan &lt;em&gt;&lt;a href="https://wiki.openstreetmap.org/wiki/AI-Assisted_Road_Tracing" rel="nofollow"&gt;machine learning&lt;/a&gt;&lt;/em&gt; untuk mendeteksi jaringan jalan melalui foto udara yang kemudian diproses lagi melalui validasi berlapis oleh tim kami yang terdiri dari 25 orang kontributor lokal di Indonesia. Jaringan jalan di Indonesia masih banyak sekali yang belum terpetakan bahkan di data resmi yang dimiliki Badan Infomasi Geospasial. Oleh karena itu jika suatu saat dibutuhkan, sebagai contoh untuk respon darurat saat terjadinya bencana, maka data keterpaparan seperti jaringan jalan dari OSM bisa dimanfaatkan untuk membantu proses pengambilan keputusan dan distribusi bantuan ke daerah yang terdampak.&lt;/p&gt;
  1288.  
  1289. &lt;p&gt;&lt;img src="https://wiki.openstreetmap.org/w/images/2/26/Indonesia_Road_Mapping_presentation-sotm2018%281%29_.jpeg" alt="Indonesia Road Mapping Presentation"/&gt;&lt;/p&gt;
  1290.  
  1291. &lt;p&gt;Saya sangat berterima kasih kepada teman-teman dan para peserta konferensi lainnya yang sudah saling berbagi ilmu dan pengamalannya. Sungguh melalui acara ini saya diingatkan kembali bahwa di luar sana masih banyak orang-orang hebat, orang-orang kreatif dan orang-orang yang telah bekerja keras membangun komunitas pemetaan di daerahnya. Banyak sekali hal positif yang bisa diambil dan dipelajari, membuat saya merasa tidak mau kalah untuk terus belajar dan berkarya.&lt;/p&gt;
  1292.  
  1293. &lt;p&gt;Tak lupa ucapan terima kasih khusus saya berikan kepada Rob, Dorothea dan seluruh panitia SotM 2018 yang telah sukses menyelenggarakan acara yang &lt;em&gt;super duper cool&lt;/em&gt; ini. Terimakasih untuk segala bantuan dan dukungannya. Kalau bukan karena program beasiswa, belum tentu saya bisa hadir di acara ini :”).&lt;/p&gt;
  1294.  
  1295. &lt;p&gt;Semoga State of The Map bisa terus diselenggarakan setiap tahunnya dengan jumlah peserta yang lebih banyak lagi! &lt;/p&gt;
  1296.  
  1297. &lt;p&gt;Long live Mapping!&lt;/p&gt;
  1298.  
  1299. &lt;p&gt;-Wulan-&lt;/p&gt;
  1300.  
  1301. &lt;p&gt;&lt;img src="https://wiki.openstreetmap.org/w/images/8/84/State_of_the_Map_2018_Scholars_w.jpg" alt="SotM 2018 Scholars."/&gt;
  1302. &lt;em&gt;SotM 2018 Scholars&lt;/em&gt;.&lt;/p&gt;
  1303. </description>
  1304.      <dc:creator>wulankhairunisa</dc:creator>
  1305.      <pubDate>Tue, 14 Aug 2018 11:03:23 +0000</pubDate>
  1306.      <comments>https://www.openstreetmap.org/user/wulankhairunisa/diary/44679#comments</comments>
  1307.      <geo:lat>-6.23762008504827</geo:lat>
  1308.      <geo:long>106.85724610074</geo:long>
  1309.      <georss:point>-6.23762008504827 106.85724610074</georss:point>
  1310.    </item>
  1311.    <item>
  1312.      <title>modifiche zona Antirata Città di Castello Perugia Italia</title>
  1313.      <link>https://www.openstreetmap.org/user/claudio62PG/diary/44677</link>
  1314.      <guid>https://www.openstreetmap.org/user/claudio62PG/diary/44677</guid>
  1315.      <description>&lt;p&gt;Corretto uso del terreno vi era indicato un bacino idrico inesistente
  1316. aggiunto campo di calcio ed edificio&lt;/p&gt;
  1317. </description>
  1318.      <dc:creator>claudio62PG</dc:creator>
  1319.      <pubDate>Tue, 14 Aug 2018 10:47:05 +0000</pubDate>
  1320.      <comments>https://www.openstreetmap.org/user/claudio62PG/diary/44677#comments</comments>
  1321.      <geo:lat>43.4633</geo:lat>
  1322.      <geo:long>12.31962</geo:long>
  1323.      <georss:point>43.4633 12.31962</georss:point>
  1324.    </item>
  1325.  </channel>
  1326. </rss>
  1327.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.openstreetmap.org/diary/rss

Home · About · News · Docs · Terms

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