Users' Diaries

Recent diary entries

Posted by prispe on 8 September 2023 in English.

On the 6th of September 2023, we the members of the committee had a review on the volume of applications submitted by the applicants for SotM Africa which is slated to be held in Cameroun this year 2923. Letters were sent to the applicants whose application was not successful.

On the 8th, we concluded were 15 of the applicants made it to the top. Letters will be sent to them by the 9th of September, 2023.

Make a Donation to UMBRAOSM Union of Brazilian OpenstreetMap Mappers and keep the site in AR and your projects!

https://www.umbraosm.com.br/doacao.html

These are the data to send a Pix to the Neon account!

To send by keys: Email: umbraosm@gmail.com

Name: Roberto Borges De Sousa

See full entry

Herausforderung: Kartografiere dein Wohnklo!

Dies ist eine Aufforderung an euch alle das Gebäude in dem ihr wohnt in OpenStreetMap ausführlich zu kartografieren, also tragt einfach alle Informationen ein, die ihr über das Gebäude wisst.

Zwei Überlegungen vorab, bevor ich erkläre, wie das am Besten geht:

  1. Es ist wahrscheinlich, dass ihr nicht wollt, dass andere wissen wo ihr wohnt, aber Änderungen in #OpenStreetMap werden natürlich mit dem Account, mit dem sie erstellt werden verknüpft und das ist öffentlich einsehbar. Wenn ihr also nicht wollt, dass jeder herausfinden kann wo ihr wohnt, dann empfehle ich, dass ihr einen OSM-Account anlegt, der nicht euer Standard-Nickname ist. Wenn ihr also normalerweise @flottebiene23 heißt, dann nennt euch einfach Brummer42 oder sogar KcA4TbGsu ist ja auch ein schöner Benutzername. Nur könnt ihr dann halt mit eurer Leistung auch nicht angeben.
  2. Zweck der Aktion ist unter anderem ein paar Leute mit dem OSM-Fieber zu “infizieren”. Also dazu zu bringen, dass sie auch künftig das ein oder andere zur Datenbank beitragen. Schon klar, dass da nur 1% hängen bleiben oder so, aber hey, 1%. Aber es ist natürlich auch schön, wenn einfach ein paar Leute ihr Wohn-Gebäude in OSM mit Daten anreichern, das ist ja auch ein Wert an sich.

Die Idee dazu kam mir unter anderem als ich vergangenes Jahr auf dem #34C3 mit @SWW13 zusammensaß und es mir sagte sein Wohngebäude sei nur so marginal in OSM drin. Daraufhin haben wir den Eintrag ausführlich gepimpt und auch die kleine Sitzbank vorm Haus und den Parkplatz gegenüber und den Glascontainer in Sichtweite noch eingetragen.

Dieser Artikel entstand ursprünglich auf diaspora*, aber ich habe ihn noch auf GitHub kopiert, auf OSM.org und auf mein Wordpress Blog

Also, Bock drauf? Dann los!

Schritt 1: Konto erstellen

See full entry

O Instituto AddressForAll em parceria com a Esri começa a liberar pacotes de dados cedidos por centenas de prefeituras do Brasil e outros países. São mapas de eixos de vias, lotes, edificações, divisas de bairros, pontos de endereços e quadras, que podem ser carregados no QGIS e JOSM para melhorar o OpenStreetMap.

Os dados serão disponibilizados em licença CC0 e CC-BY com permissão para o OSM (as licenças estará no box de metadados de cada pacote de dados) . A primeira cidade liberada é Cachoeiro do Itapemirim/ES, Brasil. Confira post no blog do Instituto.

Post blog AddressForAll: https://blog.addressforall.org/e66bce20076b

Comentários, sugestões e questões para orientar as próximas liberações também são bem-vindos.

(postagem do Instituto AddressForAll)

Location: Centro, Cachoeiro de Itapemirim, Espírito Santo, Região Sudeste, Brasil

Натрапив на дефект у побудові шосейних вело маршрутів в Komoot (на Graphhopper), але це може повторюватись і на інших навігаторах (OSMAnd ітд)

