Style | StandardCards

OpenStreetMap Blogs

Friday, 17. August 2018

OpenStreetMap User's Diaries

OpenStreetMap Carto release v4.14.0

Dear all,

Yesterday, v4.14.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released and rolled out to the openstreetmap.org servers. It might take a couple of days before all tiles show the new rendering.

Changes include

  • Added text-repeat-distance for waterways
  • Added text-repeat-distance for railways
  • Add

Dear all,

Yesterday, v4.14.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released and rolled out to the openstreetmap.org servers. It might take a couple of days before all tiles show the new rendering.

Changes include

  • Added text-repeat-distance for waterways
  • Added text-repeat-distance for railways
  • Added icon for leisure=bowling_alley
  • Added icon for leisure=outdoor_seating
  • Added icon for leisure=bird_hide
  • Added icon for shop=video
  • Added icon for shop=paint
  • Added icon for shop=massage
  • Increased casing width of tertiary road on z12
  • Standard text halo for fitness_centre and fitness_station
  • Updated Docker images definitions
  • Small documentation updates

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.13.0...v4.14.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues


Mappning i närområdet

Har raderat snabbmatstället bredvid Coop som har lagts ner för någon månad sedan. I övrigt försöker jag mappa ut en ö i ån nedanför mig. Men problemet är att hela ån bara är en smal linje , vilket inte stämmer med verkligheten. Ön kom till därför att en gång i tiden gick det ett avloppsrör rakt ut i ån och där utloppet var bildades en ö. Idag är det fastland, fast ingen verkar äga ön. Har lagt u

Har raderat snabbmatstället bredvid Coop som har lagts ner för någon månad sedan. I övrigt försöker jag mappa ut en ö i ån nedanför mig. Men problemet är att hela ån bara är en smal linje , vilket inte stämmer med verkligheten. Ön kom till därför att en gång i tiden gick det ett avloppsrör rakt ut i ån och där utloppet var bildades en ö. Idag är det fastland, fast ingen verkar äga ön. Har lagt ut trall som gångstigar, men det känns ändå ostadigt att vistas på ån då allt i princip är gungfly. Tanken var att bygga en hel skulpturpark på ån, som svämmar över varje år. Ungefär som ett Atlantis. Men så långt kom jag aldrig.


No more broken multipolygons in the standard style on openstreetmap.org

A fairly big but silent change in the openstreetmap.org map rendering infrastructure has been completed in the last days which is going to have a significant effect on mapper feedback through the standard style map.

♦ here

Technically this is just a system and software update. This however includes a new osm2pgsql version which fundamentally changes the way multipolygon geometri

A fairly big but silent change in the openstreetmap.org map rendering infrastructure has been completed in the last days which is going to have a significant effect on mapper feedback through the standard style map.

Multipolygon error in the standard style here

Technically this is just a system and software update. This however includes a new osm2pgsql version which fundamentally changes the way multipolygon geometries are assembled. This change in osm2pgsql already happened more than a year ago but osm2pgsql had not been updated on the OSMF rendering servers since then.

Before this change standard style map rendering tried very hard to salvage whatever could be salvaged from a broken multipolygon geometry. This sometimes led to strange results but usually something was shown in some way even for invalid geometries. This led to mappers often being not very diligent about multipolygon geometries - as long as it shows up in the map it is fine. For data users not using osm2pgsql (like for example my low zoom map demo) this was a big problem because if they rely on valid geometries these invalid multipolygons are all unusable - yet customers of course expect them to be usable since you can see them in the map.

Long story short: That the standard map rendering should not try to be most tolerant about multipolygon validity but rather be more strict about it to give mappers better feedback about their mapping has been a demand of many people for a long time. This has now finally happened.

Osm2pgsql now uses libosmium for building multipolygons which means it is tolerant about

  • duplicate nodes
  • duplicate segments between nodes
  • noded self intersections (i.e. rings intersecting with a node at the intersection)

It however is strict about

  • non-noded self intersections
  • open rings

Quite a few people have noticed during the last week or so already that there are a few prominent gaps in rendering where there previously were features shown. Many of these have already been fixed quickly because of this improved feedback. This is not yet very visible in the multipolygon error numbers because these count errors and do not consider their visual impact and what has been fixed quickly is primarily a few high impact cases. But there is hope that with this change in rendering and the resulting improvement in feedback to mappers about errors the increase in the number of errors in multipolygons might be stopped or at least be slowed significantly.

Multipolygon error in the standard style here

There are plenty of prominently visible gaps in the map due to broken multipolygons still waiting to be fixed of course. If you work on fixing such errors it is also a good idea to take the opportunity to split larger geometries into smaller features which can be maintained more easily and are less prone to breaking.

Multipolygon error in the OSMI here

You can find these errors not only through missing geometries in the map but also through the OSM Inspector


Hussain Street, Rasool Park Lahore

Hussain Street, Rasool Park Lahore

Hussain Street, Rasool Park Lahore


posting screen shots (rendered in Microsoft Paint) in "New Diary Entry"

How do I post screen shots in new diary entries?

How do I post screen shots in new diary entries?


jd

#Here i lonched

#Here i lonched


Vetorização semi-automática de matas densas com Sentinel-2

Neste post descrevo, e submeto a opiniões, os passos adotados para um processamento semi-automático de vetorização a partir de imagem de satélite Sentinel-2 tendo em vista a vetorização de áreas de matas com suficiente distinção entre natural=wood e landuse=forest (mata natural e mata cultivada).

Importante:
esta metodologia é aqui proposta como um auxilío

Neste post descrevo, e submeto a opiniões, os passos adotados para um processamento semi-automático de vetorização a partir de imagem de satélite Sentinel-2 tendo em vista a vetorização de áreas de matas com suficiente distinção entre natural=wood e landuse=forest (mata natural e mata cultivada).

Importante:
esta metodologia é aqui proposta como um auxilío destinado somente ao mapeamento de coberturas de terreno (landcover).
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).
Não serve para objetos pequenos como lotes, praças, etc., pois removeria detalhes que podem ser vistos nas imagens padrão do OSM.

O propósito é:
-poder gerar desenho de grandes áreas de mata densa, em interiores do território, não densamente urbanizados;
-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. Mesmo assim, deve ser verificado visualmente o resultado ao final do processamento, junto com as imagens padrão do OSM.

DESCRIÇÃO INICIAL DOS DADOS:

IMAGENS: SENTINEL-2
Cobertura: ~100x100Km

Documentação original:
https://www.sentinel-hub.com/develop/documentation/eo_products/Sentinel2EOproducts

Licença compatível com OSM:
conforme https://wiki.openstreetmap.org/wiki/Sentinel-2

Fonte das imagens:
https://earthexplorer.usgs.gov/ camadas Sentinel-2

Bandas utilizadas: B11
(testadas todas as bandas, B11 se mostrou a melhor para o objetivo; condição:nuvem=0)

Índices utilizados: NDVI; CRE

NDVI : Normalized Difference Vegetation Index

Fórmula: NDVI = (B08 - B04) / (B08 + B04)

CRE : Chlorophyll Red-Edge (abbrv. Chlred-edge)
Fórmula: CRE = (B07 / B05) ^ -1

PROCESSAMENTO - PASSOS:

1)ESCOLHA DA IMAGEM DE SATÉLITE - SENTINEL:
Escolhida imagem em data que não gere discrepâncias (para mais ou para menos) de atividade vegetal: preferencialmente entre equinócio e solstício; evitar alto inverno e alto verão.

Caso Bom Jesus, RS:
https://earthexplorer.usgs.gov/ - Sentinel - "T22JEP_20180420T132231_B11"
Data: 2018/04/20
Hora: 13:22 (09:22 Brasil; gera alguma sombra)
(A imagem abaixo pode ser aberta em nova guia para visualizar detalhes em zoom maior.)


2)Examinar no QGIS valores do raster; procurar valores limites de distinções de classes:

-Usar a imagem Bing para localizar e marcar exemplos claramente identificáveis dos tipos de vegetação a serem distinguidos em classes.

