OpenStreetMap
이 도로가 계속 차로 수가 변경되서 같은 이름 다른 차로 수의 도로를 차로 수가 바뀔 때마다 끊어서 따로 새로 추가하고 있습니다. 도움 부탁드립니다.
도로 링크 : 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 등 아파트 모여있는 개발계획구역 쪽)만 편집 중입니다. 혹시나 정자동 쪽도 도움 주실 수 있으면 부탁드립니다.
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.
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.
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.
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.
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.
Zapraszam wszystkich do wspólnego mapowania tego pięknego, ciekawego i historycznego regionu Polski.
Zachęcę po Kurpiowsku :
Καλησπέρα σε όλους και όλες,
Σας προσκαλώ στην συνάντηση της ελληνικής κοινότητας του OpenStreetMap στην Αθήνα. Ευκαιρία να μαζευτούμε οι χαρτογράφοι της Ελλάδας και να πιούμε έναν δροσιστικό καφέ μες την ζέστη του καλοκαιριού, ώστε να γνωριστούμε καλύτερα και να συζητήσουμε διάφορα σχετικά με το OSM. Και μετά να κάνουμε χαρτογράφηση στη γύρω περιοχή :slight_smile:
🗓️Ημερομηνία και ώρα: Σάββατο 26 Ιουλίου, 15:00
🔗Τοποθεσία: Piu Verde, Άλσος Παπάγου
Το Piu Verde εκτός από καφέ, προσφέρει και φαγητό, για όποιον θέλει μιας και θα είναι κοντά μεσημέρι.
Όσοι επιθυμείτε να παρευρεθείτε, συμπληρώστε το όνομα σας εδώ.
🗓️🔗Σύνδεσμος συνάντησης στο OpenStreetMap Calendar: https://osmcal.org/event/3920/
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
Editing OpenStreetMap data in QGIS
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
-Quality Assurance Tools such as OSMCha, OSM Inspector, Keep Right and Osmose
-The use of Map Roulette and Map Paint Styles
우선, 저는 한국어를 못해서 자동 번역입니다. 저는 러시아 출신이지만 지난 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.
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.
人間によって整備された公園を指します。自然のままに維持されている公園は対象外です。
= このコードブロックをコピーして、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
voltage=6600
cables=3
circuits=1
voltage=100; 200
cables=3
circuits=1
voltage=100; 200
cables=4
circuits=2
power=terminal
line_attachment=anchor
power=connection
cables=電線の本数
power=pole
line_attachment=anchor
material=concrete
operator=*
ref=*
変圧器は1個
transformer=yes
location=outdoor
voltage:primary=6600
voltage:secondary=200;100
phases:primary=1
phases:secondary=1
変圧器は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:
タグ付けに関する個人的なメモを書いています。
間違っている所があるかもしれません。間違いを見つけたらコメントしていただければ幸いです。
下に追記していきます。ある程度まとまったら別のエントリに移す予定です。
地番
住居表示
原則、町域 (町の名称から丁目を除く部分および大字の区域) までが表される。
OSMではDIN 5008の書式で記述。
Tim ban kb 4 phuong
Most of our mapping parties, if not all, start with a brief introduction. The newbies are informed about the various benefits of using and contributing to OpenStreetMap, such as massive improvements to the individual’s privacy and an easy mechanism to correct data.
However, I have been wondering if this approach is the optimal path. This doubt started nagging me after I picked up The Theory of the Leisure Class by Thorstein Veblen. If class distinctions are really so pervasive as theorized in the book, shouldn’t we try to incorporate these findings in our promotion of OSM in mapping parties and everywhere else?
A clear description of the context would be in order. Though our existing method of extolling the benefits of OSM is good, I don’t think it is the best one for India. India has, unfortunately, one of the lowest proportion of people contributing to social activities. In conversation with my friends, I often find them considering the idea of “doing something for free” repugnant. Maybe its due to the oppressive nature of the Indian classes, where people’s aspirations are mostly reduced to the singular objective of rising above their current class. Whatever is the reason, we can at least conclude that the current system of promoting OSM is unsatisfactory in the context of India.
We can, for instance, try to frame OSM as a hobby and actively compare the intensity of mapping activity with other mappers (say, by focusing on the heat map that is displayed on the OSM profile page). Setting aside the moral considerations this entails, I believe this approach is likely to bring some interesting results. People may or may not be excited by the idea of increasing their reputation by performing conspicuous leisure in the form of contributions. However, it must be tested on field before we derive any conclusions.
This diary entry was first posted on my website under CC BY-NC-SA 4.0.
Depuis avril 2025, j’ai entrepris un travail de terrain minutieux pour cartographier les lampadaires dans la commune de Jassans-Riottier (01). Mon objectif principal : relever les numéros de référence (ref) visibles sur place et les intégrer dans OpenStreetMap.
Chiffres clés
1 253 lampadaires présents dans OSM sur la zone
835 lampadaires référencés avec un ref visible
418 lampadaires sans ref dans OSM (lampadaires non numérotés ou refs absentes)
Numérotation maximale terrain connue : 1 357 lampadaires
Environ 100 lampadaires à cartographier encore pour atteindre la numérotation maximale
Méthode
Relevés terrain par secteur, avec photos et vérification
Comparaison des données OSM, Overpass, et numérisations communales
Gestion des cas particuliers (lampadaires remplacés, refs effacées, numérotation partielle)
Mises à jour régulières sur OSM
Résultats
Ce travail améliore significativement la qualité des données d’éclairage public sur OSM dans la région, facilitant la maintenance et le suivi des infrastructures. Cela contribue aussi à la précision des cartes et des services dépendants de ces données.
À venir
Finalisation des relevés à Jassans-Riottier prévue pour fin octobre 2025
Compléter la numérotation sur les lampadaires sans ref
I have been retired since 2020 after a long career in networking and IT security.
Since then, I’ve spent my time walking (nothing too ambitious: no mountains, but still around 2,000 km per year) and doing math (a lifelong hobby, mainly algebra focused on functional equations).
I discovered OSM very recently (spring 2025) when switching from Windows to Linux MINT and trying out my first smartphone with LineageOS (a de-Googled Android).
At first, I thought it was just a freely editable map application, before realizing that it is in fact:
a vast open-source application ecosystem leveraging this geospatial database for a wide variety of uses:
to contribute or make smart, efficient, even fun use of it.
to use the database for various purposes aimed at diverse audiences:
So I created an account, joined OpenStreetMapFrance (not mandatory), and tried to understand enough of the principles, limitations, and recommendations to contribute effectively.
I’m now a regular reader of the WIKI and the forum (even though I sometimes struggle to follow whole conversations – such as those about hiking route relations, linear or networked…).