При побудові шосейних треків (коли треба виключно асфальтні дороги), він відмовляється в деяких місцях вести по шосе, а обходить цю ділянку по будь-яких дорогах поруч, включаючи грунтовки і тропи. А якщо примусово прокласти там трек - пише "вам треба буде спішуватись з вело" і збільшує загальний час маршруту.

Проблема виявилась у неповному заповненні тегів якості доріг з порушенням порядку заповнення.

Зазвичай, якщо теги дороги не заповнені, але вказаний її ранг ('trunk', 'primary', 'secondary'), то маршрутизатори вважають її асфальтом.

І ось тут хтось ставить тег якості поверхні smoothness, забуваючи про surface. Коли дорога гарна, хоча б intermediate, проблем ніяких. Але якщо 'smoothness = bad', то маршрутизатор вирішить, що там грунтовка. І навіть ранг дороги 'primary' вже не допоможе, і відправить нашого шосера блукати по реальним грунтовкам

І звісно, це наче проблема розробників, але пошук через Overpass показав, що в Европі дуже мало ділянок з подібною проблемою, лічені випадки.

Можна просто виправити поточні проблемні ділянки в Україні, але постане інша задача. У нас дуже багато шосе не мають тегів типу поверхні (хоча навіть зі супутника видно, що то asphalt). І лише питання часу, коли хтось з маперів поставить знову тег якості поверхні, забувши вказати її тип, чим зробить цю дорогу "непроїздною" для шосейного велосипеда.

І доводиться просто час від часу робити пошук через Overpass

When I started getting involved in mapping on OSM around July 2021, I asked myself: “But why hasn’t anyone made a guide to help me map this country?” and indeed, there was no specific guide to contribute on North Korea!

North Korea Mapping Guide

Beginning

After learning and integrating all the basic OSM tags (including highway=*, building=*, natural=*, landuse=* etc.) and mapping some small towns of the country, I thought about creating a personal page of recurring tags for easy retrieval.

Then the idea came to me to make a thematic page on the contribution specific to this country.

Access to the terrain in North Korea is complicated, and a good understanding of satellite imagery is essential, so a guide to the subject becomes all the more relevant. So I decided to create one!

See full entry

Location: 39.008, 125.752

Revised Script for usage in macOS 12+ with zsh:

#!/bin/zsh
echo "Download"
wget -t0 -c "http://download.geofabrik.de/europe/andorra-latest.osm.pbf"
wget -t0 -c "http://download.geofabrik.de/europe/austria-latest.osm.pbf"
wget -t0 -c "http://download.geofabrik.de/europe/belgium-latest.osm.pbf"
wget -t0 -c "http://download.geofabrik.de/africa/canary-islands-latest.osm.pbf"
wget -t0 -c "http://download.geofabrik.de/europe/czech-republic-latest.osm.pbf"
wget -t0 -c "http://download.geofabrik.de/europe/denmark-latest.osm.pbf"

echo "Convert"
./osmconvert --drop-version andorra-latest.osm.pbf -o=andorra-latest.o5m
rm -rvf andorra-latest.osm.pbf
./osmconvert andorra-latest.o5m -o=merged.o5m
rm -rvf andorra-latest.o5m