Exige conhecimento da vegetação típica básica, e sobretudo poder identificá-la em imagem de satélite em cores naturais, como Bing.
Além de evidentemente poder distinguir os demais elementos, como área urbanizada, campo ralo, trilhas e corpos de água.

A identificação dos tipos wood e forest é possível de fazer somente sobre imagem Bing. Basta saber distingui-los.

O que o presente método propõe é usar uma seleção amostral, feita sobre a imagem Bing, de objetos dos quais se tenha seguro conhecimento, que sejam representantes destes 2 tipos, wood e forest, bem como dos demais objetos que não são estas 2 classe, para, nas imagens Sentinel, avaliar os valores típicos de pixels dos objetos selecionados, testando se os mesmos limites de valores são encontrados em matas típicas em algumas diversas porções da imagem.

Os valores típicos em uma imagem podem apresentar alguma variação em outras imagens e outros locais. Por isso todos os passos do método deve ser repetidos em trabalhos com outras imagens ou territórios.

Uma vez que se encontre os valores limites típicos na imagem, usá-los como parâmetros para deduzir os objetos dos tipos wood e forest na imagem toda.

-Áreas de mata cultivada isoladas são mais fáceis de distinguir no Bing. Não tanto quando plantadas em meio a mata natural.
Assim é preferível procurar primeiramente áreas destacadas de plantação, em campo aberto. Como lotes mais ou menos regulares de mata plantada.
As espécies plantadas mais comuns nesta região de enfoque são sobretudo o Pinus, para indústria de celulose, e menos comumente Eucalipto, mais para construção e lenga.

As florestas de Pinus, e florestas plantadas em geral, costumam apresentar espécimes regularmente espaçados, formando uma malha regular densa e identificável. Procurar por estas feições.
São plantadas em campos planos e também em encostas. Nas encostas podem ser detectadas por várias trilhas de serviço para extração, escalonadas. Eucalipto costuma ser plantado ao redor de sedes de fazendas em campo aberto.
A superfície apresenta maior homogeneidade de tamanho de indivíduos. Forma uma superfície mais regular.

-As matas nativas ou mais velhas, com menor atividade biológica, e por isso índices diversos nas imagens, são o restante de matas a identificar. Em geral apresentam a superfície da cobertura mais irregular. E em locais onde não haja estradas ou trilhas de serviço indicando acesso constante.

Estas áreas exclusivas com respectivos objetos-tipo servirão de amostragem de elementos das classes para avaliação dos valores de pixels. Podem ser feitos polígonos para marca-los, em layer à parte.
Com estes objetos-tipo, serão verificados e anotados os valores típicos dos pixels nas respectivas imagens de referência, examinadas alternando os layers sobre o mesmo objeto amostral: B11, NDVI, CRE. E anotados os limites de valores em relação aos objetos das demais classes. Estes valores limites típicos serão usados para distinção automática na imagem toda.

CASO: Matas nos municípios de Bom Jesus e Monte Alegre dos Campos, RS:


SENSOR / ÍNDICE :: B11 :: NDVI :: CRE
Min. :: 511 :: -0.87 :: 0.2
Max. :: 2709 :: +0.87 :: 0.75


MATA NATIVA (n.=wood) :: 1200-1800::0.30 /0.80 ::
MATA PLANTADA (l.=forest) ::150-1200 :: 0.70/0.80 ::

Mata na sombra(encosta.Sul) ::150-400 ::0.30/0.65 :: 0.4 - 0.5
Mata no sol (encosta.N.) :: 1200-1800 :: 0.65/0.80:: 0.25-0.3

campo ralo (null) :: 1500 -3000 :: :
urbanização :: 1700-3000 ::-0.10/0.20 :

água parada (açude) :: 50-150 ::-0.10/0.10 :: 0.8-1.0
água corrente (rio) :: 150-300 :: -0.30/0.60 :: 0.5-0.8

LIMITE P/ ÁGUA = 0 :: 0.5

Resultado observado:
B11 distingue bem entre mata wood e forest. Em diferentes áreas do terreno abrangido na imagem, as mesmas classes de matas apresentam alguma variação, o que pode gerar ainda algum grau de imprecisão. No entanto o limite de matas x campos ou urbanização é bem distinto. Não separa rios de forest; para isto necessita contrastar B11 com outros índices mais adequados, a seguir.
-NDVI e CRE destacam o que não é vegetação, como corpos de água.

[IMAGEM-2]


3)CORREÇÕES:
Corrigir o que não é bem detectado ou misturado quando somente usando na B11:
mata na sombra (encostas Sul); água corrente

Método: usados os índices NDVI e CRE para contrastar B11

OPERAÇÃO: B11+(1-NDVI)+CRE
Raster calculator - SINTAXE: "T22JEP_20180420T132231_B11@1" + ((1-"NDVI@1")*1800) + ("CRE@1" *2600)
Agregados empiricamente os fatores ponderadores NDVI*1800 e CRE*2600, para que fiquem acima de B11 (~2000) e equilibrá-los.

RESULTADO: "B11+1-NDVI+CRE.tif" : (10m/px)

[IMAGEM-3]


4)TESTAR CLASSES VISUALMENTE:
-Igual à etapa (2), para B11+1-NDVI+CRE:

Resultado:
5 CLASSES :
(1)forest <= 2150 <
(2)wood <= 2600 <
(3)campo alto ou ciliar <= 3500 <
(4)campo ralo ou trilha <= 3950 <
(5)água, estrada, cidade, lavourado


5)PROCESSAR A IMAGEM, REDUZINDO ÀS CLASSES TESTADAS:

CONDICIONAIS "if/then/else":
Raster calculator:
SINTAXE: (("@1"<x)* operação ) => se sim=1(opera); se não=0(não opera)

SINTAXE :
(1* ( "B11+1-NDVI+CRE@1" <=2150 ))
+ (2* (( 2150 < "B11+1-NDVI+CRE@1" ) AND ( "B11+1-NDVI+CRE@1" <= 2600 ) ))
+ (3* (( 2600 < "B11+1-NDVI+CRE@1" ) AND ( "B11+1-NDVI+CRE@1" <= 3500 ) ))
+ (4* (( 3500 < "B11+1-NDVI+CRE@1" ) AND ( "B11+1-NDVI+CRE@1" <= 3950 ) ))
+ (5* ( "B11+1-NDVI+CRE@1" > 3950 ))

Resultado:
Imagem com valores limitados às classes: "B11-5classes.tif"

[IMAGEM-4]


6)SIMPLIFICAR ÁREAS, REMOVER PIXELS ISOLADOS:

OPERAÇÕES: ~1min cada
QGIS: Processing / Toolbox /
* GDAl / Analysis / Sieve
* GRASS / r.neighbor

1 Sieve T3 C8 - Remove até 3px(10x30m)
2 Neig Max 3 Ci - Aumenta borda do maior, 1px cada lado (10m+10m)
3 Sieve T3 C4
4 Neig Mode 3 Sq
5 Sieve T6 C8 - Remove até 6px(20x30m)

Resultado:
5 classes filtradas: "B11-5classes-Filtrado.tif" (10m/px)

[IMAGEM-5]


7)REDUZIR A IMAGEM SOMENTE ÀS CLASSES DE INTERESSE (forest e wood; 1 e 2) E IGUALAR DEMAIS CLASSES (3,4,5) A "ZERO":

QGIS: Raster calculator: (( "@1" > 2 ) * 0) + (( "@1" <=2 ) * "@1" )


8)CRUZAR O RASTER PROCESSADO COM OS VETORES EXISTENTES NO OSM, DE RIOS E ESTRADAS, PARA MELHORAR RECORTES NAS MATAS:

-Baixar dados do OSM/overpass: highway=* or waterway=* and type:way
-Criar um novo layer vetor SHP contendo as linhas de highway e waterway que servirão para recortar.
-Adicionar um campo de número real, com valor "0"(zero) para todas as linhas/polígonos a serem filtrados
-Gerar um buffer sobre todas as linhas:
o buffer deve ser maior que a resolução da imagem destino e menor que os menores grupos de pixels após as filtragens.
Para não gerar pixels ligados só nos cantos nem elminar a mais do que as filtragens anteriores.
Utilizado buffer de 20m; suficiente para imagem de 10m/px. Contendo valor classe=0.
-Salvar o buffer como SHP

