Hi guys!

Quick midterm update from me! Just as a little refresher, my name is Anqi and I’ve been working on the Transliteration of Search Results project this summer.

Time has really flown by and we are at the halfway point! Here I hope to give a summary of the work that’s been done so far, as well as what I hope to accomplish during the next part of the summer! We want to be able to return the transliterated name as a field during search results, with a proof of concept shown here! We can see in this proof of concept that the results are as expected, with the addition of one transliterated name field.

{
"place_id":100067,
"licence":"Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org/copyright",
"osm_type":"way",
"osm_id":1307932969,
"place_rank":30,
"category":"amenity",
"type":"school",
"importance":-0.004452559995167061,
"addresstype":"amenity",
"name":"丹东市第六中学",
"display_name":"丹东市第六中学, 七纬路, 站前街道, 丹东市, 振兴区, 118000, 中国",
"transliterated_name":"Dan Dong Shi Di Liu Zhong Xue, Qi Wei Lu, Zhan Qian Jie Dao, Dan Dong Shi, Zhen Xing Qu, 118000, Zhong Guo",
"bbox":[124.3804784,40.1271951,124.3830593,40.1292045],
"geometry":{
"type": "Point",
"coordinates": [124.38176886493923, 40.12819985]
},

The general flow can be visualized as below.

… See full entry

Realizadas pequenas edições como número de casas, criação de edifício em vila sônia e local de interesse mercado dia também em vila sônia.

RETEX: My Urban Recycling Trekking

To be continued, maybe:

• diary entry (upcoming): choosing tags for this trekking
• diary entry (upcoming): existential questions about my encounter with Panoramax

Context

Since April 2025, I’ve been discovering OSM and trying to contribute wherever I can. Needless to say, I’m learning something new every day about OSM mapping (thanks to the Wiki, forum, and fellow contributors).

While exploring my neighborhood, I added a voluntary drop-off point (for recyclable — though not always — waste) to OSM, located 800m from my home. I then discovered that the local intermunicipal authority has an app listing a large portion of the collection points. I wondered whether it was legally and technically feasible to retrieve those, and whether it would align with the OSM ethos.

The forum quickly (and kindly) set me straight (as I said, after only 2 months with OSM, I’m learning a lot every day):

• Extracting data from a website’s database is obviously illegal unless there’s an explicit license that allows it.
• Even if there were a friendly license (which is not the case here), it would still need to be ODbL-compatible to import the data into OSM.

This led me to pursue two parallel paths:

1. Finding a sustainable solution via an open data source, which means:

   • Trying to convince the intermunicipality to publish its data, ideally on www.data.gouv.fr
   • Convincing them to make this publication sustainable (i.e., generate an export every time there are updates)
   • Assessing how, in theory, this data could be used (completeness, attribute matching, duplicate detection, handling conflicts between open data and on-the-ground data — which can either be better or simply incorrectly entered)
   • Finding out how and by whom the data could be imported
   • Seeing if all of this could happen before 2035

2. Starting manual mapping myself through field visits (the foundation of OSM’s truth)

… See full entry

RETEX : mon trekking urbain recyclage

à suivre peut-être :

• entrée de journal(à venir) : les choix de tag pour ce trekking
• entrée de journal (à venir) : Questions existentielles sur ma rencontre avec panoramax

Le contexte

Depuis avril 2025, je découvre OSM et cherche à contribuer sur ce que je peux. Autant dire que j’en apprends tous les jours sur le mapping OSM (merci WIKI, forum et autres contributeurs).

En m’intéressant au voisinage, j’ai ajouté à OSM un point d’apport volontaire (collecte de déchets recyclables - pas toujours -) à 800m de chez moi. J’ai alors découvert que l’intercommunalité locale avait une application recensant une partie importante des points de collecte et me suis demandé s’il était envisageable légalement et techniquement de les récupérer, puis si c’était conforme à l’esprit OSM.

Le forum m’a rapidement (et gentiment) recadré (quand je vous dit qu’avec 2 mois d’OSM derrière moi, j’en apprends plein tous les jours) :

• récupérer des données d’une base de données via son site Web est bien évidemment illégal si aucune mention explicite de license ad hoc n’est faite
• même si une license sympathique est exprimée (ce qui n’est pas le cas ici), encore faut-il qu’elle soit compatible avec ODBL pour l’insérer dans OSM.

Ce qui m’a conduit à deux axes d’action parallèles :

… See full entry

As you might know, we’re having OpenStreetMap Awards this year! Finally, after many skipped years, we will have the honour and the joy to recognize people and teams who have made an impact on OSM, whether it’s by mapping, writing, or coding!

The process is open, and the same as the last time: first we gather all the nominees we can think of, then some groups of notable OSM members will choose a few from those who feel to be the most notable, and after that — an open community voting to choose one for each category. And the categories are:

• Core Systems Award — for building or maintaining an core project.
• Innovation Award — for making something new.
• Influential Writing Award — for blog posts, tutorials and documentation.
• Greatness in Mapping Award — for tireless mapping!
• Expanding the Community Award — for finding us more members.
• Team Achievement Award — awarded to companies and groups.
• Ulf Möller Memorial Award — like a lifetime archievement award for individuals.

Note that only achievements made or announced in 2024 or before April 1st, 2025 are eligible.

And right now, I need you help. The deadline for submitting nominees is looming, and we’ve got too few. Each category needs at least twenty to make sense, and for some, we got like two.

This needs some archive work. Like, open WeeklyOSM or big community discussions (before April 1st), and add people, projects, and teams you think made the OSM in general slightly better.

And submit them to https://awards.openstreetmap.org/

(Yes, we’ve got the official domain, thanks to Grant!)

이 도로가 계속 차로 수가 변경되서 같은 이름 다른 차로 수의 도로를 차로 수가 바뀔 때마다 끊어서 따로 새로 추가하고 있습니다. 도움 부탁드립니다.

도로 링크 : osm.org/way/392677769#map=16/35.63247/129.43854&layers=N osm.org/way/1416020854#map=17/35.624268/129.442173&layers=N osm.org/way/1416020853 (산하중앙3로, 울산광역시 북구)

※일단은 정자동 등 제외하고 강동산하지구 부근(푸르지오1차/2차, 힐스테이트, kcc 등 아파트 모여있는 개발계획구역 쪽)만 편집 중입니다. 혹시나 정자동 쪽도 도움 주실 수 있으면 부탁드립니다.

… See full entry

July 20, 2025 - After 17 months, I have reviewed every road in the NFSR network for the Siuslaw National Forest. Below is a summary of what was involved and the process I used.

Foundational elements

The foundational elements of this project are two public domain road datasets, the NFSR data from the United States Forest Service, and the OR-Trans dataset from the state of Oregon. NFSR is the reference for road numbers, names given to roads by the USFS, road surfaces, and geometry to a certain degree. The OR-Trans data is a reference for primary road names, geometry verification, and the tag formatting of USFS roads. I was able to use additional GIS from counties to verify geometries and primary road names.

Project management

QGIS was utilized as a way to manage the entire project. I used conditional styles on manually added attributes to break the 1,977 roads from the NFSR data into workable chunks, and to keep track of what I had done. Those workable chunks were exported as KMLs to use as a reference when working in iD.

Edits on OSM

I elected to use iD for this project to force myself to manually review everything I was doing, and to remove the possibility of an accusation of a careless import.

The NFSR data contains good geometry for the most part, but there are quite a few errors that are very significant. The NFSR data also contains several discrepancies from reality, such as roads being marked as closed and not open for use, despite the roads not being gated and definitely being actively used. Blanket replacing the geometry and tags in OSM without manual review would worsen the quality of OSM data.

This was also a good opportunity to do some TIGER cleanup and resolve road/water crossing issues. Unfortunately, with the nature of the crossing issues, resolving one can lead to getting flags for multiple others along the road or waterway, which can make it appear that you are creating these issues even though they were already present.

Tag formatting

… See full entry

Północno-wschodnia Polska (Kurpie) Potrzebują pomocy!

Na terenie Kurpii (Łyse, Myszyniec, Kadzidło, Ostrołeka) brakuje wielu kluczowych elementów, aktualnych informacji, i zwyczajnego landuse’u.

Kurpie zasługują na dobrą jakość map, lecz ja sam, nie poradzę sobie z tym dosyć sporym regionem.

Apeluje o pomoc i wspólne działanie w tworzeniu dobrej mapy Kurpii!

Zapraszam wszystkich do wspólnego mapowania tego pięknego, ciekawego i historycznego regionu Polski.

Zachęcę po Kurpiowsku :

Dawajta, róbta to razem!

Καλησπέρα σε όλους και όλες,

Σας προσκαλώ στην συνάντηση της ελληνικής κοινότητας του OpenStreetMap στην Αθήνα. Ευκαιρία να μαζευτούμε οι χαρτογράφοι της Ελλάδας και να πιούμε έναν δροσιστικό καφέ μες την ζέστη του καλοκαιριού, ώστε να γνωριστούμε καλύτερα και να συζητήσουμε διάφορα σχετικά με το OSM. Και μετά να κάνουμε χαρτογράφηση στη γύρω περιοχή :slight_smile:

🗓️Ημερομηνία και ώρα: Σάββατο 26 Ιουλίου, 15:00
🔗Τοποθεσία: Piu Verde, Άλσος Παπάγου

Το Piu Verde εκτός από καφέ, προσφέρει και φαγητό, για όποιον θέλει μιας και θα είναι κοντά μεσημέρι.
Όσοι επιθυμείτε να παρευρεθείτε, συμπληρώστε το όνομα σας εδώ.

🗓️🔗Σύνδεσμος συνάντησης στο OpenStreetMap Calendar: https://osmcal.org/event/3920/

… See full entry

In 2020, I was presented with an opportunity to participate in the Humanitarian OpenStreetMap Team’s Data Quality Internship, https://www.hotosm.org/jobs/data-quality-internship/,a twelve-week program designed to facilitate deep engagement within the Humanitarian OpenStreetMap Team and its community while acquiring transferable geospatial skills.

Commencing on August 3rd, I undertook a three-month internship that concentrated on Geospatial Data Quality within the Humanitarian OpenStreetMap Team. The primary objective of this internship was to prepare interns to evaluate data quality, execute mapping and validation tasks, and provide constructive feedback to mappers engaged in HOT’s remote mapping initiatives, which included various activations. This experience necessitated the acquisition and application of both novel and established OpenStreetMap Quality Assurance tools to enhance the quality of data within the OpenStreetMap framework.

-Data Quality Assurance with QGIS

1. Downloading OpenStreetMap data into QGIS

https://youtu.be/Mvh5l0PiOiE

1. Editing OpenStreetMap data in QGIS

2. Using Map Composer

-Mapping and validation on Tasks e.g #8294 and #9194

-Introduction to Overpass Turbo and Umap: filter OSM data, extract/export data

-Improving data quality with Overpass and creating simple webmaps using Umap

• The graphic interface and tools for creating a basic map layout through the manipulation of vector data

-Quality Assurance Tools such as OSMCha, OSM Inspector, Keep Right and Osmose

-The use of Map Roulette and Map Paint Styles

• JOSM training i.e mapping and validation using JOSM, task #9055

우선, 저는 한국어를 못해서 자동 번역입니다. 저는 러시아 출신이지만 지난 3년 동안 서울에 살고 있어서 한국어로 글을 쓰고 싶습니다. 저는 1년 동안 OSM을 사용해 왔지만, 일주일 전에 지도 제작에 손을 대기로 했습니다. 제 첫 프로젝트는 «석정리». 세계문화유산화순고인돌군에서 멀지 않은 외딴 마을이에요. 어디서부터 시작해야 할지 몰라서 그냥 무작위로 이 마을을 선택했습니다.

제가 알기로는 한국의 OSM 커뮤니티는 그다지 활발하지 않은 것 같습니다. 하지만 한국에서 3년을 보냈지만 여전히 같은 관심사를 가진 친구를 찾을 수 없었기에, 이번 시도가 시간이 지나면서 결실을 맺기를 바랍니다. 어떤 식으로든 제 작업이 유용하기를 바랍니다.

제가 뭔가 잘못한 게 있다면 알려주세요. 번역가가 좋은 일을 해서 여러분을 울게 하지 않았기를 바랍니다 :) 화이팅!