for FILE in ./*.osm.pbf; do ./osmconvert --drop-version $FILE -o=$(basename $FILE .osm.pbf).o5m; ./osmconvert $(basename $FILE .osm.pbf).o5m merged.o5m -o=merged_cache.o5m; rm -rvf $(basename $FILE .osm.pbf).o5m; mv -v merged_cache.o5m merged.o5m; done

echo "splitter" 
## latest splitter Version r653 used
java -Xmx5G -jar splitter-r653/splitter.jar --output-dir=tiles --max-nodes=1200000 merged.o5m

echo "mkgmap"
## latest mkgmap Version r4910 used
## template 2022pn.typ used, use what you like :)
java -Xmx5G -jar mkgmap-r4910/mkgmap.jar --country-name=OSMMap --family-name="OSM map" --product-version=1 --bounds=bounds-latest --dem-interpolation=auto --make-poi-index --poi-address --unicode --index --split-name-index --gmapsupp --report-routing-islands -c mkgmap-r4910/examples/sample.cfg -c tiles/template.args 2022pn.typ --style-file=../ --check-styles --route --net --gmapi --add-boundary-nodes-at-admin-boundaries

echo "final clean up"
rm -rvf *latest.o5m
rm merged.o5m
cd tiles
rm -rvf *.osm.pbf
cd ..
rm -rvf 6*.img 
rm -rvf ovm_6*.img

echo "The End"

Tree mapping is a task that is better done in person than using aerial imagery, unless it is a tree row. The reasoning being that node placement of natural=tree is more precise than looking from above, since more often than not the imagery is not that clear.

Trees tell a story

When looking at this area it is fascinating how one can make out man made structures relative to the placement of trees.

trees and tree rows as nodes and ways in JOSM

Further once adding the leaf_cycle and leaf_type one can create shade maps that could be practical during heat waves like at mapasdesombra.org or if jveuxdusoleil.fr extended its algorithm to include tree details as well.

One can add the tree’s height and diameter with a check date to create a timeline of the tree’s lifespan, though also add more potential data points in ecological terms.

Or one can add the genus and/or species to ease the search for foragers like mundraub does with their overlay map.

Tree specification

See full entry

Posted by qeef on 3 September 2023 in English.

The damn deploy repository of the Divide and map. Now. has been refactored. And that’s a great opportunity for another round of load testing.

This is the third round of load testing, see the first and the second one if you are interested.

The load testing is a bit different from the last time. I performed load testing of new, freshly deployed damn project instance on $6/month VPS with 1 GB RAM, single 2.5 GHz vCPU, and 25 GB SSD. (The changes from the last time are that there is no more load testing of the “production” server, the price increased by $1/month, and shared_buffers is now 256 MB instead of 409 MB.)

The preparation for load testing on the server’s side, when the damn project is deployed, is just to run

docker-compose -f damn-deploy/gen.yml run --rm prepareloadtest

to create 1000 test users and 10 (load) testing areas in the database. For each run of load testing, the database has been deleted and created again with

systemctl stop damn-http.service
reboot
docker volume rm damn-deploy_damndb-volume
systemctl start damn.target
docker-compose -f damn-deploy/gen.yml run --rm prepareloadtest

commands. For each run of load testing, log the server’s utilization with

sar -o load-test-100 -A 15 $((4 * 61)) 1>/dev/null 2>&1

Then, from that file, you can generate data series and plot the graphs with

./get-info.sh 100
gnuplot plot1.pl
gnuplot plot2.pl

where the content of the corresponding files is

get-info.sh:

See full entry

Como presidenta do Instituto Virtual para o Desenvolvimento Sustentável - IVIDES.org, idealizei, organizei e ministrei o curso de “Capacitação em mapeamento com OpenStreetMap”, para dar início às atividades do Capítulo YouthMappers UFRJ, Rio de Janeiro, Brasil, do qual, sou também presidenta e conto com a colaboração do Dr. Manoel Fernandes, professor mentor; do Dr. Paulo Menezes, professor mentor colaborador, todos nós do Lab. GeoCart-UFRJ; e ainda, com a fundamental colaboração de alunos e alunas do nosso laboratório e de unidades vizinhas do Centro de Ciências Matemáticas e da Natureza, especificamente, da Geologia; da Meteorologia e da Ciência da Computação e Núcleo de Computação Eletrônica - NCE. Poderia desfiar um rosário de instituições nacionais, principalmente do Rio de Janeiro, que fazem parte do nosso grupo de pesquisa, mas estou aqui para falar do nosso curso!

Apresentação do curso

O curso foi ministrado entre os dias 20 de julho e 24 de agosto de 2023 e transformou-se em um curso de fluxo contínuo, uma vez que houve interesse de demais pessoas, que conheceram a iniciativa após o início de sua realização. Assim, aos participantes que concluirem com sucesso - vide as condições presentes no portal https://ivides.org/curso-osm-2023, serão emitidos certificados ao final das fases de seis meses. Os envios de resultados são realizados por esta mesma plataforma e os certificados serão enviados por e-mail cadastrado no curso (vide no mesmo local, o portal web, as informações sobre a Secretaria).

See full entry

Posted by scruss on 3 September 2023 in English.

… unless you want a greatbighuge label inexplicably hovering over the map at z=16.

Looking over this fine city of Toronto, I saw a couple of brown labels for places that are sort-of not real. Exporting and grepping local exports showed me they were landuse ways with a name value set.

I’m sure there are plenty of good examples where a landuse area would have a name. In these cases, though:

  • one was the name of a city/developer study from roughly five years ago that has disappeared from the record since then. Will it become a neighbourhood name? Who knows, but that’s for the future and not for us to force. (fun fact: it’s apparently the densest concentration of office workers in the city. Less fun but very Toronto fact: there is no dedicated transit there. I had a job there ~2006–2008 and new transit was planned, but then the trainwreck formerly known as Mayor Rob Ford happened so it didn’t.)

  • one was a drive-by tagging error by an out-of-band specialist. I really think they meant it for a bus stop.

Aligned with my personal policy of “Only kvetch after fixing”, they’re gone and our z=16 will be so much less jarring. Thank me later.

Posted by pnorman on 1 September 2023 in English.

The Standard Tile Layer has a lot of traffic. On August 1st, a typical day, it had 2.8 billion requests served by Fastly, about 32 thousand a second. The challenges of scaling to this size are documented elsewhere, and we handle the traffic reliably, but something we don’t often talk about is the logging. In some cases, you could log a random sample of requests but that comes with downsides like obscuring low frequency events, and preventing some kinds of log analysis. Critically, we publish data that depends on logging all requests.

We query our logs with Athena, a hosted version of Presto, a SQL engine that, among features, can query files on an object store like S3. Automated queries are run with tilelog, which publishes files daily to generate published files on usage of the standard tile layer.

As you might imagine, 2.8 billion requests is a lot of log data. Fastly offers a number of logging options, and we publish compressed CSV logs to Amazon S3. These logs are large, and suffer a few problems for long-term use because they:

  1. contain personal information like request details and IPs, that, although essential for running the service, cannot be retained forever;
  2. contain invalid requests, making analysis more difficult;
  3. are large, being 136 GB/day; and
  4. become slow to query, being compressed gzip files with the only indexing being the date and hour of the request, which is part of the file path.

To solve these problems we reformat, filter, and aggregate logs which lets us delete old logs. We’ve done the first two for some time, and are now doing the third.

See full entry

Posted by Heather Leson on 31 August 2023 in English.

How do we better organize to support the Humanitarian OpenStreetMap Team organization, staff, membership, and community? We have been on a journey to open up and consider what is the best way forward for HOT’s Governance. Now that we have the HOT Living Strategy, we have more incentive to imagine how we might evolve. We are taking stock of our governance and investigating how we might be able to encourage more people to engage in the governance of HOT.

The HOT Governance Working Group (GWG) started the process of research and engagement with the HOT membership in January 2023. We’ve documented this process in the GWG meeting minutes. Together we designed a terms of reference to hire support to help us research some initial bylaw adjustments and wider organizational needs and structures.

Our first big research is exploring how we govern with the board and to better support the membership chair. There will be future steps and research to consider the role of the membership and how we collaborate with the Open Mapping Hubs.

The board and membership asked us to consider the following topics: the possibility of appointed board members, board member stipends, and membership chair term. See the current HOT bylaws

Why the proposed changes

The HOT voting members have a wide range of skills, and have brought much insight and change to the organization. Currently, HOT’s board is elected from and by the voting membership. Over the past years, HOT board and organization have identified gaps in key expertise for the board, including legal, finance and large-scale fundraising. This has been documented in various OSM diary posts, the HOT board election discussions, and the Board and GWG meeting minutes.

See full entry

Location: Kemptville, North Grenville, Leeds and Grenville Counties, Eastern Ontario, Ontario, K0G 1J0, Canada

今天把好多原来是一整块的小区乡村分割然后补名字。晚上又试着给了几个小区画建筑…… 要开学了,以后可能就没有这样的机会画这么多了……唉 啊对 还有街道分界线问题……有空亲自去东边看看吧

Location: 王庙镇, 鱼台县, 济宁市, 山东省, 中国