RASTERIZAR O VETOR SOBRE A IMAGEM:
-Fazer uma cópia simples do raster anteriormente processado, a ser alterada
-Adicionar o layer vetor do buffer sobre a imagem destino:
QGIS: Raster / Conversion / Rasterize: SHP com o buffer; campo p/ valor "0"(zero); imagem destino

ÚLTIMA FILTRAGEM:
simplificar; remover últimos pequenos clumps de até 20 pixels isolados (4x5 pixels) que sobram em alguns recortes : Sieve T20 C4

Resultado: "B11-0-1-2-Filtrado+OSM.tif"

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. Somente áreas de matas com maior homogeneidade, que possuem dimensões muito maiores.

[IMAGEM-6]


9) ELIMINAR DEMAIS CLASSES NÃO UTILIZADAS - Igualar "zero" a "null":
(ajuda a reduzir a quantidade de polígnos no poligonize):

QGIS: gdal_translate / -a_nodata <X>
(X = valor da classe p/null)

Resultado:
Raster Classes 1+2+null : "B11-1-2-null+OSM.tif"


10)VETORIZAR - Gerar polígonos do raster:

QGIS: Raster / conversion / poligonize
MANTER A MESMA CRS NO PROJETO


11)SUAVIZAR POLÍGONOS - despixelizar:
QGIS: GRASS commands -> v.generalize.smooth:
(https://grass.osgeo.org/grass64/manuals/v.generalize.html)

* Sliding Averaging:
look_ahead = 3 (mín=3, sempre ímpar) slide = 0.7

Resultado: ~5min "Sliding-Average-L3-SL07-OK.shp"

LEGENDA:
Verde claro: mata nativa (natural=wood)
Verde escuro: mata cultivada (landuse=forest)
Branco: null


12)ADICIONAR TAGS OSM E LIMPAR:

ELIMINAR DO SHP POLÍGONOS TRUNCADOS DE BORDA DE IMAGEM ou RESTRINGIR POLÍGONOS A MUNICÍPIO

Salvar como novo layer: "B11+OSM-limpo.shp"

-Selecionar todo polígono que encosta nas bordas do layer e remover manualmente (pode fazer um buffer menor que os limites do layer);
-Adicionar tags (Table Manager + Field Calculator): landuse=forest; natural=wood;
-Remover tags sem uso (area; classe).

Salvar como WGS84-EPSG:4326


13) Opcional: Selecionar por máscara de município
(pois o JOSM fica muito pesado se abrir mais de 10.000 polígonos)

QGIS: Vector / Spatial Query: "SHP-origem" + Intersects + "SHP-máscara" - selection / invert / remove


PROCESSOS NO JOSM:

1)ABRIR CADA SHP SEPARADAMENTE :

-Sem baixar dados do OSM
-salvar como .osm

Já entra como polígono ou multipol(outer/inner); curvas com ~1nó/10m (mesma resolução das imagens raster)

Monte Alegre dos Campos:
QGIS: SHP 5,2MB; features/polígonos= 3.519
JOSM: "B11-MA-4326.osm" : 23,8MB; nodes= 243.070


2)SIMPLIFICAR:
Select: type:way / Symplify way
Resultado: nodes= 136.853


3) VALIDAR SEPARADAMENTE
-Sem baixar dados do OSM

Resultado:
Errors: (0)
Warnings: (28)
Self-intersecting polygon ring (3)
Self-intersecting ways (25)

Todos foram casos de auto-intersecção em cruz (quina) - imagem abaixo.
Talvez possa evitar previamente no QGIS com
QGIS: GRASS commands -> v.generalize.smooth / Displacement
(https://grass.osgeo.org/grass64/manuals/v.generalize.html)

Solução:
Alteração manual: "unglue(G)" nos nós de cada intersecção; afastar nós e ways
Cuidar: testar todos os nós da intersecção após o unglue; manter polígonos e multipolígonos fechados ao final

VALIDAR NOVAMENTE:
Resultado: VALIDAÇÃO COMPLETA (0)


4) TESTES DE CONFLITO COM O EXISTENTE:
Baixar dados do OSM;

VALIDAR:
Resultado: VALIDAÇÃO COMPLETA (0)

Pronto para aprovação e upload


5) PARA UPLOAD DOS NOVOS DADOS AO OSM:

Proposto salvar em changeset exclusivo, com a nota:
"adição de polígonos de matas (wood;forest) semi-automatizados com validação manual"

O arquivo .osm resultante deste teste para verificação pode ser baixado neste repositório (não feito upload ao OSM).


Comentários:

Onde acho que ainda pode melhorar:

Na filtragem, manter o mesmo buffer de aumento e retorno de limites de áreas vizinhas.
Ficou um pouco a mais, 10m maior, pra dentro da mata. Por um lado evita invadir outras coisas.
Mas usando os vetores do OSM para buffer de estradas e waterway, isso já resolve.

A imagem classificada tem 10m/px.
A área cobre 100.000mx100.000m.

Na minha opinião tem que simplificar e eliminar clusters pequenos, como <40x40m (~16px), pois:
-o OSM usa simplificação de áreas de terreno, exemplo maior as coast_lines;
-manter áreas pequenas de <40x40m, tumultua o resultado com objetos pequenos sem alta precisão para a imagem, objetos que não são objetivo do processo.
O objetivo são as áreas de mata densa e mais homogêneas.

Por favor, fiquem à vontade para tecer comentários se desejarem, como se vale ou não vale a pena investir neste tipo de processo para desenhar áreas de mata densa, em regiões de interior, para o OSM.

Thursday, 16. August 2018

OpenStreetMap User's Diaries

日本国内での車両別アクセス制限タグを規定するためのドラフト

osm_jp_access

OpenStreetMap 日本国内での車両別アクセス制限タグを規定するためのドラフトです。

ドラフト版が完成したらOpenStreetMap/wiki - JapanTagging (議論) のページへ転載します。

OpenStreetMap Japan Key:access draft

提案する日本の「車両別アクセスタグ」

1. access=* ┃ ┣━ 2. foot=* 歩行者 ┃ ┗━ 3. vehicle=* 車両    ┃    ┣━ 4. bicycle=* 自転車    ┃    ┣━ 5. carriage=* 軽車両    ┃    ┗━ 6. motor_vehicle 動力付き車両       ┃       ┣━ 7. t

osm_jp_access

OpenStreetMap 日本国内での車両別アクセス制限タグを規定するためのドラフトです。

ドラフト版が完成したらOpenStreetMap/wiki - JapanTagging (議論) のページへ転載します。


OpenStreetMap Japan Key:access draft

提案する日本の「車両別アクセスタグ」