OSMHungary Matrix szobában merült fel a kérdés, hogy melyik a legkényelmesebb házszámfelvivő app. Every Door (ED) és StreetComplete (SC) rajongók is jelezték, hogy az általuk használt app szerintük a nyerő, de konkrét összehasonlítást nem írt senki. Mindenkinek az a kényelmes amit ismer és használ természetesen, szóval úgydöntöttem, én majd összehasonlítom a kettőt, minél objekívebben.

ED-t már nagyon régen használtam, így letöltöttem újra, és végignyomogattam benne a funkciókat, hogy részletesen teszteljem ott milyen házszámokat felvinni mostanában. SC-ből én az Expert Editiont használom, de ez a funkció ugyanaz mindkettőben, SCEE nem ad hozzá ehhez a nézethez semmi pluszt, a képernyőképek a hagyományos SC-ben készültek.

Térkép nézet

Házszámozás workflow eléggé hasonló, mindkét programban egy külön nézetre kell váltani, bekapcsolni.

SC-ben a térképen a felvitt házszámokat kétféleképpen jeleníti meg: ha pontokon szerepelnek akkor egy kék pötty, ha épületen akkor az egész épület kék kitöltést kap. Házszám hiányát úgy lehet észrevenni, hogy az épület nincs így kiemelve, és nincs benne kék házszám pont sem.

