Users' Diaries
Recent diary entries
F4 es uno de los pocos visores de OpenStreetMap que ha estado en servicio ofreciendo renderizado en 3D por muchos años. Han habido otros servicios, pero cuando se muestra F4 cualquier persona se descresta. He empezado a mapear en 3D, y muchas de las grandes contribuciones, principalmente en Denver, en este ámbito han sido de chachafish. Lo quise contactar para obtener algunos tipos de un experto, pero dejó de mapear desde 2020 (en plena pandemia :( ), entonces me tocó buscar otras opciones.
En el wiki, en communities, hay información dispersa, pero no muestra todas las posibilidades que tiene esta herramienta. Entonces, decidí indagar en la misma página de F4 map, y encontré 2 páginas muy interesantes: render y changelog. En ellas se describe en cierto desorden todo lo que puede hacer esta herramienta.
Entonces, decidí darle un orden, extraer las etiquetas que usa y ahí tener una mejor idea de cómo debo hacer 3D mapping. Fue ahí cuando recordé Taginfo, y decidí listar este visor en este directorio, por lo que creé una entrada: https://github.com/angoca/f4demo-in-taginfo/blob/main/taginfo.json.
Además de lo anterior, es necesario manejar los colores para que se visualice más cercano a la realidad. Para eso se puede usar esta guía de nombres de colores.
Esperemos que esto sea de ayuda para que más personas se aventuren en el mapeo 3D, sobretodo teniendo un poquito más de documentación.
Yo comencé con un pequeño ejercicio en el norte de Bogotá, y estoy muy contento con el resultado del Centro Comercial Plaza Norte:
For years, an issue with Kurdish language, Arabic script, and OpenStreetMap tiles has been on my radar. In 2023 I got OSM to update Noto fonts on the tile server, but Google has moved their latest changes to individual repos.
I’m continuing to workshop a PR for that.. but in the meantime, I thought to check if OSM needs more of the language-specific Noto fonts. Back in spring 2019 I did a mini survey of where Unicode blocks were used around the OSM world.
Today I added Python scripts to check Planet PBF files (specifically name and alt_name tags on nodes) and find usage across Unicode blocks.
There are names with Latin alphabet and frequently associated characters (superscripts and subscripts, dingbats, diacritics, IPA, half-width, old italic, runic, spacing modifiers, punctuation, emoticons/emoji, and symbols from math, music, currency, and maps).
-
Africa has: TIFINAGH, ARABIC (supplements and presentation forms), CYRILLIC, ETHIOPIC, NKO, HEBREW, CJK, HANGUL, and GREEK.
-
Asia has: CYRILLIC, GREEK, HEBREW, ARABIC, SYRIAC, COPTIC, ETHIOPIC, BALINESE, JAVANESE, CJK + YI + BOPOMOFO + KANGXI, HANGUL, MONGOLIAN, TIBETAN, THAI, MYANMAR, LAO, KHMER, ARMENIAN, GEORGIAN, THAANA, SINHALA, TAMIL, ORIYA, BENGALI, GURMUKHI, GUJARATI, DEVANAGARI, KANNADA, MALAYALAM, OL_CHIKI, and TELUGU.
For the Americas, OSM already includes fonts for Cherokee and Canadian Aboriginal Symbols.
Those two scripts and OGHAM, TAGBANWA, and BAMUM were misused in Asia. The instance of TAGALOG script was a little uncertain. I removed an Apple logo because it’s from the Private Use Area.
The current font download script is pretty good, and includes additional fonts (Adlam and Tai Viet) which aren’t actively used.
so the beach town is seeing growth again, after the primary developers went bust in 2007/8. A large amount of blank land between the shops and the harbour has been cleared, and given asphalt roads, concrete footpaths, and brackish ponds for the mosquitoes to grow in! I hope the new holiday home owners like mosquitoes!
My GPS accuracy is not great and my note taking while walking is worse; but I’ve drawn some new ways on the new footpaths; and verified some of the existing paths from Kenwood Drive to Waimarie Ave are still approximately where my GPS says they are. Good fun.
Need to go back with a laptop next summer to add/tweak more. Hopefully LINZ has updated by then to provide even better coverage
The State of the Map Asia 2024 conference wasn’t held in a main travelers’ hub like Thailand but rather chose a much, not that well-known country Bangladesh, and its previously unsettled political situation, which ended with the Prime Minster fleeing to India. Summarizing all these factors might discourage most people from visiting this country, ended up most of the attendees are domestic, and plus someone like me who is a foreigner is lucky enough to obtain a VISA to pay a visit.
Bangladesh is a young country, during the conference we saw many attendees were students, who might help those international aid projects to gather map data. We can see teachers bring their students to attend the conference. And there are also various student clubs, like all Youthmappers in Bangladesh, publishing their project results. One day we might see when the country is prosperous, and students grown up, there is a chance that they will map shops and buildings in the city where they live.
I want to write something about the general participant situation here in the Asia Pacific area. In developed countries like Taiwan, there are individuals who launch interest groups to map specific map features or netizens with enough motive to contribute to OpenStreetMap project. There are other countries that rely on aid projects to map local map data, and sometimes there are sone who will map modern map features. I have heard a talk about solar pannels in Dahka.
The State of the Map Asia splits its session into quite strange 10-minute parts. I accidentally submitted two talks, and did not get rejected. I had to give a talk on the first and second day, one I introduced the community in Taiwan, and the other day I introduced some interesting projects hosted by individual mappers.
這改 State of the Map Asia 2024 大會,毋是佇逐家愛去𨑨迌的旅遊勝地泰國舉行,顛倒是佇民風較祕思,國家較封閉的孟加拉舉行。而且佇落尾的時,確實有人簽證問題無法度入境到位會場。閣加添孟加拉政局無穩定,進前總理流亡,共頭前講的原因加加起來,予世界各國的人無想欲來。這个大會會當講是孟加拉人為主,極加加添我這款會當入境的外國人。
孟加拉是少年人的國家,一般看著的參與者是學生,幫贊國際援助計畫累積基礎的地理圖資。閣有參與的老師𤆬學生,有各種的社團,比喻講孟加拉各大學的 YouthMappers 組織攏有參與,發表𪜶參與的計畫。應該是有一工社會發達,一陣學生較有歲,相信下開始畫四箍圍的店頭佮都市的建築。
閣來講起亞太的開放地圖的參與情形,除了社會經濟狀況允準以外,會當有個人發起的興趣小組佮有貢獻動機的網路鄉民以外,足濟是用援助計畫的資源來進行基礎圖資的繪製,順紲執行較現代的議題,親像講綠能相關的,比喻講達卡的日頭能枋的分佈。
演講的部份,𪜶用較奇妙的十分鐘為一个單位進行,家己無細膩投兩份演講,著勉強共平常時紹介 OpenStreetMap 的簡報拆做兩份,第一工紹介台灣的社群,進行的計畫佮未來展望,第二天就是講個別台灣社群成員的計畫。
當時欲入境孟加拉拄著挑戰,予移民官擋咧留話,愛主辦單位出面解釋,才予入境。落尾到位 Cox’s Bazar,除了佇會場發表,嘛聽捌人的經驗,體驗孟加拉旅遊勝地,會當講是孟加拉的墾丁𨑨迌踅踅。我逐家會當到海沙埔散步,體驗印度洋的海風佮海波浪。這馬回想一逝旅行,對孟加拉落地簽申請的難題,趁大會佇孟加拉舉辦的機會來到孟加拉,解鎖一个南亞國家的成就。
這次 State of the Map Asia 2024 並非在旅遊聖地泰國舉行,而是比較封閉的孟加拉,光是簽證就很容易搞死人。而在最後關頭,的確是有很多人就無法到場,簽證沒過無法入境。再加上前陣子孟加拉政局動盪,總理流亡,綜合以上種種因素,導致各國的人不大前往參與。孟加拉人為大宗的大會,再加上能有辦法進來的外國人
在會場觀察參者的人好有活力,很多援助計畫在協助積累當地基礎的地理圖資。另外參與的人口年輕,像是老師帶著學生參與,各種年輕團體組團,例如孟加拉各大學的 YouthMapper 組織都有參與,發表相關的計畫。當社會漸漸發達,大家年紀變年長,相信應該會有人轉為畫生活活動範圍的商家與都市地帶的建築。
而回到亞太這邊的開放街圖參與狀況,除了社會經濟情況允許而能以自發的興趣小組與有貢獻動機的網路鄉民之外,很多是用援助計畫的資源從事基礎圖資的繪製,順便去進行比較是近代的議題,像是跟綠能相關的,如達卡的太陽能板分佈的繪製
演講部分,他們用蠻奇特的十分鐘時間為單位進行,而自己不小心投了兩份演講,就硬著頭皮講了兩場,基本上是自己25+5演講拆一半的內容,各自在兩場演講。第一天談台灣社群,進行的計畫與未來展望,而第二天談個別的社群成員常在進行的計畫。
儘管移民官還有機場設施不是那麼友善,但我順利到達 Cox’s Bazar,除了在會場發表還有聽別人的經驗分享之外,也趁機到這個孟加拉的渡假聖地遊覽,每天到沙灘走走,體驗印度洋的浪與風。回想這一切,孟加拉簽證難申請,趁這次大會在孟加拉,解鎖到這一南亞國家遊歷的成就。
See pt1 of this series here.
See pt2 of this series here.
See pt3 of this series here.
How Does This Relate To OSM Again?
If you have been following the articles listed above, you will know the Field Mapping Tasking Manager (FMTM) is a tool developed by HOTOSM to improve the quality of field verified data associated with geometries.
In the OSM world, this means adding and improving tags for OSM geometries.
A key element of this work flow is conflation of newly collected data with existing data in OSM. Some preliminary work was done on this, but for now the team decided to pivot and focus entirely on improving the usability of FMTM from the perspective of mappers.
The conflation work will be continued further down the line.
Currently, Rob Savoye is also continuing some work in parallel for conflation of roads in the USA, with OSMUS’s osm-merge project.
The roadmap for FMTM can be found here.
Easier Field Mapping
Since release 2024.5.0, we have be focusing on what we have dubbed the ‘Mapper Frontend’.
Our primary goals:
-
Mapping should be as intuitive as possible for users, requiring minimal training or existing knowledge (with prompts).
-
The application should be fast and responsive, tailored to field mapping needs.
-
Data should load real-time, significantly improving the collaborative team experience. Joe wants to know where Jim is mapping currently, to avoid overlap.
-
A secondary goal is the potential to package it up in a mobile app wrapper, allowing for easy distribution via mobile app stores.
Had to move the summit as it was in a random place. It’s really cool up there.
Youth Mappers University of Nairobi chapter
El mapeo de interiores no es muy popular ya que requiere conocimientos de la distribución de los espacios dentro de un edificio. Normalmente esto se hace por medio de un plano, que puede ser el de evacuación. Aunque aquí empieza el problema de permisos de uso de datos para mapear en OpenStreetMap.
En Colombia estamos comenzando esta labor, pero quise listar lo que se ha hecho en Latam, y reconocer a los mapeadores:
- 들어가기에 앞서, LuxuryCoop님의 기존 제안을 보고 영감을 얻어 새로 올린 글입니다. 아래 글을 읽어보기에 앞서, 해당 글을 먼저 읽어보시는 것을 추천드립니다.
본 게시글에서는 지역의 label 태그를 위계별로 어떻게 사용하여야 할 지에 대하여 특히 주목하여 작성해 보았습니다. 기본적으로 OSM Wiki에 명시된 대로 각각의 place 태그에 대한 원론적인 위계에 주목하여 한국의 행정 구역 라벨 위계를 새로이 구성해 보았습니다.
공식 행정구역
광역자치단체
-
https://wiki.openstreetmap.org/wiki/Tag:place=province- 도(道), 특별시, 광역시, 특별자치도, 특별자치시에 사용
해당 태그는 일반적으로 주나 도 등 국가의 1차 행정구역을 나타낼 때 사용되며, 언급한 자치단체 모두 동일하게 대한민국의 1차 행정구역을 나타내므로 모두 ‘province’로 동일하게 표현하였습니다.
기초자치단체
-
https://wiki.openstreetmap.org/wiki/Tag:place=city- 시(市) -
https://wiki.openstreetmap.org/wiki/Tag:place=county- 군(郡)
시와 군의 경우는 현행 유지되는 태그를 그대로 사용하였습니다.
-
https://wiki.openstreetmap.org/wiki/Tag:place=district- 특별시, 광역시 등의 자치구 -
https://wiki.openstreetmap.org/wiki/Tag:place=borough- 자치구가 아닌 구; 일반구
자치구의 경우 시, 군과 동등한 위계에 있는 기초자치단체로써, 지방 정부에 의해 자치적으로 운영되는 행정 구역이라는, OSM Wiki에 설명되어 있는 district과 그 사용례를 같이 한다는 점에 착안하여 district로 제안해 보았습니다.
일반구의 경우, 자치구와 마찬가지로 구(區)라는 명칭을 공유한다는 점은 존재하지만, 자치구와 달리 별도의 자치권이 없는 시(市) 내부의 하위 행정구역이라는 점을 고려할 때, 자치구와는 다른 태그를 이용하여 이를 표현해야 할 필요성이 있다고 생각하였습니다. 이러한 점을 고려할 때, 일반적으로 도시 ‘내부’의 구역임을 나타내는 ‘borough’ 태그를 사용하여 달리 표기하는 것을 제안하는 바입니다.
-
https://wiki.openstreetmap.org/wiki/Tag:place=subdistrict- 행정동
현행에서는 https://wiki.openstreetmap.org/wiki/Tag:place=quarter가 동을 표현하는 데 사용되고 있지만, 해당 태그는 행정 구역을 명시한다기보다 도시 내 특정 구역을 태그하는 데 이용되는 점을 고려해보면, 거주 규모와는 별개로 행정구역임을 명확히 명시하는 subdistrict 태그를 이용하여 행정동을 표현하는 것이 좀 더 합리적이지 않을까 제안합니다. district와 연계하는 경우 구와 동의 계층이 명확해진다는 점도 존재합니다.
-
?- 법정동
‘법정동’의 경우는 일부 명칭을 제외하고는 지적 사무 외 행정적 사무와 실생활에서는 거의 쓰이지 않는다는 점을 고려할 때 지역적으로 잘 알려진 몇 법정동명을 제외하고는 법정동 relation의 name으로만 존치하고 label은 삭제합니다. 또한, 잘 알려진 몇 법정동명의 경우에는 규모에 따라suburb/quarter/neighbourhood로 구분하여 남기는 것을 제안합니다.
사실 법정동의 경우에는, 제가 제안하는 위계 구조 상에서 명확히 처리하기에는 애매한 바가 있어서, 혹시 이와 관련하여 좋은 의견 있으면 남겨주시면 감사하겠습니다.
-
https://wiki.openstreetmap.org/wiki/Tag:place=town- 읍(邑)/면(面)
Нам нужно больше пользоваться сервисами для панорам, такими как Panoramax.
Яндекс это конечно отличный сервис, но он все же не самый дружелюбный к OSM’у, и права на его панорамы могут отозвать в любой момент. Призываю всех неравнодушных людей у которых есть файлы уличных панорам (или даже фотографии уличных объектов) зайти на https://panoramax.openstreetmap.fr/upload и загрузить их туда. У iD есть отдельный слой для панорам с этого сайта, и у людей которые картируют с него будет больше открытых данных с которых будет удобнее брать информацию.
Hey hey. We at the Yerevan Tree Map project were pulling to our database new nodes tagged as https://wiki.openstreetmap.org/wiki/Tag:natural=tree for a while now, without actually pushing changes back. Now we are starting to do so. The OSM API is not quite straightforward, so we’re learning on the go. We have some 4k plus trees to push, we’ll be adding them in small batches. Later we’ll start pushing updates to existing tree nodes (e.g. when someone measures the tree or updates its state).
(English below, thanks to Deepl.com)
Ce post a été initialement publié ici.
Des données OSM en anglais, mais aussi en français, accessibles dans l’IFL pour les pays francophones du Sud
Des données OSM téléchargeables avec des attributs dans une langue autre que l’anglais, non pas avec un service web, mais une plateforme dédiée au partage de données et métadonnées géographiques, où l’on peut comprendre, voir, interroger, filtrer avant de télécharger : c’est ce que permet cette approche ETL (pour Extract, Transform, Load, soit en français « Extraction, Transformation et Chargement ») dans l’Infrastructure de Données Spatiales des Libres Géographes. Dans ce billet, je reviens sur le contexte et l’historique de ce projet personnel mené sur mon temps libre, avant d’expliquer l’approche technique mise en œuvre et, évidemment, comment accéder à ces données.
Le contexte : sortir du « english fits for all »
Si l’anglais domine l’écosystème OSM et reste la langue de référence du projet, plusieurs initiatives permettent aux non-anglophones de participer au projet et d’en bénéficier : un forum multilingue, la traduction du wiki et de certaines plateformes d’auto-apprentissage, des interfaces utilisateur traduites pour les applications et les éditeurs, y compris les préréglages d’étiquettes OSM.
Mais quelle que soit la technologie ou le service utilisé, les données OSM brutes, une fois téléchargées, restent exclusivement en anglais, et toute recherche ou filtrage des données OSM dans un logiciel SIG ne peut se faire que dans cette langue.
Ayant beaucoup formé à l’utilisation des données OSM en géomatique (notamment QGIS) depuis 2011, j’ai été vite confronté aux difficultés qu’ont pas mal de francophones non anglophones à exploiter les attributs des données OSM. Difficultés d’autant plus frustrantes, dans le cas des pays du Sud, qu’il s’agissait souvent des premières données détaillées disponibles sur leur territoire. Une barrière se levait, mais une autre lui succédait.
I just discovered https://github.com/openstreetmap/tile-attribution And it seems like a great way to get involved with openstreetmap via GitHub - It doesn’t require any coding ability, one would need an active GitHub acount to add an issue to the issue tracker but basically find a site using your favourite search engines (lets say https//ddg.gg as an example).
Check any sites who are not providing attribution to openstreetmap when using openstreetmap and report the full hostname of website to the issue tracker :-)
What can we all share to people on social media we use to promote friends & family to support OpenStreetMap’s work?
Have a great day! Josh G of Australia.
HIII!!! happy new year! i’ve decided to try an maintain a editing streak for the entirety of 2025 and it’s going pretty well (at time of writing i’ve edited daily since december 25th of 2024)! nothing much aside from that i just try to use streetcomplete when bored lol
![]()
El Palacete Pinho, en el barrio Ciudad Vieja en Belém de Pará (Brasil), fue la sede de la tan ansiada reunión de mapeadoras y mapeadores de Latinoamérica. Habían pasado cinco años (pandemia incluida) del último SOTM en Encarnación, Paraguay. Pero, para mí, eran seis años, desde la última vez que participé en el evento, en 2018, en Buenos Aires. Así, que ese hermoso palacio, ubicado a pocos metros del río Acará, fue el espacio en el que nos conocimos, encontramos y reencontramos; durante un fin de semana aprovechamos para reconectar con la comunidad regional de OpenStreetMap. De este modo, finalizamos una semana llena de eventos que comenzó con la FOSS4G el lunes antes de ese fin de semana.
El brote de cólera de 1854 en Londres representa un hito fundamental en la historia de la epidemiología. Este estudio de caso nos transporta a una época en la que la comprensión de las enfermedades infecciosas era limitada y las teorías sobre su propagación eran muy diferentes a las actuales. A través de la meticulosa investigación de John Snow, descubriremos cómo un médico logró desentrañar el misterio de este brote, desafiando las creencias establecidas y sentando las bases de la epidemiología moderna. Este caso no solo nos enseña sobre la importancia de la investigación epidemiológica para controlar enfermedades infecciosas, sino que también nos revela cómo la combinación de observación cuidadosa, pensamiento crítico y métodos innovadores puede conducir a descubrimientos transformadores en el campo de la salud pública y ¡Lo descubrió haciendo el primer análisis geoespacial de la historia!
Starting the new year with milestone achievements! In this 22nd development update, we’re excited to present comprehensive mobile support improvements across OpenStreetMap-NG. We’ve also reached critical development milestones that put us on the final stretch toward public beta testing.
🔖 You can read other development diaries here:
@NorthCrab/diary/
⭐ This project is open-source — join us today:
https://github.com/openstreetmap-ng/openstreetmap-ng
🛈 This initiative is not affiliated with the OpenStreetMap Foundation.
Video Summary
This week’s video demonstration focuses primarily on our mobile interface improvements. Through practical examples and side-by-side comparisons, I showcase how OpenStreetMap-NG elevates the mobile experience.
⬇ Click the image below to play