1. access=* ┃ ┣━ 2. foot=* 歩行者 ┃ ┗━ 3. vehicle=* 車両    ┃    ┣━ 4. bicycle=* 自転車    ┃    ┣━ 5. carriage=* 軽車両    ┃    ┗━ 6. motor_vehicle 動力付き車両       ┃       ┣━ 7. tram 路面電車       ┃       ┣━ 8. trollerbus 「トロリー」 トロリーバス       ┃       ┗━ 9. motor_car 自動車          ┃          ┣━ 10. hgv_caravan 「けん引」 重被牽引車をけん引しているけん引自動車          ┃          ┣━ 11. disabled 「標章車」 高齢運転者等、標章自動車          ┃          ┣━ 12. agricultural 「小特」 小型特殊自動車          ┃          ┣━ 13. route_bus 「路線バス」 路線定期運行の用に供する自動車          ┃          ┣━ 14. taxi=* 「タクシー」 一般乗用旅客自動車運送事業の用に供する自動車          ┃          ┣━ 15. moped=*,mofa=*,motorcycle=*「二輪」 二輪の自動車及び原動機付自転車          ┃  ┃          ┃  ┣━ 16. motorcycle 「自二輪」 大型自動二輪車、普通自動二輪車          ┃  ┃          ┃  ┗━ 17. moped 「小二輪」 小型二輪車、原動機付自転車          ┃     ┃          ┃     ┗━ 18. mofa 「原付」 原動機付自転車          ┃          ┣━ 19. hgv=*,goods=* 「貨物」           ┃  ┃          ┃  ┣━ 20. hgv:l 「大貨」           ┃  ┃          ┃  ┣━ 21. goods:m 「中貨」           ┃  ┃          ┃  ┣━ 22. goods:ms 「準中貨」           ┃  ┃          ┃  ┗━ 23. goods:normal 「普貨」           ┃          ┣━ 24. motor_car:l=*,motor_car:xm=*,motor_car:xl=* 「大型等」          ┃  ┃          ┃  ┣━ 25. motor_car:l 「大型」 大型自動車          ┃  ┃  ┃          ┃  ┃  ┣━ 20. hgv:l 「大貨」           ┃  ┃  ┃          ┃  ┃  ┗━ 26. psv:l 「大乗」 大型乗用自動車          ┃  ┃     ┃          ┃  ┃     ┣━ 27. tourist_bus 「観光バス」          ┃  ┃     ┃          ┃  ┃     ┣━ 28. bus:l 「大型バス」          ┃  ┃     ┃          ┃  ┃     ┗━ 29. minibus 「マイクロ」          ┃  ┃        ┃          ┃  ┃        ┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車          ┃  ┃          ┃  ┣━ 30. motor_car:m 「中型」 中型自動車          ┃  ┃  ┃          ┃  ┃  ┣━ 21. goods:m 「中貨」           ┃  ┃  ┃          ┃  ┃  ┗━ 31. psv:m 「中乗」 中型乗用自動車          ┃  ┃          ┃  ┣━ 32.motor_car:xm 「特定中型」 特定中型自動車          ┃  ┃  ┃          ┃  ┃  ┣━ 33.hgv:xm 「特定中貨」           ┃  ┃  ┃          ┃  ┃  ┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車          ┃  ┃          ┃  ┣━ 35.hgv 「大貨等」           ┃  ┃  ┃          ┃  ┃  ┣━ 20.hgv:l 「大貨」           ┃  ┃  ┃          ┃  ┃  ┣━ 34.mortor_car:xl 「大特」 大型特殊自動車          ┃  ┃  ┃          ┃  ┃  ┗━ 33.hgv:xm 「特定中貨」          ┃  ┃          ┃  ┣━ 22.goods:ms 「準中貨」           ┃  ┃          ┃  ┗━ 23.goods:normal 「普貨」           ┃          ┣━ 25.motor_car:l 「大型」 大型自動車          ┃  ┃          ┃  ┣━ 20.hgv:l 「大貨」           ┃  ┃          ┃  ┗━ 26.psv:l 「大乗」 大型乗用自動車          ┃     ┃          ┃     ┣━ 27.tourist_bus 「観光バス」          ┃     ┃          ┃     ┣━ 28.bus:l 「大型バス」          ┃     ┃          ┃     ┗━ 29.minibus 「マイクロ」          ┃        ┃          ┃        ┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車          ┃          ┣━ 30.motor_car:m 「中型」 中型自動車          ┃  ┃          ┃  ┣━ 21.goods:m 「中貨」           ┃  ┃          ┃  ┗━ 31.psv:m 「中乗」 中型乗用自動車          ┃          ┣━ 32.motor_car:xm 「特定中型」 特定中型自動車          ┃  ┃          ┃  ┣━ 33.hgv:xm 「特定中貨」           ┃  ┃          ┃  ┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車          ┃          ┣━ 36.motor_car:ms 「準中型」 準中型自動車          ┃  ┃          ┃  ┣━ 22.goods:ms 「準中貨」           ┃  ┃          ┃  ┗━ 37.psv:ms 「準中乗」 準中型乗用自動車          ┃          ┣━ 38.motor_car:normal 「普通」 普通自動車          ┃  ┃          ┃  ┣━ 23.goods:normal 「普貨」           ┃  ┃          ┃  ┣━ 39.motor_car:kei 「軽」 軽自動車          ┃  ┃          ┃  ┗━ 40.psv:ms 「普乗」 普通乗用自動車          ┃          ┗━ 41. psv 「乗用」 専ら人を運搬する構造の自動車             ┃             ┣━ 31.psv:m 「中乗」 中型乗用自動車             ┃             ┣━ 42.bus 「バス」             ┃  ┃             ┃  ┗━ 26.psv:l 「大乗」 大型乗用自動車             ┃     ┃             ┃     ┣━ 27.tourist_bus 「観光バス」             ┃     ┃             ┃     ┣━ 28.bus:l 「大型バス」             ┃     ┃             ┃     ┗━ 29.minibus 「マイクロ」             ┃        ┃             ┃        ┗━ 34.psv:xm 「特定中乗」 特定中型乗用自動車             ┃             ┣━ 37.psv:ms 「準中乗」 準中型乗用自動車             ┃             ┗━ 40.psv:normal 「普乗」 普通乗用自動車

参考

| 略称 | 車両の種類 | |:-------------:|:--------------- | | 大型 | 大型自動車 | | 大型等 | 大型自動車、特定中型自動車及び大型特殊自動車 | | 中型 | 中型自動車 | | 特定中型 | 特定中型自動車 | | 準中型 | 準中型自動車 | | 普通 | 普通自動車 | | 大特 | 大型特殊自動車 | | 自二輪 | 大型自動二輪車及び普通自動二輪車(道路交通法施行規則第二条の表備考の規定により二輪の自動車とみなされ、かつ、同表の大型自動二輪車又は普通自動二輪車に区分される三輪の自動車を含む。) | | 軽 | 長さが三・四〇メートル以下、幅が一・四八メートル以下、高さが二・〇〇メートル以下の普通自動車(内燃機関を原動機とする自動車にあつては、総排気量が〇・六六〇リットル以下のものに限る。) | | 小特 | 小型特殊自動車 | | 原付 | 原動機付自転車 | | 二輪 | 二輪の自動車及び原動機付自転車 | | 小二輪 | 道路交通法施行規則第二十四条第一項に規定する小型二輪車及び原動機付自転車 | | 自転車 | 普通自転車 | | トロリー | トロリーバス | | 乗用 | 専ら人を運搬する構造の自動車 | | 大乗 | 大型乗用自動車 | | 中乗 | 中型乗用自動車 | | 特定中乗 | 特定中型乗用自動車 | | 準中乗 | 準中型乗用自動車 | | バス | 大型乗用自動車及び特定中型乗用自動車 | | 大型バス | 乗車定員が三〇人以上の大型乗用自動車 | | マイクロ | 大型バス以外の大型乗用自動車及び特定中型乗用自動車 | | 路線バス | 道路運送法(昭和二十六年法律第百八十三号)第九条第一項に規定する一般乗合旅客自動車運送事業者による同法第五条第一項第三号に規定する路線定期運行の用に供する自動車 | | 普乗 | 普通乗用自動車 | | タクシー | 道路運送法第三条第一号ハに規定する一般乗用旅客自動車運送事業の用に供する自動車 | | 貨物 | 大型乗用自動車以外の大型自動車、中型乗用自動車以外の中型自動車、準中型乗用自動車以外の準中型自動車及び普通乗用自動車以外の普通自動車 | | 大貨 | 大型乗用自動車以外の大型自動車 | | 大貨等 | 大型乗用自動車以外の大型自動車、特定中型乗用自動車以外の特定中型自動車及び大型特殊自動車 | | 中貨 | 中型乗用自動車以外の中型自動車 | | 特定中貨 | 特定中型乗用自動車以外の特定中型自動車 | | 準中貨 | 準中型乗用自動車以外の準中型自動車 | | 普貨 | 普通乗用自動車以外の普通自動車 | | けん引 | 重被牽 引車を牽 引している牽 引自動車 | | 標章車 | 高齢運転者等標章自動車 |