ED-ban a felvitt és hiányzó házszámok is egy szövegdobozként jelennek meg, ahol van házszám ott a számot írja ki, ahol hiányzik, ott egy kérdőjel jelenik meg a.

Nagy különbség, hogy ED-ban csak a házszámok látszanak ilyenkor az alaptérkép felett, míg SC-ben az általános küldetések is.

… See full entry

人間によって整備された公園を指します。自然のままに維持されている公園は対象外です。

公園の敷地全体

= このコードブロックをコピーして、JOSMでCtrl+Shift+Vで貼り付けることができます。
= 先頭がイコールの行はJOSMで無視されます。

= 人工的な公園であることを表す。
leisure=park 
= 公園の名前
name=
= 管理者
operator=
= 所有者
owner=
= 一般公衆が利用可能; 特定の人のみが利用可能な場合はprivate
access=yes
= 24時間開放; 曜日や時間帯によって閉鎖される場合は変更
opening_hours=24/7
= 犬
dog=
= フェンスや壁などで公園の敷地が囲まれている場合
barrier=

電力線以外 (電話回線やインターネット回線) は対象外。

電力線とともに電話線がある場合でも、communication=lineは使用しない (このタグは海上ケーブルなどを対象としている)。

配電線 (送電線ではない)

power=minor_line
frequency=60 ← 関西は60、関東は50