継承関係

車両種別の継承関係
上記は、車両の種類の略称の記載をもとに属性の継承関係を表したもの

継承関係の注意点

よく誤解されると思われる項目

  • 「路線バス」は「バス」を継承していません。つまり、「路線バス」は「バス」ではありません。(「大型」でもない)
    このことにより、「バス」進入禁止どうろでも「路線バス」はその規制を受けません。

  • 同様に「タクシー」は「中乗」「普乗」を継承していません。

  • 「二輪」と「自二輪」は同一ではありません。タグ的に区別する必要が有ります。

  • 「小二輪」は「原付」も含みます。

マトリックス表

継承関係をマトリックスで表現したもの

  • [matrix.ods](matrix.ods) [PDF](matrix.pdf)

World Wide でのタグ構成

access=* (カテゴリ: すべての陸上交通) ┣━ 車両を使わない移動 ┃  ┣━ foot=* (歩行者) ┃  ┣━ ski=* ┃  ┣━ inline_skates=* ┃  ┣━ ice_skates=* ┃  ┗━ horse=* (乗馬) ┗━ vehicle=* (カテゴリ: すべての車両)    ┣━ 動力がない車両    ┃  ┣━ 二輪車 ┃  ┃  ┗━ bicycle=* (自転車)    ┃  ┗━ 三輪以上 ┃     ┣━ carriage=* (馬+馬車) ┃     ┗━ trailer=* (トレイラー。他の車両が牽引する必要があり、それにも自身の通行制限があります) ┃      ┗━ caravan=* ([W] キャンピングトレーラー、キャラバンとも呼ばれます)┗    ┗━ motor_vehicle=* (カテゴリ: すべての動力付き車両)       ┣━ 二輪車    ┃   ┣━ motorcycle=* (オートバイ。二輪の動力付き車両、自動車専用道路を通行可)    ┃   ┣━ moped=* (速度制限付きの原動機付き自転車。例: 多くは50ccエンジンで、最高速度約45km/h)    ┃   ┗━ mofa=* ("低速モペット"、通常は最大設計速度25km/h)       ┣━ 三輪以上    ┃   ┣━motorcar=* 自動車    ┃   ┃   ┗━ motorhome=* ([W] キャンピングカー)       ┃   ┣━ tourist_bus=* ツアーバス、観光バス(路線バスでないもの)       ┃   ┣━ goods=* (小型貨物トラック、最大積載量3.5トン未満)       ┃   ┣━ hgv=* (大型貨物トラック、最大積載量3.5トン以上)       ┃   ┣━ agricultural=* (農耕用動力付き車両(トラクターなど)、追加の制限事項があります(速度制限25km/hなど))       ┃   ┣━ atv=* バギー (幅が50インチ(1.27m)以下に制限されています)提案中です。代わりにmaxwidth=1.27を使用したほうがよいかもしれません。       ┃   ┗━ snowmobile=*       ┗━ 用途別        ┣━psv=* (乗合自動車)        ┣━bus=* (乗合自動車として使われる大型バス)        ┣━minibus=* (乗合自動車として使われる小型バス)        ┣━share_taxi=* (要求に応じて輸送する小型バス)         ┣━taxi=* (タクシー)        ┣━hov=* (相乗り自動車、2人以上が同乗した車両(地域によって異なる))        ┣━car_sharing=* (カーシェアリングサービス)        ┣━emergency=* (カテゴリー: 緊急車両。救急車、消防車、パトカーなど)        ┣━hazmat=* (危険物搭載車両)        ┗━disabled=* (身体障害者標識や、その他の障害者向けの許可。通行制限から除外するために交通標識に使用されます。ただし、駐車に関するものを除く)

World Wide との相違点

  • 日本では「自転車」は「軽車両」に含まれるが、[bicycle]と[carriage]は別物

  • 日本では「けん引」は「牽引している車両(トレーラーヘッド)」を表すが、OSMでは[trailer]は「引っ張られる台車」を示すため「非動力車両」に分類されている。そのため、提案では「hgv_caravan」と日本独自タグを新設しています。
    (タグの新設をやめ、「けん引」を「trailer」としても不都合は生じないと思いますが?)

  • 日本の「自動車」と[motor_vehicle]との違い: 日本では動力付き車両であっても「自動車」とみなさないもの(トロリーバス、路面電車など)が存在するため、提案では「motor_car(自動車)」と独自タグを新設しています。

  • 二輪車について、日本の場合は、motorcycle,moped,mofa に階層関係が存在します。

  • 「自二輪」にmotorcycleを割り当てました。「二輪」には独自タグを新設するのを避けるため、motorcycle,moped,mofaを列記することとしましたが、適切なワードを新設したほうが良いのではないでしょうか?

    • その他のタグ列記項目
    • 「二輪」→ motorcycle,moped,mofa
    • 「大型等」→ motor_car:l=,motor_car:xm=,motor_car:xl=*
    • 「貨物」→ hgv=,goods=

CC0


Updates in Lima and Arequipa (August 2018)

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:

  • Some streets in Lima and Callao are in English (like "Ayacucho Avenue")
  • More business between Plaza San Miguel and surroundings (30 min to airport)
  • Many store

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:

  • Some streets in Lima and Callao are in English (like "Ayacucho Avenue")
  • More business between Plaza San Miguel and surroundings (30 min to airport)
  • Many stores at J. Chávez airport
  • Addings in the streets (which were incomplete)
  • Design improvements for the Government Palace (3D graphic)
  • Pedestrian areas in the Parque de la Reserva
  • More buildings and recreational areas (parks) in the district of Rímac
  • Design update of the Mounumental Stadium (Estadio Monumental, with boxes, entrance areas and stands)
  • Redesign of the Jockey Plaza (with toilets, shops and parking areas)

In addition, in other cities:

  • Restaurants in Arequipa and close places (with addresses and phone numbers)
  • Some of the speed limits in Arequipa's exteriors

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.

Translated from my spanish post


مرحبا

شكرا لجميع اصدقائي هنا

شكرا لجميع اصدقائي هنا


01-24(24)

01-24内容:华信路—华龙路—化纤厂路—花园路片区初步

01-24内容:华信路—华龙路—化纤厂路—花园路片区初步

Wednesday, 15. August 2018

OpenStreetMap User's Diaries

Managed forest polygon not rendering

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.

Today I n

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.

Today I noticed that the entire area was missing from the rendered map. I can't find any apparent problem with the area, except that it might be too complex. Can anyone explain why it fails to render?

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?


Learn about Hempseed Oil

0

HempWorx CBD Oil Online

HOME » HEMPWORX CBD OIL ONLINE

HempWorx CBD Oil Online

HempWorx CBD Oil and other CBD Products are extremely popular because they work! HempWorx has full spectrum CBD oil, THC Free CBD oil, CBD oil for pets, dogs & cats, CBD topical pain cream and even CBD skin care!

HempWorx CBD Oil Full Spectrum

0

HempWorx CBD Oil Online

HOME » HEMPWORX CBD OIL ONLINE

HempWorx CBD Oil Online

HempWorx CBD Oil and other CBD Products are extremely popular because they work! HempWorx has full spectrum CBD oil, THC Free CBD oil, CBD oil for pets, dogs & cats, CBD topical pain cream and even CBD skin care!

HempWorx CBD Oil Full Spectrum

HempWorx 750mg and 500mg Full Spectrum CBD Oil are in demand! Currently HempWorx is shipping to the USA but soon HempWorx will be available in Canada, UK and Europe! The intent is to go global with their product line. Canada is legal on Oct 17th, 2018 but HempWorx will have a CBD oil in Canada to Buy Online very soon!

When you Buy HempWorx 750mg or 500mg full spectrum CBD oil, you can be assured you are getting a high quality, premium CBD oil. HempWorx 750 mg and 500mg has become extremely popular in the USA and Canada and are considered one of the BEST CBD oil brands. HempWorx CBD oil products are grown and manufactured in the state of Kentucky in the only FDA approved facility for hemp products, which means they adhere to high standards. Great news for you!

HempWorx CBD Oil is Available in Two Potent Concentrations for People

HempWorx CBD Oil comes in a 1oz bottle, 30ml and is either 500mg = 10mg per serving or 750mg = 15mg per serving of active Cannabidiol (CBD).

HempWorx 750mg & 500mg CBD Oils Come in Two Fabulous Flavors

Our hemp oils are available in two great flavors – Peppermint and au Natural. We do not use artificial sweeteners or flavoring in our products.

HempWorx 750mg & 500mg Come in Full Spectrum & THC Free Versions

We have Full Spectrum Hemp CBD Oil available that contains trace amounts of THC to help you achieve the “Entourage Effect”. Or you can purchase a “THC FREE” version of the HempWorx 750mg & 500mg CBD oils if you are subject to regular drug testing in your job. This is an Isolate version of our product line with a very high potency. HempWorx CBD oil is potent and powerful whether isolate or full spectrum, though if you do not go through drug testing, trace THC is slightly more beneficial.

HempWorx Has Pet Products!

HempWorx CBD Oil for pets is 250mg of full spectrum CBD in a natural flavor. Pets love HempWorx CBD oil. Pet CBD oil can be used for dogs, cats and other animals.  Horses can use the 750mg people version. It’s all the same great CBD oil! HempWorx also offers Dog Treats, which of course are infused with CBD and dogs love them!

HempWorx CBD Topical Pain Cream

HempWorx Relief topical pain cream works on contact. Soothe your aches and pains with this potent CBD pain cream. Customers rave about this product. It’s a very popular item!

Look Your Best with HempWorx CBD Skin Care Products

HempWorx offers 2 CBD skin care products, Revive and Renew. Both tackle fine lines and wrinkles and help nourish the skin with age defying vitamins and minerals.

HempWorx CBD Oil Products are Very Affordable

Our HempWorx 750mg & 500mg oils are affordable and below the average market retail price. You can purchase these products online at Compare CBD. The 750mg CBD oil is $89 US per bottle and the 500mg CBD oil is $69 US per bottle, whether it is Full Spectrum or THC free version.

*Please note default pricing on our Compare site is UK, please change pricing to US dollars. You will see the exact price for your HempWorx CBD Oil and Hemp Products when you click Buy Now.

HempWorx is Non GMO and Organic Hemp

HempWorx CBD oil is produced & manufactured on Kentucky farms utilizing Organic methods only and is free of GMOs, synthetics, fillers, and other ingredients that could be harmful.

HempWorx CBD Oil Has a 30 Day Money Back Guarantee

HempWorx is so confident in our oils that we give you a 30 day empty bottle refund policy. If you change your mind within 30 days of ordering, send it back and HempWorx will refund your purchase. You will need to contact HempWorx if you wish to return your purchase.

HempWorx CBD products and hemp oils are currently available in the USA only. Canada, Europe and the UK will be launching soon!

Join HempWorx Affiliate Program! Start a CBD Business Online!

Do you want to start your own CBD business? Do you want to earn money selling HempWorx CBD products? Interested in the HempWorx affiliate program? You can Join HempWorx today and be in business in 10 minutes! You will be provided an awesome back office, your own replicated websites and some great tools to help you build your business. HempWorx has online support forums on Facebook to help you get your business going in the right direction.

The CBD industry is expected to grow 700{53eb417ea3d555a48daffa75a297d3746e9d457709787625d144e594897f6ed5} by the year 2020! That’s massive! Jump on the CBD band wagon today. You do not want to miss this once in a lifetime opportunity. As more countries become legal, more opportunities for business will appear. Get your foot in that door with HempWorx!

Buy CBD Wholesale

Did you know you can buy HempWorx CBD oil wholesale in the USA and sell it in your retail location or even online? You just can’t undercut HempWorx advertised pricing. The HempWorx Wholesale CBD program is extremely lucrative with multiple packages to suit any budget.

Compare CBD also offers a Wholesale CBD program.

Want your own CBD product? Compare CBD can help you start your own CBD business, anywhere in the world! We work with over 20 partners globally to source the finest CBD products and ingredients.  We can help you from sourcing, to branding, to launch!

For more information - https://comparecbd.com/hempworx-cbd-oil


Mapeamento do Largo São João e Igreja Matriz de Laranjal Paulista em vídeo

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.

Vídeo: www.youtube.com/watch?v=ezw-fb6EPf8 (duração: 5 minutos)

O mapeamento do município de Laranjal Paulista no OpenStreetMap faz parte do meu projeto Atlas de Laranjal Paulista. Detalhes: www.igorel

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.

Vídeo: https://www.youtube.com/watch?v=ezw-fb6EPf8 (duração: 5 minutos)

O mapeamento do município de Laranjal Paulista no OpenStreetMap faz parte do meu projeto Atlas de Laranjal Paulista. Detalhes: http://www.igoreliezer.com/laranjal/w/index.php?title=Projeto:Mapa_digital


01-23(23)

01-23内容:华信路—花园路—七里河路—华龙路片区初步

01-23内容:华信路—花园路—七里河路—华龙路片区初步


Hempworx - Compare CBD Products

Hemp could be a plant that is a noteworthy supply of disarray for a few. while it's valid that a few types of hemp square measure sick gotten because of the substance cognizance adjusting drug, that could be a psychedelic particle, not the greater part of the types of Hemp contain the awareness changing medication.

Hemp oil picked up unmistakable quality with the wellbeing aware of

Hemp could be a plant that is a noteworthy supply of disarray for a few. while it's valid that a few types of hemp square measure sick gotten because of the substance cognizance adjusting drug, that could be a psychedelic particle, not the greater part of the types of Hemp contain the awareness changing medication.

Hemp oil picked up unmistakable quality with the wellbeing aware of the world. For quite a long time individuals utilized the oil until the point when it was expelled from the market since oil is produced using the seeds of the cannabis plant.

Uses-According to convictions, the plant contains the medicine for interminability. The Chinese additionally utilized hemp oil to treat Malaria, menstrual issues, and ripeness. More Info: https://comparecbd.com/hempworx-cbd-oil


Thank You for the Award

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'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 OpenSteetMap Community.

I can't express how

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'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 OpenSteetMap Community.

I can't express how thankful I am that I won the Greatness in Mapping Award. It is an honour to be recognised by such a great community. Greatness in Mapping Award 2018

I also want to thank Fingal County Council for introducing #MapLesotho because that's how I first knew about OpenSteetMap and it'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 DeBigC who dedicated his time to guide and advice me. I'm extremely grateful!


Developer wanted for CartoCSS

I recently got worried about CartoCSS project, which we use as a Mapnik configuration parser in OSM Carto. There'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 be not even basic support, like merging code or making the release.

If there's somebody ready to l

I recently got worried about CartoCSS project, which we use as a Mapnik configuration parser in OSM Carto. There'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 be not even basic support, like merging code or making the release.

If there'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 "share the keys" (or even pass the baton) in the project:

https://github.com/mapbox/carto/issues/495#issuecomment-412987738

Tuesday, 14. August 2018

OpenStreetMap User's Diaries

#My road trip to Milan

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.

The joy and anticipation of boarding a plane to Milan was out of this world but at the same time the anxiety of travellin

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.

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.

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't have a problem finding our way in the big city of Milan and all thanks to maps.me.

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. I was impressed by transport system in Milan where I noticed that public transport and cycling are encouraged and really working. public transport

cycling

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 architectural landmarks.

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. SOTM 2018 attendees

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.

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.

On the last day of the conference I had a 5 minute presentation about #MapLesotho 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. as we were moving towards the end of the ceremony speech were made and OSM awards,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.

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.


Continuity of the work on gender diversity in OSM by Geochicas - SOTM Milan 2018

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.

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

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.

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.

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.