三相6600V (高圧)

voltage=6600
cables=3
circuits=1

単相±100V

voltage=100; 200
cables=3
circuits=1

三相200V & 単相±100V (工場用)

voltage=100; 200
cables=4
circuits=2

電線の終端 (住宅などへの引き込み部分)

power=terminal
line_attachment=anchor

電線の分岐点 (電柱無し)

power=connection
cables=電線の本数

電柱

power=pole
line_attachment=anchor
material=concrete
operator=*
ref=*

変圧器付きの電柱 (単相) 6600V→±100V

変圧器は1個

transformer=yes
location=outdoor
voltage:primary=6600
voltage:secondary=200;100
phases:primary=1
phases:secondary=1

変圧器付きの電柱 (三相) 6600V→三相200V & 単相±100V

変圧器は2個

transformer=yes
location=outdoor
voltage:primary=6600
voltage:secondary=200;100
phases:primary=3
phases:secondary=3

building=residential
building:level=地上の階数 ← (2階建ての場合は2)
addr:*=住所

一世帯住宅

building=house

★他の世帯と壁を共有しない一世帯住宅 (最も一般的な一軒家)

building=detached

他の世帯と壁のみを共有する一世帯住宅 (壁越しに住んでいる)

building=semidetached_house

★集合住宅 (アパート/マンション)

building=apartments
building:flats=部屋数
name=アパート名

operator=管理会社の名前
operator:wikidata=Q00000 ← 管理会社のウィキデータ項目
operator:phone=電話番号 ← 管理会社の電話番号
operator:website=URL ← 管理会社の公式サイト
operator:addr:*=住所 ← 管理会社の住所

owner=大家さんの名前
smoking=yes/no ← 喫煙可能かどうか
wheelchair=yes/no/limited ← 車椅子で利用できるかどうか

vir: Hišna imena

Dodano:

• 2025-07-13: Polje pri Vodicah
• 2025-07-13: Adergas
• 2025-07-14: Medvode - Preska
• 2025-07-15: Medvode
• 2025-07-16: Medvode - Svetje

タグ付けに関する個人的なメモを書いています。

間違っている所があるかもしれません。間違いを見つけたらコメントしていただければ幸いです。

下に追記していきます。ある程度まとまったら別のエントリに移す予定です。

住所

地番と住居表示

地番

• addr:block_number=地番 (基本的に数字)
• addr:housenumber=支号 (必ず数字)

住居表示

• addr:block_number=街区符号 (基本的に数字)
• addr:housenumber=住居番号 (必ず数字)

字

• 字 (あざ)
• 大字 (おおあざ)
• 小字 (こあざ)

郵便番号

原則、町域 (町の名称から丁目を除く部分および大字の区域) までが表される。

電話番号

OSMではDIN 5008の書式で記述。

• 電話番号はスペースで区切る。
• 加入者番号と内線番号の間はハイフンで区切る。

国際電話から掛けられない電話番号 (フリーダイヤル、ナビダイヤル)

• contact:phoneではなくcontact:phone:JPを使用する。他のタグも同じく:JPを付ける。
• 国内電話の形式で記述する。
• 例: contact:phone:JP=0120 XXX YYY
• 0120, 0800, 0570

携帯電話

• 法律的には0X0-YYYY-ZZZZではなく0X0-YYY-ZZZZZとなる。
• DINにすると+81 X0 YYY ZZZZZとなる。

Tim ban kb 4 phuong

Questions

1. Does OSM track the last time a user made an diary entry?
2. Does the last map edit timestamp on a user’s profile indicate only the edits made to maps or diaries and notes as well?