These lines were:

  1. 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
  2. Form a group of women with a reserved chat called Geochicas, created in the conference with about 30 attendees
  3. Have a proactive communication effort in the OpenStreetMap LATAM networks to keep the debate on gender equity active
  4. Promote in the group of women peer-to-peer teaching of technical and theoretical topics
  5. Promote our continuous participation in data and free technologies events, and a systematic participation in the SOTMs.

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.

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's activities and achievements, and presented the results of [our survey on gender representation in OSM](https: //slides.com/geochicasosm/geochicas-sotm2018/). Alt text

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.

Alt text

A mixed assistance and of all countries opined around 3 premises: I will do; We should stop doing; We should start or continue.

Alt text Alt text

The ideas expressed can be summarized and grouped as follows:

I will:

  • I will give an active female role model in the community of labels
  • I will pay attention to the concerns of women in the community
  • I will promote the organization of community activities, with attention to a diverse participation, and take care of the conditions of safe access
  • I will get involved in local communities and invite women to join
  • I will participate more in debates about the community, I will listen and not judge
  • I will promote the development of easy-to-use tools to contribute to the map
  • I will be alert to violent tones and harassment in communication channels
  • I will have more reflection on the subject of privileges and inequity
  • I will inquire about COCs and be more sensitive to the issue of respectful treatment
  • Consider and take advantage of diverse abilities, in the modes of contribution to OSM

We should stop:

  • 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
  • To consider the essence of OSM as a technological project
  • To have a prejudice about the motivations for contributing
  • To have a limited vision of genders, and expand the focus to all genders
  • From supporting the foundation until a complaint system of harassment is complied with
  • Stereotyping people, groups, nationalities
  • To conceal or tolerate harassment, provocations, abuses and toxic modes, all forms of discrimination
  • To pretend that inequality and discrimination in OSM does not exist and is not a problem
  • To limit the concept of diversity to gender diversity, expand the focus

We should start to:

  • Listen with empathy and respect disagreements and differences in vision, interest, and values
  • Measure changes systematically, periodically, with surveys or other instruments
  • Improve the mechanisms for the integration of new people
  • Analyze the fine mechanisms of exclusion of marginalized groups towards debates, community, activities and OSM events. Have a constant search for integration
  • Have a financing council to know projects and proposals with a need of development, and be able to channel resources towards a greater diversity
  • 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
  • The board must have a specific work axis on diversity and clear objectives
  • Promote our allies
  • Have a more motivating perspective and also make visible the efforts and changes
  • Collaborate with allies and stakeholders with a clear stance in favor of diversity and equity
  • Develop safe spaces for women and other groups
  • Build a Code of Conduct, moderations, and an anonymous reporting system, and systems to identify micro-aggressions by the community
  • Expand the debate on the topic to share experience and co-create solutions
  • Support initiatives focused on women, such as #letgirlsmap, @OsmGirls, @geochicasosm, develop them at all scales
  • Have a formal work on the tagging system, with gender vision

(The complete list of comments and ideas written by participants to the brainstorming is transcribed in the mail list diversity-talk@openstreetmap.org)

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. 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. Alt text


Continuidad del trabajo sobre diversidad de género en OSM por Geochicas - SOTM Milán 2018

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.

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 regi

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.

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.

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.

Estas líneas fueron:

  1. 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
  2. Formar un grupo de mujeres con un chat reservado llamado Geochicas, creado en el mismo momento de la asamblea con unas 30 asistentes
  3. Tener un esfuerzo de comunicación proactivo en las redes de Openstreetmap LATAM para mantener activo el debate sobre equidad de género
  4. Promover en el grupo de mujeres la enseñanza de temas técnicos, el debate de nivel teórico
  5. Promover nuestra participación continua en eventos de datos y tecnologías libres y una participación sistemática en los SOTM.

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.

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 nuestra encuesta sobre representación de género en OSM.
Alt text

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.

Alt text

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.

Alt text Alt text

Las ideas expresadas se pueden agrupar y resumir así:

Haré:

  • Daré un modelo de rol femenino activo en la comunidad
  • Tendré atención a las preocupaciones de las mujeres de la comunidad
  • Impulsaré la organización de actividades comunitarias, con atención a una participación diversa, y cuidando de las condiciones de acceso seguro
  • Me involucraré en comunidades locales e invitaré a mujeres a unirse
  • Participaré más en debates sobre la comunidad, escucharé
  • Impulsaré el desarrollo de herramientas fáciles de uso para contribuir al mapa
  • Seré alerta hacia tonos violentos y acoso en canales de comunicación, tendré mayor reflexión sobre el tema de privilegios y de inequidad
  • Indagaré sobre COCs y seré más sensible a la cuestión del trato respetuoso
  • Considerar y aprovechar abilidades diversas, en los modos de contribución a OSM

Deberíamos dejar de:

  • Comunicar los resultados con un sistema de rankings, comprometernos más con la inclusión, valorizar habilidades distintas e centros de interes distintos
  • Considerar la esencia de OSM como un proyecto tecnológico
  • Tener prejuicio sobre las motivaciones por contribuir
  • Tener una visión limitada de los géneros, y ampliar el foco a todos los géneros
  • Apoyar a la fondación hasta que se cumpla con un sistema de denuncia del acoso
  • Estereotipar personas, grupos, nacionalidades
  • Encubrir o tolerar el acoso, las provocaciones, abusos y modos tóxicos, todas formas de discriminación
  • Pretender que la inequidad y discriminación en OSM no existe y no es un problema
  • Limitar el concepto de diversidad a la diversidad de género, ampliar el foco

Deberíamos empezar a:

  • Escuchar con empatía y respetar los desacuerdos y las diferencias de visión, interés y valores
  • Medir cambios sistematicamente, periodicamente, con encuestas
  • Mejorar los mecanismos de integración de nuevas personas
  • 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
  • Tener un consejo de financiamiento para conocer proyectos y propuestas con necesidad de desarrollo y poder canalizar recursos hacia una mayor diversidad
  • 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
  • El board debe de tener un eje de trabajo concreto sobre diversidad y objetivos claros
  • Promover nuestros aliados
  • Tener una perspectiva más motivadora y visibilizar también los esfuerzos y los cambios
  • Collaborar con aliados y grupos de interés con una postura clara a favor de la diversidad y equidad
  • Desarrollar espacios seguros para mujeres y otros grupos
  • Construir un Código de Conducta, moderaciones, y un sistema de denuncia anónimo, sistemas de identificación de microagresiones por la comunidad
  • Ampliar el debate sobre el tema para compartir experiencia y co-crear soluciones
  • Apoyar las iniciativas enfocadas a mujeres, como #letgirlsmap, @OsmGirls, @geochicasosm, desarrollarlas en todas las escalas
  • Tener un trabajo formal sobre el sistema de etiquetas con visión de género

(La lista completa de comentarios e ideas escritas por los participantes al taller están retranscritas en la lista de mail diversity-talk@openstreetmap.org).

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. 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. Alt text


Ponte Morandi: why fiddling with the map?

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. I wonder why there's need to edit further the same object to add little value to the map. People in Genoa already made the necessary changes after watching local news. I deleted the bridge because it will be quite surely removed altogether, wh

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. I wonder why there's need to edit further the same object to add little value to the map. People in Genoa already made the necessary changes after watching local news. I deleted the bridge because it will be quite surely removed altogether, what is the point of showing a "collapsed" bridge when the actual bridge segment is in ruins in the waterway below?

When the news will fade, we local mappers will once more take care of the local situation. (which will reflect on the traffic of North-West Italy, but that's another problem).


La verifica dei toponimi di Vittorio Emanuele III In Calabria

Nell'ambito del progetto #cittasenzamemoria è stata aggiornata la verifica dei toponimi dedicati a Vittorio Emanuele III in Calabria.

I dati provengono dalla mappa di OpenStreetMap finalizzata a creare una cartografia a contenuto libero del mondo. Le informazioni della mappa sono liberamente accessibili su licenza ODbL ed aggiornate ogni giorno. Per facilitare la consultazi

Nell'ambito del progetto #cittasenzamemoria è stata aggiornata la verifica dei toponimi dedicati a Vittorio Emanuele III in Calabria.

Calabria

I dati provengono dalla mappa di OpenStreetMap finalizzata a creare una cartografia a contenuto libero del mondo. Le informazioni della mappa sono liberamente accessibili su licenza ODbL ed aggiornate ogni giorno. Per facilitare la consultazione i toponimi sono anche consultabili sulla mappa on line dedicata. In totale sono stati individuati 74 odonimi qui di seguito riportati:

id toponimo Comune

1 Corso Vittorio Emanuele III Acquaformosa
2 Via Vittorio Emanuele III Acquappesa
3 Piazza Vittorio Emanuele III Acri
4 Corso Vittorio Emanuele III Albidona
5 Via Vittorio Emanuele III Alessandria del Carretto
6 Via Vittorio Emanuele III Cerchiara di Calabria
7 Via Vittorio Emanuele III Corigliano Calabria
8 Via Vittorio Emanuele III Francavilla Marittima
9 Via Vittorio Emanuele III Lungro
10 Piazza Vittorio Emanuele III Nocara
11 Via Vittorio Emanuele III Panettieri
12 Corso Vittorio Emanuele III Pedivigliano
13 Via Vittorio Emanuele III Rende
14 Via Vittorio Emanuele III San Lorenzo Bellizzi
15 Via Vittorio Emanuele III San Marco Argentano
16 Via Vittorio Emanuele III San Pietro in Guarano
17 Via Vittorio Emanuele III San Vincenzo La Costa
18 Corso Vittorio Emanuele III Trebisacce
19 Corso Vittorio Emanuele III Argusto
20 Via Vittorio Emanuele III Badolato
21 Via Vittorio Emanuele III Carlopoli
22 Via Vittorio Emanuele III di Castagna Carlopoli
23 Salita Vittorio Emanuele III Cropani
24 Corso Vittorio Emanuele III Gimigliano
25 Via Vittorio Emanuele III Magisano
26 Via Vittorio Emanuele III in San Pietro Magisano
27 Piazza Vittorio Emanuele III Maida
28 Via Vittorio Emanuele III Olivadi
29 Via Vittorio Emanuele III Palermiti
30 Piazza Vittorio Emanuele III Palermiti
31 Corso Vittorio Emanuele III Petrizzi
32 Salita Vittorio Emanuele III Petronà
33 Corso Vittorio Emanuele III San Floro
34 Via Vittorio Emanuele III Sant' Andrea Apostolo dello Ionio
35 Piazza Vittorio Emanuele III Serrastretta
36 Via Vittorio Emanuele III Settingiano
37 Via Vittorio Emanuele III Torre di Ruggiero
38 Via Vittorio Emanuele III Antonimina
39 Via Vittorio Emanuele III Bovalino
40 Via Vittorio Emanuele III Calanna
41 Piazza Vittorio Emanuele III Campo Calabro
42 Via Vittorio Emanuele III Cardeto
43 Via Vittorio Emanuele III Ciminà
44 Via Vittorio Emanuele III Cittanova
45 Piazza Vittorio Emanuele III Cosoleto
46 Via Vittorio Emanuele III Gioia Tauro
47 Via Vittorio Emanuele III Gioiosa Ionica
48 Via Vittorio Emanuele III Grotteria
49 Via Vittorio Emanuele III Melicuccà
50 Corso Vittorio Emanuele III Reggio Calabria
51 Via Vittorio Emanuele III Rizziconi
52 Via Vittorio Emanuele III San Lorenzo
53 Via Vittorio Emanuele III San Procopio
54 Via Vittorio Emanuele III Sant'Eufemia d'Aspromonte
55 Via Vittorio Emanuele III Cotronei
56 Corso Vittorio Emanuele III Isola di Capo Rizzuto
57 Via Vittorio Emanuele III Savelli
58 Corso Vittorio Emanuele III Arena
59 Piazza Vittorio Emanuele III Dasà
60 Corso Vittorio Emanuele III Dinami
61 Corso Vittorio Emanuele III Fabrizia
62 Via Vittorio Emanuele III Francica
63 Via Vittorio Emanuele III Mileto
64 Via Vittorio Emanuele III Nardidipace
65 Corso Vittorio Emanuele III Parghelia
66 Via Vittorio Emanuele III San Calogero
67 Via Vittorio Emanuele III Sorianello
68 Via Vittorio Emanuele III Villapiana
69 Via Vittorio Emanuele III Serra San Bruno
70 Corso Vittorio Emanuele III Vibo Valentia
71 Via Vittorio Emanuele III Monasterace
72 Corso Vittorio Emanuele III Mongiana
73 Piazza Vittorio Emanuele III Molochio
74 Via Vittorio Emanuele III Brancaleone

Nel dettaglio i singoli odonimi sono anche visualizzabili sulla pagina wiki del progetto #cittasenzamemoria relativa alla Calabria.

  • Metodo di lavoro

Il metodo di lavoro è consistito nel verificare i dati provenienti Censimento ISTAT 2011. 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 Italy Names per Telegram 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 locale comunità di utenti OpenStreetmap. La Calabria è risultata la maggiore regione italiana con ben 74 toponimi dedicati a Vittorio Emanuele III. 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.

  • Considerazioni finali

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.

Bubix


Information on Spam

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

  • This diary entry is/contains spam
  • This diary entry is obscene/offensive
  • This diary entry contains a th

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

  • This diary entry is/contains spam
  • This diary entry is obscene/offensive
  • This diary entry contains a threat
  • Other

This diary post is about the first option (non-email SPAM) (you-tube (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 Report option in place (I joined StopForumSpam in 2009 and am a Mod on that site, so you will have to accept a strong anti-spam obsession in this post).

You are never alone with an IP

pack of Strand cigarettes
(The subhead is inspired by the advertising for Strand cigarettes)

Telegrams became ubiquitous in the 19th Century & 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.

Our current problems with SPAM were probably initiated by the success of the Netscape Navigator browser, though that statement will take a few twists & turns to justify. Netscape (released 1994) was written by some of the same folks that had written Mosaic (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 & 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.

Sir Tim Berners-Lee wrote the code for all the initial components for a fully-functioning World Wide Web (WWW) in 1989 and gave it to the world for free (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 sepia Dorothy open the door and step into a Technicolour Wizard of Oz world — moving from text-only browsers to graphical browsers like Mosaic or Netscape was utterly compelling.

sepia dorothy

You Cannot Beat Free

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 & later (it is still there today, in spite of the anti-trust actions taken by the USA government & EU against M$) & promoted MSIE hard. They were successful, and Netscape is now dead, although it's code was made open-source & became Mozilla Firefox.

So, we now have the dawn of a new millennium, the WWW is spreading and, if you know someone's IP, then you can hack them with ease (the Windows NetBEUI local-network protocol had zero protections against hacking & gave root access to the disk from remote locations; it was a nightmare). Likewise, Bulletin Boards have become Internet Forums & 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 & blog-post spam at this moment. You know, like these Diary posts.

So What is Spam?

I've already talked about SPAM's mother (the WWW & culture of ‘free’) but We Need to Talk About Google (the father) to get to grips with what on earth is going on.

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 other 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 & blogs that would allow them to place posts with links. And lo! Spamming was born!

There are two types of spammer:–

  1. Stupid Spammers
  2. Every Other Spammer

Stupid Spammers

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 Good Idea to promote their business/site/hobby/blog by putting links to it into random forums,

There used to be lots & lots of forums or blogs that allowed anonymous logins, but not many today. So, they signup to OSM & 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.

Every Other Spammer

Just like all things, 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:–

a. Using the Profile to Spam
The Diary post and/or comment is only to get the Search Engine to visit the Profile page. As with all spammers, it shows:–
 
Joined: Today
Edits: 0
Traces: 0
 
But, somewhere on that Profile is a link.
 
b. The Patient Spammer
(these are few & far between - it also depends on the presence of an Edit function)
 
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.
 
c. The 2-Link Spammer
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.

This whole thing can be continued indefinitely.

Please help by logging in & reporting spammy posts and/or comments.